My 2 cents... When SIP message is parsed, the multipart body could be parsed. Invite module could find and process just the SDP part and the application could parse the remaining parts. On the reverse side, there should be a mechanism to originate SIP messages with multiple body parts. Ramesh ----- Original Message ---- From: Ruud Klaver <ruud@ag-projects.com> To: pjsip list <pjsip@lists.pjsip.org> Sent: Wednesday, September 10, 2008 10:10:10 AM Subject: [pjsip] SDP in multipart MIME in invite module Hi, I would like to address an issue that was discussed before on this  mailinglist. Within the context of conferencing we will need to send  and receive content other than SDP as body in INVITE messages, see  e.g. http://tools.ietf.org/html/draft-ietf-sip-uri-list-conferencing-02#section-6 . From the previous discussion and the code I have seen that the SDP  negotiation and invite modules are very tightly coupled and very  difficult to separate. I am inclined to believe it would probably be  easier to implement multipart MIME decoding in the invite module and  have it look for SDP nested in that. In this way we could use PJSIP to  transport other content along with the SDP in the body of INVITEs,  without separating the invite and SDP negotation modules too much. My questions are, is this correct and what would be the best approach  to do this? Are there more people interested in this? Ruud Klaver AG Projects _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org