Professional Documents
Culture Documents
Cisco Number ANALY - Get Practical
Cisco Number ANALY - Get Practical
Hey guys!
Here is Bruno, and I’ll be in charge of the Cisco side of this Blog, more speci�cally, Collaboration.
For my opening post, I’d like to talk about a feature on CUCM that, due all this pandemic situation, is being largely
implemented.
Cisco Single Number Reach (SNR), or known as Mobile Connect, is a feature which allows users to
answer incoming calls to their extension on either their desktop IP phone or at a remote
destination, such as a mobile phone.
As many companies had to send employees to work from home, SNR becomes really useful to cover some gaps
To give you some practical examples, there were 2 situations where I con�gured SRN to save
user’s life.
In the �rst, a small company didn’t have a good infra to send users to home (lack of
bandwidth, poor VPN) and in the second, users were vendors and �rewalls didn’t allow them
to have Jabber connected to VPN.
In both situations, users had to receive calls from a queue on UCCX.
I came up with SNR for both cases, so users could work from home, and even though they
weren’t using any softphone, they could answer calls coming from they extension.
Although Cisco does not mention in its Documentation, I con�gured and tested SNR with
UCCX with success
When a call comes in to your Extension Number, SNR will reroute the call not only to a DN,
but also to your remote number, that can be your mobile phone. If needed, you can con�gure
rerouting to a group of remote numbers that belong to an employee.
In other words, SNR provides you a functionality similar to Shared Line. The di�erence is that
in this case a shared line is organized between an o�ce phone and some remote device that
isn’t necessary in a cluster, not between the phones within a cluster.
In the End User page, make sure the Device is already associated in the Controlled Devices
and its Line is assigned as Primary Line
Check the Enable Mobility check box. You can also, modify the Maximum Wait Time for Desk
Pickup and Remote Destination Limit if required. Moreover, the default values can be seen in
the image.
Con�guring Remote Destination Pro�le
You can choose any name, associate your user ID, give a calling search space and a rerouting
CSS.
CUCM attempts to reach the remote destination through the Rerouting calling search Space.
Click Save, now you can see an option to add a new Directory number (DN) .
Click Add a new DN to navigate to directory number con�guration, where you need to specify
the directory number of the desk phone with which you need to associate the RDP and then
click Save.
Con�guring Remote Destination
Single Number Reach Voicemail Policy provides two options: Timer control and User Control,
of which the former one is default.
Under the section Timer information, you can specify the amount of delay before which the
Remote Destination should ring.
In case if the Remote Destination is required to ring immediately, you should set the Wait as 0.
It is also important to calibrate the time in which the service provider of the remote
destination sends the call to the voice-mail of the remote destination. The Stop ringing this
phone after value should be set lesser then that to ensure that call does not go to the
voicemail of the cell phone. This time value is speci�ed against Stop ringing this phone after.
If the SNR voicemail policy is con�gured for User Control, timer information changes as shown
in the image:
In case the SNR con�guration needs to be restricted based on time and day then these
options are modi�ed as required. If no restriction is needed to be applied then Ring Schedule
should be set to All the time and When receiving a call during the above ring schedule should
be set to Always ring this destination.
After you complete the con�guration of remote destination, click Save.
Check the checkbox, which is next to the line and click Save.
Bruno Falco
Bruno Falco / 1st Mar 2021 / Cisco, CUCM / Cisco, Collaboration, CUCM, SNR
Like
5th May 2022 at 11:10 PM
Like
Get Practical /