Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

1 Configuring Oracle WebLogic SIP Container

• 1.1 Oracle WebLogic SIP Container
  • 1.1.1 WebLogic Server 10.3 Platform Supports SIP and Converged Applications
• 1.2 Shared Configuration Tasks
  • 1.2.1 Shared Configuration Tasks for SIP Container and WebLogic Server
  • 1.2.2 Oracle WebLogic Server SIP Container Configuration Overview
    • 1.2.2.1 Diameter Configuration
  • 1.2.3 Methods and Tools for Performing Configuration Tasks
    • 1.2.3.1 Administration Console
    • 1.2.3.2 WebLogic Scripting Tool (WLST)
    • 1.2.3.3 Additional Configuration Methods
  • 1.2.4 Starting and Stopping Servers
  • 1.2.5 Administration Server Best Practices
  • 1.2.6 Common Configuration Tasks

2 Configuring SIP Servlet Container Properties

• 2.1 Overview of SIP Container Configuration
• 2.2 Using the Administration Console to Configure Container Properties
  • 2.2.1 Locking and Persisting the Configuration
• 2.3 Configuring Container Properties Using WLST (JMX)
  • 2.3.1 Managing Configuration Locks
  • 2.3.2 Locating the Oracle WebLogic Server SIP Container MBeans
• 2.4 WLST Configuration
  • 2.4.1 Invoking WLST
  • 2.4.2 Creating and Deleting MBeans
• 2.5 Configuring Timer Processing
  • 2.5.1 Configuring Timer Affinity (Optional)
  • 2.5.2 Configuring NTP for Accurate SIP Timers

3 Managing Network Resources

• 3.1 Overview of Network Configuration
  • 3.1.1 IPv4 and IPv6
• 3.2 Configuring Load Balancer Addresses
  • 3.2.1 Multiple Load Balancers and Multi-homed Load Balancers
• 3.3 Enabling Domain Name Service (DNS) Support
• 3.4 Configuring Network Channels for SIP or SIPS
  • 3.4.1 Reconfiguring an Existing Channel
  • 3.4.2 Creating a New SIP or SIPS Channel
  • 3.4.3 Configuring Custom Timeout, MTU, and Other Properties
  • 3.4.4 Configuring SIP Channels for Multi-Homed Machines
• 3.5 Configuring TCP and TLS Channels for Diameter Support
• 3.6 Configuring Engine Servers to Listen on Any IP Interface
• 3.7 Configuring Unique Listen Address Attributes for SIP Data Tier Replicas
• 3.8 Production Network Architectures and Configuration
  • 3.8.1 Single-NIC Configurations with TCP and UDP Channels
    • 3.8.1.1 Static Port Configuration for Outbound UDP Packets
  • 3.8.2 Multi-homed Server Configurations Overview
  • 3.8.3 Multi-homed Servers Listening On All Addresses (IP_ANY)
  • 3.8.4 Multi-homed Servers Listening on Multiple Subnets
    • 3.8.4.1 Understanding the Route Resolver
    • 3.8.4.2 IP Aliasing with Multi-homed Hardware
  • 3.8.5 Load Balancer Configurations
    • 3.8.5.1 Single Load Balancer Configuration
    • 3.8.5.2 Multiple Load Balancers and Multi-homed Load Balancers
    • 3.8.5.3 Network Address Translation Options
• 3.9 Example Network Configuration
  • 3.9.1 Example Network Topology
  • 3.9.2 Oracle WebLogic Server SIP Container Configuration
  • 3.9.3 Load Balancer Configuration
    • 3.9.3.1 NAT-based configuration
    • 3.9.3.2 maddr-Based Configuration
    • 3.9.3.3 rport-Based Configuration

4 Configuring SIP Data Tier Partitions and Replicas

• 4.1 Overview of SIP Data Tier Configuration
  • 4.1.1 datatier.xml Configuration File
  • 4.1.2 Configuration Requirements and Restrictions
• 4.2 Best Practices for Configuring and Managing SIP Data Tier Servers
• 4.3 Example SIP Data Tier Configurations and Configuration Files
  • 4.3.1 SIP Data Tier with One Partition
  • 4.3.2 SIP Data Tier with Two Partitions
  • 4.3.3 SIP Data Tier with Two Partitions and Two Replicas
