B.5 CANCEL method
29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS
The table B.5.1 lists the supported header fields within the CANCEL request.
Table B.5.1: Supported header fields within the CANCEL request
|
Item |
Header field |
Ref. |
RFC status |
II-NNI condition |
|---|---|---|---|---|
|
1 |
Accept-Contact |
[51] |
o |
do |
|
2 |
Authorization |
[13] |
o |
IF table 6.1.3.1/7 THEN do (NOTE) |
|
3 |
Call-ID |
[13] |
m |
dm |
|
4 |
Content-Length |
[13] |
t |
dt |
|
5 |
Content-Type |
[13] |
* |
IF table 6.1.3.1/20 THEN do (NOTE) |
|
6 |
CSeq |
[13] |
m |
dm |
|
7 |
Date |
[13] |
o |
do |
|
8 |
From |
[13] |
m |
dm |
|
9 |
Max-Breadth |
[79] |
o |
do |
|
10 |
Max-Forwards |
[13] |
m |
dm |
|
11 |
Privacy |
[34] |
o |
do |
|
12 |
Reason |
[48] |
o |
IF dc1 (CW: clause 12.7) THEN dm ELSE IF table 6.1.3.1/40 THEN do (NOTE) |
|
13 |
Record-Route |
[13] |
o |
do |
|
14 |
Reject-Contact |
[51] |
o |
do |
|
15 |
Request-Disposition |
[51] |
o |
do |
|
16 |
Resource-Priority |
[78] |
o |
IF table 6.1.3.1/73 THEN do (NOTE) |
|
17 |
Route |
[13] |
c |
dc |
|
18 |
Session-ID |
[124] |
m |
IF table 6.1.3.1/94 THEN dm (NOTE) |
|
19 |
Supported |
[13] |
o |
do |
|
20 |
Timestamp |
[13] |
o |
do |
|
21 |
To |
[13] |
m |
dm |
|
22 |
User-Agent |
[13] |
o |
do |
|
23 |
Via |
[13] |
m |
dm |
|
dc1: request invoked due to CW at the expiry of the "CW timer" |
||||
|
NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. |
||||
The table B.5.2 lists the supported header fields within the CANCEL response.
Table B.5.2: Supported header fields within the CANCEL response
|
Item |
Header field |
SIP status code |
Ref. |
RFC status |
II-NNI condition |
|---|---|---|---|---|---|
|
1 |
Accept-Resource-Priority |
2xx 417 |
[78] |
o |
IF table 6.1.3.1/73 THEN do (NOTE) |
|
2 |
Call-ID |
r |
[13] |
m |
dm |
|
3 |
Content-Length |
r |
[13] |
t |
dt |
|
4 |
CSeq |
r |
[13] |
m |
dm |
|
5 |
Date |
r |
[13] |
o |
do |
|
6 |
Error-Info |
3xx-6xx |
[13] |
o |
IF table 6.1.3.1/13 THEN do (NOTE) |
|
7 |
From |
r |
[13] |
m |
dm |
|
8 |
Privacy |
r |
[34] |
o |
do |
|
9 |
Record-Route |
2xx |
[13] |
o |
do |
|
10 |
Response-Source |
3xx-6xx |
[5] |
n/a |
IF table 6.1.3.1/121 THEN do (NOTE) |
|
11 |
Retry-After |
404 413 480 486 500 503 600 603 |
[13] |
o |
do |
|
12 |
Session-ID |
r |
[124] |
m |
IF table 6.1.3.1/94 THEN dm (NOTE) |
|
13 |
Supported |
2xx |
[13] |
o |
do |
|
14 |
Timestamp |
r |
[13] |
o |
do |
|
15 |
To |
r |
[13] |
m |
dm |
|
16 |
User-Agent |
r |
[13] |
o |
do |
|
17 |
Via |
r |
[13] |
m |
dm |
|
18 |
Warning |
r |
[13] |
o |
do |
|
NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. |
|||||