Mode
Wireless mode with one of the following functions enabled:
- SMS:SMPP
- SMS:XML
- SMS:CMPP
Syntax
send SMS `message` to `dest_address` destination address, from `source_address` source address. 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.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- 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.
- 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.
- receipt
- One of the following:
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.
Note: When the SMS:XML function is in enabled, default is the only available option.
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 on the user billing day.
The default source and destination address 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. No transformations are performed on the profile data of the subscriber 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 a subscriber; if the MSISDN for the subscriber cannot be determined, then no SMS message is sent and a trace log alert is generated.