[asterisk-bugs] [Asterisk 0017581]: AVAILSTATUS set to 20

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17581 
====================================================================== 
Reported By:                philipp2
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17581
Category:                   Applications/app_chanisavail
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.33 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-07-02 08:22 CDT
Last Modified:              2010-07-03 12:33 CDT
====================================================================== 
Summary:                    AVAILSTATUS set to 20
Description: 
For a SIP peer (Realtime, usually not registered (but can be) ChanIsAvail
can sometimes return "20" in AVAILSTATUS. Correct values for AVAILSTATUS
are, however, all < 10.

In the case of AVAILSTATUS=20 both AVAILCHAN and AVAILORIGCHAN are always
empty.
Hostnames can either be FQDN or IP.

Has also happend on 1.4.29 and 1.4.31.

====================================================================== 

---------------------------------------------------------------------- 
 (0124205) JJCinAZ (reporter) - 2010-07-03 12:33
 https://issues.asterisk.org/view.php?id=17581#c124205 
---------------------------------------------------------------------- 
The application is actually documented to return "both a device state and a
cause code".  In this case, the 20 is a cause code.  This behaviour is
probably bad since cause codes and device states overlap in name-space
(i.e. they both have values from 0 through 9 which collide).  

In this example, the 20 = AST_CAUSE_SUBSCRIBER_ABSENT, but if the app
returned a value of 6, that could mean AST_CAUSE_CHANNEL_UNACCEPTABLE or
AST_DEVICE_RINGING.

Changing this may break dial plans dependant on this behavior, but it IMHO
it should get changed to return the CAUSE in a different variable. 
Whomever added the CAUSE code returned could comment more on the desired
behavior. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-03 12:33 JJCinAZ        Note Added: 0124205                          
======================================================================