[asterisk-bugs] [Asterisk 0013569]: Asterisk sending the wrong codec on re-invite.
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 14 17:11:42 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13569
======================================================================
Reported By: bkw918
Assigned To: mnicholson
======================================================================
Project: Asterisk
Issue ID: 13569
Category: Channels/chan_sip/CodecHandling
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.0-rc6
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-01-14 17:11 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.
======================================================================
----------------------------------------------------------------------
(0097837) blitzrage (administrator) - 2009-01-14 17:11
http://bugs.digium.com/view.php?id=13569#c97837
----------------------------------------------------------------------
Uhhhh... that should actually be the other way around should it not?
Shouldn't they be the one providing the information?
Issue History
Date Modified Username Field Change
======================================================================
2009-01-14 17:11 blitzrage Note Added: 0097837
======================================================================
More information about the asterisk-bugs
mailing list