hello.
i've posted previously about some kannel issues and i'm pleased to
report that we've slain many of the kannel dragons we encountered...
- fixed the dreaded System Error 35 problem on OSX server
- fixed Kannel's transcoding of GSM charsets
- worked around the SMPP message throttling limitations
- found a good consulting engineer on the commerical kannel list to
help us through telco acceptance testing.
so far so good.
for the life of me, though, i'm still stumped by how seemingly-
unreliable the modem support is. i posted this (below) back in may,
and while i've jabbed at this with a stick over and over again, the
modem is still not working reliably for me.
i wrote, from scratch, a serial port device controller that has
absolutely none of the problems that kannel is having, so i don't
think it's a problem endemic to the hardware. (fyi i've tried
switching to a different multi-tech f4 and get the same results)
at this point, i have to run a modem "hup" script in crontab
("http://localhost:13000/stop-smsc?
password=blahblahblha&smsc=viamodem", wait, then "start-smsc...")
in order to keep my modem going. only the complete reinitialization of
the modem during the start-smsc sequence stops the errors and un-jams
my modem.
i've tried playing with the keepalive command... sending this:
keepalive-cmd = "ATZ;+CMGF=0"
every 90s seems to make it better -- all that breaks is *inbound*
messages rather than both inbound AND outbound :)
anyway -- if anyone's got any ideas i'd love to hear them....
-- bh
bh briannakicksass at gmail.com
Fri May 16 19:31:17 CEST 2008
hi there.
i'm using kannel in a testing environment right now. i have kannel
successfully connecting to two things:
- a telco's SMPP gateway
- a server-attached modem
both seem to work. i have a single kannel conf that defines each
service, and messages seem to be routing correctly both directions on
both gateways.
after a few hours of running, though, my modem seems to get "gummed
up" and i get errors (below) when i try to send messages. it's a
multitech GPRS MTCBAGF4.
any ideas?
and i must be missing something here, but:
- **why does SMS box say "202 Sent" when the message wasn't sent and
kannel is well aware of that fact?**
- **why does the "reset-string" never get sent to the modem even when
i've reached "max-error-count" number of these errors?**
thanks
: b
#------------------------
# server virtual smsc
# ----------------------
group = smsc
smsc-id = viamodem
smsc = at
denied-smsc-id = telcosmpp
modemtype = multitech
speed = 4800
validityperiod = 17
keepalive = 90
sim-buffering = false
max-error-count = 1
device = /dev/tty.USA4Wfd51P3.3
#------------------------
# server modem
#-----------------------
group = modems
id = multitech
name = "multitech"
detect-string = "WAVECOM"
init-string = "AT+CNMI=2,2,0,0,0"
speed = 4800
need-sleep = true
no-pin = true
reset-string = "AT+CFUN=1"
# no-smsc = true
2008-05-15 08:55:56 [3234] [10] DEBUG: send_msg: sending msg to box:
<127.0.0.1>
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: TP-Validity-
Period: 90 minutes
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: --> AT+CMGS=24^M
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: send command
status: 1
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: -->
0011000B814196787929F70000110BB1582C068321D9355C0D
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: --> ^Z
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:57 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: send command
status: -1
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: --> AT+CMGS=24^M
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: send command
status: 1
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: -->
0011000B814196787929F70000110BB1582C068321D9355C0D
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: --> ^Z
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:57 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: send command
status: -1
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: --> AT+CMGS=24^M
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: send command
status: 1
2008-05-15 08:55:57 [3234] [6] DEBUG: AT2[viamodem]: -->
0011000B814196787929F70000110BB1582C068321D9355C0D
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: --> ^Z
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:58 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: send command
status: -1
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:58 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- >
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:58 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
2008-05-15 08:55:58 [3234] [6] DEBUG: AT2[viamodem]: <-- ERROR
2008-05-15 08:55:58 [3234] [6] ERROR: AT2[viamodem]: Generic error:
ERROR
