L.1 Interworking SIP to ISUP

29.1633GPPInterworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networksTS

The I-MGCF may perform the following procedure based on the operator policy, if the called IN number and original called IN number parameters are supported in the CS network.

When receiving the History-Info header field in the incoming initial INVITE request, the I-MGCF may include a called IN number and an original called IN number parameters in the outgoing IAM as shown in table L.1.1 and table L.1.2.

Table L.1.1: Mapping of History-Info header field to called IN number

Source SIP header field and component

Source Component value

called IN number

Derived value of parameter field

Numbering plan indicator

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

hi-targeted-to-uri of the hi-entry with a hi-index that matches the last hi-entry with cause-param URI parameter with the value "380" defined in IETF RFC 8119 [148] and a mp-param header field parameter (NOTE 3);

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 I-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 Privacy header field escaped in the hi-entry above identified. (NOTE 2).

"history" or "session" or "header"

APRI

"presentation restricted"

Privacy header field absent or "none"

"presentation allowed"

NOTE 1: If the hi-targeted-to-uri is a SIP URI and does not contain "user=phone", then mapping to called IN number is impossible; therefore, there is no need to generate called IN 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 field.

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 shall appear in this hi-targeted-to-uri. Due to backward compatibility rules the hi-target-param may not appear in each concerned hi-entry; so that the identification of the hi-entry shall rely on the cause-param value.

Table L.1.2: Mapping of History-Info header field to original called IN number

Source SIP header field and component

Source Component value

original called IN number

Derived value of parameter field

Numbering plan indicator

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

hi-targeted-to-uri of the hi-entry with a hi-index that matches the first hi-entry with a cause-param URI parameter with the value "380" defined in IETF RFC 8119 [148] and a mp-param header field parameter (NOTE 4);

the global number portion of the hi-targeted-to-uri is assumed to be in form
"+" CC + NDC + SN (NOTE 2).

CC

Nature of address indicator

If CC is equal to the country code of the country where I-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 Privacy header field escaped in the hi-entry above identified (NOTE 3).

"history" or "session" or "header"

APRI

"presentation restricted"

Privacy header field absent or "none"

"presentation allowed"

NOTE 1: The original called IN number is generated only when there are more than two hi-entries having a cause URI parameter set to the value defined in IETF RFC 8119 [148].

NOTE 2: If the hi-targeted-to-uri is a SIP URI and does not contain "user=phone", then mapping to original called IN number is impossible; therefore, there is no need to generate original called IN number.

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

NOTE 4: 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 shall appear in this hi-targeted-to-uri. Due to backward compatibility rules the hi-target-param may not appear in each concerned hi-entry; so that the identification of the hi-entry shall rely on the cause-param value.