WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring SIP application composition on servers where Call Notification and Third Party Call are deployed

If you plan to run the Parlay X Call Notification over SIP/IMS and Parlay X Third Party Call over SIP/IMS Web service implementations on the same server (JVM), you must configure SIP application composition using the WebSphere Integrated Solutions Console.

Before you begin
You must have completed the following steps:
  • Completed the initial installation and configuration for TWSS base components and Web service implementations, which includes running the First Steps configuration script
  • Started WebSphere® Application Server, version 7.0.0.7 or 6.1.0.29
  • Started the deployment manager, node agents, and application servers where you have deployed the EAR files for the Parlay X Call Notification over SIP/IMS and Parlay X Third Party Call over SIP/IMS Web service implementations
About this task

The JSR 116 standard for SIP applications states that multiple applications can be invoked for the same SIP request. The process of setting up applications to comply with this standard is called application composition.

To ensure that incoming SIP requests are handled properly when the Parlay X Call Notification over SIP/IMS and Parlay X Third Party Call over SIP/IMS Web service implementations run coresident on the same server, you must configure application composition for both applications.

For help in selecting the values to specify for application composition, refer to the topic Setting up SIP application composition in the WebSphere Application Server information center.

Complete the following steps to configure SIP application composition:

  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. In the navigation pane, click Applications > Enterprise Applications.
  3. In the Enterprise Applications list, click PX21_CN_IMS. This is the EAR file name for Parlay X Call Notification over SIP/IMS.
  4. To specify the weight for the EAR file, click Startup Behavior and set the startup order.
  5. Return to the Enterprise Applications list and click PX21_CN_IMS.
  6. To specify the weight for the WAR files, click Manage Modules and set the startup order. The following Web modules exist for Call Notification:
    • callnotify-router
    • callnotify-web
    • CallNotificationSipServlet
  7. Return to the Enterprise Applications list and click PX21_TPC_IMS. This is the EAR file name for Parlay X Third Party Call over SIP/IMS.
  8. To specify the weight for the EAR file, click Startup Behavior and set the startup order.
  9. Return to the Enterprise Applications list and click PX21_TPC_IMS.
  10. To specify the weight for the WAR file, click Manage Modules and set the startup order. The following Web module exists for Third Party Call: ThirdParty Call Parlayx21 SIP.
  11. Click Save to save changes to the master configuration.
  12. Restart the PX21_CN_IMS and PX21_TPC_IMS applications.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.