DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
Use the Diam Node window to define the parameters for the SBC side of a Diameter interface.
The SBC Core uses a connection over a Diameter interface for both quality of service (QoS) resource reservation requests and for transmitting lawful intercept (LI) information to mediation servers in deployments that follow the PacketCable 2.0 LI model. Within SBC configuration there is a single Diameter node object that is shared for both use cases.
In the first use case, the Rx interface pertains to QoS resource reservation for reserving bandwidth in an IP access network. The Rx interface is used to exchange application-level session information between a Policy and Charging Rules Function (PCRF) element and the P-CSCF. The SBC, acting as a P-CSCF, creates a TCP connection with the configured PCRF. For this case, you use the Diam Node window to configure the Diameter realm for sending external QoS requests on a per-IP-trunk-group basis.
In the second case, the SBC uses a Diameter-based interface (X2 interface) over TCP transport to send intercepted call data and associated call events from the SBC to an LI mediation server. In general, LI configuration must be completed by a user with specific LI privileges (the calea
user). However because the Diameter node object is also used for a non-LI purpose, the name of the Diameter node must be assigned, as described on this page, by a user with admin
privileges. You then include the Diameter node name in the LI call data channel (CDC) configuration. However, the remaining Diameter configuration required to support PC 2.0 LI (Diameter peers and Diameter realm routes), must be completed by the calea
user within CDC configuration. Refer to PacketCable 2.0 LI Configuration for more information and to Configure CDC for PacketCable 2.0 (EMS documentation) for procedures for configuring Diameter parameters for PC 2.0 LI deployments.
The SBC 5210 and SBC 7000 systems support creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 5110 and 5400 systems which have only two physical media ports. IP interfaces from the two physical ports may be configured within the same IP Interface Groups without restrictions.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
Do not configure PCRF on the egress leg of the trunk group for REGISTER.
When configuring the Diameter node in an HA configuration, the Secondary Origin Host parameter must be configured with the Standby hostname
On the SBC main screen, navigate to All > Address Context > Diam Node.
The Diam Node window opens. In Address Context, select the address context for the Diameter node.
To create the Diam Node:
Click New Diam Node. The Create New Diam Node window opens.
To edit the Diam node configuration:
To delete the Diam Node configuration: