Hi
When I send an OTA configuration from kannel it is always ignored by
the phone (Sony Ericsson K500)
The same XML document works well with the NowSMS gateway.
The message is splitted in two SMS.
The only difference between the messages sent from kannel and the one
from NowSMS seems to be that the one from Kannel is missing a SAR UDH
in the header.
I found this comment in ota_prov.c:
/*
* Append the User Data Header (UDH) including the lenght (UDHL). Only
ports
* UDH here - SAR UDH is added when (or if) we split the message. This
is our
* *specific* WDP layer.
*/
which seems to suggest that a SAR UDH header will be added later, but it
isn't.
I also found this:
/*
* Within OTA spec this is "0B0504C34FC0020003040201", but it works
* with the following too?!
*/
octstr_append_from_hex(msg->sms.udhdata, "060504C34FC002");
I don't know what this seems to suggest but "0B0504C34FC0020003040201"
is the header sent by NowSMS except tenth byte (04) which varies.
I tried to change this but then I got two messages with segement count 1.
This is the document I've been trying to send:
<?xml version="1.0"?>
<!DOCTYPE CHARACTERISTIC-LIST SYSTEM "file:///etc/kannel/settings.dtd">
<CHARACTERISTIC-LIST>
<CHARACTERISTIC TYPE="ADDRESS">
<PARM NAME="BEARER" VALUE="GPRS"/>
<PARM NAME="PROXY" VALUE="123.45.6.7"/>
<PARM NAME="GPRS_ACCESSPOINTNAME" VALUE="sonofon.com"/>
<PARM NAME="PPP_AUTHTYPE" VALUE="PAP"/>
</CHARACTERISTIC>
<CHARACTERISTIC TYPE="URL" VALUE="http://wap.dk"/>
<CHARACTERISTIC TYPE="NAME">
<PARM NAME="NAME" VALUE="ABC"/>
</CHARACTERISTIC>
<CHARACTERISTIC TYPE="BOOKMARK">
<PARM NAME="NAME" VALUE="Wap"/>
<PARM NAME="URL" VALUE="http://wap.dk"/>
</CHARACTERISTIC>
</CHARACTERISTIC-LIST>
If I send it with NowSMS I get this at the other end (which work):
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 0b 05 04 c3 4f c0 02
00 03 e1 02 01 41 06 2c 1f ....O.......A.,.
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 2a 61 70 70 6c 69 63
61 74 69 6f 6e 2f 78 2d 77 *application/x-w
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 61 70 2d 70 72 6f 76
2e 62 72 6f 77 73 65 72 2d ap-prov.browser-
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 73 65 74 74 69 6e 67
73 00 81 6f 01 01 6a 00 45 settings..o..j.E
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 6f 06 01 87 12 49 01
87 13 11 03 31 32 33 2e 34 o....I.....123.4
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 35 2e 36 2e 37 00 01
87 1c 11 03 73 6f 6e 6f 66 5.6.7......sonof
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 6f 6e 2e 63 6f 6d 00
01 87 22 70 01 01 86 07 11 on.com..."p.....
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 03 68 74 74 70 3a 2f
2f 77 61 70 2e 64 6b 00 01 .http://wap.dk..
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 6f 08 01 87 15 11 03
41 42 43 00 01 o......ABC..
and the second message:
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 0b 05 04 c3 4f c0 02
00 03 e1 02 02 01 6f 7f 01 ....O........o..
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 87 15 11 03 57 61 70
00 01 87 17 11 03 68 74 74 ....Wap......htt
2005-07-28 13:56:36 [12042] [8] DEBUG: data: 70 3a 2f 2f 77 61 70
2e 64 6b 00 01 01 01 p://wap.dk....
with kannel on the other hand (doesn't work):
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 06 05 04 c3 4f c0 02
01 06 2c 1f 2a 61 70 70 6c ....O....,.*appl
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 69 63 61 74 69 6f 6e
2f 78 2d 77 61 70 2d 70 72 ication/x-wap-pr
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 6f 76 2e 62 72 6f 77
73 65 72 2d 73 65 74 74 69 ov.browser-setti
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 6e 67 73 00 81 6f 01
01 6a 00 45 6f 06 01 87 12 ngs..o..j.Eo....
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 49 01 87 13 11 03 31
32 33 2e 34 35 2e 36 2e 37 I.....123.45.6.7
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 00 01 87 1c 11 03 73
6f 6e 6f 66 6f 6e 2e 63 6f ......sonofon.co
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 6d 00 01 87 22 70 01
01 86 07 11 03 68 74 74 70 m..."p......http
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 3a 2f 2f 77 61 70 2e
64 6b 00 01 6f 08 01 87 15 ://wap.dk..o....
2005-07-28 13:18:59 [12042] [8] DEBUG: data: 11 03 41 42 43 00 01
01 6f 7f 01 87 ..ABC...o...
and the second message:
2005-07-28 13:19:00 [12042] [8] DEBUG: data: 06 05 04 c3 4f c0 02
15 11 03 57 61 70 00 01 87 ....O.....Wap...
2005-07-28 13:19:00 [12042] [8] DEBUG: data: 17 11 03 68 74 74 70
3a 2f 2f 77 61 70 2e 64 6b ...http://wap.dk
2005-07-28 13:19:00 [12042] [8] DEBUG: data: 00 01 01 01
Should this work or is segmentation and reassembly (SAR) not implemented
for OTA configuration messages.
Best regards
Robert Andersson