• 4.4 Storing Long-Lived Call State Data In A RDBMS
  • 4.4.1 Requirements and Restrictions
  • 4.4.2 Steps for Enabling RDBMS Call State Storage
  • 4.4.3 Using the Configuration Wizard RDBMS Store Template
    • 4.4.3.1 Modify the JDBC Datasource Connection Information
  • 4.4.4 Configuring RDBMS Call State Storage by Hand
    • 4.4.4.1 Configure JDBC Resources
    • 4.4.4.2 Configure Oracle WebLogic Server SIP Container Persistence Options
    • 4.4.4.3 Create the Database Schema
  • 4.4.5 Using Persistence Hints in SIP Applications
• 4.5 Introducing Geo-Redundancy
  • 4.5.1 Situations Best Suited to Use Geo-Redundancy
  • 4.5.2 Situations Not Suited to Use Geo-Redundancy
  • 4.5.3 Geo-Redundancy Considerations: Before Your Begin
• 4.6 Using Geographically-Redundant SIP Data Tiers
  • 4.6.1 Example Domain Configurations
  • 4.6.2 Requirements and Limitations
  • 4.6.3 Steps for Configuring Geographic Persistence
  • 4.6.4 Using the Configuration Wizard Templates for Geographic Persistence
    • 4.6.4.1 Installing and Configuring the Primary Site
    • 4.6.4.2 Installing the Secondary Site
  • 4.6.5 Manually Configuring Geographical Redundancy
    • 4.6.5.1 Configuring JDBC Resources (Primary and Secondary Sites)
    • 4.6.5.2 Configuring Persistence Options (Primary and Secondary Sites)
    • 4.6.5.3 Configuring JMS Resources (Secondary Site Only)
  • 4.6.6 Understanding Geo-Redundant Replication Behavior
    • 4.6.6.1 Call State Replication Process
    • 4.6.6.2 Call State Processing After Failover
  • 4.6.7 Removing Backup Call States
  • 4.6.8 Monitoring Replication Across Regional Sites
  • 4.6.9 Troubleshooting Geographical Replication
• 4.7 Caching SIP Data in the Engine Tier
  • 4.7.1 Configuring Engine Tier Caching
  • 4.7.2 Monitoring and Tuning Cache Performance
• 4.8 Monitoring and Troubleshooting SIP Data Tier Servers

5 Monitoring and Troubleshooting

• 5.1 Avoiding and Recovering from Server Failures
  • 5.1.1 Failure Prevention and Automatic Recovery Features
    • 5.1.1.1 Overload Protection
    • 5.1.1.2 Redundancy and Failover for Clustered Services
    • 5.1.1.3 Automatic Restart for Failed Server Instances
    • 5.1.1.4 Managed Server Independence Mode
    • 5.1.1.5 Automatic Migration of Failed Managed Servers
    • 5.1.1.6 Geographic Redundancy for Regional Site Failures
  • 5.1.2 Directory and File Backups for Failure Recovery
    • 5.1.2.1 Enabling Automatic Configuration Backups
    • 5.1.2.2 Storing the Domain Configuration Offline
    • 5.1.2.3 Backing Up Server Start Scripts
    • 5.1.2.4 Backing Up Logging Servlet Applications
    • 5.1.2.5 Backing Up Security Data
    • 5.1.2.6 Backing Up Additional Operating System Configuration Files
  • 5.1.3 Restarting a Failed Administration Server
    • 5.1.3.1 Restarting an Administration Server on the Same Machine
    • 5.1.3.2 Restarting an Administration Server on Another Machine
  • 5.1.4 Restarting Failed Managed Servers
• 5.2 Overview of Failover Detection
  • 5.2.1 WlssEchoServer Failure Detection
  • 5.2.2 Forced Shutdown for Failed Replicas
• 5.3 Improving Failover Performance for Physical Network Failures
  • 5.3.1 Starting WlssEchoServer on SIP Data Tier Server Machines
  • 5.3.2 Enabling and Configuring the Heartbeat Mechanism on Servers
• 5.4 Configuring SNMP
  • 5.4.1 Browsing the MIB
  • 5.4.2 Steps for Configuring SNMP
