> >>What are the practical effects with in-correct clock sync
> >>-like to you hear odd buzzing, or dropped voice or gaps of audio ??
> >
> >As mentioned earlier, it depends entirely upon how far off one clock is
> >from the clock at the other end of the T1.
> >
> >If they are off by a little bit
At 9:17 PM +0800 1/14/04, Steve Underwood wrote:
[snip]
It's the same in the US, however in the US there are far more independent
telcos (example, Iowa had the distinction of the most independent
telcos at 600+ of all states) and many of those do not have an
engineering staff nor the expertise to
Rich Adamson wrote:
What are the practical effects with in-correct clock sync
-like to you hear odd buzzing, or dropped voice or gaps of audio ??
You may get gaps where frames are discarded, this will be across all timeslots
so an individual loss isnt a lot of data, you'll probably get awa
On Wed, 14 Jan 2004, Steve Underwood wrote:
> That must have been an FSK modem. Most advanced modems completely loose
> sync on the first sample slip. The sample slip causes a jump in phase,
> and phase is critical to the correct operation of most modems.
It was V.22. No error correction or
> > What are the practical effects with in-correct clock sync
> > -like to you hear odd buzzing, or dropped voice or gaps of audio ??
>
> You may get gaps where frames are discarded, this will be across all timeslots
> so an individual loss isnt a lot of data, you'll probably get away with the od
Rich Adamson wrote:
To complete this rather lengthy topic... what happens if you ignore all of
this and just slap a bunch of systems together with no regard to a master
sync source? The quality and stability of your network will likely not be
as good as what it could be. If your clocks (in each d
Stephen Davies wrote:
On Wed, 14 Jan 2004, TC wrote:
What are the practical effects with in-correct clock sync
-like to you hear odd buzzing, or dropped voice or gaps of audio ??
Old-fart anecdote about this - in the early 80s we had some 1200bps
modems that we used to connect to client s
TC wrote:
To complete this rather lengthy topic... what happens if you ignore all of
this and just slap a bunch of systems together with no regard to a master
sync source? The quality and stability of your network will likely not be
as good as what it could be. If your clocks (in each device) hap
> > Think we're trying to make this more difficult then what it really is.
>
> [ lengthy and accurate text snipped ]
>
> I think you're oversimplifying. There is *no* need to have individual T1
> spans synchronized to each other unless you're trying to aggregate the data
> on those individual
> What are the practical effects with in-correct clock sync
> -like to you hear odd buzzing, or dropped voice or gaps of audio ??
You may get gaps where frames are discarded, this will be across all timeslots
so an individual loss isnt a lot of data, you'll probably get away with the odd
one but
On Wednesday, January 14, 2004 11:41 AM, TC [SMTP:[EMAIL PROTECTED]
wrote:
> What are the practical effects with in-correct clock sync
> -like to you hear odd buzzing, or dropped voice or gaps of audio ??
>
It depends on how out of sync the clocks are and the type of signaling
being used.
For a
> > To complete this rather lengthy topic... what happens if you ignore all of
> > this and just slap a bunch of systems together with no regard to a master
> > sync source? The quality and stability of your network will likely not be
> > as good as what it could be. If your clocks (in each device
On Wed, 14 Jan 2004, TC wrote:
> What are the practical effects with in-correct clock sync
> -like to you hear odd buzzing, or dropped voice or gaps of audio ??
Old-fart anecdote about this - in the early 80s we had some 1200bps
modems that we used to connect to client sites. When our phone
co
> > > If you've got spans from different providers...you're in for an
> > > adventure. You'll be able to do one of the following (which one is telco
> > > and luck dependant):
> >
> > So what you're saying is that the TE410P is not capable of *independently*
> > clocking each of the T1s. Hell e
> Think we're trying to make this more difficult then what it really is.
[ lengthy and accurate text snipped ]
I think you're oversimplifying. There is *no* need to have individual T1
spans synchronized to each other unless you're trying to aggregate the data
on those individual spans. DS2/DS
> To complete this rather lengthy topic... what happens if you ignore all of
> this and just slap a bunch of systems together with no regard to a master
> sync source? The quality and stability of your network will likely not be
> as good as what it could be. If your clocks (in each device) happe
> > If you've got spans from different providers...you're in for an
> > adventure. You'll be able to do one of the following (which one is telco
> > and luck dependant):
>
> So what you're saying is that the TE410P is not capable of *independently*
> clocking each of the T1s. Hell even the vener
> > If you've got spans from different providers...you're in for an
> > adventure. You'll be able to do one of the following (which one is telco
> > and luck dependant):
>
> So what you're saying is that the TE410P is not capable of *independently*
> clocking each of the T1s. Hell even the vener
On Tuesday, January 13, 2004 7:36 AM, Andrew Kohlsmith
[SMTP:[EMAIL PROTECTED] wrote:
> > If you've got spans from different providers...you're in for an
> > adventure. You'll be able to do one of the following (which one is
> > telco
> > and luck dependant):
If all providers are referenced back
> If you've got spans from different providers...you're in for an
> adventure. You'll be able to do one of the following (which one is telco
> and luck dependant):
So what you're saying is that the TE410P is not capable of *independently*
clocking each of the T1s. Hell even the venerable old AS5
Quoting "C. Maj" <[EMAIL PROTECTED]>:
> On Sun, 11 Jan 2004, John Brown (CV) waxed:
>
> > THank you. Thats what I thought it should be.
> >
> > Off to call the telco and tell them they are mucked up.
>
> I'm wondering if I should do the same for my T400, as I seem
> to be getting sim
> Does anyone else have 2 t1's plugged into their T400 ? If
> so, how are they synced ? This was just happening at night,
> but I lost the second span a dozen times already today, all
> within less than an hour earlier this afternoon.
>
If you've got 2 spans from the same provider, you should ju
On Sun, 11 Jan 2004, John Brown (CV) waxed:
> THank you. Thats what I thought it should be.
>
> Off to call the telco and tell them they are mucked up.
I'm wondering if I should do the same for my T400, as I seem
to be getting similar errors. Might not be just the telco.
I set one span to 1,
THank you. Thats what I thought it should be.
Off to call the telco and tell them they are mucked up.
On Sun, Jan 11, 2004 at 06:54:11PM -0600, Don Pobanz wrote:
> On Sunday, January 11, 2004 5:41 PM, John Brown (CV)
> [SMTP:[EMAIL PROTECTED] wrote:
> > Hi List,
> >
> > After reading a bunch
On Sunday, January 11, 2004 5:41 PM, John Brown (CV)
[SMTP:[EMAIL PROTECTED] wrote:
> Hi List,
>
> After reading a bunch of the docs, list post archives, it
> still seems that a clear definition of how to clock the T100P
> card is muddy.
>
> zttool says that the link is "INTERNALLY CLOCKED",
>
>
Hi List,
After reading a bunch of the docs, list post archives, it
still seems that a clear definition of how to clock the T100P
card is muddy.
zttool says that the link is "INTERNALLY CLOCKED",
does this mean the T100P is providing clock, or does
this mean the T100P is getting clock from the T
26 matches
Mail list logo
