Hi,
I guess the right direction would be to call the place you bought it, or
sierra wireless and ask them what error 304 means.
Meanwhile a question: How were you able to compile kannel on Cygwin? last I
know of it doesn't because of some issues Cygwin has with thread locking.
Are these corrected? At what version?
BR,
Nikos
----- Original Message -----
From: "Bogus Bill" <[email protected]>
To: <[email protected]>
Sent: Tuesday, February 10, 2009 5:05 AM
Subject: Invalid PDU mode parameter error
I am running Kannel 1.4.1 under Cygwin. When it sends 125 characters
(here,
all asterisks) it works fine:
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: --> AT+CMGS=125^M
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: <-- >
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: send command status:
1
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: -->
0011000B814140136651F5
0000A77E2A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A
954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9
542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA55200
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: --> ^Z
2009-02-09 21:27:26 [2180] [6] DEBUG: AT2[/dev/com3]: <-- >
2009-02-09 21:27:27 [2180] [6] DEBUG: AT2[/dev/com3]: <-- +CMGS: 168
2009-02-09 21:27:27 [2180] [6] DEBUG: AT2[/dev/com3]: <-- OK
2009-02-09 21:27:27 [2180] [6] DEBUG: AT2[/dev/com3]: send command status:
0
But when it tries to send 126 asterisks, I get
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: --> AT+CMGS=126^M
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: <-- >
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: send command status:
1
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: -->
0011000B814140136651F5
0000A77F2A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A
954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9
542A954AA552A9542A954AA552A9542A954AA552A9542A954AA552A9542A954AA5522900
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: --> ^Z
2009-02-09 21:25:45 [2180] [6] DEBUG: AT2[/dev/com3]: <-- >
2009-02-09 21:25:46 [2180] [6] DEBUG: AT2[/dev/com3]: <-- +CMS ERROR: 304
2009-02-09 21:25:46 [2180] [6] ERROR: AT2[/dev/com3]: CMS ERROR: +CMS
ERROR:
304
2009-02-09 21:25:46 [2180] [6] ERROR: AT2[/dev/com3]: CMS ERROR: Invalid
PDU
mode parameter (304)
2009-02-09 21:25:46 [2180] [6] DEBUG: AT2[/dev/com3]: send command status:
1
I know the error comes from the modem (a Sierra Wireless 881U). What AT
command strings should I be tweaking to fix this? Can anyone send me in
the
right direction to diagnose this?
Thanks in advance,
Bill Rigdon
--
View this message in context:
http://www.nabble.com/Invalid-PDU-mode-parameter-error-tp21926828p21926828.html
Sent from the Kannel - User mailing list archive at Nabble.com.
