I wish all carriers mark their ISDN parameters properly so
that it’s easier for us to globalize (read converting to e.164 form) the
Incoming ANI (read my previous blog on Calling & Called Party
Transformations in CUCM). Indeed Cisco
developers themselves missed this discrepancy on the carrier front when they
didn’t include a CSS parameter in the Voice Gateways Incoming Calling Party
Settings tab. But they did add this feature from CUCM Version 8 onwards.
Now let me walk you through the handiness of this simple
parameter to the process of globalizing the incoming ANI.
Here are 2 snippets of "deb isdn q931" from my T1 PRI:
National
Call Type Example:
Calling
Party Number i = 0x0080, '212XXXXXXX'
Plan:Unknown, Type:Unknown
Called Party
Number i = 0xA1, 'XXXXXXXXXX'
Plan:ISDN, Type:National
International
Call Type Example:
Calling
Party Number i = 0x0080, '44120XXXXXXX’
Plan:Unknown, Type:Unknown
Called Party
Number i = 0xA1, ' XXXXXXXXXX '
Plan:ISDN, Type:National
Now I am
unable to employ the Subscriber, National or International Number Type ISDN
Parameter to globalize this ANI. Also I cannot use the same digit manipulation
like adding +1 to all these as you can see that the carrier is sending both an
International & a National ANI with the unknown number type only.
So I will simply give a CSS to this number type. Here is a
screenshot for the same:
Now I will add multiple Calling Party transformations
assigned to the Partition which will be part of the above assigned CSS.
I hope this will help all of you who have been irritated
with the “Unknown” number type set by the carriers. For Asian carriers this is
the norm and hence you will have to get more creative in isolating different
ANIs to convert them to E.164 form.
HTH & Good day.
