[Anil]

Iam trying to do a browser message push( that I want to use send Alerts) to the device . When i use email address in the push URL, it works fine , meaning the message gets pushed and I can see the message in message folder on the device. But when i use device PIN in place of email address , it doesn't work and it throws error. Please see below.

The push URL
URL mdsUrl = new URL( "https", mdsHostName, mdsPort, "/push?DESTINATION=" + email/or devicepin + "&PORT=7874&REQUESTURI=/" );

From the mds console log saved.. The first one is when using email in the above URL and second case is when using devie Pin in the above URL. In both cases its to the same device. I tried this with device simulator also but ran into same issue. Please let me know what could go wrong and what can be done. Please note that this is browser message push ( not the channel push)

Case 1) when using email

Setting header property: Date = Thu, 18 Jun 2009 18:41:41 GMT
Setting header property: Server = IBM_HTTP_Server
Setting header property: Last-Modified = Thu, 18 Jun 2009 16:39:25 GMT
Setting header property: ETag = "6001-91-cf92940"
Setting header property: Accept-Ranges = bytes
Setting header property: Content-Length = 145
Setting header property: Keep-Alive = timeout=10, max=100
Setting header property: Connection = Keep-Alive
Setting header property: Content-Type = text/html
Connecting to Verizon:8443
Pushed page to the handheld.

case2) When using the device pin

Setting header property: Date = Thu, 18 Jun 2009 18:43:56 GMT
Setting header property: Server = IBM_HTTP_Server
Setting header property: Last-Modified = Thu, 18 Jun 2009 16:39:25 GMT
Setting header property: ETag = "6001-91-cf92940"
Setting header property: Accept-Ranges = bytes
Setting header property: Content-Length = 145
Setting header property: Keep-Alive = timeout=10, max=100
Setting header property: Connection = Keep-Alive
Setting header property: Content-Type = text/html
Connecting to Verizon:8443
Exception in thread "main" java.lang.RuntimeException: Cannot push data; received bad response code from Mobile Data Service: 403, could not map device 31f72685
to an IPPP host.