Avigilon H4 audio support
Answered
Good morning.
We have an Avigilon 20C-H4A-4MH-360 running on N Witness v4.0, but struggling to get audio output at all on the camera. According to the below, it is fully compatible and tested.
https://nxvms.com/ipvd?vendors=Avigilon&search=H4&camera=20C-H4A-4MH-360
The camera is enabled and set on G.711, but no line level signals are given from NX Witness.
-
I have added a Hik camera to the system and have full audio support.
I have also tested the output from the Avigilon camera by hooking it up to a Hik NVR via ONVIF, and works fine, paging from the Hik app via the NVR to the camera, so I know there is no physical or connection issue.
Any one else got issues with audio on Avigilon cameras?
0 -
Hi Gordon,
Did you try other codecs as well?
Also, could share the XML output when you run the Diagnostics the device with the Onvif Device Test Tool?
0 -
thanks Norman
The only other codec available on the camera is Opus, which doesn't work either
Please advise how I run diagnostics (I have Onvif Device Manager installed)
0 -
Hi Gordon,
You can't run the diagnostics with the Onvif Device Manager, you need the Onvif Device Test tool.
After starting OTT, go to "Diagnostics" tab
Choose "Test cases" from tabs on the left of the window.Select needed test cases from tree view
Make sure that other tests cases are not selected since its execution can take a long time.Press "Run selected" button.
Wait while tests are running. You can stop running tests at everytime with buttons "Stop"/"Halt"On the right half of the window you can see detailed information about highlighted test case: passed and failed steps, requests that were sent on this step and responses to those requests.
Optionally you can save information about testing session in XML format using "Save" button.
Very likely 2-way audio works with Onvif, if at least one of of the above line is green( like on screenshot).
Please share the XML output aft the diagnosis.
0 -
thanks. Please advise where I can download the Onvif Device Test tool
0 -
Hi Gordon,
Unfortunately this is not a tool we can provide since it is a proprietary application from the Onvif organization. The software should be requested from the Onvif organization. That being said, there are quite a few downloads available which can be found through your favourite search engine and downloaded with common sense.
0 -
OK, I've managed to get hold of v17.01 version. I've run a test under Media Configuration > audio configuration. Results are here: https://anchorsound.sharepoint.com/:u:/g/Ee-ftC2QJNRJtvKsj2kO1kEB-wL4_mhAr35Yxt8gPCj1Kg?e=EPLcyE
I have tested the 've also tested with another Avigilon camera, a 2.0MP H5 SL WDR, and I have the same issue it appears: works when connected via ONVIF to a Hikvision NVR, but fails to give audio output when connected to NX witness. I have also installed another complete independent NX VMS on a separate machine to test, and same issue.
Unless I'm doing something wrong on the VMS? I have Hik cameras and an Axis horn speaker already working.
0 -
Hi Gordon,
It seems that the cameras aren't fully Onvif compliant and I get quite a few HTTP 1.1 Bad Request notifications which basically tells you something is wrong.
Hikvision probably made a workaround that enables them to list them as Onvif, but adds audio for Avigilon devices.
I would check if there is newer firmware available for the cameras and then try again, since it unexpected that a company with the decent reputation like Avigilon wouldn't be fully compliant as a full Onvif member.
I will list the Bad Requests below as feedback for Avigilon.
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SetAudioOutputConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<Configuration token="M" tavg:ChangeNumber="30" tavg:ChangeSessionId="24339_3630" xmlns:tavg="http://www.avigilon.com/onvif/ver10/avigilon-types">
<Name xmlns="http://www.onvif.org/ver10/schema">spkCfg0</Name>
<UseCount xmlns="http://www.onvif.org/ver10/schema">2</UseCount>
<OutputToken xmlns="http://www.onvif.org/ver10/schema">spk0</OutputToken>
<OutputLevel xmlns="http://www.onvif.org/ver10/schema">100</OutputLevel>
</Configuration>
<ForcePersistence>false</ForcePersistence>
</SetAudioOutputConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2367<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SetAudioOutputConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<Configuration token="spkCfg0">
<Name xmlns="http://www.onvif.org/ver10/schema">spkCfg0</Name>
<UseCount xmlns="http://www.onvif.org/ver10/schema">0</UseCount>
<OutputToken xmlns="http://www.onvif.org/ver10/schema">z</OutputToken>
<SendPrimacy xmlns="http://www.onvif.org/ver10/schema">http://someuri</SendPrimacy>
<OutputLevel xmlns="http://www.onvif.org/ver10/schema">101</OutputLevel>
</Configuration>
<ForcePersistence>false</ForcePersistence>
</SetAudioOutputConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2362<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SetAudioSourceConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<Configuration token="micCfg0" tavg:ChangeNumber="11" tavg:ChangeSessionId="24339_3630" xmlns:tavg="http://www.avigilon.com/onvif/ver10/avigilon-types">
<Name xmlns="http://www.onvif.org/ver10/schema">Line in</Name>
<UseCount xmlns="http://www.onvif.org/ver10/schema">2</UseCount>
<SourceToken xmlns="http://www.onvif.org/ver10/schema">InvalidToken</SourceToken>
</Configuration>
<ForcePersistence>false</ForcePersistence>
</SetAudioSourceConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2362<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SetAudioEncoderConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<Configuration token="micEncCfg0" tavg:ChangeNumber="5" tavg:ChangeSessionId="24339_3630" xmlns:tavg="http://www.avigilon.com/onvif/ver10/avigilon-types">
<Name xmlns="http://www.onvif.org/ver10/schema">micEncCfg0</Name>
<UseCount xmlns="http://www.onvif.org/ver10/schema">2</UseCount>
<Encoding xmlns="http://www.onvif.org/ver10/schema">G711</Encoding>
<Bitrate xmlns="http://www.onvif.org/ver10/schema">64</Bitrate>
<SampleRate xmlns="http://www.onvif.org/ver10/schema">9</SampleRate>
<Multicast xmlns="http://www.onvif.org/ver10/schema">
<Address>
<Type>IPv4</Type>
<IPv4Address>224.3.3.5</IPv4Address>
</Address>
<Port>30004</Port>
<TTL>1</TTL>
<AutoStart>false</AutoStart>
</Multicast>
<SessionTimeout xmlns="http://www.onvif.org/ver10/schema">PT60S</SessionTimeout>
</Configuration>
<ForcePersistence>false</ForcePersistence>
</SetAudioEncoderConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2355<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<GetAudioSourceConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<ConfigurationToken>T</ConfigurationToken>
</GetAudioSourceConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2367<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<GetAudioSourceConfigurationOptions xmlns="http://www.onvif.org/ver10/media/wsdl">
<ProfileToken>8</ProfileToken>
</GetAudioSourceConfigurationOptions>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2362<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<GetAudioSourceConfigurationOptions xmlns="http://www.onvif.org/ver10/media/wsdl">
<ConfigurationToken>2</ConfigurationToken>
</GetAudioSourceConfigurationOptions>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 2367<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SetAudioSourceConfiguration xmlns="http://www.onvif.org/ver10/media/wsdl">
<Configuration token="2">
<Name xmlns="http://www.onvif.org/ver10/schema">Line in</Name>
<UseCount xmlns="http://www.onvif.org/ver10/schema">2</UseCount>
<SourceToken xmlns="http://www.onvif.org/ver10/schema">mic0</SourceToken>
</Configuration>
<ForcePersistence>false</ForcePersistence>
</SetAudioSourceConfiguration>
</s:Body>
</s:Envelope></Request>
<Response>HTTP/1.1 400 Bad Request
Server: AvigilonOnvifNvt/3.30.0.28
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 23670 -
OK, thanks.
But the Avigilon cameras work when connected to a Hik NVR? Is there an easy way we can fix this one on the NX side? The cameras are all on the latest firmware.
0 -
Hi Gordon,
As said:
>>>Hikvision probably made a workaround that enables them to list them as Onvif, but adds audio for Avigilon devices.
We do not believe in circumventing issues, but in solving issues, especially in the case when there is standard in place; Onvif.
Since Avigilon is a full member of Onvif and it is therefore reasonable to be expected that their devices should be Onvif compliant the issue should be addressed to Avigilon.
0 -
OK, I understand your position. Will try and see what I can get out of Avigilon.
0 -
Norman
Can you confirm how the checks on the supported cameras are made please. The Avigilon20C-H4A-4MH-360 is listed as being supported on two-way audio for the relevant
firmware release and we took it in good faith that this was correct. How do we ensure that this doesn't happen the next time round?0 -
Gordon,
In case of the Avigilon cameras or any other Onvif compliant camera is works as follows;
Our systems are auto-reporting, that means when there is a black dot, the function is used on at least 3 independent systems.
An open dot means that it isn't supported and a '?' means that the camera reports a certain function, but no one used it before.This seems odd in case of PTZ, but for PTZ we also require that people have set up presets to assure the controls are accurate.
What could be the case is that the function was supported in an older firmware version, but has been changed over time.
0 -
Norman
OK (the 20C-H4A-4MH-360 is actually a multisensor camera)
As mentioned above, the issue is also extant on an Avigilon H5L camera (the H5SL range is shown as a supported device on firmware 3.30 which we are using), which we have tested on fresh NX witness install without success.
0
Please sign in to leave a comment.
Comments
14 comments