Cisco Unified Mobility enforces the following limitations in operating with other
Cisco Unified Communications Manager components:
Call anchoring, which is performed based on caller ID, gets supported only from calls from registered single-mode or dual-mode phones
You do not need to configure settings for call forward unregistered, if the end user has configured remote destinations. Appropriate call forwarding will get handled as part of the Mobile Connect process.
Cisco Unified IP Phones 7940 and 7960 That Are Running SIP
When running SIP,
Cisco Unified IP Phones 7940 and 7960 do not support the Remote-in-use state and therefore cannot support desktop call pickup.
For these phones, if the mobile phone user hangs up a call that the
Cisco Unified IP Phone 7940 or 7960 that is running SIP extended to the mobile phone, the calling party hears music on hold for ten seconds (as configured by the Maximum Wait Time for Desk Pickup field for the remote destination end user) and then the call drops. Because the desktop call pickup feature does not get supported for these phones when they are running as SIP devices, the user desk phone does not display the Resume softkey, so the user cannot pick up the call on the desk phone.
Cisco recommends that you configure
Cisco Unified IP Phones 7940 and 7960 to run SCCP for users that are enabled for
Cisco Unified Mobility.
Users cannot initiate a meet-me conference as conference controller by using Mobile Voice Access but can join a meet-me conference.
If an existing conference call is initiated from a shared-line IP phone or dual-mode phone or smartphone that is a remote destination, no new conference party can get added to the existing conference after the call is sent to a mobile phone or a dual-mode handoff action occurs. To permit the addition of new conference parties, use the Advanced Ad Hoc Conference Enabled service parameter.
Dialing + Character From Mobile Phones
Users can dial a + sign through DTMF on a mobile phone to specify the international escape character.
Cisco Unified Mobility does not support + dialing through DTMF for interactive voice response (IVR) to make an outgoing call from a mobile phone to an enterprise IP phone for which the directory number contains the + character.
Cisco Unified Mobility does not support + dialing through DTMF for two-stage dialing to make an outgoing call from a mobile phone to an enterprise IP phone for which the directory number contains the + character.
For more information about configuring the international escape character in
Cisco Unified Communications Manager Administration, see the
Cisco Unified Communications Manager System Guide.
DND on the Desk Phone and Direct Calls to Remote Destination
If Do Not Disturb (DND) is enabled on a desk phone, the desk phone cannot be placed in the Remote In Use (RIU) state and the call does not get anchored in these cases:
DND is enabled with the call reject option—The call cannot get anchored.
DND is activated by pressing the DND softkey on the desk phone—The call cannot get anchored.
If DND is enabled with the ring off option, however, the call does get anchored.
Dual-Mode Handoff and Caller ID
Dual-mode handoff requires that caller ID be available in the cellular network.
Dual-Mode Phones and Call Anchoring
Dual-mode phones (
Cisco Unified Mobility Advantage and dual-mode phones that are running SCCP or SIP) that are configured as remote destinations cannot anchor calls.
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 disappear if the dual-mode phone goes out of WLAN range.
Dual-Mode Phones and Desktop Call Pickup
The desktop call pickup feature does not apply to the following mobile phone models:
Nokia 902iL and Nokia 906iL dual-mode phones that are running SIP
Nokia S60 dual-mode phones that are running SCCP
For these phone models, if the mobile phone user hangs up a call, the calling party hears music on hold for ten seconds (as configured by the Maximum Wait Time for Desk Pickup field for the remote destination end user) and then the call drops. Because the desktop call pickup feature does not get supported for these phone models, the user desk phone does not display the Resume softkey, so the user cannot pick up the call on the desk phone.
Dual-Mode Phones That Are Running SIP and Registration Period
For dual-mode phones that are running SIP,
Cisco 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.
Enterprise Features From Cellular Networks
Enterprise features from cellular networks require out-of-band DTMF.
When using intercluster DNs as remote destinations for an IP phone via SIP trunk (either intercluster trunk [ICT] or gateway), check the Require DTMF Reception check box when configuring the IP phone, so DTMF digits can be received out of band, which is crucial for Enterprise Feature Access midcall features.
Enterprise Features in GSM That Is Using DTMF
Availability of enterprise features in GSM that is using DTMF depends upon the features that are supported in the third-party smartphones.
Forced Authorization Code and Client Matter Code
The Forced Authorization Code and Client Matter Code (FAC/CMC) feature does not work with Mobile Voice Access nor with Enterprise Feature Access two-stage dialing.
The Forced Authorization Code (FAC) does not get invoked for Mobile Connect [Single Number Reach (SNR)] calls to a remote destination.
Gateways and Ports
Both H.323 and SIP VoIP gateways get supported for Mobile Voice Access.
Mobile Connect features do not get supported for T1 CAS, FXO, FXS and BRI.
Maximum Wait Timer for Desktop Call Pickup Does Not Get Applied If Hold DTMF Is Pressed
If a user presses the *81 DTMF code from a remote destination (either a smartphone or any other phone) to put a call on hold, the user desk phone displays the Resume softkey. The desk phone does not apply a timer for desktop call pickup, however; the Resume key does not stop displaying after the timeout that is configured for the end user to pick up the call and the call does not get dropped.
Instead, users should hang up the call on the remote phone, which triggers the desk phone to apply the timer for desktop call pickup. (Use the Maximum Wait Time for Desk Pickup field on the End User Configuration window to change this setting.)
Mobile Connect Support Restrictions
The Mobile Connect feature gets supported only for Primary Rate Interface (PRI) public switched telephone network (PSTN) connections.
For SIP trunks, Mobile Connect gets supported via IOS gateways or intercluster trunks.
Multilevel Precedence and Preemption (MLPP)
Mobile Connect does not work with Multilevel Precedence and Preemption (MLPP). If a call is preempted with MLPP, Mobile Connect features get disabled for that call.
Multiple-Node Cluster Environment
In a multiple-node cluster environment, if the
Cisco Unified Communications Manager publisher server is unreachable, any changes that end users make to turn Mobile Connect off or on by way of Mobile Voice Access or two-stage dialing do not get saved.
Overlap sending patterns do not get supported for the Intelligent Session Control feature.
Mobility does not support QSIG.
QSIG (Q Signaling) path replacement does not get supported.
Remote Destination Profiles
When configuring a directory number that is associated with a remote destination profile, you must use only ASCII characters in the Display (Internal Caller ID) field on the Directory Number Configuration window.
Ensure remote destinations are Time Division Multiplex (TDM) devices. You cannot configure IP phones within a
Cisco Unified Communications Manager system as remote destinations.
Ensure remote destinations specify PSTN numbers or numbers across ICT trunks.
Remote destinations cannot resume calls that
Cisco Unified IP Phones put on hold.
Enterprise feature access service parameters apply to standard phones and smartphones; however, smartphones generally use one-touch keys to send the appropriate codes. Administrators must configure any smartphones that will be used with Mobile Connect to use either the default codes for enterprise feature access or the codes that are specified in the smartphone documentation.
Session Handoff Feature
The following limitations apply to the Session Handoff feature:
Session Handoff can take place only from mobile phone to desk phone. For the other direction, the current Remote Destination Pickup method specifies using Send Call to Mobile Phone.
Only audio call session handoff gets supported.
SIP URI and Direct Calls to Remote Destination
The Intelligent Session Control feature does not support direct URI dialing. Therefore, calls made to a SIP URI cannot be anchored to an enterprise number.
Mobile Connect services do not extend to video calls. A video call that is received at the desk phone cannot get picked up on the mobile phone.