[asterisk-bugs] [Asterisk 0013569]: Asterisk sending the wrong codec on re-invite.
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Dec 16 18:53:56 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13569
======================================================================
Reported By: bkw918
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13569
Category: Channels/chan_sip/CodecHandling
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.0-rc6
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-09-26 17:48 CDT
Last Modified: 2008-12-16 18:53 CST
======================================================================
Summary: Asterisk sending the wrong codec on re-invite.
Description:
FreeSWITCH sends invite out to tf.voipmich.com with PCMU, PCMA, GSM. The
call is answered and setup using GSM since its listed first in the Answer
we receive from Asterisk. A re-invite promptly follows offering
GSM,PCMU,PCMA to which we 200 OK with ONLY GSM in the SDP in our 200 OK.
Promptly there after Asterisk starts sending PCMU packets. The re-invite
is considered a new Session Offer Answer and Asterisk ignores the Answer
and sends a media format not in the new Answer.
Asterisk PBX SVN-branch-1.6.0-r140976-/trunk is what I can see in the SDP
from John's equipment. He has disabled re-invites pending a fix for this.
======================================================================
----------------------------------------------------------------------
(0096510) mnicholson (administrator) - 2008-12-16 18:53
http://bugs.digium.com/view.php?id=13569#c96510
----------------------------------------------------------------------
I examined your trace and can confirm that the trace displays the behavior
you describe. I will take a look at this issue.
Issue History
Date Modified Username Field Change
======================================================================
2008-12-16 18:53 mnicholson Note Added: 0096510
======================================================================
More information about the asterisk-bugs
mailing list