Sorry, I have not been able to gather the information yet due to other interruptions. I will post back here when I have.
I have tried to replicate the problem with the information that you provided but I don't see the same behavior in my test.
Can you send me the configuration file of Diafaan SMS Server (menu options 'File-Export-Configuration') and the communication logs of both the SMPP Connector and the SMPP Gateway for one of the messages that causes this problem? Hopefully I can use that information to set up a test system that replicates the same problem.
I have a connector accepting inbound messages, which routes them to a gateway (using the built in routing).
The connection is send only. I am passing TLV source_subaddress so the PDUs are passing undecoded.
That works fine. The carrier connected to the gateway receives the message with the TLV. All is good. I visualise this process as the "outgoing messages" - into the connector and out over the gateway.
However - the client connected to the connector (who initiates the messages) get back, almost immediately, a deliver_sm from the connector with exactly the same source and destination, almost like it's echoed or "tromboned" back to me. The sequence number is different from the outgoing message. The client sends a deliver_sm_resp, but the connector logs an invalid sequence ID.
If the client disconnects then reconnects, then they get a flood of deliver_sm's from the connector of all the messages "tromboned" so far.
As far as I can tell, they are not being echoed back by the gateway (as the connector is send only to the gateway).
Any idea where I should be looking?
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 588
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1218