[asterisk-bugs] [Asterisk 0011750]: Asterisk ignores SDP when multiple Content-Type headers are present

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11750 
====================================================================== 
Reported By:                tasker
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11750
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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-12-2008 12:02 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-12-08 12:02  
---------------------------------------------------------------------- 
Could this be the issue?

----------------------
Content-Type: multipart/mixed; boundary=Telica-boundary

--Telica-boundary
Content-Type: application/sdp
Content-Disposition: session; handling=required
...
----------------------

The first Content-type defines a section called Telica-boundary. Within
that content is where SDP is defined. 

Would Asterisk see that as being manufacturer specific data and ignoring
everything within Telica-boundary? It would seem to be correct behavior
according to the RFC, if I am understaning it correctly, thus it isn't a
bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-12-08 12:02  tasker         Note Added: 0076812                          
======================================================================