We have a user who wants to use the Viber voice-over-IP Skype-like client on his iPad to make calls. It doesn't seem to work inisde our network - either our Lightspeed server or our SonicWall firewall are blocking communications in some way. Has anyone got Viber to work on their network - does anyone know what network settings it needs? Their FAQ seems to imply that we need to allow incoming connections on some particular ports:
That doesn't help much, though - would I need to get our SonicWall to forward those particular ports to the one particular iPad for things to work (so there would only be the one device on th network able to use Viber)? Skype works okay on our network, and I understand that functions through firewalls by initiating an outgoing connection and then having the firewall allowing a replying incoming connection.
Do I actually need to simply tell our Lightspeed device to not touch traffic going to Viber's servers, how I've recently done with Dragon Dictation traffic?:
If so, does anyone have any idea what IP addresses I need to allow? Viber's servers would seem to be based somewhere within Amazon's cloud, so I imagine they have a whole bunch of servers with dynamically-changing addresses, which might cause issues trying to set up a firewall rule for.
If you have the IP of the device add this IP to the inspectors area. Then go into the web activity report and choose show inspector data only and you should see anything that of the policies or DPI checks are blocking. You can also use the internal and external IP plus protocol report to see where the App is trying to talk to.
The support chaps are always there to help if needed also.
I wonder if its classed as P2P and you have P2P traffic blocked
Easy enough to know, as @Eappariello said, you can do the inspectors or just look in the web activity report to begin with and search for the IP of the device, i find that usually has more than enough data in it to get stuff working, or at least give you a very good idea where the problem is.
Then it would just be a case of putting the appropriate external IP in your external IP ignore list