gnokii-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Text vs PDU mode & the SMSC


From: Richard Herselman
Subject: Text vs PDU mode & the SMSC
Date: Thu, 10 Dec 2009 15:09:17 +0200
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

Dear List,

I'm using gnokii 0.6.26.dfsg-3 from the stable repos on a Debian Lenny 5.0.3 box with a USB flip-flop device. I can query the modem at /dev/ttyUSB1 with gnokii --identify etc.

1. Is there any way to force gnokii to send SMSs using text mode and not PDU mode? The device seems to supports both, but our network operator only supports text mode, so trying PDU mode won't ever work.

2. Is there any way to permanently set the SMSC number, e.g. in the gnokii config file, or otherwise customize the AT commands that gnokii sends (short of trying to hack the source code)? I've been unable to have gnokii retrieve the SMSC from the SIM card, even though the "SIM message centre" setting shows the correct number when I install the same SIM card in my Nokia phone.

Running "gnokii --getsmsc" gets me:

[...snip...]
Received message type 23
No. 1: "" (default name)
SMS center number is
No default recipient number is defined
Messages sent as Text
Message validity is Unknown
Error: The given memory location is invalid.
Serial device: closing device

With regards to my first question, here is the output from running "gnokii --sendsms 0821234567 --smsc +27829119", where it shows "PDU mode set", no matter what I try:

utah:/home/smsd# gnokii --sendsms 0821234567 --smsc +27829119
GNOKII Version 0.6.26
LOG: debug mask is 0x1
Config read from file /root/.gnokiirc.
phone instance config:
model = AT
port = /dev/ttyUSB1
connection = serial
initlength = default
serial_baudrate = 19200
serial_write_usleep = -1
handshake = software
require_dcd = 0
smsc_timeout = 10
rfcomm_channel = 1
sm_retry = 0
Initializing AT capable mobile phone ...
Serial device: opening device /dev/ttyUSB1
Serial device: setting RTS to high and DTR to high
Message sent: 0x00 / 0x0004
41 54 5a 0d | ATZ write: [ATZ<cr>]
read : [ATZ<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x000a
02 41 54 5a 0d 0d 0a 4f 4b 0d | ATZ OK Received message type 00
Message sent: 0x00 / 0x0005
41 54 45 31 0d | ATE1 write: [ATE1<cr>]
read : [ATE1<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x000b
02 41 54 45 31 0d 0d 0a 4f 4b 0d | ATE1 OK Received message type 00
Message sent: 0x00 / 0x000a
41 54 2b 43 4d 45 45 3d 31 0d | AT+CMEE=1 write: [AT+CMEE=1<cr>]
read : [AT+CMEE=1<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x0010
02 41 54 2b 43 4d 45 45 3d 31 0d 0d 0a 4f 4b 0d |  AT+CMEE=1   OK
Received message type 00
Message sent: 0x06 / 0x0007
41 54 2b 47 4d 4d 0d | AT+GMM write: [AT+GMM<cr>]
read : [AT+GMM<cr><cr><lf>Modem<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x06 / 0x0016
02 41 54 2b 47 4d 4d 0d 0d 0a 4d 6f 64 65 6d 0d |  AT+GMM   Modem
0a 0d 0a 4f 4b 0d | OK Received message type 06
Message sent: 0x06 / 0x0008
41 54 2b 43 47 4d 49 0d | AT+CGMI write: [AT+CGMI<cr>]
read : [AT+CGMI<cr><cr><lf>Victory<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x06 / 0x0019
02 41 54 2b 43 47 4d 49 0d 0d 0a 56 69 63 74 6f |  AT+CGMI   Victo
72 79 0d 0a 0d 0a 4f 4b 0d | ry OK Received message type 06
Message sent: 0x61 / 0x0009
41 54 2b 43 53 43 53 3f 0d | AT+CSCS? write: [AT+CSCS?<cr>]
read : [AT+CSCS?<cr><cr><lf>+CSCS: "IRA"<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x61 / 0x001f
02 41 54 2b 43 53 43 53 3f 0d 0d 0a 2b 43 53 43 |  AT+CSCS?   +CSC
53 3a 20 22 49 52 41 22 0d 0a 0d 0a 4f 4b 0d | S: "IRA" OK Received message type 61
Initialisation completed
Please enter SMS text. End your input with <cr><control-D>:
Test SMS message
General Data Coding
dcs: 0x0
Length: 0x10
user_data_length: 0xe
ValidityIndicator: 2
user_data: D4F29C0E9A36A7A076793E0F9FCB
Sending
Message sent: 0x63 / 0x000a
41 54 2b 43 4d 47 46 3d 30 0d | AT+CMGF=0 write: [AT+CMGF=0<cr>]
read : [AT+CMGF=0<cr><cr><lf>OK<cr><lf>]
Message received: 0x63 / 0x0010
02 41 54 2b 43 4d 47 46 3d 30 0d 0d 0a 4f 4b 0d |  AT+CMGF=0   OK
Received message type 63
PDU mode set
Sending initial sequence
Message sent: 0x64 / 0x000b
41 54 2b 43 4d 47 53 3d 32 37 0d | AT+CMGS=27 write: [AT+CMGS=27<cr>]
read : [AT+CMGS=27<cr><cr><lf>> ]
Message received: 0x64 / 0x000f
01 41 54 2b 43 4d 47 53 3d 32 37 0d 0d 0a 3e    |  AT+CMGS=27   >
Received message type 64
Got response 0
Sending frame: 05917228199111000A8180422669700000AA10D4F29C0E9A36A7A076793E0F9FCB
Message sent: 0x21 / 0x0043
30 35 39 31 37 32 32 38 31 39 39 31 31 31 30 30 | 0591722819911100
30 41 38 31 38 30 34 32 32 36 36 39 37 30 30 30 | 0A81804226697000
30 30 41 41 31 30 44 34 46 32 39 43 30 45 39 41 | 00AA10D4F29C0E9A
33 36 41 37 41 30 37 36 37 39 33 45 30 46 39 46 | 36A7A076793E0F9F
43 42 1a | CB write: [05917228199111000A8180422669700000AA10D4F29C0E9A36A7A076793E0F9FCB^Z]
SMS Send failed (Command timed out.)
Serial device: closing device




reply via email to

[Prev in Thread] Current Thread [Next in Thread]