fbus voice call info

[MrGoUp]

Dear Sirs,

I have some problems in decoding the nk6110.txt documentation from the gnokii site.

I would like to send a command via fbus to make a voice call.
I am sending to the phone the following sequence:

1E 00 0C 01 00 [Frame length] 00 01 [..phone number..] 05 01 01 05 00 03 00 00 01 01 43 [padding byte?] [ChkSum1] [ChkSum2]

Is this correct?
I am sending the phone number in this format:
for example let's say that the number is international and the number is +386 123 456 then
[..phone number..] = 91 83 16 32 54 F6

Any help and any reply will be much appreciated.

kind regards,

G.

[townsendrs]

Hi,
Here is the code for MBUS - you should be able to change protocaol to FBUS.
I noticed that for MBUS it is necessary to connected the charger for good MBUS operation and maybe this is true for FBUS too.
MBus Make Voice Call Frame
Byte Data Description

0 0x1F MBus Frame Ident
1 0x00 Destination device address - 00 is mobile phone
2 0x1D Originating device - in this case 0x1D means MBus device (eg a PC)
3 0x40 Message Type - 40 means 'Security Commands' ??

4 0x00 Bytes 4 & 5 are the number of bytes from byte 6 to message end excluding
5 0x09 Sequence No & the Checksum Bytes ie excluding the last two bytes

6 0x00
7 0x01

8 0x7C Calls Command

9 0x01 Command to make voice call

10 0x32
11 0x33 Phone number to be called in ASCII format - the number in this
12 0x34 example is '2345'
13 0x35

14 0x00 Finish byte

15 0x03 Message sequence no. - increment for each new message.
16 0x34 XOR all preceding bytes (in the example Byte 0 to Byte 15)

Response from Phone is 1F 1D 00 7F 03 7E which is the standard acknowledge frame
followed by 1F 1D 00 40 00 04 01 01 7C 01 02 39 where the byte following 7C is what
the phone has done - in this 0x01 means 'am making voice call'

Dic