To add a new PTZ preset:

1. Click on the Home button.
2. Click on the Device Setting link in the Resource Management section.

On the Device Settings screen:

1. Click on the Preset Setting tab.
2. Click on the PTZ camera that you want to configure the preset location for.

1. Use the pan tilt zoom controls to navigate to the angle and zoom that you want for the new preset location.
2. Click on the Add button.
3. Enter a Name for the preset, then click OK.

The new preset will appear in the Preset list. Repeat these steps for all of the preset locations you want to add to your system. Then return to the live view of your security cameras.

Selecting PTZ Preset Locations from the VMS Software

While viewing your PTZ camera live from the VMS software, right click on the PTZ camera with the mouse. Select PTZ Control.

When the PTZ Control box opens, you will see all of the presets towards the bottom of the controller. When you click on the play icon next to any of the presets, the PTZ camera will navigate to that preset location.

Click on the start button in the lower right, then click on Settings.

On the main settings screen, click on the PTZ link in the Camera section.

On the PTZ settings screen.

1. Select the PTZ camera that you want to use.
2. Click on the Add button to add a new preset location.

On the Add Preset screen, choose a Preset Name. Click on the vitrual keyboard enter key when you are done.

The new preset is now added.

1. Use the pan tilt zoom controls to navigate the camera to the location you want to save.
2. Click on the Save Position button.

The PTZ preset location is now setup and saved. You can click on the X button in the upper right when you are done adding all of your preset locations.

Calling your PTZ Camera Preset Locations from your DVR

Now you can call any of the preset locations from directly on your DVR / NVR and also remotely from the mobile app and desktop software.

To call your preset locations directly on your Viewtron DVR / NVR. Navigate to the single camera live view of your PTZ camera, then left-click the mouse button on the screen. Then select PTZ Control.

On the PTZ controls screen, you will see a list of all of the presets. Click on the arrow next to any of the Preset names. Your PTZ camera will navigate to that preset location.

Click on the return icon in the lower right to close the PTZ controls menu.

1. Click on the plus button to add a new live view.
2. You will see the new view tab added and notice there is an *asterisk next to it. The *asterisk is present to show you that the new view has not yet been saved. If you close the software before finishing these instructions, that view will not be saved for the next time you start the VMS software.
3. You can choose the camera layout for the view along the bottom of the screen.
4. Drag the cameras from the left menu on to the new live view grid.

You can find our setup instructions to remotely connect the decoder directly to an IP camera’s RTSP stream without a DVR here. The setup instructions to remotely connect the decoder to RTSP streams from any of our Viewtron DVR / NVRs here.

Please note that although we as using the hard wired Viewtron IP-HDMI decoder / converter in the below diagrams, this setup also works with the wireless IP camera to HDMI converter model.

Remote Spot Monitor for IP Camera Solution (without DVR)

The above diagram shows a Viewtron IP camera installed at one location (gray area on the left) and the live display TV installed a a different physical location and network (white area on the right). This setup can be referred to as a “remote spot monitor”.

Follow these instructions if you want to enable a remote spot monitor for one or more IP cameras directly (cameras are not connected to the PoE ports on a Viewtron DVR / NVR).

1. Enable the RTSP stream for your camera(s). The default RTSP port for Viewtron IP cameras is 554. You can find the setup instructions here on how-to enable the RTSP stream for Viewtron IP cameras. Be sure that the RTSP stream is enabled for your camera(s)
2. Follow these instructions to setup static IP addresses for your Viewtron IP camera. The purpose of this is to maintain the same IP address for your camera(s) even if your router is rebooted. If the IP address of your IP camera changes, the port forwarding rule that you setup will be invalid. Follow the instructions in the above link to either reserve a static IP address for your camera(s) on your router or assign a static IP address via the camera’s firmware.
3. Setup port forwarding to your IP camera on your router on port 554. You can watch the video on this page if you want understand what is port forwarding. The process to setup port forwarding is slightly different on each make and model router. So, we do not have one set of instructions on how to do this for your particular router. Follow these instructions to setup port forwarding for your Viewtron IP camera.

Remote Spot Monitor for Security Camera Solution (with DVR /NVR)

The above diagram shows the remote security camera to TV setup with the cameras connected to a DVR. The setup process is almost identical to the setup without a DVR. The only difference is that you must set up the static IP address and port forwarding for the DVR / NVR instead of the IP camera(s) directly. Please note that this setup can be applied to IP cameras connected to a Viewtron IP camera NVR and also to BNC CCTV cameras connected to a hybrid DVR.

Here is the setup.

1. Enable the RTSP stream URLs on the Viewtron DVR / NVR. You can find the RTSP setup instructions for Viewtron DVRs / NVRs here.
2. Follow these instructions to setup a static IP address to your DVR / NVR. The purpose of this is to maintain the same IP address for your DVR even if your router or DVR is rebooted. If the IP address of your DVR changes, the port forwarding rule that you setup will be invalid. Follow the instructions in the above link to either reserve a static IP address for your DVR on your router or assign a static IP address via the DVR settings.
3. Setup port forwarding to your DVR on your router on port 554. You can watch the video on this page if you want understand what is port forwarding. The process to setup port forwarding is slightly different on each make and model router. So, we do not have one set of instructions on how to do this for your particular router. Follow these instructions to setup port forwarding for your Viewtron DVR / NVR.

Port Forwarding Setup on Router (RTSP Port 554)

The exact process to setup port forwarding varies based on the make and model of the router that you are using. This is a screenshot from a LinkSys router. One of the most common residential and small business brands. Please check the manual specific for your router for port forwarding instructions. You can also refer to this webpage that has port forwarding instructions for many popular residential routers.

CCTV Camera Pros also offers this port forward router setup service for customers that would like us to handle everything for them. We also setup the static IP address and DDNS service for you.

In the above example, there are two ports setup for forwarding, 80 and 6036. You will notice that the port forwarding rule is given an Application Name for identification, an external port, internal port, protocol, and IP address.

In the case of setting up port forwarding for the RTSP stream from the Viewtron IP camera or DVR / NVR, you ONLY need to forward one port: 554. You can name the port forwarding rule whatever you like on your router. You can make the external port 554 to match the actual internal port, 554. You can specify both or TCP / IP for the protocol if your router requires that. And last, you must enter the LAN IP address of IP camera. You can use this online check open port port forwarding tool to confirm your rule is setup properly.

