In this section:
Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
An IMS Subscription stores the subscription data for an IMS user. This data is assumed to indicate the association of public and private identities and which Public User Identities within a subscription are shared and which are not. An IMS subscription supports multiple IMS users.
The SBC Core supports the following identity types:
Public identities can be grouped together to form an implicit registration set. The public identities in this set get implicitly registered via single IMS registration of one of the Public User Identity's in that set. No single public identity shall be considered as a master to the other Public User Identities. A simple diagram of implicit registration of Public User Identities is depicted below.
Public User Identities may be shared among multiple Private User Identities within the same IMS subscription. Hence a Public User Identity may be simultaneously registered from multiple UEs that use different Private User Identities and different contact addresses.
The following relationships are possible between Public User Identities and Private User Identities in IMS deployments: