WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Default service policies for Parlay X Presence over SIP/IMS

Policy attributes are retrieved from Subscription Management in the Access Gateway and are passed to the Parlay X Presence over SIP/IMS 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.

The Parlay X Presence over SIP/IMS parameters found in the TWSS Administration Console can be supplied on a per-requester or per-operation level by prefixing it with service.config and including the resulting header within the incoming SOAP header. Policy-based setting overrides only allow policies that are more restrictive than the settings found in the console.

service.config.presence.PresenceServerSIPURI

If the PresenceServerSIPURI setting is not empty, the outbound SUBSCRIBE request will have a topmost Route header containing the PresenceServerSIPURI. The SIP Container will direct the request according to this Route header.

service.standard.MaximumNotificationDuration

The maximum amount of time a notification may be set up for. Smaller values are more restrictive.

service.config.presence.PresenceServerResourceName

The resource name to use when communicating with the Traffic Shaping component.

service.config.ServiceImplementationName

Used for Fault and Alarm component Web service and Usage Record component Web service. Must be 127 characters or less in length.

service.config.presence.PresenceFetchTimeoutInMillis

Used for a SIP-based fetch or CheckImmediate operation. Fetches taking longer than this duration will receive a NotRetrieved RetrievalStatus. The value is specified in milliseconds and must be greater than zero.

service.config.presence.SubscribePresenceTimeout

Maximum lifetime of state due to a subscribePresence request. Smaller values are more restrictive.

service.standard.MaximumNotificationFrequency

Maximum rate of notification delivery in milliseconds (also can be considered minimum time between notifications). Smaller values are more restrictive.

service.config.DefaultNotificationDuration

Default duration for a startPresenceNotification operation. Specified in milliseconds. Smaller values are more restrictive.

service.standard.MaximumCount

Maximum number of notifications that may be requested. Smaller values are more restrictive.

service.standard.UnlimitedCountAllowed

Allowed to specify unlimited notification count (either by not specifying the optional Count message part in StartNotificationRequest or by specifying a value of zero). False values are more restrictive.

service.standard.GroupSupport

Groups may be included with addresses.

service.standard.NestedGroupSupport

Defines if nested groups are supported in group definitions.

service.config.ims.InterOperatorIdentifier

The setting may be either an empty string or a gen-value per RFC 3261 Section 25. If not empty, the service implementation includes P-Charging-Vector headers in its SIP signaling.

service.config.AdditionalGroupURISchemes

While presentities may have only sip:, sips:, or tel: URI schemes, group definitions may use other URI schemes. This setting specifies a comma-separated list of URI schemes that the service treats as indicating a group URI. This setting must be coordinated with the Group List Manager component configuration.

service.config.presence.supplier.PublishPresenceTimeout

The expiration time for Presence information documents, which are stored in the Presence server.

service.config.presence.supplier.SubscribePresenceWinfoTimeout

The expiration timeframe for the SIP SUBSCRIBE requests watcher information.

service.config.presence.supplier.MaximumPublishDurationAllowed

If PUBLISH request is not processed within the specified time, the application responds with the Request Timeout to the Web Service request.



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