Hi,
That's correct. When you see that warning in the cimd2 driver, the request
is rejected. Incoming packet has same sequence number as last received
packet. Code thinks it is a dupplicate?
Maybe a bug, though. Code increases seq-number by 2. Therefore in a sequence
of received packets:
request->seq receive->seq
253 255 => 0
254 0? (reject)
Can someone confirm if this is the intended behaviour?
BR,
Nikos
----- Original Message -----
From: "Marcin Bockowski" <[email protected]>
To: "Kannel" <[email protected]>
Sent: Wednesday, February 25, 2009 11:46 AM
Subject: CIMD2 sequence number ...
Hello,
i can see in my logs some amount of:
2009-02-25 06:10:45 [25263] [6] WARNING: CIMD2[SMSC]: request had same
sequence number as previous.
2009-02-25 06:56:16 [25263] [6] WARNING: CIMD2[SMSC]: request had same
sequence number as previous.
...
and in this case SMS won't hit the sms-service :-/
My kannel works in pair with Nokia SMSC.
How to prevent such things?
Regards,
--
Marcin Boζkowski
http://ktosiu.com
