smpp gateway

Report · Aug 05, 2011

Hi i am having some problems with the smpp gateway which are

some message id are not coming back to me
lots of statuses are not coming back to me

i am not sure what i causing this out of 3000 sms sent 200 had no status returned and 60 had no message id, any ideas how i can debug or solve this i have attached my cfg file.

#
# SMSGateway configuration file
# Test server config
#

# This is the IP address of SMSC
ip-address=sms1.cardboardfish.com

# Port to bind to
port=8000

# Your system id
system-id=my_username

# Your password
password=my_password

# The source address for this client
source-ton=5
source-npi=0

# This is a made-up address
source-address=5551213

# The address range this smpp client will serve
# Generally the same as your source address
addr-ton=5
addr-npi=0
address-range=5551213

# Message sending rate; how many messages per second is the
# gateway allowed to send to your service provider.
# This can be a decimal (i.e. 0.1). 0 is unlimited.
# The default is 100 messages per second.
message-rate=100.0

# The mode of the gateway; Either synchronous or asynchronous
# In synchronous mode the gateway will wait for the response
# from the server when sending a message and the SendGatewayMessage()
# CFML function will return the SMS messageID of the message
# or an empty string if their is an error. In asynchronous mode,
# the gateway will not wait for a response and the SMS messageID
# will NOT be returned from SendGatewayMessage().
# The default is synchronous.
mode=synchronous

# Should the gateway retry delivery on Network Errors?
# If a network error occurs while trying to deliver a message,
# should the message be queued for delivery when the gateway
# is able to re-bind to the SMSC. This is useful if the gateway
# is in asynchronous mode, where no error status is returned from
# the CFML SendGatewayMessage() function.
# The default is no.
network-retry=no

# Should the gateway retry delievery on Transient Errors?
# If an error is returned from the SMSC that indicates
# the message may be able to be delivered in the future,
# should the gateway attemp to resend send the message?
# This is useful if the gateway is in asynchronous mode,
# where no error status is returned from the CFML
# SendGatewayMessage() function.
# The default is no.
transient-retry=no

##################################################
# Everything below here is usually OK.
##################################################

# The function in the Gateway CFC which the is called
# when an incoming message arrives.
#
cfc-method=onIncomingMessage

# The default destination address info
destination-ton=1
destination-npi=1
# You can't have a default destination
# destination-address=

# The service type can be empty or one of
# the following values:
# CMT, CPT, VMN, VMA, WAP or USSD
# service-type=

# From the spec:
# Identifies the type of system requesting the bind.
# This may enable SMSC responses which are
# particular to a given type of ESME.
system-type=SMPP

# The receive timeout is a timeout for trying to receive a message
# from the SMSC. If you want go to infinite wait until a PDU
# is received, set the receive-timeout to -1.
# The value is in seconds. The default is 30 seconds.
receive-timeout=10

# The ping interval is how often the SMS Gateway will send an
# EnquireLink PDU to the server to verify the health of the connection.
# The value is in seconds. The default is 60 seconds.
ping-interval=60

# The number of connection attempts the gateway will make until it gives up.
# Use -1 to retry until connected. The default is -1 (try forever).
retries=-1

# Connection retry interval; how long to wait between connection attemps.
# The value is in seconds. The default is 10 seconds.
retry-interval=10

Report · Aug 06, 2011

On 8/5/2011 8:34 PM, craig_mac said:

i am not sure what i causing this out of 3000 sms sent 200 had no status
returned and 60 had no message id, any ideas how i can debug or solve this i

what does "no status returned" mean? no delivery receipt? does your SMS vendor

return hex IDs (you won't be able to tell from the IDs as cf will try to convert

them to decimal)? if so there's a bug w/cf's hex-to-decimal conversion, see:

http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=86928

no IDs returned depends on your SMS vendor. for the ones i've dealt with it,

often means they couldn't send the SMS because of an issue w/the phone number,

the network, etc. there should be an entry in the event gateway log for those.

Report · Aug 06, 2011

Hi Paul,

Yes delivery reciepts, i spoke to my provider and they think coldfusion is getting confused with the reponses they send back, they send the messageid in 1 response, the status in another and "something else" in another.which i dont have to hand at the min.

the "something else" causes errors in my logs which forces the connection to be reset

The provider thinks coldfusion is expecting an id and they may send the "something else" so coldfusion trys to convert the response to an id but cant and error.

let me know what you think.

Report · Aug 06, 2011

> Yes delivery reciepts, i spoke to my provider and they think coldfusion is
> getting confused with the reponses they send back, they send the messageid in
> 1 response, the status in another and "something else" in another.which i
> dont have to hand at the min.

the messageID comes back synch, immediately. the delivery receipt depends on 
their network & of course on the receiver, maybe they will return the receipt, 
maybe not.

if your vendor is standard, the  receipt comes back as a "regular" SMS except 
the CFEvent.Data.esmClass is 4 (vs 0 for "normal" SMS & 64 for multipart SMS). 
you have to parse that message to get the receipt (but you probably know that).

> the "something else" causes errors in my logs which forces the connection to
> be reset

why are they sending *anything else*?

> The provider thinks coldfusion is expecting an id and they may send the
> "something else" so coldfusion trys to convert the response to an id but cant
> and error.

no idea what "something else" is or why they'd be sending it. if it's an error, 
cf knows that as long as your vendor is standard. if it's clearly a string, cf 
just passes that on to your onIncomgMessage() method where you can deal with it.

did you ask them about the format of the ID?

Adobe Community

smpp gateway