It appears that I can only get a destination pattern match on 9T? When I disbale this dial-peer, none of the other destination patterns match per... debug voice dialpeer default. I also assume this is why my cor list are not working properly, all call are routed out the 9T dial-peer with no COR bound to it... Any insight would be greatly appreciated. My destination patterns are as follows... I also have my preference set to one for fxo 0/1/0 two for 0/1/1 three for 0/1/4 etc... Output with dial-peer shutdown... Match Rule=DP_MATCH_DEST; Called Number=9195 Otherwise... 9T pots win out... |
|||
 |
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
User loginNavigationPopular contentToday's:All time:
PollRecent comments
Who's onlineThere are currently 4 users and 20 guests online.
Online usersWho's new |
|
About CMTBSyndicate Popular TagsActive forum topicsVoice News
Cisco TAC Issues - CME - UEArchive
|
Destination pattern problems on UC520
Looks to me that you might have a problem with a translation rule.
When I look at this line of your debug output
Match Rule=DP_MATCH_DEST; Called Number=9195
The Called number is showing 4 digits. It looks like you are translating the full dialed number down to 4 digits.
You can use the following command to test your translation rules.
test voice translation-rule RULENUMBER ENterATestNumbertoDial
Another command I use to test is an Undocumented command
CSIM START PhonenumberToDial
this command actually sends a test call from the box rather than the phone. Bypassing COR if you had it applied.
four digits
When I get to that fourth digit it cuts off the call, that's my 9 for an outside line, 1 for LD, and 95... = 954 for Fort Lauderdale Florida... It won't let me enter anymore digits and drops the line. I'll check what you posted though, as always thanks!
NOTE... I did notice that in CUE, only 9.T and .T are setup for patterns in Configure / System Parameters / Transfer Patterns... could this be a IOS VS CUE functionality issue?
HUM... Probably not...
To configure your Cisco Unified CME system to permit transfers to nonlocal destinations (VoIP or PSTN), set the transfer-pattern command under telephony-service. The transfer-pattern command also allows you to specify that specific transfer-to destinations should receive only blind transfers. You also have to use this configuration for SIP VoIP transfers. The transfer-pattern command allows you to restrict trunk-to-trunk transfers to prevent incoming PSTN calls from being transferred back out to the PSTN (employee toll fraud). Trunk-to-trunk transfers are disabled by default, because the default is to allow only local extension-to-extension transfers.
???
Num-Exp
Do you have any num-exp statements that might be matching it?
Also I noticed that preference statements don't seem to matter all the time in the UC500. I have an install that I noticed it matches based on which dial-peer statments are configured first. If you do a show dial-peer voice summary, it will show you that ordered listed. What is the first dial-peer with 9 as the destination pattern? Is is the one you are matching outbound?
more info
No Num-EXP statements...
Order of dial-peer destination patterns seems correct as well. It's hopping on 57 first, and only other 9T desc patterns.
50 pots up up 9911 1 up 0/1/0
51 pots up up 911 1 up 0/1/0
52 pots up up 9[2-9]......... 1 up 0/1/0
53 pots up up 1 91............. 1 up 0/1/0
54 pots up up 011 9011T 1 up 0/1/0
55 pots up up 1900 91900....... 1 up 0/1/0
56 pots up up 1976 91976....... 1 up 0/1/0
57 pots up up 9T 1 up 0/1/0
Do you have COR on the other dial-peers?
Just a quick trubleshooting tip.
For the Router Consule do a Csim Start
CSIM START is an undocumented Cisco command (it will never show up when you use the question mark for help) This command will actually send a test call from the router itself bypassing COR.
hope it helps,
Ted