-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
Powering up/Booting or connecting a Poly Poly Studio X, G62 or G7500 to a network switch initiates certain network Protocols
NOTE: The below has been originally tested with a Studio X50 running Software 3.13
INITIAL BOOT PROCESS
Within this DHCP Discover message, the Poly devices uses various Sub-Options
- Option 12 Host Name (Studio X,G62 or G7500 and from 4.1.2 also for TC8 or TC10)
The above can be used to identify the device in the Network
- Option 55 is a List of Sub Options
For Studio X,G62 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" for the free Poly Lens service has more details on how to use this.
DHCP Option Format: https://<ServerUser>:<Password>@<ProvisioningServerAddressURL>
Since TCOS 6.3.0 for TC8 and TC10, the options 66 or 160 can be used as well - DHCP Option 15 can be used so the phone can identify the Domain it is using
- DHCP Option 6 is to identify the DNS / Domain Name server(s)
DHCP Option 42 can be used to set the => time <= on the device
If set to the default AUTO setting and no timeserver using DHCP Option 42 is supplied the device will try and use ntp.polycom.com
- DHCP Option 3 requests the default router or => gateway address <=
- DHCP Option 1 request's the phones => subnet address <=
- DHCP Option 60 Identifies the Vendor Class Identifier for Studio X or G7500
TC8 or TC10
More details on the Poly Phone DHCP Vendor Option can be found in the => Technical Bulletin 54041 <= and troubleshooting => here <=.
The same applies to Poly Studio X or G7500
Once the device has an IP it will attempt to connect to Poly Lens and other locations:
The TC device, G7500, or Studio X are then joining the Multicast group 224.0.0.251
The TC device then uses 224.0.0.200 to advertise and pair with a compatible device
Failing to be able to pair to a Studio X, Studio G62 or G7500 the TC device will display:
Enabling LLDP
A Poly Studio X, Studio G62 or G7500 as a factory default does not have LLDP enabled and this needs to be activated.
- TV UI via Touch enabled Screen or Mouse via right swipe to the left System Settings > Lan Properties > General > Enable LLDP
- Via the Web UI General Settings > Lan Network > Lan Options
Enabling 802.1p/Q VLAN
A Poly Studio X, Studio G62 or G7500 as a factory default does not have LLDP enabled and this needs to be activated.
- TV UI via Touch enabled Screen or Mouse via right swipe to the left System Settings > Lan Properties > 802.1p/Q > 802.1p/Q
- Via the Web UI General Settings > Lan Network > Lan Options > Enable 802.1p/Q
The device may reboot and may no longer accessible via the Web Interface if the VLAN selected is not enabled on the Switch and/or the IP has changed.
System Port Usage
Source =>here<=
The following table lists the inbound, outbound, and bidirectional ports used by your G7500 and Studio X series system.
| 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 |
|
443 |
Bidirectional |
Static |
TCP/SCTP |
Static TCP HTTPS web server listener that provides TLS access to the web interface. AirPlay Microsoft Exchange Server Zero Touch Onboarding Provisioning (for example, Poly Clariti Manager) Video system control using a Poly TC device Video system control using a Poly Trio system REST API 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 |
Troubleshooting:
- Feb 23, 2024 Question: Can I remotely take a Wireshark capture from a Poly Studio X or G7500?
Answer: Enable Telnet Access via the Web Interface or Poly Lens Security > Access > Enable Telnet Access and save the setting.
- Place a FAT 32 formatted max 32GB USB stick in the Studio X or G7500
- Connect via Telnet on Port 24
- To start the trace type packetcapture start
To stop the trace type packetcapture stop
Then remove the USB Stick
Need help or have any questions? Start a new discussion here and get the answers you need.
