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. 


Note

The  SBC 7000 system supports 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 5400 system 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.

Command Syntax

% 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>

Command Parameters

Diameter Node Parameters

Parameter

Length/Range

Description

diamNode

1-23

<diameterNode_name> – Diameter node name. If you are configuring the SBC for PC 2.0 LI, use this name in the LI CDC. Refer to PacketCable 2.0 LI Configuration.

dumpPduN/A

When this flag is enabled, the SBC logs the DIAMETER PDU sent and received on the Rx interface to the debug log.

  • disabled (default)
  • enabled

This flag is not applicable if you are using the Diameter node for PC 2.0 LI.

ipInterfaceGroupName

N/A

The name of the IP interface group to use.

ipV4Address

N/A

IPv4 address used to create connections towards peer.

ipV6Address

N/A

IPv6 address used to create connections towards peer.

originRealm

0-128

The origin realm for this node.

peer

0-23

Use this parameter to define the Diameter peer configuration for this node.

  • deviceWatchdogTimer – Device-Watchdog-Requests timer value, in milliseconds (range: 0-100000 / default=1000).
  • deviceWatchdogTimerAnswerTimeout – The Device Watchdog Answer timeout value, in milliseconds. SBC considers a peer down if a Device Watchdog Request is not replied to by a Device Watchdog Answer before this timer expires. (range: 1000-500000 | default = 2000)
  • fqdn – FQDN for this peer (1-256 characters).
  • ipAddress – IP Address of this peer.
  • sessionDistribution – Use this parameter to specify how to distribute Diameter sessions.

    • honor-reply-order (default) – Diameter session creation across multiple IP connections under this peer honors the order of the IP addresses that are returned in the DNS reply starting from the first one.

    • round-robin – Diameter session creation across multiple IP connections under this peer are rotated in round-robin fashion starting from the first one.

  • state – Admin state of this peer.
    • disabled (default)
    • enabled
  • tcpPort – TCP port number of this peer (default is 3868).

primaryOriginHost

0-128

The primary origin host for this node.

realmRoute

1-23

<realmRoute name> – Realm route for this node. Additional realm route arguments:

  • appId – Application ID (Diameter interface type) for this route.
    • e2
    • rf
    • rx (default is rx for the PCRF interface)
    • x2 (applies only when using Diameter to support PC 2.0 LI)
  • peer – The name of the peer this route belongs to.
  • priority – Priority of this Route. (range 0-100 / default = 0)
  • realm – Realm name of this route.
  • state– Administrative state of this peer.
    • disabled (default)
    • enabled

secondaryOriginHost

0-128

The secondary origin host for this node.

state

N/A

Use this flag to set the state of this Diameter node.

  • disabled (default)
  • enabled

transactionTimeout

500-6000

When transactionTimeout is configured, the SBC intiates retransmission of the diameter message after the configured value + 1.1 secs (1.1secs is hardcoded value in SBC). For example, if the configured value of transactionTimeout is 1000 (1 sec), then the SBC will initiate retransmission of the diameter message after 2.1 secs. The SBC supports only one diameter retransmission.

Command Example (P-CSCF/PCRF Use Case)

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:

  1. At least one IP address is required (ipV4Address or ipV6Address)
  2. diamNode name
  3. primaryOriginHost name
  4. ipInterfaceGroupName
  5. originRealm name

Default Values:

  • state = disabled
  • transactionTimeout = 1000 ms


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:

  1. fqdn
  2. ipAddress
  3. peer name

Default values:

  • state = disabled
  • tcpPort = 3868

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:

  1. peer name
  2. realm
  3. realmRoute name

Default values:

  • appId = rx (for PCRF interface)
  • state = disabled
  • priority = 0