Summary:ASTERISK-13761: Hangup cause 18 (no user response) is an end user condition and should not be used for protocol timeouts
Reporter:David Woolley (davidw)Labels:
Date Opened:2009-03-17 07:25:54Date Closed:2011-06-07 14:08:02
Versions:Frequency of
Description:We had a requirement for implementing failovers to alternative CCMs when talking to Cisco and therefore decided we needed to determine which failures implied a failure on a trunk that had failed since the last qualify.  We decided to use ${HANGUPCAUSE} to refine the ${DIALSTATUS} information.  Empirically, we found that we got 18 (no user response) when we tripped a no response to our critical packet for the INVITE on the trunk.

However, looking at the description of this condition, and, in particular looking at the definition used in <http://www.quintum.com/support/xplatform/network/Q931_Disconnect_Cause_Code_List.pdf>, it seems to me that this cause code is intended for end user no answer oonditions, particularly where it is either known that the the user wasn't made aware of the call, or that it is not absolutely certain that they were made aware.  In particular, it looks like this is the default choice for end use no answer, with 19 only being used if it was certain they were alerted.

It seems to me that 102 (recovery on timer expired) is probably more appropriate.


There has been no obvious change in this area of the code in
Comments:By: Tilghman Lesher (tilghman) 2009-07-16 12:09:34

As in the other issue, we have no way of distinguishing trunks from actual peers in the current code, so I am suspending this issue until such change is made that we can.