send SMS `specified` to `default` destination address, `default` TON and `default` NPI from `default` source address, `default` TON and `default` NPI on `now`. Request delivery receipt `default`. Select SMS Gateway `default`.

Mode

Wireless mode with the SMS:SMPP function:

Syntax

send SMS `message` to `dest_address` destination address, `ton` TON and `npi` NPI from `source_address` source address, `ton` TON and `npi` NPI on delivery-day. Request delivery receipt `receipt`. Select SMS Gateway `sms_gateway`.

Parameters

message
String. This text may contain policy parameters (described later in this section) to perform parameter substitution within the message text.
dest_address
String. If not the default, this overrides the configured address. You can specify dest_address as one or more comma-separated static values, or as one or more comma-separated references to custom fields in the subscriber profile.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

ton
If not the default, this overrides the configured Type of Number. One of the following:
  • default (default)
  • UNKNOWN
  • INTERNATIONAL
  • NATIONAL
  • NETWORK SPECIFIC
  • SUBSCRIBER NUMBER
  • ALPHANUMERIC
  • ABBREVIATED
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

npi
If not the default, this overrides the configured Number Plan Indicator. One of the following:
  • default (default)
  • UNKNOWN
  • ISDN (E163/E164)
  • DATA (X.121)
  • TELEX (F.69)
  • LAND MOBILE (E.212)
  • NATIONAL
  • PRIVATE
  • ERMES
  • INTERNET (IP)
  • WAP CLIENT ID
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

source_address
String. If not the default, this overrides the configured address.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

delivery-day
String. Enter a value in one of the following formats:
  • now (default)—Keep the default value now to deliver the SMS immediately when the policy is triggered.
  • day—Enter an integer between 1 and 31 to deliver the SMS on the specified day of the month. If the specified day of the month has passed for the current month, the SMS will be delivered on that day in the following month. If the specified day of the month does not exist in the current month, the SMS will be delivered on the last day of the month. Any value less than 1 or greater than 31 is invalid.
  • smart string—Enable the Evaluate as Expression checkbox. In the Value field, enter an arithmetic expression containing one of the following policy parameters:
    • {User.BillingDay} —The billing day for the subscriber profile. Resolves to an integer between 1 and 31. If this parameter is used, the parameter {User.custom_field}, where custom_field is a configured custom subscriber profile field, may also be used if the custom field resolves to an integer value.
    • {User.Pool.BillingDay}—The billing day for the pool profile of the subscriber. Resolves to an integer between 1 and 31. If this parameter is used, the parameter {User.Pool.custom_field}, where custom_field is a configured custom pool profile field, may also be used if the custom field resolves to an integer value.
    The arithmetic expression supports addition and subtraction and must not contain the default value now. The result will be evaluated with consideration to the number of days in the current month. For example, the expression {User.BillingDay}-4 would deliver the SMS four days before the billing day for the subscriber . If the expression would result in the SMS being sent in the past, the SMS will not be sent.
Note: Scheduled SMS delivery is only available when the billing type for the subscriber is monthly.
receipt
One of the following:
  • default (default)—Use global default configured for this MPE device.
  • No Delivery Receipt
  • Delivery Receipt on success and failure
  • Delivery Receipt on failure
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

sms_gateway
Select the SMS gateway to use for the send action. default uses the default SMS gateway configured for the Policy Server.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.

Click OK.

Description

Sends an SMS text message, with specified text, to the subscriber associated with the message.

Messages can be up to 254 characters long. If long message support is configured, SMS messages longer than 160 characters are split into segments and reassembled by the receiving device; messages of up to 1000 characters are supported. See the Oracle Communications Policy Management Configuration Management Platform Wireless User's Guide for information on configuring long message support.
Note: Messages over 1000 characters are truncated.

The default source and destination address, TON, and NPI configured on the MPE device can be used or overridden.

To send notifications to multiple destinations, you can specify dest_address as one or more comma-separated static values, or as one or more comma-separated references to custom fields in the subscriber profile. Destinations must all be of the same type; this ensures that the same TON and NPI settings configured in the policy action will apply to all destinations. No transformations are performed on the subscriber’s profile data by the MPE device, so custom fields used as alternate destinations must contain values formatted as required by the SMSC. Multivalued fields (LDAP attributes) are not supported.

If the addresses specified are not available (for example, if a custom field is not populated in the subscriber database), then the global default is used; if the global default is not configured, then the SMS message is sent to the MSISDN for the subscriber; if the MSISDN for the subscriber cannot be determined, then the SMS message is not sent and a trace log alert is generated.

You can request a receipt from the SMSC server, which will be logged in the file SMPP.log, when the message is delivered to the subscriber. You can request a receipt on success, failure, or in either case. See the Oracle Communications Policy Management Configuration Management Platform Wireless User's Guide for information on configuring delivery receipt default actions.

Example

send SMS `you have reached 80%% of your quota` to `{User.MSISDN},{User.AltDest1},{User.AltDest2}` destination address, `default` TON and `default` NPI from `614` source address, `default` TON and `default` NPI on `now`. Request delivery receipt `default`. Select SMS Gateway `default`.