| Oracle® Communication and Mobility Server Installation Guide 10g Release 3 (10.1.3) Part Number E12657-02 |
|
|
View PDF |
| Oracle® Communication and Mobility Server Installation Guide 10g Release 3 (10.1.3) Part Number E12657-02 |
|
|
View PDF |
This chapter describes Oracle Communication and Mobility Server (OCMS) and recommended topologies in the following sections:
OCMS is a carrier grade SIP (Session Initiation Protocol) and J2EE execution platform for applications needing to send or receive messages over a SIP enabled broadband network or cellular network. This platform is referred to as a SIP Application Server.
Examples of such applications are as follows:
IP Telephony
Video Calling
Instant Messaging
Speed Dial Service
Call Forwarding Service
Third Party Call Control
Emergency Call Service
OCMS can be deployed either for broadband or 3GPP IP Multimedia System (IMS) networks offering value-added services.
This release of Oracle Communication and Mobility Server includes enhancements and new features. To read about new and improved features, see Oracle Communication and Mobility Server Administrator's Guide, and Oracle Technology Network at http://www.oracle.com/technology/products/ocms/otn_front.htm.
This section describes prerequisites for installing OCMS and for using specific OCMS functionality.
To install OCMS your system must meet the following requirements:
Red Hat Enterprise Linux AS 4 (update 5 or higher), AS 5 (update 1 or higher)
Recommended for development purposes only: Microsoft Windows 2000 with Service Pack 3 or above, Microsoft Windows Server 2003 (32-bit) with Service Pack 1 or above, or Microsoft Windows XP Professional with Service Pack 2
Java 2 Platform, Enterprise Edition Software Development Kit (JDK) 5.0, (JDK version 1.5). Oracle Application Server installation mode uses the JDK 1.5.0 from the installation of Oracle Application Server. Standalone developer mode bundles JDK 1.5.0 with the OCMS installation.
Oracle 10g Database (10.2.0.3 or higher) or Oracle Database 11g (11.1.0.6 or higher), for Subscriber Data Services and Presence.
Refer to What Components are Installed for more information on Subscriber Data Services.
a LAN connection and an IP address and hostname
Note:
The listed operating systems are certified and supported for Oracle Communication and Mobility Server. Other operating systems have not been certified.OCMS requires the use of ports for TCP and UDP communications for the SIP Container, Presence server, and, if installed, the Edge Proxy. Default port numbers will be specified for the SIP Container and Edge Proxy ports, or use port numbers that you specify. The Presence port is not configurable during installation, but can be configured in the MBean browser. Refer to the Oracle Communication and Mobility Server Administrator Guide for information on how to reconfigure port numbers following installation.
During installation, selected ports are verified. If a port is in use by another application, the installation will not succeed, and an error message will appear.
Table 1-1 lists the default ports used by OCMS when you install the Edge Proxy application.
Table 1-2 lists the default ports used by OCMS when you do not install the Edge Proxy application:
Table 1-2 Default Ports: Edge Proxy Not Installed
| SIP Port | Edge Proxy Port | Presence Port |
|---|---|---|
|
5060 |
N/A |
5070 |
To check if a port is being used in Windows, you can run the netstat command as follows:
C:\> netstat -an | find "portnum"
Note that you need double quotes around the port number.
To check if a port is being used in Linux, you can run the netstat command as follows:
netstat -a | grep <portnum>
Oracle Communication and Mobility Server can be installed in the following installation modes:
Table 1-3 lists requirements for each installation mode.
Table 1-3 Requirements for Installation Modes
| Requirement | Oracle Application Server mode | Standalone Developer mode |
|---|---|---|
|
Oracle Containers for J2EE (OC4J) |
Required before installation |
Not required. Included with the installation. |
|
Provided by Oracle Application Server. |
Included. |
The standalone developer mode allows developers to develop and test SIP applications in a minimal installation environment, without an application server. This installation mode installs Oracle Containers for J2EE (OC4J).
Standalone developer mode is not typically recommended for production deployment because of limited management capabilities.
The recommended installation mode installs OCMS into an Oracle Application Server Release 10.1.3.4 or higher environment. This installation mode allows OCMS to use OC4J features such as Oracle High Availability (HA), clustering, and replication.
Oracle Communication and Mobility Server is deployed with an OC4J container that you manage using the Oracle 10g Enterprise Manager Application Server Control console. The Application Server Control functions enable starting, stopping, restarting, deploying, undeploying, and redeploying applications
Additionally, the Application Server Control MBean browser enables you to configure and manage the OCMS components. Configuring the attributes of the OCMS MBeans (Managed Beans) enables you to execute such administrative tasks as configuring the DNS (Domain Name System), configuring and managing Presence, and the basic configuration (port, IP, and host address) of the OCMS SIP Server itself.
For more information on managing and configuring OCMS in an Oracle Application Server environment, refer to "Managing the SIP Server" in the Oracle Communication and Mobility Server Administrator's Guide.
For more information on features provided by Oracle Application Server, refer to Oracle Application Server Administrator's Guide.
The following applications are selected for installation by default, unless the user de-selects them during installation.
SIP Container: A SIP Servlet Container extends the J2EE Application Server, providing a runtime environment for SIP applications, including services such as security, concurrency, lifecycle management, transaction, deployment, and other services. A JSR116-compliant SIP Servlet Container provides network services for sending and receiving SIP requests and responses using a combination of transport protocols, IP addresses, and port numbers to listen for incoming SIP traffic. The OCMS SIP Servlet Container can be installed on an existing instance of Oracle Application Server, running in OC4J. Alternatively, the OCMS SIP Servlet Container can run on its own standalone instance of OC4J. The typical OCMS SIP Servlet Container is composed of an Oracle Application Server instance with OC4J as its J2EE container, and Oracle Process Manager and Notification Server (OPMN) to monitor the server. OCMS currently supports high availability deployments in this configuration only.
Subscriber Data Services: Subscriber Data Services is installed when applications require the authentication and security services provided by OCMS. Subscriber Data Services requires Oracle Database.
Proxy Registrar: Proxy Registrar combines the functions of a SIP Proxy Server and Registrar. Its main tasks include registering subscribers, looking up subscriber locations, and proxying requests to destinations.
The Proxy Registrar depends on the Subscriber Data Services for the Location Service and the registrar subcomponents of the Proxy Registrar to function.
Presence: The Presence application enables a service provider to provide Presence services to end users as well as enabling the service provider to base other services on Presence information (for example, intelligent call routing based on Presence information).
The Presence application depends on the SIP Container.
Aggregation Proxy: Aggregation Proxy authenticates any XCAP requests and Web Services calls. The XCAP requests and Web Services calls are then proxied to their respective servers. For more information, refer to Oracle Communication and Mobility Server Administrator's Guide.
The Aggregation Proxy depends on the SIP Container and Subscriber Data Services.
Application Router: Application Router is a SIP application that routes incoming SIP requests to the correct application. It is a required component for composing applications or for deploying new applications of your own.
The Application Router routes requests by placing route headers in each SIP request it processes. A number of route headers can be placed in a request, each representing a different destination URI. The SIP request is either sent through the chain of destination URIs, or proxied to a new URI after arriving at its first destination.
The Application Router application depends on the SIP Container and Subscriber Data Services.
The following applications are not installed by default, and must be selected for installation by the user from the list of available applications:
Parlay X Presence Web Services: Presence Web Services provides support for the Parlay X Presence Web Services. This is an implementation of the Parlay X 2.1 Web Services interface.
The Presence Web Service application depends on the SIP Container
STUN Server: The STUN server implements the STUN (Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators) server protocol. This acts as a NAT traversal mechanism to allow clients to find out the external IP address and port that the client is represented by.
The STUN server depends on the SIP Container.
Edge Proxy: Edge Proxy provides a SIP distribution for routing requests, proxying SIP requests to a particular OCMS SIP Server instance. The Edge Proxy forms logical pathways between individual clients and SIP servers, such that SIP traffic sent from a particular client session is always handled by the same server. As the number of SIP clients increases, additional Edge Proxy servers can be added, providing highly scalable handling of SIP clients.
The Edge Proxy is available for installation only in Oracle Application Server Mode.
User Dispatcher: The User Dispatcher enables stateful applications, such as the Presence applications, to scale. The User Dispatcher is a proxy that dispatches SIP and XCAP (over HTTP) requests to the their appropriate destinations on a consistent basis.
For more description and configuration information on these features, refer to Oracle Communication and Mobility Server Administrator's Guide.