You can see the standard LAN Ethernet port in between the power supply input and HDMI output ports. To start the setup follow these steps.

1. Using a standard CAT5 or CAT6 network cable, connect the decoder / converter to your network.
2. Using a standard HDMI video cable, connect the HDMI output port to your HDMI TV / montior.
3. Connect the included 12V DC power supply to the DC12V input, and connect the other end to a standard 110v power receptacle.

When the converter boots up and is not yet setup to connect to a video stream, it displays the IP address assigned to it on the screen. Use this IP address to access the converter via a web browser. The default user id is admin. The default password is also admin.

After you login to the converter box, do the following.

1. Click on the WIFI setting link under System settings.
2. Change the WIFI dropdown to Enabled.
3. Click on the Apply button.

When done, reboot the converter box.

After you reboot, log into the IP converter / decoder box again via a web browser and do the following.

1. Click on the WIFI setting link under System settings.
2. All of the wireless networks in range will now appear on the WIFI list drop down. Select your wireless network. Enter the WIFI password.
3. You must either enable DHCP or disable and assign a static IP address to your decoder in the WIFI IP field. If disable DHCP and you are manually assigning a static IP address, you must also assign the WIFI Gateway and WIFI Netmask. This will depend on the setting on your router.
4. Click Apply.

You must reboot your decoder box again. This time be sure to unplug the network cable from the LAN port on your decoder, then unplug the power supply, wait 5 seconds and plug it back in. You must unplug the network cable before you reboot in order for the decoder to connect to your wireless access point.

When you reboot, you will notice now that a WIFI IP address will appear on the screen. Now your IP to HDMI decoder is connected to your network over the wireless network connection.

Setup IP Camera RTSP Stream(s)

1. Log into your IP decoder box again. This time using the WIFI IP address
2. Click Stream Address Settings on the left.
3. Select the number of RTSP camera streams that you want to configure (1-4).
4. Enter the RTSP stream URL for each security camera that you want to display. You can find instructions on how to enable the RTSP stream and locate the URL for Viewtron IP cameras and Viewtron DVRs / NVRs here.
   • Viewtron IP Camera RTSP Stream Setup
   • Viewtron DVR / NVR RTSP Stream Setup
5. Click Apply.

The live view of your security camera(s) should now appear streaming on your TV.

4K Resolution Spot Monitor for IP Camera

Here is a 4K resolution image captured from the HDMI output of the Viewtron wireless IP camera to TV converter / decoder. Please click on the image to see the full UHD 4K resolution image.

How to configure Viewtron LPRs with the Mobile App

Initial Steps

First, you’ll want to download SuperLive Plus from the Google Play Store or the App Store.

Once you’ve downloaded the app, make an account here:

Now, plug your LPR camera into a PoE/Ethernet port on your network. Make sure the camera is receiving power (the camera will click, and then take a few minutes to boot).

Note: The Viewtron LPR camera cannot be plugged directly into a Third-Party DVR or NVR. It must be connected to a network with internet connection!

Finding the LPR Camera on your network

Now get on a PC connected to the same network as your camera.

Download the Viewtron IPTool for Windows or Mac. This tool allows you to find Viewtron devices on your network.

You can double-click the LPR camera to open its’s WebUI.

Connecting the LPR to your Mobile Device

The username for the camera is admin and the password is 123456. The camera may prompt you to change the password.

Once you have logged into the WebUI, follow these steps:

• Go to Config (1) -> Network (2) -> NAT (3) and then Enable NAT (4). Then Save (5).
• Now, go to SuperLive Plus and Scan for Devices (6 + 7)
• You can Scan the QR Code (8) and then enter the Security Code on the last box of the Add Device screen.

While you are in the WebUI, you can also configure the License Plate Recognition settings in:

Event -> License Plate Detection

Configuring Notifications with your LPR

Now that the LPR is tied to your mobile device, you’ll need to ensure that push notifications are on.

You can do this by going to Push Settings, selecting your LPR and Enabling Message Subscription and Smart Alarm

Ensure that your LPR settings are configured properly so you can receive notifications.

Click on the Settings link on your DVR / NVR.

Click on the AI / Event link on the main settings screen.

1. Click on the General Event link on the left.
2. Click on the Exception Alarm link on the top navigation.
3. Setup the Buzzer to Off for the Network Disconnection settings.
4. Click Apply.

Viewtron DVRs have a setting that allows you to do exactly this: Adjust the resolution without changing the camera’s FOV or Aspect Ratio. It’s called Lite Mode.

You can find Lite mode here:

Start -> Settings -> Camera -> Camera Signal

Once Enabled, hit Apply.

Then, you can double-check your resolution and framerate in the Encode Parameters:

Start -> Settings -> Record -> Encode Parameters

Now you can see there is higher framerates to choose from! The lower resolution will also lengthen your recording time before overwriting.

To setup H.265 video codec recording, do the following on your DVR.

1. Click on the menu button in the lower right and select settings.
2. From the main settings screen click on the Encode Parameters link in the Record section. The above screen will appear.
3. Set the Encode setting for each of your security cameras to H.265 or H.265+
4. Be sure to do this for Schedule Recording and Event Recording by clicking on those links near the top of the settings.
5. Click apply after you change each one.

There are only a few steps you need to take in order to utilize this feature:

1. Plug the Viewtron Encoder into a network that has any Windows Computer on it. You do not need the Decoder right now.

2. Download the Viewtron Decoder Network Scan Tool on a Windows PC so that you can locate the decoder on your network.

3. Unzip the file on your PC and run the tool. In Windows 11, this is done by right-clicking and using Extract All. The network scanner will automatically search the network for all Viewtron Encoders & Decoders.

4. Double-click the Lan IP of the Encoder to log into it through the webpage. The default username is admin and the default password is admin.

5. Once on the WebUI, go to System -> Network and disable DHCP. Then, scroll down and click Apply.

6. The Encoder will prompt you to restart it. Unplug the Encoder from the network and from power.

7. Plug the Encoder & Decoder into power.

8. Plug the Encoder and Decoder into each other with a Cat5e Ethernet cable.

You’re done!

How to configure a Viewtron NVR or DVR with the IP-HDMI-D4:

Initial Steps

You’re done!

