10-20-2010 05:14 AM - edited 03-16-2019 01:26 AM
10-20-2010 05:46 AM
Yes this is possible; however, most people who do this loc/glob configuration are using an E.164 dial plan instead. In your case, you can likely set the incoming call transformation masks at the service parameter level since it should apply equally at all ingress gateways. After that you add a partition, CSS, and Calling Party Transformation Patterns that strip the 9. Apply that CSS to the device pool or manually to the device.
10-20-2010 06:14 AM
yeah I know Globalization usually refers to the use of E.164. we are not prepared to moved to that quite yet. You refered to a service parameter that needs to be set? Have this working on a softphone but does not work on the ip phones. Is this parameter related to this?
thanks,
mike
10-20-2010 06:23 AM
The Incoming Calling Party
10-20-2010 07:09 AM
Ah,
These patterns rely's on the Carrier sending the correct ISDN. For remote sites calls are coming over Analog FXO so there is no isdn information. To address this I was thinking on doing this with Transformation Patterns/CSS apllied at the gw and then using different transformations applied at the phone.
GW transform:
for local area codes (954XXXXXXX) transform to prefix 9
for [2-9]xx[2-9]xxxxxx prefix 91 (all other national numbers)
Phone transform:
for local area codes (9.954XXXXXXX) transform to strip 9
for 9.1[2-9]xx[2-9]xxxxxx strip 9 (all other national numbers)
I am just curious to why this would present correct on softphone and not an IP Phone.
Thanks for the input.
mike
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide