Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
JIRAIDAUTHSBX-130992
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b802fd, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7d0460, userName='null'}



Panel

In this section:

Table of Contents
maxLevel2



Info
iconfalse

Related articles:

Children Display


Use the Diam Node window to define the parameters for the SBC side of a Diameter interface.

The 

Spacevars
0series4
 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 for more information and to . 

Refer to one of the following pages for procedures for configuring Diameter parameters for PC 2.0 LI deployments:

documentation
  • )
for procedures for configuring Diameter parameters for PC LI deployments.
  • (RAMP)

Include Page
_IP_IGs_ServedBySeperateProcessors
_IP_IGs_ServedBySeperateProcessors

Note

Do not configure PCRF on the egress leg of the trunk group for REGISTER.


Note

When configuring the Diameter node in an HA configuration, the Secondary Origin Host parameter must be configured with the Standby hostname

To View Diam Node Configuration

On the

Spacevars
0product
 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.

Figure 1: Diam Node Window

To Create the Diam Node

To create the Diam Node:

  1. Click New Diam Node. The Create New Diam Node window opens.

    Image Modified

  2. Use the following table to configure the fields and then click Save.
    Table 1: Diam Node Parameters

    Parameter

    		Length/Range

    Description

    Name

    		1-23 characters

    The name of this Diameter node. If you are configuring the SBC for PC 2.0 LI, use this name in the LI CDC configuration. 

    Refer to one of the following pages for more information:

    documentation
    • )
    for more information.

    Origin Realm

    		1-128 characters

    The origin realm for the node.

    Primary Origin Host

    		1-128 characters

    The primary origin host for the node.

    Secondary Origin Host

    		1-128 characters

    The secondary origin host for the node.

    Transaction Timeout

    		500-6000

    The timeout value in milliseconds, with a default value of 1000.

    State

    		N/A

    The state of the Diameter node.

    • Disabled (default)
    • Enabled

    Dump Pdu

    		N/A

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

    • Disabled (default)
    • Enabled

    Multiexcerpt include
    MultiExcerptNameDump PDU intro
    PageWithExcerptDiameter Message Tracing

    Use this feature to print the incoming/outgoing PDU (Protocol Data Unit) of this Diameter Node for either DBG or TRC logs.

    • Off (default) – Stop printing the PDU.
    • Dbg – Print the PDU in the DBG log.
    • Trc – Print the PDU in the TRC log.

    Refer to Diameter Message Tracing for additional information.

    Info

    This flag is not applicable when

    This option is not applicable if you are

    using the Diameter node for PC 2.0 LI.


    IP Interface Group Name

    		N/A

    The name of the IP Interface group to use.

    IP V4Address

    		N/A

    The IPv4 address used to create connections towards a peer.

    IP V6Address

    		N/A

    The IPv6 address used to create connections towards a peer.


To Edit the Diam Node

To edit the Diam node configuration:

  1. Click the radio button next to the Diam node name. The Edit Selected Diam Node window opens.
  2. Make any required changes and click Save.

To Delete the Diam Node 

To delete the Diam Node configuration:

  1. Click the radio button next to the Diam node you want to delete.
  2. Click the Delete icon the "Delete" icon (X) at the end of the row.
  3. Confirm the deletion when prompted.