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
Creating Grouped Configurations for IMS (SRC CLI)
Configuration groups allow you to share the IMS configuration with different IMS instances in the SRC network. You can also set up different configurations for different instances.
You can then create a grouped IMS configuration that is shared with some IMS instances. For example, if you create two different IMS groups called config1 and config2 within the shared IMS configuration, you could select the IMS configuration that should be associated with a particular IMS instance.
Use the shared option of the slot number ims statement to select the group for an IMS instance as part of the local configuration. Use the shared ims group name configuration statements to configure the group.
To select and configure a group:
- From configuration mode, select a group for an IMS instance.
For example, to select a group called config1 in the root group:[edit]user@host# set slot 0 ims shared /config1
- Commit the configuration. [edit]user@host# commit commit complete.
- From configuration mode, configure a group. For example,
to configure a group called config1, specify the group as part of
the IMS configuration. [edit]user@host# edit shared ims group config1 ? Possible completions: <[Enter]> Execute this command > configuration | Pipe through a command
For more information, see Configuring the IMS Software (SRC CLI).
Related Documentation
- Configuring the IMS Software (SRC CLI)
- Configuring the Subscriber Type (SRC CLI)
- Configuring a NIC Proxy for IMS (SRC CLI)
- Configuring IMS for Failover (SRC CLI)
- IMS Environment Overview
