[asterisk-bugs] [Asterisk 0009077]: Playback(<file>|noanswer) and in-band info are not working with chan_skinny

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9077 
====================================================================== 
Reported By:                pj
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   9077
Category:                   Channels/chan_skinny
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 53885 
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             02-15-2007 13:08 CST
Last Modified:              08-03-2007 16:47 CDT
====================================================================== 
Summary:                    Playback(<file>|noanswer) and in-band info are not
working with chan_skinny
Description: 
tried to playback with noanswer option, it works with chan_sip or chan_iax,
but not with chan_skinny, also other inband info messages from telco are
not possible with chan_skinny.
eg.: when calling to unavailable gsm phone and telco operator says "person
you are calling isn't available" chan_skinny plays normal ringing tone,
chan_sip and chan_iax plays this in-band messages fine.
tested with ci$co 7920.
====================================================================== 

---------------------------------------------------------------------- 
 DEA - 08-03-07 16:47  
---------------------------------------------------------------------- 
Oddly enough PJ's logs showed that it did get into the AST_CONTROL_PROGRESS
case even with the !sub->outgoing

So while I agree the test is pointless and should be removed, the log
points
to the possibility that that variable is mis-used/mis-set elsewhere in the
code. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-03-07 16:47  DEA            Note Added: 0068408                          
======================================================================