<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I am not concerned with what works, and more concerned with what
is the best solution. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jason Aarons (US)
[mailto:jason.aarons@us.didata.com] <br>
<b>Sent:</b> Monday, June 28, 2010 5:25 PM<br>
<b>To:</b> Jim Reed; Bill; Beck, Christopher; cisco-voip<br>
<b>Subject:</b> RE: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>While it’s working, from a solution design standpoint I’m being
told that if the timing varies from the providers it could result in problems,
so design preference should be to have separate routers in this scenario. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m with you, I’ve done it before and it did work, and I’d hate
to explain it to customer they need another router if the clocks are far apart.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jim Reed
[mailto:jreed@swiftnews.com] <br>
<b>Sent:</b> Monday, June 28, 2010 6:09 PM<br>
<b>To:</b> Bill; Beck, Christopher; Jason Aarons (US); cisco-voip<br>
<b>Subject:</b> Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.5pt;
font-family:"Verdana","sans-serif"'>I am currently using PRIs from different
vendors — AT&T and Integra — on the same router. Two (2) separate
VWICs on the same 2851. VWIC2-1MFT-T1/E1. No problems with voice
quality, errors, etc. Configured as follows:<br>
network-clock-participate wic 0 <br>
network-clock-participate wic 1 <br>
network-clock-select 1 T1 0/0/0<br>
Just thought I’d pass it along.<br>
</span></b><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif"'>--
<br>
Jim Reed<br>
Manager of Technical Services<br>
Swift Communications, Inc.<br>
970-384-9141 (Direct)<br>
775-772-7666 (Cell)<br>
Sorry, no faxes accepted.<br>
Please send documents by eMail.<br>
</span></b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
<br>
<br>
On 6/28/10 3:44 PM, "Bill" <<a
href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Are you sure that is the case currently? I think you can have
multiple PRI’s inside the same router on an ISR but they can not be on the same
VWIC. <br>
<br>
Jason said you can not have multiple PRI’s within the same router.<br>
</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Beck, Christopher [<a
href="mailto:CBeck@usg.com]">mailto:CBeck@usg.com]</a> <br>
<b>Sent:</b> Monday, June 28, 2010 4:40 PM<br>
<b>To:</b> Bill; 'Jason Aarons (US)'; 'cisco-voip'<br>
<b>Subject:</b> RE: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><br>
<span style='color:#1F497D'>This is true on the 2800/3800 today (except in the
case of the NM-NDV modules mentioned, but I don’t think so even in that case).
It is because there is a “single” PLL clocking circuit shared for all
PRI’s. The WIC must be configured to participate in that clocking circuit
prior to setting up the PRI. I can’t remember any device that
could handle this in 20 years of installing channel banks, muxes, routers, etc.<br>
<br>
That said, a lot of times it will work acceptably because the clocks are close
enough, especially if the local loop provider is the same on all links.
But, you have to test it to know in any case.<br>
</span></span><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
<br>
-Chris<br>
<br>
</span><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
</span><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a href="mailto:cisco-voip-bounces@puck.nether.net]">mailto:cisco-voip-bounces@puck.nether.net]</a>
<b>On Behalf Of </b>Bill<br>
<b>Sent:</b> Monday, June 28, 2010 4:21 PM<br>
<b>To:</b> 'Jason Aarons (US)'; 'cisco-voip'<br>
<b>Subject:</b> Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>What? I know you could not do different Telco’s on the same two
port card but you can’t do two telco’s in the same router? Is there an official
response to this? Is there a specific defect I can reference with my Cisco AM? <br>
</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [<a
href="mailto:cisco-voip-bounces@puck.nether.net]">mailto:cisco-voip-bounces@puck.nether.net]</a>
<b>On Behalf Of </b>Jason Aarons (US)<br>
<b>Sent:</b> Monday, June 28, 2010 4:12 PM<br>
<b>To:</b> cisco-voip (cisco-voip@puck.nether.net)<br>
<b>Subject:</b> [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><br>
A TAC engineer at Cisco Live confirmed you can’t have multiple voice PRIs from
separate telcos come into a G2 with different clocks. For example you have a
AT&T PRI, a Verizon PRI, a Century Link PRI, a Alltell PRI, a Paetec PRI
all in the same router. You can’t clock the backplane to more than one
source! You’ll get slips, etc audio will sound bad, faxes/modems will
fail. Fix is separate routers. He said he thought a 2800 with DSPs
on a NM-HDV module would work though. My exact question was can you carve
up the backplane PVDM3 clocking for separate PRIs somehow. </span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-family:"Verdana","sans-serif"'>
<hr size=1 width="100%" align=center>
</span></div>
<p style='margin-bottom:12.0pt'><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
</span><b>Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you are
hereby notified that you have received this communication in error and that any
use or reproduction of this email or its contents is strictly prohibited and
may be unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it from your
computer. Thank you. <br>
</b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
Confidentiality Notice: This email is intended for the sole use of the intended
recipient(s) and may contain confidential, proprietary or privileged
information. If you are not the intended recipient, you are notified that any
use, review, dissemination, copying or action taken based on this message or
its attachments, if any, is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy or delete all copies of
the original message and any attachments. Thank you.</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=1 width="100%" align=center>
</div>
<p><strong>Disclaimer: This e-mail communication and any attachments may
contain confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee, you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this communication
in error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you. </strong><o:p></o:p></p>
</div>
</body>
</html>