Before you begin
Avoid trouble: For a list of restrictions that are
changed based on various service levels of the product, see the topic
What is new in the Feature Pack for CEA.
gotcha
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 application server installation. The
sample IP PBX is in the form of an enterprise application 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.
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 with the Feature
Pack for CEA at
app_server_root
/feature_packs/cea/samples/plantsbywebsphere/documentation/index.html,
as well as the topic Setting up a CEA Feature Pack demonstration environment.
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
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: 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.
- 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.
- You might see different product versions of the Plants By WebSphere sample application
installed in your machine environment. Make sure that you install
the edition that comes with the Feature Pack for CEA entitled PlantsByWebSphere
Ajax Edition for CEA (PlantsByWebSphereAjax).
- Different versions of the PlantsByWebSphere sample application
are supplied with the Feature Pack for Communications Enabled Applications
(CEA) and the Feature Pack for Web 2.0. However, the sample application
from these two feature packs cannot coexist on the same application
server. This problem is due to Java™ Naming Directory Interface (JNDI)
name and context root conflicts. To avoid this problem, do not install
both the CEA and Web 2.0 versions of the PlantsByWebSphere sample
application on the same application server.
gotcha