Consider the following configuration:
voice translation-rule 78
rule 1 /.*/ /19047580977/
voice translation-profile 2214
translate calling 78
dial-peer voice 42 pots
translation-profile outgoing 2214
Rule 1 any 13023970096
dial-peer voice 84 pots
translate-outgoing calling 160
Some questions I'd like to clarify:
1. Do both configuration achieve the same effect -- which is to add "1" to the destination-pattern number?
2. What's the difference between "voice translation-rule" vs. "translation-rule"?
3. What's the maximum number of "translation-rule" lines I can create in one Cisco box?
Using forward-digits plus the translation patterns is a bit redundant. If you just want to add a 1, why not get rid of the translation pattern, remove forward-digits 0, and add prefix 1?
If you would like all the numbers to be sent, just put parenthesis around your destination pattern so it's not literal - (5551234), or add forward-digits all
2. translation-rule is the old style of translation, and is a legacy method that is no longer suggested to use.
3. you can create up to 1000 profiles, and each profile can contain 16 rules.
Hope that clarifies a bit.
Thanks Nick. The main reason behind the config is this:
1. The inbound number (VoIP) doesn't send "1" but the POTS provider requires "1" to be prefixed always.
2. The receiving end (POTS) is a different number. The overall effect is to translate the inbound (VoIP) to another number, hence "forward-digits 0" and sending just the "prefix" (the number assigned by the POTS provider).
VoIP inbound -> translate to POTS number
I'm thinking of doing this:
voice translation-rule 2200
rule 1 /^\(*.+\)/ /1\1/
So I only use one voice profile translation rule and one profile to append "1" to all inbound VoIP numbers. What's a better way of "translating" an inbound VoIP number to a different number and out to the POTS? Thanks again!
It's probably easier to keep a standard destination-pattern, and then do your translation on the translation-pattern.
dial-p v 1
translation-profile in YY
translate called 1
rule 1 /5551234/ /15554321/
Thanks Nick. However, this would restrict the total number of translation to 128 (the limit of voice translation-rule) since it would require 1-translation profile and 1-voice translation rule for each number. Is there another way to break the 128-limit? Even with the 1,000 limit on the translation-profile, it's still limited by the 128 max of voice translation-rule.
I just realized that the configuration is replacing the CALLING number with "1" + destination pattern number since the provider will not accept if it's not in this format. Which means, I can't use any of the CALLING number digits. Is there another way of using the destination pattern number as the CALLING number without resorting to "voice translation-profile" and "voice translation-rule"?
You could use a TCL/IVR script.
But again, why can't you use translation rule ?
Sorry, I can' understand you explanation above.
Consider the following:
dial-peer voice 429 pots
translation-profile outgoing 6156
voice translation-profile 6156
translate calling 113
voice translation-rule 113
rule 1 /.*/ /13104640522/
Calling party --> DID provider --> Router --> POTS
Client calls a DID number -- this is the destination pattern or the called number. The PSTN provider will only accept the call if the number calling is in the form of 1 + destination pattern in this case "13104640522". The original ANI is discarded and replaced by "13104640522" which is now accepted by the PSTN provider. The call is allowed and the receiving (POTS leg) sees the new ANI as "13104640522."