[asterisk-bugs] [Asterisk 0013569]: Asterisk sending the wrong codec on re-invite.
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri May 15 07:18:36 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=13569
======================================================================
Reported By: bkw918
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 13569
Category: Channels/chan_sip/CodecHandling
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.0-beta1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-09-26 17:48 CDT
Last Modified: 2009-05-15 07:18 CDT
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0104810) file (administrator) - 2009-05-15 07:18
https://issues.asterisk.org/view.php?id=13569#c104810
----------------------------------------------------------------------
bkw918: I disagree on that last note. We *do* care and this issue has been
kept open for awhile to try to bring it to a resolution. The entire problem
though was that we did not know how the Asterisk machines were actually
configured, so in order to reproduce this I guess we'll just have to guess
on everything and hope for the best.
After re-reading the notes I agree with Matt's analysis and will work with
dvossel on this. I also think we will be able to recreate this using a sipp
scenario file.
Issue History
Date Modified Username Field Change
======================================================================
2009-05-15 07:18 file Note Added: 0104810
======================================================================
More information about the asterisk-bugs
mailing list