McDewey

Restrictions Feature Unified Communications Manager uses“ beep” and “beepbeep” tones when a new party is added and when the new party drops from the Ad Hoc conference, respectively. When a party is added to an Ad Hoc conference, a user on a phone that is running SIP may not hear the beep; when a participant drops from the Ad Hoc conference, a user on a phone that is running SIP may not hear the “beepbeep”. Users might not hear the beeps because of the time it takes Unified Communications Manager to set up and tear down connections during the conferencing process. You can invoke Ad Hoc conference linking for phones that are running SIP only by using the Conference and Transfer functions. The system does not support Direct Transfer and Join. Supported phones that are running SIP comprise Cisco Unified IP Phone 7911, 7941, 7961. Ad Hoc conference on SIP phones: • Cisco Unified IP Phone 7911 • Cisco Unified IP Phone 7941 • Cisco Unified IP Phone 7961 • Phones display individual calls as conference calls. Cisco Unified IP Phones 7940 and 7960 can create local conference calls but not Ad Hoc conference calls. • Conference list (ConfList), is not available. • Remove last conference participant (RmLstC), is not available. • Drop Ad Hoc conference is not supported. • The SIP Profile parameter Conference Join Enabled controls behavior of the phone that is running SIP when the conference controller exits a locally hosted conference. If the Conference Join Enabled check box is unchecked, all legs disconnect when the conference controller exits the Ad Hoc conference call. If the Conference Join Enabled check box is checked, the remaining two parties stay connected. • To achieve the same level of control that the Drop Ad Hoc Conference parameter settings provide for conference calls that a phone that is running SCCP initiates, the administrator can use a combination of the Conference Join Enabled SIP profile parameter and the Block OffNet to OffNet Transfer service parameter for conferences that are initiated on the phone that is running SIP (Cisco Unified IP Phone 7940 or 60). (Because the phone that is running SIP performs a transfer when it drops out of the conference call, the Block OffNet to OffNet Transfer can prevent toll fraud by not allowing two offnet phones to remain in the call.) • Unified Communications Manager uses “beep” and “beepbeep” tones when a new party is added and when the new party drops from the Ad Hoc conference, respectively. When a party is added to an Ad Hoc conference, a user on a phone that is running SIP may not hear the beep when a participant drops from the Ad Hoc conference, a user on a phone that is running SIP may not hear the “beepbeep”. Users might not hear the beeps because of the time it takes Unified Communications Manager to set up and tear down connections during the conferencing process. Ad Hoc conference on SIP phones: • Cisco Unified IP Phone 7940 • Cisco Unified IP Phone 7960 • Third-Party Phone Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 229 Conferencing Features Conference Restrictions