/mcpUse Cisco Unified CM Administration to configure third-party phones that are running SIP (For more information, see "Configure SIP Profile" topic in System Configuration Guide for Cisco Unified Communications Manager the ). The administrator must perform configuration steps on the third-party phone that is running SIP; see the following examples: • Ensure that proxy address in the phone is the IP or Fully Qualified Domain Name (FQDN) of Cisco Unified Communications Manager. • Ensure directory numbers in the phone match the directory numbers that are configured for the device in Cisco Unified CM Administration. • Ensure digest user ID (sometimes referred to as Authorization ID) in the phone matches the Digest User ID in the Cisco Unified CM Administration. For more information, refer to the documentation that came with the third-party phone. AS-SIP Conferencing MOH is applied to its target (a held party, transferee just before transfer, or conferee just before joining the conference), if the feature invoker (holder, transferor, or conference initiator) supports Cisco-proprietary feature signaling. If the feature invoker does not support Cisco-proprietary feature signaling, then MOH is not applied to its target. Also, if an endpoint explicitly signals that it is a conference mixer, then MOH will not be played to the target. There are two forms of AS-SIP Conferencing: • Local mixing • Conference Factory Local mixing To the Unified CM, the conference initiator simply appears to have established simultaneously active calls, one to each of the other conference attendees. The initiator host the conference locally and the voices are mixed there. The calls from the conference initiator have special signaling that prevent it from being connected to an MOH source. Conference Factory The conference initiator calls a Conference Factory Server located off a SIP trunk. Through IVR signaling, the conference initiator instructs the Conference Factory to reserve a conference bridge. The Conference Factory gives the numeric address (a routable DN) to the conference initiator, who then establishes a subscription with the bridge to receive conference list information to track the participants. The Conference Factory sends special signaling that prevent it from being connected to an MOH Source. AS-SIP Prerequisites Determine whether sufficient Device License Units are available. For more information, see"Smart Software Licensing" chapter from System Configuration Guide for Cisco Unified Communications Manager Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 815 QoS Management AS-SIP Conferencing