The Do Not Disturb (DND) feature provides a subscriber the capability to block incoming calls during periods of time that the subscriber does not wish to be disturbed. Features such as CFSIE-DND and endpoint-based call forwarding on busy can be used to redirect the calling party to another destination while DND is active.
The subscriber can continue to originate calls while DND is active.
If DND is active, incoming calls are handled in one of the following ways:
If an applicable call forwarding is active, the call is diverted to the configured forwarding target
Otherwise the call is either rejected with SIP message "480 Temporarily Unavailable" (default for external calls) or the call is diverted to an intercept announcement that indicates the reason the call cannot be completed to the expected destination (standard for internal calls).
The administrator defines the behaviour for external calls
by setting the RTP parameter Srx/Main/DNDAnnAlways either to RtpFalse (reject with 480) or RtpTrue (announcement).
Subscribers have to be provisioned for the DND service in order to be able to use server-based DND.
OpenStage phones should be configured for uaCSTA and Server Based Features. To allow the server-based feature to be de-/activated from generic SIP phones (e.g. OptiPoint), Prefix Access Codes for the DND De-/Activate
(Do Not Disturb Deactivate/Activate) vertical services have to be created in adequate numbering plans.
Lotus Sametime Unified Telephony Enterprise Communications SIP endpoints also provide an endpoint-based DND feature. However, if configured and active, the Lotus Sametime Unified Telephony-based feature takes precedence over the local feature. Server- and endpoint-based DND shouldn't be active at the same time.
How to Provision a Subscriber for Server-based Do Not DisturbParent topic: Calling Services
CFSIE - Do Not Disturb
This procedure describes how to configure Do Not Disturb at the feature profile or subscriber level. Feature profiles, in turn, can be created and configured at the switch level or the BG (Business Group) level. At the subscriber level, the previously assigned feature profile can be overwritten to selectively enable, disable or modify the feature configuration for the particular subscriber. Those subscriber-level modifications effectively disconnect the individual service configuration from the underlying feature profile: a subsequent Reset Subscriber Lines
on the feature profile will not influence a disconnected subscriber's service configuration.
RTP Management via Telephony Control Server Assistant