I've had cases of similar behaviour where the driver fails to send messages out
and nothing else but a restart helps.
I understood from the following messages that this is a fundamental problem
with the smpp driver. How to fix this?
Regards,
Indrek
Michael Mulcahy wrote:
Hi All,
There is a bug in the current SMPP driver that stops the driver from
accepting messages to be submitted to the SMSC.
Scenario:
SMPP SMSC configured as receiver and transmitter, transmitter and
receiver connected and bound successfully.
1) Receiver SMPP connection disconnects
2) SMPP SMSC status changed to SMSCCONN_RECONNECTING
3) Receiver SMPP connection reconnects to SMSC after reconnect delay
and sends bind_receiver pdu
4) In handling of bind_receiver_resp the status is incorrectly set to
SMSCCONN_ACTIVE_RECV as the previous status was SMSCCONN_RECONNECTING
(This does not take into account that the transmitter is still
successfully
connected)
5) Now the driver cannot receive any messages for submission to SMSC
as status is not SMSCCONN_ACTIVE.
There also appears to be a potential race condition in the
handling of the bind_transmitter_resp and the bind_receiver_resp pdus,
the status variable is modified in both places and is not protected.
Regards,
Michael Mulcahy.
ANAM Wireless Internet Solutions
http://www.anam.com mailto:[EMAIL PROTECTED]
+353 1 284 7555
Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland
