McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 82

↗ View in doc context
page
82
source
cucm/v15/feature-config-guide/feature-config-guide.md
chunk_id
cucm::v15::feature-config-guide::feature-config-guide::38

Description Restriction Dual-Mode Handoff and Caller ID The handoff DN method of dual-mode handoff requires a caller ID in the cellular network. The mobility softkey method does not require caller ID. Dual-Mode Phones and CTI Applications While a dual-mode phone is in Wi-Fi enterprise mode, no CTI applications control it nor monitor it. The In Use Remote indicator for dual-mode phones on a shared line call in the WLAN disappears if the dual-mode phone goes out of WLAN range. Dual-Mode Phones and SIP Registration Period For dual-mode phones, Unified Communications Manager determines the registration period by using the value in the Timer Register Expires (seconds) field of the SIP profile that associates with the phone, not the value that the SIP Station KeepAlive Interval service parameter specifies. The standard SIP profile for mobile devices determines the registration period as defined by the Time Register Expires field in that profile. Dual-Mode Phones Enterprise features from cellular networks require out-of-band DTMF. When using intercluster DNs as remote destinations for an IP phone over a SIP trunk (either intercluster trunk or gateway), check the Require DTMF Reception check box when configuring the IP phone. This allows DTMF digits to be received out of band, which is crucial for enterprise feature access midcall features. Enterprise Features From Cellular Networks Both H.323 and SIP VoIP gateways are supported for mobile voice access. Cisco Unified Mobility features are not supported for T1 CAS, FXO, FXS and BRI. SNR(Single Number Reach) is not supported with MGCP(Media Gateway Controlled Protocol). Gateways and Ports When initially configured, Jabber devices count as registered devices. These devices increase the count of registered devices in a node, set by the Maximum Number of Registered Devices service parameter. Jabber Devices Cisco Unified Mobility supports a maximum of nine locales. If more than nine locales are installed, they appear in the Available Locales pane, but you can only save up to nine locales in the Selected Locales pane. If you attempt to configure more than nine locales for Cisco Unified Mobility, the following message appears: “Update failed. Check constraint (informix.cc_ivruserlocale_orderindex) failed.” Locales Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 40 Remote Worker Features Cisco Unified Mobility Restrictions