[cisco-voip] Independent PRIs -- Single Router

Thu Feb 11 19:44:17 EST 2010

The first gen 2 port VWICs have a single PLL chip shared between both
ports. I've heard the version2 VWICs corrected this but have heard
conflicting reports. Either way, I think there may be a clocking issue
for one of the PRIs if using WIC/VWIC slots and PVDM/DSPs on the
mainboard. Another possibility would be to do internal clocking on one
of the PRIs, but I've never had success with that on a PRI yet from a
carrier when trying to overcome a clocking issue.

On Thu, Feb 11, 2010 at 3:19 PM, Jason Aarons (US)
<jason.aarons at us.didata.com> wrote:
> 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.
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jim Reed
> Sent: Thursday, February 11, 2010 3:29 PM
> To: Lopez,Jim; Nick Matthews
>
> Cc: cisco-voip
> Subject: Re: [cisco-voip] Independent PRIs -- Single Router
>
>
>
> 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.
>
> Thank You...
> --
> Jim Reed
> Technology Wrangler
> Swift Communications, Inc.
> 970-683-5646 (Direct)
> 775-772-7666 (Cell)
>
> “Did Adam and Eve
> have navels?”
>        --Martin Gardner
>
>
>
> On 2/11/10 12:54 PM, "Lopez,Jim" <JLOPEZ at vha.com> wrote:
>
> Cool.  I didn't know you could correct this issue with different DSP groups.
>
> 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.
>
> So I guess depending upon what kind of hardware you have available you can
> correct this issue different ways.
>
> Here's a nice link about clock slips.
>
> http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html
>
>
> Jim
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nick Matthews
> Sent: Thursday, February 11, 2010 12:36 PM
> To: Jim Reed
> Cc: cisco-voip
> Subject: Re: [cisco-voip] Independent PRIs -- Single Router
>
> The impact of not creating two separate clocking domains is having
> slips on one of your controllers.  The impact of slips can vary - it
> will kill nearly any fax or modem on it, and can cause mild amount of
> clips, bits, and audio noise on your voice calls.  Many people have it
> on their network for extended periods of time since people have become
> accustomed to "cell phone quality".  Faxes and modems won't play on
> it, however.
>
> To create two clocking domains you need two different groups of DSPs.
> This is usually done with a card like the NM-HDV or NM-HDV2, where
> there are DSPs on a NM you insert into the router.
>
>
> -nick
>
> On Thu, Feb 11, 2010 at 12:29 PM, Jim Reed <jreed at swiftnews.com> wrote:
>> Peter,
>> Thank You!  That's one I HAD NOT thought of.  But it makes perfect sense
>> as
>> they are different vendors.  That being said - and me being ignorant in
>> that
>> respect - what is the method for configuring separate clocking domains, if
>> you don't mind me asking.
>>
>> Thank You...
>> --
>> Jim Reed
>> Swift Communications, Inc.
>> 970-683-5646 (Direct)
>> 775-772-7666 (Cell)
>>
>> "Did Adam and Eve
>> have navels?"
>>        --Martin Gardner
>>
>>
>>
>> On 2/11/10 10:21 AM, "Peter Slow" <peter.slow at gmail.com> wrote:
>>
>> you sir, are going to want to make sure that whatever hardware you
>> use, it has two separate clocking domains, otherwise you are going to
>> be a very unhappy camper.
>>
>> For instance, a 5300  or a VWIC-2MFT-T1 with DSPs all clocked off the
>> same source aren't going to work.
>>
>> -Peter
>>
>> On Thu, Feb 11, 2010 at 11:55 AM, Cristobal Priego
>> <cristobalpriego at gmail.com> wrote:
>>> Jim,
>>>
>>> when you create your outgoing dial-peers on the gateway just configure th
>>> proper port to point them to the outoing pri, on the cucm you only need
>>> to
>>> point them to the H.323 device and the gateway will take care or the
>>> rest.
>>> for incoming calls just make sure you have an incoming dial-peer and then
>>> a
>>> voip dial-peer pointing to your first and second node
>>>
>>>
>>> 2010/2/11 Jim Reed <jreed at swiftnews.com>
>>>>
>>>> Due to contract obligations, we need to connect PRIs from two (2)
>>>> different vendors to a single router.  I think I've got a fairly firm
>>>> grasp
>>>> on what needs to be done but thought I would run it by this group to see
>>>> if
>>>> I'm missing anything.
>>>>
>>>> Fortunately, I can have the DIDs from one PRI moved to the other so it's
>>>> my intent to have all inbound calls one (1) PRI and all outbound calls
>>>> on
>>>> the other.
>>>>
>>>> Once the contract is up on the more expensive PRI, we'll contract for a
>>>> second from the other vendor and bond all forty-six (46) channels
>>>> together.
>>>>
>>>> My assumption is that I need only a single gateway address and just
>>>> identify which interface (port) to use when the caller makes an outbound
>>>> call.  Everything is configured H323.
>>>>
>>>> Any advice, hints, tips, suggestions, etc., will be greatly appreciated.
>>>>  There will be a few analog devices off fxs ports but that is pretty
>>>> much
>>>> a
>>>> no brainer.  Just want to make sure I get things in Call Manager
>>>> 4.2(3)sr4a
>>>> and the 2851 router configured correctly.
>>>>
>>>> Thank You...
>>>> --
>>>> Jim Reed
>>>> Technology Wrangler
>>>> Swift Communications, Inc.
>>>> 970-683-5646 (Direct)
>>>> 775-772-7666 (Cell)
>>>>
>>>> "Did Adam and Eve
>>>> have navels?"
>>>>        --Martin Gardner
>>>>
>>>>
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> ________________________________
>
> 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.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>