sip server ipv4 rfc3262
DESCRIPTION
sip serverTRANSCRIPT
NTT Advanced Technology Corporation
SIP Conformance
Test Specification For SIP Server (IPv4)
SIP Extended Operation
(RFC 3262)
Revision 1.0
NTT Advanced Technology Corporation - 1 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
References
This test specification focus on the following SIP related RFCs.
RFC 3262 Reliability of Provisional Responses in the Session Initiation Protocol
(SIP)
NTT Advanced Technology Corporation - 2 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
---TOC--- References..................................................................................................................... 1
1. Introduction......................................................................................................... 3
2. Common Topology................................................................................................... 4
Figure 1. Topology No.1............................................................................... 4
3. Terminology........................................................................................................... 5
4. Description........................................................................................................... 6
5. Server Test........................................................................................................... 7
5.1. Reliability of Provisional Response............................................... 7
5.1.1. SIP Proxy- Forwarding PRACK request....................................... 7
5.1.2. SIP Proxy- PRACK request without Proxy-Authorization... 19
5.1.3. SIP Proxy- Sending reliable provisional response as UAS
23
5.1.4. SIP Proxy- Reliability of Probisional Responses for
re-INVITE......................................................................................................... 34
NTT Advanced Technology Corporation - 3 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
1. Introduction
This test specification focuses on SIP server functionalities described in RFC3262 .
NTT Advanced Technology Corporation - 4 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
2. Common Topology
Figure 1. Topology No.1 ---+-----------+---------
| |
| UA11
R11
|
---+---R-------+---------
| |
| NUT(ProxyServer1/Registrar)
R12
|
---+-----------+---------
|
UA12
NTT Advanced Technology Corporation - 5 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
3. Terminology NUT : Node Under Test
TN : Tester Node
NTT Advanced Technology Corporation - 6 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
4. Description
Each test specification consists of following parts.
Category: The Category shows what classification of device must satisfy
the test.
Network Topology: Network Topology which is used in the test.
Procedure: The Procedure describes step-by-step instructions for carrying
out the test.
Judgment: The Judgment describes expected result. If we can observe as same
result as the description of Judgment, the NUT passes the test.
References: The References section contains some parts of specification
NTT Advanced Technology Corporation - 7 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
5. Server Test
5.1. Reliability of Provisional Response
5.1.1. SIP Proxy- Forwarding PRACK request
Category:
Server Test
Network Topology:
Refer the topology "Figure 1. Topology No.1".
Procedure:
This test sequence is following.
UA11 : Proxy : UA12
| : | : |
| : | : |
|-------:------->| : | 1.INVITE
|<------:--------| : | 2.407
|-------:------->| : | 3.ACK
| : | : |
|-------:------->| : | 4.INVITE
| : |-------:------->| 5.INVITE(*1)
|<------:--------| : | 6.100(*2)
| : | : |
| : |<------:--------| 7.183
|<------:--------| : | 8.183(*3)
| : | : |
|-------:------->| : | 9.PRACK
| : |-------:------->|10.PRACK(*4)
| : | : |
| : |<------:--------|11.200 (PRACK)
|<------:--------| : |12.200 (PRACK)(*5)
| : | : |
| : |<------:--------|13.200 (INVITE)
|<------:--------| : |14.200 (INVITE)(*6)
| : | : |
|-------:------->| : |15.ACK
NTT Advanced Technology Corporation - 8 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
| : |-------:------->|16.ACK(*7)
| | |
|<===============================>| Both Way RTP Media
| | |
| : |<------:--------|17.BYE
|<------:--------| : |18.BYE
| : | : |
|-------:------->| : |19.200
| : |-------:------->|20.200
| : | : |
1. UA11 Send INVITE.
2. UA11 Receive 407 Proxy Authentication Required.
3. UA11 Send ACK.
4. UA11 Send INVITE.
5. UA12 Receive INVITE.
6. UA11 Receive 100 Trying.
7. UA12 Send 183 Session Progress.
8. UA11 Receive 183 Session Progress.
9. UA11 Send PRACK.
10. UA12 Receive PRACK.
11. UA12 Send 200 OK (for PRACK).
12. UA11 Receive 200 OK (for PRACK).
13. UA12 Send 200 OK (for INVITE).
14. UA11 Receive 200 OK (for INVITE).
15. UA11 Send ACK.
16. UA12 Receive ACK.
17. UA12 Send BYE.
18. UA11 Receive BYE.
19. UA11 Send 200.
20. UA12 Receive 200.
Packet Description
4. INVITE UA11 -> NUT
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000004, cnonce="6f54a149",
uri="sip:[email protected]",
NTT Advanced Technology Corporation - 9 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
response="b51e504e73af54829e4f2bd7f8dc4654"
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844526 IN IP4 192.0.10.10
s=-
c=IN IP4 192.0.10.10
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
5. INVITE NUT -> UA12
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Max-Forwards: 69
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844526 IN IP4 192.0.10.10
s=-
c=IN IP4 192.0.10.10
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
NTT Advanced Technology Corporation - 10 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
6. 100 Trying NUT -> UA11
SIP/2.0 100 Trying
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Content-Length: 0
7. 183 Session Progress UA12 -> NUT
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
Contact: <sip:[email protected]>
Require: 100rel
RSeq: 1
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 147
v=0
o=UA12 2890844527 2890844527 IN IP4 192.0.11.11
s=-
c=IN IP4 192.0.11.11
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000
8. 183 Session Progress NUT -> UA11
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
NTT Advanced Technology Corporation - 11 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
Contact: <sip:[email protected]>
Require: 100rel
RSeq: 1
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 147
v=0
o=UA12 2890844527 2890844527 IN IP4 192.0.11.11
s=-
c=IN IP4 192.0.11.11
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000
9. PRACK UA11 -> NUT
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000005, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
RAck: 1 2 INVITE
Content-Length: 0
10. PRACK NUT -> UA12
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.122
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
Max-Forwards: 69
Record-Route: <sip:ss.under.test.com;lr>
NTT Advanced Technology Corporation - 12 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
RAck: 1 2 INVITE
Content-Length: 0
11. 200 OK (for PRACK) UA12 -> NUT
SIP/2.0 200 OK
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.122
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
Content-Length: 0
12. 200 OK (for PRACK) NUT -> UA11
SIP/2.0 200 OK
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
Content-Length: 0
13. 200 OK (for INVITE) UA12 -> NUT
SIP/2.0 200 OK
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
NTT Advanced Technology Corporation - 13 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Content-Length: 0
14. 200 OK (for INVITE) NUT -> UA11
SIP/2.0 200 OK
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Content-Length: 0
15. ACK UA11 -> NUT
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b76
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000004, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 ACK
Content-Length: 0
16. ACK NUT -> UA12
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.1
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b76
;received=192.0.10.10
Max-Forwards: 69
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
NTT Advanced Technology Corporation - 14 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 ACK
Content-Length: 0
Judgment:
*1:INVITE request from NUT to UA12.
As a SIP Message,
See generic_message.txt
As a SIP request,
- Request-Line:
See generic_forward_from-UA11.txt
See generic_forward_R-URI_non-responsible-domain.txt
- Headers:
- outside of a dialog
See generic_forward_from-UA11.txt
See generic_forward_request.txt
* Supported
Must exist.
Must equal as that in the message from UA11.
Must include "100rel". [RFC3262-4-2]
- Bodies:
See generic_forward_from-UA11.txt
*2:100 response from NUT to UA11.(Optional)
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_make_response.txt
Status-Code: Must be "100".
- Headers:
See generic_make_response.txt
* Via
NTT Advanced Technology Corporation - 15 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet
was received. [RFC3261-18-28]
* RSeq:
Must not exist. [RFC3262-3-3]
* Require(if exists)
Must not include 100rel. [RFC3262-3-3]
*3:183 response from NUT to UA11.
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_forward_from-UA12.txt
Status-Code: Must be "183".
- Headers:
See generic_forward_from-UA12.txt
See generic_forward_response.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet
was received. [RFC3261-18-28]
* Require
Must exist and include "100rel". [RFC3262-3-9]
Must equal as that in the message from UA12.
* RSeq
Must exist. [RFC3262-3-10]
response-num: Must be between 1 and 2**31-1. [RFC3262-3-11]
Must equal as that in the message from UA12.
- Bodies:
See generic_forward_from-UA12.txt
*4:PRACK request from NUT to UA12.
As a SIP Message,
See generic_message.txt
NTT Advanced Technology Corporation - 16 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
As a SIP request,
- Request-Line:
See generic_forward_from-UA11.txt
See generic_forward_R-URI_responsible-domain.txt
- Headers:
- outside of a dialog
See generic_forward_from-UA11.txt
See generic_forward_request.txt
* RAck
Must exist.
Must equal as that in the message from UA11.
* Require
Must not include 100rel. [RFC3262-4-1]
- Bodies:
See generic_forward_from-UA11.txt
*5:200 response for PRACK from NUT to UA11.
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_forward_from-UA12.txt
Status-Code: Must be "200".
- Headers:
See generic_forward_from-UA12.txt
See generic_forward_response.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet
was received. [RFC3261-18-28]
- Bodies:
See generic_forward_from-UA12.txt
*6:200 response for INVITE from NUT to UA11.
NTT Advanced Technology Corporation - 17 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_forward_from-UA12.txt
Status-Code: Must be "200".
- Headers:
See generic_forward_from-UA12.txt
See generic_forward_response.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet
was received. [RFC3261-18-28]
- Bodies:
See generic_forward_from-UA12.txt
*7:ACK request from NUT to UA12.
As a SIP Message,
See generic_message.txt
As a SIP request,
- Request-Line:
See generic_forward_from-UA11.txt
See generic_forward_R-URI_responsible-domain.txt
- Headers:
- outside of a dialog
See generic_forward_from-UA11.txt
See generic_forward_request.txt
* Require
Must not include 100rel. [RFC3262-4-1]
- Bodies:
See generic_forward_from-UA11.txt
References:
NTT Advanced Technology Corporation - 18 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
[rfc3262.txt]
3 UAS Behavior
<b>A UAS MUST NOT attempt to send a 100 (Trying) response reliably.</b>
Only provisional responses numbered 101 to 199 may be sent reliably.
If the request did not include either a Supported or Require header
field indicating this feature, the UAS MUST NOT send the provisional
response reliably.
NTT Advanced Technology Corporation - 19 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
5.1.2. SIP Proxy- PRACK request without Proxy-Authorization
Category:
Server Test
Network Topology:
Refer the topology "Figure 1. Topology No.1".
Procedure:
This test sequence is following.
UA11 : Proxy : UA12
| : | : |
| : | : |
|-------:------->| : | 1.INVITE
|<------:--------| : | 2.407
|-------:------->| : | 3.ACK
| : | : |
|-------:------->| : | 4.INVITE
| : |-------:------->| 5.INVITE
|<------:--------| : | 6.100
| : | : |
| : |<------:--------| 7.183
|<------:--------| : | 8.183
| : | : |
|-------:------->| : | 9.PRACK
|<------:--------| : |10.407(*1)
| : | : |
|-------:------->| : |11.PRACK
| : |-------:------->|12.PRACK
| : | : |
| : |<------:--------|13.200 (PRACK)
|<------:--------| : |14.200 (PRACK)
| : | : |
| : |<------:--------|15.200 (INVITE)
|<------:--------| : |16.200 (INVITE)
| : | : |
|-------:------->| : |17.ACK
| : |-------:------->|18.ACK
| | |
NTT Advanced Technology Corporation - 20 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
|<===============================>| Both Way RTP Media
| | |
| : |<------:--------|19.BYE
|<------:--------| : |20.BYE
| : | : |
|-------:------->| : |21.200
| : |-------:------->|22.200
| : | : |
1. UA11 Send INVITE.
2. UA11 Receive 407 Proxy Authentication Required.
3. UA11 Send ACK.
4. UA11 Send INVITE.
5. UA12 Receive INVITE.
6. UA11 Receive 100 Trying.
7. UA12 Send 183 Session Progress.
8. UA11 Receive 183 Session Progress.
9. UA11 Send PRACK.
10. UA11 Receive 407 Proxy Authentication Required.
11. UA11 Send PRACK.
12. UA12 Receive PRACK.
13. UA12 Send 200 OK (for PRACK).
14. UA11 Receive 200 OK (for PRACK).
15. UA12 Send 200 OK (for INVITE).
16. UA11 Receive 200 OK (for INVITE).
17. UA11 Send ACK.
18. UA12 Receive ACK.
19. UA12 Send BYE.
20. UA11 Receive BYE.
21. UA11 Send 200.
22. UA12 Receive 200.
Packet Description
9. PRACK UA11 -> NUT
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7688
Max-Forwards: 70
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
NTT Advanced Technology Corporation - 21 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
RAck: 1 2 INVITE
Content-Length: 0
10. 407 Proxy Authentication Required NUT -> UA11
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7688
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 3 PRACK
Proxy-Authenticate: Digest realm="under.test.com", qop="auth",
nonce="f84f1cec41e6cbe5aea9c8e88d359",
opaque="", stale=FALSE, algorithm=MD5
Content-Length: 0
11. PRACK UA11 -> NUT
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000005, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 4 PRACK
RAck: 1 2 INVITE
Content-Length: 0
Judgment:
*1:407 response from NUT to UA11.
As a SIP Message,
See generic_message.txt
As a SIP response,
NTT Advanced Technology Corporation - 22 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
- Status-Line:
See generic_make_response.txt
Status-Code: Must be "407".
- Headers:
See generic_make_response.txt
See generic_proxy-auth.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet was
received. [RFC3261-18-28]
References:
[rfc3262.txt]
9 Security Considerations
The PRACK request can be injected by attackers to force
retransmissions of reliable provisional responses to cease. As these
responses can convey important information, <b>PRACK messages SHOULD be
authenticated as any other request.</b> Authentication procedures are
specified in RFC 3261.
NTT Advanced Technology Corporation - 23 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
5.1.3. SIP Proxy- Sending reliable provisional response as UAS
Category:
Server Test
Network Topology:
Refer the topology "Figure 1. Topology No.1".
Procedure:
This test sequence is following.
UA11 : Proxy : UA12
| : | : |
| : | : |
|-------:------->| : | 1.INVITE
|<------:--------| : | 2.407
|-------:------->| : | 3.ACK
| : | : |
|-------:------->| : | 4.INVITE
| : |-------:------->| 5.INVITE
|<------:--------| : | 6.100
| : | : |
|<------:--------| : | 7.183(*1)
|-------:------->| : | 8.PRACK
|<------:--------| : | 9.200 (PRACK)(*2)
| : | : |
| : |<------:--------|10.183
|<------:--------| : |11.183
| : | : |
|-------:------->| : |12.PRACK
| : |-------:------->|13.PRACK(*3)
| : | : |
| : |<------:--------|14.200 (PRACK)
|<------:--------| : |15.200 (PRACK)
| : | : |
| : |<------:--------|16.200 (INVITE)
|<------:--------| : |17.200 (INVITE)
| : | : |
|-------:------->| : |18.ACK
| : |-------:------->|19.ACK
NTT Advanced Technology Corporation - 24 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
| | |
|<===============================>| Both Way RTP Media
| | |
| : |<------:--------|20.BYE
|<------:--------| : |21.BYE
| : | : |
|-------:------->| : |22.200
| : |-------:------->|23.200
| : | : |
1. UA11 Send INVITE.
2. UA11 Receive 407 Proxy Authentication Required.
3. UA11 Send ACK.
4. UA11 Send INVITE.
5. UA12 Receive INVITE.
6. UA11 Receive 100 Trying.
7. UA11 Receive 183 Session Progress.
8. UA11 Send PRACK.
9. UA11 Receive 200 OK (for PRACK).
10. UA12 Send 183 Session Progress.
11. UA11 Receive 183 Session Progress.
12. UA11 Send PRACK.
13. UA12 Receive PRACK.
14. UA12 Send 200 OK (for PRACK).
15. UA11 Receive 200 OK (for PRACK).
16. UA12 Send 200 OK (for INVITE).
17. UA11 Receive 200 OK (for INVITE).
18. UA11 Send ACK.
19. UA12 Receive ACK.
20. UA12 Send BYE.
21. UA11 Receive BYE.
22. UA11 Send 200.
23. UA12 Receive 200.
Packet Description
4. INVITE UA11 -> NUT
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
NTT Advanced Technology Corporation - 25 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
qop=auth, nc=00000004, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844526 IN IP4 192.0.10.10
s=-
c=IN IP4 192.0.10.10
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
5. INVITE NUT -> UA12
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Max-Forwards: 69
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844526 IN IP4 192.0.10.10
s=-
c=IN IP4 192.0.10.10
t=0 0
NTT Advanced Technology Corporation - 26 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
6. 100 Trying NUT -> UA11
SIP/2.0 100 Trying
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 INVITE
Content-Length: 0
7. 183 Session Progress NUT -> UA11
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=px3012
Call-ID: [email protected]
Contact: <sip:[email protected]>
Require: 100rel
RSeq: 1
CSeq: 2 INVITE
Content-Length: 0
8. PRACK UA11 -> NUT
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699123
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000005, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=px3012
Call-ID: [email protected]
NTT Advanced Technology Corporation - 27 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
CSeq: 3 PRACK
RAck: 1 2 INVITE
Content-Length: 0
9. 200 OK (for PRACK) NUT -> UA11
SIP/2.0 200 OK
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699123
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=px3012
Call-ID: [email protected]
CSeq: 3 PRACK
Content-Length: 0
10. 183 Session Progress UA12 -> NUT
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
Contact: <sip:[email protected]>
Require: 100rel
RSeq: 1
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 147
v=0
o=UA12 2890844527 2890844527 IN IP4 192.0.11.11
s=-
c=IN IP4 192.0.11.11
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000
11. 183 Session Progress NUT -> UA11
SIP/2.0 183 Session Progress
NTT Advanced Technology Corporation - 28 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
Contact: <sip:[email protected]>
Require: 100rel
RSeq: 1
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 147
v=0
o=UA12 2890844527 2890844527 IN IP4 192.0.11.11
s=-
c=IN IP4 192.0.11.11
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000
12. PRACK UA11 -> NUT
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000005, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 4 PRACK
RAck: 1 2 INVITE
Content-Length: 0
/* To tag is different from that of 7.183 response, */
/* and is same as that of 10.183 response. */
13. PRACK NUT -> UA12
NTT Advanced Technology Corporation - 29 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
PRACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.122
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
Max-Forwards: 69
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 4 PRACK
RAck: 1 2 INVITE
Content-Length: 0
14. 200 OK (for PRACK) UA12 -> NUT
SIP/2.0 200 OK
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.122
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 4 PRACK
Content-Length: 0
15. 200 OK (for PRACK) NUT -> UA11
SIP/2.0 200 OK
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 4 PRACK
Content-Length: 0
16. 200 OK (for INVITE) UA12 -> NUT
SIP/2.0 200 OK
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1
;received=192.0.50.50
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
NTT Advanced Technology Corporation - 30 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Content-Length: 0
17. 200 OK (for INVITE) NUT -> UA11
SIP/2.0 200 OK
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]>
Content-Length: 0
18. ACK UA11 -> NUT
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b76
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000004, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 ACK
Content-Length: 0
19. ACK NUT -> UA12
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.1
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b76
;received=192.0.10.10
Max-Forwards: 69
NTT Advanced Technology Corporation - 31 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 2 ACK
Content-Length: 0
Judgment:
*1:183 response from NUT to UA11.
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_make_response.txt
Status-Code: Must be "183".
- Headers:
See generic_make_response.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet was
received. [RFC3261-18-28]
* Require
Must exist and include "100rel". [RFC3262-3-9]
* RSeq
Must exist. [RFC3262-3-10]
response-num: Must be between 1 and 2**31-1. [RFC3262-3-11]
*2:200 response for PRACK from NUT to UA11.
As a SIP Message,
See generic_message.txt
As a SIP response,
- Status-Line:
See generic_make_response.txt
Status-Code: Must be "200".
- Headers:
NTT Advanced Technology Corporation - 32 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
See generic_make_response.txt
* Via
via-received: Must be added if the host portion of the "sent-by"
parameter contains a domain name. [RFC3261-18-27]
via-received: Must contain the source address from which the packet was
received. [RFC3261-18-28]
*3:PRACK request from NUT to UA12.
As a SIP Message,
See generic_message.txt
As a SIP request,
- Request-Line:
See generic_forward_request.txt
See generic_forward_R-URI_responsible-domain.txt
- Headers:
- outside of a dialog
See generic_forward_message.txt
See generic_forward_request.txt
* RAck
Must exist.
Must equal as that in the message from UA11.
* Require
Must not include 100rel. [RFC3262-4-1]
- Bodies:
See generic_forward_message.txt
References:
[rfc3262.txt]
3 UAS Behavior
<b>An element that can act as a proxy can also send reliable provisional
responses. In this case, it acts as a UAS for purposes of that
transaction.</b> However, it MUST NOT attempt to do so for any request
that contains a tag in the To field. That is, a proxy cannot
generate reliable provisional responses to requests sent within the
context of a dialog. Of course, unlike a UAS, <b>when the proxy element
receives a PRACK that does not match any outstanding reliable
NTT Advanced Technology Corporation - 33 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
provisional response, the PRACK MUST be proxied.</b>
(snip)
Retransmissions of the reliable provisional response cease when a
matching PRACK is received by the UA core. PRACK is like any other
request within a dialog, and the UAS core processes it according to
the procedures of Sections 8.2 and 12.2.2 of RFC 3261. <b>A matching
PRACK is defined as one within the same dialog as the response, and
whose method, CSeq-num, and response-num in the RAck header field
match, respectively, the method from the CSeq, the sequence number
from the CSeq, and the sequence number from the RSeq of the reliable
provisional response.</b>
NTT Advanced Technology Corporation - 34 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
5.1.4. SIP Proxy- Reliability of Probisional Responses for
re-INVITE
Category:
Server Test
Network Topology:
Refer the topology "Figure 1. Topology No.1".
Procedure:
This test sequence is following.
UA11 : Proxy : UA12
| : | : |
| : | : |
|-------:------->| : | 1.INVITE
|<------:--------| : | 2.407
|-------:------->| : | 3.ACK
| : | : |
|-------:------->| : | 4.INVITE
| : |-------:------->| 5.INVITE
|<------:--------| : | 6.100
| : | : |
| : |<------:--------| 7.183
|<------:--------| : | 8.183
| : | : |
|-------:------->| : | 9.PRACK
| : |-------:------->|10.PRACK
| : | : |
| : |<------:--------|11.200 (PRACK)
|<------:--------| : |12.200 (PRACK)
| : | : |
| : |<------:--------|13.200 (INVITE)
|<------:--------| : |14.200 (INVITE)
| : | : |
|-------:------->| : |15.ACK
| : |-------:------->|16.ACK
| | |
|<===============================>| Both Way RTP Media
| | |
NTT Advanced Technology Corporation - 35 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
|-------:------->| : |17.INVITE
| : |-------:------->|18.INVITE
|<------:--------| : |19.100
| : | : |(*1)
| : |<------:--------|20.183
|<------:--------| : |21.183
| : | : |
|-------:------->| : |22.PRACK
| : |-------:------->|23.PRACK
| : | : |
| : |<------:--------|24.200 (PRACK)
|<------:--------| : |25.200 (PRACK)
| : | : |
| : |<------:--------|26.200 (INVITE)
|<------:--------| : |27.200 (INVITE)
| | |
|-------:------->| : |28.ACK
| : |-------:------->|29.ACK
| | |
|<===============================>| Both Way RTP Media
| | |
| : |<------:--------|30.BYE
|<------:--------| : |31.BYE
| : | : |
|-------:------->| : |32.200
| : |-------:------->|33.200
| : | : |
1. UA11 Send INVITE.
2. UA11 Receive 407 Proxy Authentication Required.
3. UA11 Send ACK.
4. UA11 Send INVITE.
5. UA12 Receive INVITE.
6. UA11 Receive 100 Trying.
7. UA12 Send 183 Session Progress.
8. UA11 Receive 183 Session Progress.
9. UA11 Send PRACK.
10. UA12 Receive PRACK.
11. UA12 Send 200 OK (for PRACK).
12. UA11 Receive 200 OK (for PRACK).
13. UA12 Send 200 OK (for INVITE).
14. UA11 Receive 200 OK (for INVITE).
15. UA11 Send ACK.
16. UA12 Receive ACK.
NTT Advanced Technology Corporation - 36 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
17. UA11 Send INVITE.
18. UA12 Receive INVITE.
19. UA11 Receive 100 Trying.
20. UA12 Send 183 Session Progress.
21. UA11 Receive 183 Session Progress.
22. UA11 Send PRACK.
23. UA12 Receive PRACK.
24. UA12 Send 200 OK (for PRACK).
25. UA11 Receive 200 OK (for PRACK).
26. UA12 Send 200 OK (for INVITE).
27. UA11 Receive 200 OK (for INVITE).
28. UA11 Send ACK.
29. UA12 Receive ACK.
30. UA12 Send BYE.
31. UA11 Receive BYE.
32. UA11 Send 200.
33. UA12 Receive 200.
Packet Description
17. INVITE UA11 -> NUT
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf0
Max-Forwards: 70
Proxy-Authorization: Digest username="UA11",
realm="under.test.com",
nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",
qop=auth, nc=00000004, cnonce="6f54a149",
uri="sip:[email protected]",
response="b51e504e73af54829e4f2bd7f8dc4654"
Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 5 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844527 IN IP4 192.0.10.10
NTT Advanced Technology Corporation - 37 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
s=-
c=IN IP4 192.0.10.10
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=sendonly
18. INVITE NUT -> UA12
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.5
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf0
;received=192.0.10.10
Max-Forwards: 69
Record-Route: <sip:ss.under.test.com;lr>
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 5 INVITE
Contact: <sip:[email protected]>
Supported: 100rel
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK
Content-Type: application/sdp
Content-Length: 151
v=0
o=UA11 2890844526 2890844527 IN IP4 192.0.10.10
s=-
c=IN IP4 192.0.10.10
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=sendonly
19. 100 Trying NUT -> UA11
SIP/2.0 100 Trying
Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf0
;received=192.0.10.10
From: UA11 <sip:[email protected]>;tag=9fxced76sl
To: UA12 <sip:[email protected]>;tag=314159
Call-ID: [email protected]
CSeq: 5 INVITE
Content-Length: 0
NTT Advanced Technology Corporation - 38 - SIP Conformance Test Specification
for SIP Server (IPv4) SIP Extended Operation (RFC 3262)
Judgment:
*1:183 response from NUT to UA11.
Must not be transmitted. [RFC3262-3-5]
References:
[rfc3262.txt]
3 UAS Behavior
An element that can act as a proxy can also send reliable provisional
responses. In this case, it acts as a UAS for purposes of that
transaction. <b>However, it MUST NOT attempt to do so for any request
that contains a tag in the To field.</b> That is, a proxy cannot
generate reliable provisional responses to requests sent within the
context of a dialog. Of course, unlike a UAS, when the proxy element
receives a PRACK that does not match any outstanding reliable
provisional response, the PRACK MUST be proxied.