Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
Symbols
- 3GPP
- 3GPP gateway
- charging rule
- charging rule installation
- charging rule removal
- charging rule report
- Charging-Rule-Base-Name
- Charging-Rule-Install
- Charging-Rule-Name
- configuration statements
- configuration summary
- directory-connection
- directory-eventing
- file logging
- grouped configurations
- Gx interface
- initial properties
- Juniper-Substitution
- Juniper-Substitution-Name
- Juniper-Substitution-Value
- local properties
- managing
- NIC proxies
- NIC proxy
- non-parameterized charging rule
- object adapter Internet address
- overview
- parameterized charging rule
- PCRF
- peer communication
- restarting
- SAE
- service accounting
- service activation sequence
- service deactivation sequence
- service modification sequence
- session termination sequence
- starting
- stopping
- subscriber login sequence
- subscriber logout sequence
- subscriber type
- system logging
- 3GPP Gy
- configuration statements
- configuration summary
- directory-connection
- directory-eventing
- file logging
- grouped configurations
- initial properties
- interface
- local properties
- managing
- NIC proxies
- NIC proxy
- object adapter Internet address
- overview
- peer communication
- restarting
- service activation sequence
- service deactivation sequence
- starting
- stopping
- subscriber login sequence
- subscriber logout sequence
- subscriber type
- system logging
- 3GPP Gy NIC proxies
A
- Application Services Gateway. See Web Services Gateway
- arguments for scripts and methods
- ASG (Application Services Gateway). See Web Services Gateway
B
- B2B environments
- business partner responsibilities
- business partners
- business-to-business environments
C
- classify-traffic condition
- expanded classifiers
- clients
- configuration namespace
- conventions
- customer support 1
D
- Diameter
- documentation
- dynamic properties
- Dynamic Service Activator
- access constraints
- access to attributes
- access to methods
- access to methods and scripts
- access to scripts
- access to service sessions
- API
- attributes
- configuring with C-Web interface
- configuring with SRC CLI
- gateway extension
- general properties
- groups
- interacting with Web application server 1, 2
- loading
- logging properties
- configuring, C-Web interface 1, 2
- configuring, SRC CLI
- methods 1
- monitoring with SRC CLI
- NIC proxies, monitoring
- NIC proxies, viewing
- overview
- properties for clients and scripts
- redundancy
- sample data 1, 2
- scripts
- service sessions
- session handles
- SOAP operations, monitoring
- SOAP operations, viewing
- starting with C-Web interface
- starting with SRC CLI
- statistics, viewing
- subscriber types
- test environment
- configuring, SRC CLI 1, 2
- PCMM services
- testing 1
E
G
- gateway
- gateway extension
I
- IMS service sessions
- configuring
- test environment
- testing 1, 2
L
M
- managing
- SAE via external applications 1, 2
- services via external application
- manuals
- methods
N
- namespace, configuration
- NIC (network information collector)
- Dynamic Service Activator and
- testing
- test data 1, 2
- test data, 3GPP Gy
- NIC proxies
- notice icons
O
- operation
P
R
S
- SAE (service activation engine)
- configuring 3GPP gateway as external plug-in
- configuring 3GPP Gy as external plug-in
- configuring IMS as external plug-in
- managing via external applications 1, 2
- scripts
- services
- sessions
- service
- SOAP
- SRC owners 1
- SRC SOAP Gateway. See Web Services Gateway
- static properties
- support, technical See technical support
T
- technical support
- text conventions defined
W
- Web application gateway client
- Web application server 1
- Web applications
- Web Services Description Language. See WSDL
- Web Services Gateway 1
- clients 1
- Web application
- wholesaler-retailer environments
- WSDL files
Related Documentation
- Configuring the Diameter Application (SRC CLI)
- Viewing SRC Diameter Server State (SRC CLI)
Configuring Diameter Peers (SRC CLI)
Use the following configuration statements to configure the Diameter peers:
shared network diameter peer name { protocol [(tcp | sctp)...];address [address...];enforce-source-address;local-address local-address;connect-timeout connect-timeout;watchdog-timeout watchdog-timeout;state-machine-timeout state-machine-timeout;reconnect-timeout reconnect-timeout;port port;origin-host origin-host;incoming-queue-limit incoming-queue-limit;active-peer;}
 | Note: When you commit the Diameter peer configuration, keep in mind the following conditions:
|
To configure the Diameter peer:
- From configuration mode, access the statements for the
peer.user@host# edit shared network diameter peer name
The peer name must be unique.
- Specify the protocol for the transport connection.[edit shared network diameter peer name]user@host# set protocol [(tcp | sctp)...]
- (Optional) Specify the addresses of the remote peer. If
SCTP is the transport protocol, you can specify multiple addresses.
If TCP is the transport protocol, you can specify only a single address.[edit shared network diameter peer name]user@host# set address [address...]
- (Optional) Specify whether the remote peer must connect
from one of the IP addresses listed by the address option.[edit shared network diameter peer name]user@host# set enforce-source-address
- (Optional) Specify the local address of the peer.[edit shared network diameter peer name]user@host# set local-address local-address
- (Optional) Specify the maximum amount of time allowed
for the Diameter peer to respond to a connection request.[edit shared network diameter peer name]user@host# set connect-timeout connect-timeout
- (Optional) Specify the watchdog timeout used for the connection
to the remote peer.[edit shared network diameter peer name]user@host# set watchdog-timeout watchdog-timeout
- (Optional) Specify the Diameter state machine timeout.[edit shared network diameter peer name]user@host# set state-machine-timeout state-machine-timeout
- (Optional) Specify the time interval between connection
attempts when the peer is in the disconnected state.[edit shared network diameter peer name]user@host# set reconnect-timeout reconnect-timeout
- (Optional) Specify the port for the client.[edit shared network diameter peer name]user@host# set port port
- (Optional) Specify the identifier for the endpoint that
the peer presents during connection establishment.[edit shared network diameter peer name]user@host# set origin-host origin-host
- (Optional) Specify the number of messages allowed on the
incoming message queue for a peer.[edit shared network diameter peer name]user@host# set incoming-queue-limit incoming-queue-limit
- (Optional) Specify whether the peer connection is in active
mode.[edit shared network diameter peer name]user@host# set active-peer
Note: Active mode means that the SRC software actively tries to connect to the peer. Make sure the peer you are connecting to supports active peers. The MX Series router does not support active peers. The SRC software can still be configured, but the connection attempts will not work.
Related Documentation
- Configuring the Diameter Application (SRC CLI)
- Viewing SRC Diameter Server State (SRC CLI)
