OMA DM Notification Message

OMA DM Notification Message SearchSearch

SMS & MMS Technical Forum » WAP Technical Discussions (unsupported) » OMA DM Notification Message « Previous || Next »
Author Message
ali
New member
Username: Razaq

Post Number: 1
Registered: 01-2010
Posted on Thursday, January 21, 2010 - 09:57 am:   

Hi Folks,

Something very strange;-) I am unable to browse the dusicssion pages from my firefox (v-3.5.7).


Anyway, I am trying to send a notification message to DM Client (Nokia-E51 handset). I expect DM profile to automaticaly start configuration/connection upon receiving the notification message, or atleast there be a sign that msg was receiced;-)

Here is what I am doing:

0) Nowsms->WebInterface->Send WAP Push Message
1) Push Type->Advance
2) Content-Type->x-wap-application:syncml.dm (actually i have tried with x-wap-application:push.syncml and application/vnd.syncml.notification. But i do think syncml.dm is the right type)
3) Content Encoding->Hex String(convert to binary)
4) I did try to explicitly input the 'X-WAp-Application ID' which is 'AF' in this case.

Below is the example that i have got from funambol (Funambol DM Server
Developer's Guide Version 3.0 September 2006) doc for testing purpose.

///////////////////////////////
Example 3 page 82:
06 05 04 0B 84 C0 02 01 06 03 C4 AF 87 A0 96 3B 47 B8 D0 B3 D7 4C 45 9F B5 44
35 98 B1 02 C0 00 00 00 00 09 06 73 79 6E 63 34 6A


WDP Header:
06: User-Data-Header(UDHL) Length = 6 bytes
05: UDH IE Identifier Port Number
04: UDH port number IE length
0B: Destination port (high)
84: Destination port (low)
C0: Origination port (high)
02: Origination port (low)

WSP Header:
01: Transaction ID / Push ID
06: PDU Type(push)
03: Headers length (content type + headers)
C4: Content type
AF: X-WAP-Application-ID
87: Id for urn: x-wap-application:syncml.dm
Digest:
A0 96 3B 47 B8 D0 B3 D7 4C 45 9F B5 44 35 98 B1
Notification Message:
02 C0 00 00 00 00 09 06 73 79 6E 63 34 6A
///////////////////////////////////


Any thoughts what is missing?

cheers,
ali
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1686
Registered: 08-2008
Posted on Thursday, January 21, 2010 - 03:12 pm:   

Hi Ali,

Thank you for letting us know about the Firefox problem. Our web server is hosted on a cluster server, and our provider made some changes last week to move us to a different cluster front end. However, it obviously has some problems. I've switched DNS back to the old cluster front end, and it seems to resolve the problem. However, it will take some time for this change to propagate through DNS caches.

I will take a look at the your technical issue later today.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1691
Registered: 08-2008
Posted on Thursday, January 21, 2010 - 04:17 pm:   

Hi Ali,

For #2, you want to be using application/vnd.syncml.notification as the MIME content type.

For #4, use 0xAF as the X-WAP-Application-ID ... otherwise NowSMS is going to interpret this as a text string "AF".

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1692
Registered: 08-2008
Posted on Thursday, January 21, 2010 - 04:18 pm:   

Oops ... correction on #4 ... I just looked at your hex example. AF is not the X-WAP-Application-ID value, 87 is. Assuming that the hex example is correct, you want to use 0x87 as the X-WAP-Application-ID value. (87 without the 0x prefix would be interpreted as decimal.)


--
Des
NowSMS Support
ali
New member
Username: Razaq

Post Number: 2
Registered: 01-2010
Posted on Friday, January 22, 2010 - 07:39 am:   

Hi Des,

Thanks for followup. Glad to know you people care for firefox;-)

Well, no luck so far. I took that hex data from document that i have mentioned in original post, just to make sure I am not screwing anything. My own hex encoder should be ready soon.

Here is the snip form DM Notification spec "OMA-TS-DM_Notification-V1_2-20070209-A":


a) The Content-Type code 0x44 MUST be used instead of the textual representation of the MIME code.

b) The X-WAP-Application-ID header [PUSHMSG] MUST include the application-id associated with the Sync ML
Device Management User Agent. The application-id code 0x07 MUST be used instead of the textual representation
of the Application-id.

c) The push message is sent to the default non-secure connectionless push port (2948)


