GSC3570 secure open door via GDS3710
The GDS37xx can be powered via PoE, the GSC3570 can connect to same network via PoE or WiFi. For open door combination with GSC3570 and
GDS37xx, if GSC3570 needs to control multiple GDS37xx, it has to use SIP and the related GDS37xx will control the strike/lock. The different GDS37xx
doorbell call will have“ One Button Open Door” displayed when in “Preview” (early media support) or when call established.
The GSC3570 user will press the virtual button on touch screen to remotely open the door controlled by the related GDS37xx.There is no door
limitation for such usage but only ONE DOOR can be opened at one time. It is just a SIP call open door application, but strike/lock control circuit is
located outdoor.
For “Secure Open Door”, the GSC3570 is peering with GDS37xx. The GSC3570 controlling the relay/strike/lock from inside the building (Unlike
GDS37xx installed outside), but only ONE door can be controlled because GSC3570 only has one Relay Control circuit build in.
This peering can be via LAN/WAN but LAN is recommended and actually most of the application scene are in LAN environment because most likely
the GSC3570 and GDS37xx are in the same building. Although SIP/UCM over Internet/WAN also works, it is recommended to use static IP if the
GSC3570 (inside) and GDS37xx(outside) are at same location in the same LAN.
This setup is much simple and reliable in case there is network outage like Internet/UCM is down.
For the GSC3570 and GDS37xx peering, it can be used via SIP only (Cloud or UCM); IP only (No SIP proxy or UCM but static IP address) and Mixed
(SIP and fallback to IP if Proxy failed).
GDS3710 Web Configuration
This setup can be found under device web UI→Door System Settings →Basic Settings:
GSC3570 secure open door via GDS3710-GDS3710 configuration
GSC3570 Web Configuration
Notes
Minimum firmware required for this to work:
Outdoor Device: GDS371x (FW1.0.11.23) and GDS370x(FW1.0.3.11)
Indoor Device: GSC3570(FW1.0.5.2)