ATT Alternate Destination Routing

[deefish]

We are struggling with trying to use ATT ADR with our Avaya switch.

Call comes in from originator who has set up ADR using RouteIT. The vector just has one command: busy.

ATT monitored the test calls and said we are sending the right Cause Code of 17 [user busy], but the message they are receiving is a DISCONNECT and they are expecting a RELEASE.


If we change to RNA, it works fine, the call goes back to originator, and then send the call to another center. But the time it takes to get the call to the other destination is unacceptable.

Anybody have this working that can provide some insight?

 

[BIS]

Try to set the vector to 'disconnect'.

 

[deefish]

We did...then they don't get the proper cause code of 17 that ATT expects to see.

I wonder if it has something to do with 'answer supervision'?