WebSphere brand IBM WebSphere Presence Server, Version 7.0

Configuring Presence Server to interact with S-CSCF sources

Follow these steps to configure Presence Server to interact with external sources for the Serving-Call/Session Control Function (S-CSCF).

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.
To configure Presence Server to work with S-CSCF, you will need the following information:
  • SIP address of the S-CSCF server
  • P-asserted-identity of the requester authorized to get information from the S-CSCF server
  • URI for the authorized S-CSCF user
About this task

This value will appear in the P-Asserted-Id: header for outgoing SUBSCRIBE requests sent to the IBM® XDMS shared list server. The S-CSCF examines p-asserted-identity header verifying it relates to an authorized user.

To configure integration with S-CSCF, complete the following steps:

  1. Open SystemConfiguration.xml with a text editor.
  2. Modify the attributes on the S-CSCF tag for your preferred configuration. This tag identifies the S-CSCF server and establishes parameters for communicating with it.
    You can set the following attributes. By default, enable is set to false and the other attributes are blank.
    enable="false"
    true to enable integration with S-CSCF; false to disable it
    sipAddress=""
    Address of the S-CSCF server to which SUBSCRIBE requests are sent
    fromURI=""
    A valid SIP URI that will appear in the From: header for outgoing SUBSCRIBE requests sent to the S-CSCF.
    assertedIdentity=""
    URI, in scheme:identity format, of the requester authorized to get information from the S-CSCF server. The S-CSCF examines p-asserted-identity header verify it relates to an authorized user
    For the assertedIdentity attribute, the display name is optional. If you choose to define a display name, you must use the HTML code for symbols for the value of the attribute. For example, use
    <assertedIdentity="&quot;Super Admin&quot; &lt;glm:GLMSuperAdmin&gt;"/>
    instead of
    <assertedIdentity=""Super Admin" <glm:GLMSuperAdmin>" />
    subscribeExpiration="63"
    Time, in minutes, to specify in the Expire header when Presence Server sends SUBSCRIBE requests to the S-CSCF. The subscription will be refreshed as long as there are client subscriptions on the server.
    retryInterval="5"
    Time, in minutes, to wait before retrying a request that fails. This applies specifically to outgoing SUBSCRIBE requests sent to the S-CSCF. The valid range is 1-1440.
    specifyAssertedIdentityOnAllRequests="true"
    If set to true, a P-Asserted-Identity must be specified in all outgoing subsequent subscribe requests. If set to false, a P-Asserted-Identity is required only in the first outgoing SUBSCRIBE request but is not required in subsequent SUBSCRIBE requests.
    Here is an example of an S-CSCF tag:
    • <S-CSCF enable="true" sipAddress="sip:server.example.com:7010;transport=UDP" fromURI="sip:Admin1@example.com" assertedIdentity="&quot;Super Admin1&quot;&lt;sip:ps@example.com&gt;" subscribeExpiration="63" retryInterval="5" specifyAssertedIdentityOnAllRequests="true"/>
  3. Save and close the file.
  4. Open ConfigurationParams.txt with a text editor.
  5. 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
  6. 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
  7. 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.