This is the advise that CCTV Camera Pros gave to this customer.

Each report allows our software development team to refine the system and deliver a more reliable experience for everyone.

Here is how to document and report false alarms from AI Events:

When documenting a false positive, there is a few things that we will need:

• A Snapshot & Recording of the AI Event
• The Model & Firmware Version of the recorder you are using
• The Model & Firmware Version of the camera that recorded the false positive

First, get the Snapshot & Recording of the event.

This can be found by going to Start -> Intelligent Analytics.

Then, you can search for your desired event by event type (1), date/time (2), and camera (3). Then, click Search.

When you find the false positive event, click it and then select the check-mark box on the top-right of the thumbnail.

Then switch the viewport to Record. If you would like to, you can Adjust the duration of the recording. 

Now, insert a USB drive into the NVR.

Then, click the Backup button and then select Backup Picture and Record. 

Export the data to a place of your choosing on the thumb drive.

Next, find the Model and Firmware for your Recorder.

The Model (1) of your recorder can be found by going to:

Start -> Settings -> System -> Information -> Basic

The Firmware Version (2) of your recorder can be found by clicking the View button next to “About this machine.”

Finally, find the Model and Firmware Version of the camera that captured the false positive.

The Model (1) and Firmware Version (2) of your camera can be found by going to:

Start -> Settings -> Camera -> Edit Camera

You may need to scroll to the right on the bottom scroll bar.

Here’s how we would lay out the data based on the examples above:

Camera: IP-A8D
Camera FW: 5.2.3.23

Recorder: VT-NVR-4
Recorder FW: 1.4.13.850

You can access your Viewtron DVR / NVRs activity log as follows.

Click on the menu button in the lower left, then select Settings.

On the main settings page, click on View Log in the System section.

On the System View Log screen, you can choose a date range for the event you are searching for. You can also select the type of event you want displayed if you want to narrow down your search.

For event types where there was a video recording, you can click on the video player icon next to the event to playback the recorded video surveillance footage.

——————————————————————————————————————————

If you purchased your Viewtron Hybrid DVR after January 1st, 2026, here is how many IP cameras your DVR can support:

VT-DVR-4: 2 additional IP channels, up to 6 ch. 6 total channels supported

VT-DVR-8: 8 additional IP channels, up to 16ch. 16 total channels supported

VT-DVR-16: 8 additional IP channels, up to 16ch. 24 total channels supported

VT-DVR-32/4K: 8 additional IP channels, up to 16ch. 40 total channels supported

——————————————————————————————————————————

Please note that you will have to disable some of your Coaxial outputs on the back of the DVR in order to utilize extra IP channels!

If you purchased your DVR earlier than January 1st, 2026, feel free to email us at info@cctvcamerapros.net and we can check for you!

From the main settings menu, select AI / Event. One the AI / Event screen:

1. Click on the AI / Event link.
2. Click on the Motion link on the left.
3. Set the Schedule to <None> for all of your security cameras.

Click Apply in the lower right.

You should also ensure that you Viewtron NVR is setup not to record on Motion Detection Events.

Select Record from the main settings menu. Make sure the recording mode that you are using DOES NOT include Motion Record.

For Viewtron AI security camera systems, I usually recommend to setup a custom recording configuration that consists of Always (24 x 7) Recording + AI Record. This give you continuous recording but also bookmarks all of the AI detection events. This way you never miss any recording but it is easy to locate the human detection and / or vehicle detection events on your system. If you are using LPR cameras and face recognition cameras, those AI events will also all be bookmarked.

COC is a technology allowing surveillance systems to transmit video, power, and control signals (like PTZ, zoom, and OSD menus) simultaneously over a single coaxial cable.

If your camera does not support COC, you will need to use the RS485 ports on the back of your DVR. RS485 is the protocol used to send control signals to your analog cameras. The RS485 ports on the back of Viewtron DVRs typically look like this:

In this picture I have labeled the A and B ports to reflect what they may be labeled as on your camera.

—————————————————————————————————————————

Once you have connected the RS485 cables to your DVR, you will have to change the Control Protocol, BAUD rate, and Address settings in the Viewtron DVR (These values can typically be found in the OSD menu of your camera).

Once you find these values, locate the settings in the Protocol menu:

Start -> Settings – > Camera -> PTZ -> Protocol

Once you match the Protocol, Baud Rate, and Address and click Apply, you should then be able to go to the PTZ control in the Live Display menu and control your cameras.

This feature is located in the Trigger Mode section of your event menu, which is found in the AI/Event settings. Please note that the specific feature is not present in this screenshot.  

If you enable the Pop-up Message trigger in the Trigger General section, you should get a pop-up notification on the Live View screen, like this:

However, if you press “Don’t show later” on that pop-up box, the pop-ups will be disabled regardless of your trigger settings.

Once that pop-up disappears, you will need to go into your settings to re-enable pop-ups. Here’s where you do that:

Settings  ->  AI/Event  ->  Event Notification  ->  Display

Once you go here, you will find yourself on this screen where you can disable the check-box.

Your pop-ups will now appear again!

To setup DDNS on Viewtron recorders, follow these instructions.

Click on the Start button in the lower left, then click on settings

On the main settings screen, click on the Network link.

On the Network screen, click on the DDNS link on the gray navigation menu. On the DDNS screen do the following:

1. Check the Enable checkbox.
2. Select autoddns.com from the DDNY type dropdown box. This is the free DDNS server provided to Viewtron products.
3. Enter a name in the Domain Name field. In my example above, I chose mydvr91.autoddns.com.
4. Click on the Register button.

If that name is available, you will see a success message. If the name is taken, you must choose another.

Next, click on the Apply button. Confirm that the Connection Status says: Success. You can now close the DDNS settings on your DVR / NVR.

DDNS is now setup so that you can access your DVR / NVR using the DDNS hostname that you setup. In this example, mydvr91.autoddns.com.

You can now use that DDNS hostname to access your DVR / NVR in a web browser, form the mobile app, and from the VMS software.

What is DDNS?

DDNS stands for Dynamic Domain Name Service. To understand DDNS, it helps to know how the Internet works. Every device connected to the Internet has an IP address – a string of numbers like 98.234.12.45. When you type a website name like google.com into your browser, DNS (Domain Name Service) translates that name into an IP address so your computer knows where to connect. DDNS does the same thing, but with one important difference: it automatically updates when your IP address changes.

Most home and business Internet connections use a dynamic IP address, which means your Internet provider can change your IP address at any time. When that happens, your remote access to your security camera system stops working because the address you saved in your phone app or computer software is no longer valid. DDNS solves this problem by giving your DVR a hostname (like mydvr91.autoddns.com) that automatically updates whenever your IP address changes. Your DVR periodically checks in with the DDNS server, and if your IP has changed, it updates the record so your hostname always points to the right place.

How DDNS Helps You Access Your Security Cameras

I hear from customers all the time who had remote viewing working perfectly, then one day it just stopped. Nine times out of ten, their IP address changed and they didn’t know it. With DDNS enabled, you don’t have to worry about this – your hostname always points to your current IP address, so your connection stays reliable.

The free DDNS service built into Viewtron DVRs and NVRs uses autoddns.com and is included at no extra cost. You don’t need to sign up for a third-party service or pay monthly fees. Just pick a hostname, register it directly from your DVR’s menu, and you’re set. This is one of those features that takes two minutes to configure and saves you headaches down the road.

1. Reduced False Alarms:
   • Traditional motion detection works by analyzing pixel changes in the video feed, which can be triggered by environmental factors like moving trees, shadows, or abrupt lighting changes.
   • SMD uses AI to specifically detect humans, vehicles, or both, ignoring irrelevant environmental noise. This makes the system more reliable and trustworthy.
2. Customizable Detection:
   • SMD allows users to configure the system to detect only humans, only vehicles, or both. This level of customization ensures that the system focuses on relevant events.
3. AI-Based Processing:
   • Unlike traditional motion detection, which relies on pixel changes, SMD uses AI to analyze video data. This ensures that the system can differentiate between objects like humans and vehicles, providing more accurate detection.

However, SMD is a function that is only supported over BNC connections. It is not compatible with any IP cameras.

If you are able to see your devices on the SuperLive Plus app and your local recorder but are having trouble connecting the devices to your Viewtron VMS software, here are some troubleshooting steps you can try:

Step 1: Check your Network Connection

Make sure that the PC you are on is connected to the internet.

On windows, you can check on the bottom right of your screen; if you see a PC with a Cable or a Wi-Fi symbol, you are connected. If you see a Globe with an error symbol, then you are not connected.

For Mac users, check the dock on the top of your screen. You will see a Wi-Fi symbol or a <…> symbol depending on your type of connection.

If you are using an IP to connect to your devices, make sure that your PC is on the same network as that device.

Step 2: Double-Check your credentials

Make sure that you have entered your credentials correctly. In the Resource Management tab of the VMS Software, Edit (1) your device settings and make sure that the Serial Number (3) and User/password (4) are correct.

In the case that you are using a Static IP Address instead of a Serial Number, double-check to make sure that it matches the serial number of the device you are connecting to. (Please note that we do not recommend this method; if you encounter a system reboot of your devices while they are set to DHCP, its IP can change)

Step 3: Reboot Services using ServerTrayUI

Sometimes, there can be a hang-up within the local service that manages the VMS software on your pc. This can prevent your PC from connecting to other devices. Here’s how to reboot the VMS server:

First, search for “ServerTrayUI” on your computer. You can search for it in the Start Menu on Windows, or the Applications Folder for Mac.

Next, Locate the ServerTray UI icon in the Show Hidden Icons section of your PC. It’s a small arrow on the right side of your screen.

Once the app opens, check the Status to see if all the servers are running. Even if they are, press the Reboot All button and wait for the status to refresh to Running.

Then, restart the VMS software.

—————————————————————————————————————————

If you follow these steps and are still having trouble, please call our Technical Support number at (561) 433-8488!

You may want to use this Python based Viewtron IP Camera API server to build your application. It supports HTTP Posts / webhooks directly from Viewtron AI cameras and from Viewtron NVRs.

Login to your Viewtron NVR. Click on the start button in the lower left, then select Settings. On the main settings screen, click on Network.

On the network screen do the following.

1. Click on the HTTP POST link on the left menu under Integration.
2. On the HTTP POST screen, check the enable checkbox.
3. Enter the server connection information that you want the HTTP POST webhook to be sent to.
4. Check the Snap and Original image check boxes if you want to send JPEG images of the event to your server.
5. Click on the Apply button.
6. Next to Event Type. Click on the Configure button.

On the Event Type screen

1. Select which events types that you included in your application on the left side of the screen
2. Click on the >> button to move those events to the Send Event side of the screen.
3. Click OK after you have added all of the event types that you want to include.
4. When you return to the main HTTP POST screen, click Apply again.

If your server is ready to receieve POSTs, you can click on the Test button to test the connection between the Viewtron NVR and you API server application.

When you are done, you may close this screen on your NVR.

If your Viewtron AI cameras are connected to the PoE ports of a Viewtron NVR, you must configure the NVR to send the webhooks to your server. You will not receive the HTTP Post webhooks directly from the IP cameras. It will come from the NVR. This reference documents the NVR API format (v2.0) and supported detection types.

Setup Instructions: See How to Setup NVR API Webhook Events for configuration steps.

NVR vs IP Camera API Format

The NVR uses API version 2.0, which has a different XML structure than the IP Camera v1.x format:

Message Types

The NVR sends three types of HTTP Posts:

Keepalive

Periodic heartbeat (no event data).

<?xml version="1.0" encoding="UTF-8"?>
<config version="2.0.0" xmlns="http://www.ipc.com/ver10">
    <messageType>keepalive</messageType>
    <deviceInfo>
        <deviceName><![CDATA[NVR Name]]></deviceName>
        <ip><![CDATA[192.168.0.55]]></ip>
        <mac><![CDATA[58:5B:69:40:F4:0D]]></mac>
    </deviceInfo>
</config>

Alarm Status

Lightweight notification when an alarm triggers or clears (no images).

<?xml version="1.0" encoding="UTF-8"?>
<config version="2.0.0" xmlns="http://www.ipc.com/ver10">
    <messageType>alarmStatus</messageType>
    <deviceInfo>
        <deviceName><![CDATA[NVR Name]]></deviceName>
        <ip><![CDATA[192.168.0.55]]></ip>
        <mac><![CDATA[58:5B:69:40:F4:0D]]></mac>
        <channelId>1</channelId>
    </deviceInfo>
    <currentTime>1772056914000000</currentTime>
    <alarmStatusInfo>
        <perimeterAlarm><item id="1">true</item></perimeterAlarm>
    </alarmStatusInfo>
