[asterisk-bugs] [Asterisk 0011624]: ChanIsAvail shouldn't generate warnings

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11624 
====================================================================== 
Reported By:                pj
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   11624
Category:                   Applications/app_chanisavail
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 93763 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             12-22-2007 13:33 CST
Last Modified:              12-27-2007 10:56 CST
====================================================================== 
Summary:                    ChanIsAvail shouldn't generate warnings
Description: 
I'm using ChanIsAvail() before dial() to determine what channel is
available to place call. It works, but if sip or iax peer is unavalable or
offline, ChanIsAvail generates annoying warnings to console and asterisk
messages. 
I think this should be put into debug level.

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

---------------------------------------------------------------------- 
 file - 12-27-07 10:56  
---------------------------------------------------------------------- 
's' queries the devicestate core see to whether the device is in use or not
otherwise chanisavail actually tries to place an outgoing call to the
device. What the channel driver does during that time is not under the
control of chanisavail. The only way that it could work is to expand the
API call that requests an outgoing call to a device to say whether to
display warning/error information or not... and I don't want to go down
that path. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-27-07 10:56  file           Status                   assigned => resolved
12-27-07 10:56  file           Resolution               reopened => won't fix
12-27-07 10:56  file           Note Added: 0076038                          
======================================================================