Support for Display Name Updates over STI-AS/VS API

Overview

The SBC's handling of the request (ingress INVITE) follows the conditions described below:

• If you configure the STI Profile, and From and P-Asserted-Identity (PAI) headers are present in the ingress INVITE, the SBC sends display names of both From and PAI headers to the PSX.
• If multiple PAI headers are present in the ingress INVITE, the SBC selects the display name based on the following order of preference:
  1. If a TEL URI with display name is present in the ingress INVITE, the SBC prioritizes it. If TEL URI does not have a display name, the SBC does not send display name from the PAI header to the PSX, even though the SIP URI have a display name.
  2. If multiple SIP URI with display name are present in the ingress INVITE, the SBC selects the SIP URI with userinfo as digits.  If the selected SIP URI does not have a display name, the SBC does not send display name from the PAI header to the PSX, even though other SIP URI headers have a display name.
  3. If no TEL URI/SIP URI with digits is present in the ingress INVITE, the SBC sends the topmost PAI header display name to the PSX. If the topmost PAI header does not have a display name, the SBC does not send any display name to the PSX.

• If the From header is present in the ingress INVITE, the SBC sends the display name from the From header to the PSX.

  Note

  The SBC supports a maximum length of 35 for display name strings at the D+ interfaces.

The SBC's handling of the response follows the conditions described below

• The PSX sends verified display name, and the SBC adds verified display name to the From and PAI header. The PSX sends display name responses per route.
• If multiple PAI headers are present in the INVITE, the SBC adds verified display name to all PAI headers.
• The SBC adds the received display name to both From and PAI header, even if the string is empty (“”).
• The privacy interactions of the SBC are as follows:
  • If the From header is anonymized, the SBC does not add the STI verified display name to the From header. In all other cases, the SBC adds the display name to both From and PAI headers.
  • If you enable sending PAI header in the egress, the SBC adds the STI verified display name to the PAI header, even though "Privacy: id" is present. 
  • If the PAI headers are removed due to privacy, the  SBC only adds the display name to From header.

For examples of SBC's behavior for the From and PAI headers, see the following table:

CAM Changes

The SBC adds the verified display name "STI Display Name" to the CDR record under Protocol Variant Specific String, as sub-field 80.

SIP Protocol Variant String

For more information, refer to the following:

• CAM Changes in This Release
• SIP-I Signaling Sub-field Descriptions