torture_hgs

libosip2-3.0.1

s=SIP Call
t=3149328700 0
c=IN IP4 135.180.130.88
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This INVITE has illegal LWS within the SIP URL.
INVITE sip:[e-mail]; transport=udp SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 2@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
t=3149328700 0
c=IN IP4 135.180.130.88
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This INVITE has illegal >1 SP between elements of the Request-URI.
INVITE sip:[e-mail]  SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 3@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This INVITE is legal and has a Request-URI with a SIP URL containing escaped characters
INVITE sip:[e-mail];other-param=summit SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 4@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This INVITE is illegal as it the Request-URI contains a SIP URL containing escaped headers
INVITE sip:[e-mail]?Route=%3Csip:sip.example.com%3E SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 5@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This INVITE contains an unknown URI scheme in the Request-URI.
INVITE name:user SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 6@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This OPTIONS request is legal despite there being no LWS between the display name and < in the From header.
OPTIONS sip:[e-mail] SIP/2.0
To: sip:[e-mail]
From: "caller"<sip:[e-mail]>
Call-ID: 1234abcd@10.0.0.1
CSeq: 1 OPTIONS
Via: SIP/2.0/UDP 135.180.130.133

|This OPTIONS request is legal despite there being extra LWS between the display name and < in the From header.
OPTIONS sip:[e-mail] SIP/2.0
To: sip:[e-mail]
From: "caller"    <sip:[e-mail]>
Call-ID: 1234abcd@10.0.0.1
CSeq: 2 OPTIONS
Via: SIP/2.0/UDP 135.180.130.133

|This INVITE is illegal as it contains a non GMT time zone in the SIP Date of the Expires header.
INVITE sip:[e-mail] SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 7@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Expires: Fri, 01 Jan 2010 16:00:00 EST
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
t=3149328700 0
c=IN IP4 135.180.130.88
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This is a legal INVITE but the message content has long since expired.
INVITE sip:[e-mail] SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 8@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This is a legal SIP request with the Max-Forwards header set to zero.
INVITE sip:[e-mail] SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Call-ID: 9@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Max-Forwards: 0
Content-Type: application/sdp
Content-Length: 178

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This is a legal REGISTER message where the Contact header contains a SIP URL with an escaped header within it. 
REGISTER sip:company.com SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Contact: sip:[e-mail]
Call-ID: k345asrl3fdbv@10.0.0.1
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 135.180.130.133
Contact: <sip:[e-mail]?Route=%3Csip:sip.example.com%3E>

|This is an illegal message as the REGISTER request contains a SIP URL with an escaped header but it is not enclosed in <> 
REGISTER sip:company.com SIP/2.0
To: sip:[e-mail]
From: sip:[e-mail]
Contact: sip:[e-mail]
Call-ID: k345asrl3fdbv@10.0.0.1
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 135.180.130.133
Contact: sip:[e-mail]?Route=%3Csip:sip.example.com%3E

|This is a legal message that contains long values in many headers.
INVITE sip:[e-mail] SIP/2.0
To: "I have a user name of extreme proportion" <sip:[e-mail]:6000;other-param=1234567890somethingelselong1234567890>
From: sip:[e-mail]
Call-ID: kl24ahsd546folnyt2vbak9sad98u23naodiunzds09a3bqw0sdfbsk34poouymnae0043nsed09mfkvc74bd0cuwnms05dknw87hjpobd76f
CSeq: 1 INVITE
My-State: sldkjflzdsfaret0803adgaasd0afds0asdaasd
Via: SIP/2.0/UDP sip33.example.com
Via: SIP/2.0/UDP sip32.example.com
Via: SIP/2.0/UDP sip31.example.com
Via: SIP/2.0/UDP sip30.example.com
Via: SIP/2.0/UDP sip29.example.com
Via: SIP/2.0/UDP sip28.example.com
Via: SIP/2.0/UDP sip27.example.com
Via: SIP/2.0/UDP sip26.example.com
Via: SIP/2.0/UDP sip25.example.com
Via: SIP/2.0/UDP sip24.example.com
Via: SIP/2.0/UDP sip23.example.com
Via: SIP/2.0/UDP sip22.example.com
Via: SIP/2.0/UDP sip21.example.com
Via: SIP/2.0/UDP sip20.example.com
Via: SIP/2.0/UDP sip19.example.com
Via: SIP/2.0/UDP sip18.example.com
Via: SIP/2.0/UDP sip17.example.com
Via: SIP/2.0/UDP sip16.example.com
Via: SIP/2.0/UDP sip15.example.com
Via: SIP/2.0/UDP sip14.example.com
Via: SIP/2.0/UDP sip13.example.com
Via: SIP/2.0/UDP sip12.example.com
Via: SIP/2.0/UDP sip11.example.com
Via: SIP/2.0/UDP sip10.example.com
Via: SIP/2.0/UDP sip9.example.com
Via: SIP/2.0/UDP sip8.example.com
Via: SIP/2.0/UDP sip7.example.com
Via: SIP/2.0/UDP sip6.example.com
Via: SIP/2.0/UDP sip5.example.com
Via: SIP/2.0/UDP sip4.example.com
Via: SIP/2.0/UDP sip3.example.com
Via: SIP/2.0/UDP sip2.example.com
Via: SIP/2.0/UDP sip1.example.com
Via: SIP/2.0/UDP host.example.com;received=135.180.130.133;branch=C1C3344E2710000000E299E568E7potato10potato0potato0
Content-Type: application/sdp

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=SIP Call
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000