For (a) you were right as here [ http://www.wapforum.org/wina/wsp-content-type.htm ] 0x44 is equals to application/vnd.syncml.notification. I did try to use 0x07 for 'X-WAp-Application ID' but again didn't work!


How bout the port? what port nowsms will target in Advance type WAP Push Message ? Thats the only thing i can suspect.

regards,
ali
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1702
Registered: 08-2008
Posted on Friday, January 22, 2010 - 09:41 pm:   

Hi Ali,

You are correct that the X-WAP-Application-ID value needs to be 7 (or 0x07), not 0x87. A value of 7 gets encoded as 0x87 in the resulting WDP message ... so I was confused.

I just tried sending out a message myself, and when you use Content Type = "application/vnd.syncml.notification" and X-WAP-Application-ID value of 7 ... the header generated by NowSMS is virtually identical to the binary example you have above.

The only differences are the transaction ID, which is obviously going to be different ... and the source port. NowSMS always uses a source port of 9200 decimal when sending a push (the standard connection less WDP port number), whereas your binary example is using 0xC002. I can't see where this would be of any significance, as the source port setting is somewhat arbitrary ... what is important is the destination port.

Are you sure that your content is valid? I'm not familiar with how the "Digest" value is calculated in a SyncML notification.

--
Des
NowSMS Support
Tom Herman
New member
Username: Hmazsa

Post Number: 1
Registered: 10-2010
Posted on Tuesday, October 26, 2010 - 10:12 am:   

Hi ali,

I would like to send a notification message according to your post using funambol dm server. But when I send a message, it is not received by the phone. Fortunately I can debug an android phone, so I can see that the message rceived, but the phone (HTC G1) can not process it. :-( After it I tried it on some other phones without success. Would you tell me how could you solve the problem?

Thanks, Tom
ali
New member
Username: Razaq

Post Number: 3
Registered: 01-2010
Posted on Wednesday, October 27, 2010 - 09:22 am:   

Hi Tom,

Its been a while I did that stuff so bear with my poor memories!

Very first, In case of success you should be able to trigger the SyncML profile activation, assuming you are doing the same as i mentioned in original post.

Secondly, even you do phone debug that wont help. You need to look at funambol logs to figure-out the problem.

I would conclude that AFAIK on phone there is no way you can check the formatted data. I would strongly suggest to use the funambol example to start-by.

cheers,
ali
Tom Herman
New member
Username: Hmazsa

Post Number: 2
Registered: 10-2010
Posted on Wednesday, October 27, 2010 - 09:57 am:   

Hi ali,

Thanks. Unfortunately I tried to use funambol example. As I can see the funambol generated byte array is valid (according to the specification http://repo.or.cz/w/syncmlbtproxy.git/blob_plain/bacc13e71bcc7e083dd5b6af1f7c6a2 0f9befaa2:/doc/specs/OMA-TS-DM-Notification-V1_2-20060424-C.pdf) The problem is that, the message is sent, and may be recevied by the phone, but nothing happens. In the funambol logs I can see that the notification message was sent, but the phone did not tried to connect to the server. So I think something is wrong with the generated notification message. :-(
But to tell the truth, I do not know what the phone should do when it receive a valid notifiction message. I think it should try to connect to the funambol dm server.. In your original post I can see your byte array which is also a valid message, but something was wrong with it. Do you remember what should be done to work properly?

Thanks, Tom
ali
New member
Username: Razaq

Post Number: 4
Registered: 01-2010
Posted on Wednesday, October 27, 2010 - 10:17 am:   

Just spoke to a friend of mine and here is what he has to say:

START_SNIP:

"argh, the binary SMS problem!!!

its strange, he can see that the sms arrives but not gets processed? I guess for an android phone ( which doesnt have a syncml or a dm client built in), the format of the SMS must be dependent upon which 3rd party client they install, no?"

END_SNIP:


>But to tell the truth, I do not know what the phone should do when it receive a valid notifiction message.

Well, if every thing goes fine then you should be able to notice a sort of activity on the phone, say connecting, a pop-up message etc (I have never used android device) . Think about this notification more like an operator configuration message.


Have a look at my friends feedback and see if you gets you somewhere.


good luck,
ali
Tom Herman
New member
Username: Hmazsa

Post Number: 3
Registered: 10-2010
Posted on Wednesday, October 27, 2010 - 10:52 am:   

Thanks again. Your friend may be right, therefore I tried it in some Nokia phones too, but the result was the same.:-( and AFAIK Nokia smartphones have Syncm dm handling.
So the binary SMS may be wrong, but which part of it? I looked over questions and answers of the post , but I did not recognise the solution.

best regards, Tom
ali
New member
Username: Razaq

Post Number: 5
Registered: 01-2010
Posted on Wednesday, October 27, 2010 - 11:03 am:   

///////////////////////////////
Example 3 page 82:
06 05 04 0B 84 C0 02 01 06 03 C4 AF 87 A0 96 3B 47 B8 D0 B3 D7 4C 45 9F B5 44
35 98 B1 02 C0 00 00 00 00 09 06 73 79 6E 63 34 6A


WDP Header:
06: User-Data-Header(UDHL) Length = 6 bytes
05: UDH IE Identifier Port Number
04: UDH port number IE length
0B: Destination port (high)
84: Destination port (low)
C0: Origination port (high)
02: Origination port (low)

WSP Header:
01: Transaction ID / Push ID
06: PDU Type(push)
03: Headers length (content type + headers)
C4: Content type
AF: X-WAP-Application-ID
87: Id for urn: x-wap-application:syncml.dm
Digest:
A0 96 3B 47 B8 D0 B3 D7 4C 45 9F B5 44 35 98 B1
Notification Message:
02 C0 00 00 00 00 09 06 73 79 6E 63 34 6A
///////////////////////////////////

Checkout the 'Notification Message' header with hex encoder and thats the the best thing comes to my mind. Other than that lets see what Des from SMS-Now have to say ;-)

cheers,
ali

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics