PSX Globalization Summary
...
When the receives a globalized number in Request-URI, it uses that number to populate the called number in the policy request. The PSX uses the received number for call processing. However, when the Request-URI contains a number in "local number + phone-context" format, only the local number (represented by the user part of SIP URI ) is populated as the called number in policy request which the PSX uses for call processing. In this scenario the phone-context received in the incoming SIP message is not honored and hence not used for call processing. The honors phone-context received in R-URI using the honorPhoneContext flag configurable in the Feature Control Profile. When this flag is enabled, phone-context received in R-URI is honored and local number+phone-context is used for call processing.
Currently in PSX, a local number can be is globalized from the PSX using the globalization profile. When the “Globalize Flag” in the Globalization profile is enabled, the PSX copies the country code to the policy response and indicates to the that number has been is globalized, and to prepend the CC to called number before sending out the message to next hop. The uses the country-code received in policy response and appends to it a '+' followed by the called number and sends the global number is Egress Request-URI and To Header.
...
When the phoneContextParameterLength flag is configured in the SBC for
for a length greater than "0" for the globalized called number, the PSX sends the configured value in a policy response to the
SBC. The
SBC, in turn, uses this configured value to insert phone-context parameter of received length in
RURI and
To headers.
When the SBC flag
flag honorPhoneContextParameter is enabled, the
SBC uses uses the country-code received in policy response and appends to it a '+' followed by the called number and sends the global number is Egress Request-URI and To Header.
...
For configuration details, see refer to the following pages:
Honor Phone Context Parameter:
...