gnokii-users
[Top][All Lists]
Advanced

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

Re: Nokia 3410 support / development help


From: Bertrik Sikken
Subject: Re: Nokia 3410 support / development help
Date: Sat, 30 Nov 2002 14:20:58 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826

Pawel Kot wrote:

On Fri, 29 Nov 2002, Bertrik  Sikken wrote:

I see no difference with other values.

I don't know what an SMSC location is exactly.
In the menu on the phone, I see in menu message/settings that there
are 5 specific profiles for sending SMSs each with its own phone
number (only in profile 1 the phone number is set) and one general
profile.with a couple of other settings.


Well, we need a brute force. You mentioned that you compared the speed of
the communucation with te windows software. Could you please sniff the
communication of the windwos software when:
- getting SMSC settings
- reading alarm info
At least these two things at the moment.

I did a little investigation. What I saw in the log I sent you
is that apparently the phone sends some unexpected packet of
data. In order to test this I added an extra call to SM_Block
in function GetSMSCenter, file nk6100.c:

static gn_error GetSMSCenter(GSM_Data *data, GSM_Statemachine *state)
{
 unsigned char req[] = {FBUS_FRAME_HEADER, 0x33, 0x64, 0x00};

 req[5] = data->MessageCenter->No;

if (SM_SendMessage(state, 6, 0x02, req) != GN_ERR_NONE) return GN_ERR_NOTREADY;
 SM_Block(state, data, 0x02);
 return SM_Block(state, data, 0x02);
}

The extra call to SM_Block is supposed to absorb the unexpected packet.
It seems to work in principle, stdout reports:
No. 1: "Set 1" (default name)
SMS center number is +31626000230
Default recipient number is 221
Messages sent as Text
Message validity is 24 hours

Stderr reports:
(...)
Found model "NHM-2"
Message sent: 0x02 / 0x0006
00 01 00 33 64 01 | 3d [Received Ack of type 02, seq: 6]
[Sending Ack of type 02, seq: 0]
Message received: 0x02 / 0x0004
01 0f 00 c9 | É Received message type 02
UNHANDLED FRAME RECEIVED
request: 0x02 / 0x0006
00 01 00 33 64 01 | 3d reply: 0x02 / 0x0004 01 0f 00 c9 | É Please read Docs/Reporting-HOWTO and send a bug report!
[Sending Ack of type 02, seq: 1]
Message received: 0x02 / 0x0022
01 08 00 34 01 f0 00 f6 00 03 81 22 f1 00 00 00 | 4 ð ö "ñ 00 00 00 00 00 07 91 13 26 06 00 32 f0 00 00 00 | & 2ð 00 00 | Received message type 02
Serial device: closing device

Interestingly, in the log from the windows software each of the
transfers involved in getting the smsc has two extra bytes with
something that looks like a sequence number (0x142->0x144->0x146)

Regards,
Bertrik





reply via email to

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