12-03-2009 07:48 AM - edited 03-15-2019 08:39 PM
We have two locations long distance apart with our phones. In the past I have set up a route pattern so that say a user in location A dials 8 then the number they will actually call out from the gateway of location B. This way Location A does not need to make long distance calls to Location B instead can go through our network and call out of the gateway of Location B and therefore be a local call.
However, I am now attempting to make this easier so instead of the user dialing 8, it will automatically know to go through. For example, right now if a user dials 8.429xxxx they can call from location A to location B locally. However, I now want them to be able to dial long distance but like they normally would anywhere else such as 9.1902429xxxx and it will go to the gateway in location B and strip the area code and 9 off and then call locally through gateway B.
I thought if I changed the discard digits to predot 11/10d->7D it would change the 919024295445 to call from the gateway of 4295445. In the route list i have gateway B selected and this discard digit pattern sleected however when i do a dial analyzer it is not stripping the dialed number down. Does anyone know what I am doing wrong? Below is the results of the dialed digit analyzer:
# Results Summary
* Calling Party Information
o Calling Party = 1000
o Partition =
o Device CSS =
o Line CSS = MDC-LD-CSS
o AAR Group Name =
o AAR CSS =
* Dialed Digits = 919024295445
* Match Result = RouteThisPattern
* Matched Pattern Information
o Pattern = 9.1902429XXXX
o Partition = MDC-Local-P
o Time Schedule =
* Called Party Number = 919024295445
* Time Zone = Greenwich Standard Time
* End Device = MDCHLF_Local_RL_prefix
* Call Classification = OffNet
* InterDigit Timeout = NO
* Device Override = Disabled
* Outside Dial Tone = NO
# Call Flow
* Route Pattern :Pattern= 9.1902429XXXX
o Positional Match List = 9:19024295445
o DialPlan =
o Route Filter
+ Filter Name =
+ Filter Clause =
o Require Forced Authorization Code = No
o Authorization Level = 0
o Require Client Matter Code = No
o Call Classification =
o PreTransform Calling Party Number = 1000
o PreTransform Called Party Number = 919024295445
o Calling Party Transformations
+ External Phone Number Mask = YES
+ Calling Party Mask =
+ Prefix =
+ CallingLineId Presentation = Default
+ CallingName Presentation = Default
+ Calling Party Number = 1000
o ConnectedParty Transformations
+ ConnectedLineId Presentation = Default
+ ConnectedName Presentation = Default
o Called Party Transformations
+ Called Party Mask =
+ Discard Digits Instruction = None
+ Prefix =
+ Called Number = 919024295445
* Route List :Route List Name= MDCHLF_Local_RL_prefix
o RouteGroup :RouteGroup Name= MDCIPTGW-2-RG
+ PreTransform Calling Party Number = 1000
+ PreTransform Called Party Number = 919024295445
+ Calling Party Transformations
# External Phone Number Mask = Default
# Calling Party Mask =
# Prefix =
# Calling Party Number = 1000
+ Called Party Transformations
# Called Party Mask =
# Discard Digits Instructions = PreDot 11/10D->7D
# Prefix =
# Called Number = 19024295445
+ Device :Type= MGCPT1PRIPort
# End Device Name = S0/SU3/DS1-0@mdciptgw-2
# PortNumber = 0
# Device Status = Registered
# AAR Group Name =
# AAR Calling Search Space =
# AAR Prefix Digits =
# Call Classification =
# Calling Party Selection =
# CallingLinePresentation =
# ConnectedLinePresentation =
# Number Of Strip Digits =
# CallerID DN =
Solved! Go to Solution.
12-03-2009 09:45 AM
Kerri,
I have never been a fan of the pre-built discard instructions like 11/10D->7D .
What I would try was to change the RP 9.1902429xxxx to 91902.XXXxxxx and simply strip
pre-dot at the egress Route list on gateway B (as the first choice). In case the WAN
link or gateway B is down then set up gateway A as the 2nd choice, strip pre-dot
and prepend 1902.
HTH - I've done this a bunch of times and has always worked.
Art
12-03-2009 08:27 AM
Hello Kerri,
Just a gotchya that has stung me a thousand times, did you reset the GW?
HTH,
Art
12-03-2009 08:35 AM
Thanks for the reply. I know when I update the route pattern it says it will automatically reset the associated gateways. However, I did just try to go to the gateway and reset it but still no luck. Too bad that did not resolve the problem. Please I would aprreciate any suggestions.
12-03-2009 08:50 AM
It goes out the of the correct gateway but for some reason is not stripping the number down to 7 digits. When I set the route pattern and actually make the call the phone service is telling me that "the number I am dialing is not a long distance call and do not dial 1...."
12-03-2009 09:45 AM
Kerri,
I have never been a fan of the pre-built discard instructions like 11/10D->7D .
What I would try was to change the RP 9.1902429xxxx to 91902.XXXxxxx and simply strip
pre-dot at the egress Route list on gateway B (as the first choice). In case the WAN
link or gateway B is down then set up gateway A as the 2nd choice, strip pre-dot
and prepend 1902.
HTH - I've done this a bunch of times and has always worked.
Art
12-03-2009 10:06 AM
Great Thanks! I never really thought of taking that approach. It works now!
04-28-2015 11:50 PM
The PreAt, 11D/10D@7D, 11D@10D, IntlTollBypass, and 10-10-Dialing complex DDI's are not available without the @ symbol in the route pattern.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: