Having problems connecting to Pexipdemo?
This is most likely due to an enterprise firewall that might be a bit restrictive as most IT-departments wants to control what traffic is flowing in their network.
In most cases this is due to port 40.000-49.999/UDP being blocked outbound from your network to the Pexipdemo network.
If you have a very strictly firewalled Skype/Lync environment, see this article to understand what must be allowed to connect out to Pexipdemo.
If you struggle to get video in your browser, you may also be firewalled, see this article to understand more.
A more comperhensive list of ports used, also for individual types of endpoints/protocols can be found further down this page.
The Pexipdemo network currently consists of Pexip nodes in US, Europe, Singapore, China and Australia.
Depending on what parts of the world you are coming from, and what URIs and hostnames you are connecting to you might be connected to different data centers, normally you will automatically be connected to the data center closest to the location of your endpoint/client or call control server.
18.104.22.168 /26 (Europe)
22.214.171.124 /26 (US)
You may not have to open to all locations, depending on what datacenter your DNS lookup of pexipdemo.com resolves to. There are multiple nodes for each data center, so if you have to put a specific FW rule in place, ensure to allow the full /28 network, not just one IP-address.
The ports you are connecting to will differ if you use SIP, H323, Lync or WebRTC.
Below is a consolidated overview, and broken out pr connection method.
Source ports would be defined by the calling client, so Pexip determines destination ports on the Pexip side.
Ports opened towards Pexipdemo (consolidated)
80/TCP - HTTP redirect and SfB Avatar
443/TCP - HTTPS WebRTC signaling
5060/TCP - SIP
5061/TCP - SIP Secure (TLS)
1719/UDP - H323 RAS signalling
1720/TCP - H323 H225 signalling
30000-39999/TCP- H323 Q931/H245 signalling
40000-49999/UDP – Media (RTP/RTCP)
40000-49999/TCP– Media (RDP sharing)
For more details:
Read more here if you have a Lync client behind a strict firewall - and cannot get media trough
Read more here if you have a WebRTC client behind a strict firewall - and cannot get media trough