The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
madams
New Contributor

atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Hello,

We have adtran 830 (rev A04) with E1 modules. We are trying to connect to an AudioCodes M3K. The AudioCodes is set to: generate clock, crc4, HDB3, Network side EuroISDN.

We are getting a D-channel alarm on the AudioCodes side:

On the AdTran side:

ae3.png

ae2.png

ae1.png

When we change the the "auto alarm" setting the AudioCodes sees the change and reflects the AIS or RAI so the cabling looks to be correct.

Any suggestions would be greatly appericated...

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Port 2 is still showing an LOS alarm. I agree it seems strange. It almost seems like the transmit pair from the ATLAS is fine, but the receive pair is bad.

The alarm refresh is real-time. It will take 15-20 seconds for the LOF to clear, but the LOS should clear almost immediately. You can verify the port on the ATLAS with a loopback plug, if you have one. All alarms should clear to a hard loopback.

View solution in original post

0 Kudos
5 Replies
Anonymous
Not applicable

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Thank you for using the ADTRAN Community Support Forums.

I'm not positive which port, in the screen captures above, you are using. If you are using PORT 2, then it is showing an LOS (Loss of Signal) alarm, which means it is not receiving any signal on that port. This would indicate a cable issue.

If you are using PORT 1, then do you have it configured as a NETWORK TERM or USER TERM entry in the DIAL PLAN? The ATLAS it is configured based on what it is terminating, so when connecting to a NETWORK PRI (or a PRI from equipment acting in a Network role) the ATLAS PRA should be configured as a NETWORK TERM entry (the ATLAS is in a "user role"). When connecting to user equipment, or equipment in a user role, the ATLAS PRA should be configured as a USER TERM entry (the ATLAS is acting in the "network role").

Hope this helps,

Patrick

madams
New Contributor

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Hi Patrick

Sorry about the port confusion. The port is slot-1 port-2. The information about user\network was good because I had them backwards. The AudioCodes shows the following:

ae4.png

ae9.png

Futhermore on the adtran side when I change the "auto alarm" mode to AIS or RAI it is reflected on the AudioCodes side. I was hoping that proved the cabling is good.

The dial plan is configured as the following:

ae6.png

ae7.png

Alrams are still the same:

ae8.png

We are going to attempt to straighten out the cabling tomorrow. It just seems odd the audioccodes doesn't see this as an LOS and then responds to the chnage in alarm mode on the adtran side any chance we could be having an issue with the alram refresh? Thanks...

madams
New Contributor

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Hi Patrick,

One thing I forgot to mention was in the audiocodes port picture it is port 6 and it is in a d-channel alarm..,

Anonymous
Not applicable

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Port 2 is still showing an LOS alarm. I agree it seems strange. It almost seems like the transmit pair from the ATLAS is fine, but the receive pair is bad.

The alarm refresh is real-time. It will take 15-20 seconds for the LOF to clear, but the LOS should clear almost immediately. You can verify the port on the ATLAS with a loopback plug, if you have one. All alarms should clear to a hard loopback.

0 Kudos
madams
New Contributor

Re: atlas 830 E1 connection to AudioCodes Mediant 3000

Jump to solution

Hi Patrick,

It was the cabling. Thanks for your help...