[VoiceOps] Probably OT - Mitel - Adtran

Carlos Alcantar carlos at race.com
Thu Dec 2 13:38:13 EST 2010

I would connect a t1 test set directly to the pbx.  Set it to auto and
see what it sync's up with.



Carlos Alcantar

Race Telecommunications, Inc.

101 Haskins Way

South San Francisco, CA 94080

P: 415.376.3314

F: 650.649.3551

E: carlos at race.com




From: voiceops-bounces at voiceops.org
[mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Price
Sent: Thursday, December 02, 2010 8:03 AM
To: Richey; voiceops at voiceops.org
Subject: Re: [VoiceOps] Probably OT - Mitel - Adtran


Most Mitel PBX's use D4/B8ZS.  It's a strange setup but a known Mitel
configugation.   Their vendor is yanking your chain.    


From: voiceops-bounces at voiceops.org
[mailto:voiceops-bounces at voiceops.org] On Behalf Of Richey
Sent: Thursday, December 02, 2010 9:26 AM
To: voiceops at voiceops.org
Subject: [VoiceOps] Probably OT - Mitel - Adtran


Sorry if this is off topic but I really don't know of a better place to
ask this question.


I had a customer with a couple of locations that have Mitel SX200 PBXs.
Their voice vendor asked us to hand them a Voice T1 out of our CPE which
is an Adtran TA904.   They told us that the T1 needed to be configured
as D4/AMI.  After the install the customer experienced dropped calls and
the vendor could only really say that everything worked find with the
previous carrier so it has to be our problem.    After a day or so of
trying to figure out the problem I switched to D4/B8ZS because I was out
of ideas.    As soon as I switched to D4/B8ZS the errors stopped and the
calls stopped dropping.     I questioned the vendor again and he swears
that their side is set for D4/AMI and now he thinks it much be a glitch
in the Adtran.


I think it's either the vendor didn't look at the config or it's
something strange in the Mitel.  Has anyone else come across this





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20101202/60828aa6/attachment.html>

More information about the VoiceOps mailing list