Configuring Engine Servers to Listen on Any IP Interface
4.7 Configuring Unique Listen Address Attributes for SIP Data Tier Replicas
Each replica in the SIP data tier must bind to a unique Listen Address attribute a unique multi-home name or IP address in order to contact one another as peers. Follow these instructions for each replica to assign a unique Listen Address: 1. Access the Administration Console for the Oracle WebLogic Communication Services domain.2. Select Environment Servers from the left pane.
3. In the right pane, select the name of the server to configure.4. Select the Configuration General tab.
5. Enter a unique DNS name or IP address in the Listen Address field.6. Click Save.
4.8 Production Network Architectures and Configuration
Most production Enterprise Deployment installations of Oracle WebLogic Communication Services contain one or more of the following characteristics: ■ Multiple engine tier servers arranged in a cluster. ■ Multiple network channels per engine tier server instance, in support of multiple SIP transport protocols or multiple Network Interface Cards NICs on multi-homed hardware. ■ One or more load balancers, or a multi-homed load balancer, performing server failover and possibly Network Address Translation NAT for source or destination network packets. A combination of these network elements can make it difficult to understand how elements interact with one another, and how a particular combination of elements or configuration options affects the contents of a SIP message or transport protocol datagram. The sections that follow attempt to describe common Oracle WebLogic Communication Services network architectures and explain how servers are configured in each architecture. The sections also explain how information in SIP messages and transport datagrams is affected by each configuration. Figure 4–1 shows the typical Open Systems Interconnect OSI model layers that can be affected by different network configurations. Note: Using the 0.0.0.0 configuration affects only UDP traffic on Linux platforms. Oracle WebLogic Communication Services only creates TCP and HTTP listen threads corresponding to the configured host name of the server, and localhost. If multiple addresses are mapped to the host name, Oracle WebLogic Communication Services displays warning messages upon startup. To avoid this problem and listen on all addresses, specify the :: address, which encompasses all available addresses for both IPv6 and IPv4 for HTTP and TCP traffic as well. Managing Network Resources 4-9 Figure 4–1 OSI Layers Affected by Oracle WebLogic Communication Services Network Configuration Layer 3 Network and Layer 4 Transport contain the source or destination IP address and port numbers for both outgoing and incoming transport datagrams. Layer 7 Application may also be affected because the SIP protocol specifies that certain SIP headers include addressing information for contacting the sender of a SIP message.4.8.1 Single-NIC Configurations with TCP and UDP Channels
In a simple network configuration for a server having a single NIC, one or more network channels may be created to support SIP messages over UDP and TCP, or SIPS over TLS. It is helpful to understand how this simple configuration affects information in the OSI model, so that you can understand how more complex configurations involving multi-homed hardware and load balancers affect the same information. Figure 4–2 Single-NIC Network Channel Configuration Figure 4–2 shows a single engine tier server instance with a single NIC. The server is configured with one network channel supporting SIP over UDP and TCP. SIP channels always support both UDP and TCP transports; you cannot support only one of the two. Figure 4–2 also shows two clients communicating with the server, one over UDP and one over TCP. For the TCP transport, the outgoing datagram delivered from Oracle WebLogic Communication Services to the UA contains the following information:Parts
» Oracle Fusion Middleware Online Documentation Library
» Messaging Oracle WebLogic Communication Services
» Telephony Oracle WebLogic Communication Services
» Presence Oracle WebLogic Communication Services
» WebLogic Server 10.3 Platform with support for SIP and converged applications
» Shared Configuration Tasks for Oracle WebLogic Communication Services and Oracle WebLogic Server
» Diameter Configuration Oracle WebLogic Communication Services Configuration Overview
» Administration Console Methods and Tools for Performing Configuration Tasks
» WebLogic Scripting Tool WLST
» Editing Configuration Files Additional Configuration Methods
» Setting Log Levels You can set log levels by manually editing the
» Starting and Stopping Servers
» Administration Server Best Practices Common Configuration Tasks
» Overview of SIP Container Configuration
» Locking and Persisting the Configuration
» Managing Configuration Locks Configuring Container Properties Using WLST JMX
» Locating the Oracle WebLogic Communication Services MBeans
» Invoking WLST WLST Configuration
» Configuring Timer Affinity Optional
» Configuring NTP for Accurate SIP Timers
» IPv4 and IPv6 Overview of Network Configuration
» Multiple Load Balancers and Multi-homed Load Balancers
» Enabling Domain Name Service DNS Support
» Creating a New SIP or SIPS Channel
» Configuring Custom Timeout, MTU, and Other Properties
» Configuring SIP Channels for Multi-Homed Machines
» Configuring Engine Servers to Listen on Any IP Interface
» Static Port Configuration for Outbound UDP Packets
» Multi-homed Server Configurations Overview
» Multi-homed Servers Listening On All Addresses IP_ANY
» Understanding the Route Resolver
» IP Aliasing with Multi-homed Hardware
» Single Load Balancer Configuration
» IP Masquerading Alternative to Source NAT If you choose not to enable source
» Example Network Topology Example Network Configuration
» Oracle WebLogic Communication Services Configuration
» NAT-based configuration Load Balancer Configuration
» maddr-Based Configuration Load Balancer Configuration
» rport-Based Configuration Load Balancer Configuration
» Authentication Providers Authentication for SIP Servlets
» Identity Assertion Support Oracle Fusion Middleware Online Documentation Library
» Role Assignment for SIP Servlet Declarative Security
» Security Event Auditing Oracle Fusion Middleware Online Documentation Library
» Common Security Configuration Tasks
» What Is Digest Authentication?
» Digest Authentication Support in Oracle WebLogic Communication Services
» Prerequisites for Configuring LDAP Digest Authentication
» Using Unencrypted Passwords If you are using an RDBMS, or if your LDAP
» Using Precalculated Hash Values If you want to use precalculated hash values,
» Using Reverse-Encrypted Passwords Oracle WebLogic Communication Services
» Reconfigure the DefaultAuthenticator Provider
» Configure an Authenticator Provider
» In the left pane of the Console, select the Security Realms node.
» Select the Providers Authentication tab.
» Click New. Configure an LDAP Digest Identity Asserter Provider Follow these instructions to
» Click OK. Configure an LDAP Digest Identity Asserter Provider Follow these instructions to
» Select the Configuration Provider Specific tab in the right pane.
» Click Save to save your changes. Select the Performance tab in the right pane.
» Select the Providers Authentication tab. Click New.
» Click OK. Select the Configuration Provider Specific tab in the right pane.
» Click Save to save your changes.
» Store User Password Information in the Description Field
» Set the Embedded LDAP Password
» Configure the Digest Identity Asserter Provider
» Configuring the Default Identity Asserter
» Select the Configuration Provider Specific tab.
» Click Save. Oracle Fusion Middleware Online Documentation Library
» Configuring Oracle WebLogic Communication Services to Use WL-Proxy-Client-Cert
» Supporting Perimeter Authentication with a Custom IA Provider
» Understanding Trusted Host Forwarding with P-Asserted-Identity
» Overview of Strict and Non-Strict P-Asserted-Identity Asserter Providers
» Configuring the Identity Header Assertion Provider
» Configuring a X-3GPP-Asserted-Identity Provider
» Configuring Basic Authentication for HTTP Servlets
» Add Oracle WebLogic Communication Services
» Configuring Oracle Internet Directory Add a New Oracle WebLogic Communication Services
» Grant Verifier Privileges to the Oracle WebLogic Communication Services Instance
» Create a Group Assign Group Memberships to Users
» datatier.xml Configuration File Configuration Requirements and Restrictions
» SIP Data Tier with One Partition
» SIP Data Tier with Two Partitions
» SIP Data Tier with Two Partitions and Two Replicas
» Requirements and Restrictions Storing Long-Lived Call State Data In A RDBMS
» Steps for Enabling RDBMS Call State Storage
» Modify the JDBC Datasource Connection Information
» Configure JDBC Resources Configuring RDBMS Call State Storage by Hand
» Configure Oracle WebLogic Communication Services Persistence Options
» Situations Best Suited to Use Geo-Redundancy
» Situations Not Suited to Use Geo-Redundancy
» Geo-Redundancy Considerations: Before Your Begin
» Example Domain Configurations Using Geographically-Redundant SIP Data Tiers
» Requirements and Limitations Using Geographically-Redundant SIP Data Tiers
» Steps for Configuring Geographic Persistence
» Installing and Configuring the Primary Site
» Installing the Secondary Site
» Configuring JDBC Resources Primary and Secondary Sites
» Configuring Persistence Options Primary and Secondary Sites
» Configuring JMS Resources Secondary Site Only
» Call State Replication Process Call State Processing After Failover
» Removing Backup Call States Monitoring Replication Across Regional Sites
» Configuring Engine Tier Caching Monitoring and Tuning Cache Performance
» Launching Sash from the Command Line
» Viewing Subcommands Viewing Available Commands
» Creating a User from the Sash Command-Line Prompt
» Creating a User with the Command Service MBean
» Provisioning XDMS User Accounts Using the CommandService MBean
» Provisioning XDMS User Accounts from the Sash Prompt
» Provisioning XDMS User Accounts
» Adding XDMS Users Using xcap Commands
» Overview of Sash Scripting with Sash
» Overload Protection Failure Prevention and Automatic Recovery Features
» Redundancy and Failover for Clustered Services
» Automatic Restart for Failed Server Instances
» Managed Server Independence Mode
» Automatic Migration of Failed Managed Servers
» Geographic Redundancy for Regional Site Failures
» Enabling Automatic Configuration Backups
» Storing the Domain Configuration Offline
» Backing Up Server Start Scripts
» Backing Up Logging Servlet Applications
» Backing Up SerializedSystemIni.dat and Security Certificates All servers create a
» Backing Up the WebLogic LDAP Repository The default Authentication,
» Backing Up Additional Operating System Configuration Files
» Restarting an Administration Server on the Same Machine
» Restarting an Administration Server on Another Machine
» Restarting Failed Managed Servers
» WlssEchoServer Failure Detection Overview of Failover Detection
» Forced Shutdown for Failed Replicas
» Starting WlssEchoServer on SIP Data Tier Server Machines
» Files for Troubleshooting Understanding and Responding to SNMP Traps
» Recovery Procedure If this trap occurs in isolation from other traps indicating
» Recovery Procedure See connectionReestablishedToPeer
» Recovery Procedure See the Recovery Procedure for
» Recovery Procedure Follow this recovery procedure:
» Additional Overload Information If you set the queue length as an incoming call
» Recovery Procedure This trap is generated during normal startup procedures
» Recovery Procedure Restart the engine tier server. Repeated occurrences of
» Recovery Procedure If this trap is generated as a result of a server instance
» Additional Shutdown Information The Administration Console generates SNMP
» Recovery Procedure This trap is generated during normal deployment
» Recovery Procedure During normal shutdown procedures this alarm should
» Recovery Procedure The typical failure is caused by an invalid sip.xml
» Watches and Notifications Using the WebLogic Diagnostics Framework WLDF
» Image Capture Using the WebLogic Diagnostics Framework WLDF
» Configuring Server-Scoped Monitors Instrumentation
» Configuring Application-Scoped Monitors Instrumentation
» Defining Logging Servlets in sip.xml Configuring the Logging Level and Destination
» Using XML Documents to Specify Logging Criteria
» Using Servlet Parameters to Specify Logging Criteria
» Adding Tracing Functionality to SIP Servlet Code
» Order of Startup for Listeners and Logging Servlets
» Modifying JVM Parameters in Server Start Scripts
» Tuning Garbage Collection with JRockit
» Using Oracle JRockit Real Time Deterministic Garbage Collection
» Using Oracle JRockit without Deterministic Garbage Collection
» Tuning Garbage Collection with Sun JDK
» Avoiding JVM Delays Caused By Random Number Generation
» Overview of Presence Oracle Fusion Middleware Online Documentation Library
» Configuring XDMS Configuring Presence
» Command Service XDMS Provisioning
» Aggregation Proxy Configuring Presence
» PresenceSupplierWebService PresenceConsumerWebService Configuring Presence Web Services
» MessagingWebServiceConfig Configuring Presence Web Services
» Overview of Diameter Protocol Configuration
» Steps for Configuring Diameter Client Nodes and Relay Agents
» Installing the Diameter Domain
» Enabling the Diameter Console Extension
» Configuring Two-Way SSL for Diameter TLS Channels
» Configuring and Using SCTP for Diameter Messaging
» Creating a New Node Configuration General Node Configuration
» Configuring the Sh Client Application
» Configuring the Rf Client Application Configuring the Ro Client Application
» Configuring a Diameter Relay Agent
» Configuring the Sh and Rf Simulator Applications Enabling Profile Service using an Sh backend
» Configuring Peer Nodes Configuring Routes
» Example Domain Configuration Oracle Fusion Middleware Online Documentation Library
» Troubleshooting Diameter Configurations Oracle Fusion Middleware Online Documentation Library
» Components Architecture User Messaging Service Overview
» Introduction to Oracle User Messaging Service Configuration
» How to Set the Storage Method
» Adding Business Terms How to Add or Remove User Messaging Preferences Business Terms
» About Driver Properties How to Configure a Driver
» Securing Passwords How to Configure a Driver
» E-Mail Driver Interoperability This section details interoperability features of the
» Common Properties These are common driver properties that are indicative of
» Email Custom Properties These are properties specific to this driver and are
» Client API MessageInfo Support These properties are message delivery related
» SMPP Driver Interoperability This section details interoperability features of the
» Custom Properties These are properties specific to this driver and are
» About XMPP XMPP is an open, XML-based protocol for Instant Messaging
» XMPP Driver Interoperability This section details interoperability features of the
» XMPP Custom Properties The XMPP Driver includes the custom properties
» VoiceXML Driver Interoperability This section details interoperability features of
» Click Browse, and navigate to ORACLE_
» Common Properties The following common driver properties are indicative
» Custom Properties The following custom property is available:
» Client API MessageInfo Support This table shows if the protocol or driver
» Web Service Security on Notification
» Enabling UMS Service Security
» Enabling Client Security Securing User Messaging Service
» Keystore Configuration Client Aliases
» Troubleshooting Oracle User Messaging Service
» Configuring Logging Log Files
» Using WebLogic Server Administration Console
» Metrics and Statistics Undeploying and Unregistering Drivers
» Click Invoke. Oracle Fusion Middleware Online Documentation Library
» Proxy Registrar Oracle Fusion Middleware Online Documentation Library
» STUN Service Oracle Fusion Middleware Online Documentation Library
» Goals of the Oracle WebLogic Communication Services Base Platform Load Balancer
» Example of Writing and Retrieving Call State Data
» RDBMS Storage for Long-Lived Call State Data
» Engine Tier Geographically-Redundant Installations
» Example Hardware Configurations Oracle Fusion Middleware Online Documentation Library
» Alternate Configurations Oracle Fusion Middleware Online Documentation Library
» Single-node Topologies OWLCS Deployment Topologies
» Runtime Processes Introduction to OWLCS Enterprise Deployment Topology
» Request Flow Introduction to OWLCS Enterprise Deployment Topology
» Client Connections Introduction to OWLCS Enterprise Deployment Topology
» SIP Containers OWLCS extends the core WebLogic Server platform with a
» Third-Party Load Balancer A third-party load balancer balances the load of
» Proxy Registrar The OWLCS Proxy Registrar combines the functionality of a
» Presence Web Services OWLCS enables Web Service clients to access
» Third-Party Call Control Web Services The Third Party Call Parlay X 2.1
» Aggregation Proxy The Aggregation Proxy authorizes web service calls and
» Authentication Proxy The Authentication Proxy is a SIP application that upon
» File Transfer Service OWLCS includes an Oracle-proprietary file transfer
» Messaging Services Messaging Services implements support for a subset of
» STUN Service The OWLCS STUN Service implements STUN Simple
» DAR Configuration DAR Configuration. Application Router is a SIP
» Oracle Communicator Client Oracle Communicator is a client communication
» State Tier The Oracle WebLogic Communication Services SIP state tier node
» User Dispatcher The User Dispatcher enables the Presence and XDMS
» Oracle RAC Database Oracle RDBMS should be installed and operational in
» Overview of SIP State Tier Configuration
» SIP State Tier with One Partition A single-partition, two server SIP state tier
» SIP State Tier with Two Partitions Multiple partitions can be created by defining
» SIP State Tier with Two Partitions and Two Replicas Replicas of the call state can
» Storing Long-Lived Call State Data in an RDBMS
» Geographic Redundancy Oracle WebLogic Communication Services Enterprise Deployment Topology
» Stateless User Dispatcher and Even Distribution The most basic approach is to
» Presence Application Broadcast Another solution is to have the Presence
» OWLCS Presence Failover Standby Server Pool
» Fatal Failures If the failure is fatal all state information is lost and established
» Temporary Failures A temporary failure is one where none or little data is lost
» Broadcasting Fail-Over Events In this approach each dispatcher instance have
» Shared State If all dispatcher nodes in the cluster share the same state from a
» Updating the Node Set Depending on the algorithm used to find the server
» Migrating Presentities When the node set has been updated some Presentites
» One Presence Server Overloaded for 60 Seconds The cluster consists of four
» One Presence Server Overloaded Multiple Times for Five Seconds This use case
» Overload Policy Triggered by an OWLCS Software Failure A failure in the OWLCS
» A Presence Server Hardware Failure The cluster consists of four Presence
» Expanding the Cluster with One Presence Node The cluster consists of 3 Presence
» Terminology Overview of SIP Application Upgrades
» Requirements and Restrictions for Upgrading Deployed Applications
» Steps for Upgrading a Deployed SIP Application
» Defining the Version in the Manifest
» Deploy the Updated Application Version
» Undeploy the Older Application Version
» Architecture of Web Service Client Applications
» Enabling Client Security Web Service Security
» Keystore Configuration Web Service Security
» Client Aliases Web Service Security
Show more