02-26-2013 09:11 AM
we are developer of SKEBBY (http://freesms.skebby.com/) a famous blackberry application for free SMS. Starting from 6 February we are encountering problem with your RIM PUSH SERVICES, we wrote a couple of email to support and finally to BlackBerryPushServices@rim.com where they suggested me to post a message here, there is anyone who can help us sorting it out. Our application is not working as we wished and some user are complaining about us and Blackberry.
03-22-2013 04:43 AM - last edited on 04-05-2013 09:41 AM by mdandrea
sorry for the delay of our answer, my techician told me that:
when we try to do the POST to
to the port 20558
with application ID <removed>
we receive a 403 error
some months ago all was fine and then suddenly it stop to work
Do you made same change or can we do something to reactivate it.
we thank you in advance and stay at your disposal.
03-22-2013 07:56 AM
No changes were made.
The port number is only required by your device side application on BlackBerry OS <=7. BlackBerry 10 device side applications no longer require the port. And port was never required when initiating a push from your server side application.
So ensure you are not POSTing your request to the port from your server side application. Also ensure you are setting the Basic Auth header when you initiate the push in the form of <Application-Id>:<password> and base64 encoded
03-22-2013 09:17 AM
No change were made also on our side, so we do not understand why it suddently stopped, it could be possibile that we missed some sort of payment or activation cost to blackberry ? If it was so how much would it cost to have BIS (blackberry internet services) reactivated ? There would be any alternative to let us interact with the mobile phone of our client ?
03-22-2013 09:53 AM - last edited on 04-05-2013 09:41 AM by mdandrea
If your application had expired or was inactive you would receive a 401 error (not a 403) error. I tried pushing to your URL using my own app id: https://cpxxx.pushapi.na.blackberry.com/mss/PD_pus
Are you sure nothing changed on your end, for example, firewall or other networking changes that may be blocking this outgoing request now?
04-05-2013 09:42 AM
Please try to avoid posting your application ID to to forums as well as your content provider ID.
What is the exact error description that you get back with the 403 error?
Also, you mentioned port 20558. What is this exactly? When you send a push out, you do not specify a port.