penelope

I have one system out of 12 that forwarded off-net calls got an AT&T recording of "your call did not go through..." It would work calling the forwarded extension internally, calling the auto-attendant, and calling reception and getting transfered to the extension but NOT on inbound DID calls over an ISDN. It didn't matter if the extension was forwarded to a local number and went out the COs or to a long-distance number and went out the ISDN.

All the usual suspects were checked out and MANY MANY hours of testing with Avaya and AT&T. I did find that when I created a dummy extension real quick to test with (and so it was bare bones with no coverage path) that it DID work without coverage to vmail. That led to another tangent about it being a problem with answer supervision, etc.

AT&T trace showed that their 4E was receiving two progress messages without ever receiving an answer message. Their error codes meant "message not compatible with call state." I had already brought that up to Avaya that it seemed that once the call was answered, either by AA or the console, and then transfered, it worked.

Avaya finally found a setting that corrected it. They changed the DS1 Interworking Message to ALERTing instead of PROGress.

My only question now is that every other system is set to PROGress. Yeah, why question it if it works? I just don't want it coming back to bite me because it screws up something else!

Penelope