<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR>
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-GB vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=390102012-29062006><FONT face=Arial
color=#0000ff size=2>You mentioned that these are DDI numbers for you? I'd
recommend putting "direct-inward-dial" on those peers.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=390102012-29062006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=390102012-29062006><FONT face=Arial
color=#0000ff size=2>I've seen this behavior before, where some peers have DID
on them, and some don't, and incoming calls seem to prefer non-did enabled
dial-peers. My general rule of thumb is that when I have DID on a line,
all POTS peers get direct-inward-dial on them just to prevent problems
(or to prevent someone from getting dial-tone
accidentally).</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Nick
Kassel<BR><B>Sent:</B> Thursday, June 29, 2006 7:07 AM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip] Dialpeer
mismatch<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We had an issue with a new
installation of a remote site today, they have a PRI E1 on a 1760 router with
a range of DDI numbers.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">When I added the following dial
peers to allow 4 digit dialling when the WAN is down across SRST we came
across a problem. When in SRST the 4 digit dialling worked
fine.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">dial-peer voice 2000
pots</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">destination-pattern
2…</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">prefix 02079532</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">port 0/0:15</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">dial-peer voice 6000
pots</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">destination-pattern
6…</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">prefix 02071496</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">port 0/0:15</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue we had was that now any
inbound calls originating from 207 XXX XXXX fail, the calls came in to the
router and there were no errors on the debug then you received a dialtone
after hanging up the debug would show the call clearing down as you would
expect. Any other calls from other area codes were fine.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Obviously the 2 prefix being
presented was mismatching with the destination-pattern 2… in the dial-peer
voice 2000 pots dial peer. </SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there anyway I can get round as
we would very much like to have these dial-peers in.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P></DIV><BR><BR>
<TABLE style="COLOR: black" bgColor=white>
<TBODY>
<TR>
<TD><BR>***********************************************************************************************<BR><BR>The information contained in this e-mail is strictly confidential, some or all<BR>of which may be legally privileged. It is for the intended recipient only.<BR>Access to this e-mail by any other person is prohibited. If you are not the<BR>intended recipient, any use, disclosure, copying, printing, distribution of,<BR>replying to or any action taken or omitted to be taken in reliance on this<BR>e-mail, is prohibited and may be unlawful. Please contact the sender immediately<BR>should this e-mail have been incorrectly addressed or transmitted.<BR><BR>You accept that any instructions are deemed to have been given at the time the<BR>recipient(s) accesses them and that delivery receipt does not constitute<BR>acknowledgement or receipt by the intended recipient(s). You accept that there<BR>may be a delay in processing the instructions received from e-mails after<BR>Charles Stanley has received them. You are advised that urgent, time sensitive<BR>and confidential communications should not be sent by e-mail. <BR><BR>You acknowledge that e-mails are not secure and you accept the risk of<BR>malfunction, viruses, unauthorised interference, mis-delivery or delay.<BR>************************************************************************************************<BR><BR><BR>Charles Stanley & Co. Ltd<BR>Registered Office: 25 Luke Street London EC2A 4AR<BR><BR>Tel: 0207 739 8200 Fax: 0207 739 7798<BR>Registered in England No. 1903304<BR><BR>Charles Stanley Sutherlands and Charles Stanley Securities are divisions of Charles Stanley & Co. Ltd<BR><BR>Authorised and Regulated by the Financial Services Authority, Member of the<BR>London Stock Exchange, International Securities Markets Association, and The London International Financial Futures &<BR>Options Exchange.<BR><BR>This footnote also confirms that this email message has been swept by McAfee<BR>VirusScan and SurfControl Email Filter software.<BR></TD></TR></TBODY></TABLE></BLOCKQUOTE></BODY></HTML>