<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:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
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";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Great thanks for the information. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Justin Steinberg
[mailto:jsteinberg@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, June 29, 2010 10:34
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Bill<br>
<b><span style='font-weight:bold'>Cc:</span></b> Dennis Heim; Nick Matthews;
cisco-voip<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] ISR G2
PVDM3 DSPs on backplane</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>here is a whitepaper that
covers this issue:<br>
<br>
<a
href="http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html">http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html</a><br>
<br>
Nick's link covers the configuration.<br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Tue, Jun 29, 2010 at 9:56 AM, Bill <<a
href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>>
wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Thanks for everyone's input. I don't believe in doing things cheap on
the<br>
front end only to have problems down the road and look like the bad guy. I<br>
will just split the PRI's to different routers. Does anyone have any<br>
official documentation from Cisco that this is not supported or recommended?<br>
That will go along way in justifying the additional hardware.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
-----Original Message-----<br>
From: Dennis Heim [mailto:<a href="mailto:Dennis.Heim@cdw.com">Dennis.Heim@cdw.com</a>]<br>
Sent: Tuesday, June 29, 2010 8:54 AM<br>
To: Nick Matthews; Bill Riley<br>
Cc: cisco-voip<o:p></o:p></span></font></p>
</div>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Subject: RE: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
<br>
It is just bad design practice to get into to have PRIs from different<br>
provider on the same clocking domain. You might be able to get away with it,<br>
but really you are just putting the end-customer in a bad spot down the<br>
road.<br>
<br>
Dennis Heim<br>
Network Voice Engineer<br>
CDW Advanced Technology Services<br>
<st1:Street w:st="on"><st1:address w:st="on">11711 N. Meridian Street, Suite
225</st1:address></st1:Street><br>
<st1:place w:st="on"><st1:City w:st="on">Carmel</st1:City>, <st1:State w:st="on">IN</st1:State>
<st1:PostalCode w:st="on">46032</st1:PostalCode></st1:place><br>
<br>
317.569.4255 Office<br>
317.569.4201 Fax<br>
317.694.6070 Cell<br>
<a href="mailto:dennis.heim@cdw.com">dennis.heim@cdw.com</a><br>
<a href="http://cdw.com/content/solutions/unified-communications/"
target="_blank">cdw.com/content/solutions/unified-communications/</a><br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Nick Matthews<br>
Sent: Monday, June 28, 2010 11:27 PM<br>
To: Bill Riley<br>
Cc: cisco-voip<br>
Subject: Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
<br>
I've seen this dozens of times. Most people probably don't even realize<br>
they have a problem. Some may even have two providers that have managed
to<br>
be on the same clocking domain. I've even seen some people with providers<br>
that were willing to be the slave because the provider is SIP on the other<br>
side of the router.<br>
<br>
The only way to provide two different voice clocking domains is by having<br>
two separate groups of DSPs - this means HDV cards.<br>
<br>
If you have one PRI for failover or that is not used until the first is<br>
filled, you can probably get away with slips. The basic rule I've gone by<br>
is: if you don't need to fax or modem over the T1, you're probably
alright<br>
with slips if it's not your primary line. There are chances for voice<br>
quality, it all depends. It could be a cell-phone like quality issue you<br>
probably won't notice, or distinct chirps on the line that can be annoying.<br>
<br>
-nick<br>
<br>
On Mon, Jun 28, 2010 at 8:38 PM, Bill Riley <<a
href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>><br>
wrote:<br>
> I am not concerned with what works, and more concerned with what is<br>
> the best solution.<br>
><br>
><br>
><br>
> From: Jason Aarons (US) [mailto:<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>]<br>
> Sent: Monday, June 28, 2010 5:25 PM<br>
> To: Jim Reed; Bill; Beck, Christopher; cisco-voip<br>
> Subject: RE: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
><br>
><br>
><br>
> While it's working, from a solution design standpoint I'm being told<br>
> that if the timing varies from the providers it could result in<br>
> problems, so design preference should be to have separate routers in this<br>
scenario.<br>
><br>
><br>
><br>
> I'm with you, I've done it before and it did work, and I'd hate to<br>
> explain it to customer they need another router if the clocks are far<br>
apart.<br>
><br>
><br>
><br>
> From: Jim Reed [mailto:<a href="mailto:jreed@swiftnews.com">jreed@swiftnews.com</a>]<br>
> Sent: Monday, June 28, 2010 6:09 PM<br>
> To: Bill; Beck, Christopher; Jason Aarons (US); cisco-voip<br>
> Subject: Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
><br>
><br>
><br>
> I am currently using PRIs from different vendors - AT&T and Integra -<br>
> on the same router. Two (2) separate VWICs on the same 2851.<br>
VWIC2-1MFT-T1/E1.<br>
> 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>
> --<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>
><br>
><br>
><br>
> On 6/28/10 3:44 PM, "Bill" <<a
href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>>
wrote:<br>
><br>
> Are you sure that is the case currently? I think you can have multiple<br>
> PRI's inside the same router on an ISR but they can not be on the same<br>
VWIC.<br>
><br>
> Jason said you can not have multiple PRI's within the same router.<br>
><br>
><br>
> ________________________________<br>
><br>
> From: Beck, Christopher [mailto:<a href="mailto:CBeck@usg.com">CBeck@usg.com</a>]<br>
> Sent: Monday, June 28, 2010 4:40 PM<br>
> To: Bill; 'Jason Aarons (US)'; 'cisco-voip'<br>
> Subject: RE: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
><br>
> This is true on the 2800/3800 today (except in the case of the NM-NDV<br>
> modules mentioned, but I don't think so even in that case). It is<br>
> because there is a "single" PLL clocking circuit shared for all
PRI's. <br>
> The WIC must be configured to participate in that clocking circuit<br>
> prior to setting up the PRI. I can't remember any device
that could<br>
> 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<br>
> are close enough, especially if the local loop provider is the same on<br>
> all links. But, you have to test it to know in any case.<br>
><br>
><br>
><br>
> -Chris<br>
><br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Bill<br>
> Sent: Monday, June 28, 2010 4:21 PM<br>
> To: 'Jason Aarons (US)'; 'cisco-voip'<br>
> Subject: Re: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
><br>
> What? I know you could not do different Telco's on the same two port<br>
> card but you can't do two telco's in the same router? Is there an<br>
> official response to this? Is there a specific defect I can reference<br>
> with my Cisco AM?<br>
><br>
><br>
> ________________________________<br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Jason Aarons<br>
> (US)<br>
> Sent: Monday, June 28, 2010 4:12 PM<br>
> To: cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)<br>
> Subject: [cisco-voip] ISR G2 PVDM3 DSPs on backplane<br>
><br>
> A TAC engineer at Cisco Live confirmed you can't have multiple voice<br>
> PRIs from separate telcos come into a G2 with different clocks. For<br>
> example you have a AT&T PRI, a Verizon PRI, a Century Link PRI, a<br>
> Alltell PRI, a Paetec PRI all in the same router. You can't clock the<br>
> backplane to more than one source! You'll get slips, etc audio
will<br>
sound bad, faxes/modems will fail.<br>
> Fix is separate routers. He said he thought a 2800 with DSPs
on a<br>
> NM-HDV module would work though. My exact question was can you carve<br>
> up the backplane PVDM3 clocking for separate PRIs somehow.<br>
><br>
> ________________________________<br>
><br>
> Disclaimer: This e-mail communication and any attachments may contain<br>
> confidential and privileged information and is for use by the<br>
> designated<br>
> addressee(s) named above only. If you are not the intended addressee,<br>
> you are hereby notified that you have received this communication in<br>
> error and that any use or reproduction of this email or its contents<br>
> is strictly prohibited and may be unlawful. If you have received this<br>
> communication in error, please notify us immediately by replying to<br>
> this message and deleting it from your computer. Thank you.<br>
><br>
> Confidentiality Notice: This email is intended for the sole use of the<br>
> intended recipient(s) and may contain confidential, proprietary or<br>
> privileged information. If you are not the intended recipient, you are<br>
> notified that any use, review, dissemination, copying or action taken<br>
> based on this message or its attachments, if any, is prohibited. If<br>
> you are not the intended recipient, please contact the sender by reply<br>
> email and destroy or delete all copies of the original message and any<br>
attachments. Thank you.<br>
><br>
><br>
><br>
> ________________________________<br>
><br>
> Disclaimer: This e-mail communication and any attachments may contain<br>
> confidential and privileged information and is for use by the<br>
> designated<br>
> addressee(s) named above only. If you are not the intended addressee,<br>
> you are hereby notified that you have received this communication in<br>
> error and that any use or reproduction of this email or its contents<br>
> is strictly prohibited and may be unlawful. If you have received this<br>
> communication in error, please notify us immediately by replying to<br>
> this message and deleting it from your computer. Thank you.<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>