</config>

Alarm Data

Full event with detection details and images.

<?xml version="1.0" encoding="UTF-8"?>
<config version="2.0.0" xmlns="http://www.ipc.com/ver10">
    <messageType>alarmData</messageType>
    <deviceInfo>
        <deviceName><![CDATA[NVR Name]]></deviceName>
        <ip><![CDATA[192.168.0.55]]></ip>
        <mac><![CDATA[58:5B:69:40:F4:0D]]></mac>
        <channelId>1</channelId>
    </deviceInfo>
    <smartType>regionIntrusion</smartType>
    <currentTime>1772056914604000</currentTime>
    <eventInfo>
        <item>
            <eventId>916</eventId>
            <targetId>716</targetId>
            <boundary>area</boundary>
            <pointGroup>
                <item><x>1590</x><y>3080</y></item>
                <item><x>4715</x><y>3181</y></item>
                <item><x>4772</x><y>9217</y></item>
                <item><x>416</x><y>9141</y></item>
            </pointGroup>
            <rect>
                <x1>3096</x1><y1>3715</y1>
                <x2>4005</x2><y2>9861</y2>
            </rect>
        </item>
    </eventInfo>
    <sourceDataInfo>
        <dataType>0</dataType>
        <width>1280</width>
        <height>720</height>
        <sourceBase64Length>400924</sourceBase64Length>
        <sourceBase64Data>... base64 JPEG ...</sourceBase64Data>
    </sourceDataInfo>
    <targetListInfo>
        <item>
            <targetId>716</targetId>
            <targetType>person</targetType>
            <targetImageData>
                <dataType>0</dataType>
                <width>336</width>
                <height>448</height>
                <targetBase64Length>78796</targetBase64Length>
                <targetBase64Data>... base64 JPEG ...</targetBase64Data>
            </targetImageData>
        </item>
    </targetListInfo>
</config>

Confirmed Detection Types

These detection types have been tested with NVR v2.0 firmware:

regionIntrusion (Perimeter Intrusion) Confirmed

Triggered when a person or vehicle enters a defined zone.

IP Camera equivalent: PEA with <perimeter> block

lineCrossing (Tripwire / Line Crossing) Confirmed

Triggered when a person or vehicle crosses a defined line.

<eventInfo>
    <item>
        <eventId>1409</eventId>
        <targetId>1309</targetId>
        <boundary>tripwire</boundary>
        <directionLine>
            <startPoint><x>3579</x><y>2550</y></startPoint>
            <endPoint><x>3655</x><y>9797</y></endPoint>
        </directionLine>
        <rect>
            <x1>3494</x1><y1>4409</y1>
            <x2>4261</x2><y2>9791</y2>
        </rect>
    </item>
</eventInfo>

IP Camera equivalent: PEA with <tripwire> block

Image Options

The NVR can be configured to send different image combinations with each alarmData post:

Detection Types – Testing in Progress

The following detection types are available on Viewtron AI cameras but have not yet been tested through NVR forwarding. We will update this section as testing continues.

If you test any of these through an NVR, please reply to this post with the smartType value you observe.

Timestamps

NVR v2.0 uses 16-digit Unix microsecond timestamps:

<currentTime>1772056914604000</currentTime>

To convert to seconds, divide by 1,000,000:

• 1772056914604000 ÷ 1,000,000 = 1772056914.604 (Unix timestamp with milliseconds)

Developer Resources

Python API Server: https://github.com/mikehaldas/IP-Camera-API

The server includes:

• server.py – HTTP server that accepts webhooks from both IP Cameras and NVRs
• viewtron.py – Parser classes for v1.x (IP Camera) and v2.0 (NVR) formats
• Automatic image extraction and saving
• CSV event logging

Clone and run:

git clone https://github.com/mikehaldas/IP-Camera-API.git
cd IP-Camera-API
pip install xmltodict
python3 server.py

Related Posts

• How to Setup IP Camera API Webhook Events – Direct camera webhook setup
• How to Setup NVR API Webhook Events – NVR webhook setup
• API Webhooks for AI Security Camera Alarms – IP Camera detection types reference

Please note if your camera is connected a PoE port on a Viewtron NVR, you must put the IP camera on your local network in order to access the IP camera API directly. Instead of connecting the IP camera to your NVR directly via the NVR PoE ports, you must connect it via the LAN by connecting it to a PoE switch external to the NVR.

Log into your Viewtron IP camera through a web browser.

Click on the Network link on the left side menu, then click on the HTTP POST link.

On the HTTP Post / HTTP Notification screen, click on the Edit button then be sure that V1 is selected in the Push Protocol Version dropdown. Click Save.

Next, click on the Add button.

Then fill in the API server IP address, port, and path. Select Persistent connection from the connection Type dropdown. Set Heartbeat Interval to 30 seconds and check the Send Heartbeat Checkbox. You can also check off the type of alarms and data that you want the server to send. In my testing, I only wanted to send LPR events, so I only checked License Plate Detection in the Smart Alarm Type section. Be sure to check the Smart Alarm Data cehck box. Optionally check the Original and Target picture options if your application will be using the LPR snapshot images. If you are not using images, leave these unchecked as these increase the size of the HTTP Post payload significantly.

When done, click the Save button.

The IP camera is now setup to send webhook HTTP Posts to your server. If you are looking for a server to get you started with your development project. Mike developed one and open sourced it on Github. You can download Mike’s IP camera API server here and you can find the complete Viewtron API developers guide for IP cameras and NVRs here.

Viewtron AI security cameras may be configured to send outbound HTTP Posts / webhooks when an AI detection alarm event occurs. Click here if you are looking for the Webhook API guide for Viewtron NVRs. The format is slightly different. Supported events include license plate recognition, face detection, human detection, vehicle detection, intrusion detection, and more. Please refer to the below API documentation for details on using the webhooks for your application. Please refer to these setup instructions to enable webbook APIs on your Viewtron security camera.

Contents

