| Oracle® Communications WebRTC Session Controller System Administrator's Guide Release 7.0 E40973-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications WebRTC Session Controller System Administrator's Guide Release 7.0 E40973-01 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of the configuration of the Oracle WebRTC Session Controller Media Engine.
You configure the WebRTC Session Controller Media Engine using one of the following interfaces: a command-line interface (CLI), web interface or SNMP
Command-Line Interface (CLI) through console, telnet or secure shell (SSH)
Http/web using a browser interface provided by the Media Engine
SNMP Interface
HTTP/SOAP/WSDL Interface
Configuring the Media Engine does not use the WebLogic domain Administration Console For more information about setting up and accessing Media Engine interfaces see the chapter on Managing and Administering Net-Net OS-E Systems in Oracle Communications Net-Net OS-E System Administration Guide.
You must configure the WebRTC Session Controller Media Engine to receive requests from Signaling Engines and to forward the requests to your SIP network infrastructure. The Media Engine also allows requests originating from SIP clients on your network to communicate with WebRTC clients through the Signaling Engine.
You perform the following Media Engine configuration tasks using of the Media Engine administration interfaces:
The following sections provide a general overview of each task along with a reference to the related chapter in the Oracle Communications Net-Net OS-E System Administration Guide. For detailed information on each task, see the referenced chapter.
Media Engine requires setting up users unique to those configured in the WebRTC Session Controller Oracle WebLogic domain. You must also assign the proper permissions and authorizations to each user to secure your Media Engine server.
For more information see the chapter on configuring permissions, user and authorizations in Oracle Communications Net-Net OS-E System Administration Guide.
You must configure the web and network interfaces used by the Signaling Engine and Media Engine to communicate with each other. The network configuration required by your environment determines whether you need to configure multiple IP interfaces, VLANs, and other network properties.
For more information on setting up the Media Engine network interfaces and properties see the chapter on enabling Net-Net OS-E interfaces and protocols in Oracle Communications Net-Net OS-E System Administration Guide.
The Media Engine provides several services and interfaces with external systems that are used with WebRTC Session Controller. These services include:
Cluster-Master Services
Directory Services
Accounting Services
Authentication Services
OS-E Database
Registration Services
Server Load
Call Failover (Signaling and Media)
Load-Balancing
File-Mirror
Route Server
Sampling
Third-Party-Call-Control (3PCC)
Logging
Data and Archiving
External Database Connections
System Maintenance
Back Up
The services you use depend on the WebRTC Session Controller implementation in your environment.
For more information on all of the services listed, including how to enable a service using an administration interface like CLI, see the chapter on enabling Net-Net OS-E Services in Oracle Communications Net-Net OS-E System Administration Guide.
The Media Engine can capture SIP call detail records (CDRs) and other accounting records associated with the SIP sessions generated by WebRTC Session Controller from WebRTC and SIP client requests.
For information on using Media Engine accounting features see the chapter on configuring Net-Net OS-E accounting and provisioning in Oracle Communications Net-Net OS-E System Administration Guide.
The Media Engine contains a configurable Domain Name Systems (DNS) resolver used to configure and cache heavily used static server mappings, including SIP service to SIP server mappings, and mappings resulting from interactions with external servers. You can also configure the Media Engine to ignore lookups involving specific domain names.
For more information on Media Engine DNS capabilities, see the chapter on configuring domain name systems in Oracle Communications Net-Net OS-E System Administration Guide.
You must configure the Media Engine to communicate with SIP servers in your network infrastructure so WebRTC requests can be forwarded from external clients to your SIP clients. Media Engine supports SIP servers from multiple vendors.
For information on configuring the SIP server pools and SIP directories required by the Media Engine to communicate with your environment see the chapter on configuring SIP servers, directories and federations in Oracle Communications Net-Net OS-E System Administration Guide.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
