Send VoiceOps mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Re: Adtran TA900 timing problems (Paul Timmins)
2. Re: Adtran TA900 timing problems (Matt Yaklin)
3. Re: Adtran TA900 timing problems (Matt Yaklin)
4. Re: Adtran TA900 timing problems (Jay Hennigan)
5. Re: Adtran TA900 timing problems (My List Account)
----------------------------------------------------------------------
Message: 1
Date: Mon, 4 Nov 2013 12:18:47 -0500
From: Paul Timmins <[email protected]>
To: My List Account <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
We've never seen that here. Do you see incrementing errors on either side of
the interface? Do you have log entries on the TA900s?
I assume you tested newer (or older) firmware revisions on the TA900s?
On Mon, 11/04/2013 11:24 AM, "My List Account" <[email protected]> wrote:
>
Has anyone ever seen this problem? I have a good number of TA900s and TA900Es
on the other side of a 7206VXR with PA-MC-T3 cards. Once every few months SIP
accounts in the TA900s that are attached to FXS ports have trouble passing
audio. It sounds like the audio stream is On/Off about every 3 seconds. The
only ?fix? is to change the timing from the T1 to internal or reboot the router
which effectively does the same thing.
It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or data
traffic behind the router. We never see a problem with other Cisco routers
connected to the same DS3(s) including voice on Cisco 2431-8FXS and 16FXS
rotuers. When the problem happens it will happen to every TA900 or TA900E at
the same time on the same DS3. It?s always a single random DS3 in the same
box.
I?ve had countless tickets open with our DS3/T1 Provider over the years and
they always say they see nothing. Adtran?s only solution so far is to change
the timing when it happens. One tech suggested we just run internal timing
all the time but that seems to only work for 31 days. I?ve completely swapped
out the 7200 and the PA-MC-T3 cards. I?ve had a JDSU test set on random DS3s
for weeks at a time and never seen a problem.
We set up the routers so that the T1 is the Primary and the Internal is
secondary. I suspect that something happens to the primary clock and it fails
to the internal clock. When the primary clock becomes available again the
TA900 does not revert back to the T1 clock. So when we get to around 31 days
the internal timing fails and then the problem with the audio happens.
-Richey
_______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20131104/f2a6f9db/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 4 Nov 2013 12:33:24 -0500 (EST)
From: Matt Yaklin <[email protected]>
To: My List Account <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-15"; Format="flowed"
I have also not been seeing such a problem with an almost identical
setup.
I am using a 7206VXR with PA-MC-2T3+. Two port DS3 card, clear or
channelized running c7200-js-mz.123-3a.bin. The DS3 is using internal
timing. It is channelized.
My DS3 goes from the router to an Adtran M13 mux (MX2820 with a M13 card).
That Adtran M13 mux card gets it's timing from the loop.
As an example of a flawlessly working Adtran hanging off the DS3 is a:
Total Access 916 (1st Gen)
A2.04.00.E
We also use the FXS ports on this box.
On the TA916:
The primary clock source is t1 0/1.
The secondary clock source is t1 0/2 (we do not have a 2nd t1 installed).
We do not set the internal at all.
This T1 is carried over our SONET network, other M13 muxes, etc.. which
pretty much all have BITS clocks connected to them for proper network
timing. From the Central Office to the customer premise would either
be a T1 or copper pairs build a T1 (TA3000) leased from Fairpoint.
Only the Cisco to the M13 mux card has an odd timing setup with no
true BITS clock going into them.
How much of the network do you control? I am going to guess you lease
a channelized DS3(s) from an ILEC and then they terminate the leased T1s
into THEIR m13 mux at the central office which come back to you over the
DS3?
Is the cisco router DS3 using internal or line timing?
Do you have a totally different Cisco 7206 with Adtran 9xx devices hanging
off of it then "just work"? You mention other Cisco routers so I am just
wondering if a 9xx is working on them...
Just rambling here... throwing out what I do. It might set off a light
bulb that leads to the fix.
matt
On Mon, 4 Nov 2013, My List Account wrote:
>
> Has anyone ever seen this problem?? I have a good number of TA900s and
> TA900Es on the other side of a 7206VXR with PA-MC-T3 cards.?? Once every few
> months SIP accounts in the TA900s that are attached to FXS ports have trouble
> passing
> audio.? It sounds like the audio stream is On/Off about every 3 seconds.??
> The only ?fix? is to change the timing from the T1 to internal or reboot the
> router which effectively does the same thing.
>
> ?
>
> It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or
> data traffic behind the router.? We never see a problem with other Cisco
> routers connected to the same DS3(s) including voice on Cisco 2431-8FXS and
> 16FXS
> rotuers.?? When the problem happens it will happen to every TA900 or TA900E
> at the same time on the same DS3.?? It?s always a single random DS3 in the
> same box.
>
> ?
>
> I?ve had countless tickets open with our DS3/T1 Provider over the years and
> they always say they see nothing.? Adtran?s only solution so far is to change
> the timing when it happens.?? One tech suggested we just run internal timing
> all the time but that seems to only work for 31 days.? I?ve completely
> swapped out the 7200 and the PA-MC-T3 cards.?? I?ve had a JDSU test set on
> random DS3s for weeks at a time and never seen a problem.
>
> ?
>
> We set up the routers so that the T1 is the Primary and the Internal is
> secondary.? I suspect that something happens to the primary clock and it
> fails to the internal clock.? ?When the primary clock becomes available again
> the TA900
> does not revert back to the T1 clock.? So when we get to around 31 days the
> internal timing fails and then the problem with the audio happens.?
>
> ?
>
> ?
>
> ?
>
> -Richey
>
>
>
------------------------------
Message: 3
Date: Mon, 4 Nov 2013 12:41:33 -0500 (EST)
From: Matt Yaklin <[email protected]>
To: My List Account <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-15"; Format="flowed"
I forgot to mention that the cisco T1s on the DS3 use line
timing in my setup. So line and line on both sides. The T1
and the Adtran.
Also these routers have the concept of bandwidth points. I assume
you are not oversubscribed and the router is very busy?
matt
On Mon, 4 Nov 2013, Matt Yaklin wrote:
>
>
> I have also not been seeing such a problem with an almost identical
> setup.
>
> I am using a 7206VXR with PA-MC-2T3+. Two port DS3 card, clear or
> channelized running c7200-js-mz.123-3a.bin. The DS3 is using internal
> timing. It is channelized.
>
> My DS3 goes from the router to an Adtran M13 mux (MX2820 with a M13 card).
> That Adtran M13 mux card gets it's timing from the loop.
>
> As an example of a flawlessly working Adtran hanging off the DS3 is a:
>
> Total Access 916 (1st Gen)
> A2.04.00.E
>
> We also use the FXS ports on this box.
>
> On the TA916:
> The primary clock source is t1 0/1.
> The secondary clock source is t1 0/2 (we do not have a 2nd t1 installed).
> We do not set the internal at all.
>
> This T1 is carried over our SONET network, other M13 muxes, etc.. which
> pretty much all have BITS clocks connected to them for proper network
> timing. From the Central Office to the customer premise would either
> be a T1 or copper pairs build a T1 (TA3000) leased from Fairpoint.
>
> Only the Cisco to the M13 mux card has an odd timing setup with no
> true BITS clock going into them.
>
> How much of the network do you control? I am going to guess you lease
> a channelized DS3(s) from an ILEC and then they terminate the leased T1s
> into THEIR m13 mux at the central office which come back to you over the
> DS3?
>
> Is the cisco router DS3 using internal or line timing?
>
> Do you have a totally different Cisco 7206 with Adtran 9xx devices hanging
> off of it then "just work"? You mention other Cisco routers so I am just
> wondering if a 9xx is working on them...
>
> Just rambling here... throwing out what I do. It might set off a light
> bulb that leads to the fix.
>
> matt
>
>
> On Mon, 4 Nov 2013, My List Account wrote:
>
>>
>> Has anyone ever seen this problem?? I have a good number of TA900s and
>> TA900Es on the other side of a 7206VXR with PA-MC-T3 cards.?? Once every
>> few months SIP accounts in the TA900s that are attached to FXS ports have
>> trouble passing
>> audio.? It sounds like the audio stream is On/Off about every 3 seconds.??
>> The only ?fix? is to change the timing from the T1 to internal or reboot
>> the router which effectively does the same thing.
>>
>> ?
>>
>> It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or
>> data traffic behind the router.? We never see a problem with other Cisco
>> routers connected to the same DS3(s) including voice on Cisco 2431-8FXS and
>> 16FXS
>> rotuers.?? When the problem happens it will happen to every TA900 or TA900E
>> at the same time on the same DS3.?? It?s always a single random DS3 in the
>> same box.
>>
>> ?
>>
>> I?ve had countless tickets open with our DS3/T1 Provider over the years and
>> they always say they see nothing.? Adtran?s only solution so far is to
>> change the timing when it happens.?? One tech suggested we just run
>> internal timing
>> all the time but that seems to only work for 31 days.? I?ve completely
>> swapped out the 7200 and the PA-MC-T3 cards.?? I?ve had a JDSU test set on
>> random DS3s for weeks at a time and never seen a problem.
>>
>> ?
>>
>> We set up the routers so that the T1 is the Primary and the Internal is
>> secondary.? I suspect that something happens to the primary clock and it
>> fails to the internal clock.? ?When the primary clock becomes available
>> again the TA900
>> does not revert back to the T1 clock.? So when we get to around 31 days the
>> internal timing fails and then the problem with the audio happens.?
>>
>> ?
>>
>> ?
>>
>> ?
>>
>> -Richey
>>
>>
>
------------------------------
Message: 4
Date: Mon, 04 Nov 2013 13:14:53 -0800
From: Jay Hennigan <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 11/4/13 9:41 AM, Matt Yaklin wrote:
>
> I forgot to mention that the cisco T1s on the DS3 use line
> timing in my setup. So line and line on both sides. The T1
> and the Adtran.
Don't do that then. :-)
Every T1 span must have exactly one source of clocking.
My recommendation is to configure the T3 controller on the 7206VXR to
internal clocking on all of its T1s, and clock the Adtrans from T1 0/1
(line).
If both sides are set to internal, you'll get clock slips as the
oscillators drift slightly with respect to each other.
If both sides are set to line, then there's no reference clock. The
line will probably sync up initially as the free-running T1 will be
close enough to sync. Over time the frequency will drift up or down
until one side can no longer sync. In some cases they'll recover on
their own, and in others you need to shut/no shut or otherwise force a
resync.
So, don't do that.
--
Jay Hennigan - CCIE #7880 - Network Engineering - [email protected]
Impulse Internet Service - http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV
------------------------------
Message: 5
Date: Mon, 4 Nov 2013 16:23:37 -0500
From: "My List Account" <[email protected]>
To: "'Matt Yaklin'" <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
" How much of the network do you control? I am going to guess you lease a
channelized DS3(s) from an ILEC and then they terminate the leased T1s into
THEIR m13 mux at the central office which come back to you over the DS3?"
It's 7206 >> CLEC >> TA900. We don't have control over what's in the
middle. These circuits span multiple Central Offices in our LATA. The
last mile is from the ILEC to CO where it's then handed to a 3rd party CLEC
that moves it around town back to us on their SONET ring and then they hand
it to us out of a DMXTend on DS3 interfaces.
" Do you have a totally different Cisco 7206 with Adtran 9xx devices hanging
off of it then "just work"? You mention other Cisco routers so I am just
wondering if a 9xx is working on them..."
It's one 7206 with 4 DS3s. The CPE on the far end of the 7206 are TA900s,
TA900e (mlppp), Cisco IAD2431s, Cisco 2800s, 3800s, etc. Only the TA900s
with an analog hand off on FXS ports to the customer's PBX or Fax machine
encounter this problem and nothing else.
Richey
-----Original Message-----
From: Matt Yaklin [mailto:[email protected]]
Sent: Monday, November 04, 2013 12:33 PM
To: My List Account
Cc: [email protected]
Subject: Re: [VoiceOps] Adtran TA900 timing problems
I have also not been seeing such a problem with an almost identical setup.
I am using a 7206VXR with PA-MC-2T3+. Two port DS3 card, clear or
channelized running c7200-js-mz.123-3a.bin. The DS3 is using internal
timing. It is channelized.
My DS3 goes from the router to an Adtran M13 mux (MX2820 with a M13 card).
That Adtran M13 mux card gets it's timing from the loop.
As an example of a flawlessly working Adtran hanging off the DS3 is a:
Total Access 916 (1st Gen)
A2.04.00.E
We also use the FXS ports on this box.
On the TA916:
The primary clock source is t1 0/1.
The secondary clock source is t1 0/2 (we do not have a 2nd t1 installed).
We do not set the internal at all.
This T1 is carried over our SONET network, other M13 muxes, etc.. which
pretty much all have BITS clocks connected to them for proper network
timing. From the Central Office to the customer premise would either be a T1
or copper pairs build a T1 (TA3000) leased from Fairpoint.
Only the Cisco to the M13 mux card has an odd timing setup with no true BITS
clock going into them.
How much of the network do you control? I am going to guess you lease a
channelized DS3(s) from an ILEC and then they terminate the leased T1s into
THEIR m13 mux at the central office which come back to you over the DS3?
Is the cisco router DS3 using internal or line timing?
Do you have a totally different Cisco 7206 with Adtran 9xx devices hanging
off of it then "just work"? You mention other Cisco routers so I am just
wondering if a 9xx is working on them...
Just rambling here... throwing out what I do. It might set off a light bulb
that leads to the fix.
matt
On Mon, 4 Nov 2013, My List Account wrote:
>
> Has anyone ever seen this problem?? I have a good number of TA900s and
> TA900Es on the other side of a 7206VXR with PA-MC-T3 cards.?? Once every
few months SIP accounts in the TA900s that are attached to FXS ports have
trouble passing audio.? It sounds like the audio stream is On/Off about
every 3 seconds.?? The only ?fix? is to change the timing from the T1 to
internal or reboot the router which effectively does the same thing.
>
> ?
>
> It never has an effect on PRI/T1 voice, Hosted PBX behind that router,
> or data traffic behind the router.? We never see a problem with other
Cisco routers connected to the same DS3(s) including voice on Cisco
2431-8FXS and 16FXS rotuers.?? When the problem happens it will happen to
every TA900 or TA900E at the same time on the same DS3.?? It?s always a
single random DS3 in the same box.
>
> ?
>
> I?ve had countless tickets open with our DS3/T1 Provider over the
> years and they always say they see nothing.? Adtran?s only solution so far
is to change the timing when it happens.?? One tech suggested we just run
internal timing all the time but that seems to only work for 31 days.? I?ve
completely swapped out the 7200 and the PA-MC-T3 cards.?? I?ve had a JDSU
test set on random DS3s for weeks at a time and never seen a problem.
>
> ?
>
> We set up the routers so that the T1 is the Primary and the Internal
> is secondary.? I suspect that something happens to the primary clock and
it fails to the internal clock.? ?When the primary clock becomes available
again the TA900 does not revert back to the T1 clock.? So when we get to
around 31 days the internal timing fails and then the problem with the audio
happens.
>
> ?
>
> ?
>
> ?
>
> -Richey
>
>
>
------------------------------
Subject: Digest Footer
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
End of VoiceOps Digest, Vol 53, Issue 6
***************************************
