Problem with sending OMA SyncML settings via SMS

Problem with sending OMA SyncML settings via SMS SearchSearch
Author Message
Antonio Ong
New member
Username: Tonio_d_monio

Post Number: 1
Registered: 10-2006
Posted on Tuesday, October 17, 2006 - 03:41 pm:   

Hi,

Fairly new to the message board. I'm in the process of creating a site to send OMA settings for Nokia 3250 however I've been receiving "App. Closed: WatcherMainThread".

I've gone thru most of the advice in this board but still the OMA setting is not received properly. I'm hoping that maybe someone can point out whats wrong -- i guess it must be something silly but for the life of me i can't seem to find it. Details below:

XML:
<?xml version="1.0"?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd">
<wap-provisioningdoc>
<characteristic type=\"APPLICATION\">\n";
<parm name="APPID" value="w5"/>
<parm name="NAME" value="SVC"/>
<characteristic type="APPADDR">
<parm name="ADDR" value="http://server.mysyncML"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8099"/>
</characteristic>
</characteristic>
<characteristic type="RESOURCE">
<parm name="URI" value="./contact"/>
<parm name="NAME" value="ContactDB"/>
<parm name="AACCEPT" value="text/x-vcard,text/vcard"/>
</characteristic>
<characteristic type="APPAUTH">
<parm name="AAUTHNAME" value="ant"/>
<parm name="AAUTHSECRET" value="1234"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

========================
SMS # 1 of 2 (140 bytes)
========================
WDP
0B -> UDH length (not including this field)
05 -> information element identifier (05 = application port addressing scheme, 16-bit address)
04 -> information element length
0B 84 -> destination port
23 F0 -> source port
00 03
17 -> Transaction ID
02 -> Total Msg Segments
01 -> Current Msg Segment

WSP
WSP Header
17 -> Transaction ID
06 -> PDU Type (Push)
2F -> Header length (47)
1F 2D -> Length-Quote-Length
B6 -> Content Type='application/vnd.wap.connectivity-wbxml'
91 81
92 -> Start of MAC value (40 bytes, "1234")
41 31 31 31 37 43 31 43 36 33 36 38
31 34 32 32 35 45 45 32 41 38 44 35
45 38 37 42 37 39 32 32 33 46 44 43
33 34 34 45
00 -> End of MAC

WBXML
03 0B 6A 00 45 C6 00 01 55 01 87 36 __ 00 00 06 03 77 35 00 01 87 07 06 03
53 56 43 00 01 C6 00 01 56 01 87 34 __ 00 00 06 03 68 74 74 70 3A 2F 2F 73
65 72 76 65 72 2E 6D 79 73 79 6E 63 __ 4D 4C 00 01 C6 53 01 87 23 06 03 38
30 39 39 00 01 01

========================
SMS # 2 of 2 (118 bytes)
========================
WDP
0B -> UDH length (not including this field)
05 -> information element identifier (05 = application port addressing scheme, 16-bit address)
04 -> information element length
0B 84 -> destination port
23 F0 -> source port
00 03
17 -> Transaction ID
02 -> Total Msg Segments
02 -> Current Msg Segment

WSP
01 C6 00 01 59 01 87 3A 00 00 06 03 __ 2E 2F 63 6F 6E 74 61 63 74 00 01 87
07 06 03 43 6F 6E 74 61 63 74 44 42 __ 00 01 87 00 01 2E 00 00 06 03 74 65
78 74 2F 78 2D 76 63 61 72 64 00 00 __ 01 80 03 74 65 78 74 2F 76 63 61 72
64 00 01 01 C6 57 01 87 31 00 00 06 __ 03 61 6E 74 00 01 87 00 01 32 00 00
06 03 31 32 33 00 01 01 01 01

Appreciate any help on this.
Antonio Ong
New member
Username: Tonio_d_monio

Post Number: 2
Registered: 10-2006
Posted on Thursday, October 19, 2006 - 08:26 am:   

bump?
adam michalak
New member
Username: Gsarider

Post Number: 1
Registered: 02-2008
Posted on Thursday, February 14, 2008 - 09:22 pm:   

so, is there a solution to our problem yet?
please let me know either way
thx