The Ribbon DSC’s main functionality is to route acceptable incoming Diameter messages to the appropriate destination using relay or redirection as required.

The Ribbon DSC supports default capabilities and is designed to allow routing with a minimum of provisioning. Using the default capabilities, the functionality of each new Diameter connection is tracked as long as the connection provides the necessary routing information. The routing information then is used with default routing to provide quick and easy setup and functionality for the Ribbon DSC.

When an Adjacent Diameter Node (ADN) establishes connections, this node publishes its capabilities by sending a configuration dependent Capabilities Exchange Request (CER) or a Capabilities Exchange Answer (CEA) message. These CE messages may contain Vendor ID and Application ID AVPs. The message header contains an Application ID (refer to Message Format). This information is then stored and shared to each DSC process for use by default routing. The information shared contains which DSC process has access to the ADN connection, and the ADN's Vendor ID, Application ID, and Application Type (Authorization or Accounting). This information is displayed with the status of the ADN connection in the DSC Web UI.

The ADN Connections UI has Peer Identity attributes that identify the ADN in an ADN Connection. The Peer Identity attributes are the Vendor-Id, the Product-Name, and the Firmware-Revision. The DSC Node populates the Peer Identity attributes with the retrieved values and adds an entry that identifies the ADN to the debug log when a connection is successfully established with the ADN.

Note

If the ADN connection is inactive or goes down, the Advertised Capabilities are cleared but the ADN's Peer Identity information on the UI are not cleared. Instead, the debug log adds an entry that identifies the ADN connection and the Peer Identity and Advertised Capabilities information.

The DSC routing tables (refer to Routing of Diameter Signaling Traffic using Routing Tables) are used to provision more complex and powerful routing based on incoming Adjacent Diameter Node (ADN), Command Code, AVPs, and/or Application IDs.

Related Articles:

  • No labels