Also. do refer RFC 3459.
That should give u more pointers and details towards the same.
Rama
Prashant Prabhu <[EMAIL PROTECTED]> wrote:
hi,Which document should be referred for information on the Content-Type being "multipart/signed" ?RFC 3261, as such, does not define any parameter "boundary" in Content-Type.thanks,prashant_______________________________________________----- Original Message -----From: Ramachandran IyerSent: Wednesday, June 02, 2004 11:34 AMSubject: RE: [Sip-implementors] multi body boundary in SIPSome more info on the same...Below is an example of a SIP message having multi-part bodies. Some of the points to note here are..1> In the main msg Content Type is specified as 'multipart/signed' which i guess is used for embedded SIP msg's .. i believe 'multipart/mixed' should also do fine. This indicates there are multiple bodies in the SIP msg.2> Content Length in the INVITE specifies the total length of both bodies (lenght of body 1 + length of body 2)3> Content Type also has a 'boundary' field which specifies how the bodies will have a boundary mark .. in the below example the boundary being ' boundary42'4> Also each body will have a '--' {double dash} along with the boundary field param to indicate the beginning of the body. In the belwo case the first body itself happens to be a sip message and having its own sdp body inside.5> The end of the last body is indicated by a post '-' along with the boundary field and the 2 pre-dash.INVITE sip:[EMAIL PROTECTED] SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds8
To: Bob <sip:[EMAIL PROTECTED]>
From: Alice <sip:[EMAIL PROTECTED]>;tag=1928301774
Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Max-Forwards: 70
Date: Thu, 21 Feb 2002 13:02:03 GMT
Contact: <sip:[EMAIL PROTECTED]>
Content-Type: multipart/signed;
protocol="application/pkcs7-signature";
micalg=sha1; boundary=boundary42
Content-Length: 568
--boundary42
Content-Type: message/sip
INVITE sip:[EMAIL PROTECTED] SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds8
To: Bob <[EMAIL PROTECTED]>
From: Alice <[EMAIL PROTECTED]>;tag=1928301774
Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Max-Forwards: 70
Date: Thu, 21 Feb 2002 13:02:03 GMT
Contact: <sip:[EMAIL PROTECTED]>
Content-Type: application/sdp
Content-Length: 147
v=0
o=UserA 2890844526 2890844526 IN IP4 here.com
s=Session SDP
c=IN IP4 pc33.atlanta.com
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
--boundary42
Content-Type: application/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=smime.p7s;
handling=required
ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfHfYT6
4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbB9HGTrfvbnj
n8HHGTrfvhJhjH776tbB9HG4VQbnj7567GhIGfHfYT6ghyHhHUujpfyF4
7GhIGfHfYT64VQbnj756
--boundary42-
Kaitki Agarwal <[EMAIL PROTECTED]> wrote:Yes. It always starts with two dashes. You should refer to RFC 3204 for more information on this.-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Romel Khan
Sent: Tuesday, June 01, 2004 11:57 AM
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] multi body boundary in SIPDoes boundary always start with two dashes?Eg: --ANSI-ISUP-boundary
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
