Loading ...
Loading ...
Loading ...
VIVOTEK
User's Manual - 373
servername
© 2022 VIVOTEK INC. All Right Reserved
229
x-sessioncookie: string[22]
content-type: application/x-vvtk-tunnelled
pragma : no-cache
cache-control : no-cache
content-length: 32767
expires: Sun, 9 Jam 1972 00:00:00 GMT
User must use GET and POST to establish two channels for downstream and upstream. The x-
sessioncookie in GET and POST should be the same to be recognized as a pair for one session. The
contents of upstream should be base64 encoded to be able to pass through the proxy server.
This channel will help perform real-time event subscription and notification as well as camera
control more efficiently. The event and control formats are described in another document.
See Event/control tunnel spec for detail information
8.13 Get SDP of Streams
Note: This request requires Viewer access privileges.
Method: GET/POST
Syntax:
http://<servername>/<network_rtsp_s<0~(n*m)-1>_accessname>
n denotes the value of "capability_nvideoin", m denotes the value of "capability_nmediastream".
Example:
For m=2, the values are shown as
network_rtsp_s0_accessname = live1s1.sdp
network_rtsp_s1_accessname = live1s2.sdp
network_rtsp_s2_accessname = live2s1.sdp
network_rtsp_s3_accessname = live2s2.sdp
etc.
* For version number(httpversion) above 0311c, the default RTSP access name format is
“live<n>s<m>.sdp”. Please refer to the “subgroup of network: rtsp” for setting the accessname of
SDP.
* You can get the SDP by HTTP GET.
* When using scalable multicast, Get SDP file which contains the multicast information via HTTP.
Note:
* We recommend to use new format to access streaming when
capability_media_streamprofiles_support=1, please refer to
Methods for Accessing Streaming
Loading ...
Loading ...
Loading ...