[VoiceOps] Adtran TA900 timing problems

My List Account mylists at battleop.com
Mon Nov 4 16:23:37 EST 2013


" 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:myaklin at g4.net] 
Sent: Monday, November 04, 2013 12:33 PM
To: My List Account
Cc: voiceops at voiceops.org
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
> 
> 
>




More information about the VoiceOps mailing list