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
The CEA capability
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 application
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.
About this task
Web services require a Web Services Description
Language (WSDL) file that describes the interface. The WSDL file can
be interpreted by Web service tools to generate the Web services client
code needed to communicate with the Web service. As a result, an application
developer need only call the correct set of Java APIs to manage phone calls in an application.
This task lists the steps needed to create and deploy
an application that can manage phone calls, including how to configure
the application server. Formerly, this capability required building
SIP servlets and a detailed understanding of the SIP specification.
The CEA technology greatly reduces the amount of code required.
The CEA capability allows users to do the following:
- Open a session to start monitoring a phone
- Get notifications about phone activity
- Make phone calls between two phones
- End an active phone call
- Close a session to stop monitoring a phone
Note: In order to open a session and monitor
a phone for activity, you need to provide an address of record for
your phone. This could be a URI (uniform resource indicator) of a
phone. A SIP URI, for example, has the format of sip:username@serviceprovider,
which represents the address of your phone on the Internet.
Results
An application has been developed and deployed
that uses a Web services client to handle phone calls and call notifications.
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.
gotcha
Best practice: To avoid connection
timeout exceptions, it is a best practice to increase the default
connection using the Java virtual
machine custom property com.ibm.websphere.webservices.http.maxConnection.
The default connection is 50 and once it is reached, the next request
waits for a connection to be freed. If it does not get a connection
in 5 minutes, it can time out. You might increase the default connection
from 50 to 200 in a scenario where you need more connections. To learn
more about this custom property, see the HTTP transport custom properties
for Web services applications. To learn how to configure this custom
property, see the Java virtual
machine (JVM) custom properties information.
bprac