ACM indicating call forwarding

181 (Call Is Being Forwarded) response

See table 7.5.4.2.1.6

CPG indicating call forwarding (see NOTE)

181 (Call Is Being Forwarded) response

See table 7.5.4.2.1.7

ACM indicating ringing

180 (Ringing) response

See table 7.5.4.2.1.8

CPG indicating alerting (see NOTE)

180 (Ringing) response

See table 7.5.4.2.1.9

ANM

200 (OK) response

See table 7.5.4.2.1.10

CON

200 (OK) response (Neither a 181 (Call Is Being Forwarded) response nor a 180 (Ringing) response was received)

See table 7.5.4.2.1.10

NOTE: A CPG will be sent if an ACM was already sent.

hi-targeted-to-uri of the last History-Info hi-entry containing a "cause" URI parameter, as defined in IETF RFC 4458 [113]. (NOTE 2)

The global number portion of the hi-targeted-to-uri is assumed to be in form
“+” CC + NDC + SN.(NOTE 1)

CC

Nature of address indicator

If CC is equal to the country code of the country where O‑MGCF is located AND the next ISUP node is located in the same country, then set to “national (significant) number” else set to “international number”.

CC, NDC, SN

Address signals

If NOA is “national (significant) number” then set to NDC + SN.

If NOA is “international number”

then set to CC + NDC + SN.

NOTE 1: If the SIP URI doesn’t contain “user=phone”, mapping to redirection number is impossible, therefore no need to generate Redirection number and Redirection number restriction parameter (per table 7.5.4.2.1.3), Notification subscription options can’t be set as “presentation allowed with redirection number”.

NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

“history” or “session” or “header”

Presentation restricted indicator

“Presentation restricted”

Privacy "headers" component of the hi-targeted-to-uri and Privacy header field absent

or “none”

“Presentation allowed” or absent

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

Notification subscription options

If the priv-value “history” or “session” or “header” is received within the Privacy header field or the priv-value "history" is received within the "headers" component of the hi-targeted-to-uri representing the diverting URI(s) and within the hi-targeted-to-uri representing diverted-to URI then “presentation not allowed” shall be set.

Otherwise, if the priv-value “history” is received only within the "headers" component of the hi-targeted-to-uri representing the diverted-to URI then “presentation allowed without redirection number” shall be set. (NOTE 1, NOTE 2)

Otherwise, "presentation allowed with redirection number" shall be set.

"cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing hi-targeted-to-uri with "cause" URI parameter. (NOTE 3)

Cause value

Redirecting reason

404

Unknown

302

Unconditional

486

User busy

408

No reply

480

Deflection immediate response

503

Mobile subscriber not reachable

487

Deflection during alerting

NOTE 1: diverting URI corresponds to the hi-targeted-to-uri of the hi-entry containing a hi-index value that match the "mp" header field parameter value of the diverted-to URI. If the diverted-to URI does not contain the "mp" header field parameter, the diverting URI corresponds to the hi-targeted-to-uri of the hi-entry before the last hi-entry containing "cause" URI parameter.

NOTE 2: diverted-to URI corresponds to the hi-targeted-to-uri of the last hi-entry containing "cause" URI parameter and is mapped to the Redirection number, see table 7.5.4.2.1.2.

NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

181 (Call Is Being Forwarded)

ACM

Generic notification indicator

Notification indicator

Call is diverting

History-Info header field

See table 7.5.4.2.1.2

Redirection number

See table 7.5.4.2.1.2

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.3

Redirection number restriction

See table 7.5.4.2.1.3

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.4

Call diversion information Notification subscription options

See table 7.5.4.2.1.4

hi-targeted-to-uri; "cause" URI parameter as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE)

See table 7.5.4.2.1.4

Call diversion information Redirecting reason

See table 7.5.4.2.1.4

NOTE: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

181 (Call Is Being Forwarded) response

CPG

Generic notification indicator

Notification indicator

Call is diverting

"cause" URI parameter, as defined in IETF RFC 4458  [113] of the last History-Info hi-entry containing hi-targeted-to-uri with "cause" URI parameter. (NOTE 2)

486

Event information

Event indicator

CFB (national use)

408 (see NOTE 1)

CFNR (national use)

302

CFU (national use)

Any other value, or if appropriate "national use" value (CFB, CFNR or CFU) is not used in a network. or if no agreement exists between operators to use these values, or if no hi-targeted-to-uri with "cause" URI parameter is contained in the SIP 181.

