Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||||
---|---|---|---|---|---|---|
In this section:
|
Available_since | ||
---|---|---|
|
Use the Diameter Node object to define the parameters for the SBC side of a Diameter interface.
The
Spacevars | ||
---|---|---|
|
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.
Include Page | ||||
---|---|---|---|---|
|
Note |
---|
When configuring a Diameter node in an HA configuration, the |
Note |
---|
Do not configure PCRF on the egress leg of the trunk group for REGISTER. |
Code Block | ||||
---|---|---|---|---|
| ||||
% 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> |
Code Blockcaption | |||||
---|---|---|---|---|---|
| |||||
% set addressContext default diamNode <node name>
originRealm <realm name>
primaryOriginHost <Host name>
secondaryOriginHost <Secondary host>
state <disabled | enabled>
ipInterfaceGroupName <IG Name>
networkSegmentName <Network Segment name>
ipNameV4 <IPv4 address>
ipNameV6 <IPv6 address>
peer <peer name>
state <disabled | enabled>
ipAddress <IPv4 address>
fqdn <FQDN>
tcpPort <port>
deviceWatchdogTimer <timer value>
deviceWatchdogTimerAnswerTimeout <timeout value>
realmRoute <Realm Route name>
peer <Peer name>
realm <Realm>
appId rx
state <disabled | enabled> |
Parameter | Length/Range | Description | ||||
---|---|---|---|---|---|---|
| 1-23 |
| ||||
dumpPdu | N/A | When this flag is enabled, the
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 |
When transactionTimeout is configured, the SBC initiates 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. |
Parameter | Length/Range | Description | ||||
---|---|---|---|---|---|---|
| 1-23 |
| ||||
dumpPdu | N/A | When this flag is enabled, the
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. | ||||
| 1-23 | The IPv4 address variable name. | ||||
| 1-23 | The IPv6 address variable name. | ||||
| N/A | Name of the Network Segment ID. | ||||
| 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 | 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. |
Example Diameter Node configuration:
Code Block | ||
---|---|---|
| ||
% 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:
diamNode
nameprimaryOriginHost
nameipInterfaceGroupName
originRealm
nameDefault Values:
Example Diameter Node Configuration for SBC CNe
Code Block |
---|
set addressContext default diamNode Diam originRealm pcscf-rf-ims.test primaryOriginHost pcrf1 secondaryOriginHost pcrf2 networkSegmentName sg-default-pkt0 ipNameV4 SGPKT0 ipInterfaceGroupName LIGSG state enabled |
Mandatory Parameters
ipNameV4
or ipNameV6
) and networkSegmentName
is required.diamNode
nameprimaryOriginHost
nameipInterfaceGroupName
originRealm
nameDefault Values:
Requirements:
ipNameV4
/ipNameV6
unless the diamNode
is in disabled state.ipAddress
(networkSegmentName
) assigned for the diamNode
is from the new Network Segment Table NsTableType
="NS_SG
".ipInterfaceGroup
associated with the diamNode
contains at least one ipInterface
of type NS_SG
on non-PFE deployments.ipAddress
(networkSegmentName
) assigned for the diamNode
is from the new Network Segment Table NsTableType
="PFE
" on non-PFE deployments.ipInterfaceGroup
associated with the diamNode
contains at least one ipInterface
of type PFE
(for PFE deployments) or type SG
(for non-PFE deployments).ipAddress
/ipMetaVar
are hidden for CNF.ipName
is in use by the diamNode
.
Example Peer Configuration:
Code Block | ||
---|---|---|
| ||
% 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:
Code Block | ||
---|---|---|
| ||
% 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: