I wanted a translation rule that would strip the "9" for SIP trunk and add "1+area code" to local number because the SIP trunk required it. I also wanted to add a "1" if the user put in the area code but forgot the 1. I made this rule: voice translation-rule 410 UC520#test voice translation-rule 410 96191112222 You would think this would work? If I go to the phone and enter 91112222 it correctly dials 16191112222 as rule 1 stipulates.... If I go to the phone and try to enter 96191112222 it does not dial 16191112222 as the test indicates it should, but rather the phone stops accepting digit inputs after 96191112 and it attempts to dial 16196191112! I've been completed dumbfounded by this for hours. whay the extra 619 and what happeed to the last three digits? |
|||
 |
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
User loginNavigationPopular contentToday's:All time:
Recent comments
Who's onlineThere are currently 0 users and 19 guests online.
Who's new |
|
About JSCSJSCSSyndicate Popular TagsActive forum topics
Voice News
Cisco TAC Issues - CME - UE
Archive
|
Good advise, I'll look into
Good advise, I'll look into COR. Stupid question, but what is a dial-peer?
Brian
www.jaydien.com
translation rule...
I would say something is messed on the way the UC is doing the translation rule because...
I was thinking... Your rule 1 match is actually a match on 2, and vice versa...
Ex.
voice translation-rule 410
rule 1 /^9\(..........\)$/ /1\1/
rule 2 /^9\(.......\)$/ /1619\1/
You say test voice translation-rule 410 91112222
Matched with rule 1
This is a seven digit number so it should in fact match rule 2...
and conversly the ten digit should match rule 1...
I don't know if that is a typo, and probably isn't the root cause of your problem but I would investigate. I created a mock rule like you have defined and tested it out, ex below.
UC520#test voice translation-rule 666 92223333
Matched with rule 2
Original number: 92223333 Translated number: 16192223333
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
UC520#test voice translation-rule 666 96192223333
Matched with rule 1
Original number: 96192223333 Translated number: 16192223333
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
Oh yeah, one more thought
You say...
If I go to the phone and try to enter 96191112222 it does not dial 16191112222 as the test indicates it should, but rather the phone stops accepting digit inputs after 96191112 and it attempts to dial 16196191112!
This would lead me to belive there is a destination pattern match listed on a dial peer for default 9[2-9].........
The default associated with this is a 10 digit forwarder, I.E. forward-digits 10
It's almost like you have 7 digits setup for calls in CCA, hence something like 9[2-9]...... and perhaps forward-digits 7. This would in the end match rule 2, and not 1 as stated in your output, and would in fact dial 96196191112...
Not a stupid question - A good question
A dial peer is an addressable endpoint.
From the command line it is how we tell Call Manager Express how to route calls out of and into the system.
For Example lets say you have a SIP trunk and a FXO port or 4 on your UC520. If a user dials an Emergency number like 911 here in the States I typically want that call to go out the FXO port to my local carrier. The dial peer tells the system what to with the call and what trunk to use.
Here is an example
dial-peer voice 58 pots
description ** FXO pots dial-peer **
preference 1
destination-pattern 911
port 0/1/1
forward-digits 3
no sip-register
here is a good link to help understand dial-peers
JSCSJSCS
If the phone only accepts a certain amount of digits then dials,you may be running into a dial-peer configuration issue.
Please post your config so that we can take a look at it.
It Could be COR - Class of Restriction
You might be blocking a dial peer from the extension with COR (Class of Restriction).
To troubleshoot COR issues use the CSIM START command.
csim start is an undocumented Cisco IOS command - It does not show up when you use the question mark. This command is used to place a test call from the router itself, this way the call bypasses all Class of Restriction on ephone-dns.
Type csim start followed by the phone number you are testing.
If the call goes through you have a problem with your COR setup.
Hope that helps,
Ted
Yeah I've seen this same
Yeah I've seen this same issue myself with my system. It is as if the phone itself is expecting a certain amount of digits. I haven't had much luck with that either so I'm curios if anyone else has some input on this.
Another annoying oddity of this system is that after you make these changes in CLI, if for any reason you happen to go and use the config assistant for something else, like modifying extensions, it will erase any modifications that you did using CLI. Really annoying.
Brian
www.jaydien.com
1.5
CCA 1.5 beware mwwwaaaahahahahahaha....