📄 torture-test.txt
字号:
Message Details
NEWMETHOD sip:user@comapny.com SIP/2.0
To: sip:j.user@company.com
From: sip:caller@university.edu;tag=23411413
Max-Forwards: 3
Call-ID: 0ha0isndaksdj@10.0.1.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.9 REGISTER with Unknown Authorization Scheme
This message is a REGISTER request with an unknown authorization
scheme.
The server should do something reasonable, such as rejecting the
request.
Message Details
REGISTER sip:company.com SIP/2.0
To: sip:j.user@company.com
From: sip:j.user@company.com;tag=87321hj23128
Max-Forwards: 8
Call-ID: 0ha0isndaksdj@10.0.1.1
CSeq: 8 REGISTER
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Authorization: Super-PGP ajsohdaosdh0asyhdaind08yasdknasd09asidhas0d8
2.10 Multiple SIP Request in a Single Message
This message contains two requests, separated by a bunch of
whitespace. Since the message exceeds the length indicated in the
Content-Length header, the message should be rejected. (Multiple SIP
requests per UDP packet are no longer allowed.)
Message Details
REGISTER sip:company.com SIP/2.0
To: sip:j.user@company.com
From: sip:j.user@company.com;tag=43251j3j324
Max-Forwards: 8
Call-ID: 0ha0isndaksdj@10.0.2.2
Contact: sip:j.user@host.company.com
CSeq: 8 REGISTER
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Length: 0
INVITE sip:joe@company.com SIP/2.0
To: sip:joe@company.com
From: sip:caller@university.edu;tag=141334
Max-Forwards: 8
Call-ID: 0ha0isnda977644900765@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m =video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.11 INVITE missing Required Headers
This message contains no Call-ID, From, or To header.
The server should not crash, and ideally should respond with an
error.
Message Details
INVITE sip:user@company.com SIP/2.0
CSeq: 0 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.12 INVITE with Duplicate Required Headers
The message contains a request with an extra Call-ID and To field.
The server should not crash, and should ideally respond with an
error.
Message Details
INVITE sip:user@company.com SIP/2.0
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Max-Forwards: 70
CSeq: 0 INVITE
Call-ID: 98asdh@10.1.1.1
Call-ID: 98asdh@10.1.1.2
From: sip:caller@university.edu;tag=3413415
From: sip:caller@organization.org
To: sip:user@company.com
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.13 INVITE with Illegal Expires Header
This message contains an Expires header which has illegal values for
a number of components, but otherwise is syntactically correct.
Message Details
INVITE sip:user@company.com SIP/2.0
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Max-Forwards: 88
CSeq: 0 INVITE
Call-ID: 98asdh@10.1.1.2
Expires: Thu, 44 Dec 19999 16:00:00 EDT
From: sip:caller@university.edu;tag=3651
To: sip:user@company.com
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.14 200 OK Response with Broadcast Via Header
This message is a response with a 2nd Via header of 255.255.255.255.
On receiving this response, the top Via header is stripped and the
packet forwarded. Since the next address is the broadcast address,
it causes the packet to be broadcast onto the network. A smart server
should ignore packets with 2nd Via headers that are 255.255.255.255
or 127.0.0.1. At the very least it should not crash.
Message Details
SIP/2.0 200 OK
Via: SIP/2.0/UDP 135.180.130.57;branch=0
Via: SIP/2.0/UDP 255.255.255.255;branch=0
Max-Forwards: 70
Call-ID: 0384840201@10.1.1.1
CSeq: 0 INVITE
From: sip:user@company.com;tag=11141343
To: sip:user@university.edu;tag=2229
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 224.2.17.12/127
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.15 INVITE with Invalid Via and Contact Headers
This is a request with the Via and Contact headers incorrect. They
contain additional semicolons and commas without parameters or
values.
The server should respond with a Bad Request error.
Message Details
INVITE sip:user@company.com SIP/2.0
To: sip:j.user@company.com
From: sip:caller@university.edu;tag=134161461246
Max-Forwards: 7
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133;;,;
Contact: "" <> ;,"Joe" <sip:joe@org.org>;;,,;;
Content-Type: application/sdp
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.16 INVITE with Incorrect Content-Length Header
This is a request message with a Content Length that is much larger
than the length of the body.
When sent UDP, the server should respond with an error. With TCP,
there's not much you can do but wait...
Message Details
INVITE sip:user@company.com SIP/2.0
Max-Forwards: 80
To: sip:j.user@company.com
From: sip:caller@university.edu;tag=93942939o2
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 9999
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.17 INVITE with Invalid Value for Content-Length
This is a request message with a negative value for Content-Length.
The server should respond with an error.
Message Details
INVITE sip:user@company.com SIP/2.0
Max-Forwards: 254
To: sip:j.user@company.com
From: sip:caller@university.edu;tag=3
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: -999
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.18 INVITE with Garbage after Message Body
This is a request message with garbage after the end of the SDP
included in the body.
The servers should reject the request as the body is longer than the
Content-Length.
Message Details
INVITE sip:user@company.com SIP/2.0
To: sip:j.user@company.com
From: sip:caller@university.edu;tag=3223
Max-Forwards: 7
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 138
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
asdpasd08asdsdk:;;asd
a0sdjhg8a0''...'';;;;
2.19 INVITE with Error in Display Name in To Header
This is a request with an unterminated quote in the display name of
the To field.
The server can either return an error, or proxy it if it is
successful parsing without the terminating quote.
Message Details
INVITE sip:user@company.com SIP/2.0
To: "Mr. J. User <sip:j.user@company.com> From: sip:caller@university.edu;tag=93334
Max-Forwards: 10
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5050;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 138
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=0 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.20 INVITE with a Semicolon-Separated Parameter in the "user" Part
This is an INVITE request with a semicolon-separated parameter in
the "user" part.
Outbound proxies should direct it appropriately.
Message Details
INVITE sip:user;par=u%40h.com@company.com SIP/2.0
To: sip:j_user@company.com
From: sip:caller@university.edu;tag=33242
Max-Forwards: 3
Call-ID: 0ha0isndaksdj@10.1.1.1
CSeq: 8 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
2.21 INVITE with Illegal Enclosing of Request-URI in "<>"
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -