User Guide

Table Of Contents
1070 Chapter 44: Using the SMS Event Gateway
Incoming PDU handling
If the ColdFusion SMS event gateway gets an Unbind PDU from the SMSC, it sends an
unbind_resp PDU to the SMSC, does a restart, and attempts to rebind to the SMSC.
When the event gateway receives an EnquireLink or any other request PDU from the SMSC, it
sends a default response to the SMSC.
The gateway receives incoming messages from the SMSC in deliver _sm PDUs; it does not
handle data_sm PDUs. Deliver_sm PDUs can contain user- or application-generated messages,
or disposition responses for messages that the gateway has sent. The gateway extracts the short
message field and source and destination addresses from the PDU, puts them in a CFEvent
object, and sends the object to ColdFusion event gateway services for delivery to the listener
CFC. For information on how the CFML application must handle these incoming messages, see
“Handling incoming messages” on page 1073.
Outgoing message handling
The gateway supports three types of outgoing messages from ColdFusion applications. The
CFML
sendGatewayMessage function or a listener CFC method cfreturn tag can specify the
following commands:
submit Sends a submit_sm PDU with the message contents to the SMSC. This PDU sends a
message to a single destination.
submitMulti Sends a submit_multi PDU with the message contents to the SMSC. This PDU
sends a message to multiple destinations.
data Sends a data_sm PDU with the message contents to the SMSC. This is an alternative to
the submit command, and is typically used by interactive applications such as those provided via a
wireless application protocol (WAP) framework.
The SMS gateway lets you control the contents of all of the fields of these PDUs. For more
information, see the documentation for the individual commands in “Sending outgoing
messages” on page 1075.
When you send a message, if the SMSC responds with a status that indicates that the message was
rejected or not sent, ColdFusion MX logs information about the failure in the eventgateway.log
file. If the SMSC indicates that the service type is not available (SMPP v5
ESME_RSERTYPUNAVAIL status or AT&T Serviced denied status), and the gateway
configuration file transient-retry value is set to yes, the gateway also tries to resend the message.
Outgoing message synchronization and notification
The gateway and SMSC communicate asynchronously: the gateway does not wait for a response
from the SMSC for one message before it sends another message. However, you can configure
your gateway instance so that the CFML
sendGatewayMessage function behaves asynchronously
or synchronously.
In asynchronous mode, the function returns when the message is queued in ColdFusion gateway
services.
In synchronous mode, the function waits until the SMSC receives the message and returns a
message ID, or an error occurs.