Replies: 2 comments
-
|
Resolved this ourselves with a custom patch to the ONVIF plugin. Root cause: Axis A8004-VE has no ONVIF Profile T / backchannel support at all (firmware limitation). The RTSP server returns 551 unconditionally. Solution: Patched One-way audio (doorbell mic → phone) works via the standard ONVIF RTSP stream after adding an audio encoder to the H264 profile. For anyone hitting this with other Axis cameras: the VAPIX |
Beta Was this translation helpful? Give feedback.
-
|
Hey @patikoija - care to share the edits you made to use transmit.cgi? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Axis A8004-VE doorbell does not support ONVIF Profile T backchannel (
www.onvif.org/ver20/backchannel). The camera's GStreamer RTSP server returns551 Option not supportedwhen the DESCRIBE request includesRequire: www.onvif.org/ver20/backchannel. This is a firmware limitation (firmware 1.65.14, latest available).One-way audio (doorbell mic → phone speaker) works correctly after adding audio encoder to the ONVIF H264 profile. Only the talkback direction (phone mic → doorbell speaker) is broken.
Camera Details
http://www.onvif.org/ver10/media/wsdl) — no Media 2 / Profile Troot.Audio.DuplexMode=full)What the camera DOES support for talkback
VAPIX HTTP audio push (tested — endpoint accepts connections):
Axis RTSP simplex=receiver (tested — DESCRIBE returns SDP):
Requires ANNOUNCE→SETUP→RECORD flow (not DESCRIBE→SETUP→PLAY)
Suggested Fix
When
checkIntercom()fails with "ONVIF audio backchannel not found", fall back to:A plugin setting like "Two-Way Audio URL override" (similar to how some NVRs allow specifying a custom talkback RTSP URL) would be a general solution for cameras that support non-standard talkback methods.
Logs
Camera RTSP response:
Beta Was this translation helpful? Give feedback.
All reactions