• 10.1 Intrusion Detection (Perimeter)
• 10.2 Line Crossing (Tripwire)
• 10.3 Face Detection
• 10.4 License Plate Recognition (LPR)
• 10.5 Region Entry/Exit Detection
• 10.6 Target Counting
• 10.7 Video Metadata Detection
• 10.8 Loitering Detection
• 10.9 Illegal Parking Detection
• 10.10 Thermal Imaging
• 10.11 Real-Time Target Object Tracking (traject)

10.1 Intrusion Detection (Perimeter)

GetSmartPerimeterConfig

Retrieves the intrusion/perimeter detection configuration.

Successful Response:

<?xml version="1.0" encoding="utf-8"?>
<config xmlns="http://www.ipc.com/ver10" version="2.0.0">
  <perimeter>
    <switch type="boolean">true</switch>
    <alarmHoldTime type="uint32">20</alarmHoldTime>
    <objectFilter>
      <car>
        <switch type="boolean">true</switch>
        <sensitivity type="uint32" max="100" min="1" default="50">50</sensitivity>
      </car>
      <person>
        <switch type="boolean">true</switch>
        <sensitivity type="uint32" max="100" min="1" default="50">50</sensitivity>
      </person>
      <motor>
        <switch type="boolean">true</switch>
        <sensitivity type="uint32" max="100" min="1" default="50">50</sensitivity>
      </motor>
    </objectFilter>
    <saveTargetPicture type="boolean">false</saveTargetPicture>
    <saveSourcePicture type="boolean">false</saveSourcePicture>
    <regionInfo type="list" maxCount="4" count="1">
      <item>
        <pointGroup type="list" maxCount="8" count="4">
          <item>
            <X type="uint32">4075</X>
            <Y type="uint32">2466</Y>
          </item>
          <!-- Additional points... -->
        </pointGroup>
      </item>
    </regionInfo>
  </perimeter>
</config>

[Back to Top]

10.2 Line Crossing (Tripwire)

GetSmartTripwireConfig

Retrieves the line crossing/tripwire detection configuration.

Successful Response:

<?xml version="1.0" encoding="utf-8"?>
<config xmlns="http://www.ipc.com/ver10" version="2.0.0">
  <types>
    <tripwireDirection>
      <enum>none</enum>
      <enum>rightortop</enum>
      <enum>leftorbotton</enum>
    </tripwireDirection>
  </types>
  <tripwire>
    <switch type="boolean">false</switch>
    <alarmHoldTime type="uint32">20</alarmHoldTime>
    <objectFilter>
      <car>
        <switch type="boolean">true</switch>
        <sensitivity type="uint32" max="100" min="1" default="50">50</sensitivity>
      </car>
      <person>
        <switch type="boolean">true</switch>
        <sensitivity type="uint32" max="100" min="1" default="50">50</sensitivity>
      </person>
    </objectFilter>
    <lineInfo type="list" maxCount="4" count="1">
      <item>
        <direction type="tripwireDirection">rightortop</direction>
        <startPoint>
          <X type="uint32">10</X>
          <Y type="uint32">10</Y>
        </startPoint>
        <endPoint>
          <X type="uint32">1000</X>
          <Y type="uint32">1000</Y>
        </endPoint>
      </item>
    </lineInfo>
  </tripwire>
</config>

[Back to Top]

10.3 Face Detection

GetSmartVfdConfig

Retrieves the face detection configuration.

Notes:

• Face detection events are sent via HTTP POST when configured in Alarm Server settings
• Event type code: VFD (face detection) or VFD_MATCH (face match with database)
• Events include face crop image and full scene image (Base64 encoded)

[Back to Top]

10.4 License Plate Recognition (LPR)

GetSmartVehicleConfig

Retrieves the license plate recognition configuration.

Successful Response:

<?xml version="1.0" encoding="UTF-8"?>
<config version="2.0.0" xmlns="http://www.ipc.com/ver10">
  <types>
    <plateAreaType>
      <enum continent="NorthAmerica">U.S.A</enum>
      <enum continent="NorthAmerica">Canada</enum>
      <enum continent="Europe">Germany</enum>
      <enum continent="Europe">Britain</enum>
      <!-- Additional regions... -->
    </plateAreaType>
    <alarmListType>
      <enum>blackList</enum>
      <enum>whiteList</enum>
      <enum>strangerList</enum>
    </alarmListType>
  </types>
  <vehicle>
    <switch type="boolean">true</switch>
    <plateSencitivity type="uint8">49</plateSencitivity>
    <plateSupportArea type="plateAreaType">U.S.A</plateSupportArea>
    <saveTargetPicture type="boolean">true</saveTargetPicture>
    <saveSourcePicture type="boolean">true</saveSourcePicture>
    <dedupMode>
      <switch type="boolean">false</switch>
      <intervalTime type="uint32" default="5">5</intervalTime>
    </dedupMode>
    <regionInfo type="list" maxCount="1" count="1">
      <item>
        <X1 type="uint32">375</X1>
        <Y1 type="uint32">2866</Y1>
        <X2 type="uint32">9625</X2>
        <Y2 type="uint32">8800</Y2>
      </item>
    </regionInfo>
  </vehicle>
</config>

AddVehiclePlate

Adds license plates to the whitelist or blacklist.

Request Example:

<?xml version="1.0" encoding="utf-8"?>
<config>
  <vehiclePlates type="list" count="1">
    <item>
      <carPlateNumber type="string"><![CDATA[ABC1234]]></carPlateNumber>
      <beginTime type="string"><![CDATA[2024/01/01 00:00:00]]></beginTime>
      <endTime type="string"><![CDATA[2024/12/31 23:59:59]]></endTime>
      <carOwner type="string"><![CDATA[John Doe]]></carOwner>
      <plateItemType type="string">whiteList</plateItemType>
    </item>
  </vehiclePlates>
</config>

Notes:

• plateItemType can be whiteList, blackList, or strangerList
• beginTime and endTime set the validity period for the plate

GetVehiclePlate

Retrieves license plates from the database.

Request Example:

<config xmlns="http://www.ipc.com/ver10" version="2.0.0">
  <vehiclePlates type="list" maxCount="10000" count="1">
    <searchFilter>
      <item>
        <pageIndex type="uint32">0</pageIndex>
        <pageSize type="uint32">10</pageSize>
        <listType type="vehicleListTypes">allList</listType>
        <carPlateNum type="string"></carPlateNum>
      </item>
    </searchFilter>
  </vehiclePlates>
