Hi Paul,

Finally got dome time to test the OMA code from the MBUNI project.
Works fine for OTA phones and for Nokia OMA phones.

I tried it with Motorola ones without luck
the messages arrived and the phone but when i try to enter the pin it give
incorrect pin number but i enter the right one.

I did try to debug the output with some help from some docs i did get
online.
and i got the following by comparing the output from NowSMS ( works with
nokia and motorola when sending XML)
and kannel. Here is the output:

Kannel:

// TP-UDH:
0b  UDH Length
05  Port Addressing IE Type 16-bit port addressing
04  Port Addressing IE Length
0b 84  Destination Port (2948 - push connectionless port )
0b 84  Source Port (2948 ???)
00  IE type
03  IE Length
31   Datagram Reference Number
03  Total Number Of segments
01   Current Segement Number

01  TID
06   UNIT PUSH
2f          Length for content-type and HEADERS
1f 2d   Content type value length given as "Length-quote Length"

// MEDIA-TYPE PARAMETER
b6  application/vnd.wap.connectivity-wbxml
91 81   SEC = 1
92   MAC
61 37 39 64 30 37 65                                                a79d07e
31 61 36 63 30 65 63 37 36 66 39 37 32 38 63 30   1a6c0ec76f9728c0
63 61 39 31 64 33 64 36 65 33 34 34 64 65 30 34   ca91d3d6e344de04
62
b

00   End of string for the encoded MAC value

// WBXML:
......

----------------------------------------------------------------------------
-

NowSMS
// TP-UDH:
0b  UDH Length
05  Port Addressing IE Type 16-bit port addressing
04   Port Addressing IE Length
0b 84   Destination Port (2948 - push connectionless port )
23 f0   Source Port (9200 ???)
00   IE type
03   IE Length
5f    Datagram Reference Number:
03   Total Number Of segments
01   Current Segement Number

5f  TID
06  Unit Push
2f          Length for content-type and HEADERS
1f 2d   Content type value length given as "Length-quote Length"


// MEDIA-TYPE PARAMETER
b6   application/vnd.wap.connectivity-wbxml
91 81   SEC = 1
92   MAC

39 42 31 42 33                                                         9B1B3
34 38 36 46 42 46 36 42 39 41 46 37 42 38 30 31  486FBF6B9AF7B801
45 41 34 31 44 41 45 42 38 33 36 30 32 37 43 36  EA41DAEB836027C6
30 34 42
04B

00  End of string for the encoded MAC value

// WBXML:
......

In both cases the userpin is 1234.

I'm not very familiar with SHA encoding besides that the only difference i
see is the
source port on kannel port 2948 is being used and on Nowsms port 9200. But
according to the
docs shouldn't matter. May be an error in the SHA??

Cheers,
Edward

----- Original Message ----- 
From: "Paul Bagyenda" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, July 21, 2004 4:47 AM
Subject: Re: Kannel OMA-OTA


> Hi Edward,
>
>   I have the CVS snapshot of the time if you want that. It shouldn't be
> a big problem getting those changes into the current one though...
>
> P.
>
> ----------  You wrote  ----------
>
> Subject: Kannel OMA-OTA
> Date: Tuesday 20 July 2004 04:26 am
> From: "Edward C.A. Tromp" <[EMAIL PROTECTED]>
> To: [email protected]
>
> Guys,
>
> I'm planning to use OMA-OTA as a provision mechanism for phones that
> support
>   this feature. I've search on the mailing list and saw that Paul
> Bagyenda did
>   do some work regarding this. I was trying to add his patch to the
> current
>   CVS but with no succes i think i need the cvs from the day that diff
> was
>   submitted.
>
> My question are:
> 1. Is there a way to get an older CVS that's from that specific day.
> (Maybe
>   Paul can assist) 2. Are their plans to incorporate this in the standard
>   kannel release.
>
> Cheers,
> Edward
>
> -----------------------------
> P. A. Bagyenda
> Digital Solutions
> P.O.Box 23833
> 58 Bukoto Str.
> Kampala, UGANDA
>
> Tel: +256-41-540143
> Mob: +256-77-507743
> Web: http://www.dsmagic.com
> -----------------------------
>
>
> This email and any files transmitted with it are confidential, and may
> also
> be legally privileged. If you are not the intended recipient, you may
> not
> review, use, copy, or distribute this message. If you receive this
> email in
> error, please notify the sender immediately by reply email and then
> delete
> this email.
>
>


Reply via email to