10 Managing Oracle WebLogic Communication Services for Click-to-Dial Functionality

Oracle WebLogic Communication Services provides click-to-dial functionality for applications primarily through contextual actions. Contextual actions provide related information and actions to users within the immediate context of the object instances upon which they act. This chapter explains how to enable and configure these services.

It includes the following topics:

Section 10.1, "Introduction to Third Party Call Web Service"
Section 10.2, "Modifying Third Party Call Web Service Default Settings Using the System MBean Browser"
Section 10.3, "Call Routing Through a Session Border Controller"

10.1 Introduction to Third Party Call Web Service

The Third Party Call Web service in Oracle WebLogic Communication Services enables click-to-dial functionality in applications by providing an interface to initiate a call between two parties. The Web service is an implementation of the Parlay X 2.1 Third Party Call Interface.

The Third Party Call Web service can:

Set up a call between two parties
Query the status of an ongoing call
Cancel a call it is creating
Terminate an ongoing call it created

The Third Party Call Web service is provided through the thirdpartycall application, which is installed with default configuration settings in the domain for the each product family.

10.2 Modifying Third Party Call Web Service Default Settings Using the System MBean Browser

You can use the System MBean Browser to modify the default configuration settings for the thirdpartycall application for the product family domains.

To modify the MBeans for the thirdpartycall application with the System MBean Browser from the Fusion Applications Control:

From the target navigation pane, expand the farm and then Application Deployments.
Select the application thirdpartycall.
From the Application Deployment menu, select System MBean Browser.

Fusion Applications Control displays the System MBean Browser page.
Scroll down to the node that displays oracle.ucs.thirdpartycall. Expand the oracle.ucs.thirdpartycall node and drill down to the node that displays the ThirdPartyCallConfiguration MBean.
Click the ThirdPartyCallConfiguration MBean node. The configuration settings for the thirdpartycall application appear on the right pane. Select the Attributes tab to display the details for this group of attributes.

For more information about the configurable attributes for the thirdpartycall application, see Table 10-1.
Update values of the attributes to modify by entering the new value in the Value field.
Click Apply.

For general information about the System MBean Browser, see the "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" section in Oracle Fusion Middleware Administrator's Guide.

Table 10-1 contains a list of attributes for configuring the Third Party Call Web service

Table 10-1 Configuration Attributes for Third Party Call Web Service

Attribute	Format	Description	Values
`ChargingAllowed`	String	Specifies if charging is allowed.	Default: False Note: No server restart is required if you change the value.
`ControllerUri`	String in URI format	Specifies the Third Party controller Session Initiation Protocol (SIP) URI that is used to establish the third party call. If this value is set, a call appears to the callee to come from this URI.	Default: empty By default, no controller URI is used to establish the call. In this case, the call appears to the callee to come from the caller. Note: You must restart the server if you change this value.
`MaximumCallDuration`	int	Specifies the maximum time (in minutes) for an ongoing call. If this time expires, the call is terminated.	Default: 1440 (24 hours) Minimum: -1 (0 and -1 means that call-length supervision is disabled) Maximum: Unbounded Note: No server restart is required if you decrease this value. You must restart the server if you increase the value or set the value to 0 or -1.
`PAssertedIdentityUri`	String in URI format	Specifies the SIP URI used in the `P-Asserted-Identity` header added by the Third Party Call service. If left blank the `P-Asserted-Identity` header is not added.	Default: empty Note: You must restart the server if you change this value.
`StatusRetentionTime`	int	Specifies the time (in minutes) for retaining the status information about a call after it was terminated.	Default: 5 Minimum: -1 (0 and -1 means that the status information is removed when the call is terminated). Maximum: Unbounded Note: No server restart is required if you change the value.
`PreloadedRouteUri`	String in URI format	Specifies the SIP URI to put in a route header of outgoing SIP `INVITE` requests during a call setup.	Default: empty Note: You must restart the server if you change this value.

10.3 Call Routing Through a Session Border Controller

The Third Party Call Web service interfaces on the backend with SIP infrastructure, such as a SIP-enabled switch or a SIP-to-PSTN gateway. When the SIP infrastructure lies outside the enterprise network, such as in the case of a hosted SIP trunking service or if the switch is in an external network, a Session Border Controller (SBC) is typically used to secure and control the interaction. A SBC is a piece of equipment that is deployed at the border of the network and controls the signaling and media across network address translation (NAT) devices and firewall boundaries. In addition, it prevents unauthorized access and denial of service (DoS) attacks.

You can route the Third Party Call Control (TPCC) requests through an SBC either by setting up an outbound proxy server or by configuring one TPCC attribute.

This section contains the following topics:

Section 10.3.1, "Setting Up an Outbound Proxy Server"
Section 10.3.2, "Configuring the PreLoadedRouteUri Attribute"

10.3.1 Setting Up an Outbound Proxy Server

You can set up the SBC as an outbound proxy server and route TPCC requests through the outbound proxy server. If you define an outbound proxy server (SBC) for a SIP Servlet container, any request from all SIP servlet applications (including the thirdpartycall application) on this SIP Servlet container is routed through the SBC.

Oracle WebLogic SIP Server provides Oracle WebLogic Administration Console extensions that allow you to modify the SIP Servlet container properties. To set up an outbound proxy:

Enter the following URL in a browser:
```
http://hostname:port_number/console
```
where the hostname and the port_number correspond to the Administration Server for the domain.
Log in using the Oracle Fusion Middleware administrative user name and password.
Select the SipServer node in the left pane. The right pane of the console displays the tabbed pages that are used for configuring and monitoring WebLogic SIP Server.
Select the Proxy tab.
Select the Proxy Routing Policy as proxy.
In the Proxy Routing URIs section, enter the URI as sip:SBC_hostname:SBC_portnumber, where SBC_hostname and SBC_portnumber represent the host and port of the Session Border Controller, respectively.
Click Save.

For more information, see the "SIP Server: Configuration: Proxy" topic in the Oracle WebLogic Administration Console Help.

Note:

Oracle recommends that you use the Administration Console to modify sipserver.xml indirectly, rather than editing the file by hand. Using the Administration Console ensures that the sipserver.xml document always contains valid XML.

10.3.2 Configuring the PreLoadedRouteUri Attribute

To route requests only from the thirdpartycall application through SBC, set the value of the PreLoadedRouteUri attribute as sip:SBC_hostname:SBC_portnumber, where SBC_hostname and SBC_portnumber represent the host and port of the SBC, respectively.

For more information about modifying the PreLoadedRouteUri attribute, see Section 10.2.