access.log not logging correctly?

below is an extract from access.log (msisdn and message have been masked):

2002-10-03 11:10:11 Receive SMS [SMSC:] [SVC:] [ACT:] [from:xxxxxxxx] [to:1234] [flags:0:1:0:0:0] [msg:24:xxxxxxxxxxxx] [udh:0:]
2002-10-03 11:10:11 Sent SMS [SMSC:] [SVC:default] [ACT:] [from:13013] [to:xxxxxxxx] [flags:0:1:0:0:0] [msg:43:xxxxxxxxxxxxxxxxxx] [udh:0:]

the reply was never received... what makes me suspicious was the timestamps.... from my observation of the successfully-replied messages on my system, there should be a difference of several seconds between the "Receive" and the "Sent" log.

this is what bearerbox.log says:

2002-10-03 11:10:10 [5] DEBUG: AT2[/dev/ttyS0]: <-- +CMT: ,38
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: <-- 069156694895990408A149988631000020013011018023185324AB19634D9D44960C0693C
560B0592C1683C162
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: Numeric sender  <xxxxxxxx>
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: --> AT+CNMA^M
2002-10-03 11:10:11 [8] DEBUG: boxc_sender: sent message to <127.0.0.1>
2002-10-03 11:10:11 [7] DEBUG: boxc_receiver: got ack
2002-10-03 11:10:11 [7] DEBUG: boxc_receiver: sms received
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: TP-Validity-Period: 24.0 hours
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=50^M
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: <-- >
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: send command status: 1
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: --> 0011000881499886310000A72B5324AB19634D9D44960C0693C560B0592C1683C1622CE9D
0CA92C160B2180C368BC56230D80D
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: --> ^Z
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: <-- OK
2002-10-03 11:10:11 [5] DEBUG: AT2[/dev/ttyS0]: send command status: 0
2002-10-03 11:10:12 [5] DEBUG: AT2[/dev/ttyS0]: <-- >
2002-10-03 11:10:12 [5] DEBUG: AT2[/dev/ttyS0]: <-- ERROR

the last line is worrying.... is this normal? i notice that this only happens for the unreceived messages....

while i do not doubt that the at2 module is superior to at, i'm quite amazed about the fact that there is no longer any FAILED sending, except when the destination msisdn is invalid... how about the occasional connection problem with the base stations? i mean, i get "sending failed" on my mobile at least once a day but how does kannel handle this when it happens on the modem?

for accounting purposes, i need the logs to reflect the correct status... it's ok to fail but if it says "sent", it must really mean that the message has reached the smsc....

 


-> [email protected]


---------------------------------
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!