In this section:

Overview

Note

This feature is supported over the SBC-GW-GW-SBC scenario.


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:

Note

For all cases mentioned below, privacy transparency is enabled.


Ingress INVITE Display name

STI-VS Response

Egress INVITE

Comments

From: “ribbonUser”

PAI: “ribbonUser”

“verified” ribbonUser

From: “verified” ribbonUser 

PAI: “verified” ribbonUser


From: “ribbonUser”

PAI: “ribbonUser”

NONE

From: “ribbonUser”

PAI : “ribbonUser”

Falls back to default SBC behavior

From: “ribbon”

PAI: “ribbonUser”

NONE

From: “ribbonUser”

PAI: “ribbonUser”

Default behavior. Preference: PAI over From
From: “ribbon”“” ribbonFrom: “” ribbon


From: "ribbon"

PAI: "ribbon"

"verified" ribbon

From: “verified” ribbon

PAI: "verified" ribbon


From: "ribbon"

PAI: "ribbon"

""

From:<>

PAI: <>

If the STI-VS returns an empty string as a response, the display names of both From and PAI are empty.


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

Sub fieldNameLength
1Protocol Variant3 (SIP) / 5 (SIP-T)
2Call IDvariable(256)
3From Field256
4To Field256
5Redirect Attempt Count3
6Reserved0
7Display name47
8User parameter of P-K-CallForwardingLast Header24
9Userinfo and Hostname of SIP request URI header256
10User and hostname of SIP URI PAI header256
11USername parameter of the Proxy authorization header20
12displayname of Tel URI PAI header11
13INVITE contact header128
14200 OK INVITE contact header128
15Redirecting reason parameter of P-K-CallforwardingOriginal header4
16Userinfo of Tel URI PAI header127
17Contractor Number value of P-Sig-Info header16
18ACK Received for 200 OK1
19Status Msg for Call Release3
20Reason Header value Q8503
21NAPT Status of the SIP SG for Signaling1
22NAPT Status of the SIP SG for Media1
23Original Peer SDP Address for NAPT or ICE48
24UUI Sending Count2
25UUI Receiving Count2
26Service Information3
27ICID127
28Generated host for ICID127
29Originating IOI127
30Terminating IOI127
31P-K-Adn Header Number31
32IP Address for FQDN calls or IP address of route header selected as next hop48
33Transport Protocol1
34Direct Media Call1
35Inbound SMM Indicator1
36Outbound SMM Indicator1
37Originating Charge Area5
38Terminating Charge Area5
39Feature Tag in Contact Header200
40Feature Tag in Accept-Contact Header200
41P-Charging-Function-Address1024
42P-Called-Party-Id128
43P-Visited-Network-Id256
44Direct Media with NAPT Call1
45Ingress SMM Profile Name24
46Egress SMM Profile Name24
47P-Access-Network-Information header256
48IMS Node functionality2
49IMS node role1
50IMS Use PcfaCcf1
51P-CSCF calling party50
52P-CSCF called party50
53ICE used on Call1
54ICE Complete - Time-stamp when ICE Completes21
55Transit IOI List639
56Loop Back Ravel Call1
57Optimal Media Routing Applied1
58IMS PAI Service header64
59Feature-Caps header300
60Called Asserted Identity256
61NNI-Type1
62Neighbour Address39
63Relationship mode1
64Session direction1
65SMM CDR Field #1256
66SMM CDR Field #2256
67SMM CDR Field #3256
68SMM CDR Field #4256
69SMM CDR Field #5256
70Origination ID 36
71STI Service Type 1
72STI Service Status 1
73STI Reason Code

 3

74

Ingress Global SMM Profile Name

24

75

Egress Global SMM Profile Name  

24

76

Ingress AddrContext SMM Profile Name

24

77

Egress AddrContext SMM Profile Name 

24

78

Ingress Zone SMM Profile Name

24

79

Egress Zone SMM Profile Name 

24

80STI Display Name35
81AniDnis Loop Detection Fail1

For more information, refer to the following: