Policy attributes are retrieved from Subscription Management
in the Access Gateway and
are passed to the Parlay X Terminal Status 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 Terminal Status 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. ProcessUpToLimit
If set to
true,
the MaximumTarget limits specified is enforced.
- Type: Boolean
- Value: true
service.config. MaximumTargets
Number of targets
processed for the ProcessUpToLimit policy, if the GetStatusForGroup
operation is set to true.
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.config.presence.PresenceServerResourceName
The
resource name to use when communicating with the Traffic Shaping component.
- Type: String
- Value: PresenceServer
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.
- Type: String
- Value: TerminalStatus_IMS = PX21_TS_IMS
service.config.presence.TerminalBusyRpidActivities
A
comma-separated list of the RPID activities that indicate a terminal
is busy.
- Type: String
- Value: on-the-phone
service.config.presence.PresenceFetchTimeoutInMillis
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.
- Type: Integer
- Value: 1000
service.standard.BusyAvailable
Defines whether
busy can
be returned as a status or be a trigger.
- Type: Boolean
- Value: true
service.standard.MaximumNotificationFrequency
Maximum
rate of notification delivery in milliseconds (also can be considered
minimum time between notifications). Smaller values are more restrictive.
service.standard.MaximumNotificationDuration
Maximum
amount of time a notification can be configured for. Smaller values
are more restrictive.
- Type: Integer
- Value: 3600000 (1 hour)
service.standard.MaximumNotificationAddresses
Maximum
number of addresses for which a notification can be set up. Smaller
values are more restrictive.
service.config.DefaultNotificationDuration
Default
duration for a startPresenceNotification operation. Specified in milliseconds.
Smaller values are more restrictive.
- Type: Integer
- Value: 86400000 (24 hours)
service.standard.MaximumCount
Maximum number
of notifications that can 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.
- Type: Boolean
- Value: true
service.standard.GroupSupport
Defines whether
groups can be included with addresses.
- Type: Boolean
- Value: true
service.standard.NestedGroupSupport
Defines
whether nested groups can be included in group definitions.
- Type: Boolean
- Value: true
service.config.ims.InterOperatorIdentifier
The
setting can be either an empty string or a generated value, per RFC
3261 Section 25. If it is 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 Web service treats
as indicating a group URI. This setting must be coordinated with the
Group List Manager component configuration.