[cisco-voip] Independent PRIs -- Single Router

[Nick Matthews]

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
>
>