• 5.5 Understanding and Responding to SNMP Traps
  • 5.5.1 Files for Troubleshooting
  • 5.5.2 Trap Descriptions
    • 5.5.2.1 connectionLostToPeer
    • 5.5.2.2 connectionReestablishedToPeer
    • 5.5.2.3 dataTierServerStopped
    • 5.5.2.4 overloadControlActivated, overloadControlDeactivated
    • 5.5.2.5 replicaAddedToPartition
    • 5.5.2.6 replicaRemovedEnginesRegistration
    • 5.5.2.7 replicaRemovedFromPartition
    • 5.5.2.8 serverStopped
    • 5.5.2.9 sipAppDeployed
    • 5.5.2.10 sipAppUndeployed
    • 5.5.2.11 sipAppFailedToDeploy
• 5.6 Using the WebLogic Diagnostics Framework (WLDF)
  • 5.6.1 Data Collection and Logging
  • 5.6.2 Watches and Notifications
  • 5.6.3 Image Capture
  • 5.6.4 Instrumentation
    • 5.6.4.1 Configuring Server-Scoped Monitors
    • 5.6.4.2 Configuring Application-Scoped Monitors
• 5.7 Logging SIP Requests and Responses
  • 5.7.1 Defining Logging Servlets in sip.xml
  • 5.7.2 Configuring the Logging Level and Destination
  • 5.7.3 Specifying the Criteria for Logging Messages
    • 5.7.3.1 Using XML Documents to Specify Logging Criteria
    • 5.7.3.2 Using Servlet Parameters to Specify Logging Criteria
  • 5.7.4 Specifying Content Types for Unencrypted Logging
  • 5.7.5 Enabling Log Rotation and Viewing Log Files
  • 5.7.6 trace-pattern.dtd Reference
  • 5.7.7 Adding Tracing Functionality to SIP Servlet Code
  • 5.7.8 Order of Startup for Listeners and Logging Servlets
• 5.8 Tuning JVM Garbage Collection for Production Deployments
  • 5.8.1 Modifying JVM Parameters in Server Start Scripts
  • 5.8.2 Tuning Garbage Collection with JRockit
  • 5.8.3 Using Oracle JRockit Real Time (Deterministic Garbage Collection)
  • 5.8.4 Using Oracle JRockit without Deterministic Garbage Collection
  • 5.8.5 Tuning Garbage Collection with Sun JDK
• 5.9 Avoiding JVM Delays Caused By Random Number Generation

6 Configuring Diameter Client Nodes and Relay Agents

• 6.1 Overview of Diameter Protocol Configuration
• 6.2 Steps for Configuring Diameter Client Nodes and Relay Agents
• 6.3 Installing the Diameter Domain
• 6.4 Enabling the Diameter Console Extension
• 6.5 Creating TCP, TLS, and SCTP Network Channels for the Diameter Protocol
  • 6.5.1 Configuring Two-Way SSL for Diameter TLS Channels
  • 6.5.2 Configuring and Using SCTP for Diameter Messaging
• 6.6 Configuring Diameter Nodes
  • 6.6.1 Creating a New Node Configuration (General Node Configuration)
  • 6.6.2 Configuring Diameter Applications
    • 6.6.2.1 Configuring the Sh Client Application
    • 6.6.2.2 Configuring the Rf Client Application
    • 6.6.2.3 Configuring the Ro Client Application
    • 6.6.2.4 Configuring a Diameter Relay Agent
    • 6.6.2.5 Configuring the Sh and Rf Simulator Applications
    • 6.6.2.6 Enabling Profile Service (using an Sh backend)
  • 6.6.3 Configuring Peer Nodes
  • 6.6.4 Configuring Routes
• 6.7 Example Domain Configuration
• 6.8 Troubleshooting Diameter Configurations

7 Oracle WebLogic Server SIP Container Base Platform Topologies

• 7.1 Goals of the Oracle WebLogic Server SIP Container Base Platform
• 7.2 Load Balancer
• 7.3 Engine Tier
• 7.4 SIP Data tier
  • 7.4.1 Example of Writing and Retrieving Call State Data
  • 7.4.2 RDBMS Storage for Long-Lived Call State Data
• 7.5 Geographically-Redundant Installations
• 7.6 Example Hardware Configurations
• 7.7 Alternate Configurations

8 Upgrading Deployed SIP Applications

• 8.1 Overview of SIP Application Upgrades
• 8.2 Requirements and Restrictions for Upgrading Deployed Applications
• 8.3 Steps for Upgrading a Deployed SIP Application
• 8.4 Assign a Version Identifier
  • 8.4.1 Defining the Version in the Manifest