PROGRESS

History-Info header field

See table 7.5.4.2.1.2

Redirection number

See table 7.5.4.2.1.2

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.3

Redirection number restriction

See table 7.5.4.2.1.3

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.4

Call diversion information Notification subscription options

See table 7.5.4.2.1.4

hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2)

See table 7.5.4.2.1.4

Call diversion information Redirecting reason

See table 7.5.4.2.1.4

NOTE 1: This appears in the cases of CFNR.

NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

180 (Ringing) response

ACM

History-Info header field

If hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113].

Generic notification indicator

Notification indicator

Call is diverting

History-Info header field

See table 7.5.4.2.1.2

Redirection number (NOTE 1)

See table 7.5.4.2.1.2

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.3

Redirection number restriction (NOTE 1)

See table 7.5.4.2.1.3

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.4

Call diversion information Notification subscription options (NOTE 1)

See table 7.5.4.2.1.4

hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2)

See table 7.5.4.2.1.4

Call diversion information Redirecting reason (NOTE 1)

See table 7.5.4.2.1.4

NOTE 1: Parameter shall only be supplied if hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113].

NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

180 (Ringing) response

CPG

History-Info header field

If hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113].

Generic notification indicator

Notification indicator

Call is diverting

Event information

Event indicator

ALERTING

History-Info header field

See table 7.5.4.2.1.2

Redirection number

(NOTE 1)

See table 7.5.4.2.1.2

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.3

Redirection number restriction (NOTE 1)

See table 7.5.4.2.1.3

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.4

Call diversion information Notification subscription options (NOTE 1)

See table 7.5.4.2.1.4

hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2)

See table 7.5.4.2.1.4

Call diversion information Redirecting reason (NOTE 1)

See table 7.5.4.2.1.4

NOTE 1: Parameter shall only be supplied if hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113].

NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear.

200 (OK) response

ANM/CON

History-Info header field

See table 7.5.4.2.1.2

Redirection number(NOTE)

See table 7.5.4.2.1.2

Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field

See table 7.5.4.2.1.3

Redirection number restriction

See table 7.5.4.2.1.3

NOTE: Redirection number shall only be supplied if 200 (OK) response is mapped to ANM message.

IAM

INVITE request

Redirecting number

History-Info header field

IF Redirection counter exceeds 1

hi-targeted-to-uri of the

penultimate created hi-entry

(NOTE 9)

IF Redirecting number is available

set to the value of the

Redirecting number

ELSE

set to the Unknown User

Identity (NOTE 10)

ELSE

no mapping (NOTE 8)

Nature of address indicator

"national (significant) number"

hi-targeted-to-uri

Add CC (of the country where the MGCF is located) to Redirecting number Address Signals to construct E.164 number in URI.

"international number"

Map complete Redirecting number Address Signals to E.164 number in URI.

Address Signals

If NOA is "national (significant) number" then the format of the Address Signals is:

NDC + SN

If NOA is "international number"

then the format of the Address Signals is:

CC + NDC + SN

hi-targeted-to-uri

Addr-spec

"+" CC NDC SN mapped to userinfo portion of SIP URI. (NOTE 5)

Add "user=phone".

Redirecting number

APRI

Privacy header field that

corresponds to the penultimate hi-targeted-to-uri entry in the History-Info header

Priv-value

"presentation restricted"

"history"

"presentation allowed"

Privacy header field absent or "none" (NOTE 3)

Redirection information

Redirecting indicator

Privacy header field that

corresponds to the penultimate hi-targeted-to-uri entry in the History-Info header

Priv-value

Call diverted

Privacy header field absent or "none" (NOTE 4)

Call diverted, all redirection information presentation restricted

"history"

Redirection information

Redirection counter

1

hi-index and "mp" header field parameter (NOTE 7)

Number of diversions is shown to the number of levels in hi-index

Index for Original called number = 1

Index for Called party number = 1.1 and addition "mp=1"

2

Index for Original called number = 1

Index for Redirecting number = 1.1 and addition of "mp=1"

Index for Called party number = 1.1.1 and addition of "mp=1.1"

N

Index for Original called number = 1

Placeholder History entry with Index = 1.1 and addition of "mp=1"

…

Fill up

…

