[EMAIL PROTECTED] wrote:
Hello,
we're using Kannel 1.4.1 on Solaris 10 to send UCP messages with
requests for Delivery Notification. Each message gets a unique
identifier, the submission to the SMSC is logged to a database.
On every receipt of a UCP message type 53 Kannel sends two messages to a
cgi script which does the logging of the DNs to the database.
At this point Kannel seems to mix up things:
We sent UCP messages for both an active and an switched off mobile and
got UCP messages with a delivery state of ..0/000
...("Delivered"/"Success") and ..1/107.. ("buffered"/"Absent
subscriber"). Upon this Kannel generated one HTTP message for the active
mobile ("smsc submit") and THREE messages for the inactive ("smsc
submit"), ("message buffered") which are OK and ("delivery success")
which seem to belong to the active mobile and makes the whole thing
worthless.
We searched the forum for this issue but found nothing.
What could we have overseen? (Yes, we DO use unique identifiers.)
Hi Bernd,
this sounds to me like a UCP timestamp race-condition.
As you may know, UCP is unlike SMPP not suitable to handle a UUID for the ACK
PDU it returns on a MT request, literally this means we get the timestamp of the
SMSC for it in the ACK.
Inside Kannel we used that as identifier, which can mix up things if you send 2
or more messages to the same destination within the same second, and SMSC
responds in the ACK with the same timestamp for those MTs.
Ok, I recall... you said 2 targets, one that is online and the other is off.
Hmm...
Can you please forward us the bearerbox.log in debug log-level for review? (In
case privacy is the matter, please blank out the MSISDN parts).
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
