Sep 30

Calling Party Number for Mobile Connect (SNR) on Internal Phones

Had a request from a customer to see about removing a prefix from the calling party number when a known Mobile (Remote Destination) calls an office extension phone. The prefix was interfering with call-back and visual display in Missed Calls. So the scenario was mobile 0420999xxx would call into the Office, this mobile is configured as a Remote Destination, therefore the system matches it with the internal extension (ext. 4000). The call proceeds to ring an internal extension, however the calling party display number is 04000. Zero is the access code for PSTN Calls.

I found the MGCP Gateway (this also relates to SIP and H323 gateways in CUCM) was directing the call to a translation pattern. This translation pattern was prefixing a ‘0’ to the calling party number. So even though the system matched the remote destination number to an extension the translation pattern still proceeded to prefix a ‘0’. This is because the transformation of the remote destination number to the associated extension is actioned at the gateway level when the call first arrives. But the Translation pattern prefixes a ‘0’ to all calls to extensions from the Gateway including calls from the transformed remote destination.

How to Resolve

There a few options to work around this issue. I was working with an MGCP Gateway, so I will opt to change add a prefix ‘0’ at the Gateway configuration page. There are four rows containing call types. International, National, Subscriber and Unknown. These types cover all possible calling party types. Under the Prefix Digit column, I will enter a ‘0’ into all the rows. I will also ensure the Use Device Pool checkbox is unchecked for each call type.

Then open the translation pattern and remove the Calling Party Prefix digit of ‘0’.

Make a test call and the calling number should only display the extension. Plus all other calls from the PSTN should maintain the ‘0’ prefix.

May 09

Cisco Licensing Snippet – Single Number Reach (SNR)

Cisco Licensing for CUCM 9.0+ caters for a few different scenarios through the use of licensing levels/types. CUWL Pro, CUWL Standard, UCL Enhanced / Plus, Basic and Essential. I will go through the main type of licensing in a later blog, but for now I’ll explain the licensing requirements / quirks around Single Number Reach (SNR).

Mobile Connect and SNR are to describe the same feature in CUCM, which is to allow users to have inbound calls redirected to their mobile devices (or other PSTN Numbers) automatically. This feature can be managed by the user themselves, configuring schedules, disabling the service, changing phone numbers, or configuring the number of times my deskphone will ring before I want the call to be directed to my mobile phone etc. Just about all of my Telephony deployments have included this requirement.

So now, for the licensing aspect. An End User with the ‘Mobile Connect’ box checked will consume a single Basic License. For those who don’t manage their CUCM license with care, enabling SNR for all users in the Business will blow out your licensing budget.

As shown in the below image, I have 14 Basic Licenses being consumed by the SNR feature alone. This can tip me over the licensing edge if I don’t have my devices configured correctly.

CUCM License Summary

The next image shows that I have consumed a Basic License and I do not own any other Device. This is important to note.

CUCM Basic License

What happens if I didn’t purchase any Basic Licenses?

As we all know Cisco CUCM licensing levels allow the lower levels to borrow licenses from the upper levels. Example. SNR will consume a Basic License, but if there are no Basic Licenses to allocate, it will look to the next level and check if the Enhanced license level has any available licenses to allocate, if not, the system will check the next level repeating the process all the way to CUWL Professional. So in effect your single SNR enabled feature can consume a CUWL Pro License, and I’m sure you didn’t spend all that money of CUWL Pro licenses for it just to be consumed by the SNR feature.

How to Avoid Consuming a Basic License

If you know your CUCM licensing basics, you’ll know that UCL Enhanced allows an end user to own a single device, a UCL Enhanced Plus license allows you to own two devices, CUWL Stand and Pro allows you to own 10 devices, so you could say CUCM 9.0+ licensing is now very user centric.

So, here is the trick, not a trick really just configuring CUCM Licenses correctly. You need to assign ownership for devices to your end users. That’s it. So if you have UCL Enhanced Plus, configure the users deskphone to have an owner. By configuring this, the SNR feature will sit within the boundaries of the UCL License and NOT consume any additional licenses. I did say CUCM licensing is user centric, this is just a way for Cisco to force you to configure Owners for Devices.

The below image is a snippet from a Device Configuration page, showing the Owner Field.

CUCM Device Page

Couple more screen shots displaying the UCL Enhance Plus license summary page in CUCM, detailing a user who owns two devices and also has the SNR Feature enabled.

CUCM UCL Enhance Plus Summary

Continuing from the above screen shot, displays the actual details for this UCL Enhanced Plus User. As you can I also added an Analogue device to this End User to show that both IP Phones and Analogue Devices can be assigned ownership.

CUCM UCL Enhanced PLus License Detail