Cisco CUCM – Controlling Phones Remotely

Hey guys,

Today I’m going to talk about a very useful feature which gives us power to control remotely a Deskphone, and even make calls from it.

image

First things first, you will need to install an extension to your Browser, to be able to control the phones.

If you are using Google Chrome, download the extension HERE.
If you are using Mozilla Firefox, download the extension HERE.

CUCM Configuration

With the Browser extension installed, let’s check now what do we need to do on CUCM.
It’s pretty easy!

  • Phone Web Access
    Make sure the deskphone is enabled for Web Access. Go to the Device’s Page, scroll down till you see the Web Access option. It must be Enable.

    image

  • NEW End User
    We could use any End User for that. But, as I’m centralize all requests in one user, I decided to create a new one only for that.
    Each phone you want to control, you have to associate to that End User.
    So, create a new user, associate as many phones as you want to Control, and add a Rule you have in your CUCM which gives them ability to control the phones.

imageimage

  • Remote Control
    After installing the Browser extension, and configuring the Phone and End User, now it’s time to test the Remote Control.
    Go to CUCM, find the Phone you want to access and get the IP Address (Phone must be registered)
    PS: If you are controlling a phone which is MRA registered, you will need to be able to route to its real IP Address

image

As soon as you click on the IP Address, to access the Phone’s information, you will notice now something different. The option Control Me will be displayed.

image

Then, you will be asked to enter the Username and Password, from the End User we created above.

image

And now you have the Phone’s screen being displayed, with all available commands next to it.
From there, you can access the Settings, change configuration, and even Make calls…

image

Hope you enjoyed this quick, but useful and interesting Tip! Smile

See ya!!

Bruno

Media Resources on CUCM (Conference Bridge and Transcoder)

Hi people,

In this post I’ll cover a little bit of resources on CUCM, more specifically Transcoding and Conference Bridge.

The requirements to have them configured on your Voice Gateway, and consequently being used on CUCM, are DSPs.
DSPs reside either directly on a voice network module, on PVDM2s that are installed in a voice network module or on PVDMs that are installed directly onto the motherboard, such as on the Cisco 2800 and 3800 series voice gateway routers.

Having your DSP, let’s configure this bad boy in your Voice Gateway.

  • Configuring SCCP

!— This sccp ccm command adds CallManager server(s) !— to the list of available servers to which the voice gateway can register.
Gateway(config)#sccp ccm 192.168.252.18 identifier 18 priority 1 version 4.1
Gateway(config)#sccp ccm 192.168.198.10 identifier 5 priority 2 version 4.1
Gateway(config)#sccp ccm 192.168.198.11 identifier 4 priority 3 version 4.1
Gateway(config)#sccp ccm 192.168.198.12 identifier 11 priority 4 version 4.1

!— Selects the local interface that SCCP applications !— use to register with CUCM.
Gateway(config)#sccp local loopback 1

!— Enables SCCP and brings it up administratively.
Gateway(config)#sccp Gateway(config)#exit

  • Configuring DSP Farm for Transcoding


!— The dsp services dspfarm command enables DSP farm services for the voice card.

Gateway(config)#voice-card 0
Gateway(config-voicecard)#dsp services dspfarm


!— The dspfarm profile 111 transcode command enters the !— DSP farm profile configuration mode !— to define a profile for DSP farm services. !— For this profile, a transcode profile is created.

Gateway(config-voicecard)#exit
Gateway(config)#dspfarm profile 111 transcode


!— Specifies the codecs supported by a DSP farm profile.

Gateway(config-dspfarm-profile)#codec ?
   g711alaw      G.711 A Law 64000 bps
   g711ulaw      G.711 u Law 64000 bps
   g729abr8      G.729ab 8000 bps
   g729ar8       G.729a 8000 bps
   g729br8       G.729b 8000 bps
   g729r8        G.729 8000 bps
   pass-through  Stream Pass Through

!— Specifies the maximum number of sessions that are !— supported by the profile. !— Number is determined by the available registered !— DSP resources.
Gateway(config-dspfarm-profile)#maximum sessions 20

!— The associate application sccp command associates the SCCP protocol !— to the DSP farm profile.
Gateway(config-dspfarm-profile)#associate application sccp

!— Enables the profile, allocates !— DSP farm resources, and associates the application.
Gateway(config-dspfarm-profile)#no shutdown
Gateway(config-dspfarm-profile)#exit
Gateway(config)#gateway

!— Sets the Real-Time Transport !— Protocol (RTP) timeout interval to clear hanging connections. !— Seconds range is 180 to 1800. The default is 1200.
Gateway(config-gateway)#timer receive-rtp 600

  • Creating Call Manager group

Gateway>enable
Gateway#configure terminal
Gateway(config)#sccp ccm group 111

!— Adds a Cisco Unified CallManager server to the Cisco !— Unified CallManager group and establishes its priority within the group.
Gateway(config-sccp-ccm)#associate ccm 18 priority 1
Gateway(config-sccp-ccm)#associate ccm 5 priority 2
Gateway(config-sccp-ccm)#associate ccm 4 priority 3
Gateway(config-sccp-ccm)#associate ccm 11 priority 4

!— Associates a DSP farm profile to the Cisco Unified CallManager group. !— The device-name must match the device name configured in Cisco Unified CallManager.
Gateway(config-sccp-ccm)#associate profile 111 register DE_XCODE_01


!— Binds an interface to the Cisco Unified CallManager group.

Gateway(config-sccp-ccm)#bind interface loopback 1
Gateway(config-sccp-ccm)end

Now, let’s do the same for Conferencing Bridge

The process is purely the same, so I’ll just put the commands here:

Gateway>enable
Gateway#configure terminal
Gateway(config)#voice-card 0
Gateway(config-voicecard)#dsp services dspfarm
Gateway(config-voicecard)#exit
Gateway(config)#dspfarm profile 999 conference
Gateway(config-dspfarm-profile)#description conference profile 999
Gateway(config-dspfarm-profile)#codec ?
   g711alaw      G.711 A Law 64000 bps
   g711ulaw      G.711 u Law 64000 bps
   g729abr8      G.729ab 8000 bps
   g729ar8       G.729a 8000 bps
   g729br8       G.729b 8000 bps
   g729r8        G.729 8000 bps
   pass-through  Stream Pass Through

Gateway(config-dspfarm-profile)#maximum sessions 4
Gateway(config-dspfarm-profile)#associate application sccp
Gateway(config-dspfarm-profile)#no shutdown
Gateway(config-dspfarm-profile)#exit
Gateway(config)#gateway
Gateway(config-gateway)#timer receive-rtp 600
Gateway(config-gateway)#exit

Gateway>enable
Gateway#configure terminal
Gateway(config)#sccp ccm group 999
Gateway(config-sccp-ccm)#associate ccm 18 priority 1
Gateway(config-sccp-ccm)#associate ccm 5 priority 2
Gateway(config-sccp-ccm)#associate ccm 4 priority 3
Gateway(config-sccp-ccm)#associate ccm 11 priority 4
Gateway(config-sccp-ccm)#associate profile 999 register 00C88B514BDF
Gateway(config-sccp-ccm)#bind interface loopback 1

Gateway(config-sccp-ccm)end

Time now to add them to our Unified Communications Manager

  • Transcoder

On CUCM, go to Media Resources >> Transcoder >> Add new

Choose Cisco IOS Enhanced Media Termination Point for the Transcoder Type, and fill the rest with your Device Pool,  and for the Device Name, use the name you added on the Gateway:

image

Save and Reset it. You must see it as registered

  • Conference Bridge

On CUCM, go to Media Resources >> Conference Bridge >> Add new

Choose Cisco Conference Bridge Hardware for the Conference Bridge Type, and fill the rest with your Device Pool, Location, and for the Mac Address, use the name you added on the Gateway:

image

Save and Reset it. You must see it as registered

Now, added them both in a Media Resource Group, and then add this group to a Media Resource Group List.

Job done!!

Cheers Smile

Cisco Single Number Reach

Hey guys!
Here is Bruno, and I’ll be in charge of the Cisco side of this Blog, more specifically, 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 you may have in your infrastructure.

To give you some practical examples, there were 2 situations where I configured SRN to save user’s life.
In the first, 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 firewalls 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 configured and tested SNR with UCCX with success  Smile

So, how does this work?

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 configure 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 difference is that in this case a shared line is organized between an office phone and some remote device that isn’t necessary in a cluster, not between the phones within a cluster.

image
Said that, let’s get down to business!

What do you need to configure?

Configuring End User

Configuring Remote Destination Profile

Configuring Remote Destination

Configuring End User

In the End User page, make sure the Device is already associated in the Controlled Devices and its Line is assigned as Primary Line

imageimage

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.

image

Configuring Remote Destination Profile

Time to create a new Remote Destination Profile.
On CUCM, go to Device > Device Settings > Remote Destination Profile > Add new

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.

image

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 configuration, where you need to specify the directory number of the desk phone with which you need to associate the RDP and then click Save.

imageimage

Configuring Remote Destination

Time to configure the Remote Destination.
Specify the Destination number, as this is the number for your Remote destination.
Ensure that the check box, Enable Unified Mobility features, Enable Single Number Reach, Enable Move to Mobile is checked.

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 specified against Stop ringing this phone after.

image

If the SNR voicemail policy is configured for User Control, timer information changes as shown in the image:

In case the SNR configuration needs to be restricted based on time and day then these options are modified 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 configuration of remote destination, click Save.

IMPORTANT STEP!!!
Check the checkbox, which is next to the line and click Save.

image

That’s all guys!
I hope this post will help you out!

See ya!

Bruno Falco