Press "Enter" to skip to content

Polycom VVX and Trio Network Ports for Skype for Business Online

0

Howdy Folks,

I’m working with a customer who requires being able to lock down the network to and from the Trio and VVX devices.  I’ve been trying to work with Polycom to get a definitive list of URLs, as well as IP, addresses but it seems quite hard going to obtain them.  I’ve got a pretty impressive Cisco Meraki home network so I started the network monitoring and this is what I’ve found out.

 

Networking Reports

For the VVX

 

For the Trio:

 

What makes up the group Windows Office365 according to Meraki.

 

What can we understand about the above, the VVX hadn’t been online in a while so we know that the downloads.polycom.com was me updating the devices. Anything running from 192.168.0.* is from my internal network while I was doing device configuration.

 

We saw late last year that Microsoft are simplifying the required IP addresses and ports: https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Simplified-port-requirements-for-Skype-for-Business-Online/ba-p/77094  

 

We also know that the required URLs for the client are outlined on: https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US&fromAR=1#bkmk_lyo

 

The current list of IP addresses utilised by Skype for Business Online for IPv4 is:

13.67.180.128/32
13.70.151.216/32
13.71.127.197/32
13.75.126.169/32
13.72.245.115/32
13.73.1.120/32
13.76.241.210/32
13.78.94.7/32
13.79.153.60/32
13.89.240.113/32
13.91.252.242/32
13.95.234.10/32
13.107.3.0/24
13.107.8.0/24
13.107.64.0/18
23.97.78.16/32
23.99.101.118/32
23.99.112.73/32
23.99.113.163/32
23.99.121.38/32
23.101.61.176/32
23.101.112.170/32
23.101.151.89/32
23.103.176.128/26
23.103.176.192/27
23.103.178.128/26
23.103.178.192/27
40.69.45.108/32
40.74.62.125/32
40.78.146.128/32
40.83.17.24/32
40.83.124.144/32
40.84.28.125/32
40.115.1.44/32
40.117.145.132/32
40.122.44.96/32
40.123.43.195/32
40.127.129.109/32
40.127.169.165/32
51.140.62.120/32
51.140.79.167/32
51.140.126.38/32
51.140.143.149/32
51.140.155.234/32
51.141.28.50/32
51.141.42.151/32
51.141.49.0/32
51.141.51.76/32
52.112.0.0/14
52.163.60.30/32
52.163.126.215/32
52.163.225.1/32
52.165.150.215/32
52.165.238.202/32
52.166.61.83/32
52.170.21.67/32
52.172.185.18/32
52.175.37.105/32
52.177.200.188/32
52.178.94.2/32
52.178.161.139/32
52.178.198.107/32
52.187.79.90/32
52.228.25.96/32
52.231.36.175/32
52.231.207.185/32
52.238.119.141/32
52.242.23.189/32
52.244.160.207/32
104.41.208.54/32
104.44.195.0/24
104.44.200.0/23
104.45.18.178/32
104.46.62.41/32
104.47.151.128/32
104.208.28.54/32
104.209.188.207/32
104.210.9.95/32
104.215.11.144/32
104.215.62.195/32
137.116.66.252/32
137.116.248.105/32
137.117.128.25/32
138.91.237.237/32
168.61.145.101/32
168.63.245.120/32

All of my media traffic appears to be going to 52.122.0.0/14 subnet.  It didn’t seem to make a difference whether I went through a PSTN conference or through a standard Microsoft Phone System, clearly, this was my media traffic was being routed to.

 

The one thing, however, I want to call out that I can’t find anywhere in Polycom documentation is why there was communication to/from the VVX on Port 12345.   I set up a second NIC on my Surface Pro and hooked the VVX daisy-chained and the port was only being used for BToE.

 

Next steps are as well to see if the VVX or the Trio are speaking to anything other than the Office 365 and Skype for Business approved URLs.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.