Dial Pattern Manipulation when using centralized SIP

[jameskuder]

We are currently on CUCM v10.5.2 and utilize an Enterprise SIP solution via our carrier

We have a site that resides in an area code of 509 and all of 509-xxx-xxxx numbers reside on our eSIP platform which is housed in our Datacenter of which the Trunk Group has a native area code of 206. The issue is with local calling from a 509 # to another local 509#.

If they try to dial the local 7digit number, it will automatically prefix the outgoing call with a 206. The only way they can call local number is to dial 1-509 even though it is local.

Tried figuring our how to address this as the same scenario is happening for other offices that have been migrated to eSIP.

They did not have this issue when their numbers were terminating at the local site via an ISDN PRI to a local voice route.

Looking for a solution if anyone else has dealt with this issue.

[Dennis Mink]

you would need to design your CSS and partitions in such a way, that only branches in the 509 area prefex 509 when dialing 7 digits local rather than automatically prefixing 206 to ALL 7 digits local calls. Translation patterns in various partitions are probably the easiest way to achieve this.

[jameskuder]

You wouldn't by any chance have an example of how to configure the specific translations and what to apply them to? Each site has a Region, MGRL, Location, and Device Pool setup for it. They all use the same LRG. They also each have their own CSS

[Dennis Mink]

you would need to test it on a test branch.

create partition_test  with Route Pattern XXXXXXX and route it through you SLRG, ad a translation pattern that prefixes 509 to XXXXXXX.  also in your test partition. add the partition to a test CSS and put a single test phone in it. remove the automated 206 prefix on your trunk (for testing purposes only)  and make a local call 1234567. before you do that, you can check your Dialed number analyzer and sanity check this theory.

lemme know what you find

[jameskuder]

What section of the TP am I putting this

add a translation pattern that prefixes 509 to XXXXXXX.

[Dennis Mink]

yeah so in the TP, the pattern itself is XXXXXXX and put it in your test partition and then  under "called party transformations" put in 509 in "Prefix digits (outgoing calls)" 

you might actually want to add a 509XXXXXXX pattern using SLRG to that same test partition as well (sorry)