• 8.5 Deploy the Updated Application Version
• 8.6 Undeploy the Older Application Version
• 8.7 Roll Back the Upgrade Process
• 8.8 Accessing the Application Name and Version Identifier
• 8.9 Using Administration Mode

A SIP Servlet Container Configuration Reference

• A.1 Overview of sipserver.xml
• A.2 Editing sipserver.xml
  • A.2.1 Steps for Editing sipserver.xml
• A.3 XML Schema
• A.4 Example sipserver.xml File
• A.5 XML Element Description
  • A.5.1 enable-timer-affinity
  • A.5.2 overload
    • A.5.2.1 Selecting an Appropriate Overload Policy
    • A.5.2.2 Overload Control Based on Session Generation Rate
    • A.5.2.3 Overload Control Based on Capacity Constraints
    • A.5.2.4 Two Levels of Overload Protection
  • A.5.3 message-debug
  • A.5.4 proxy—Setting Up an Outbound Proxy Server
  • A.5.5 t1-timeout-interval
  • A.5.6 t2-timeout-interval
  • A.5.7 t4-timeout-interval
  • A.5.8 timer-b-timeout-interval
  • A.5.9 timer-f-timeout-interval
  • A.5.10 max-application-session-lifetime
  • A.5.11 enable-local-dispatch
  • A.5.12 cluster-loadbalancer-map
  • A.5.13 default-behavior
  • A.5.14 default-servlet-name
  • A.5.15 retry-after-value
  • A.5.16 sip-security
  • A.5.17 route-header
  • A.5.18 engine-call-state-cache-enabled
  • A.5.19 server-header
  • A.5.20 server-header-value
  • A.5.21 persistence
  • A.5.22 use-header-form
  • A.5.23 enable-dns-srv-lookup
  • A.5.24 connection-reuse-pool
  • A.5.25 globally-routable-uri
  • A.5.26 domain-alias-name
  • A.5.27 enable-rport
  • A.5.28 image-dump-level
  • A.5.29 stale-session-handling
  • A.5.30 enable-contact-provisional-response
  • A.5.31 app-router
  • A.5.32 use-custom-app-router
  • A.5.33 app-router-config-data
  • A.5.34 custom-app-router-jar-file-name
  • A.5.35 default-application-name

B SIP Data Tier Configuration Reference

• B.1 Overview of datatier.xml
• B.2 Editing datatier.xml
• B.3 XML Schema
• B.4 Example datatier.xml File
• B.5 XML Element Description

C Diameter Configuration Reference

• C.1 Overview of diameter.xml
• C.2 Graphical Representation
• C.3 Editing diameter.xml
  • C.3.1 Steps for Editing diameter.xml
• C.4 XML Schema
• C.5 Example diameter.xml File
• C.6 XML Element Description
  • C.6.1 configuration
  • C.6.2 target
  • C.6.3 host
  • C.6.4 realm
  • C.6.5 address
  • C.6.6 port
  • C.6.7 tls-enabled
  • C.6.8 sctp-enabled
  • C.6.9 debug-enabled
  • C.6.10 message-debug-enabled
  • C.6.11 application
    • C.6.11.1 class-name
    • C.6.11.2 param*
  • C.6.12 peer-retry-delay
  • C.6.13 allow-dynamic-peers
  • C.6.14 request-timeout
  • C.6.15 watchdog-timeout
  • C.6.16 supported-vendor-id+
  • C.6.17 include-origin-state
  • C.6.18 peer+
    • C.6.18.1 host
    • C.6.18.2 address
    • C.6.18.3 port
    • C.6.18.4 protocol
  • C.6.19 route
    • C.6.19.1 realm
    • C.6.19.2 application-id
    • C.6.19.3 action
    • C.6.19.4 server+
  • C.6.20 default-route
    • C.6.20.1 action
    • C.6.20.2 server+

D Startup Command Options

E Supported Platforms, Protocols, RFCs and Standards

• E.1 Supported Configurations
• E.2 Supported SIP Clients
• E.3 Supported Load Balancer
• E.4 Supported Databases
• E.5 Overview of Oracle WebLogic Server SIP Container Standards Alignment
• E.6 Java Sun Recommendation (JSR) Standards Compliance
• E.7 IETF RFC Compliance
• E.8 3GPP R6 Specification Conformance

F Using Oracle WebLogic SIP Container Export/Import

• F.1 Export
  • F.1.1 Export the Database Data from the Current Environment
• F.2 Import

Index