VIVOTEK
User's Manual - 389
© 2020 VIVOTEK INC. All Right Reserved
258
-------------------------------------------------------------------------
GET /cgi-bin/admin/ctrlevent.cgi
x-sessioncookie: string[22]
accept: application/x-vvtk-tunnelled
pragma: no-cache
cache-control: no-cache
-------------------------------------------------------------------------
POST /cgi-bin/admin/ ctrlevent.cgi
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
© 2020 VIVOTEK INC. All Right Reserved
259
network_rtsp_s2_accessname = live2s1.sdp
network_rtsp_s3_accessname = live2s2.sdp
etc.
* Note: RTSP access name format is modified to “live<n>s<m>.sdp” after version
number(httpversion) is 0311c.
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.
8.14
Open the Network Stream
Note:
This request requires Viewer access privileges.
Syntax:
For HTTP push server (MJPEG):
http://<
servername
>/<network_http_s<0~m-1>_accessname>
For RTSP (MP4), the user needs to input theURL below into an RTSP compatible player.
rtsp://<
servername
>/<network_rtsp_s<0~m-1>_accessname>
“m” is the stream number.
For details on streaming protocol, please refer to the “control signaling” and “data format”
documents.
8.15
Send Data
(capability_nuart > 0)
Note:
This request requires Viewer privileges.
Method:
GET/POST
Syntax:
http://<
servername
>/cgi-bin/viewer/senddata.cgi?
[com=<value>][&data=<value>][&flush=<value>] [&wait=<value>] [&read=<value>]
PARAMETER
VALUE
DESCRIPTION
com
1 ~ <max. com port
number>
The target COM/RS485 port number.