Index for Redirecting number = 1.[(N-1)* ".1"] and addition of "mp" header field parameter set to the hi-index value of the hi-targeted-to-uri that precede.

Index for Called party number = 1.N* ".1" (e.g. N=3  1.1.1.1) and addition of mp=1.[(N-1)*].1

Redirection information

Redirecting reason and

Original redirection reason

(NOTE 1)

hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113].

The Redirecting reason shall be mapped to the last hi-targeted-to-uri.

If the redirection counter is 2 or higher, the Original redirection Reason shall be mapped to the second hi-targeted-to-uri.

If the redirection counter is 3 or higher, for each hi-targeted-to-uri following a placeholder History-Info hi-entry the value "404" shall be taken (NOTE 2)

cause value

unknown/not available

404

unconditional

302

User Busy

486

No reply

408

Deflection during alerting

487

Deflection immediate response

480

Mobile subscriber not reachable

503

Called party number

See Redirecting number Nature of address indicator and Address signal

History-Info header field see hi-targeted-to-uri

URI of the last hi-targeted-to-uri entry of History-Info header field

Original called number

See Redirecting number Nature of address indicator and Address signal

History-Info header field see hi-targeted-to-uri

URI of first hi-targeted-to-uri entry of History-Info header field (NOTE 6, NOTE 9)

IF the Original called number is available:

set to the value of the Original

called number

ELSE

IF the Redirection counter equals

1 AND the Redirecting number is

available,

set to the value of the

Redirecting number

ELSE

set to the Unknown User

Identity (NOTE 10)

Original called number

APRI

Privacy header field of the first hi-targeted-to-uri entry of History-Info header

Priv-value

"presentation restricted"

"history"

"presentation allowed"

Privacy header field absent or "none"

NOTE 1: Original redirection reason contains the "unknown/not available" value. Based on operator agreement or national regulatory requirements other values of original redirection reason may be used.

NOTE 2: For all History-Info hi-entries except the first one a "cause" URI parameter as defined in IETF RFC 4458 [113] has to be included.

NOTE 3: If the Redirecting indicator has the value "Call diverted, all redirection information presentation restricted", the privacy value "history" shall be set.

NOTE 4: If the Redirecting number APRI has the value "presentation restricted", the privacy value "history" shall be set.

NOTE 5: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI.

NOTE 6: The used URI scheme can be tel URI or SIP URI since the first hi-targeted-to-uri entry of the History-Info header field does not contain the "cause" URI parameter.

NOTE 7: The hi-target-param defined in IETF RFC 7044 [91] defines the "mp" as a header field parameter that contains the value of the hi-index in the hi-entry with an hi-targeted-to-uri that reflects the Request-URI that was retargeted, thus identifying the "mapped from" target. Since the hi-entries are created based on the redirection counter to reflect the diverting/diverted-to entries, the hi-target-param "mp" header field parameter shall be present in each entry except the first one.

NOTE 8: If the Original called number parameter is not available and if the value of the Redirecting counter is equal to one, the Redirecting number parameter is used for the first hi-targeted-to-uri entry of the History-Info header field.

NOTE 9: If a further SIP to ISUP interworking occurs, parameters not present in the original message can then be included.

NOTE 10: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user’s identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74].

INVITE request

IAM

In History-Info SIP header field, hi-targeted-to-uri in hi-entry having a hi-index that match the "mp" header field parameter value of the last hi-entry containing an "mp" header field parameter and a "cause" URI parameter, as defined in IETF RFC 4458 [113]. (NOTE 1) (NOTE 3)

Redirecting number

hi-targeted-to-uri

appropriate global number portion of the URI, assumed to be in form
"+" CC + NDC + SN

CC

Nature of address indicator

If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to "national (significant) number" else set to "international number"

CC, NDC, SN

Address signals

If NOA is "national (significant) number" then set to
NDC + SN.

If NOA is "international number"

then set to CC + NDC + SN

Privacy header field or/and priv‑value component of the hi-entry in History-Info header field (NOTE 2)

APRI

If the priv-value "history" or "session" or "header" is received within the Privacy header field or if the priv-value "history" is received within the "headers" component of the hi-targeted-to-uri in hi-entry before last hi-entry containing a "cause" URI parameter then "presentation restricted" shall be set.

Otherwise, "presentation allowed" shall be set.

NOTE 1: If the SIP URI doesn’t contain "user=phone", mapping to redirecting number is impossible, therefore no need to generate Redirecting number.

NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header.

NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. If the "mp" header field parameter is missing in the last hi-entry containing a "cause" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the entry just before.

Privacy header field and priv‑value of hi-entry having a hi-index that match the "mp" header field parameter value of the last hi-entry containing an "mp" header field parameter and a "cause" URI parameter as defined in IETF RFC 4458 [113] of the History-Info header field. (NOTE 3)

"history" or "session" or "header"

for the Privacy header field or for the hi-targeted-to-uri entry

Redirecting indicator

Call diverted, all redirection information presentation restricted

Privacy header field and the privacy component of the hi-targeted-to-uri entry either absent

or

"none"

Call diverted

Original redirection reason

Unknown/not available (NOTE 4)

Cause value in the last hi-targeted-to-uri containing a "cause" URI parameter as defined in IETF RFC 4458 [113] (NOTE 3)

Cause parameter value

Redirecting reason

Redirecting reason

404

Unknown/not available

302

Unconditional

486

User busy

408

No reply

480

Deflection immediate response

487

Deflection during alerting

503

Mobile subscriber not reachable

History-Info header field

Redirection counter

number of History-Info hi-entry(ies) containing a "cause" URI parameter with value as listed as cause parameter value in this table (NOTE 1, NOTE 2)

NOTE 1: If the determined number of redirection in SIP exceeds the ISUP maximum parameter value, the MGCF shall set the Redirection counter to its maximum value. For instance, in ISUP ITU-T Q.763 [4], the Redirection counter parameter cannot exceed 5.

NOTE 2: The Redirection counter value will be incremented regardless of the SIP URI format.

NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. If the "mp" header field parameter is missing in the last hi-entry containing a "cause" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the entry just before.

NOTE 4: Based on the operator agreement or national regulatory requirements other values of original redirection reason may be used.

Numbering Plan Indicator

"ISDN (Telephony) numbering plan (Recommendation E.164)"

hi-targeted-to-uri of hi-entry having a hi-index that match the "mp" header field parameter value of the first hi-targeted-to-uri containing an "mp" header field parameter and a "cause" URI parameter, as defined in IETF RFC 4458 [113]; the

global number portion of the URI, is assumed to be in form
"+" CC + NDC + SN

(NOTE 1) (NOTE 3)

CC

Nature of address indicator

If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to "national (significant) number" else set to "international number"

CC, NDC, SN

Address signals

If NOA is "national (significant) number" then set to
NDC + SN.

If NOA is "international number"

then set to CC + NDC + SN

priv‑value component

in History-Info header field of the History-Info header field entry as defined above in this table (NOTE 2)

"history" or "session" or "header"

APRI

"presentation restricted"

Privacy header field absent or "none"

"presentation allowed"

NOTE 1: If it is SIP URI and doesn’t contain "user=phone", mapping to Original called number is impossible, therefore no need to generate Original called number.

NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header.

NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. If the "mp" header field parameter is missing in the first hi-entry containing a "cause" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the hi-entry preceding the first hi-entry containing the "cause" URI parameter.

History-Info header field

See table 7.5.4.3.2

Redirecting number

See table 7.5.4.3.2

History-Info header field

See table 7.5.4.3.3

Redirection information

See table 7.5.4.3.3

History-Info header field

See table 7.5.4.3.4

Original called number

See table 7.5.4.3.4

181 (Being forwarded)

ACM no indication with Redirection number and Call diversion information parameters (CFU, CFB, Cdi)

See table 7.5.4.3.8

180 (Ringing)

ACM indicating ringing, oBCi: "Call diversion may occur" (CFNR, Cda)

See subclause 7.2.3.1.4

181 (Being forwarded)

CPG indicating progress or subsequent diversion indicated in the CPG with Redirection number and Call diversion information parameters (CFNR, Cda)

See table 7.5.4.3.9

180 (Ringing)

CPG indicating ringing and Redirection number restriction parameter

See table 7.5.4.3.10

200 (OK)

ANM and Redirection number restriction parameter

See table 7.5.4.3.11

Presentation restricted indicator

"Presentation restricted"

privacy "headers" component of the hi-targeted-to-uri

"history"

"presentation allowed" or absent AND any previously received notification subscription options was NOT "presentation not allowed" AND was NOT "presentation allowed without redirection number"

Privacy header field absent

or

"none"

Generic notification indicator

Notification indicator

