Choose one Axis HTTP audio source addressing method

Bottom line: Choose one audio-source addressing method for each HTTP media request. Keep source selection and audio enablement visible in the request review before troubleshooting codecs, players or the network.

Source fact: documented behavior

Axis’s Media stream over HTTP documents media retrieval through /axis-cgi/media.cgi, with Matroska or MP4 containers carrying video and audio.

The audiochannel option cannot be used together with audiodeviceid and audioinputid; the device and input options likewise cannot be used with audiochannel.

For audio inclusion, the documented audio option also requires audio support to be enabled for the source with AudioSource.A#.AudioSupport=yes.

What the source does not establish

Do not infer that a selected input is the intended microphone or that audible playback proves an authorized recording policy. Confirm the exact device and supported source identifiers. Keep audio privacy, retention and permission decisions with the responsible owner. Do not copy source example addresses or credentials into an operating request.

Applicability questions

• Which physical or logical audio source should this authorized consumer receive?
• Will the request use the channel form or device/input identifiers?
• Is source audio support enabled through the device’s supported configuration?
• Which player, container and permitted listening position will be used for acceptance?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends reviewing audio selection as a small, explicit request contract before changing unrelated media settings.

1. Obtain the intended source identity through the exact product’s supported information. Record the request template without credentials, including the chosen addressing form, desired audio inclusion and container. Remove inherited options from the other addressing form rather than leaving both in a long copied URL. Ask the audio owner to confirm the intended source and approved test material.
2. Use an authorized test environment and a harmless, identifiable audio input. Request the stream with the chosen form and record the actual request and response. Check both the selected source and whether audio is present in the consumer. For a comparison case, use an approved video-only request and label its expected difference. Avoid changing gain, encoding and network policy simultaneously.
3. If the selected stream lacks the required audio, inspect the request’s addressing consistency and the documented source-enable requirement before expanding the investigation. Verify identifiers against the device instead of substituting numbers until something plays. Keep a separate entry for a rejected request, a wrong source and an audio-enable mismatch so the corrective action addresses the observed problem.

Verification and evidence

Retain the sanitized request template, source-identity reference, relevant enablement setting, consumer version and a permitted observation record. Where recording a sample is authorized, keep only the minimum sample needed for the test. Have the source owner confirm which input was heard; do not close the check from a moving level indicator alone.

For later client changes, review the complete emitted request again for mixed addressing forms. Repeat the selected-source and audio-presence checks before adopting a copied media profile. Record the proposed cases and actual outcomes separately; this article supplies no device-specific compatibility or successful playback result.

Official references

• Media stream over HTTP — Axis Communications; official VAPIX documentation.

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.