This Frequently Asked Questions (FAQ) document provides concise answers and guidance for using the GDS371x/370x Series Facility Access Systems. It is intended to assist administrators and users in resolving common issues and understanding key features.
Product Overview & Specifications
GDS370x models (GDS3702, GDS3705) are IP audio-only door access systems. GDS371x models (GDS3710, GDS3712) add an integrated HD camera for video intercom, live video streaming, snapshots, and ONVIF Profile S compatibility for VMS/NVR integration.
The GDS371x/370x series supports multiple access methods depending on model and configuration, including RFID cards/key fobs (125 kHz EM), PIN codes (GDS3705, GDS3710), SIP-based remote door opening, Wiegand input from external readers, and HTTP API-triggered door control.
Yes. The GDS371x and GDS370x support peer-to-peer SIP mode, allowing direct IP calls to compatible SIP endpoints without requiring a SIP server. A SIP server is only needed for PBX-based call routing or multi-extension environments.
Yes. The GDS37xx series is designed for outdoor installation and meets the following environmental and mechanical protection standards, depending on the model:
- All GDS37xx models are rated IP66, providing full protection against dust ingress and powerful water jets.
- GDS3705 and GDS3710 are rated IK09, offering high resistance to mechanical impact and vandalism.
- GDS3702 and GDS3712 are rated IK10, providing very high mechanical impact resistance suitable for outdoor environments with elevated vandalism risk.
Installation & Hardware Interfaces
The GDS series supports power via PoE (Power over Ethernet) as well as DC power input. Administrators should use the power method specified in the user manual and ensure the power source meets the device’s electrical requirements.
The GDS371x/370x can be surface-mounted using the included metal backplate and tamper-resistant screws. The mounting template supports common wall surfaces and standard electrical boxes.
Door locks connect to the device’s dry-contact relay outputs. Both fail-secure (NO) and fail-safe (NC) lock wiring are supported. Wiring diagrams are provided in the GDS371x/370x User Manual.
Yes. The GDS371x/370x supports Wiegand 26-bit input and output, allowing integration with external card readers, keypads, or access controllers, depending on deployment requirements.
Yes. Proper grounding is recommended to improve electrical safety, reduce interference, and protect the device from electrical surges.
Initial Setup & Device Access
The default administrator username is admin. Each device has a unique, randomly generated password printed on the device label. The password should be changed upon first login.
You can access the GDS371x/370x Web UI using one of the following methods:
- Via UPnP (Windows networks):
- Open File Explorer → Network on a Windows PC.
- Locate the GDS371x/370x under Other Devices.
- Double-click the device to open its Web UI in the default browser.
- If the device does not appear, ensure UPnP is enabled on the network.
- Via GS Search utility:
- Download and run the GS Search tool from the Grandstream website.
- Click Search to discover devices on the network.
- Double-click the GDS371x/370x entry to open the Web UI.
- Via GDS Manager:
- Install and launch GDS Manager.
- Navigate to Device → Search and start device discovery.
- Double-click the detected GDS371x/370x to access the Web UI.
- Using the default static IP (no DHCP available):
- Connect the GDS371x/370x directly to a computer.
- Assign the computer a static IP in the 192.168.1.0/24 subnet (excluding .168).
- Open a browser and navigate to http://192.168.1.168
No. The device can operate in direct IP (peer-to-peer) mode. A SIP server is optional and required only for PBX-based deployments.
Configure a SIP account in the Web UI by entering the SIP server address, SIP user ID, authentication ID, and password. Registration status can be verified on the SIP Account Status page.
Yes. All the GDS37xx models can be centrally managed using Grandstream GDS Manager for provisioning, monitoring, and firmware management. Additionally, GDS371x/370x models can be managed using TR-069/GDMS.
Intercom & Door Control Features
When the doorbell button is pressed, the GDS371x/370x places a SIP call to one or more predefined destinations. These destinations can be SIP extensions, IP phones, video phones, Wave clients, or paging groups, depending on the configuration.
The GDS371x/370x can call SIP-compatible endpoints such as Grandstream IP phones, video phones, IP PBXs, Wave desktop and mobile clients, and other SIP-compliant devices that support audio and video calls.
Yes. The GDS371x/370x supports two-way audio communication using its built-in microphone and speaker. It also streams video from the GDS371x to the receiving endpoint, but it does not support receiving video from the remote party.
During an active call, authorized users can unlock connected doors by sending configured DTMF digits or by using supported on-screen controls on compatible endpoints. The GDS371x/370x then triggers the appropriate relay output.
Yes. All GDS371x/370x models support up to two independent relay outputs, allowing control of multiple doors or access systems.
If a call is not answered, the GDS371x/370x follows the configured call routing behavior, which may include calling additional destinations, timing out, or triggering predefined actions as configured on the Web UI.
RFID cards and key fobs are enrolled and managed through the GDS371x/370x Web UI or supported management tools. Each credential can be assigned access permissions, door relay behavior, and validity rules.
Yes. The GDS371x/370x supports time schedules that define when access credentials or door control actions are permitted. Schedules can be configured to allow or deny access based on time of day and day of the week.
Yes. When multiple relay outputs are available, each relay can be configured with independent access rules, schedules, and credential assignments.
Yes. Authorized users can unlock doors remotely using SIP DTMF commands, HTTP API calls, or supported management applications, depending on configuration.
Yes. The GDS371x/370x records access events such as card usage, door unlock actions, and access denials. These logs can be reviewed through the Web UI or exported for audit purposes.
Alarms & Event Handling
The GDS371x/370x models support two physical alarm input ports that can be connected to third-party low-voltage sensors, such as door sensors, exit buttons, or IR motion detectors.
The key characteristics of the alarm inputs are:
- Input type: Voltage-based alarm input
- Supported voltage range: 3 V < Vin < 15 V
- Trigger condition: Any voltage change within the supported range will be detected and can trigger an alarm event or action
- Typical devices: Door contact sensors, motion sensors, emergency buttons, and other compatible low-voltage sensing devices
Alarm inputs must remain within the specified voltage range, as higher voltages or incorrect polarity may damage the device.
The GDS371x/370x supports the following alarm trigger types:
- Motion Detection Alarm (GDS371x Only)
- Password Error Alarm (GDS3710 and GDS3705 Only)
- Hostage Code Alarm (GDS3710 and GDS3705 Only)
- Tamper Alarm
- SIP Calling Trigger Alarm
- Digital Input
- Non-scheduled Access Alarm
- Unauthorized RFID Card Access Alarm
When an alarm event is triggered, the GDS371x/370x can perform actions such as initiating audio alarm, SIP calls, triggering relay outputs, sending emails, or generating logs, depending on configuration.
Yes. The GDS371x/370x can be configured to automatically place SIP calls to predefined destinations when specific alarm conditions are met, enabling immediate notification of security events.
Yes. The GDS371x/370x records alarm events, access attempts, door actions, and system events in its event logs. These logs can be viewed and exported through the Web UI for review or auditing.
Yes. Each alarm input can be individually configured with its own trigger conditions, actions, and schedules, allowing flexible event handling tailored to specific deployment requirements.
Configuration Provisioning & Firmware
The GDS371x/370x allows administrators to back up and restore configuration files directly through the Web UI using the Data Maintenance export/import feature. Configuration files can be exported and stored locally, then restored to the same device or deployed to another GDS371x/370x running a compatible firmware version.
Yes. The GDS371x/370x supports automatic provisioning using HTTP, HTTPS, and TR-069. Provisioning parameters can be configured manually in the Web UI or delivered from a provisioning server.
Firmware can be upgraded through the Web UI by configuring an upgrade server. Firmware upgrades can also be managed centrally through supported management platforms.
In general, configuration settings are preserved during firmware upgrades. However, administrators are strongly recommended to back up the configuration before upgrading in case a factory reset or rollback is required.
Troubleshooting & Maintenance
Verify that the Doorbell Mode is set to “Call Doorbell Number”, and check that at least one call destination is configured for the doorbell button.
In SIP mode, confirm the account registration status. In direct IP mode, ensure that direct IP call settings are active and that the target IP address is reachable.
This issue is typically caused by using an incorrect PIN entry sequence based on the configured PIN Type. Verify the correct procedure for the selected mode:
- Private PIN: Press star (*), enter the virtual number, press star (*) again, enter the private PIN, then press pound (#).
- Card & Private PIN: Swipe a valid RFID card, then press star (*), enter the private PIN, and pound (#).
- Unified PIN: Press star (*), enter the local PIN, then press pound (#) to unlock the door.
In addition, confirm that the user or access group is assigned to an active access schedule that permits entry at the current time, and that card management is properly configured and enabled if Card & Private PIN authentication is required.
This behavior is usually caused by access or security rules rather than a hardware issue. One common cause is the Non-Scheduled Access Alarm, which is triggered when a user presents a valid card but attempts to open the door outside their assigned access schedule.
Another possible cause, on the GDS3710/GDS3705 only, is the Hostage Code Alarm. When a configured hostage password is entered on the keypad, the door opens normally while an alarm is triggered according to the assigned alarm action profile.
Please ensure to review access schedules, alarm event settings, and hostage code configuration to determine which condition applies.
This behavior is usually caused by alarm configuration settings. Even if an alarm action profile includes an audible prompt, no sound will be played if the corresponding event is selected under Silent Alarm in the Alarm Events Config.
In addition, the alarm action profile itself may not have an audible prompt configured. Verify that the alarm event is not marked as silent and that the assigned alarm action profile includes an audio prompt option. Both conditions must be satisfied for an audible alarm to play.
If the device can place and receive calls but does not unlock the door, the issue is typically related to relay configuration, access rules, or wiring, not SIP signaling. Verify the following:
- Relay assignment: Ensure the door unlock action is mapped to the correct relay output.
- Relay mode: Confirm the relay is configured as Normally Open (NO) or Normally Closed (NC) to match the lock type (fail-secure vs. fail-safe).
- Lock power: Verify that the electric strike or magnetic lock has a proper external power supply and is not powered solely by the GDS relay.
- DTMF/unlock method: Confirm the correct DTMF digits or SIP INFO method is configured and supported by the calling endpoint.
- Wiring integrity: Check relay wiring, terminal connections, and confirm a flyback diode is installed for inductive loads.