[asterisk-bugs] [Asterisk 0017802]: Direct Media mode - Wrong Coder Selected

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Aug 5 13:50:33 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17802 
====================================================================== 
Reported By:                ShayS
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17802
Category:                   Channels/chan_sip/CodecHandling
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0-beta2 
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-08-05 09:13 CDT
Last Modified:              2010-08-05 13:50 CDT
====================================================================== 
Summary:                    Direct Media mode - Wrong Coder Selected
Description: 
In direct media mode, when peers settings have different codec setting -
each part of the call using different codec.
IPP 6000 codec: alaw, ulaw
IPP 4709 codec: g722, alaw, ulaw

IPP 4709 calls 6000.
Before the PBX send 200OK to caller it doesn't join capabilities between
the peers.

IPP 6000 is using alaw
IPP 4709 is using g722

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

---------------------------------------------------------------------- 
 (0125583) pabelanger (manager) - 2010-08-05 13:50
 https://issues.asterisk.org/view.php?id=17802#c125583 
---------------------------------------------------------------------- 
Please upload a debug log rather then a note, helps to keep the issue
clean.
---
We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs
from an Asterisk machine for the purpose of helping bug marshals
troubleshoot an issue:

http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt


Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-05 13:50 pabelanger     Note Added: 0125583                          
======================================================================




More information about the asterisk-bugs mailing list