Cisco Cisco Tunnel Terminating Gateway (TTG)
Diameter Endpoint Configuration Mode Commands
peer ▀
Command Line Interface Reference, StarOS Release 16 ▄
3439
port port_number
Specifies the port number for this Diameter peer. The port number must be an integer from 1 through 65535.
connect-on-application-access
Activates peer on first application access.
send-dpr-before-disconnect
Sends Disconnect-Peer-Request (DPR).
disconnect-cause
Sends Disconnect-Peer-Request to the specified peer with the specified disconnect reason. The disconnect
cause must be an integer from 0 through 2, for one of the following:
cause must be an integer from 0 through 2, for one of the following:
REBOOTING(0)
BUSY(1)
DO_NOT_WANT_TO_TALK_TO_YOU(2)
rlf-template rlf_template_name
Specifies the RLF template to be associated with this Diameter peer.
rlf_template_name
must be an alphanumeric string of 1 through 127 characters.
Important:
Rate Limiting Function (RLF) is a license-controlled feature. A valid feature license must be
installed prior to configuring this feature. Contact your Cisco account representative for more information.
Important:
Peer level RLF template takes precedence over the endpoint level template.
sctp
Uses Stream Control Transmission Protocol (SCTP) for this peer.
+
Indicates that more than one of the previous keywords can be entered within a single command.
Usage
Use this command to add a peer to the Diameter endpoint.
If the Diameter server side endpoint is catering to multiple peers, there has to be an entry for each peer in the
peer list for that endpoint.
In cases where the client like GGSN does not use a diameter proxy, the peer list can be as large as the number
of session managers on a GGSN. This might lead to a very complex configuration at the Diameter server
endpoint.
To simplify the configurations, the Diameter server endpoint accepts a wildcarded peer name (with * as a
valid wildcard character).
The client peers which satisfy the wild-carded pattern are treated as valid peers and the connection will be
accepted. The new token ‘wildcarded*’ indicates that the peer name is wildcarded and any ‘*’ in the
preceding string should be treated as a wildcard.
If the Diameter server side endpoint is catering to multiple peers, there has to be an entry for each peer in the
peer list for that endpoint.
In cases where the client like GGSN does not use a diameter proxy, the peer list can be as large as the number
of session managers on a GGSN. This might lead to a very complex configuration at the Diameter server
endpoint.
To simplify the configurations, the Diameter server endpoint accepts a wildcarded peer name (with * as a
valid wildcard character).
The client peers which satisfy the wild-carded pattern are treated as valid peers and the connection will be
accepted. The new token ‘wildcarded*’ indicates that the peer name is wildcarded and any ‘*’ in the
preceding string should be treated as a wildcard.