Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS.
BR, Nikos ----- Original Message ----- From: Henri Hovi To: Nikos Balkanas Cc: [email protected] Sent: Wednesday, December 16, 2009 11:15 AM Subject: Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas <[email protected]> Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos ----- Original Message ----- From: Henri Hovi To: Rajeev Agarwal Cc: Nikos Balkanas ; [email protected] Sent: Wednesday, December 16, 2009 8:52 AM Subject: Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal <[email protected]> wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=tester&password=foobar&to=xxxxxxxxxx&udh=%06%05%04%40%AB%23%F0&text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas <[email protected]> Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos ----- Original Message ----- From: Henri Hovi To: Rajeev Agarwal Cc: [email protected] Sent: Tuesday, December 15, 2009 2:36 PM Subject: Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal <[email protected]> wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
