Documentation for Axxon Next 4.4.6. Documentation for other versions of Axxon Next is available too.

Previous page Get list of video sources (cameras)  Get high and low quality streams Next page

On page:

Important!

You can get audio from x64 Server only.

You can't get audio in MJPEG format.

General information

GET http://IP-Address:port/prefix/live/media/{VIDEOSOURCEID}

{VIDEOSOURCEID} - three-component source endpoint ID (see Get list of video sources (cameras)).  For instance, "SERVER1/DeviceIpint.3/SourceEndpoint.video:0:0".

Important!

If no parameters are specified in the request, then the video will be received in the MJPEG format.

ParameterRequiredDescription
formatNo

The "mp4" player allows to receive the original video in H.264 and H.265. In all other cases the server recompresses it to MJPEG format.  

  • Important!

    If video is requested in the format that differs from the original one, then recompression will be performed, therefore, Server load will increase.

w, hNo

w – frame width, h – frame height.

Note

If h and w values are more than size of original video, the video will be received with original size.

Zooming out of width and height is available only discretely - in 2, 4, 8 times, etc. If specified sizes are not corresponding to 1/2, 1/4 etc. of original video size, the video will be received with size divisible by the original video size close to specified values.

Important!

The mp4 video is transferred without scaling.

frNo

fps.

Important!

This parameter is relevant only for MJPEG video.

enable_token_auth No

Get signed links to video streams.

enable_token_auth - enable authorization by token =1.

valid_token_hours - signature validation time (in hours). The maximum value is a week. The default value is 12 hours.

valid_token_hoursNo


Sample request:

GET http://IP-Address:port/prefix/live/media/Server1/DeviceIpint.23/SourceEndpoint.video:0:0?w=640&h=480&enable_token_auth=1&valid_token_hours=1

RTSP video

RTSP protocol video is sent in the original format only.

Request to get the structure of the RTSP link: http://login:password@IP-address:Port/live/media/Server1/DeviceIpint.23/SourceEndpoint.video:0:0?format=rtsp

Sample response:

{
    "http": {
        "description": "RTP/RTSP/HTTP/TCP",
        "path": "hosts/Server1/DeviceIpint.23/SourceEndpoint.video:0:0",
        "port": "8554"
    },
    "rtsp": {
        "description": "RTP/UDP or RTP/RTSP/TCP",
        "path": "hosts/Server1/DeviceIpint.23/SourceEndpoint.video:0:0",
        "port": "554"
    }
}

Request to get video: GET rtsp://login:password@IP-address:554/hosts/Server1/DeviceIpint.23/SourceEndpoint.video:0:0

Attention!

In some cases, the RTSP video can be streamed with artifacts. To fix this, change the TCP/IP settings using this reg file.

HTTP video

ffplay.exe -v debug "http://login:password@IP-address:8001/live/media/Server1/DeviceIpint.23/SourceEndpoint.video:0:0?w=1600&h=0"

Important!

HTTP sends video in mjpeg only, w and h parameters are mandatory.

Tunneling RTSP over HTTP

see Configure tunneling RTSP over HTTP in VLC

Video is sent over the tunnel in the original format.

Sample request:

ffplay -rtsp_transport http "rtsp://login:password@IP-Address:80/rtspproxy/hosts/Server1/DeviceIpint.23/SourceEndpoint.video:0:0"

GET for VLC: rtsp://login:password@IP-Address:80/rtspproxy/hosts/Server1/DeviceIpint.23/SourceEndpoint.video:0:0

H.264 and H.265 video

To get live video in the original H.264/H.265 format use mp4 format.

Sample request:

ffplay.exe "http://root:root@192.168.25.112:8001/live/media/Server1/DeviceIpint.61/SourceEndpoint.video:0:0?format=mp4"


  • No labels