Vivotek

Vivotek Audio Not Working? Enterprise Fix Guide

Fix Vivotek audio issues in enterprise settings with step-by-step guidance using VAST Security Station and brand-specific tools. Enterprise-grade solutions for IT professionals.

Is this your issue?

Camera shows **offline in VMS dashboard** but responds to **ping**
RTSP stream drops **intermittently** despite stable network link
PoE negotiation fails — switch port shows **Class 0** instead of **Class 3**
Firmware update **stuck in pending state** in the management platform
Audio is disabled in **VAST Security Station** despite being enabled in **camera settings**
VMS logs show **codec mismatch** for **G.711** or **G.722**
Shepherd diagnostics report **audio=0** for the camera

Sound familiar? The guide below will help you fix it.

Confirm Vivotek Audio Failure in Enterprise Environment

Your Vivotek camera is reporting audio failure despite stable network connectivity. This typically stems from audio codec mismatches, disabled microphone/speaker toggles, or VMS integration misconfigurations. The solution requires brand-specific tools like VAST Security Station and Shepherd diagnostics. Proceed with the following structured approach to isolate the issue.

Quick Fixes for Vivotek Audio Issues

Perform these immediate checks before diving into advanced diagnostics:

Check VAST Dashboard: In VAST Security Station, navigate to Cameras → [Device] → Status and confirm Audio is marked as Enabled. If disabled, toggle the Microphone and Speaker switches.
Verify PoE Link Light: Ensure the switch port connected to your FD9391-EHTV or IB9391-EHT shows a green PoE Class 3 light. A Class 0 status indicates PoE negotiation failure.
Ping Camera IP: Open a terminal and execute ping [camera_ip]. If the camera responds but audio fails, the issue lies in VMS integration or codec settings.

Verify VAST Security Station Network Configuration

Check VLAN Assignment

Open VAST Security Station and navigate to Network → VLAN Configuration.
Locate your camera's VLAN ID and ensure it matches the switch port's VLAN configuration.
Confirm IGMP Snooping is disabled for the camera's VLAN. If enabled, disable it in the switch's VLAN Settings.
Use Shepherd diagnostics to verify the camera is receiving the correct IP address within the assigned VLAN.

Validate PoE Budget

Access your managed switch via CLI and run show power inline [port] to check PoE power consumption.
Confirm the camera's PoE Class 3 requirement is met. If the switch port shows Class 0, reconfigure the port to 802.3af or 802.3at.
Ensure the PoE budget on the switch is not exhausted. If multiple cameras are connected, redistribute power or use a PoE Injector for the affected device.

Diagnose VAST Security Station Audio Settings

Confirm Microphone/Speaker Enable Toggle

In VAST Security Station, open the camera's Configuration → Audio Settings menu.
Ensure both Microphone and Speaker are enabled. If disabled, toggle the switches and save changes.
Restart the camera via VAST → Device Management → Power Cycle to apply the changes.

Validate Audio Codec Compatibility

Navigate to VAST → Stream Profiles for the camera.
Check the Audio Codec dropdown and ensure G.711 is selected. If using ONVIF Profile S, this is the default setting.
If the VMS is using a different codec (e.g. G.722), update the camera's Audio Codec to match via VAST → Audio Settings.

Troubleshoot VMS Integration with Vivotek

Re-Register Camera in VMS

In your VMS platform (e.g. MxManagementCenter), locate the affected camera and initiate a Re-Registration.
Ensure the RTSP Stream URL includes the audio=1 parameter. Example: rtsp://[camera_ip]:554/cam/realtime?audio=1.
Verify the VMS license includes audio support for the camera model. If not, contact your VMS vendor for an upgrade.

Check VMS Database Consistency

Access the VMS database via SQL Management Studio and run a database integrity check for the camera's record.
If inconsistencies are found, perform a database repair using the VMS vendor's tools.
Re-sync the camera with the VMS by exporting the camera's RTSP stream and re-importing it into the VMS platform.

Advanced Diagnostics with VAST Tools

Use Shepherd Device Discovery

Launch Shepherd on your management PC and scan for Vivotek devices on the network.
Select the affected camera and review the Device Health tab for audio-related errors (e.g. codec mismatch, disabled microphone).
If audio=0 is reported, update the camera's RTSP stream URL in VAST → Stream Profiles to include audio=1.

Analyse VAST System Logs

Open VAST Security Station and navigate to Support → System Logs.
Filter logs for the camera's Serial Number and look for entries containing audio, codec, or stream failure.
If the log shows RTSP stream dropped, verify the VMS port matches the camera's RTSP Port setting in VAST → Network → RTSP Configuration.

Support Escalation Path

Initiate RMA Process

Access VAST → Support → RMA Request and input the camera's Serial Number (found in System Info).
Attach the VAST System Log, Shepherd Diagnostic Report, and VMS Integration Settings.
Contact Vivotek Enterprise Support via the Support Portal and select Priority Tier 2 for urgent audio failures.

Root Causes of Vivotek Audio Failures

Enterprise-Specific Issues

PoE Budget Exhaustion: Ensure the PoE switch has sufficient headroom for the FD9391-EHTV or IB9391-EHT camera. A Class 0 status indicates insufficient power.
VMS Licensing Conflicts: Verify the VMS license includes audio support for the camera model. If not, upgrade the license or contact the VMS vendor.
Firmware Incompatibility: Ensure the camera is on the Stable Firmware Channel in VAST → Firmware Management. Avoid Beta Channels for production devices.
UK-Specific Considerations: For pre-1920s terraced houses, confirm the VMS server is on the same VLAN as the camera. Use dedicated camera VLANs to avoid 2.4GHz WiFi degradation from low-E windows.

Vivotek Audio Preventive Maintenance Guide

Enterprise Network Best Practices

Schedule VAST Firmware Updates quarterly using Staged Rollouts in VAST → Deployment.
Configure QoS Policies for Vivotek cameras to prioritise audio streams over video.
Use SNMP Monitoring on the managed switch to track PoE power usage and VLAN assignments.

Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.

Is It Time for a Vivotek Audio Upgrade? for Vivotek Cameras

Camera Lifecycle Management

Wired Camera Lifespan: 5–8 years typical. Replace FD9391-EHTV or IB9391-EHT models if sensor degradation or firmware EOL is detected.
NVR HDD Lifespan: 3–5 years for WD Purple/Seagate SkyHawk drives. Replace if RAID parity checks fail.
UK Procurement Considerations: Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods. If troubleshooting exceeds 30 minutes and basic fixes fail, hardware replacement is likely required.

What if this wasn't your problem to solve?

scOS detects suspicious activity — not motion. It only alerts you when something matters, like a person would. Designed to be left alone. All features included.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No feature tiers. Hub included, from £10/month. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

Network misconfigurations are a common root cause. Verify that the camera is assigned to the correct VLAN in VAST Security Station under Network → VLAN Configuration. Ensure the VLAN is permitted on the switch and that IGMP Snooping is disabled. If the camera is on a different subnet than the VMS, configure static IP routing in the switch. Use Shepherd diagnostics to confirm the camera is receiving the correct IP address and that PoE Class 3 is negotiated. If VLAN assignment is correct, check for DHCP exhaustion by reviewing lease times in the VAST System Health Check dashboard.

Verify VAST Security Station integration settings for the affected camera. Navigate to Cameras → [Device] → Audio Settings and confirm Microphone and Speaker are enabled. Check the Audio Codec dropdown for compatibility with the VMS platform. If using ONVIF Profile S, ensure G.711 is selected. If the camera is registered to a different VMS instance, re-register it via VAST → Device Management → Re-Register. Confirm the RTSP stream URL in VAST → Stream Profiles includes the audio=1 parameter. If the VMS is using a different port, update the RTSP Port setting in the camera's Network → RTSP Configuration menu.

Access VAST → Firmware Management to check the camera's firmware channel. Ensure it's set to Stable unless troubleshooting a known issue. If a firmware update is pending, initiate a Staged Rollout via VAST → Deployment → Firmware Update. Avoid using Beta Channels for production devices. If a rollback is required, navigate to VAST → Device Management → Firmware Rollback and select the previous version. Confirm Firmware Compatibility with the camera model in the VAST Compatibility Matrix. If the update fails, check the VAST System Log for errors related to firmware signature verification.

For enterprise support escalation, access VAST → Support → RMA Request and provide the Serial Number from the camera's System Info menu. Include the VAST System Log, Shepherd Diagnostic Report, and VMS Integration Settings. Contact Vivotek Enterprise Support via the Support Portal and select Priority Tier 2 for urgent audio failures. Provide the Camera Model, Firmware Version, and VMS Platform (e.g. MxManagementCenter) in the support ticket. If the issue persists after 24 hours, request a Remote Session with Vivotek engineers using the VAST Remote Diagnostics Tool.

All Troubleshooting Guides