[asterisk-bugs] [Asterisk 0011750]: Asterisk ignores SDP when multiple Content-Type headers are present
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jan 15 08:43:40 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11750
======================================================================
Reported By: tasker
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 11750
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.4.17
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 01-12-2008 09:56 CST
Last Modified: 01-15-2008 08:43 CST
======================================================================
Summary: Asterisk ignores SDP when multiple Content-Type
headers are present
Description:
Asterisk ignores the SDP information when multiple Content-Type headers are
defined. Specifically, it seems to happen when SDP is not the first header
in a multiple Content-Type situation. The call is still handled and results
in one-way audio (inbound RTP only).
======================================================================
----------------------------------------------------------------------
tasker - 01-15-08 08:43
----------------------------------------------------------------------
The above code solves the issue. It was just a matter of incrementing the
'search' pointer by 1 more when "; boundary" was present, since it contains
11 characters instead of 10 due to the space between the semi-colon and
"boundary".
Issue History
Date Modified Username Field Change
======================================================================
01-15-08 08:43 tasker Note Added: 0076972
======================================================================
More information about the asterisk-bugs
mailing list