Avaya tie trunk to NEC - Help Please! 2

[simreal]

I posted this in the NEC forum as well.

Trying to setup a tie trunk between a S8700 to an NEC 2400 NEAX.

We thought we had it. We had an ISDN trunk between the NEC and the Avaya.

We can get calls from the NEC to the Avaya but we cant get calls from the Avaya to th NEC. The calls hit the trunk but we get "denial even 1195 circ/channel unavail".

Called Avaya and they sugguested we set it up as a TIE trunk with wink/wink instead of a standard isdn-pri trunk. We tried it and all of the b-channels go into inservice-active. We cant get calls through either way now.

Any advice? It's been a few years since I had to troubleshoot a T1 so I'm sure I'm missing something here.

 

[koglass]

This may help. I would also Status the Trunk Group in the avaya switch and see what it is doing. Out of Service, busied out, Out of service Far End, etc.

Cause Value 44
[0x2C/0xAC] -
Requested circuit/channel not available
The call was not completed because the circuit/channel requested for use in the SETUP
message was not available, and the call could not be negotiated to another channel either
because no other channel was available, or negotiation is not supported or was not wanted for
this call.
This Cause Value is generated when a glare condition is occurring and B-channel negotiation is
not supported.
Communication Manager generates this Cause Value when:
? It is the NETWORK side of the interface and a glare condition is occurring on the
requested B-channel.
? The B-channel requested in the incoming SETUP message is not in the correct
maintenance state to handle a call (for example, it is busied out or undergoing testing).

 

[simreal]

The channels in the trunk show in service active. The first few seconds after releasing the trunk into service they will show connected to ports on the IPSI or occasionally ports on a ds1 board in another port network.

 

[PBXadmin]

If you had the trunks working in one direction when they were programmed as ISDN, I would put the configuration back in that was working and then troubleshoot the problem of one-way connectivity.

The last part of the documentation for cause value 44 states that you should change the Channel Negotiation field to preferred if exclusive does not work. You may want to try this.

Let us know how you make out.

 

[simreal]

Thats what we ended up doing. We have it working both directions now. The NEC wasn't administered to translate more than 5 digits so it was denying the calls.

Everything is working properly now.

Thanks for the input.