Single Number Reach and MobileConnect

        Single Number Reach allows users to give out a single number and be reached on multiple devices (maximum of four). When calling a user’s Single Number Reach DID, four seconds (default) go by before ringing the user’s remote destinations (eg. cell phone, home phone, etc.). Once the remote destination is ringing, the Send Call to Mobile Menu Timer Service Parameter (default 60 seconds) defines the amount of time the remote destination(s) has to pick up the call.

        Users/Administrators can set the schedule (days/times) that SNR is active for each of their remote destinations though the ccmuser or appadmin GUI.

        MobileConnect allows users to receive a call on their primary device (desk phone) and press the Mobility soft-key or line button which calls their remote destination device (eg. cell phone). Once the user picks up their remote device, the call is connected on their remote device and the person they are talking to is none the wiser. MobileConnect also allows users to hang up their remote destination device and seamlessly pick the call up on their primary phone (default time to pick up is 10 seconds).

How to configure Single Number Reach and MobileConnect:

1. Create End User and verify that the user is associated to their phone and that “Enable Mobility” (uses 4 device licenses per user, and 2 if adjunct) and “Enable Mobile Voice Access” is checked along with their Primary User Device selected.
1. Selecting the Primary User Device takes the Mobility Enabled End User license and changes it into an Adjunct license.
2. Under Enable Mobile Voice Access is the Maximum Wait Time for Desk Pickup which is defaulted at 10 seconds. This is the time (in milliseconds) that the user has to pick up the MobileConnect call after hanging up their remote destination device. It is recommended that if users are not at their desk, that they let the other party hang up first as their call may be hijacked at their desk.
2. Create/modify a SoftKey Template to include Mobility.
1. If the user’s phone is a 8900/9900 series phone, a Phone Button Template must be created with a Mobility line key.
3. On the user’s phone, apply the new softkey (or phone button template) and select the user under the Owner User ID.
1. If the Owner User ID is not selected, MobileConnect will fail with a message stating “You are not a valid Mobile Phone User”.
2. If the Owner User ID is grayed out, it is because you have Extension Mobility selected. The Cisco Help Guide states that you should not have both EM and Owner User ID selected, but I’ve tested and it works fine.
4. Under Device > Device Settings > Remote Destination Profile create a new RDP for each MobileConnect/SNR user.
1. For the call to actually reach the external number, the Rerouting Calling Search Space is the CSS that controls this.
2. You must select a Rerouting CSS that can reach the PSTN or the SNR will fail for external numbers.
3. Make sure the Privacy setting is set to "Default"
5. Under Device > Destination Profile create a new RD for each MobileConnect/SNR user.
1. You must put the user’s remote destination here along with the out-dialing number(s) such as 91 or 81, unless it is an internally reachable extension. Always associate the line for SNR to work.
2. Instead of using 91 or 81 for dialing out, you can also set an Application Dial Rule which will be triggered for SNR.
6. Under System > Service Parameters, select the Cisco CallManager service.
1. Verify that "Privacy Setting" is set to True (default)
2. Verify that "Enforce Privacy Settings on Held Calls" is set to False (default)
3. You cannot transfer a call from a cell phone to a desk phone if the Remote Destination Profile Privacy specifies On, and the "Enforce Privacy Setting on Held Calls" service parameter specifies True.
7. Reset the user’s phone and test SNR and MobileConnect.

.