[asterisk-bugs] [Asterisk 0018868]: [patch] dont get early media on outgoing calls

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18868 
====================================================================== 
Reported By:                isrl
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18868
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-3171 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-22 08:30 CST
Last Modified:              2011-03-07 11:50 CST
====================================================================== 
Summary:                    [patch] dont get early media on outgoing calls
Description: 
on most outgoing calls i dont get early media 
card is a sangoma a101c 
libpri tried 1.14.11.5 and 1.4.12
dahdi 2.4.0


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

---------------------------------------------------------------------- 
 (0132700) cmaj (reporter) - 2011-03-07 11:50
 https://issues.asterisk.org/view.php?id=18868#c132700 
---------------------------------------------------------------------- 
Patch works for me. Pretty simple and doesn't seem to cause any harm.

And 8 could mean a pattern, as you wrote in your note on 2/22. So
PRI_PROG_INBAND_AVAILABLE is technically not correct for that, either.
Should be PRI_PROG_INBAND_OR_PATTERN_AVAILABLE.

These are larger issues, for sure. But I got bit on this during a 1.6 to
1.8 upgrade and consider it a major bug that can be fixed with just one
line of extra code. So why the heck not?

Also, why would libpri assign the state by way of a bitmask'ed OR for
progressmask if you'll only ever use one value?

I can provide you plenty of DIDs where this was breaking under 1.8 -
people just hearing dead air when they call them, after it worked fine on
1.6. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-07 11:50 cmaj           Note Added: 0132700                          
======================================================================