[FAQ] What basic network data is send and received by a Poly Studio X or G7500

Polycom Employee & Community Manager

[FAQ] What basic network data is send and received by a Poly Studio X or G7500

Powering up/Booting or connecting a Poly Poly Studio X or G7500 to a network switch initiates certain network Protocols


NOTE: The below has been tested with a Studio X50 running Software 3.13 





Within this DHCP Discover message, the phone uses various Sub-Options


  • Option 12 Host Name
    The above can be used to identify the device in the Network


  • Option 55 is actually a List of Sub Options

    For Studio X or G7500 option 66 or 160 is used to discover the location of the provisioning Server being used. The section "Onboard Video Devices via the DHCP Auto Discovery" has more details on this.

  • 42 like 4 can be used to set the => time <= on the device

  • 15 can be used so the phone can identify the Domain it is using

  • 6 is to identify the DNS / Domain Name server(s)

  • like 42 can be used to set the => time <= on the device

  • 3 requests the default router or => gateway address <=

  • 1 request's the phones => subnet address <=

  • Option 60 Identifies the Vendor Class Identifier for Studio X or G7500


    More details on the Poly Phone DHCP Vendor Option can be found in the => Technical Bulletin 54041 <= and troubleshooting => here <=. The same is applicable to Poly Studio X or G7500



Once the device has an IP it will attempt to connect to Poly Lens and other locations:



The TC8, G7500 or Studio X are then joining the Multicast group



The TC8 then uses to advertise and pair with a compatible device



System Port Usage


Source =>here<=


The following table lists the inbound, outbound, and bidirectional ports used by your G7500 and Studio X series system.

Table 1. G7500 and Studio X Family System Port Usage
Port Direction Type Protocol Function Open by Default? Configurable Port?
22 Inbound Static SSH Command-line API access over SSH No No
23 Inbound Static TCP

Command-line API access over telnet

No No
24 Inbound Static TCP Command-line API access over telnet No No
53 Outbound Static UDP DNS Yes No
80 Inbound Static TCP

HTTP web server listener that provides access to the web interface. Redirects all sessions to HTTPS on port 443. Also used by AirPlay.

Yes Yes
123 Outbound Static UDP NTP (automatic time synchronization) Yes No
161 Inbound Static UDP SNMP reporting No Yes





Static TCP HTTPS web server listener that provides TLS access to the web interface.


Microsoft Exchange Server

Zero Touch Onboarding

Provisioning (for example, Poly Clariti Manager)

Video system control using a Poly TC8 device

Video system control using a Poly Trio system


Polycom Content App

Poly Lens

Polycom Support Site. (https://downloads.polycom.com/)

Yes No
514 Outbound Static UDP Remote logging No Yes
554 Inbound Static TCP, UDP AirPlay (Real-Time Streaming Protocol [RTSP]) No No
601 Outbound Static TCP Remote logging No Yes
1718 Outbound Static UDP H.255.0 gatekeeper discovery No No
1719 Bidirectional Static UDP H.255.0 RAS signaling No

Yes (outbound)

No (inbound)

1720 Bidirectional Static TCP H.255.0 call signaling Yes No
1900 Inbound Static UDP AirPlay/Bonjour (Simple Service Discovery Protocol [SSDP]) Yes No
2000 Inbound Static UDP Multicast pairing Yes No
3689 Inbound Static TCP iTunes Music Sharing/AirPlay (Digital Audio Access Protocol [DAAP]) Yes No
4100–4115 Bidirectional Static TCP AirPlay (audio control) Yes No
4100–4115 Inbound Static UDP AirPlay (audio data) Yes No
4443 Bidirectional Static TCP/TLS Web server for peripheral device software downloads and log uploads Yes No
5001 Inbound Static TCP/TLS Polycom Content App Yes No
5060 Bidirectional Static TCP or UDP, depending the on configuration SIP Yes No
5061 Bidirectional Static TLS SIP Yes No
5297 Inbound Static TCP Bonjour Yes No
5298 Inbound Static TCP Bonjour Yes No
5353 Inbound Static UDP Bonjour/AirPlay (multicast Domain Name System [mDNS]) Yes No
6514 Outbound Static TLS Remote logging No Yes
7000 Inbound Static TCP AirPlay standard services Yes No
7080 Inbound Static TCP Web services Yes No
7081 Inbound Static TCP Web services Yes No
7100 Inbound Static TCP AirPlay mirroring services Yes No
16384–32764 Bidirectional Dynamic UDP RTP/RTCP (video and audio streams) Yes Yes
18888 Inbound Static TCP Modular room messaging Yes No
44444 Inbound Static TCP Content stream Yes No
47000 Inbound Static TCP AirPlay casting services Yes No
49152–65535 Bidirectional Dynamic TCP H.245 Yes Yes
49159 Inbound Static UDP Bonjour/AirPlay (mDNS [Windows]) Yes No
49163 Inbound Static UDP Bonjour/AirPlay (mDNS [Windows]) Yes No

If official support is required please check how to phone or open a case here

The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.


⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓SIGNATURE ⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓
Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
Please also ensure you always check the VoIP , Video Endpoint , Microsoft Voice , PSTN or other FAQ's in the different sections