Table of Contents
Advertisement
DEVELOPING COLDFUSION 9 APPLICATIONS
Using External Resources
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,
places 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
messages" on page 1298.
Outgoing message handling
The gateway supports three types of outgoing messages from ColdFusion applications. The CFML
function or a listener CFC method
sendGatewayMessage
Sends a submit_sm PDU with the message contents to the SMSC. This PDU sends a message to a single
submit
destination.
Sends a submit_multi PDU with the message contents to the SMSC. This PDU sends a message to
submitMulti
multiple destinations.
Sends a data_sm PDU with the message contents to the SMSC. This command is an alternative to the submit
data
command, and interactive applications such as those provided via a wireless application protocol (WAP) framework
typically use it.
The SMS gateway lets you control the contents of all of the fields of these PDUs. For more information on the
individual commands, see
"Sending outgoing
When you send a message, if the SMSC responds with a status that indicates that the message was rejected or not sent,
ColdFusion 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
function behaves asynchronously or synchronously.
sendGatewayMessage
• 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.
For more information on configuring message synchronization and sending messages synchronously, see
"Controlling SMS message sending and
cfreturn
messages" on page 1300.
response" on page 1303.
Last updated 8/5/2010
"Handling incoming
tag can specify the following commands:
1296
Advertisement
Table of Contents
