WebSphere brand IBM WebSphere Presence Server, Version 7.0

Configuring for SIP external sources

Follow these steps to configure Presence Server to interact with SIP external sources.

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.

Note that the file UpdateConfiguration.jar must be in the class path.

Before you can make configuration changes, you will need to know the external source's SIP address–starting with either sip or sips.
Note: For sips addresses, Transport Layer Security (TLS) is the only supported protocol.
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 SIP external source examines the p-asserted-identity header to verify that it relates to an authorized user.

To configure the SIP external source, enable the External Sources mechanism and provide the authenticated identity of the Presence Server. You can configure the SIP external source by completing the following steps:

  1. Open SystemConfiguration.xml with a text editor.
  2. Within the <externalSources> element, create a separate externalSource tag for each external source you want to define. Each externalSource tag defines a SIP external source and sets the protocols for communicating with it.
    You can set the following attributes for each external source. Default values, where applicable, are shown.
    enable="false"
    true to enable integration with this SIP external source; false to disable it
    sipAddress=""
    SIP address of the external source
    fromURI=""
    A valid SIP URI that will appear in the From: header for outgoing SUBSCRIBE requests sent to the external source.
    assertedIdentity=""
    URI, in scheme:identity format, of the requester authorized to get information from the SIP external source. The SIP external source examines the p-asserted-identity header to verify that 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="60"
    Time, in minutes, to specify in the Expire header when Presence Server sends SUBSCRIBE requests to the external source. 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 external source. The valid range is 1-1440.
    triggerEventPackage=""
    The event package with which the external source is associated
    sourceEventPackage=""
    The event package used for outgoing subscriptions against the SIP external source
    acceptHeader=""
    The values used for the Accept header in outgoing subscriptions in comma-separated format. for example accept1,accept2.

    If you leave this value blank, Presence Server sends outgoing subscription requests without an Accept header.

    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 externalSource tag:
    • <externalSource 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="20" retryInterval="10" triggerEventPackage="presence" sourceEventPackage="presence" acceptHeader="" specifyAssertedIdentityOnAllRequests="true"/>
  3. On the waitForExternalInformation tag, modify the maxInterval attribute to specify how long to wait while collecting information from IBM XDMS and other external sources before notifying the client.

    maxInterval specifies the time, in seconds, to wait while collecting information from IBM XDMS and other external sources before sending a notification to the client. For group subscriptions, the time is measured after the group content is received from IBM XDMS.

    Valid values are 0-60. The default value is 15.
    Note: Avoid setting the interval too small, to avoid having notifications sent before all information has been collected. It is also recommended that you select a value of 30 or below because a subscriber may invalidate the subscription if a notification is not returned within 30 seconds.
    For example:
    • <waitForExternalInformation maxInterval="15" />
  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.