AudioCodes Mediant 1000 and CS1000M - Interfacing Issues with PRI

[AJ9U]

We are beginning a trial of SIP trunking. We have an MPLS circuit coming in from the carrier, connecting to an Acme Packet SBC, and then connecting to an Audiocodes Mediant 1000 gateway. The gateway connects to the CS1000M MG release 4.0 system via ISDN PRI. We cannot get the PRI to stay up for more than 30 seconds to a minute. We have tried changing every parameter we can think of on the PBX and gateway. We have connected the PBX PRI to a T-Berd to do simulation, and it works perfectly – but it won’t work when connected to the Mediant.

We are not sure, but we suspect it might be a clocking issue. Normally the DDP looks for clocking from the carrier, but in this case the Mediant looks to the PBX for clocking. But we have set the Mediant as network and CS as user, and vice versa, and it does not seem to matter - we can’t keep the span up.

One of the reasons we chose that gateway was because it has been used many times with CS1000s, and it is a DevConnect partner. So we know it has to be possible. Have any of you been successful getting them to work together?

 

[nortelvet]

I have seen a few systems connected to Mediant product, provided they are a DevConnect partner and achieved this via the T1/E1 connectivity then both Avaya and Mediant should have application notes describing the configuration requirements of each device. Your Mediant distributor should be able to source these.

That said, it sounds as though this is a clocking issue, are there messages output to the TTY from the time the loop in enabled until it drops 30-60 seconds later? I assume you have other T1/E1 services in the PABX, therefore, your system will be configured to track from one of those services, therefore, you need to configure the Mediant to track its clock sync from the PABX.