Well that's what I did and they seem to be operating just fine. The
CLEC told me even though they are the same CLEC, it is a different
switch.. but yeah hehe in theory I guess the timing would have to be
the same since THEIR switches are linked, eh?
On 4/28/06, [EMAIL PROTECTED] [EMAIL
Hi,
With a digium dual PRI card (dual span). Is there any reason I can't
have both PRIs being PRIMARY timing sources? They are both from
different CLECs, and as such I need them both to do their own timing.
___
--Bandwidth and Colocation provided by
On Friday 28 April 2006 14:07, Matt wrote:
With a digium dual PRI card (dual span). Is there any reason I can't
have both PRIs being PRIMARY timing sources? They are both from
different CLECs, and as such I need them both to do their own timing.
Nope. Digium cards do not support this
Matt wrote:
Hi,
With a digium dual PRI card (dual span). Is there any reason I can't
have both PRIs being PRIMARY timing sources? They are both from
different CLECs, and as such I need them both to do their own timing.
If the two CLECs had different timing, it would mean modem calls
Matt wrote:
Hi,
With a digium dual PRI card (dual span). Is there any reason I can't
have both PRIs being PRIMARY timing sources? They are both from
different CLECs, and as such I need them both to do their own timing.
No. However, if the two CLECs are close enough in timing, it should
Ok.. I sort of lied.. it's the same CLEC but two different switches..
was told by them since they are different switches I needed primary
timing so in theory it should work if I set it as secondary.. ok
we'll try!
Just out of curiousity.. what happens if I set both as 1 (primary?)
On
The following information is accurate for a situation where both T1s are
connected to telco switches and the telco is therefore providing the
timing signals. If one of the T1s is point to point (such as a tie line)
then this information may or may not apply depending upon what's on the
remote end.
