WebSphere brand IBM WebSphere Presence Server, Version 7.0

Adding headers to outgoing NOTIFY requests

You can configure Presence Server to copy additional headers from incoming SUBSCRIBE requests to NOTIFY requests on the same session.

Before you begin
You will need the following files to complete this task. After you install the Presence Server product, these files are found in the directory was_root/installableApps/presence/scripts/config.
  • SystemConfiguration.xml
  • ConfigurationParams.txt
  • UpdateConfiguration.jar
Before you can make changes to your configuration, the file UpdateConfiguration.jar must be in the class path.
About this task

The 3GPP specification for SIP requires that an application server be able to extract certain types of headers from incoming SUBSCRIBE requests and insert them into the corresponding NOTIFY requests. For example, when an application server acting as an originating user agent (UA) issues a SUBSCRIBE request and receives a NOTIFY request, it expects to collect and use information from the P-Charging-Vector header that is included in the request.

You can configure Presence Server so that it includes copies specific types of headers from SUBSCRIBE requests and includes them in the NOTIFY requests it sends.

To arrange for one or more header types to be copied and included in NOTIFY requests, complete the following steps:

  1. Open SystemConfiguration.xml with a text editor.
  2. In the <copyToNotifyHeaders> element, set enable="true".
  3. Within the <copyToNotifyHeaders> element, create one or more header tags–one for each header type that you want to configure.
    You can set the following attribute for header. There is no default value.
    name="header_type"
    Name of the header type, as specified in 3GPP specification 24.229 for SIP.
    For example:
    • <copyToNotifyHeaders enable="true">
    • <header name="P-Charging-Vector" />
    • </copyToNotifyHeaders>
  4. Save and close the file.
  5. Open ConfigurationParams.txt with a text editor.
  6. Update the following parameters for your environment:
    • cfg.system = xml_path (where xml_path is the directory location for SystemConfiguration.xml)
    • username = database_administrator_user_name
    • password = database_administrator_password
    • DB2 dbDriver = com.ibm.db2.jcc.DB2Driver
    • Oracle dbDriver = oracle.jdbc.driver.OracleDriver
    • DB2 dbConnectionString = jdbc:db2://database_host_name:database_port/database_name
    • Oracle dbConnectionString = jdbc:oracle:thin:@database_host_name:database_port:database_name
  7. Run the java command that is appropriate for your operating system:
    Important: Enter the following parameters on a single line.
    • AIXLinux java -classpath UpdateConfiguration.jar: jdbc_path CmdConfig config_path/ConfigurationParams.txt
    (where jdbc_path is the directory location for your JDBC drivers and config_path is the directory location for ConfigurationParams.txt)
    Important: JDBC drivers must be separated by a colon.
    For example:
    • AIX /usr/IBM/WebSphere/AppServer/java/bin/java -classpath UpdateConfiguration.jar:/opt/IBM/db2/V9.5/java/db2jcc.jar:/opt/IBM/db2/V9.5/java/db2jcc_license_cu.jar CmdConfig ConfigurationParams.txt
    • Linux /opt/IBM/WebSphere/AppServer/java/bin/java -classpath UpdateConfiguration.jar:/opt/IBM/db2/V9.5/java/db2jcc.jar:/opt/IBM/db2/V9.5/java/db2jcc_license_cu.jar CmdConfig ConfigurationParams.txt
  8. Restart the application:
    1. Click Applications > Application types > WebSphere Enterprise Applications.
      Note: If you are using WebSphere® Application Server version 6.1.0.x, reach this window by clicking Applications > Enterprise Applications.
    2. Select the check box associated with the Presence Server.
    3. Click Stop. The Application Status column should indicate a Stopped status.
    4. Click Start. The Application Status column should indicate a Started status.



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