|This is an illegal and badly mangled message.
OPTIONS sip:135.180.130.133 SIP/2.0
Via: SIP/2.0/UDP company.com:5604
From: sip:[e-mail]
To: sip:user@135.180.130.133
Call-ID: [e-mail]
CSeq: 1 OPTIONS
Expires: 0 [e-mail]
To: sip:user@135.180.130.133
Call-ID: [e-mail]
CSeq: 1 OPTIONS
Contact: sip:host.company.com
Expires: 0xpires: 0sip:host.company.com
Expires: 0
Contact: sip:host.company.com

|This is a legal message with a large number of SDP attributes and a long telephone subscriber Request-URI
INVITE sip:[phone];phone-context=name%40domain;new=user?%22Route%3a%20X%40Y%3bZ=[e-mail];user=phone SIP/2.0
Via: SIP/2.0/UDP iftgw.there.com:5060
From: sip:[e-mail];user=phone
To: sip:[e-mail];user=phone
Call-ID: [e-mail]
CSeq: 56 INVITE
Content-Type: application/sdp
Content-Length: 350

v=0
o=faxgw1 2890844527 2890844527 IN IP4 iftgw.there.com
s=Session SDP
c=IN IP4 iftmg.there.com
t=0 0
m=image 49172 udptl t38
a=T38FaxVersion:0
a=T38maxBitRate:14400
a=T38FaxFillBitRemoval:0
a=T38FaxTranscodingMMR:0
a=T38FaxTranscodingJBIG:0
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:260
a=T38FaxUdpEC:t38UDPRedundancy

|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.
REGISTER sip:bell-tel.com SIP/2.0
Via: SIP/2.0/UDP saturn.bell-tel.com
From: sip:[e-mail]
To: sip:[e-mail]
Call-ID: [e-mail]
CSeq: 2 REGISTER
Contact: sip:[e-mail];user=phone

|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.
REGISTER sip:bell-tel.com SIP/2.0
Via: SIP/2.0/UDP saturn.bell-tel.com
From: sip:[e-mail]
To: sip:[e-mail]
Call-ID: [e-mail]
CSeq: 3 REGISTER
Contact: <sip:[e-mail];user=phone>

|This is a legal INVITE where the To and From header contain display names that contain multiple tokens but are unquoted
INVITE sip:[e-mail] SIP/2.0
Via:     SIP/2.0/UDP c.bell-tel.com
From:    A. Bell <sip:[e-mail]>
To:      T. Watson <sip:[e-mail]>
Call-ID: [e-mail]
CSeq:    1 INVITE

|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.
INVITE sip:[e-mail] SIP/2.0
Via:     SIP/2.0/UDP c.bell-tel.com
From:    Bell, Alexander <sip:[e-mail]>
To:      Watson, Thomas <sip:[e-mail]>
Call-ID: [e-mail]
CSeq:    1 INVITE

|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.
INVITE sip:[e-mail] SIP/02.00
Via:     SIP/2.0/UDP c.bell-tel.com
From:    A. Bell <sip:[e-mail]>
To:      T. Watson <sip:[e-mail]>
Call-ID: [e-mail]
CSeq:    1 INVITE

|This is an illegal INVITE as the SIP Protocol version is unknown.
INVITE sip:[e-mail] SIP/7.0
Via:     SIP/2.0/UDP c.bell-tel.com
From:    A. Bell <sip:[e-mail]>
To:      T. Watson <sip:[e-mail]>
Call-ID: [e-mail]
CSeq:    1 INVITE

|