[OpenSIPS-Devel] [ opensips-Bugs-2993623 ] Multipart/mixed messages with textops and mediaproxy

SourceForge.net noreply at sourceforge.net
Thu Nov 8 19:46:35 CET 2012


Bugs item #2993623, was opened at 2010-04-28 07:36
Message generated for change (Comment added) made by denodaeus
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2993623&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: 1.6.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jim Fitzgerald (agelmar)
Assigned to: Dan (dan_pascu)
Summary: Multipart/mixed messages with textops and mediaproxy

Initial Comment:
I have a server sending INVITE messages with a multipart/mixed body. There are 2 misbehaviours I had to correct because of a special constellation:
the content-Type header of my server looks like this:

> Content-Type: multipart/mixed;boundary=unique-boundary-1

saying that the parsing string is "unique-boundary-1". In the textops.c the string is hardcoded and checks for "-Boundary". So if I use the filter_body("application/sdp") function it fails. So Textops should read the delimiter string from Content-Type header dynamically. The hardcoded delimiter is in textops.c line 908.

Filtering works after correcting textops.c, but still mediaproxy module has a problem. After calling filter_body() I will route the call over mediaproxy, so I call use_media_proxy() from mediaproxy.c. But this function works with the uncorrected INVITE pakage again. So if it searches application/sdp it only finds multipart/mixed and no mediaproxy channel is created. Best solution would be to get mediaproxy to work with the previously corrected pakage. I am using a workaround now, replacing "status = get_sdp_message(msg, &sdp);" on line 1445 in mediaproxy.c with "status = 1;". 

regards


----------------------------------------------------------------------

Comment By: Robert Smith (denodaeus)
Date: 2012-11-08 10:46

Message:
I'm actually encountering this now with a callmanager setup using SIP-T to
communicate over, and I want to get rid of the mixed multipart content and
retain the sdp.

In the SDP body, we have:
Content-Type:
multipart/mixed;boundary=uniqueBoundary#015#012Content-Length:
478#015#012#015#012--uniqueBoundary#015#01

But it's hard coded to match on "--Boundary" only.

This bug is quite old, but wanting to bring up that we'd also like to see
the ability to honor the boundary= param here to specify a dynamic
multipart boundary token.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2993623&group_id=232389



More information about the Devel mailing list