<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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)">
<title>Re: [cisco-voip] Independent PRIs -- Single Router</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I understood the problem is PVDM2/DSPs sit have a single PLL
(phase-locked loop) which can only clock to 1 source. I could be wrong.<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"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Jim Reed<br>
<b>Sent:</b> Thursday, February 11, 2010 3:29 PM<br>
<b>To:</b> Lopez,Jim; Nick Matthews<br>
<b>Cc:</b> cisco-voip<br>
<b>Subject:</b> Re: [cisco-voip] Independent PRIs -- Single Router<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"'>So, if I’m reading Jim’s response correctly,
they remedied the issue by just using single port VWICs instead of dual port.
No need for an NM-HD2V. That won’t be an issue with this
configuration.<br>
<br>
Thank You...<br>
</span></b><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif"'>--
<br>
Jim Reed<br>
Technology Wrangler<br>
Swift Communications, Inc.<br>
970-683-5646 (Direct)<br>
775-772-7666 (Cell)<br>
<br>
</span></b><b><i><span style='font-size:7.0pt;font-family:"Verdana","sans-serif"'>“Did
Adam and Eve<br>
have navels?”<br>
</span></i></b><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif"'> --Martin
Gardner<br>
</span></b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
<br>
<br>
On 2/11/10 12:54 PM, "Lopez,Jim" <JLOPEZ@vha.com> wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:9.0pt;
font-family:"Verdana","sans-serif"'>Cool. I didn't know you could correct
this issue with different DSP groups.<br>
<br>
We had problems with slips between a data T1 and our voice PRI, provided by
different vendors, where they were connected to the same 2-port VWIC. We just
installed another VWIC card, move the data circuit onto it and the slips went
away.<br>
<br>
So I guess depending upon what kind of hardware you have available you can
correct this issue different ways.<br>
<br>
Here's a nice link about clock slips.<br>
<br>
<u><span style='color:blue'><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>
</span></u><br>
<br>
Jim<br>
<br>
-----Original Message-----<br>
From: <u><span style='color:blue'>cisco-voip-bounces@puck.nether.net</span></u>
[<u><span style='color:blue'><a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a></span></u>]
On Behalf Of Nick Matthews<br>
Sent: Thursday, February 11, 2010 12:36 PM<br>
To: Jim Reed<br>
Cc: cisco-voip<br>
Subject: Re: [cisco-voip] Independent PRIs -- Single Router<br>
<br>
The impact of not creating two separate clocking domains is having<br>
slips on one of your controllers. The impact of slips can vary - it<br>
will kill nearly any fax or modem on it, and can cause mild amount of<br>
clips, bits, and audio noise on your voice calls. Many people have it<br>
on their network for extended periods of time since people have become<br>
accustomed to "cell phone quality". Faxes and modems won't play
on<br>
it, however.<br>
<br>
To create two clocking domains you need two different groups of DSPs.<br>
This is usually done with a card like the NM-HDV or NM-HDV2, where<br>
there are DSPs on a NM you insert into the router.<br>
<br>
<br>
-nick<br>
<br>
On Thu, Feb 11, 2010 at 12:29 PM, Jim Reed <<u><span style='color:blue'>jreed@swiftnews.com</span></u>>
wrote:<br>
> Peter,<br>
> Thank You! That's one I HAD NOT thought of. But it makes
perfect sense as<br>
> they are different vendors. That being said - and me being ignorant
in that<br>
> respect - what is the method for configuring separate clocking domains, if<br>
> you don't mind me asking.<br>
><br>
> Thank You...<br>
> --<br>
> Jim Reed<br>
> Swift Communications, Inc.<br>
> 970-683-5646 (Direct)<br>
> 775-772-7666 (Cell)<br>
><br>
> "Did Adam and Eve<br>
> have navels?"<br>
> --Martin Gardner<br>
><br>
><br>
><br>
> On 2/11/10 10:21 AM, "Peter Slow" <<u><span style='color:
blue'>peter.slow@gmail.com</span></u>> wrote:<br>
><br>
> you sir, are going to want to make sure that whatever hardware you<br>
> use, it has two separate clocking domains, otherwise you are going to<br>
> be a very unhappy camper.<br>
><br>
> For instance, a 5300 or a VWIC-2MFT-T1 with DSPs all clocked off the<br>
> same source aren't going to work.<br>
><br>
> -Peter<br>
><br>
> On Thu, Feb 11, 2010 at 11:55 AM, Cristobal Priego<br>
> <<u><span style='color:blue'>cristobalpriego@gmail.com</span></u>>
wrote:<br>
>> Jim,<br>
>><br>
>> when you create your outgoing dial-peers on the gateway just configure
th<br>
>> proper port to point them to the outoing pri, on the cucm you only
need to<br>
>> point them to the H.323 device and the gateway will take care or the
rest.<br>
>> for incoming calls just make sure you have an incoming dial-peer and
then<br>
>> a<br>
>> voip dial-peer pointing to your first and second node<br>
>><br>
>><br>
>> 2010/2/11 Jim Reed <<u><span style='color:blue'>jreed@swiftnews.com</span></u>><br>
>>><br>
>>> Due to contract obligations, we need to connect PRIs from two (2)<br>
>>> different vendors to a single router. I think I've got a
fairly firm<br>
>>> grasp<br>
>>> on what needs to be done but thought I would run it by this group
to see<br>
>>> if<br>
>>> I'm missing anything.<br>
>>><br>
>>> Fortunately, I can have the DIDs from one PRI moved to the other
so it's<br>
>>> my intent to have all inbound calls one (1) PRI and all outbound
calls on<br>
>>> the other.<br>
>>><br>
>>> Once the contract is up on the more expensive PRI, we'll contract
for a<br>
>>> second from the other vendor and bond all forty-six (46) channels<br>
>>> together.<br>
>>><br>
>>> My assumption is that I need only a single gateway address and
just<br>
>>> identify which interface (port) to use when the caller makes an
outbound<br>
>>> call. Everything is configured H323.<br>
>>><br>
>>> Any advice, hints, tips, suggestions, etc., will be greatly
appreciated.<br>
>>> There will be a few analog devices off fxs ports but that is
pretty much<br>
>>> a<br>
>>> no brainer. Just want to make sure I get things in Call
Manager<br>
>>> 4.2(3)sr4a<br>
>>> and the 2851 router configured correctly.<br>
>>><br>
>>> Thank You...<br>
>>> --<br>
>>> Jim Reed<br>
>>> Technology Wrangler<br>
>>> Swift Communications, Inc.<br>
>>> 970-683-5646 (Direct)<br>
>>> 775-772-7666 (Cell)<br>
>>><br>
>>> "Did Adam and Eve<br>
>>> have navels?"<br>
>>> --Martin Gardner<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> cisco-voip mailing list<br>
>>> <u><span style='color:blue'>cisco-voip@puck.nether.net<br>
</span></u>>>> <u><span style='color:blue'>https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</span></u>>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> <u><span style='color:blue'>cisco-voip@puck.nether.net<br>
</span></u>>> <u><span style='color:blue'>https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</span></u>>><br>
>><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <u><span style='color:blue'>cisco-voip@puck.nether.net<br>
</span></u>> <u><span style='color:blue'>https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</span></u>><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<u><span style='color:blue'>cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip</span></u></span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<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></P></BODY></HTML>