Receiving call notifications in web applications

You can embed the CallNotification widget in an existing application to enable users to enter their phone number and receive notifications of incoming calls. You embed the communications enabled applications (CEA) widget using the Dojo Toolkit provided with the CEA feature.

Before you begin

Dojo widgets are prepackaged components of JavaScript code, HTML markup and CSS style declarations that can be used to enhance web sites with interactive features. You can use the Dojo Toolkit that comes with the CEA feature to embed CEA widgets in your applications. This capability also requires an IP private branch exchange (PBX) as part of your infrastructure. An IP PBX is a business telephone system designed to deliver voice over a data network and interoperate with the Public Switched Telephone Network (PSTN). A sample IP PBX application is included in the Samples section of the information center. The sample IP PBX is in the form of an enterprise archive (EAR) file and is for test purposes only. The details of installing and configuring the vendor-specific IP PBX are not provided. Along with the sample IP PBX, two soft phones are needed to test the application.

Deprecated feature Deprecated feature: CEA Dojo widgets encapsulate various user interfaces that are based on the CEA Rest API. These widgets are deprecated. You can also obtain the source for these widgets from developerWorks®. depfeat

About this task

The CallNotification widget is built using the functionality provided in the Dojo Toolkit. This widget can be configured to allow users to enter their phone number and receive notifications of incoming calls. The CallNotification widget can also be customized to match the look and feel of the page by overriding the default CSS file. The functionality provided by the widget can be extended, allowing the user to create their own custom version to handle more advanced tasks.

This task lists the steps needed to enable phone call management in an existing application, including how to install the SIP IP PBX sample application and configure the application server. To quickly learn how the CEA widgets work in an online application, you can install the PlantsByWebSphere Ajax Edition for CEA (PlantsByWebSphereAjax) sample application. For more information about the sample application, see the supporting documentation that is provided in the PlantsByWebSphere directory of the CEA samples package that you can download from the WebSphere® Application Server Samples page. Additionally, read about setting up and using the communications enabled application samples.

Avoid trouble Avoid trouble: In the following procedure, complete either Step 6 or Step 7. Step 6 enables the widget for desktop browsers. Step 7 enables the widget for Apple and Android mobile browsers.gotcha

Procedure

  1. Enable the system application.
  2. Install and configure the IP PBX.
  3. Configure the IP PBX location.
  4. Restart the application server.
  5. Copy the CEA widgets into the application you are enhancing.
  6. Embed the widgets in the application you are enhancing.
  7. Embed the mobile widgets in the application you are enhancing.
  8. Install and start the application you have enhanced.
  9. Test the application you have enhanced.

Results

You have enabled the CallNotification widget within an application to allow users to enter their phone number and receive notifications of incoming calls.

Avoid trouble Avoid trouble: If problems are encountered, troubleshooting can be done to find the source. Here is a checklist.
  • Is the IP PBX installed and started? If using the sample IP PBX, the administrative console of its application server can be used to verify the installation.
  • Are the phones set up correctly? They should list that they are registered with the IP PBX and in ready state.
  • Is the new application installed and started? Check with the administrative console or verify by looking in the SystemOut.log file.
    Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
  • Initiate a network trace to see how messages are exchanged on the network between the application, IP PBX, and phones.
  • When you test the widgets, use two completely separate browsers, or the same browser on two separate machines. Using tabs in the same browser, or even launching separate instances of the same browser on the same machine, will cause session issues.
  • Enable browser cookies to allow the CEA widgets to store state information about the active widget session. This process enables the user to access another web page with the embedded CEA widget or refresh the current page while keeping the widget session active. If you disable cookies and access another page with the embedded CEA widget or refresh the current page, the CEA widget loads to the default state.
gotcha
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=tcea_enable_call_notifications_widgets
File name: tcea_enable_call_notifications_widgets.html