<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Oops Sorry,</DIV>
<DIV> </DIV>
<DIV>International dialing from US would be 9011T</DIV>
<DIV> </DIV>
<DIV>dial-peer voice xxx pots<BR>destination-pattern 9011T<BR>prefix 011<BR>port 0/0/0:23<BR><BR><BR>--- On <B>Mon, 3/15/10, kapil atrish <I><nice_chatin@yahoo.com></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: kapil atrish <nice_chatin@yahoo.com><BR>Subject: Re: [cisco-voip] Quest for the best H.323 dial-peer configuration<BR>To: "BillCarter" <bcarter@sentinel.com>, "Nick Matthews" <matthnick@gmail.com><BR>Cc: "Cisco-Voip-Puck" <cisco-voip@puck.nether.net><BR>Date: Monday, March 15, 2010, 11:33 AM<BR><BR>
<DIV id=yiv997757608>
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR>
<TD vAlign=top>
<DIV>There is no need for direct-inward-dial on all the dial-peers but dp 1 pots.</DIV>
<DIV> </DIV>
<DIV>You need to put forward-digit 7 on dp 100 for local calls to succeed. Likewise on dp 101.</DIV>
<DIV> </DIV>
<DIV>Perhaps you need international dialing:</DIV>
<DIV> </DIV>
<DIV>dial-peer voice xxx pots<BR>destination-pattern 900T<BR>prefix 00<BR>port 0/0/0:23<BR></DIV>
<DIV><BR><BR>--- On <B>Mon, 3/15/10, Nick Matthews <I><matthnick@gmail.com></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Nick Matthews <matthnick@gmail.com><BR>Subject: Re: [cisco-voip] Quest for the best H.323 dial-peer configuration<BR>To: "Carter, Bill" <bcarter@sentinel.com><BR>Cc: "Cisco-Voip-Puck" <cisco-voip@puck.nether.net><BR>Date: Monday, March 15, 2010, 10:35 AM<BR><BR>
<DIV class=plainMail>[1-79] is going to cause problems with your other dial peers. If you<BR>do digit by digit dialing (fxs ports, srst/cme phones) then you're<BR>going to hit dial peer 10 for 4 digit numbers that start with 9.<BR><BR>Additionally, since 10 is the only dial peer that will match [0-8]...<BR>there is no reason to have a preference command.<BR><BR>Other than that, it looks alright. Having incoming called-number . on<BR>all the pots dial peers other than 1 is redundant. All incoming TDM<BR>calls are going to match the first dial peer in the router with<BR>incoming called-number . (even FXS which can get you in trouble).<BR>It's not going to cause problems but is a misunderstood aspect of dial<BR>peer matching.<BR><BR>As an aside, I prefer to put () around explicit matches that I want to<BR>forward. For example, destination-pattern 9911 with a prefix of 911<BR>could be simplified to a destination-pattern of
9(911). The<BR>parenthesis are a regular express non-literal match so they aren't<BR>discarded. To each his own however.<BR><BR>-nick<BR><BR>On Fri, Mar 12, 2010 at 2:27 PM, Carter, Bill <<A href="http://us.mc550.mail.yahoo.com/mc/compose?to=bcarter@sentinel.com" target=_blank rel=nofollow>bcarter@sentinel.com</A>> wrote:<BR>> I get confused with "incoming called-number" Should it be "incoming<BR>> called-number ." or ""incoming called-number .T"<BR>><BR>> Not getting any action here so how about this:<BR>><BR>> dial-peer voice 1 pots<BR>> incoming called-number .<BR>> direct-inward-dial<BR>> port 0/0/0:23<BR>> !<BR>> dial-peer voice 10 voip<BR>> preference 1<BR>> destination-pattern [1-79]...<BR>> session target ipv4:X.X.X.X<BR>> incoming called-number .<BR>> voice-class codec 1<BR>> voice-class h323 1<BR>> dtmf-relay
h245-alphanumeric<BR>> fax-relay ecm disable<BR>> fax-relay sg3-to-g3<BR>> fax rate disable<BR>> no vad<BR>> !<BR>> dial-peer voice 100 pots<BR>> destination-pattern 9[2-9]......<BR>> direct-inward-dial<BR>> port 0/0/0:23<BR>> !<BR>> dial-peer voice 101 pots<BR>> destination-pattern 91[2-9]..[2-9]......<BR>> direct-inward-dial<BR>> port 0/0/0:23<BR>> prefix 1<BR>> !<BR>> dial-peer voice 102 pots<BR>> destination-pattern 9911<BR>> direct-inward-dial<BR>> port 0/0/0:23<BR>> prefix 911<BR>> !<BR>><BR>> -----Original Message-----<BR>> From: <A href="http://us.mc550.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net" target=_blank rel=nofollow>cisco-voip-bounces@puck.nether.net</A><BR>> [mailto:<A
href="http://us.mc550.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net" target=_blank rel=nofollow>cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Carter, Bill<BR>> Sent: Thursday, March 11, 2010 7:37 PM<BR>> To: Cisco-Voip-Puck<BR>> Subject: [cisco-voip] Quest for the best H.323 dial-peer configuration<BR>><BR>> I want to put together the worlds best H.323 dial-peer configuration<BR>> template. Here are the guidelines.<BR>><BR>> - US dial plan<BR>> - telco sends 4-digits<BR>> - all ip phone DNs begin with [0-8]...<BR>> - all ip phones dial 9 then the pstn number<BR>> - don't use 9T<BR>> - pstn connection is a Pri on voice-port 0/0/0:23<BR>> - fxs port 0/1/0 with did ending in 1000<BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> <A href="http://us.mc550.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" target=_blank
rel=nofollow>cisco-voip@puck.nether.net</A><BR>> <A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank rel=nofollow>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> <A href="http://us.mc550.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" target=_blank rel=nofollow>cisco-voip@puck.nether.net</A><BR>> <A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank rel=nofollow>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="http://us.mc550.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" target=_blank rel=nofollow>cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank
rel=nofollow>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></DIV></BLOCKQUOTE></TD></TR></TBODY></TABLE><BR></DIV></BLOCKQUOTE></td></tr></table><br>