[asterisk-bugs] [Asterisk 0018476]: Codec negotiation algorithm

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18476 
====================================================================== 
Reported By:                manzo_zeti
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18476
Category:                   Codecs/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.15 
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-12-15 07:19 CST
Last Modified:              2010-12-15 11:33 CST
====================================================================== 
Summary:                    Codec negotiation algorithm
Description: 
According to the provided documentation ( sip.conf ), when Asterisk is
placing a call the CODEC used will be the first CODEC in the allowed
CODEC's that the caller indicates that it supports.

So if, for instance, we have the following setup:

[caller]
disallow=all
allow=g729
allow=alaw

[called]
disallow=all
allow=alaw
allow=gsm

RTP stream from caller to called would be transcoded from $WATHEVER to
G.729.
Such behavior is sub-optimal when $CUSTOMERS devices come in the scene
since 
we can't be sure that our configured codec preferences are the same as
theirs.

I think Asterisk should place call using the first CODEC sent by the
caller in the INVITE message that [caller] indicates that it supports.

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

---------------------------------------------------------------------- 
 (0129615) dzajro (reporter) - 2010-12-15 11:33
 https://issues.asterisk.org/view.php?id=18476#c129615 
---------------------------------------------------------------------- 
There are many scenarios benefiting from current mechanism. But maybe it
could be configuration related. Something like "honor host preferences" vs.
"honor my preferences". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-15 11:33 dzajro         Note Added: 0129615                          
======================================================================