> But it can't read the SMSC number,
> which I think is the reason the SMS aren't delivered.
did you follow the suggestion in the warning message?
"Cannot read the SMSC number from your phone. If the sms send will fail,
please use --smsc option explicitely giving the number."
I saw that, but didn't know how to find the SMSC for my network. (Anyone on the list familiar with Telecom NZ who can help?) I hoped that extracting an SMS from the phone would reveal my SMSC, but my attempts to use --getsms with memory types ME ("Invalid type of memory") and SM, IN, OU, AR, F1 etc ("Current frame isn't handled by the incoming function") have all failed so far.
--getsmsc also returns "The current frame isn't handled by the incoming function".
0.6.18 is too old, you should upgrade to 0.6.22 anyway
Done, thanks.
> If not, how can I contribute best by testing and identifying the model
> this device corresponds to?
provide the debug log and the output of gnokii --identify
also copy what the display shows when you type *#0000# on phone keypad
address@hidden:~$ gnokii --config ~/.gnokiirc.2125 --identify
GNOKII Version 0.6.22
LOG: debug mask is 0x1
Config read from file /home/chris/.gnokiirc.2125.
phone instance config:
model = 6510
port = /dev/ttyUSB0
connection = dlr3p
initlength = default
serial_baudrate = 19200
serial_write_usleep = -1
handshake = software
require_dcd = 0
smsc_timeout = 10
rfcomm_channel = 1
sm_retry = 0
Connecting
Serial device: opening device /dev/ttyUSB0
Serial device: setting RTS to low and DTR to low
Serial device: setting RTS to high and DTR to high
Serial device: setting speed to 19200
Switching to FBUS mode
Serial device: setting speed to 115200
Getting model...
Message sent: 0x1b / 0x0006
00 01 00 07 01 00 |
[Received Ack of type 1b, seq: 80]
[Sending Ack of type 1b, seq: 3]
Message received: 0x1b / 0x0032
01 36 00 08 00 01 58 2c 00 26 56 20 52 32 30 31 | 6 X, &V R201
5f 30 33 77 32 34 5f 34 39 5f 31 32 2e 6e 62 72 | _03w24_49_12.nbr
0a 32 35 2d 30 37 2d 32 30 30 35 0a 52 0a 44 00 | 25-07-2005 R D
00 00 |
Received message type 1b
model length: 1
Received model R
Identifying...
Message sent: 0x1b / 0x0005
00 01 00 00 41 | A
Message sent: 0x1b / 0x0006
00 01 00 07 01 00 |
[Received Ack of type 1b, seq: 1]
[Sending Ack of type 1b, seq: 4]
Message received: 0x1b / 0x0006
01 36 00 01 02 00 | 6
Received message type 1b
Received imei
[Received Ack of type 1b, seq: 2]
[Sending Ack of type 1b, seq: 5]
Message received: 0x1b / 0x0032
01 36 00 08 00 01 58 2c 00 26 56 20 52 32 30 31 | 6 X, &V R201
5f 30 33 77 32 34 5f 34 39 5f 31 32 2e 6e 62 72 | _03w24_49_12.nbr
0a 32 35 2d 30 37 2d 32 30 30 35 0a 52 0a 44 00 | 25-07-2005 R D
00 00 |
Received message type 1b
Received revision V R201_03w24_49_12.
model length: 1
Received model R
IMEI : Unknown
Manufacturer : Nokia
Model : R
Product name : R
Revision : V R201_03w24_49_12.
Serial device: closing device
Entering "*#0000#" brings up a screen with the title "Model Number" and text "Nokia 2125". Other Nokias I have available (E70, 6820, 3100, 1100) all give a much more informative version screen than this. Is there another method to get the 2125 to confess its true identity?