<HTML>
<HEAD>
<TITLE>Re: [cisco-voip] International Calling Weirdness</TITLE>
</HEAD>
<BODY>
<FONT SIZE="4"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:14.0px'><B>Just a last note while I try some of these other suggestions.<BR>
<BR>
When I change the Route Pattern to 9.01145XXXXXXXX and the destination pattern in the dial peer to 901145T or 901145........ and prefix back on the 01145, the call goes through just fine. If I set the Route Pattern 9.0145@ it doesn’t work. Or if I set the Route Pattern to 9.011XXXXXXXXXX and the destination pattern to 9011T or 9011.......... it doesn’t work. Seems to want something finite behind that 011. Thanks for everyone’s help on this.<BR>
</B></SPAN></FONT></FONT><FONT FACE="Verdana, Helvetica, Arial"><B><FONT SIZE="2"><SPAN STYLE='font-size:10.0px'>-- <BR>
Jim Reed<BR>
Swift Communications, Inc.<BR>
970-243-2200 Ext. 12301<BR>
775-772-7666 (Cell)<BR>
</SPAN></FONT></B><SPAN STYLE='font-size:12.0px'><BR>
<BR>
<BR>
On 3/12/10 11:50 AM, "Matthew Ballard" <mballard@otis.edu> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT SIZE="4"><FONT FACE="Calibri"><SPAN STYLE='font-size:14.0px'>Try changing the destination pattern to 9011T. I believe as is it will strip the 901, leaving 14579282828, which isn’t a valid number to send to the telco. If you make the pattern 9011T, it will only send 4579282828 (so only starting with the country code). Depending on your telco you may also have to force the type to international, which could be done using a translation-rule/profile, on the interface, or possibly a couple of other ways. Reference the thread I started earlier this week about H.323 Gateway (Cisco) and Plan Type.<BR>
<BR>
Matthew Ballard<BR>
Network Manager<BR>
Otis College of Art and Design<BR>
<BR>
<BR>
On 3/12/10 9:50 AM, "Jim Reed" <<FONT COLOR="#0000FF"><U>jreed@swiftnews.com</U></FONT>> wrote:<BR>
<BR>
</SPAN></FONT></FONT><BLOCKQUOTE><FONT SIZE="4"><SPAN STYLE='font-size:14.0px'><FONT FACE="Verdana, Helvetica, Arial"><B>First off, thanks to Ryan, Jason and Scott for their replies.<BR>
<BR>
An interesting note is that if I set up a Route Pattern with the exact number in it and a matching dial peer on the router at Locations B and C, the call goes through with no problem. Here is what the default dial peer looks like and the modified one I put in the routers as a test.<BR>
<BR>
dial-peer voice 400 pots<BR>
description Outbound International Calls to PRI<BR>
destination-pattern 901T<BR>
port 0/1/0:23<BR>
prefix 01<BR>
<BR>
<BR>
dial-peer voice 401 pots<BR>
description Denmark Test<BR>
destination-pattern 90114579282828<BR>
port 0/1/0:23<BR>
prefix 0114579282828<BR>
<BR>
The Route Patterns in Call Manager have the entire number in the Route Pattern field and Discard Digits is set to none. I would think if the problem was with the telco, it wouldn’t work under any scenario yet it works just fine when I set it up this way. I have tried several variations on the Route Pattern and Dial Peer using only portions of the number but none of them seem to work except for an exact match. I’m still doing some additional testing. Just wanted to pass this along in case it rang any bells for anyone.<BR>
<BR>
Thank You...<BR>
</B></FONT></SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>