SMS Gateway incoming message CFEvent structure 1043
SMS Gateway incoming message CFEvent structure
The SMS gateway puts the following information in a CFEvent instance that it sends to the CFC
listener method:
Field Value
OriginatorID
Contents of the PDU
source_addr
field, the address of the device that sent
the message.
CfcMethod
Listener CFC method name. Value of the configuration file
cfc-method
entry, or
onIncomingMessage
if the configuration file does not have this
entry.
Data.MESSAGE
Contents of the
short_message
field of the PDU.
Data.sourceAddress
The address of the device that sent this message.
Data.destAddress
The address to which the message was sent; an address in the range
specified by the gateway configuration file
address-range
setting.
Data.esmClass
Contents of the PDU esm_class field. Identifies the message type. A
number in the range 0-255 representing a Byte value, where bits 2-5 (0-
indexed) indicate the message type, and therefore the contents of the
data.MESSAGE field, as follows. (Reserved values are omitted.)
xx0000xx
Normal
message
xx0001xx
SMSC
delivery
receipt
xx0010xx
SME
Delivery
Acknowledgement
xx0100xx
SME Manual/User Acknowledgement
xx0110xx
Conversation abort (Korean CDMA only)
xx1000xx
Intermediate
Delivery
Notification
For more information on this field, see the SMPP specification.
Data.protocol
Contents of the PDU protocol_id field. Meaningful for messages sent from
GSM networks only. For more information, see the GSM 03.40
specification.
Data.priority
Contents of the PDU priority_flag field. A message priority level set by the
originating SME, in the range 0-3; 0 is the lowest priority and 3 is the
highest priority. The specific priority level meaning depends on the
originating network. For more details, see the SMPP specification.
Data.registeredDelivery Contents of the PDU registered_delivery field, indicating the type of
delivery receipt or acknowledgement that the sender requested. A number
in the range 0-32, representing the sum of the following values:
0 No
SMS
delivery
receipt requested
or
1 SMSC delivery receipt requested on delivery success or failure
or
2 SMSC delivery receipt requested on delivery failure only
Plus
0 No SME acknowledgement requested
or
4 SME Delivery Acknowledgement requested
or
8 SME Manual/User Acknowledgement requested
or
12
Both Delivery and Manual/User Acknowledgements requested
Plus
0 No
Intermediate
notification requested
or
16 Intermediate notification requested
Summary of Contents for COLFUSION MX 7 - INSTALLING AND USING COLDFUSION MX
Page 1: ...COLDFUSION MX7 CFML Reference...
Page 20: ...20 Chapter 1 Reserved Words and Variables...
Page 50: ...50 Chapter 2 ColdFusion Tags cfelse br Searching cfif cfloop cfif...
Page 101: ...cfdefaultcase 101 cfdefaultcase cfswitch cfoutput Your grade is grade cfoutput...
Page 115: ...cfdocumentsection 115 cfdocumentsection cfoutput cfdocument...
Page 411: ...cftable 411 cftable body html...
Page 515: ...Chr 515 maxlength 5 p input type Submit name input type RESET cfform...
Page 605: ...GetEncoding 605 WriteOutput The encoding is theEncoding cfscript cfif...
Page 629: ...GetProfileString 629 tr td input type Submit name Submit value Submit td td td tr table form...
Page 655: ...IIf 655 cfoutput IIf Hour Now GTE 12 DE It is afternoon or evening DE It is morning cfoutput b...
Page 664: ...664 Chapter 3 ColdFusion Functions cfelse h3 Conversion error h3 cfif...
Page 687: ...IsStruct 687 cfoutput cfquery cfif cfoutput hr Employee Add Complete cfoutput cfcase cfswitch...
Page 751: ...LSDateFormat 751 hr noshade cfoutput cfloop...
Page 861: ...StructFind 861 cfquery cfif cfoutput hr Employee Add Complete cfoutput cfcase cfswitch...
Page 903: ...Val 903 value Is the beginning numeric name form...
Page 932: ...932 Chapter 3 ColdFusion Functions...
Page 944: ...944 Chapter 4 ColdFusion MX Flash Form Style Reference...
Page 962: ...962 Chapter 5 Application CFC Reference...
Page 1054: ...1054 Chapter 6 ColdFusion MX Event Gateway Reference...