</config>

Notes:

• LPR events are sent via HTTP POST when configured in Alarm Server settings
• Event type code: VEHICLE or VEHICE (typo in some firmware)
• Events include plate number, plate image, and overview image (Base64 encoded)
• See Python API Server for parsing examples

[Back to Top]

10.5 Region Entry/Exit Detection

GetSmartAoiEntryConfig

Retrieves the region entry detection configuration.

GetSmartAoiLeaveConfig

Retrieves the region exit detection configuration.

Event Type Codes: AOIENTRY (region entry), AOILEAVE (region exit)

[Back to Top]

10.6 Target Counting

GetSmartPassLineCountConfig

Retrieves the target counting configuration.

GetPassLineCountStatistics

Gets current counting statistics.

Successful Response:

<?xml version="1.0" encoding="utf-8"?>
<config xmlns="http://www.ipc.com/ver10" version="2.0.0">
  <entranceCount>
    <person type="uint32">0</person>
    <car type="uint32">0</car>
    <bike type="uint32">0</bike>
  </entranceCount>
  <exitCount>
    <person type="uint32">0</person>
    <car type="uint32">0</car>
    <bike type="uint32">0</bike>
  </exitCount>
</config>

[Back to Top]

10.7 Video Metadata Detection

GetSmartVsdConfig

Retrieves the video metadata detection configuration. Video metadata detection identifies humans and vehicles in the scene and provides bounding box coordinates.

Event Type Code: VSD

[Back to Top]

10.8 Loitering Detection

GetSmartLoiteringConfig

Retrieves the loitering detection configuration. Triggers when a person remains in a defined area longer than the specified duration.

Event Type Code: LOITER

[Back to Top]

10.9 Illegal Parking Detection

GetSmartPvdConfig

Retrieves the illegal parking detection configuration. Triggers when a vehicle is parked in a prohibited zone.

Event Type Code: PVD

[Back to Top]

10.10 Thermal Imaging

GetMeasureTemperatureConfig

Retrieves the thermal imaging temperature measurement configuration (for thermal cameras only).

[Back to Top]

Event Type Code Reference

When receiving HTTP POST alarm events, use these codes to identify the event type:

10.11 Real-Time Target Object Tracking (traject)

The Viewtron IP camera has an advanced HTTP Post system called httpPostV2 that supports real-time target tracking of human objects and vehicle objects. When subscribed to the traject data type, the camera sends continuous HTTP Posts (~7 per second) with bounding box coordinates and target classification for the entire duration a target is being tracked in the detection zone.

This is fundamentally different from the alarm-based HTTP Post approach documented above. Alarm posts send one event when detection starts. httpPostV2 traject sends a continuous stream of tracking data — there are zero gaps while a target is present.

Comparison: Alarm Posts vs traject

Use cases:

• Relay/lighting control based on continuous human presence
• People/vehicle counting with real-time position tracking
• Dwell time analysis
• Custom alarm logic based on target position and movement

How httpPostV2 Works

httpPostV2 is a subscription system configured on the camera. You define:

1. Where to send — your server URL (up to 3 URLs supported)
2. Which events — detection types to subscribe to (PERIMETER, TRIPWIRE, MOTION, etc.)
3. Which data types — what kind of data to include in posts

Available data types

You can subscribe to multiple data types on the same URL. When all five are subscribed, traject posts start first (within the first frame of detection), followed by smartData with images, then alarmStatus.

Configuring httpPostV2

httpPostV2 is configured via the camera’s API using SetHttpPostConfig. It can also be configured in the camera’s web interface under Network > HTTP Post > Smart Track Data.

Get current config

POST or GET http://<camera-ip>/GetHttpPostConfig

Set traject subscription

<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0" xmlns="http://www.ipc.com/ver10">
<httpPostV2><postUrlConf>
  <urlList type="list" count="1"><item>
    <urlId>1</urlId>
    <switch>true</switch>
    <url>
      <protocol>http</protocol>
      <domain><![CDATA[YOUR_SERVER_IP]]></domain>
      <port>YOUR_PORT</port>
      <path><![CDATA[/API]]></path>
      <authentication>none</authentication>
    </url>
    <heatBeatSwitch>true</heatBeatSwitch>
    <keepaliveTimeval>90</keepaliveTimeval>
    <subscribeDateType type="list" count="1">
      <item>traject</item>
    </subscribeDateType>
    <subscriptionEvents type="list" count="1">
      <item>PERIMETER</item>
    </subscriptionEvents>
  </item></urlList>
</postUrlConf></httpPostV2>
</config>

Replace YOUR_SERVER_IP and YOUR_PORT with your API server’s address.

Available subscription events

ALL, MOTION, SENSOR, PERIMETER, TRIPWIRE, OSC, AVD,
AOIENTRY, AOILEAVE, PASSLINECOUNT, TRAFFIC, VSD, PVD, LOITER, ASD

traject XML Format

When a target enters the detection zone, the camera sends posts like this at ~7 per second:

<?xml version="1.0" encoding="UTF-8" ?>
<config version="1.7" xmlns="http://www.ipc.com/ver10">
  <types>
    <targetType>
      <enum>person</enum>
      <enum>car</enum>
      <enum>motor</enum>
    </targetType>
  </types>
  <subscribeOption type="subscribeRelation">FEATURE_RESULT</subscribeOption>
  <currentTime type="tint64">1774646121524166</currentTime>
  <mac type="string"><![CDATA[58:5b:69:5f:42:1b]]></mac>
  <sn type="string"><![CDATA[I421B0Z1173Q]]></sn>
  <deviceName type="string"><![CDATA[FaceCam]]></deviceName>
  <traject type="list" count="1">
    <item>
      <targetId type="uint32">434</targetId>
      <point>
        <x type="uint32">0</x>
        <y type="uint32">0</y>
      </point>
      <rect>
        <x1 type="uint32">6534</x1>
        <y1 type="uint32">2708</y1>
        <x2 type="uint32">7585</x2>
        <y2 type="uint32">6388</y2>
      </rect>
      <velocity type="uint32">0</velocity>
      <direction type="uint32">0</direction>
      <targetType type="targetType">person</targetType>
      <trajectlength type="list" count="0"/>
    </item>
  </traject>
</config>

traject fields

Each post is approximately 1.7 KB. Posts stop within ~140ms of the target leaving the detection zone.

