📄 torture-test.txt
字号:
This INVITE is illegal because the Request-URI has been enclosed
within in "<>".
An intelligent server may be able to deal with this and fix up
athe Request-URI if acting as a Proxy. If not it should respond 400
with an appropriate reason phrase.
Message Details
INVITE <sip:user@company.com> SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=39291
Max-Forwards: 23
Call-ID: 1@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133
Content-Type: application/sdp
Content-Length: 174
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
2.22 INVITE with Illegal LWS within Elements of Request-URI
This INVITE has illegal LWS within the SIP URI.
An intelligent server may be able to deal with this and fix up
the Request-URI if acting as a Proxy. If not it should respond 400
with an appropriate reason phrase.
Message Details
INVITE sip:user@company.com; transport=udp SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=231413434
Max-Forwards: 5
Call-ID: 2@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 174
v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
s=-
c=IN IP4 135.180.130.88
t=3149328700 0
m=audio 492170 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC
`
2.23 INVITE with illegal >1 SP between elements of Request URI
This INVITE has illegal >1 SP between elements of the Request-URI.
An intelligent server may be able to deal with this and fix up
the Request-URI if acting as a Proxy. If not it should respond 400
with an appropriate reason phrase.
Message Details
INVITE sip:user@company.com SIP/2.0
Max-Forwards: 8
To: sip:user@company.com
From: sip:caller@university.edu;tag=8814
Call-ID: 3@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 174
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.24 INVITE with a legal SIP URI containing escaped characters
This INVITE is legal and has a Request-URI with a SIP URI containing
escaped characters.
Message Details
INVITE sip:sip%3Auser%40example.com@company.com;other-param=summit
SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=938
Max-Forwards: 87
Call-ID: 4@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 174
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.25 INVITE with the illegal use of escaped headers in Request-URI
This INVITE is illegal as it the Request-URI contains a SIP URI
containing
escaped headers.
An intelligent server may be liberal enough to accept this. A server
acting as a proxy should remove the escaped header before processing.
Message Details
INVITE sip:user@company.com?Route=%3Csip:sip.example.com%3E SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=341518
Max-Forwards: 7
Call-ID: 5@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 174
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.26 INVITE containing an unknown scheme in the Request URI
This INVITE contains an unknown URI scheme in the Request-URI.
A server should reject this message with a 400 response plus an
appropriate reason phrase despite being able to understand the
To header as a SIP URI.
Message Details
INVITE name:user SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=384
Max-Forwards: 3
Call-ID: 6@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw
Content-Type: application/sdp
Content-Length: 174
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.27 OPTIONS with no LWS between display name and < This OPTIONS request is legal despite there being no LWS between
the display name and < in the From header.
Message Details
OPTIONS sip:user@company.com SIP/2.0
To: sip:user@company.com
From: "caller"<sip:caller@example.com>;tag=323
Max-Forwards: 70
Call-ID: 1234abcd@10.0.0.1
CSeq: 1 OPTIONS
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
2.28 OPTIONS with extran LWS between display name and < This OPTIONS request is legal despite there being extra LWS between
the display name and < in the From header.
Message Details
OPTIONS sip:user@company.com SIP/2.0
To: sip:user@company.com
From: "caller" <sip:caller@example.com>;tag=32
Max-Forwards: 70
Call-ID: 1234abcd@10.0.0.1
CSeq: 2 OPTIONS
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
2.29 INVITE with an illegal SIP Date format.
This INVITE is illegal as it contains a non GMT time zone in the SIP
Date header.
An intelligent server may be able to fix this up and correct the time
to GMT. Alternatively this message may illicit a 400 response with an
appropriate reason phrase.
Message Details
INVITE sip:user@company.com SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=2
Max-Forwards: 70
Call-ID: 7@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Date: Fri, 01 Jan 2010 16:00:00 EST
Content-Type: application/sdp
Content-Length: 174
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.30 INVITE with Passed Expries Time
This is a legal INVITE but the message content has long since
expired.
A server should respond 408 (Timeout).
Message Details
INVITE sip:user@company.com SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=3843
Max-Forwards: 70
Call-ID: 8@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Content-Type: application/sdp
Content-Length: 174
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.31 INVITE with Max-Forwards Set to Zero
This is a legal SIP request with the Max-Forwards header set to zero.
A proxy or gateway should not forward the request and respond 483
(Too Many Hops).
Message Details
INVITE sip:user@company.com SIP/2.0
To: sip:user@company.com
From: sip:caller@university.edu;tag=3ghsd41
Call-ID: 9@10.0.0.1
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Max-Forwards: 0
Content-Type: application/sdp
Content-Length: 174
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.32 REGISTER with a Escaped Header in a Legal SIP URI of a Contact
This is a legal REGISTER message where the Contact header contains a
SIP URI with an escaped header within it.
Message Details
REGISTER sip:company.com SIP/2.0
To: sip:user@company.com
From: sip:user@company.com;tag=8
Max-Forwards: 70
Contact: sip:user@host.company.com
Call-ID: k345asrl3fdbv@10.0.0.1
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Contact: <sip:user@example.com?Route=%3Csip:sip.example.com%3E>
2.33 REGISTER with a Escaped Header in a Illegal SIP URI of a Contact
This is an illegal message as the REGISTER request contains a SIP
URI with an escaped header but it is not enclosed in <> A server should respond 400 with an appropriate reason phrase.
Message Details
REGISTER sip:company.com SIP/2.0
To: sip:user@company.com
From: sip:user@company.com;tag=998332
Max-Forwards: 70
Contact: sip:user@host.company.com
Call-ID: k345asrl3fdbv@10.0.0.1
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw
Contact: sip:user@example.com?Route=%3Csip:sip.example.com%3E
2.34 INVITE with Long Values in Headers
This is a legal message that contains long values in many headers.
Message Details
INVITE sip:user@company.com SIP/2.0
To: "I have a user name of extreme proportion"
<sip:user@company.com:6000;other-
param=1234567890somethingelselong1234567890> From: sip:caller@university.edu;tag=12481841982424
Call-ID:
kl24ahsd546folnyt2vbak9sad98u23naodiunzds09a3bqw0sdfbsk34poouymnae004
3nsed09mfkvc74bd0cuwnms05dknw87hjpobd76f
CSeq: 1 INVITE
P-My-State: sldkjflzdsfaret0803adgaasd0afds0asdaasd
Via: SIP/2.0/TCP sip33.example.com
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -