What is Do Not Disturb (DND) on my IP phone?

When focus matters, ringing breaks flow. DND keeps the phone quiet while calls still reach you in other ways—similar to the Do Not Disturb feature ¹ found across phones and UC apps.

DND stops your phone from ringing. The PBX or the phone either silences the alert or rejects the call so it goes to voicemail or a rule you set.

Below I explain how DND works, how it differs from forwarding and rejection, how to turn it on, which calls can still get through, and why some calls ring even when DND is active. I also give quick tables and steps you can follow today.

How does DND differ from call forwarding and call rejection?

These features look similar at first. In practice they act very different at the SIP layer.

DND suppresses alerts on your device. Call forwarding sends calls elsewhere. Call rejection refuses the call. Each one changes what the caller hears and where the call goes.

The simple idea

DND is about silence on your endpoint. It tells your phone or PBX to stop ringing and screen pop. The call may still route to voicemail or follow your busy rules. The call forwarding feature ² tells the PBX to send the call to a different target. Call rejection tells the PBX or phone to refuse the call outright.

What the caller hears

• DND (silent mode): The phone stays quiet. The PBX may still ring the line in the background for a short time, then send to voicemail.
• DND (reject mode): The phone or PBX sends a busy signal (often SIP 486 Busy Here ³). The caller hears busy or goes to voicemail fast.
• Call forwarding: The caller hears ringing at the new target. They may never hit your voicemail if the forward is unconditional.
• Call rejection: The caller hears busy or a fast failure message. No ring, no voicemail unless rules catch it.

Common SIP behavior (kept simple)

• DND often means your phone returns 486 to the PBX, or it just mutes the ringer and still answers after a timeout. Some systems also publish a presence event package ⁴ so co-workers see a red BLF or “DND.”
• Forwarding may send a 302 Moved Temporarily redirect ⁵ or the PBX may re-route the call under server rules.
• Reject is a straight 4xx response. No redirection unless the PBX adds one.

Which should you use?

Use DND when you want silence but still want voicemail and presence to reflect “busy.” Use forwarding when you want another person or device to take the call. Use reject when you want the call to fail fast or you need a rule based on “busy” state.

Quick comparison table

How do I enable DND on my IP PBX or handset?

You can toggle DND on the phone, in apps, or at the server. Pick one method and standardize it.

Use the phone’s DND key, a feature code, or a UC app toggle. For clean sync across devices, prefer server-controlled DND with presence.

Three ways to turn it on

1. Phone-local DND: Press the DND softkey or menu option. The phone mutes the ringer or sends busy on its own. Simple and fast.
2. Server-controlled DND: Toggle DND in your PBX/UC client or web portal. The server enforces busy treatment and updates presence for all devices on that line.
3. Feature codes: Dial a code like *78 to enable and *79 to disable. Good for users who live on headsets without a DND key.

Why server-controlled often wins

Server DND keeps everything in sync. Your desk phone, softphone, and mobile app all show the same state. Keys like Busy Lamp Field (BLF) ⁶ change. Queues and ring groups see your line as busy and can follow busy rules. Local-only DND may silence one device but leave others ringing.

Per-line or global?

Many multi-line sets let DND be per line or global. Decide which fits your workflow:

• Per line: Quiet one extension, leave another open (for exec-assist pairs or shared lines).
• Global: Silence the whole device (for meetings).

Common options to set in templates

• DND mode: Silent only vs reject with 486.
• Alert type: Off, beep-only, or visual flash.
• Publish presence: On, so teams see your state.
• Auto-off schedule: Clear DND at end of day.
• Intercom override: Allow or block paging during DND.
• Emergency bypass: Allow 911 alerts or not (see next section).

A simple rollout plan

• Put a DND toggle on a softkey for every template.
• Enable server DND sync across clients.
• Teach two ways to exit DND fast: press the key or dial the disable code.
• Document what callers hear and where calls land when DND is on. Users trust features they understand.

