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