That is correct, each message part triggers an HTTP callback if not all of the message parts are received within the timeout period. There is no easy way to count each long message only once. If you want to do that you must keep a list of received message IDs and skip counting the message parts where the message ID is recent and already in the list.
It is not normal for this error to occur very often, this might be an indication of an underlying issue with your configuration, modems or SMPP server.
I'm just seeking some clarification.
I am seeing quite a few messages like this :
Timeout on partially received message(s), 14 message parts transferred to the received messages list.
The default messageIn handling is CombineMessageParts.
The docs suggest this will generate 14 "message_in" messages through the http callback, is this correct? It would therefore be up to me to ensure only one of those is counted statistically (by checking the message_parts fields).
Most Users Ever Online: 529
Currently Browsing this Page:
Guest Posters: 657
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1425