08-30-2013 02:16 PM
09-03-2013 07:38 AM
I am a BIS push 'virgin', I have only ever done BES push and then only from the BB end. But I will try to describe what I know. Our BES end developer is on holiday atm, so I can't get clarification. So forgive me if some of the following is not clear and/or 100% accurate.
When we do BES push, we actually just do a POST to the BES MDS Server. Our code runs in the corporate network, and we push to a specific PORT on the BES Server. I believe this PORT is actually managed by MDS, so if we stopped MDS, this service will disappear. So perhaps it should be called BES MDS push But I have always called it BES push, to distinguish from BIS Push.
This is different to BIS push, where you push to a Server managed by BBRY. I presume using BIS Push, the POST is directed to an MDS like Service that is running on the BBRY supplied Server.
Now when you push, as I understand it, for both BIS and BES Push, you have two types of push that you can do:
1) PAP push, which is the standard, and
2) RIM push, which is specific to RIM.
These two have a different format payload as I understand it. Also PAP has some extra bells and whistles, for example, delivery confirmation. However for our specific application, we use RIM Push. We fire and forget.
I hope this is helpful.
You say you are getting 2002 - bad address.
According to this:
2002 indicates a PIN error with a PAP push. Now as noted, I am a BIS Push virgin. Do BBs have to subscribe to your push service before you can push to them? This would seem reasonable to stop people just willy-nuilly pushing to any BB PIN they find I don't have this problem with BES push - the PINs are known to BES.
09-03-2013 09:11 AM