This Frequently Asked Questions (FAQ) document provides concise answers and guidance for using the Grandstream facility speaker, the GSC3516. This FAQ is intended to assist administrators and users in resolving common issues and understanding key features.
Product Overview & Specifications
The GSC3516 is equipped with a 15 Watt HD speaker.
The GSC3516 can be powered using the PoE only.
The GSC3516 supports 16 SIP accounts.
G.711µ/a, G.722 (wide-band), G.726-32, iLBC, Opus, G.729A/B in-band and out-of-band DTMF (In audio, RFC2833, SIP INFO), VAD, CNG, AEC, PLC, AJB, AGC, ANS
The GSC3516 supports high-resolution audio with a sample rate of 48KHz.
The Ethernet port of the GSC3516 supports auto-sensing 10/100Mbits per second speeds.
Setup & Registration
The GSC3516 can be installed on the wall and on the ceiling tiles.
The GSC3516 supports OpenVPN®, it can be connected to any VPN server as long as it supports OpenVPN®.
Yes, PPPoE protocol is supported by the GSC3510/3505.
Mass provisioning can be done using TR-069 through Grandstream cloud management platform, GDMS Unified Communication, or using your own TR-069 server.
GSC3516 can also be provisioned using AES encrypted XML configuration files.
Calling Features & Line Management
Yes, the GSC3516 supports multicast paging. It does not require to have a configured SIP account. The speaker listens on the configured multicast IP address. Once an audio stream is received on the multicast IP address, the speaker will automatically play the paging.
Yes, you can initiate an RTSP audio stream to the GSC speaker, which will be played in real-time.
Playback cascade is a feature that allows playing the same paging on all the secondary GSC3510/3505 speakers. The user pages the primary GSC speaker which duplicates the paging traffic and sends it to the speakers configured as secondary to the paged speaker.
Configuration, Provisioning, & Firmware
The current firmware version of device can be found on web UI on Status > System Info > Information > Software Version.
GSC3516 supports firmware upgrade via the following methods:
- Method 1: Upload the firmware file
Manually upload the firmware file through the device Web UI to perform the upgrade (supported for applicable firmware versions only).
- Method 2: Using a firmware server (HTTP/HTTPS/TFTP)
Configure the device to retrieve and install firmware from a remote server using supported protocols: HTTP, HTTPS, or TFTP.
The firmware server address can be provisioned manually in the Web UI or automatically via DHCP options (for example, Option 66 or Option 160, depending on deployment).
- Method 3: Using GDMS
Upgrade firmware centrally via GDMS (Grandstream Device Management System), enabling remote, batch, and scheduled firmware management.
To save a backup file of the configuration of the GSC3516, please follow the steps mentioned below.
- Access the webUI and use the administrator’s credentials to log in.
- Navigate to Maintenance > Upgrade
- Click on “Download Device Configuration” to download the configuration file in .txt format. The user also download the config file in xml format.
The GSC3516 supports layer 2 QoS features, such as, 802.1Q, 802.1p, 802.1e and layer 3 QoS like ToS, DiffServ, MPLS.
Troubleshooting & Maintenance
The GSC3516 can be reset to factory setting either through the physical button, and it can be reset also through the web UI configuration page.
- Physical reset button: Press and hold the reset button next to the Ethernet port for 10 seconds. The LED will blink fast in a red color indicating that the device is being reset to factory settings.
- Web UI configuration page: Navigate to Maintenance > Upgrade then click Factory Reset button.
You should make sure that the phone is connected to the network and the phone is able to obtain an IP address. Secondly, check if the account is set to active by setting the “Account Active” configuration in the Account page of the web interface to “Yes”. Additionally, check if the login information and the SIP server are correct. If the SIP server is wrong, the phone cannot contact the SIP sever for registration. If the login information is wrong, the SIP server will reject the registration request of the phone.
If all of the above are correct, there may be a problem with NAT traversal. If the GSC3516 is on a LAN and needs to register to a SIP server on a public IP, please enable NAT traversal by selecting the NAT traversal method according to your network environment. If you are unsure, it is recommended to select “Auto” to enable the automatic NAT traversal configuration feature.
GSC3516 provides diagnostic features such as, Syslog, packet capture, ping tool, traceroute tool, and remote diagnostics tool which allows remote access and collection of the logs.
Network & Security
GSC3574/3575 supports encryption methods like TLS, SRTP, HTTPS, and SSH.