Re: sendota not using wbxml but plain xml

Julien Buratto <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Hi Nikos,

I'm sorry to post here, but as I've been using 1.4.1 without problems
and when upgrated to 1.4.3 the behaviour changed, I thought it was
more adeguate to post on the "devel" list to understand if there were
code differences which may affect the use of sendota. If in 1.4.3 a
new use has been introduced, this should have been documented but I
have not found anything on this.

I can confirm that your testing URL works also on my environment, so
I'd rather be more procise on how I use the sendota interface.

The XML doc I'm using is confirmed to work on 1.4.1, and its:

<?xml version="1.0"?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN"
"http://www.wapforum.org/DTD/prov.dtd">
<wap-provisioningdoc version="1.0">
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="SyncProfile"/>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w5"/>
<parm name="NAME" value="SyncProfile"/>
<parm name="TO-NAPID" value="INTERNET"/>
<parm name="ADDR" value="http://domain.com:80/sync" />
<parm name="PORT" value="80" />
<characteristic type="RESOURCE">
<parm name="URI" value="card"/>
<parm name="NAME" value="Contacts"/>
<parm name="AACCEPT" value="text/x-vcard,text/vcard"/>
</characteristic>
<characteristic type="APPAUTH">
<parm name="AAUTHNAME" value="ausername"/>
<parm name="AAUTHSECRET" value="apassword"/>
</characteristic></characteristic>
</wap-provisioningdoc>

Posting this XML to sendota on 1.4.3 provide this result:

URL USED

http://myhost:13013/cgi-bin/sendota?from=012345678&to=012345678&text=%3C!DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22+%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0D%0A%3Cwap-provisioningdoc+version%3D%221.0%22%3E%0D%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0D%0A%3Cparm+name%3D%22NAME%22+value%3D%22SyncProfile%22%2F%3E%0D%0A%3C%2Fcharacteristic%3E%0D%0A%3Ccharacteristic+type%3D%22APPLICATION%22%3E%0D%0A%3Cparm+name%3D%22APPID%22+value%3D%22w5%22%2F%3E%0D%0A%3Cparm+name%3D%22NAME%22+value%3D%22SyncProfile%22%2F%3E%0D%0A%3Cparm+name%3D%22TO-NAPID%22+value%3D%22INTERNET%22%2F%3E%0D%0A%3Cparm+name%3D%22ADDR%22+value%3D%22http%3A%2F%2Fdomain.com%3A80%2Fsync%22+%2F%3E%0D%0A%3Cparm+name%3D%22PORT%22+value%3D%2280%22+%2F%3E%0D%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0D%0A%3Cparm+name%3D%22URI%22+value%3D%22card%22%2F%3E%0D%0A%3Cparm+name%3D%22NAME%22+value%3D%22Contacts%22%2F%3E%0D%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcard%2Ctext%2Fvcard%22%2F%3E%0D%0A%3C%2Fcharacteristic%3E%0D%0A%3Ccharacteristic+type%3D%22APPAUTH%22%3E%0D%0A%3Cparm+name%3D%22AAUTHNAME%22+value%3D%22ausername%22%2F%3E%0D%0A%3Cparm+name%3D%22AAUTHSECRET%22+value%3D%22apassword%22%2F%3E%0D%0A%3C%2Fcharacteristic%3E%3C%2Fcharacteristic%3E%0D%0A%3C%2Fwap-provisioningdoc%3E&username=fake&password=fake&type=oma-settings&sec=userpin&pin=1234

SMSBOX LOG:

