How to check, on an Nx Witness system, that it sends its alarms to GC Surge by e-mail (SMTP): where the settings are, what must be switched on, how to test, and what to do when it fails. Use it together with Not Receiving Alarms.
Nx Witness is a video management system. The alarms come from the Nx Witness server, not from the single cameras. An alarm e-mail needs three parts: the e-mail settings of the system, motion detection on the camera, and an event rule that sends the e-mail. Names differ a little between versions.
Who it is for: Technicians and admins who can sign in to Nx Witness as an administrator.
You need | Notes |
|---|---|
The address of the Nx Witness server and its port | The factory port is 7001. Tick HTTPS (secure) in GC Surge. |
An administrator account of the system | A local administrator account of the system. |
The values from GC Surge | In GC Surge: Sites & Cameras |
Watch:
Field in Nx Witness | Must be |
|---|---|
Email (the sender) | From email from Setup details |
SMTP Server | Host |
Port | Port |
User | Username |
Password | Password (use the show and copy buttons in Setup details) |
Connection type | The value of Encryption. For "tls" with port 587 choose TLS. |
Do this for every camera that should send alarms.
Part of the rule | Must be |
|---|---|
Event | Motion on Camera (or the analytics event you use) |
Source | The cameras that should send alarms |
Action | Send email |
Target | To email from Setup details, under additional recipients |
Schedule | Covers the times when alarms are wanted |
Interval of action | Instant, or the shortest interval. A long interval holds alarms back. |
Symptom | Cause | What to do |
|---|---|---|
GC Surge shows Setup failed at Device credentials | Wrong password, or the user is not an administrator. | In GC Surge: Edit, enter an administrator account, Save and retry. |
GC Surge shows Setup failed at Camera reachable or Loading device settings | Wrong port, HTTPS (secure) not ticked, or the address of a camera was used. | Use the address and port of the Nx Witness server (7001) and tick HTTPS (secure). |
Test of the e-mail settings fails | No internet access of the server, a blocked outbound port, wrong user or password, or the wrong connection type. | Section 2. Copy user and password again. Choose TLS for port 587. |
Test works, but no alarm arrives | No motion detection, no recording schedule, or the rule is off. | Sections 3 and 4. |
Alarms arrive late or one per several minutes | Interval of action of the rule is high. | Set it to Instant or the shortest value. |
Only some cameras send alarms | The other cameras are not in the Source of the rule, or have no motion detection. | Add them to the rule. Do section 3 for them. |
The server is offline in the Nx Witness client | The server computer is switched off or has no network. | Start the server. No alarms can be sent while it is offline. |
Alarms stopped after an update or a restore | The e-mail settings or the rule were removed. | Retry in GC Surge. Then check sections 1 and 4. |
Thank you — your feedback goes to the team that owns this page.
