[SIPForum-discussion] SOS:the basic rules of SIP-T

Thu Jun 12 09:21:10 UTC 2008

Hi Clifford and all, 

there is a SIP-T sample from RFC3204 as followed,

My question is Which character is allowed at the four lines with  number marked respectively, the CRLF sequence or CR or LF ? 

INVITE sip:14084955072 at sc1.nortelnetworks.com SIP/2.0

Via: SIP/2.0/UDP sc10.nortelnetworks.com

From: sip:14085655675 at sc10.nortelnetworks.com

To: sip:14084955072 at sc1.nortelnetworks.com

Call-ID: 1231999021712095500999 at sc12.nortelnetworks.com

CSeq: 1234 INVITE

Contact: <sip:14085655675 at sc10.nortelnetworks.com>

Content-Length: 358

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

MIME-Version: 1.0

--unique-boundary-1

Content-Type: application/SDP; charset=ISO-10646

①？

v=0

o=audet 2890844526 2890842807 5 IN IP4 134.177.64.4

s=SDP seminar

c=IN IP4 MG141.nortelnetworks.com

t= 2873397496 2873404696

m=audio 9092 RTP/AVP 0 3 4

②？

--unique-boundary-1

Content-type:application/QSIG; version=iso

Content-disposition: session; handling=required;  ③？

08 02 55 55 05 04 02 90 90 18 03 a1 83 01

70 0a 89 31 34 30 38 34 39 35 35 30 37 32

④？

--unique-boundary-1--

Well, My 2 cents is all of them (CRLF/LF/CR) are acceptable, as the end-of-line of SIP message could be depended on the OS(such as the DOS chooses CRLF, the Linux uses LF) But I am not sure~~ I can’t find out any RFC(include RFC3372 and RFC3204) elaborating SIP-T’s format ,espacially with a SDP and ISUP Msg bodys in this way.

Any response is a helpful

Regards

Nora

 --unique

 Via: SIP/

---------------------------------
 雅虎邮箱，您的终生邮箱！
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080612/1845941a/attachment-0014.html>