2009-06-08 11:49:04 [5987] [3] INFO: /cgi-bin/sendota: XML request for
target <00393356359515>
2009-06-08 11:49:04 [5987] [3] DEBUG: Octet string at 0x83a6d70:
2009-06-08 11:49:04 [5987] [3] DEBUG:   len:  385
2009-06-08 11:49:04 [5987] [3] DEBUG:   size: 1024
2009-06-08 11:49:04 [5987] [3] DEBUG:   immutable: 0
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 01 06 2f 1f 2d b6 91 81
92 36 35 43 45 43 30 38   ../.-....65CEC08
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 44 42 38 38 46 44 37 31
46 32 32 44 37 31 43 30   DB88FD71F22D71C0
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 33 31 38 45 44 34 42 45
41 36 34 31 45 34 32 35   318ED4BEA641E425
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 44 00 03 0b 6a 00 c5 45
03 31 2e 30 00 01 c6 50   D...j..E.1.0...P
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 03 42 4f 4f 54 53 54 52
41 50 00 01 87 05 03 4e   .BOOTSTRAP.....N
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 41 4d 45 00 06 03 53 79
6e 63 50 72 6f 66 69 6c   AME...SyncProfil
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 65 00 01 01 c6 50 03 41
50 50 4c 49 43 41 54 49   e....P.APPLICATI
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 4f 4e 00 01 87 05 03 41
50 50 49 44 00 06 03 77   ON.....APPID...w
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 35 00 01 87 05 03 4e 41
4d 45 00 06 03 53 79 6e   5.....NAME...Syn
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 63 50 72 6f 66 69 6c 65
00 01 87 05 03 54 4f 2d   cProfile.....TO-
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 4e 41 50 49 44 00 06 03
49 4e 54 45 52 4e 45 54   NAPID...INTERNET
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 00 01 87 05 03 41 44 44
52 00 06 03 68 74 74 70   .....ADDR...http
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 3a 2f 2f 64 6f 6d 61 69
6e 2e 63 6f 6d 3a 38 30   ://domain.com:80
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 2f 73 79 6e 63 00 01 87
05 03 50 4f 52 54 00 06   /sync.....PORT..
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 03 38 30 00 01 c6 50 03
52 45 53 4f 55 52 43 45   .80...P.RESOURCE
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 00 01 87 05 03 55 52 49
00 06 03 63 61 72 64 00   .....URI...card.
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 01 87 05 03 4e 41 4d 45
00 06 03 43 6f 6e 74 61   ....NAME...Conta
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 63 74 73 00 01 87 05 03
41 41 43 43 45 50 54 00   cts.....AACCEPT.
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 06 03 74 65 78 74 2f 78
2d 76 63 61 72 64 2c 74   ..text/x-vcard,t
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 65 78 74 2f 76 63 61 72
64 00 01 01 c6 50 03 41   ext/vcard....P.A
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 50 50 41 55 54 48 00 01
87 05 03 41 41 55 54 48   PPAUTH.....AAUTH
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 4e 41 4d 45 00 06 03 61
75 73 65 72 6e 61 6d 65   NAME...ausername
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 00 01 87 05 03 41 41 55
54 48 53 45 43 52 45 54   .....AAUTHSECRET
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 00 06 03 61 70 61 73 73
77 6f 72 64 00 01 01 01   ...apassword....
2009-06-08 11:49:04 [5987] [3] DEBUG:   data: 01
                         .
2009-06-08 11:49:04 [5987] [3] DEBUG: Octet string dump ends.
2009-06-08 11:49:04 [5987] [3] INFO: /cgi-bin/sendota <<default>>
<00393356359515>
2009-06-08 11:49:04 [5987] [3] DEBUG: message length 385, sending 4 messages

this seems definitively not to looks as a wbxml doc.

As per the post "sendota problems" on the "user list" it seems that
kannel does not support "wap-provisioningdoc" anymore, I'm wondering
when this support was removed from 1.4.1 to 1.4.3

Julien

