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
Configuring the SRC 3GPP Gateway Gx Interface (SRC CLI)
Use the following configuration statements to configure the SRC 3GPP gateway Gx interface:
slot number gw-3gpp gx { destination-host destination-host;destination-realm destination-realm;diameter-peer [diameter-peer.....];protocol (tcp | sctp);port port; address address; origin-host origin-host; origin-realm origin-realm; }
 | Note: The SRC 3GPP gateway uses its own Diameter stack, which is configured under the [edit slot 0 gw-3gpp gx] hierarchy. It does not use the Diameter stack configured under the [edit system diameter] hierarchy; this Diameter stack is used for SAE and router communication. |
To configure the SRC 3GPP gateway Gx interface:
- From configuration mode, access the statement that configures
the SRC 3GPP gateway Gx interface.user@host# edit slot 0 gw-3gpp gx
- (Optional) Specify the Diameter identifier for the remote
endpoint, which is the destination of the Diameter message. The Destination-Host
AVP (AVP Code 293) is of the DiameterIdentity type and is present
in all Diameter messages.[edit slot 0 gw-3gpp gx]user@host# set destination-host destination-host
- Specify the Diameter identifier for the realm of the remote
endpoint, which is the destination of the Diameter message. The Destination-Realm
AVP (AVP Code 283) is of the DiameterIdentity type and is present
in all Diameter messages.[edit slot 0 gw-3gpp gx]user@host# set destination-realm destination-realm
- Specify the list of remote Diameter peers (PCRFs) that
connect to the SRC 3GPP gateway over the Gx interface. [edit slot 0 gw-3gpp gx]user@host# set diameter-peer [diameter-peer....]
Each Diameter peer you specify must be previously configured under the [edit shared network diameter peer] hierarchy.
- (Optional) Specify the protocol for the transport connection.[edit slot 0 gw-3gpp gx]user@host# set protocol [(tcp | sctp)...]
- (Optional) Specify the port to use for incoming connections.[edit slot 0 gw-3gpp gx]user@host# set port port
- Specify the local address of the peer.[edit slot 0 gw-3gpp gx]user@host# set address address
- Specify the Diameter identifier for the local endpoint
that is the originator of the Diameter message.[edit slot 0 gw-3gpp gx]user@host# set origin-host origin-host
- Specify the Diameter identifier for the realm of the local
endpoint that is the originator of the Diameter message.[edit slot 0 gw-3gpp gx]user@host# set origin-realm origin-realm
- (Optional) Verify your configuration.
[edit slot 0 gw-3gpp gx] user@host# show address 10.10.10.10; destination-host testpcrf; destination-realm englab.juniper.net; diameter-peer [ primary-pcrf secondary-pcrf ]; origin-host duke; origin-realm example; port 3868; protocol tcp; }
Related Documentation
- SRC 3GPP Gateway Overview
- Configuration Statements for the SRC 3GPP Gateway
- Configuring the SRC 3GPP Gateway (SRC CLI)
