Policy attributes are retrieved from Subscription Management
in the Access Gateway and
are passed to Parlay X SMS over SMPP 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 SMS over SMPP parameters
found in the TWSS Administration Console can
be supplied on a per-requester or per-operation level by using the
prefix service.config.SMS_IMS. 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.standard.VirtualNumber
The number that
will be used as source address in Parlay sendSms call. In Parlay,
this need to be valid address in the network; otherwise the sendSms()
call will fail. Not required.
- Type: String
- Value: tel:111112223300
service.standard.MaximumNotificationAddresses
Maximum
number of addresses for which a notification can be set up. For some
services, this limit is used only if
service.config.ProcessUpToLimit is
true. Not required.
service.config.ChargeForFirstSegmentOnly
If
true, then charging information for large messages is included only
in the first segment. If false, then charging information is included
in all segments. (In the case of a single-segment message, charging
information is always included in the segment.) Required.
- Type: Boolean
- Value: true
service.config.messaging.ConfirmDelivery
Causes
the final status to be delayed for a send request until the backend
reports back on each target. The ReceiptRequest is a request for a
notification on the results of the send request from
Parlay X SMS over SMPP back
to the requester, and it requires that the policy be true in order
for the notification to have meaning and for the notification to be
sent. Not required.
- Type: Boolean
- Value: false
service.config.MaximumTargets
The
maximum number of targets the Web service implementation should use
in a single message. This number is used by the common layer if
service.config.ProcessUpToLimit is
set to true. Not required.
service.config.ProcessUpToLimit
If
true, then enforce
service.config.MaximumTargets.
Not required.
- Type: Boolean
- Value: true
service.config.ReceivedRetainTime
Time
in minutes to keep the received data messages in the database. Not
required.
- Type: Integer
- Value: 43200 (30 days)
service.config.StatusRetainTime
Time
in minutes to keep the send data status records in the database. Not
required.
- Type: Integer
- Value: 43200 (30 days)
service.config.messaging.target.Aliases
The
list of valid alias names currently configured, with target ranges
separated by semicolons. Not required.
- Type: SemiColonStringList
- Value: null
service.config.messaging.target.Ranges
The
list of target URI ranges separated by semicolons. Not required.
- Type: SemiColonStringList
- Value: null
service.config.messaging.Billing
The
charging code to be passed to the backend (SMSC) along with the request
for billing purposes. This policy is used only when the
WAP Push over SMPP and
Parlay X SMS over SMPP Web service implementations are
coresident on the same server. Not required.
service.custom.messaging.ServiceType
The type
of messaging service to use, for billing purposes. Not required.
service.custom.priorityEnabled
Whether priority
is enabled. Use in conjunction with service.custom.requestPriority
to define the priority of messages according to which backend servers
the messages are associated with.
- Type: Boolean
- Value: true
service.custom.requestPriority
The priority
value that is set. When service.custom.priorityEnabled is true, this
policy defines the priority of messages for SMS over SMPP. Different
accounts with different priorities are created in the network element
(SMSC). For different accounts, only the user IDs and passwords of
the defined backend servers vary. IP address, port number, and other
details remain the same.
To define priority levels, use
service.custom.priority with
the following syntax:
service.custom.priority.backend_alias.priority.Primary = user,password
service.custom.priority.backend_alias.priority.Secondary = user,password
where:
- backend_alias is the alias for the backend.
- priority is the priority level; it matches
the value for service.custom.requestPriority.
- user is the user ID for the backend.
- password is password for the backend user
ID.
For example, to set priority levels for two backend aliases:
service.custom.priority.backend1.1.Primary = user,password
service.custom.priority.backend1.1.Secondary = user,password
service.custom.priority.backend2.1.Primary = user,password
service.custom.priority.backend2.1.Secondary = user,password
notification.Endpoint.Type
Determines
the type of import component to which your application connects. If
the value is set to OneAPI, the message is routed to the callout corresponding
to the SMS_OneAPIImport. If the value is set to JSON, the message
is routed to the callout corresponding to SMS_JSONImport. If the value
is null, then the application uses the import component that is defined
for the Web service your application is associating with.