Axis RTSP setup: H.264 URLs, profiles and accounts

Confirm the device's services

Axis's getting-started instructions require RTSP to be active and an administrator to check the camera. They also describe API discovery because available APIs differ between devices. Record the model and AXIS OS version before relying on a current API example for an older camera.

Our compatibility notes distinguish this manufacturer evidence from playback tested in CameraViewer. A documented endpoint helps prepare a connection; testing still needs the exact camera, firmware and selected stream.

Start with one explicit stream request

Axis's VAPIX streaming documentation shows /axis-media/media.amp with the videocodec=h264 parameter:

rtsp://CAMERA_IP/axis-media/media.amp?videocodec=h264

Replace CAMERA_IP with the reachable device address and authenticate using device credentials. Check the configured RTSP service rather than treating the omitted port in this example as a guarantee about your installation.

For supported devices, streamprofile=PROFILE_NAME selects a saved profile and camera=NUMBER selects a video source. Check which profiles and sources exist before adding them. The same documentation scopes available settings by device.

Keep the first URL simple. Adding a profile name, source number and resolution together makes a rejected request harder to diagnose. The RTSP setup guide explains the difference between the host, path and query parameters.

Check profiles and account types in the model manual

The AXIS Q1645 manual describes stream profiles with codec, resolution and frame-rate settings. It also describes separate ONVIF accounts: creating one activates ONVIF communication, and that account supplies the credentials for it. These are Q1645 instructions, so check your own manual's menus before making changes.

Keep the RTSP account and any ONVIF account labeled in your private notes. If a later connection fails, the labels make it easier to check whether you supplied the account meant for that service. The ONVIF setup guide covers the distinction between discovery, authentication and live video.

Work from the simplest reproducible failure

If the camera rejects a profile request, return to the simple URL and compare the saved profile name with your notes. If the wrong source appears, confirm the source number from the device. If there is no connection at all, check the address and RTSP service before changing video settings.

A successful sign-in followed by missing video calls for a stream-settings check. Record the requested codec, selected profile and exact symptom. CameraViewer has demonstrated H.264 fixture decoding and manual RTSP entry; physical Axis camera playback remains unverified. That evidence cannot promise support for every Axis codec or authentication setting.

Use the connection troubleshooting guide to keep the next attempt focused. Preserve the original settings so you can return to a known starting point after each change.

For the manufacturer reference and documented URL examples, return to the Axis connection resource.