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 SAE for External Plug-Ins (SRC CLI).
- Special Types of Event Publishers
- Configuring the SAE for External Plug-Ins (SRC CLI)
- Special Types of Event Publishers
Configuring the SAE for IMS
You must configure the SAE to recognize IMS by adding information about IMS to the SAE properties. Tasks for configuring the SAE for IMS are:
Configuring IMS as an External Plug-In
To configure an external plug-in for the SAE:
- From configuration mode, access the statement that configures
the external plug-ins. user@host# edit shared sae configuration plug-ins name name external
- Configure the object reference of the external plug-in
that is exported to the SAE. [edit shared sae configuration plug-ins name name external] user@host# set corba-object-reference corba-object-reference
where corba-object-reference is one of the following references:
- Path to the interoperable object reference (IOR) file in the format file:///opt/UMC/ims/var/run/ims.ior
- The corbaloc URL in the format corbaloc::host:9801/ASGIMS where host is the IP address of the C Series Controller or 127.0.0.1
- Common Object Services (COS) in the format corbaname::host:2809#ASGIMS/statesync/hostname or corbaname::host:2809/NameService#ASGIMS/statesync/hostname where
- host is the IP address of the C Series Controller
- hostname is the hostname of the C Series Controller
- Specify the plug-in attributes. [edit shared sae configuration plug-ins name name external] user@host# set attributes ?
Attributes for IMS are service-name, service-session-name, router-name, login-name, terminate-cause, property.
For more information about configuring plug-in attributes, see Configuring the SAE for External Plug-Ins (SRC CLI).
Configuring Event Publishers
You must configure the SAE to publish the global service tracking events to the IMS. Any other events are ignored.
For information about configuring event publishers, see Special Types of Event Publishers.
Related Documentation
- Configuring the SAE for External Plug-Ins (SRC CLI)
- Special Types of Event Publishers
