02-14-2013 07:57 AM
Perform an nslookup on the URL you are pushing to, that will give you the IP needed. If it is still failing after opening this IP and port then you will need to do more investigation with your network teams to determine the point of failure.
03-14-2013 01:34 AM - edited 03-14-2013 01:41 AM
We have opened port 443 and the ip 188.8.131.52 also. But still not able to send the notifications.
Our network team wants to know the following :
Service provider used for sending notifications?
Service port used?
Need to know whether Blackberry has white listed our Public ip?
Does blackberry whitelist's an ip. We need to resolve this issue as we have moved to production, but are not able to send notifications. Please suggest how can we solve this issue.
03-14-2013 09:00 AM
No, there should not be any whitelisting required on our end.
Are you able to add a firewall rule based on domain name (i.e. cp476.pushapi.na.blackberry.com)? Its underlying IP address might change.
03-14-2013 10:31 AM - edited 03-14-2013 10:36 AM
Thanks for your reply.
We can add a rule based on the ip and not on the domain name.We are getting an
Caused by java.net.connectexception : Connection timed out:connect
and in some cases:
net.rim.pushsdk.commons.PushSDKException: SocketTimeoutException caught sending message to PPG URL address: https://cp476.pushapi.na.blackberry.com/mss/PD_pus
Caused by: java.net.SocketTimeoutException: connect timed out
We have two notification servers for two different apps. We are getting the timeout response after 21 secs and in some cases after a min. What could be the issue. Can't we manually set the timeout , while sending the push notifications.
03-14-2013 11:37 AM
Tried. It Didn't worked. The network team has allowed outgoing traffic for all the ips. They get a request on the firewall for the said ip and it passes successfully through it. But still we are getting the connection timed out exception.
03-14-2013 01:52 PM
Unfortunately, I'm not sure if I can be of more assistance.
There seems to be something on your end blocking the request from going through.
If it makes it through the firewall, then what else could it be?
We have tried on our end and we can communciate with the PPG using your PPG URL without the SocketTimeoutConnection, so the URL is fine. It must be something unique to your environment.
03-15-2013 03:14 AM
Thanks for your reply. Can you please tell me how frequently the ips change.
Today when I was doing the ip lookup for the domain names, we got the same ip for both the domains cp476 and cp451.
03-15-2013 08:51 AM
As far as I know (but I'm not involved in the actual configuration process of these servers so it's just a guess on my part), the IPs are pretty static. Just one for the main PPG servers and then for its backup if the main one goes down.
I believe all cpxxx URLs are ultimately mapped to the same IP.
If you put in a firewall rule to allow 184.108.40.206 and you're still getting the timeout, then it must be something else blocking it would be my guess.
03-16-2013 10:00 AM - edited 03-16-2013 10:03 AM
Thanks for your reply.
It might be some network related issue at our end. The firewall team says that the packets are getting dropped as they are not in sync. Will check it at our end.