1INVITE sip:vivekg@chair.dnrc.bell-labs.com SIP/2.0
2TO :
3 sip:vivekg@chair.dnrc.bell-labs.com ;   tag    = 1a1b1f1H33n
4From   : "J Rosenberg \\\"" <sip:jdrosen@lucent.com>
5  ;
6  tag = 98asjd8
7CaLl-Id
8 : 0ha0isndaksdj@10.1.1.1
9cseq: 8
10  INVITE
11Via  : SIP  /   2.0
12 /UDP
13    135.180.130.133
14Subject :
15NewFangledHeader:   newfangled value
16 more newfangled value
17Content-Type: application/sdp
18v:  SIP  / 2.0  / TCP     12.3.4.5   ;
19  branch  =   9ikj8  ,
20 SIP  /    2.0   / UDP  1.2.3.4   ; hidden
21m:"Quoted string \"\"" <sip:jdrosen@bell-labs.com> ; newparam = newvalue ;
22  secondparam = secondvalue  ; q = 0.33
23
24v=0
25o=mhandley 29739 7272939 IN IP4 126.5.4.3
26s=
27c=IN IP4 135.180.130.88
28m=audio 49210 RTP/AVP 0 12
29m=video 3227 RTP/AVP 31
30a=rtpmap:31 LPC/8000
31
32|This message tests support for Proxy-Require and Require
33INVITE sip:user@company.com SIP/2.0
34To: sip:j_user@company.com
35From: sip:caller@university.edu
36Call-ID: 0ha0isndaksdj@10.1.1.1
37Require: newfeature1, newfeature2
38Proxy-Require: newfeature3, newfeature4
39CSeq: 8 INVITE
40Via: SIP/2.0/UDP 135.180.130.133
41
42|This message contains unknown schemes in the Request URI, To, From and Contact headers.
43INVITE name:John_Smith SIP/2.0
44To: isbn:2983792873
45From: http://www.cs.columbia.edu
46Call-ID: 0ha0isndaksdj@10.1.2.3
47CSeq: 8 INVITE
48Via: SIP/2.0/UDP 135.180.130.133
49Content-Type: application/sdp
50Contact: Joe Bob Briggs <urn:ipaddr:122.1.2.3>
51
52v=0
53o=mhandley 29739 7272939 IN IP4 126.5.4.3
54c=IN IP4 135.180.130.88
55m=audio 49210 RTP/AVP 0 12
56m=video 3227 RTP/AVP 31
57a=rtpmap:31 LPC/8000
58
59|This message is a registration request with an expiration year of 2040
60REGISTER sip:company.com SIP/2.0
61To: sip:user@company.com
62From: sip:user@company.com
63Contact: sip:user@host.company.com
64Call-ID: 0ha0isndaksdj@10.0.0.1
65CSeq: 8 REGISTER
66Via: SIP/2.0/UDP 135.180.130.133
67Expires: Thu, 01 Dec 2040 16:00:00 GMT
68
69|It is a request that includes an Accept header without SDP.
70INVITE sip:user@company.com SIP/2.0
71To: sip:j_user@company.com
72From: sip:caller@university.edu
73Call-ID: 0ha0isndaksdj@10.0.0.1
74Accept: text/newformat
75CSeq: 8 INVITE
76Via: SIP/2.0/UDP 135.180.130.133
77Content-Type: application/sdp
78Content-Length: 148
79
80v=0
81o=mhandley 29739 7272939 IN IP4 126.5.4.3
82c=IN IP4 135.180.130.88
83m=audio 49210 RTP/AVP 0 12
84m=video 3227 RTP/AVP 31
85a=rtpmap:31 LPC/8000
86
87|
88INVITE sip:user@comapny.com SIP/2.0
89To: sip:j.user@company.com
90From: sip:caller@university.edu
91Call-ID: 0ha0isndaksdj@10.0.0.1
92CSeq: 8 INVITE
93Via: SIP/2.0/UDP 135.180.130.133
94Content-Type: application/newformat
95Content-Length: 42
96
97<audio>
98 <pcmu port="443"/>
99</audio>
100
101|This request message contains a new method, NEWMETHOD
102NEWMETHOD sip:user@comapny.com SIP/2.0
103To: sip:j.user@company.com
104From: sip:caller@university.edu
105Call-ID: 0ha0isndaksdj@10.0.0.1
106CSeq: 8 NEWMETHOD
107Via: SIP/2.0/UDP 135.180.130.133
108Content-Type: application/sdp
109Content-Length: 148
110
111v=0
112o=mhandley 29739 7272939 IN IP4 126.5.4.3
113c=IN IP4 135.180.130.88
114m=audio 49210 RTP/AVP 0 12
115m=video 3227 RTP/AVP 31
116a=rtpmap:31 LPC/8000
117
118|This message is nearly identical to test7. but cseq does not match!
119NEWMETHOD sip:user@comapny.com SIP/2.0
120To: sip:j.user@company.com
121From: sip:caller@university.edu
122Call-ID: 0ha0isndaksdj@10.0.1.1
123CSeq: 8 INVITE
124Via: SIP/2.0/UDP 135.180.130.133
125Content-Type: application/sdp
126Content-Length: 148
127
128v=0
129o=mhandley 29739 7272939 IN IP4 126.5.4.3
130c=IN IP4 135.180.130.88
131m=audio 49210 RTP/AVP 0 12
132m=video 3227 RTP/AVP 31
133a=rtpmap:31 LPC/8000
134
135|This message is a REGISTER request with an unknown authorization scheme
136REGISTER sip:company.com SIP/2.0
137To: sip:j.user@company.com
138From: sip:j.user@company.com
139Call-ID: 0ha0isndaksdj@10.0.1.1
140CSeq: 8 REGISTER
141Via: SIP/2.0/UDP 135.180.130.133
142Authorization: Super-PGP ajsohdaosdh0asyhdaind08yasdknasd09asidhas0d8
143
144|Content-length is wrong (and Multiple SIP requests per UDP packet are no longer allowed.)
145REGISTER sip:company.com SIP/2.0
146To: sip:j.user@company.com
147From: sip:j.user@company.com
148Call-ID: 0ha0isndaksdj@10.0.2.2
149Contact: sip:j.user@host.company.com
150CSeq: 8 REGISTER
151Via: SIP/2.0/UDP 135.180.130.133
152Content-Length: 0
153
154
155
156INVITE sip:joe@company.com SIP/3.0
157To: sip:joe@company.com
158From: sip:caller@university.edu
159Call-ID: 0ha0isnda977644900765@10.0.0.1
160CSeq: 8 INVITE
161Via: SIP/2.0/UDP 135.180.130.133
162Content-Type: application/sdp
163
164v=0
165o=mhandley 29739 7272939 IN IP4 126.5.4.3
166c=IN IP4 135.180.130.88
167m=audio 49210 RTP/AVP 0 12
168m=video 3227 RTP/AVP 31
169a=rtpmap:31 LPC/8000
170
171|The message contains a request with an extra Call-ID and To field
172INVITE sip:user@company.com SIP/2.0
173CSeq: 0 INVITE
174Via: SIP/2.0/UDP 135.180.130.133
175Content-Type: application/sdp
176
177v=0
178o=mhandley 29739 7272939 IN IP4 126.5.4.3
179c=IN IP4 135.180.130.88
180m=audio 49210 RTP/AVP 0 12
181m=video 3227 RTP/AVP 31
182a=rtpmap:31 LPC/8000
183
184| extra callid: should respond with an error!
185INVITE sip:user@company.com SIP/2.0
186Via: SIP/2.0/UDP 135.180.130.133
187CSeq: 0 INVITE
188Call-ID: 98asdh@10.1.1.1
189Call-ID: 98asdh@10.1.1.2
190From: sip:caller@university.edu
191From: sip:caller@organization.org
192To: sip:user@company.com
193Content-Type: application/sdp
194
195v=0
196o=mhandley 29739 7272939 IN IP4 126.5.4.3
197c=IN IP4 135.180.130.88
198m=audio 49210 RTP/AVP 0 12
199m=video 3227 RTP/AVP 31
200a=rtpmap:31 LPC/8000
201
202|This message contains an Expires header which has illegal values
203INVITE sip:user@company.com SIP/2.0
204Via: SIP/2.0/UDP 135.180.130.133
205CSeq: 0 INVITE
206Call-ID: 98asdh@10.1.1.2
207Expires: Thu, 44 Dec 19999 16:00:00 EDT
208From: sip:caller@university.edu
209To: sip:user@company.com
210Content-Type: application/sdp
211
212v=0
213o=mhandley 29739 7272939 IN IP4 126.5.4.3
214c=IN IP4 135.180.130.88
215m=audio 49210 RTP/AVP 0 12
216m=video 3227 RTP/AVP 31
217a=rtpmap:31 LPC/8000
218
219|This message is a response with a 2nd Via header of 255.255.255.255
220SIP/2.0 200 OK
221Via: SIP/2.0/UDP 135.180.130.57;branch=0
222Via: SIP/2.0/UDP 255.255.255.255;branch=0
223Call-ID: 0384840201@10.1.1.1
224CSeq: 0 INVITE
225From: sip:user@company.com
226To: sip:user@university.edu;tag=2229
227Content-Type: application/sdp
228
229v=0
230o=mhandley 29739 7272939 IN IP4 126.5.4.3
231c=IN IP4 224.2.17.12/127
232m=audio 49210 RTP/AVP 0 12
233m=video 3227 RTP/AVP 31
234a=rtpmap:31 LPC/8000
235
236|This is a request with the Via and Contact headers incorrect
237INVITE sip:user@company.com SIP/2.0
238To: sip:j.user@company.com
239From: sip:caller@university.edu
240Call-ID: 0ha0isndaksdj@10.0.0.1
241CSeq: 8 INVITE
242Via: SIP/2.0/UDP 135.180.130.133;;,;
243Contact: "" <> ;,"Joe" <sip:joe@org.org>;;,,;;
244Content-Type: application/sdp
245
246v=0
247o=mhandley 29739 7272939 IN IP4 126.5.4.3
248c=IN IP4 135.180.130.88
249m=audio 49210 RTP/AVP 0 12
250m=video 3227 RTP/AVP 31
251a=rtpmap:31 LPC/8000
252
253|This is a request message with a Content Length that is much larger than the length of the body
254INVITE sip:user@company.com SIP/2.0
255To: sip:j.user@company.com
256From: sip:caller@university.edu
257Call-ID: 0ha0isndaksdj@10.0.0.1
258CSeq: 8 INVITE
259Via: SIP/2.0/UDP 135.180.130.133
260Content-Type: application/sdp
261Content-Length: 9999
262
263v=0
264o=mhandley 29739 7272939 IN IP4 126.5.4.3
265c=IN IP4 135.180.130.88
266m=audio 49210 RTP/AVP 0 12
267m=video 3227 RTP/AVP 31
268a=rtpmap:31 LPC/8000
269
270|This is a request message with a negative value for Content-Length
271INVITE sip:user@company.com SIP/2.0
272To: sip:j.user@company.com
273From: sip:caller@university.edu
274Call-ID: 0ha0isndaksdj@10.0.0.1
275CSeq: 8 INVITE
276Via: SIP/2.0/UDP 135.180.130.133
277Content-Type: application/sdp
278Content-Length: -999
279
280v=0
281o=mhandley 29739 7272939 IN IP4 126.5.4.3
282c=IN IP4 135.180.130.88
283m=audio 49210 RTP/AVP 0 12
284m=video 3227 RTP/AVP 31
285a=rtpmap:31 LPC/8000
286
287|This is a request message with garbage after the end of the SDP included in the body.
288INVITE sip:user@company.com SIP/2.0
289To: sip:j.user@company.com
290From: sip:caller@university.edu
291Call-ID: 0ha0isndaksdj@10.0.0.1
292CSeq: 8 INVITE
293Via: SIP/2.0/UDP 135.180.130.133
294Content-Type: application/sdp
295Content-Length: 148
296
297v=0
298o=mhandley 29739 7272939 IN IP4 126.5.4.3
299c=IN IP4 135.180.130.88
300m=audio 49210 RTP/AVP 0 12
301m=video 3227 RTP/AVP 31
302a=rtpmap:31 LPC/8000
303asdpasd08asdsdk:;;asd
304 a0sdjhg8a0''...'';;;;
305
306|This is a request with an unterminated quote in the display name of the To field
307INVITE sip:user@company.com SIP/2.0
308To: "Mr. J. User <sip:j.user@company.com>
309From: sip:caller@university.edu
310Call-ID: 0ha0isndaksdj@10.0.0.1
311CSeq: 8 INVITE
312Via: SIP/2.0/UDP 135.180.130.133
313Content-Type: application/sdp
314Content-Length: 138
315
316v=0
317o=mhandley 29739 7272939 IN IP4 126.5.4.3
318c=IN IP4 135.180.130.88
319m=audio 49210 RTP/AVP 0 12
320m=video 3227 RTP/AVP 31
321a=rtpmap:31 LPC/8000
322
323|This is an INVITE request with a semicolon-separated parameter in the "user" part
324INVITE sip:user;par=u%40h.com@company.com SIP/2.0
325To: sip:j_user@company.com
326From: sip:caller@university.edu
327Call-ID: 0ha0isndaksdj@10.1.1.1
328CSeq: 8 INVITE
329Via: SIP/2.0/UDP 135.180.130.133
330
331|This INVITE is illegal because the Request-URI has been enclosed within in "<>"
332INVITE <sip:user@company.com> SIP/2.0
333To: sip:user@company.com
334From: sip:caller@university.edu
335Call-ID: 1@10.0.0.1
336CSeq: 1 INVITE
337Via: SIP/2.0/UDP 135.180.130.133
338Content-Type: application/sdp
339Content-Length: 178
340
341v=0
342o=mhandley 29739 7272939 IN IP4 126.5.4.3
343s=SIP Call
344t=3149328700 0
345c=IN IP4 135.180.130.88
346m=audio 49210 RTP/AVP 0 12
347m=video 3227 RTP/AVP 31
348a=rtpmap:31 LPC/8000
349
350|This INVITE has illegal LWS within the SIP URL.
351INVITE sip:user@company.com; transport=udp SIP/2.0
352To: sip:user@company.com
353From: sip:caller@university.edu
354Call-ID: 2@10.0.0.1
355CSeq: 1 INVITE
356Via: SIP/2.0/UDP 135.180.130.133
357Content-Type: application/sdp
358Content-Length: 178
359
360v=0
361o=mhandley 29739 7272939 IN IP4 126.5.4.3
362s=SIP Call
363t=3149328700 0
364c=IN IP4 135.180.130.88
365m=audio 49210 RTP/AVP 0 12
366m=video 3227 RTP/AVP 31
367a=rtpmap:31 LPC/8000
368
369|This INVITE has illegal >1 SP between elements of the Request-URI.
370INVITE sip:user@company.com  SIP/2.0
371To: sip:user@company.com
372From: sip:caller@university.edu
373Call-ID: 3@10.0.0.1
374CSeq: 1 INVITE
375Via: SIP/2.0/UDP 135.180.130.133
376Content-Type: application/sdp
377Content-Length: 178
378
379v=0
380o=mhandley 29739 7272939 IN IP4 126.5.4.3
381s=SIP Call
382c=IN IP4 135.180.130.88
383t=3149328700 0
384m=audio 49210 RTP/AVP 0 12
385m=video 3227 RTP/AVP 31
386a=rtpmap:31 LPC/8000
387
388|This INVITE is legal and has a Request-URI with a SIP URL containing escaped characters
389INVITE sip:sip%3Auser%40example.com@company.com;other-param=summit SIP/2.0
390To: sip:user@company.com
391From: sip:caller@university.edu
392Call-ID: 4@10.0.0.1
393CSeq: 1 INVITE
394Via: SIP/2.0/UDP 135.180.130.133
395Content-Type: application/sdp
396Content-Length: 178
397
398v=0
399o=mhandley 29739 7272939 IN IP4 126.5.4.3
400s=SIP Call
401c=IN IP4 135.180.130.88
402t=3149328700 0
403m=audio 49210 RTP/AVP 0 12
404m=video 3227 RTP/AVP 31
405a=rtpmap:31 LPC/8000
406
407|This INVITE is illegal as it the Request-URI contains a SIP URL containing escaped headers
408INVITE sip:user@company.com?Route=%3Csip:sip.example.com%3E SIP/2.0
409To: sip:user@company.com
410From: sip:caller@university.edu
411Call-ID: 5@10.0.0.1
412CSeq: 1 INVITE
413Via: SIP/2.0/UDP 135.180.130.133
414Content-Type: application/sdp
415Content-Length: 178
416
417v=0
418o=mhandley 29739 7272939 IN IP4 126.5.4.3
419s=SIP Call
420c=IN IP4 135.180.130.88
421t=3149328700 0
422m=audio 49210 RTP/AVP 0 12
423m=video 3227 RTP/AVP 31
424a=rtpmap:31 LPC/8000
425
426|This INVITE contains an unknown URI scheme in the Request-URI.
427INVITE name:user SIP/2.0
428To: sip:user@company.com
429From: sip:caller@university.edu
430Call-ID: 6@10.0.0.1
431CSeq: 1 INVITE
432Via: SIP/2.0/UDP 135.180.130.133
433Content-Type: application/sdp
434Content-Length: 178
435
436v=0
437o=mhandley 29739 7272939 IN IP4 126.5.4.3
438s=SIP Call
439c=IN IP4 135.180.130.88
440t=3149328700 0
441m=audio 49210 RTP/AVP 0 12
442m=video 3227 RTP/AVP 31
443a=rtpmap:31 LPC/8000
444
445|This OPTIONS request is legal despite there being no LWS between the display name and < in the From header.
446OPTIONS sip:user@company.com SIP/2.0
447To: sip:user@company.com
448From: "caller"<sip:caller@example.com>
449Call-ID: 1234abcd@10.0.0.1
450CSeq: 1 OPTIONS
451Via: SIP/2.0/UDP 135.180.130.133
452
453|This OPTIONS request is legal despite there being extra LWS between the display name and < in the From header.
454OPTIONS sip:user@company.com SIP/2.0
455To: sip:user@company.com
456From: "caller"    <sip:caller@example.com>
457Call-ID: 1234abcd@10.0.0.1
458CSeq: 2 OPTIONS
459Via: SIP/2.0/UDP 135.180.130.133
460
461|This INVITE is illegal as it contains a non GMT time zone in the SIP Date of the Expires header.
462INVITE sip:user@company.com SIP/2.0
463To: sip:user@company.com
464From: sip:caller@university.edu
465Call-ID: 7@10.0.0.1
466CSeq: 1 INVITE
467Via: SIP/2.0/UDP 135.180.130.133
468Expires: Fri, 01 Jan 2010 16:00:00 EST
469Content-Type: application/sdp
470Content-Length: 178
471
472v=0
473o=mhandley 29739 7272939 IN IP4 126.5.4.3
474s=SIP Call
475t=3149328700 0
476c=IN IP4 135.180.130.88
477m=audio 49210 RTP/AVP 0 12
478m=video 3227 RTP/AVP 31
479a=rtpmap:31 LPC/8000
480
481|This is a legal INVITE but the message content has long since expired.
482INVITE sip:user@company.com SIP/2.0
483To: sip:user@company.com
484From: sip:caller@university.edu
485Call-ID: 8@10.0.0.1
486CSeq: 1 INVITE
487Via: SIP/2.0/UDP 135.180.130.133
488Expires: Thu, 01 Dec 1994 16:00:00 GMT
489Content-Type: application/sdp
490Content-Length: 178
491
492v=0
493o=mhandley 29739 7272939 IN IP4 126.5.4.3
494s=SIP Call
495c=IN IP4 135.180.130.88
496t=3149328700 0
497m=audio 49210 RTP/AVP 0 12
498m=video 3227 RTP/AVP 31
499a=rtpmap:31 LPC/8000
500
501|This is a legal SIP request with the Max-Forwards header set to zero.
502INVITE sip:user@company.com SIP/2.0
503To: sip:user@company.com
504From: sip:caller@university.edu
505Call-ID: 9@10.0.0.1
506CSeq: 1 INVITE
507Via: SIP/2.0/UDP 135.180.130.133
508Max-Forwards: 0
509Content-Type: application/sdp
510Content-Length: 178
511
512v=0
513o=mhandley 29739 7272939 IN IP4 126.5.4.3
514s=SIP Call
515c=IN IP4 135.180.130.88
516t=3149328700 0
517m=audio 49210 RTP/AVP 0 12
518m=video 3227 RTP/AVP 31
519a=rtpmap:31 LPC/8000
520
521|This is a legal REGISTER message where the Contact header contains a SIP URL with an escaped header within it.
522REGISTER sip:company.com SIP/2.0
523To: sip:user@company.com
524From: sip:user@company.com
525Contact: sip:user@host.company.com
526Call-ID: k345asrl3fdbv@10.0.0.1
527CSeq: 1 REGISTER
528Via: SIP/2.0/UDP 135.180.130.133
529Contact: <sip:user@example.com?Route=%3Csip:sip.example.com%3E>
530
531|This is an illegal message as the REGISTER request contains a SIP URL with an escaped header but it is not enclosed in <>
532REGISTER sip:company.com SIP/2.0
533To: sip:user@company.com
534From: sip:user@company.com
535Contact: sip:user@host.company.com
536Call-ID: k345asrl3fdbv@10.0.0.1
537CSeq: 1 REGISTER
538Via: SIP/2.0/UDP 135.180.130.133
539Contact: sip:user@example.com?Route=%3Csip:sip.example.com%3E
540
541|This is a legal message that contains long values in many headers.
542INVITE sip:user@company.com SIP/2.0
543To: "I have a user name of extreme proportion" <sip:user@company.com:6000;other-param=1234567890somethingelselong1234567890>
544From: sip:caller@university.edu
545Call-ID: kl24ahsd546folnyt2vbak9sad98u23naodiunzds09a3bqw0sdfbsk34poouymnae0043nsed09mfkvc74bd0cuwnms05dknw87hjpobd76f
546CSeq: 1 INVITE
547My-State: sldkjflzdsfaret0803adgaasd0afds0asdaasd
548Via: SIP/2.0/UDP sip33.example.com
549Via: SIP/2.0/UDP sip32.example.com
550Via: SIP/2.0/UDP sip31.example.com
551Via: SIP/2.0/UDP sip30.example.com
552Via: SIP/2.0/UDP sip29.example.com
553Via: SIP/2.0/UDP sip28.example.com
554Via: SIP/2.0/UDP sip27.example.com
555Via: SIP/2.0/UDP sip26.example.com
556Via: SIP/2.0/UDP sip25.example.com
557Via: SIP/2.0/UDP sip24.example.com
558Via: SIP/2.0/UDP sip23.example.com
559Via: SIP/2.0/UDP sip22.example.com
560Via: SIP/2.0/UDP sip21.example.com
561Via: SIP/2.0/UDP sip20.example.com
562Via: SIP/2.0/UDP sip19.example.com
563Via: SIP/2.0/UDP sip18.example.com
564Via: SIP/2.0/UDP sip17.example.com
565Via: SIP/2.0/UDP sip16.example.com
566Via: SIP/2.0/UDP sip15.example.com
567Via: SIP/2.0/UDP sip14.example.com
568Via: SIP/2.0/UDP sip13.example.com
569Via: SIP/2.0/UDP sip12.example.com
570Via: SIP/2.0/UDP sip11.example.com
571Via: SIP/2.0/UDP sip10.example.com
572Via: SIP/2.0/UDP sip9.example.com
573Via: SIP/2.0/UDP sip8.example.com
574Via: SIP/2.0/UDP sip7.example.com
575Via: SIP/2.0/UDP sip6.example.com
576Via: SIP/2.0/UDP sip5.example.com
577Via: SIP/2.0/UDP sip4.example.com
578Via: SIP/2.0/UDP sip3.example.com
579Via: SIP/2.0/UDP sip2.example.com
580Via: SIP/2.0/UDP sip1.example.com
581Via: SIP/2.0/UDP host.example.com;received=135.180.130.133;branch=C1C3344E2710000000E299E568E7potato10potato0potato0
582Content-Type: application/sdp
583
584v=0
585o=mhandley 29739 7272939 IN IP4 126.5.4.3
586s=SIP Call
587c=IN IP4 135.180.130.88
588t=3149328700 0
589m=audio 49210 RTP/AVP 0 12
590m=video 3227 RTP/AVP 31
591a=rtpmap:31 LPC/8000
592
593|This is an illegal and badly mangled message.
594OPTIONS sip:135.180.130.133 SIP/2.0
595Via: SIP/2.0/UDP company.com:5604
596From: sip:iuser@company.com
597To: sip:user@135.180.130.133
598Call-ID: 1804928587@company.com
599CSeq: 1 OPTIONS
600Expires: 0 0l@company.com
601To: sip:user@135.180.130.133
602Call-ID: 1804928587@company.com
603CSeq: 1 OPTIONS
604Contact: sip:host.company.com
605Expires: 0xpires: 0sip:host.company.com
606Expires: 0
607Contact: sip:host.company.com
608
609|This is a legal message with a large number of SDP attributes and a long telephone subscriber Request-URI
610INVITE sip:+1-972-555-2222;phone-context=name%40domain;new=user?%22Route%3a%20X%40Y%3bZ=W%22@gw1.wcom.com;user=phone SIP/2.0
611Via: SIP/2.0/UDP iftgw.there.com:5060
612From: sip:+1-303-555-1111@ift.here.com;user=phone
613To: sip:+1-650-555-2222@ss1.wcom.com;user=phone
614Call-ID: 1717@ift.here.com
615CSeq: 56 INVITE
616Content-Type: application/sdp
617Content-Length: 350
618
619v=0
620o=faxgw1 2890844527 2890844527 IN IP4 iftgw.there.com
621s=Session SDP
622c=IN IP4 iftmg.there.com
623t=0 0
624m=image 49172 udptl t38
625a=T38FaxVersion:0
626a=T38maxBitRate:14400
627a=T38FaxFillBitRemoval:0
628a=T38FaxTranscodingMMR:0
629a=T38FaxTranscodingJBIG:0
630a=T38FaxRateManagement:transferredTCF
631a=T38FaxMaxBuffer:260
632a=T38FaxUdpEC:t38UDPRedundancy
633
634|This REGISTER contains a contact where the 'user' parameter should be interpreted as being a contact-param and not a url-param. The register should succeed but a subsequent retrieval of the registration must not include "user=phone" as a url-parameter.
635REGISTER sip:bell-tel.com SIP/2.0
636Via: SIP/2.0/UDP saturn.bell-tel.com
637From: sip:watson@bell-tel.com
638To: sip:watson@bell-tel.com
639Call-ID: 70710@saturn.bell-tel.com
640CSeq: 2 REGISTER
641Contact: sip:+1-972-555-2222@gw1.wcom.com;user=phone
642
643|This register contains a contact where the 'user' parameter is a url-param. The register should succeed and a subsequent retrieval of the registration must include "user=phone" as a url-parameter.
644REGISTER sip:bell-tel.com SIP/2.0
645Via: SIP/2.0/UDP saturn.bell-tel.com
646From: sip:watson@bell-tel.com
647To: sip:watson@bell-tel.com
648Call-ID: 70710@saturn.bell-tel.com
649CSeq: 3 REGISTER
650Contact: <sip:+1-972-555-2222@gw1.wcom.com;user=phone>
651
652|This is a legal INVITE where the To and From header contain display names that contain multiple tokens but are unquoted
653INVITE sip:t.watson@ieee.org SIP/2.0
654Via:     SIP/2.0/UDP c.bell-tel.com
655From:    A. Bell <sip:a.g.bell@bell-tel.com>
656To:      T. Watson <sip:t.watson@ieee.org>
657Call-ID: 31414@c.bell-tel.com
658CSeq:    1 INVITE
659
660|This is an illegal invite at the display names in the To and From headers contain non-token characters but are unquoted. A server may be intelligent enough to cope with this but may also return a 400 response with an appropriate reason phrase.
661INVITE sip:t.watson@ieee.org SIP/2.0
662Via:     SIP/2.0/UDP c.bell-tel.com
663From:    Bell, Alexander <sip:a.g.bell@bell-tel.com>
664To:      Watson, Thomas <sip:t.watson@ieee.org>
665Call-ID: 31415@c.bell-tel.com
666CSeq:    1 INVITE
667
668|This should be rejected with 400. Section 4.1 lists SIP version as a literal and doesn't say anything about ignoring leading zeros. As an example of why rejecting it is a good idea, consider version numbers like 2.1 and 2.01 - they are unlikely to refer to the same version.
669INVITE sip:t.watson@ieee.org SIP/02.00
670Via:     SIP/2.0/UDP c.bell-tel.com
671From:    A. Bell <sip:a.g.bell@bell-tel.com>
672To:      T. Watson <sip:t.watson@ieee.org>
673Call-ID: 31416@c.bell-tel.com
674CSeq:    1 INVITE
675
676|This is an illegal INVITE as the SIP Protocol version is unknown.
677INVITE sip:t.watson@ieee.org SIP/7.0
678Via:     SIP/2.0/UDP c.bell-tel.com
679From:    A. Bell <sip:a.g.bell@bell-tel.com>
680To:      T. Watson <sip:t.watson@ieee.org>
681Call-ID: 31417@c.bell-tel.com
682CSeq:    1 INVITE
683
684|