Call is diverting

Redirection number

History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter

hi-targeted-to-uri:

Nature of address indicator:

"national (significant) number"

hi-targeted-to-uri

Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI.

"international number"

Map complete Redirection number Address Signals to E.164 number in URI.

Address Signals

If NOA is "national (significant) number" then the format of the Address Signals is:

NDC + SN

If NOA is "international number"

then the format of the Address Signals is:

CC + NDC + SN

hi-targeted-to-uri

Addr-spec

"+" CC NDC SN mapped to userinfo portion of SIP URI. (NOTE 2)

Add "user=phone".

Call diversion information

Redirecting reason

IETF RFC 4458 [113] "cause" URI parameter in the hi-targeted-to-uri (NOTE 1)

cause value

Unknown

404

Unconditional

302

User busy

486

No reply

408

Deflection immediate response

480

Deflection during alerting

487

Mobile subscriber not reachable

503

Notification subscription options

privacy "headers" component of the hi-targeted-to-uri (NOTE 1)

unknown

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

presentation not allowed

A 181 Being Forwarded shall not be sent

presentation allowed with redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

presentation allowed without redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

NOTE 1: Needs to be stored for a possible inclusion into subsequent messages.

NOTE 2: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI.

Event information

Event Indicator

PROGRESS

Generic notification indicator

Notification indicator

Call is diverting

Redirection number

History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter

hi-targeted-to-uri:

Nature of address indicator

"national (significant) number"

hi-targeted-to-uri

Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI.

"international number"

hi-targeted-to-uri

Map complete Redirection number Address Signals to E.164 number in URI.

Address Signals

If NOA is "national (significant) number" then the format of the Address Signals is:

NDC + SN

If NOA is "international number"

then the format of the Address Signals is:

CC + NDC + SN

hi-targeted-to-uri

Addr-spec

"+" CC NDC SN mapped to userinfo portion of SIP URI. (NOTE 2)

Add "user=phone".

Call diversion information

Redirecting reason

IETF RFC 4458 [113] "cause" URI parameter in the hi-targeted-to-uri (NOTE 1)

cause value

Unknown

404

Unconditional

302

User busy

486

No reply

408

Deflection immediate response

480

Deflection during alerting

487

Mobile subscriber not reachable

503

Notification subscription options

privacy "headers" component of the hi-targeted-to-uri (NOTE 1)

unknown

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c

presentation not allowed

A 181 Being Forwarded shall not be sent

presentation allowed with redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c

presentation allowed without redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c

NOTE 1: Needs to be stored for a possible inclusion into subsequent messages.

NOTE 2: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI.

Event information

Event Indicator

ALERTING

Redirection number

History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter

See table 7.5.4.3.8

Call diversion information

Redirecting reason

IETF RFC 4458 [113]

"cause" URI parameter in the hi-targeted-to-uri (NOTE 1)

cause value

Unknown

404

Unconditional

302

User busy

486

No reply

408

Deflection immediate response

480

Deflection during alerting

487

Mobile subscriber not reachable

503

Notification subscription options

privacy "headers" component of the hi-targeted-to-uri (NOTE 1)

unknown

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

presentation not allowed

The 180 Ringing response shall be sent without the History-Info header field included

presentation allowed with redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

presentation allowed without redirection number

Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c

If no Call diversion information parameter is present

IETF RFC 4458 [113] "cause" URI parameter in the hi-targeted-to-uri

Value stored from a previously received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9.

privacy "headers" component of the hi-targeted-to-uri

Value stored from a previously received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9.

Redirection number restriction (NOTE 2)

See table 7.5.4.3.7

NOTE 1: Needs to be stored for a possible inclusion into subsequent messages.

NOTE 2: This parameter may appear without call diversion information parameter and redirection number. In such cases, the O-MGCF shall send the previously sent and stored History-Info header field and set the priv-value in the History-Info header field as described in table 7.5.4.3.7.

Redirection number

History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter

See table 7.5.4.3.8

IETF RFC 4458 [113] "cause" URI parameter in the hi-targeted-to-uri

Value stored from a previous received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9.

Redirection number restriction (NOTE)

See table 7.5.4.3.7

NOTE: This parameter may appear without Call diversion information parameter and Redirection number. In such cases, the O-MGCF shall send the previously sent and stored History-Info header field and set the priv-value in the History-Info header field as described in table 7.5.4.3.7.