Accepted Solutions
This is what you have today that would affect called or calling number in or outbound to ATT.
Used in the outbound direction in dial-peer 201-204
voice translation-rule 301
rule 1 /^222/ //
voice translation-profile OUT_TO_ATT
translate called 301
Used in the inbound direction in dial-peer 200
voice translation-rule 2
rule 1 /^214.......$/ /8\0/
rule 2 /^469.......$/ /8\0/
rule 3 /^972.......$/ /8\0/
rule 4 /^682.......$/ /8\0/
rule 5 /^..........$/ /81\0/
rule 6 /.*/ /8011\0/
voice translation-profile IN_FROM_ATT
translate calling 2
translate called 200
Voice translation-rule 2 adds an 8 in-front of rule 1 to 4 and 81 in-front of what it match in rule 5 and then 8011 in-front of what it match in rule 6. This is what make the 8 appear to the calling number for calls inbound to you.
What you need to do is remove the 8 for calling number when you send it out to ATT. That can be done by adding below or a variation of it depending on your needs.
voice translation-rule 302
rule 1 /^8\(.*\)/ /\1/
voice translation-profile OUT_TO_ATT
translate calling 302
To be frank this translation is very wide, it will remove an 8 from the start of any calling number that leaves the gateway to ATT. So you might want to make it more specific that what I have in the example.
Sounds like you are rewriting calling number inbound to have an 8 in-front of it to be able to call back to it from your directories list on you phone. Then when you forward the call out to your mobile your keeping that calling number as is when sent out to PSTN. You would need to again rewrite the calling number on the way out to PSTN to remove the 8 that you added in the inbound direction.
@EdLaw wrote:Thanks for the assistance. I looks like I am too much of a beginner to find this on the gateway. I see on the route pattern configuration under Called Party Transformations that discard digits is set to PreDot. I assumed this would accomplish removing the (8) in front of the number. Am I incorrect?
That would affect the called number, not the calling. On the gateway in IOS you would look for voice translation rules. Have alook at this excellent document that explains how this works. https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/61083-voice-transla-rules.html
This is what you have today that would affect called or calling number in or outbound to ATT.
Used in the outbound direction in dial-peer 201-204
voice translation-rule 301
rule 1 /^222/ //
voice translation-profile OUT_TO_ATT
translate called 301
Used in the inbound direction in dial-peer 200
voice translation-rule 2
rule 1 /^214.......$/ /8\0/
rule 2 /^469.......$/ /8\0/
rule 3 /^972.......$/ /8\0/
rule 4 /^682.......$/ /8\0/
rule 5 /^..........$/ /81\0/
rule 6 /.*/ /8011\0/
voice translation-profile IN_FROM_ATT
translate calling 2
translate called 200
Voice translation-rule 2 adds an 8 in-front of rule 1 to 4 and 81 in-front of what it match in rule 5 and then 8011 in-front of what it match in rule 6. This is what make the 8 appear to the calling number for calls inbound to you.
What you need to do is remove the 8 for calling number when you send it out to ATT. That can be done by adding below or a variation of it depending on your needs.
voice translation-rule 302
rule 1 /^8\(.*\)/ /\1/
voice translation-profile OUT_TO_ATT
translate calling 302
To be frank this translation is very wide, it will remove an 8 from the start of any calling number that leaves the gateway to ATT. So you might want to make it more specific that what I have in the example.
@EdLaw wrote:Thanks @Roger Kallberg ! This is a huge help. If I added translate calling 302 in your example, how would that affect translate calling 2?
It would not affect that rule set at all as it’s used on another dial-peer in the inbound direction.
There are many places where this could be set. See below for a few, but for sure not a complete list.
- Gateway in CUCM
- Trunk, if you use SIP for communication to your voice gateways
- Calling party transformation, can be set on various places
- In IOS on voice gateways with voice translation rules
- Translation pattern
- Route Pattern
- Route List details for Route Group
Personally I tend to prefer doing it in IOS as that's the most flexible way of doing it and it's on the ingress/egress border.
