Skip to main content
OpenEye Knowledge Base

Recorder Settings in OWS

Within the Customer Portal, access the Recorder List under Management tab > Recorders > Recorders. Click Edit next to the desired recorder in the Recorder List to view Recorder Settings.

Remote Network Settings

OWS Recorder List Remote Network Settings.png

The Remote Network Settings tab allows users to configure the method used to connect to the recorder. Users can control individual options by switching each to on or off.

Inbound HTTP/HTTPS Traffic

When this option is disabled Direct Connect and LAN Smart Forwarding UI is hidden and a command is sent to the recorder to disallow any inbound traffic from OWS. Only local network inbound traffic is allowed.

Direct Connect

Configure this option when using a static External IP Address to connect to the recorder. This will send video directly from the recorder to the client and bypass Web Services. Using this option may require port forwarding configuration.

LAN Smart Forwarding

When the recorder and client are both on the same LAN, Web Services attempts to send the video directly from the recorder to the client. This feature is enabled by default because it can improve video playback performance in many circumstances.

Enable Domain Redirect

Redirect over HTTPS in Lan Smart Forwarding mode to a pre-selected domain name with a valid CA signed cert imported into the recorder.

NOTE: Check Enable Domain Redirect to enter Domain Redirect Target and Port.

Peer to Peer

Web Services will provide the client and recorder information needed for the client to connect directly to the recorder. This allows video to be streamed direct.


This connection method transfers video from the recorder to the client by relaying it through the Web Services servers.

Web Connect Region

Web Connect servers are available in multiple regions to provide the fastest possible connection to your recorder. This region is set by default and is typically not necessary to change.

General Info

OWS Recorder List General Info.png

Clicking Edit on the Recorder List page will bring a user to the recorder’s General Info. The General Info page contains the following elements:

Recorder Name

The name of the recorder

Recorder Custom ID

A manually assigned ID for internal organization

Location ID

A manually assigned ID for internal organization

Immix Integration ID

ID for Immix Integrations

Serial Number

Serial Number of the recorder

Address, City, State/Province, Country, Postal Code

Address for the customer account

Software Version

Software version currently installed on the recorder

NAT Traversal Mode

NAT Traversal Mode will always be Automatic except when Direct Connect is configured

Recorder Device ID

Recorder Device ID is used for 3rd party integration

Location manager

Manually given name allows users to create locations for recorders

Move Recorder

Move the recorder to a different Customer Account controlled by the Channel Partner.


Permanently remove the recorder from the Customer Account


OWS Recorder List Cameras.png

Cameras associated with a Recorder are listed by Camera Name, Camera ID, Integration ID and Status. A notification appears when any camera is Disabled or Out-of-Service. Disabled or Out-of-Service cameras will remain visible on the recorder if the Visible box is checked. Clicking the X next to Status will remove the camera from the recorder. Unchecking Health Events removes a camera from all health alerts and health reports. The camera functions normally for all other alerts and reports.


OWS Recorder List Support.png

Support provides recorder diagnostic information, a reboot option, and a connection code entry field to allow technical support to remotely access your recorder. 

Remote Assist Session

If working with Technical Support and they are unable to connect to the recorder using Web Connect, they can attempt to initiate a remote session from this menu. Technical Support will provide a code. Once entered, Connect allows support to temporarily take control of the recorder to remotely resolve issues.

Reboot the Recorder

Reboot will restart the recorder. If the recorder is accepting communications from OWS but not allowing users to connect, this will send a reboot command to the recorder. If the site network is having issues, or the recorder is in a failed state, it may never complete.  

Diagnostic Information

This gives a quick snapshot of information relating to communication back and forth between the recorder and OWS. Seeing numbers here is a good thing, what you don’t want to see is 0s or a blank field. That would indicate that we are unable to communicate with the NVR. 

  • Recorder Last Active: This refers to the last time OWS received any data from the recorder.  

  • Recorder Last Registered: This refers to the most recent time the recorder initiated a connection with the OWS relay servers. Units that are online but idle (no connections streaming video) should refresh this connection periodically. This time will continue to climb with active connections over the OWS relay such as a connection via Command Station Desktop Client streaming video. 

  • Recorder Last Response: This shows how recently the recorder processed and replied to a request over the OWS relay. If the recorder is idle or no connections are active, this may return “Not Yet Occurred This Session”. 

  • Recorder Response Sequence: This is the number of successful replies the recorder has made to requests sent over OWS. If “Recorder Last Response” has not occurred, this will not either.  

  • Session Request Sequence: This tracks the number of requests sent to the recorder over the OWS relay. Comparing to “Recorder Last Response” can show if the NVR is falling behind on fulfilling OWS relay requests. 

Configuration Files

OWS Recorder List Configuration Files.png

Configuration files are automatically collected from the recorder every 7 days and after performing a software update. A manual backup of the configuration can be performed from the recorder System Settings. Click Download to retrieve a configuration file, then import the file to a recorder to install the previous configuration.

  • Was this article helpful?