I have had Kannel running for the last several months and have been having
problems with sudden queuing of messages which corrects itself with a simple
stop and start of Kannel.  However, this morning it looks like nothing is
going out regardless of restarting Kannel and unplugging the modem.

Here is Kannel's status and a segment from the sms connection log:

Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52',
compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System
Linux, release 2.6.24-21-generic, version #1 SMP Tue Oct 21 23:09:30 UTC
2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version
2.6.30. Using native malloc.

Status: running, uptime 0d 0h 4m 57s

WDP: received 0 (0 queued), sent 0 (0 queued)

SMS: received 0 (0 queued), sent 0 (0 queued), store size 6

SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec

DLR: 0 queued, using internal storage

Box connections:
    smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 4m 56s)
 SMSC connections:
    *vzn00*    AT2[vzn00] (online 283s, rcvd 0, sent 0, failed 0, queued 11
msgs)

2008-11-07 07:58:48 [6456] [6] DEBUG: AT2[vzn00]: <-- >
2008-11-07 07:58:48 [6456] [6] DEBUG: AT2[vzn00]: send command status: 1
2008-11-07 07:58:48 [6456] [6] DEBUG: AT2[vzn00]: -->
0051000A8103414046490000A74705
0003020202402C90B26C36839A65B6FD9D76B340CEB79C8E2ECBDDA0221EFE9ED7E5651688586EBFC7F2F0380F4ABB41C176599E1E8759A0582E276B28
2008-11-07 07:58:48 [6456] [6] DEBUG: AT2[vzn00]: --> ^Z
2008-11-07 07:58:52 [6456] [6] DEBUG: AT2[vzn00]: <-- >
2008-11-07 07:58:52 [6456] [6] DEBUG: AT2[vzn00]: <-- ERROR
2008-11-07 07:58:52 [6456] [6] ERROR: AT2[vzn00]: Generic error: ERROR
2008-11-07 07:58:52 [6456] [6] DEBUG: AT2[vzn00]: send command status: -1
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: TP-Validity-Period: 24.0
hours
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: --> AT+CMGS=75^M
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: <-- >
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: send command status: 1
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: -->
0051000A8103414046490000A747050003020202402C90B26C36839A65B6FD9D76B340CEB79C8E2ECBDDA0221EFE9ED7E5651688586EBFC7F2F0380F4ABB41C176599E1E8759A0582E276B28
2008-11-07 07:58:54 [6456] [6] DEBUG: AT2[vzn00]: --> ^Z
2008-11-07 07:58:56 [6456] [6] DEBUG: AT2[vzn00]: <-- >
2008-11-07 07:58:56 [6456] [6] DEBUG: AT2[vzn00]: <-- ERROR
2008-11-07 07:58:56 [6456] [6] ERROR: AT2[vzn00]: Generic error: ERROR
2008-11-07 07:58:56 [6456] [6] DEBUG: AT2[vzn00]: send command status: -1
2008-11-07 07:58:58 [6456] [6] DEBUG: AT2[vzn00]: TP-Validity-Period: 24.0
hours
2008-11-07 07:58:58 [6456] [6] DEBUG: AT2[vzn00]: --> AT+CMGS=75^M
2008-11-07 07:58:58 [6456] [6] DEBUG: AT2[vzn00]: <-- >

I have a plethora of questions about the real meaning of some of the
elements of the status page but, has anyone seen this behavior and know a
fix?
Is this a potential modem/SIM/network hardware problem?

Any help would be greatly appreciated.

Thanks,

-Tony

Reply via email to