SMS
SMS Attributes
| Name | Allowed values | Default value |
|---|---|---|
to |
Phone number |
See below |
from |
Phone number |
See below |
action |
A relative or absolute URL address |
None |
method |
GET, POST |
POST |
to
The 'to' attribute takes a valid E.164 phone number as a value. CPaaS will send an SMS message to this number. When sending an SMS during an incoming call, 'to' defaults to the caller. When sending an SMS during an outgoing call, 'to' defaults to the called party. The value of 'to' must be a valid phone number.
from
The 'from' attribute takes a valid E.164 phone number as an argument. When sending an SMS during an incoming call, 'from' defaults to the calling party. When sending an SMS during an outgoing call, 'from' defaults to the called party.
action
The 'action' attribute takes a URL address as an argument. After processing the <Sms> verb, CPaaS will make a GET or POST request to this URL with the form parameters 'SmsStatus' and 'SmsSid'. Using an 'action' URL, your application can receive synchronous notification that the message was successfully enqueued or not.
If you provide an 'action' URL, CPaaS will use the RCML received in your response to the 'action' URL request to continue the current call. Any RCML verbs occuring after an <Sms> which specifies an 'action' attribute are unreachable. If no 'action' is provided, <Sms> will finish and CPaaS will move on to the next RCML verb in the document. If there is no next verb, CPaaS will end the phone call.
method
The 'method' attribute takes the value 'GET' or 'POST'. This tells CPaaS whether to request the 'action' URL via HTTP GET or POST. This attribute is modeled after the HTML form 'method' attribute.