Elements of Oracle Communications Core Session Manager and SLRM Configuration
Oracle Communications Core Session Manager software is deployed as either the CSM or the SLRM component, as configured with the set component command. Each component consists of multiple configuration elements. This guide presents these elements, separating them along conceptual category with chapters roughly equating to configuration sequence. This section lists configuration elements, providing the reader with a consolidated picture of overall product configuration for both components.
Oracle documents this product using an Essentials model, which results in a unique OCUSM Essentials Guide document, and refers to the OCSBC Documentation Set for additional, related components, features and procedures. The documentation set, listed in the front matter of this document, provides configuration information across all session control products. The OCUSM and OCCSM filter out configuration elements, sub-elements and parameters that do not apply to themselves, preventing you from performing invalid configuration procedures.
See the Base Configuration Elements Appendix for minimal configuration setting examples that establish an operable OCCSM or OCSLRM.
CSM Configuration Elements
Required elements of initial device configuration for CSM, explained Getting Started chapter in the ACLI Configuration Guide, include:
- Boot Parameters
- Device Passwords
- Management Interfaces
- Default Gateway
- Product licensing
Required network and SIP service configuration elements, explained in multiple chapters in the ACLI Configuration Guide, include:
- Enable SIP-Config—System Configuration Chapter
- Default Gateway—System Configuration Chapter
- Service physical and network interface(s)—System Configuration Chapter
- SIP Interfaces—System Configuration Chapter
- SIP Ports—System Configuration Chapter
- Realms—Realms and Nested Realms Chapter
- Required IMS Core
configuration elements, explained in the
Oracle Communications Core Session Manager Supporting the IMS Core Chapter in this document,
include:
- Subscriber Database
- SIP Registrar
- ENUM for e.164 Translation
- Registration Event
Common Oracle Communications Core Session Manager Configuration Elements
Common configuration that may be needed for your CSM deployment includes:
- Session Agents
- ENUM Routing
- High Availability (HA)
- CDR Accounting Management
- SNMP Management
- Initial Filter Criteria (iFC)
- 3rd Party Registration Service
SLRM Configuration Elements
Required elements of initial device configuration for SLRM, explained in the Getting Started chapter, include:
- Boot Parameters, including identifying the primary management port
- Device Passwords
- Management Interfaces
Required network and SIP service configuration elements, explained in multiple chapters, include:
- Enable SIP-Config—System Configuration Chapter
- Default Gateway—System Configuration Chapter
- Service physical and network interface(s)—System Configuration Chapter
- SIP Interfaces—System Configuration Chapter
- SIP Ports—System Configuration Chapter
- Realms—Realms and Nested Realms Chapter
- Session Agents—Session Routing and Load Balancing Chapter
- ENUM—Routing with Local Policy Chapter
- Local Routing—Routing with Local Policy Chapter
- Elements of IMS Core
service configuration, explained in the
Oracle Communications Core Session Manager Supporting the IMS Core Chapter, include:
- Subscriber Database
- SIP Registrar
- Authentication Profile
- ENUM for e.164 Translation
Other Configuration Elements
Common secondary management element configuration includes:
- Additional management interface(s)
- CDR Accounting Management
- SNMP Management
Configuration elements that are available, but may not be required for your deployment include:
- Assorted SIP Functions
- Number Translation
- Admission Control and QoS
- DoS and other Security Functions
- Traffic Monitoring
See the Appendix on Base Configuration Elements for a list of configuration setting examples that bring your system to a minimally operational state in an IMS environment. Change addressing and other infrastructure-dependent setting examples to match that of your environment.