Chapter 19 Do Not Disturb
Overview of Do Not Disturb Architecture
•Beep
•Flash
You can configure DND Incoming Call Alert on a
Overview of Do Not Disturb Architecture
This section provides an overview of DND architecture for both SIP and SCCP devices and includes the following topics:
•DND Status Notification for SIP Devices, page
•DND Status Notification for SCCP Devices, page
DND Status Notification for SIP Devices
Cisco Unified Communications Manager supports Do Not Disturb that a SIP device initiates or that a Cisco Unified Communications Manager device initiates. A DND status change gets signaled from a SIP device to Cisco Unified Communications Manager by using the SIP PUBLISH method (RFC3909). A DND status change gets signaled from a Cisco Unified Communications Manager to a SIP device by using a dndupdate
DND Status Notification for SCCP Devices
Cisco Skinny Client Control Protocol (SCCP) supports Do Not Disturb requests that an SCCP device initiates or that a Cisco Unified Communications Manager device initiates. A DND status change gets signaled from an SCCP device to Cisco Unified Communications Manager by using SCCP messaging.
System Requirements for the Do Not Disturb Feature
The following sections provide software and hardware requirement for Do Not Disturb:
•Software Requirements, page
•Hardware Requirements, page
Software Requirements
To operate, the Do Not Disturb feature requires the following software components:
•Cisco Unified Communications Manager Release 7.0(1) or later
Cisco Unified Communications Manager Features and Services Guide for Cisco Unified Communications Manager Business Edition
|
| ||
|
|
