Removing leading digit from ANI received by Unity

Unanswered Question
Oct 24th, 2008

We have set up CUCM so that the ANI from the gateway is pre-pended with the external access code (9), so that when you hit the missed/received calls directory you can auto dial the number straight back. Sadly, this has the unwanted side effect that the ANI received by Unity now has a 9 in front of it, which is then posted on the email notifications to the user e.g. "you had a call from 902077551234" when what you really want is "you had a call from 02077551234". This is annoying the users who would like to dial the number back from their blackberry without editing the number.

Has anybody got a solution to this, either in CUCM, Unity, MS-Exchange or Blackberry?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (2 ratings)
Loading.
Brandon Buffin Fri, 10/24/2008 - 07:24

To my knowledge, there is no way in Unity to modify the ANI. One way to accomplish this is to create a translation pattern through which all calls to Unity pass. You can use the translation pattern to strip the 9.

Hope this helps.

Brandon

PETER NEGUS Fri, 10/24/2008 - 08:17

Hi Brandon

Thanks for your post. Ah, if only every country was like the US, and had a fixed length dial plan, the CUCM translation pattern would work. Sadly, I can't see a way of stripping the "9" in the translation pattern as it relies on a fixed length mask.

allan.thomas Fri, 10/24/2008 - 09:02

Since the release of Cisco CallManager version 3.3(3)SR1, there is an alternative solution available for prefixing numbers for incoming calls on MGCP devices within the CallManager service parameters.

Certainly from CUCM 4.1 you also have the option of configuring the prefix on Phone devices as well MGCP devices.

Have you tried specifically configuring the prefix on either Phone devices or MGCP devices.

Configuring the prefix on the phone device at least will ensure that your missed calls will have the 9 prefixed in the history.

Essentially there are four parameters within Cisco CallManager under the Clusterwide Parameters (Device - PRI and MGCP Gateway) section and also in (Device - Phone section), in the service parameters for Cisco CallManager.

They are:

National Number Prefix-This parameter defines the number that is prefixed to an incoming national number and provides a means to help identify national numbers, if necessary. This parameter allows you to prefix specified digits to the calling number of an inbound call based on the Type of Number field in an inbound offered call (ISDN SETUP message). For example, a national call from 4085551212 can be assigned the prefix 91. The maximum length is eight digits, and the allowed values are 0 through 9, #, and *.

International Number Prefix-This parameter defines the number that is prefixed to an incoming international number and provides a means to help identify international numbers, if necessary. This parameter allows you to prefix specified digits to the calling number of an inbound call based on the Type of Number field in an inbound offered call (ISDN SETUP message). For example, an international call from 456789 can be assigned the prefix 9 011. The maximum length is eight digits, and the allowed values are 0 through 9, #, and *.

Subscriber Number Prefix-This parameter defines the number that is prefixed to an incoming subscriber number, and provides a means to help identify subscriber numbers, if necessary. This parameter allows you to prefix specified digits to the calling number of an inbound call based on the Type of Number field in an inbound offered call (ISDN setup message). For example, a subscriber call from 1212 can be assigned the prefix 9. The maximum length is eight digits, and the allowed values are 0 through 9, #, and *.

Unknown Number Prefix-This parameter defines the number that is prefixed to an incoming unknown number and provides a means to help identify unknown number types, if necessary. This parameter allows you to prefix specified digits to the calling number of an inbound call based on the Type of Number field in an inbound offered call (ISDN SETUP message). For example, an unknown call from 5550123 can be assigned the prefix 7. The maximum length is eight digits, and the allowed values are 0 through 9, #, and *.

Note: These prefix values are added to numbers in missed or received incoming calls based on the inbound Q.931 call type value. These prefix values always need to match what the Telco requires in order to place the call. This method only applies to Q.931 gateways. As for all other Cisco CallManager versions, the National Number Prefix can be set to 91 and International Number Prefix can be set to 9011.

HTH

Allan.

PETER NEGUS Mon, 10/27/2008 - 03:09

Hi Allan

Thanks for your suggestion - it would fix the problem were it not for the gateway to the legacy network during migration. This is pumping calls through with number type = Subscriber which is the same as the PSTN.

eschulz Mon, 10/27/2008 - 10:25

You could try using the Extension Remapping feature in Unity. This allows some rudimentary manipulation of Calling and Called numbers on inbound calls to Unity. I think the feature is mostly considered obsolete due to better translation features in CUCM. That's probably why you'll only read about it in older Config Guides, such as this...

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/3x/integration/guide/30/ccm31/ITAPPXB.html

However, the same functionality still exists in all versions of Unity, 4.x, 5.x, 7.x.

-Eric

vmilanov Mon, 10/27/2008 - 14:13

Hi,

you did not mention which version CUCM you ar e using, but because I had faced similar problem, and IMHO, up to and including CUCM 6.1 there is no feasible and scalable solution to modify ANI (exept for the calls originating from the CUCM endpoints). I have found that the remote destination profile with assigned transformation pattern(s) and a CSS to it, has such a functionality, but even if it works for you, it has a limitation of max 2 calls simultnaiously to a remote destination.

But, since CUCM 7.0 there is a new feature called Dial Plan normalization, which allows you to modify ANI of incoming calls, and even in such a way that a local call presented to a remote or international ip phone has coresp. long-distance or international formatted ANI.

HTH,

Vasil

vmilanov Mon, 10/27/2008 - 14:18

Hi again,

I forget to tell you that there is actually a way to modify the ANI, but it is outside the CUCM - the voice translation rules in IOS. In case you decide to use this feature, you should move from single hop gw (MGCP for an example) to two hop gw, SIP or H323. That might bring some complications, but it works.

Regards,

Vasil

Actions

This Discussion