On Cisco Unified IP Phones, the message that indicates that the Do Not Disturb (DND) feature is active takes priority over the message that indicates that the user has new voicemail messages, which allows the user to know when DND is active. However, the message that indicates that the Call Forward All feature is active has a higher priority than DND.

For locally parked calls, Park Reversion overrides DND (both options). If Phone A has DND turned on and parked a call, the park reversion to Phone A will occur normally and will ring Phone A.

For remotely parked calls, DND overrides Park Reversion:

• If Phone A activates DND Ringer Off and shares a line with Phone A-prime, when Phone A-prime parks the call, park reversion on Phone A will not ring and will honor the DND settings.

• If Phone A activates DND Call Reject, the park reversion call will not be presented to Phone A.

For a locally placed Pickup request, Pickup overrides DND (both options). If Phone A has DND turned on and has initiated any type of Pickup, the Pickup call would be presented normally, and it will ring Phone A.

For a remotely placed Pickup request, DND overrides Pickup.

• If Phone A (with DND Ringer Off activated) shares a line with Phone A-prime, when Phone A-prime initiates Pickup, the Pickup call to Phone A will not ring and will honor DND settings.

• If Phone A is in DND Call Reject mode, the Pickup call will not be presented to Phone A.

Hold reversion and intercom override DND (both options), and the call gets presented normally.

MLPP (phones that are running SCCP) and CER calls override DND (both options). MLPP and CER calls get presented normally, and the phone will ring.

For the originating side, callback overrides DND. When the activating device is on DND mode (both options), the callback notification (both audio and visual) will still be presented to the user.

For the terminating side, DND overrides callback:

• When the terminating side is on DND Ringer Off, the Callback Available screen will be sent after the terminating side goes off hook and on hook.

• When the terminating side is on DND Call Reject and is available (goes off hook and on hook), a new screen will be sent to the activating device as "<DirectoryNumber> has become available but is on DND-R" if the activating device is in same cluster. Callback available notification will be sent only after the terminating side disables DND Call Reject.

For the DND Ringer Off option, only visual notification gets presented to the device.

For the DND Call Reject option, no notification gets presented to the device.

If a device in a Hunt List has DND Ringer Off activated, the call will get still presented to the user when a call gets made to that Hunt List. However, the DND Incoming Call Alert settings would still apply.

If a device in a Hunt List has DND Call Reject activated, any calls to that Hunt List will go to the next member and will not get sent to this device.

For extension mobility, the device profile settings include DND incoming call alert and DND status. When a user logs in and enables DND, the DND incoming call alert and DND status settings get saved, and these settings get used when the user logs in again.

Note	When a user who is logged in to extension mobility modifies the DND incoming call alert or DND status settings, this action does not affect the actual device settings.

The following examples use the DND Ringer Off option.

Normal Priority Call with DND Ringer Off Enabled on a Nonshared Line

The following figure shows the steps that are associated with DND when you place a normal-priority call to a phone with DND Ringer Off enabled on a nonshared line:

1. Phone B activates DND. Phone B displays Do Not Disturb is active.

2. Phone A dials phone B.

3. Phone B beeps, and phone A receives ringback tone.

   

Normal Priority Call with DND Ringer Off Enabled on a Shared Line

The following figure shows the steps that are associated with DND when you place a normal-priority call to a phone with DND Ringer Off enabled on a shared line:

1. Phone B activates DND. Phone B displays Do Not Disturb is active.

2. Phone A dials a shared line on phone B.

3. Phone B beeps, and phone B', which shares the line, rings normally.

4. Phone A receives ringback tone.

   

High Priority Call with DND Ringer Off Enabled on a Shared Line

The following figure shows the steps that are associated with DND when you place a high-priority call to a phone with DND Ringer Off enabled on a shared line:

1. Phone B activates DND. Phone B displays Do Not Disturb is active.

2. Phone A dials a shared line on phone B.

3. Phone B beeps, and phone B', which shares the line, rings normally.

4. Phone A receives ringback tone.

5. Phone B answers and parks the call.

6. Park reversion occurs, and phone B rings normally.

   

Normal Call with DND and Call Forward No Answer Enabled on a Nonshared Line

The following steps show the call flow for a call that you make to a phone with both DND and Call Forward No Answer active:

1. Phone B configures Call Forward No Answer to forward calls to Phone C.

2. Phone B activates DND.

3. Phone A calls Phone B.

4. Phone B beeps and does not answer the call.

5. The call gets forwarded to phone C, which rings normally.

The following examples use the DND Call Reject option.

Normal Priority Call with DND Call Reject Enabled on a Nonshared Line

The following steps show the call flow for a call with Call Reject enabled on a nonshared line:

1. Phone B activates DND Call Reject with a DND Incoming Call Alert setting of Beep Only.

2. Phone A call Phone B.

3. Cisco Unified Communications Manager rejects the call with the reason User Busy.

4. Phone B gets a beep tone only.

Normal Priority Call with DND Call Reject Enabled on a Shared Line

The following steps show the call flow for a call with Call Reject enabled on a shared line:

1. Phone B activates DND Call Reject with a DND Incoming Call Alert setting of Beep Only.

2. Phone A call Phone B.

3. Cisco Unified Communications Manager rejects the call with the reason User Busy.

4. Phone B gets a beep tone only.

5. Phone B-prime, which is not on DND, rings normally.

High-Priority Call with DND Call Reject Enabled on a Shared Line

The following steps show the call flow for a high-priority call with DND Call Reject enabled on a shared line:

1. Phone A activates DND Call Reject with a DND Incoming Call Alert setting of Beep Only.

2. Phone A calls Phone B.

3. Cisco Unified Communications Manager extends the call the Phone B.

4. Phone B answers the call.

5. Phone A parks the call.

6. Phone A-prime, which is not on DND, rings normally.

7. Park Reversion occurs, and Phone A rings normally.