2009/6/8 Nikos Balkanas <[email protected]>:
> Sure.
>
> These examples are straight out of the manual. Please pose these questions
> to users' list, they have no place here.
>
> Here you go:
>
> A) OTA settings from kannel.conf:
>
> http://127.0.0.1:13006/cgi-bin/sendota?otaid=wap&user=simple&pass=elpmis&from=013452678&to=012345678
>
> wbxml fakesmsc:
>
> 2009-06-08 02:40:06 [22483] [0] INFO: fakesmsc: Got message 1: <013452678
> 012345678 udh %06%05%04%C3O%C0%02
> %01%06%2C%1F*application%2Fx-wap-prov.browser-settings%00%81%EA%01%01j%00E%C6%06%01%87%12E%01%87%13%11%03127.0.0.1%00%01%87%14a%01%87!%11%032101234567%00%01%87%22p%01%87%23%11%03nbal%00%01%87%24%11%03black%00%01%87(r%01%87)k%01%01%86%07%11%03h>
>
> B) OTA URL settings:
>
> http://127.0.0.1:13006/cgi-bin/sendota?user=simple&pass=elpmis&from=013452678&to=012345678&text=<%3Fxml%20version="1.0"%3F><!DOCTYPE%20CHARACTERISTIC-LIST%20SYSTEM%20"file:gw%2Fsettings.dtd"><CHARACTERISTIC-LIST><CHARACTERISTIC%20TYPE="URL"%20VALUE="http%3A%2F%2Fwww.company.com%2F"%2F><%2FCHARACTERISTIC-LIST>
>
> wbxml fakesmsc:
>
> 2009-06-08 03:07:53 [22483] [0] INFO: fakesmsc: Got message 2: <013452678
> 012345678 udh %06%05%04%C3O%C0%02
> %01%06%2C%1F*application%2Fx-wap-prov.browser-settings%00%81%EA%01%01j%00E%86%07%11%03http%3A%2F%2Fwww.company.com%2F%00%01%01>
>
> Cleaner wbxml output can be seen from the smsbox logs.
>
> BR,
> Nikos
>
> ----- Original Message ----- From: "Julien Buratto"
> <[email protected]>
> To: "Nikos Balkanas" <[email protected]>
> Cc: "Alexander Malysh" <[email protected]>; <[email protected]>
> Sent: Sunday, June 07, 2009 12:31 AM
> Subject: Re: sendota not using wbxml but plain xml
>
>
>> Hi Nikos, could you post your testing URL ?
>> I would like to post same url to my installation and see what happens..
>>
>> Thanks
>> J
>>
>> 2009/6/5 Nikos Balkanas <[email protected]>:
>>>
>>> Hi,
>>>
>>> I tested it with fakesmsc. OTA pushed msg is sent as wbxml in 1.4.3. It
>>> is
>>> urlencoded in the fakesmsc client, but I assume this is the way for the
>>> fakesmsc client to display binary messages.
>>>
>>> BR,
>>> Nikos
>>> ----- Original Message ----- From: "Julien Buratto"
>>> <[email protected]>
>>> To: "Alexander Malysh" <[email protected]>
>>> Cc: <[email protected]>
>>> Sent: Friday, June 05, 2009 1:57 AM
>>> Subject: Re: sendota not using wbxml but plain xml
>>>
>>>
>>>> Hi Alexander,
>>>>
>>>> I could/would like to know myself if there is a bug here or not, I
>>>> can/want to provide feedbacks too but I don't know how to confirm
>>>> there is one..
>>>>
>>>> If you can provide me a process to verify this, I will be happy to
>>>> help.. otherwise, is anyone willing to test the sendota interface on
>>>> 1.4.3 and confirm if it works or not ?
>>>>
>>>> Julien
>>>>
>>>> 2009/6/1 Alexander Malysh <[email protected]>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> as far as I know, ota should be sent as wbxml. Could someone confirm
>>>>> that
>>>>> we
>>>>> have now have
>>>>> a bug there?
>>>>>
>>>>> Thanks,
>>>>> Alex
>>>>>
>>>>> Am 29.05.2009 um 08:40 schrieb Julien Buratto:
>>>>>
>>>>>> Hi, I noticed the logs that my sendota requests are sent in plain XML
>>>>>> with 1.4.3 version while with 1.4.1 the XML was converted to WBXML.
>>>>>>
>>>>>> I was wondering if someone knows any change of the code which could
>>>>>> cause this or could suggest some hints to test/verify
>>>>>>
>>>>>> Thanks
>>>>>> Julien
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Julien Buratto
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Julien Buratto
>
>



-- 
Julien Buratto
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.