NVR Compatibility

However, httpPostV2 traject works when the camera is connected to the NVR’s PoE port. You configure httpPostV2 directly on the camera’s firmware — the camera sends traject posts independently of the NVR. The NVR continues to handle recording and alarm events normally.

Recommended setup for full coverage:

1. Configure the NVR HTTP Post to your server — receives alarm events with images (v2.0 format, documented in NVR API Detection Events)
2. Configure the camera httpPostV2 to your server with traject subscribed — receives real-time tracking (v1.x format)
3. Your server receives both streams

Firmware Compatibility

httpPostV2 traject has been confirmed working on IPC firmware 5.1.4.0 (API protocol v1.7). Other Viewtron AI camera models with perimeter detection should support httpPostV2 as well.

The GetHttpPostConfig endpoint will show whether your camera supports httpPostV2. If the response includes an httpPostV2 element, the feature is available.

Python API Server

Our open source Python API server on GitHub handles httpPostV2 traject posts alongside the standard alarm events. The server auto-detects the post type and processes it accordingly.

For questions about httpPostV2 or the API server, contact Mike at mike@cctvcamerapros.net.

Back to API Documentation Index

Here’s how to change your Channel Layout of your HDMI Decoder to optimize your view.

In this example, we only want to view 2 streams at once. However, we have a ton of dead space below our monitor where we aren’t using the 3rd and 4th streaming channel.

Right now our setup looks like this:

Once we’re finished, it will look like this:

————————————————————————————————————————————————-

First, log into your IP Decoder using your preferred web browser. The IP, username, and password of the Decoder is on the silver sticker on top of the unit.

Once logged in, go to the Stream address setting window to change the number of channels to 2 (or however many you want in this case). Then, hit Apply.

Now, go to the Advanced Setting tab and select Channel Layout. Here, you can adjust the windows of each channel by clicking the box in the corner. Be sure to Enable Video Channel Layout at the top of your screen. Adjusting the aspect ratio here will reduce stretching/squishing.

You can also move the position of the window by clicking in the center and dragging.

Finally, hit Apply and your settings will be saved.

Now, our picture is clearer!

1. Motorized Zoom Is Far More Convenient

Motorized zoom cameras allow you to adjust zoom and focus remotely through the camera’s interface or NVR/DVR. There’s no need to climb a ladder or physically open the camera housing.

If the field of view needs to be changed later, adjustments can be made in minutes from anywhere.

Motorized zoom cameras also have Auto-focus. This removes the hassle of adjusting focus entirely.

2. Varifocal Lenses Are Hard to Fine-Tune

Manual varifocal cameras require physical adjustment of both zoom and focus rings. These controls are extremely sensitive, and even slight movements can throw the image out of focus.

Installers often have to make repeated micro-adjustments to get the image just right, which can be time-consuming and frustrating.

3. The Cost Difference Is Minimal

In the past, motorized zoom cameras were significantly more expensive. Today, that price gap has largely disappeared due to technological progression.

For a small difference in price, motorized zoom cameras provide much greater flexibility and ease of use. This makes them the smarter long-term choice.

Video Demo

Here’s a good video where Mike goes over the motorized zoom capabilities of the IP-A8DZ, one of our most popular motorized-zoom cameras.

If youre configuring a Viewtron NVR or Hybrid DVR for remote access or custom network settings and can’t select the correct Ethernet interface (Ethernet Port 1), there’s a simple setting that may be causing the issue:

First, go to the Network page.

Once in the Network menu, go to PPPoE.

Make sure that the check-box is Disabled, and then click Apply.

Now, go back to the TCP/IP page. Enabling and Disabling PPPoE may clear your TCP/IP network settings, so be sure to re-enable Obtain an IP Address Automatically. If you are using a custom network setup you can skip Step 3 on the chart and use your own custom settings.

What is PPPoE?

• PPPoE (Point-to-Point Protocol over Ethernet) is a method that allows a device to connect to an ISP using a username and password over an Ethernet connection.

• It is commonly used by DSL and some fiber providers that require authentication to access the internet.

• In most networks, the router handles PPPoE, so individual devices (like NVRs or DVRs) do not need it enabled.

If Enabled:

• The recorder locks certain manual network configuration options.

• The TCP/IP interface selection becomes restricted.

• Ethernet Port 1 may be unavailable or greyed out in the TCP/IP menu.

Most installations do not require PPPoE because the router handles the internet authentication, not the recorder.

The reason that you are seeing the  “The Device Resource Is Limited” message when you try to enable line crossing detection is because you must already have another type of AI event already enabled on that camera – most likely intrusion detection.

Although Viewtron AI cameras support multiple types of AI detection events, sometimes you can not enable more than one. Also, sometimes you can enable more than one, but you are forced to lower the recording resolution of that camera in to free up processing resources. Please disable the other AI detection type that you have enabled if you want to enable line crossing detection.

You do this by going into the AI / Event section on the Viewtron NVR (refer to the above screenshot).

1. Select the camera from the Camera Name Field.
2. Select each of the AI detection types and uncheck the “Enable Detection by IPC” check box for each type that you are not using. E.G. Line Crossing, Region Intrusion, Region Entrance, Region Exiting
3. Click Apply in the lower right as you uncheck each one.

You can watch video demos of all of the different AI software functions that Viewtron IP cameras support here.

Intrusion Detection

• Detection Area: Uses a polygon-shaped zone to define the area of interest.
• Trigger Mechanism: An alarm is triggered when a human or vehicle enters or exits the defined intrusion zone at any location.
• Use Case: Suitable for monitoring a specific area where any entry or exit is considered a security event.

Line Crossing Detection

• Detection Area: Involves drawing one or more virtual tripwires (lines) on the scene being monitored.
• Trigger Mechanism: An alarm is triggered when a human or vehicle crosses the line in a specified direction (e.g., A->B, B->A, or both directions A<->B).
• Use Case: Ideal for monitoring specific entry or exit points, such as a parking lot entrance or a walkway, where crossing a line in a particular direction is significant.

Both methods can be applied to human detection and vehicle detection. And both can trigger alarms, video recording, push notifications, and other actions, but the key difference lies in how the detection area is defined and the type of movement being monitored.

You can watch video demos of all of the different AI software functions that Viewtron IP cameras support here.