NoahLink wrote:
> They suggested we lower our ping time to 22 seconds
which I did. I am getting
> the following errors pretty regularly. I suspect maybe
it is a config value in
> my CFG file but i'm not sure. Thoughts?
using synch or asynch mode? is network retry turned on?
what's the message
sending rate?
> Jan 14, 2009 10:15 AM Information SMS monitor
(GateWayName)
> SMSGateway (GateWayName) Ping reports connection bad,
restarting
this looks like the issue. network problems or simply on
their end.
> Can you hook me up with however you have your CFG file
setup so i can compare?
> I am using mostly the same values that came with the
example one with a couple
> tweaks (the ping seconds for example).
won't do you much good but:
# This is the IP address of SMSC
ip-address=xxxxx
# Port to bind to
port=xxxxx
# Your system id
system-id=xxxxx
# Your password
password=xxxxx
# The source address for this client
source-ton=1
source-npi=1
source-address=xxxxx
# The address range this smpp client will serve
addr-ton=1
addr-npi=1
address-range=xxxxx
# Message sending rate; how many messages per second is the
# gateway allowed to send to your service provider.
message-rate=100
# 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=10
# 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
8
Replies
AdChoices