WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Administering Parlay X Terminal Status over SIP/IMS

After you deploy Parlay X Terminal Status over SIP/IMS, you can use the TWSS Administration Console to change the deployment configuration properties for the Web service and related Service Platform components.

TWSS Administration Console settings

This Web service implementation adds the following configurable settings to the TWSS Administration Console:
  • Services: Default values used for Parlay X Terminal Status over SIP/IMS:
    • Terminal Status Web Service: Allows Parlay X clients to retrieve rich presence information from IMS. The following lists the configurable runtime properties:
      • Maximum Notification Duration: Maximum notification duration in milliseconds.
      • Default Notification Duration: The default duration time for operations that establish notifications, which are specified in milliseconds. The smaller values are more restrictive.
      • Terminal Busy RPID Activities: A comma-separated list of RPID activities indicating that the terminal is busy.
      • Unlimited Count Allowed: An unlimited number of status updates are allowed, when set to true.
      • Maximum Notification Addresses: The maximum number of addresses a client can request in a single notification lookup.
      • Inter Operator Identifier: The InterOperatorIdentifier (ioi) is used to create the P-Charging-Vector orig-ioi and term-ioi parameters. The setting may be either an empty String or a "gen-value". If not empty, the service implementation includes P-Charging-Vector headers in its SIP signalling.
      • Service Implementation Name: The actual name used by the service. The name which is used in this field, has to be less than 127 characters in length.
      • Maximum Notification Frequency: The minimum time in milliseconds between notifications.
      • Presence Server SIP URI: All SIP requests for presence information are routed to this URI. If the request is blank, then the SIP requests will be routed to the address according to the URI of the presentity.
        Note: TWSS supports address URIs that use the following schemes only: tel:, sip:, sips:, short:.
      • Presence Server Traffic Shaping Resource Name: The resource name for the backing server.
      • Presence Fetch Timeout In Milliseconds: This is for a SIP-based “fetch” or CheckImmediate operation, which defines the maximum time it takes a synchronous Web Service to send a NOTIFY through the presence server. Fetches taking longer than this duration, will receive a NotRetrieved RetrievalStatus. The value is specified in milliseconds, and must be greater than zero.
      • Presence Server Resource Name: The resource name used when communicating with the Traffic Shaping component.
      • Process Up To Limit: If multiple target limits are enforced, then the limits which are specified by the Maximum Targets are set to true.
      • Additional Group URI Schemes: This setting specifies a comma-separated list of URI schemes that the service views as indicating a group URI. This setting must be coordinated with the Group List Manager component configuration.
      • Group Support: This value is set to true and is not configurable. Group URIs may be included in the address list.
      • Busy Available: If set to true, then this can be used as a criteria for notification.
      • Maximum Notification Count: The maximum number of notifications that a client may request.
      • Maximum Targets: If the ProcessUpToLimit is set to true, then the maximum number of targets for a GetStatusForGroup operation can be processed. Targets which are not processed will have their StatusData.RetrievalStatus set to "NotRetrieved".
      • SIP Fetch Timeout in Milliseconds: The maximum time a synchronous Web service operation should wait on a Presence server request.
      • Nested Group Support: This value is set to true and is not configurable. The true value supports nested groups in group definitions.
  • Common Components: Click the name of a Service Platform component–for example Fault Alarm Client or Usage Record Client–to configure it to work with this Web service implementation. If you leave the endpoint URI empty for a component, then the component is disabled.

You can receive additional information on specific properties from the online help in the TWSS Administration Console.

Policies

Policy attributes are retrieved from Subscription Management in the Access Gateway and are passed to the Parlay X Terminal Status over SIP/IMS Web service in the SOAP headers. If the policies are not found in the TWSS SOAP header, then the Web service uses the values that are defined in the TWSS Administration Console.

For information about default policy configuration, refer to the following topic: Default service policies for Parlay X Terminal Status over SIP/IMS.

Actions taken when a PX Notification endpoint is not configured properly

An improper or nonexistent configuration of a PX Notification endpoint in the TWSS Administration Console is not initially rejected by the Parlay X Terminal Status over SIP/IMS Web service. The Web service issues a SOAX0160 alarm after discovering the misconfigured PX Notification endpoint, but the alarm does not occur until after the initial startNotification request has been accepted. Because of the incorrectly configured PX Notification endpoint, Parlay X Terminal Status over SIP/IMS cannot send outbound notifications, (such as statusChanged, statusError, or statusEnd), to the Parlay X client.




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