View Single Post
  #3  
Old 05-26-2010, 04:52 PM
rogerg's Avatar
rogerg rogerg is offline
Brainiac
 
Join Date: Jan 2010
Location: Houston, Tx
Posts: 51
rogerg has 10 reputation points
Default

The issue the original poster is asking about is regarding an AVAYA configured for ISDN PRI from a CO providing ISDN NI2 / DMS100.

The issue only occurs when a user dials an at&t mobile phone and the called user disconnects. All other calls are completed normal.

If a user calls other than an at&t mobile phone and the called party disconnects, the list trace shows a cause-code of 16 (Normal Call Clearing).

If a user calls an at&t mobile phone and the called party disconnects, the list trace shows a cause-code 31 (Normal, Unspecified). The local ISDN provider also sees at&t sending the cause-code 31. The local ISDN provider is simply passing the code to the AVAYA.

Is there away to have CM map cause-code 31 to a normal disconnect, or is there another way to allow CM to terminate the call instead of sending busy-tone to the AVAYA handset?
__________________
Gary Rogerson
AVAYA ACE
Reply With Quote