Will DND block emergency calls, intercom, or ring groups?

DND blocks inbound alerts to you. Outbound is not blocked. Some inbound types can bypass if allowed.

DND does not stop you from dialing out, including emergency calls. Inbound intercom, pages, or ring groups may bypass DND only if you enable priority or whitelist rules.

Outbound calls

DND affects incoming alerts to your device. It does not restrict you from making outbound calls. You can still dial coworkers, customers, and emergency services from the phone. Your call privileges stay the same.

Intercom and paging

By default, intercom and auto-answer paging are blocked by DND. Many systems add a priority/whitelist feature. If you enable it, certain extensions (e.g., security desk, broadcast system) can override DND and play at a set volume. Use this with care. Limit it to a small list and log every use.

Ring groups and queues

Behavior depends on where DND lives:

• Server-controlled DND: The PBX can mark your line busy/unavailable. Most queues skip you and pick the next agent. Many ring groups do the same.
• Local-only DND: Your phone may stay silent, but the PBX may still think you are idle. It might try to send you calls. The group rings “on paper,” but your handset stays quiet. This can hurt queue metrics. If you run a queue, prefer server DND.

Emergency alerts

Some deployments want emergency broadcast or priority calls to bypass DND. That is possible with priority levels or MLPP-like settings. Keep the list very short. Test with the safety team. Document the behavior so people know what to expect in a real event.

Recommended policy

• Keep outbound clear at all times.
• Block paging during DND unless the sender is on a security whitelist.
• Use server DND so ring groups and queues honor your state.
• Describe exceptions in a one-page user guide, and test them monthly.

Why do calls still ring when DND is enabled?

This is usually a scope or sync problem. Sometimes it is a group rule or an override.

Check if DND is local or server-based, confirm which line it applies to, and look for ring-group or priority bypass rules. Then test with a clean call.

The most common reasons

1. Local DND, server unaware
   You pressed DND on the handset, but the PBX still thinks you are idle. Queues and ring groups keep targeting you. Your phone stays silent, yet teammates hear it is “ringing you.” Fix by using server-controlled DND or enable presence publish from the phone.

2. Wrong line or account scope
   On multi-line phones, DND might be set only on Line 1. Calls to Line 2 still ring. Switch DND to global or set it per line as needed.

3. Whitelist or priority bypass
   You may have allowed boss, security, or paging to bypass DND. These will still ring or auto-answer. Review the override list and remove entries you no longer need.

4. Team or group policy
   Some ring groups ignore local DND by design. They ring every member to meet SLAs. Move to server DND so the PBX can mark you unavailable, or change the group strategy to skip DND users.

5. Mobile and soft client still active
   Your desk phone has DND, but your softphone does not. The soft client rings. Turn on DND in the app or use server DND so all devices sync.

6. Beep-only mode
   Your template may set DND to beep-only or visual-only. Users still hear a short tone. Switch to reject or true silent mode if needed.

7. Subscription/presence not updating
   BLF lamps and PBX state may lag if presence events are off. Enable presence and use the SIP Events framework (SUBSCRIBE/NOTIFY) ⁷ so state changes flow fast.

A quick diagnostic path

• Step 1: Confirm where you toggled DND (phone key, app, or code).
• Step 2: Check scope (per-line vs global). Try both if unsure.
• Step 3: Place a direct call to the extension. If this still rings, DND is not active on that target.
• Step 4: Try a ring group call. If only the group rings, review group policy for DND skip or ignore.
• Step 5: Review override lists (priority callers, paging). Remove test caller to verify.
• Step 6: Turn on server logs and a short SIP trace. Look for a 486 from your device or a server-side busy rule. If neither appears, DND is not engaged on the path you think.
• Step 7: Sync all devices. Sign out/in on soft clients, and push the latest provisioning to the set.

Settings that prevent surprises

Conclusion

DND is simple when rules are clear: use server-controlled DND for sync, set the right scope, keep overrides rare, and test with a quick direct call and a group call.

Footnotes