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 Diameter Node object 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 Diameter Node object 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 node name (<diameterNode_name>
) 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 information and 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.
When configuring a Diameter node in an HA configuration, the secondaryOriginHost
parameter must be configured with the Standby hostname.
Do not configure PCRF on the egress leg of the trunk group for REGISTER.
% set addressContext <addressContext_name> diamNode <diameterNode_name> dumpPdu <disabled | enabled> ipInterfaceGroupName <IPIG_name> ipV4Address <IPv4 address towards peer> ipV6Address <IPv6 address towards peer> originRealm <origin realm name> peer <peer_name> deviceWatchdogTimer <0-100000 ms> deviceWatchdogTimerAnswerTimeout <1000-500000 ms> fqdn <1-256 characters> ipAddress <IP address> sessionDistribution <honor-reply-order | round-robin> state <disabled | enabled> tcpPort <#> primaryOriginHost <primary host name> realmRoute <realmRoute_name> appId <e2 | rf | rx> peer <name> priority <0-100> realm <name> state <disabled | enabled> secondaryOriginHost <secondary host name> state <disabled | enabled> transactionTimeout <500-6000 milliseconds>
Diameter Node Parameters
Parameter | Length/Range | Description |
---|---|---|
| 1-23 |
|
dumpPdu | N/A | When this flag is enabled, the SBC logs the DIAMETER PDU sent and received on the Rx interface to the debug log.
This flag is not applicable if you are using the Diameter node for PC 2.0 LI. |
| N/A | The name of the IP interface group to use. |
| N/A | IPv4 address used to create connections towards peer. |
| N/A | IPv6 address used to create connections towards peer. |
| 0-128 | The origin realm for this node. |
| 0-23 | Use this parameter to define the Diameter peer configuration for this node.
|
| 0-128 | The primary origin host for this node. |
| 1-23 |
|
| 0-128 | The secondary origin host for this node. |
| N/A | Use this flag to set the state of this Diameter node.
|
| 500-6000 | Enter desired transaction timeout in milliseconds. (default = 1000) |
Example Diameter Node configuration:
% set addressContext ADDR_CONTEXT_1 diamNode diam ipInterfaceGroupName LIG1 ipV4Address 10.54.154.89 ipV6Address fe80::210:6bff:fe03:231 originRealm pcscf-open-ims.test primaryOriginHost katie secondaryOriginHost eleanor transactionTimeout 1500
Mandatory parameters:
Default Values:
Example Peer Configuration:
% set addressContext ADDR_CONTEXT_1 diamNode diam peer camiant.nj.sonusnet.com ipAddress 1.2.3.4 fqdn camiant.nj.sonusnet.com tcpPort 4868
Mandatory parameters:
Default values:
Example Realm Route Configuration:
% set addressContext ADDR_CONTEXT_1 diamNode diam realmRoute camiant.nj.sonusnet.com realm camiant.nj.sonusnet.com peer camiant.nj.sonusnet.com appId rx priority 1
Mandatory parameters:
Default values: