06-10-2008 07:00 AM - edited 03-15-2019 11:11 AM
Hey guys I have a CME system at my small business and I am now in need of translation rules because my internal 3 digit numbering plan conflicts with some area codes in the US.
I want users to have a dial a 9 then the 10 digit phone number for local calls.
I also want users to have dial a 9 then 1 then the 10 digit number for long distance.
However my provider will only accept the 10 digit phone number for both local and long distance calls.
Any help is appreiciated.
06-10-2008 07:08 AM
No need for translation rules in this case:
dial-peer voice 9 pots
description local calls
destination-pattern 9[2-9]......
prefix 408 <- your area code here
port x/y
dial-peer voice 91 pots
description long distance
destination-pattern 91[2-9][0-8].[2-9]......
forward-digits 10
port x/y
Hope this helps, please rate post if it does!
06-10-2008 07:16 AM
Hi I am using VOIP dial-peers. I cannot use the prefix command and it does not strip off the first number in the destination-pattern command. Already tried that. I need translation rules.
06-10-2008 07:33 AM
You should have mentioned the SIP trunk :)
voice translation-profile 9-to-area
translate called 100
voice translation-profile strip-9
translate called 101
voice translation-rule 100
rule 1 /^9/ /408/
voice translation-rule 101
rule 1 /^91/ //
dial-peer voice 9 voip
description local calls
destination-pattern 9[2-9]......
translation-profile outgoing 9-to-area
dial-peer voice 91 voip
description long distance
destination-pattern 91[2-9][0-8].[2-9]......
translation-profile outgoing strip-91
Hope this helps, please rate post if it does!
06-10-2008 08:06 AM
We have to dial 10 digits here in Houston.
I think translation rule 100 needs to look like this:
rule 1 /^9/ //
Correct?
What should the destination pattern read? I tried this config real quick and it didnt work so i had to revert back.
I used 9[2-9]......... for the destination-pattern on the dial peer.
What did I miss? Any way to test the translation rules before applying them?
06-10-2008 08:35 AM
Hi, seems to me the rules are right, of course replace my example 408 with your area code.
You can "test voice translation-rule XXX YYY".
Thanks for the appreciation and good luck!
06-10-2008 08:56 AM
I did my rule like this
rule 1 /^9/ //
Remember I need to dial a 10 digit number.
06-10-2008 09:07 AM
NANP:
Area code (3), exchange code (3), number (4) = 10
BUT, you also need to remove the 1 used for long distance in the US.
So the rule should be really
rule 1 /^91/ //
That removes the leading 91. If you are supposed to leave 1 in place, you'll be calling 11 digits, not 10.
06-10-2008 10:13 AM
For local and long distance numbers I DO NOT have to dial a 1. I need to give my phone company 10 digits period. I want my internal users to dial a 9 then the 10 digit number for local calls. For long distance I want my internal users to dial a 91 then the 10 digit number.
Remember my phone company will only accept a 10 digit number no matter if it is long distance or local. They dont care one way or the other.
06-10-2008 10:29 AM
Well, that is exactly what the rules I suggested above do.
For local calls, leading 9 is replaced with you area code. For long distance, leading 91 is removed. In both cases, 10 digits are sent.
I suppose that for international, 011 has to be prepended and destination-pattern would look like: 011[1-9].....T
Another translation-profile and rule would ensure that 9 is prefixed to calling number for incoming calls, this to facilitate callback.
You can check which number is ultimately sent to ITSP with "debug ccsip message" and "term mon".
06-10-2008 10:50 AM
OH I think where I was getting confused was Houston has 3 area codes, 281, 713, and 832.
I will make a rule 1 /^9/ // with a destination-pattern of 9[2-9].........
06-10-2008 11:04 AM
But that will make users dial 9 followed by 10 digits, that I think is not customary in the U.S.
I guess you've to decide which one of the three area codes is your "local" one.
06-10-2008 11:18 AM
YES, that is exactly what I want. I need my users to dial 9 then the 10 digits. In major US cities this is normal.
06-10-2008 12:40 PM
OK here is another question for you. My home CME system I want the users to dial 9 then the 10 digit number however my SIP provider wants a 1 in front of the 10 digit number. What does the rule need to look like to accomplish this?
06-10-2008 12:49 PM
Have to admit I misunderstood the 9 + 10 digits thing since the very beginning.
I also do not understand what is the point to have to remember that for three area codes only, no 1 needs to be dialed. In my way of thinking, either 1 or no 1, all calls should go through.
Anyway, what do you want is done with:
voice translation-profile strip-91
translate called 100
voice translation-profile strip-9
translate called 101
voice translation-rule 100
rule 1 /^91/ //
voice translation-rule 101
rule 1 /^9/ //
dial-peer voice 9281 voip
destination-pattern 9281[2-9]......
translation-profile outgoing strip9
dial-peer voice 9713 voip
destination-pattern 9713[2-9]......
translation-profile outgoing strip9
dial-peer voice 9932 voip
destination-pattern 9832[2-9]......
translation-profile outgoing strip9
dial-peer voice 91 voip
description long distance
destination-pattern 91[2-9][0-8].[2-9]......
translation-profile outgoing strip-91
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