0% found this document useful (0 votes)
120 views

IP Camera Standard API Interface Specification v3.0 (2013-07-18)

This document provides an interface specification for IP cameras, including: 1. An overview of the product and firmware versions supported. 2. Definitions of general notations used such as abbreviations, URL syntax, and parameter value conventions. 3. Details of the interface specification including server responses and API groups covering functions like parameters, users, images, PTZ control, I/O control, video/audio streaming, and firmware upgrade.

Uploaded by

Steveli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
120 views

IP Camera Standard API Interface Specification v3.0 (2013-07-18)

This document provides an interface specification for IP cameras, including: 1. An overview of the product and firmware versions supported. 2. Definitions of general notations used such as abbreviations, URL syntax, and parameter value conventions. 3. Details of the interface specification including server responses and API groups covering functions like parameters, users, images, PTZ control, I/O control, video/audio streaming, and firmware upgrade.

Uploaded by

Steveli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 53

IP Camera Standard API - Interface

Specification
Revision: 3.0

Date: 2013-July-18

TABLE OF CONTENTS
DOCUMENT HISTORY ....................................................................................... 3
1 OVERVIEW ................................................................................................... 5
1.1 Product and firmware versions ........................................................................... 5
2 REFERENCES ................................................................................................ 5
3 DEFINITIONS ............................................................................................... 6
3.1 General notation .................................................................................................. 6
3.1.1 General abbreviations .............................................................................. 6
3.1.2 Style convention....................................................................................... 6
3.1.3 General CGI URL syntax and parameters ............................................... 7
3.1.4 Parameter value convention ..................................................................... 8
4 INTERFACE SPECIFICATION ............................................................................ 9
4.1 Server responses ................................................................................................. 9
4.1.1 HTTP status codes ................................................................................... 9
5 API GROUPS ............................................................................................... 11
5.1 General .............................................................................................................. 11
5.1.1 Update and list parameters and their values .......................................... 11
5.1.2 Add, modify and delete users ................................................................. 14
5.1.3 List users information ............................................................................ 16
5.1.4 Get, modify snapshot path ..................................................................... 17
5.1.5 Local Storage Management ................................................................... 18
5.1.6 Factory default ....................................................................................... 19
5.1.7 Hard factory default ............................................................................... 20
5.1.8 Backup ................................................................................................... 20
5.1.9 Restore ................................................................................................... 21
5.1.10 Firmware upgrade ................................................................................ 22
5.1.11 Restart server........................................................................................ 24
5.1.12 Server report......................................................................................... 24
5.1.13 System logs .......................................................................................... 25
5.1.14 System date and time ........................................................................... 25

1
5.1.15 IEEE 802.1x certificate upload ............................................................ 28
5.2 Image ................................................................................................................ 29
5.2.1 MJPEG images (snapshot) CGI request ................................................ 29
5.3 PTZ ................................................................................................................... 30
5.3.1 PTZ ........................................................................................................ 30
5.4 I/O ..................................................................................................................... 38
5.4.1 I/O control .............................................................................................. 38
5.4.2 Event Data .............................................................................................. 40
5.5 Video and Audio ............................................................................................... 45
5.5.1 Connect video and audio stream ............................................................ 45
5.5.2 Connect video stream by http ................................................................ 46
5.5.3 RTSP ...................................................................................................... 47

2
DOCUMENT HISTORY
Version Date Comment

2.01 2009-Aug-27 Initial version.

2.02 2009-Dec-18 Add 5.5.1 2nd H.264 Streaming Syntax

Add 5.1.13 Time Zone Setting

Add 5.3.1 PTZ Control Setting

2.03 2009-Mar-22 Add 5.1.7 Backup

Add 5.1.8 Restore

2.04 2010-Dec-3 5.3.1.1 PTZ control:

Add PTZ control supported camera models table

Add Valid values: pushaf, zoomtrigger, reset, zoomreset,

focusreset for autofocus parameter

Add zoomsteps and focussteps parameters

2.05 2011-June-1 Add Section: 5.1.5 Local Storage Management

5.3.1.1 PTZ control updates:

Add model: Full HD Multiple Streams IP Camera-Zoom

Update <autofocus> Valid Values

Update <gotoserverpresetno> Valid Values

Update <query> Valid Values

Add <setserverpresetno> parameter

2.06 2011-Sep-28 Add Section: 5.1.1.2 List parameter options

5.1.10.2 Start firmware upgrade updates:

Add model: HD IP Camera/ V Series/ IP PTZ, Full HD Multiple

Streams series, Full HD IP PTZ

5.3.1.1 PTZ control updates: Add Full HD IP PTZ model

Add Section: 5.3.1.2 Sequence Lines Configuration

2.07 2012-Apr-23 Update 5.3.1 PTZ control with center mode

Center

imagewidth

imageheight

stream

3
3.0 2013-July-18 Remove information regarding N3&A2 devices

For all models, the available preset number is from 1 to 256

Add Section: 5.4.2 Event Data

5.3.1.1 PTZ:

Add <continuousirismove> parameter

Update < gotoserverpresetno > Valid Values

Update < setserverpresetno > Valid Values

Add <gotoserverautopanno> parameter

Add <gotoservercruiseno> parameter

Add <gotoserversequenceno> parameter

5.3.1.2 Sequence Lines Configuration

Update < PresetNbr > Valid Values

5.3.1.3 PTZ configuration update:

Add home parameter

5.1.10.2 Start firmware upgrades:

Add valid values of Xarina models

Add Section: 5.1.15 IEEE 802.1x certificate upload

4
1 OVERVIEW
This document specifies the external HTTP-based application programming interface of the IP camera.

The HTTP-based video interface provides the functionality for requesting images and for getting and

setting internal parameter values. The image and CGI-requests are handled by the built-in Web server in

the camera.

1.1 Product and firmware versions


The support for the HTTP API is product and firmware dependent. Please refer to the Release Notes for

the actual product for compliance information.

2 REFERENCES

HTTP protocol

 Hypertext Transfer Protocol -- HTTP/1.0

External application programming interfaces (Client side)

 IP Camera API parameters

RTSP Protocol

 Real Time Streaming Protocol - RFC 2326

SDP Protocol

 Session Description Protocol - RFC 2327

5
3 DEFINITIONS

This section contains information on general usage of this document.

3.1 General notation

3.1.1 General abbreviations

The following abbreviations are used throughout this document

Common Gateway Interface - a standardized method of communication between a client


CGI
(e.g. a web browser) and a server (e.g. a web server).

Not applicable - a feature/parameter/value is of no use in a specific task


N/A

RFC 1738 describes the syntax and semantics for a compact string representation for a

resource available via the Internet. These strings are called "Uniform Resource Locators"
URL
(URLs).

A Uniform Resource Identifier (URI) is a compact string of characters for identifying an


URI
abstract or physical resource. RFC 2396 describes the generic syntax of URI.

3.1.2 Style convention

In URL syntax and in descriptions of CGI parameters, text in italics within angle brackets denotes content

that should be replaced with either a value or a string. When replacing the text string, the angle brackets

must also be replaced. An example of this is the description of the name for the server, denoted with

<servername> in the URL syntax description below, which is replaced with the string myserver in the

URL syntax example, also shown below.

URL syntax is written with the word "Syntax:" shown in bold face, followed by a box with the referred

syntax, as shown below. The name of the server is written as <servername>. This is intended to be

replaced with the name of the actual server. This can either be a name, e.g. "thecam" or

"thecam.adomain.net" or the associated IP number for the server, e.g. 192.168.0.250.

Syntax:

http://<servername>/cgi-bin/admin/userinfo.cgi

6
A description of returned data is written with "Return:" in bold face, followed by the returned data in a

box. All data returned as HTTP-formatted, i.e. starting with the string HTTP, is line-separated with a

Carriage Return and Line Feed (CRLF) printed as \r\n.

Return:

HTTP/1.0 <HTTP code> <HTTP text>\r\n

URL syntax examples are written with "Example:" in bold face, followed by a short description and a light

grey box with the example.

Example: Request user privacy.

http://myserver/cgi-bin/admin/privacy.cgi

Examples of what can be returned by the server from a request are written with "Example:" in bold face,

followed by a short description and a light grey box with an example of the returned data.

Example: Returned data after a successful request.

HTTP/1.0 200 Ok\r\n

3.1.3 General CGI URL syntax and parameters

CGI URLs are written in lower-case. CGI parameters are written in lower-case and as one word. When the

CGI request includes internal camera parameters, the internal parameters must be written exactly as

named in the camera or video server. For the POST method, the parameters must be included in the body

of the HTTP request. The CGIs are organized in function related directories under the cgi-bin directory.

The file extension of the CGI is required.

Syntax:

http://<servername>/cgi-bin/<subdir>[/<subdir>...]/<cgi>.<ext>

[?<parameter>=<value>[&<parameter>=<value>...]]

7
Example: List the Network parameters.

http://<servername>/cgi-bin/admin/param.cgi?action=list&group=Network

3.1.4 Parameter value convention

In tables defining CGI parameters and supported parameter values, the default value for optional

parameters is system configured.

8
4 INTERFACE SPECIFICATION
4.1 Server responses

4.1.1 HTTP status codes

The built-in Web server uses the standard HTTP status codes.

Return:

HTTP/1.0 <HTTP code> <HTTP text>\r\n

with the following HTTP code and meanings

HTTP code HTTP text Description

200 OK The request has succeeded, but an application

error can still occur, which will be returned as an

application error code.

204 No Content The server has fulfilled the request, but there is

no new information to send back.

302 Moved Temporarily The server redirects the request to the URI

given in the Location header.

400 Bad Request The request had bad syntax or was impossible

to fulfill.

401 Unauthorized The request requires user authentication or the

authorization has been refused.

404 Not Found The server has not found anything matching the

request.

409 Conflict The request could not be completed due to a

conflict with the current state of the resource.

500 Internal Error The server encountered an unexpected

condition that prevented it from fulfilling the

request.

9
503 Service Unavailable The server is unable to handle the request due

to temporary overload.

Example: Request includes invalid file names.

HTTP/1.0 404 Not Found\r\n

10
5 API GROUPS

To make it easier for developers to get an idea of which API requests are supported for different products,

the requests have been grouped together. Information about which groups are supported can be found

in the product-specific release notes document.

5.1 General

The requests specified in the General section are supported by all video products with firmware version

z20070921 and below.

5.1.1 Update and list parameters and their values

Note:

 The parameter is specified in the parameter document.

 The URL must follow the standard way of writing a URL, (RFC 2396: Uniform Resource

Identifiers (URI) Generic Syntax); that is, spaces and other reserved characters (";", "/", "?", ":",

"@", "&", "=", "+", "," and "$") within a <parameter> or a <value> must be replaced with

%<ASCII hex>. For example, in the string My camera, the space will have to be replaced with

%20, My%20camera.

Method: GET/POST

Syntax:

http://<servername>/cgi-bin/admin/param.cgi?

<parameter>=<value>[&<parameter>=<value>...]

with the following parameter and values

<parameter>=<value> Values Description

action=<string> add, remove, update Specifies the action to take. Depending on this

or list parameter, various parameters may be set, as

described in the following sections.

11
5.1.1.1 List parameters

Syntax:

http://<servername>/cgi-bin/admin/param.cgi?action=list

[&<parameter>=<value>...]

with the following parameter and values

<parameter>=<value> Values Description

group=<string>[& <group[.name]>[,<group[.name]>...] Returns the value of the

group=<string>...] camera parameter named

<group>.<name>.

The camera parameters

must be entered exactly as

they are named in the

camera or video server.

Example: List the Network parameters.

http://myserver/cgi-bin/admin/param.cgi?action=list&group=Network

Example: List the names of all Event parameters and Network parameters

http://myserver/cgi-bin/admin/param.cgi?action=list&group=Event&group=Network

5.1.1.2 List parameter options

List the all available options for some parameters.

Syntax:

http://<servername>/cgi-bin/admin/param.cgi?action=options

12
5.1.1.3 List output format

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

<parameter pair>

where <parameter pair> is

<parameter>=<value>\n

[ <parameter pair> ]

Example: Network query response.

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

root.Network.IPAddress=192.168.0.250\n

root.Network.SubnetMask=255.255.255.0\n

If the CGI request includes an invalid parameter value, the server returns an error message.

Return:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

# Error: <description>\n

5.1.1.4 Update parameters

Syntax:

http://<servername>/cgi-bin/admin/param.cgi?action=update

[&<parameter>=<value>...]

with the following parameters and values

13
<parameter>=<value> Values Description

<string>=<string> <group.name>=<value> Assigns <value> to the parameter

<group.name>.

The <value> must be URL-encoded when it

contains non-alphanumeric characters.

The camera parameters must be entered

exactly as named in the camera or the

video server.

Example: Set the exposure mode to auto.

http://myserver/cgi-bin/admin/param.cgi?

action=update&ImageSource.I0.Sensor.Exposure=auto

Example: Set the event enable.

http://myserver/cgi-bin/admin/param.cgi?

action=update& Event.E0.Enabled=yes

5.1.2 Add, modify and delete users

Add a new user with password and group membership, modify the information and remove a user.

Note: This request requires root access (root authorization).

Method: GET/POST

Syntax:

http://<servername>/cgi-bin/admin/pwdgrp.cgi?

<parameter>=<value>[&<parameter>=<value>...]

with the following parameters and values

14
<parameter>=<value> Values Description

action=<string> add, update, remove or add = create a new user account.

get
update = change account information of

specified parameters if the account exists.

remove = remove an existing account if it

exists.

get = get a list of the users which belong to

each group defined.

user=<string> <string> The user account name, a non-existing user

name. Valid characters are a thru z, A thru Z

and 0 thru 9.

pwd=<string> <string> The unencrypted password of the account.

Valid characters are a thru z, A thru Z and 0

thru 9.

sgrp=<string>:[<string>...] <string>[,<string>...] Colon separated existing secondary group

names of the account.

Ex: dido:camctrl:talk:listen

Example: Create a new administrator account.

http://myserver/cgi-bin/admin/pwdgrp.cgi?action=add&user=joe&pwd=foo&sgrp=dido:camctrl:talk:listen

Example: Change the password of an existing account.

http://myserver/cgi-bin/admin/pwdgrp.cgi?action=update&user=joe&pwd=bar

Example: Remove an account.

http://myserver/cgi-bin/admin/pwdgrp.cgi?action=remove&user=joe

15
Example: List groups and users.

http://myserver/cgi-bin/admin/pwdgrp.cgi?action=get

5.1.3 List users information

List the user information with password or privacy.

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/privacy.cgi

Example: List the username and privacy

http://myserver/cgi-bin/admin/privacy.cgi?

Response:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

Username:Dido:Camset:Talk:Listen \n

Admin:1:1:1:1\n

Syntax:

http://<servername>/cgi-bin/admin/userinfo.cgi

Example: List the username and password.

http://myserver/cgi-bin/admin/userinfo.cgi?

16
Response:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

List username and password\n

Admin:1234\n

5.1.4 Get, modify snapshot path

Get or modify Admin snapshot path, Admin can capture images by the web page snapshot button, and

the images are stored at the path you set.

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/snapshot.cgi? <parameter>=<value>]

with the following parameters and values

<parameter>=<value> Values Description

path=<string> <string> Valid character: A-Za-z0-9and some special tokens

_/\~!@#$%^&+-:

action=<string> get Get the Admin snapshot path.

set
Set the Admin snapshot path, with action=set parameter path

is required.

Example: Set the Admin snapshot path to C:\capture

http://myserver/cgi-bin/admin/snapshot.cgi?action=set&path=C%3A%5Ccapture

17
Response:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\n

\n

OK\n

5.1.5 Local Storage Management

Manage the local storage, including format storage, list existing file, remove or download an existing file.

Note: This request requires root access (root authorization).

Method: GET/POST

Syntax:

http://<servername>/cgi-bin/admin/storagemanagement.cgi?

<parameter>=<value>[&<parameter>=<value>...]

with the following parameters and values

<parameter>=<value> Values Description

action=<string> format, format = format the local storage device

list,
list = get a list of the existing files in the local storage
remove,

download
remove = remove an existing file in local storage

download = download an existing file from the local

storage .

filename=<string> <string> The filename of the file that is to be removed or

downloaded.

18
Example: Format the local storage device.

http://myserver/cgi-bin/admin/storagemanagement.cgi?action=format

Example: Get the file list from the local storage.

http://myserver/cgi-bin/admin/storagemanagement.cgi?action=list

Example: Remove an existing file.

http://myserver/cgi-bin/admin/storagemanagement.cgi?action=remove&filename=A_20110101_010101.avi

Example: Download an existing file.

http://myserver/cgi-bin/admin/storagemanagement.cgi?action=download&filename=A_20110101_010101.avi

5.1.6 Factory default

Reload factory default. All parameters except Network.BootProto, Network.IPAddress,

Network.SubnetMask, Network.Broadcast, Network.DefaultRouter and Network port are set to their

factory default values.

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/factorydefault.cgi

19
5.1.7 Hard factory default

Reload factory default. All parameters are set to their factory default value.

Note: This request requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/hardfactorydefault.cgi

5.1.8 Backup

Download a unit specific backup of all files in the folder /etc in tar format.

Note: This request requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/backup.cgi

Response:

HTTP/1.0 200 OK\r\n

Content-Type: application/octet-stream\r\n

Content-length: 15899\r\n

Content-Disposition: attachment; filename=config_file.bin\r\n

<file content of config_file.bin >

20
5.1.9 Restore

Upload a unit specific backup previously created by the backup.cgi.

Note: This request requires administrator access (administrator authorization).

Method: POST

Syntax:

http://<servername>/cgi-bin/admin/restore.cgi

The file is provided in the HTTP body according to the format given in RFC 1867. The body is created

automatically by the browser if using HTML form with input type “file.”

Response: Upload of backup, where “\r\n” has been omitted in the HTTP body.

POST /cgi-bin/admin/restore.cgi? HTTP/1.0\r\n

Content-Type: multipart/form-data; boundary=AaBo3x\r\n

Content-Length: <content length>\r\n

\r\n

--AaBo3x\r\n

Content-Disposition: form-data; name=" config_file.bin ";

filename=" config_file.bin "\r\n

Content-Type: application/octet-stream\r\n

\r\n

<file content of config_file.bin>

\r\n

--AaBo3x--\r\n

21
5.1.10 Firmware upgrade

5.1.10.1 Before firmware upgrade

It will stop some process (like stream server, image transfer .. etc) to prepare firmware upgrade.

Note: This request requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/beforeupgrade.cgi

5.1.10.2 Start firmware upgrade

Upgrade the firmware version.

Note: This requires administrator access (administrator authorization).

Method: POST

Syntax:

http://<servername>/cgi-bin/admin/firmwareupgrade.cgi[?<parameter>=<value>]

with the following parameters and values

<parameter>=<value> Values Description

filename=<string> Full HD Multiple Specifies the filename of firmware upgrade.

Streams series:

uImage, uImage = kernel package binary file.

userland.img, cameraFw = camera parameters binary file.

var, userland.jffs2 = JFFS2 image binary file.

uImage_userland, var = variable binary file.

mcu.bin (Zoom Type uImage_userland.jffs2 = kernel package

model only) binary file + JFFS2 image binary file

22
userland.img = UBIFS image binary file

Full HD IP PTZ: uImage_userland = kernel package binary file

uImage, + UBIFS image binary file

userland.img, switch.bin = Switch Board firmware upgrade

var, main.bin = Main Board firmware upgrade

uImage_userland, module.bin = Camera Module firmware

switch.bin, upgrade

main.bin,

module.bin

Full HD WDR IP

Camera:

uImage.img

userland.img

var

uImage_userland

uboot

The file content is provided in the HTTP body according to the format given in RFC 1867. The body is

created automatically by the browser if using HTML form with input type "file".

Example:

POST /cgi-bin/admin/firmwareupgrade.cgi?filename=userland.jffs2 HTTP/1.0\r\n

Content-Type: multipart/form-data; boundary=AsCg5y\r\n

Content-Length: <content length>\r\n

Authorization: Basic QWRtaW46MTIzNA==

\r\n

--AsCg5y\r\n

Content-Disposition: form-data; name="userland.jffs2"; filename="userland.jffs2"\r\n

Content-Type: application/octet-stream\r\n

\r\n

<firmware file content>

\r\n

--AsCg5y--\r\n

23
5.1.11 Restart server

Restart server.

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/restart.cgi

5.1.12 Server report

This CGI request generates and returns a server report. This report is useful as an input when requesting

support. The report includes product information, parameter settings and system logs.

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/serverreport.cgi

24
5.1.13 System logs

Get system log information.

Note: This requires administrator access (administrator authorization).

Note: The response is product/release-dependent.

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/systemlog.cgi

Return:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

<system log information>

5.1.14 System date and time

Get or set the system date and time.

Method: GET/POST

Syntax:

http://<servername>/cgi-bin/admin/date.cgi?<parameter>=<value>

with the following parameter and values

<parameter>=<value> Values Description

action=<string> get or set Specifies what to do.

25
get = get the current date and time.

set = set the current date and/or time.

5.1.14.1 Get system date and time

Syntax:

http://<servername>/cgi-bin/admin/date.cgi?action=get

Return:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

<month> <day>, <year> <hour>:<minute>:<second>\r\n

Example:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

Apr 03, 2003 15:16:04\r\n

5.1.14.2 Set system date and time

Syntax:

http://<servername>/cgi-bin/admin/date.cgi?action=set[&<parameter>=<value>...]

with the following parameters and values

26
<parameter>=<value> Values Description

year=<int> 2007 - 2099 Current year.

month=<int> 1 - 12 Current month.

day=<int> 1 - 31 Current day.

hour=<int> 0 - 23 Current hour.

minute=<int> 0 - 59 Current minute.

second=<int> 0 - 59 Current second.

timezone=<string> GMT-12…GMT+13 Time zone.

The set action produces one of the following server responses:

Return: A successful set.

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

OK\r\n

Return: A failed set. Settings or syntax are probably incorrect.

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

Request failed: <error message>\r\n

Example: Set the date.

http://myserver/cgi-bin/admin/date.cgi?action=set&year=2005&month=4&day=3

Response:

HTTP/1.0 200 OK\r\n

27
Content-Type: text/plain\r\n

\r\n

OK\r\n

5.1.15 IEEE 802.1x certificate upload

Upload the 802.1x certificate

Note: This request requires administrator access (administrator authorization).

Method: POST

Syntax:

http://<servername>/cgi-bin/admin/upload_certificate.cgi[?<parameter>=<value>]

with the following parameters and values

<parameter>=<value> Values Description

type=<string> ca_certificate Specifies the type of uploaded certificate.

client_certificate Those certificate files are provided by

private_key authentication server.

The file content is provided in the HTTP body according to the format given in RFC 1867. The body is

created automatically by the browser if using HTML form with input type "file".

Example:

POST /cgi-bin/admin/upload_certificate.cgi?type=ca_certificate HTTP/1.0\r\n

Content-Type: multipart/form-data; boundary=AsCg5y\r\n

Content-Length: <content length>\r\n

Authorization: Basic QWRtaW46MTIzNA==

\r\n

--AsCg5y\r\n

Content-Disposition: form-data; name=" ca_certificate "; filename=" ca_certificate "\r\n

Content-Type: application/octet-stream\r\n

\r\n

28
<firmware file content>

\r\n

--AsCg5y--\r\n

5.2 Image

5.2.1 MJPEG images (snapshot) CGI request

Method:GET

Syntax:

http://<servername>/cgi-bin/jpg/image.cgi?

When a JPEG image is requested, the server returns either the specified JPEG image file or an error.

Return:

HTTP/1.0 200 OK\r\n

Content-Type: image/jpeg\r\n

Content-Length: <image size>\r\n

\r\n

<JPEG image data>\r\n

Example: Requested JPEG image.

HTTP/1.0 200 OK\r\n

Content-Type: image/jpeg\r\n

Content-Length: 15656\r\n

\r\n

<JPEG image data>\r\n

29
5.3 PTZ

5.3.1 PTZ

Provide CGI commands for PTZ function control.

5.3.1.1 PTZ control

To control the Pan, Tilt and Zoom behavior of a PTZ unit, the following PTZ control URL is used. This URL

has view access rights.

Important:

Some PTZ units automatically reduce pan and tilt movements as the zoom factor increases. Therefore,

the actual movement may be less than what is requested of these units.

The PTZ control is device-dependent; PTZ control supported camera models are as follows:

Classification Model name

Full HD Multiple Streams IP NH073-10x

Camera-Zoom NH073-18x

X0S6-7

X0S7-7

Full HD Multiple Streams IP NH223,

Camera-Motorized NH323,

NH053,

W2 (NV223),

W3 (NV323),

W5 (NV053)

Full HD IP PTZ NH720

NH820

Note:

The URL must follow the standard way of writing a URL, (RFC 2396: Uniform Resource Identifiers (URI)

Generic Syntax); that is, spaces and other reserved characters (";", "/", "?", ":", "@", "&", "=", "+", ","

and "$") within a <parameter> or a <value> must be replaced with %<ASCII hex>. For example, in the

string My camera, the space will have to be replaced with %20, My%20camera.

Method: GET/POST

Syntax:

30
http://<servername>/cgi-bin/com/ptz.cgi?<parameter>=<value>[&<parameter>=<value>...]

with the following parameters and values

Parameter name Default Valid values Description

value

move Full HD IP PTZ: Moves the device 5 degrees in

home the specific direction.

up

down

left

right

upleft

upright

downleft

downright

pan Full HD IP PTZ: Pans the device relative to the

-180.0 to 180.0 (0, 0)position

tilt Full HD IP PTZ: Tilts the device relative to the

-10.0 to 190.0 (0, 0)position

zoom Full HD IP PTZ: Zoom the device n steps

0 to 9999

focus Full HD IP PTZ: Move focus n steps

0 to 9999

rpan Full HD IP PTZ: Pans the device n degrees

-360.0 to 360.0 relative to the current position

rtilt Full HD IP PTZ: Tilts the device n degrees

-360.0 to 360.0 relative to the current position

rzoom Full HD IP PTZ: Zoom the device n steps

-9999 to 9999 relative to the current position;

Positive values mean zoom in,

and negative values mean

zoom out.

31
rfocus Full HD IP PTZ: Move device n steps relative to

-9999 to 9999 the current position; Positive

values mean focus far, and

negative values mean focus

near.

autofocus Full HD IP PTZ: on/off: Autofocus on/off.

on, off pushaf: Aurofocus by one push

Full HD Multiple Streams IP zoomtrigger: Aurofocus by

Camera-Zoom: zoom in/out

on, off, zoomtrigger, pushaf zoomreset: reset zoom

Full HD Multiple Streams IP focusreset: reset focus

Camera-Motorized: reset: reset zoom & Focus

pushaf, zoomreset, focusreset

continuouspantiltmove Full HD Multiple Streams IP Continuous pan/tilt motion.


Camera-Zoom:
Positive values mean right
-100 to 100, -100 to 100
(pan) and up (tilt), negative

values mean left (pan) and

down (tilt). "0,0" means stop.

continuouszoommove -100 to 100 Continuous zoom motion.

Positive values mean zoom in

and negative values mean

zoom out.

Higher value gives higher

speed.(Motorized models

exclusive)

"0" means stop.

zoomsteps Full HD Multiple Streams IP Positive values mean zoom in

Camera-Motorized: and negative values mean

1, 2, 4, 8, 16, 32, 64, 128, -1, zoom out.

-2, -4, -8, -16, -32, -64, -128

focussteps Full HD Multiple Streams IP Positive values mean focus

Camera-Motorized: near and negative values mean

1, 2, 4, 8, 16, 32, 64, 128, -1, focus far.

32
-2, -4, -8, -16, -32, -64, -128

continuousfocusmove -100 to 100 Continuous focus motion.

Positive values mean focus

near and negative values mean

focus far.

Higher value gives higher

speed.(Motorized models

exclusive)

"0" means stop.

continuousirismove stop stop stop: stop the change of


open aperture
close
open: increase the aperture

continuously

close: decrease the aperture

continuously

(This parameter is only

available for the device which

equip with C/S mount lens and

support RS485)

gotoserverpresetno Full HD IP PTZ: Move to the position associated


1 to 256 with the specified preset
Full HD Multiple Streams IP position number.
Camera-Zoom:

1 to 256

gotoserverautopanno Full HD IP PTZ: Run the Autopan function


1,2,3,4 associated with specified

autopan function number

gotoservercruiseno Full HD IP PTZ: Run the Cruise function


1,2,3,4,5,6,7,8 associated with specified cruise

function number

gotoserversequenceno Full HD IP PTZ: Run the Sequence function


1,2,3,4,5,6,7,8 associated with specified

33
sequence function number

center <int x>,<int y> Used to send the coordinates

for the point in the image

where the user clicked. This

information is then used by the

server to center the clicked

point. Used for center mode

together with the following

parameters: imagewidth,

imageheight, and stream. See

center mode example.

imagewidth 1, ... The current image width of the

image seen. Used for center

mode.

imageheight 1, ... The current image height of

the image seen. Used for

center mode.

stream h264 For example: If

h264_2 rtsp://server_address/h264

jpeg is connected, then

stream=h264. Used for center

mode.

query Full HD IP PTZ: Returns the current parameter


position values.
Full HD Multiple Streams IP

Camera-Zoom:

position

info 1 1 Returns a description of

available PTZ commands.

Example: Center mode command which centers the clicked point.

34
http://myserver/cgi-bin/com/ptz.cgi?center=2,4&imageheight=578&imagewidth=722&stream=h264

Example: Request information about which PTZ commands are available.

http://myserver/cgi-bin/com/ptz.cgi?info=1

5.3.1.2 Sequence Lines Configuration


Sequence Lines are configurable for IP PTZs, Full HD IP PTZs and some IP Cameras as shown below:

Classification Model name

Full HD Multiple Streams IP NH073-3x

Camera-Zoom NH073-18x

X0S6-7

X0S7-7

Full HD Multiple Streams IP NH063

Camera (RS-485 capable) W6 (NV063)

X0S6-6

X0S7-6

Full HD IP PTZ NH720

NH820

Note: This request requires administrator access (administrator authorization).

With the following parameters and values

Parameter name Default value Valid values Description

PresetNbr 1 1 … 256 The number of the PTZ preset

position.

MoveSpeed Full HD IP PTZ: Full HD IP PTZ: The speed at which to move

10 0 … 14 camera to this preset position.

WaitTiime 1 0 … 255 The view time for this preset

position in seconds.

35
Example: Create a Sequence Line parameter group

http://<servername>/cgi-bin/admin/param.cgi?action=add&group=GuardTour

Example: Add a Sequence Point to the Sequence Line

http://<servername>/cgi-bin/admin/param.cgi?action=add&group=GuardTour.G1.Tour

Note: Preset Points should be available before adding a Sequence Point to the Sequence Line.

Example: Modify the parameter values

http://<servername>/cgi-bin/admin/param.cgi?action=update&GuardTour.G1.Tour.T1.PresetNbr=2

Example: Add another Sequence Point and modify the parameter values in the same request

http://<servername>/cgi-bin/admin/param.cgi?action=add&group=GuardTour.G1.Tour&GuardTour.

G1.Tour.T.PresetNbr=3&GuardTour.G1.Tour.T.WaitTime=5

36
5.3.1.3 PTZ configuration

Configure PTZ preset positions. On Screen Display (OSD) control.

Note: This request requires administrator access (administrator authorization).

Method: GET/POST

Syntax:

http://<servername>/cgi-bin/com/ptzconfig.cgi?

<parameter>=<value>[&<parameter>=<value>...]

with the following parameters and values

<parameter>=<value> Values Description

setserverpresetname=<int>,<string> Full HD IP PTZ: Associates the current position

<preset to <preset name> as a preset

no><preset position in the server.

name>1

setserverpresetno=<int> Full HD IP Saves the current position as a

PTZ/Full HD preset position number in the

Multiple server.

Streams IP

Camera-Zoom:

1 to 256

removeserverpresetname=<string> Full HD IP PTZ: Removes the specified preset

<preset name>1 position associated with

<preset name>.

removeserverpresetno=<int> Full HD IP PTZ: Removes the specified preset

1, ... position.

setserverautopan=<int>,<string> Full HD IP PTZ:

<autopan

line>,<state>

37
setserverautopandirspeed=<int>,<string>,<int> Full HD IP PTZ: Set autopan direction

<autopanline>, and speed.

<direction>, <direction>:left,right

<speed> <speed>:0-3

setservercruise=<int>,<string> Full HD IP PTZ: Set cruise line.

<cruise <state>

line>,<state> start : start cruise

setting

end : end cruise

setting

home=<string> yes To set the home position with

current position of PTZ. This

position will be used in

move=home API command.

1
<preset name> is a string with a maximum of 31 characters, ~ is not allowed.

5.4 I/O

The requests in the I/O section are supported by the products with Input/Output functions

5.4.1 I/O control

5.4.1.1 Input

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/io/input.cgi? <parameter>=<value>

with the following parameters and values

<parameter>=<value> Values Description

38
check=<int>[,<int>,…] <id1>[,<id2>…] Returns the status (1 or 0) of one of more inputs

numbered id1, id2,…

checkactive=<int>[,<int>,…] <id1>[,<id2>…] Returns the status (active or inactive) of one or

more inputs numbered id1,id2

Number of inputs may be different according to the camera model. Please see the product’s specification

http://myserver/cgi-bin/io/input.cgi?check=1

Response:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

Input1=0

5.4.1.2 Output

Note: This requires administrator access (administrator authorization).

Method: GET

Syntax:

http://<servername>/cgi-bin/io/output.cgi? <parameter>=<value>

with the following parameters and values

<parameter>=<value> Values Description

check=<int>[,<int>,…] <id1>[,<id2>…] Returns the status (1 or 0) of one or more

outputs numbered id1, id2,…

checkactive=<int>[,<int>,…] <id1>[,<id2>…] Returns the status (active or inactive) of one or

more outputs numbered id1,id2

action=<string> <id1>:<a> <id> = Output number. If omitted, output 1 is

39
selected.

<a> = Action character: / of \

/=active, \=inactive

Number of outputs may be different according to the camera model. Please see the product’s

specification

Example: Set output 1 active

http://myserver/cgi-bin/io/output.cgi?action=1:/

Response:

HTTP/1.0 200 OK\r\n

Content-Type: text/plain\r\n

\r\n

OK

5.4.2 Event Data

Note: This section explains the commands related to eventdata.cgi. This command could deliver setting

and current status of IP Camera motion detection, I/O and tampering.

Method: GET

Syntax:

http://<servername>/cgi-bin/admin/eventdata.cgi?<parameter>=<value>[&<parameter>=<value>...]

with the following parameter and values

<parameter>=<value> Values Description

action=<string> get, monitor get: get the current status of event

data.

monitor: get the current status of

event data continuously

40
group=<string> Motion, Motion1, Motion2, Motion3, Motion: Motion detection

IO, T0 (event.E1)

Motion1: Motion detection

(event.E10)

Motion2: Motion detection

(event.E11)

Motion3: Motion detection

(event.E12)

IO: Digital Input / Output

Information

T0: Tampering alarm(event.E2)

Value of parameter group can be

concatenated by “,”

MotionParam Enabled,Level,Sensitivity,Triggered This parameter can used to query

the interest parameter of event

data. If the command omitted the

MotionParam parameter, the

return result contains all the data

about the motion detection.

Value of parameter MotionParam

can be concatenated by “,”

Enabled: The motion event is

enabled or not. (0: disable, 1:

enable)

Level: Percentage of motion

detected in all interested area.

(0…100)

Sensitivity: Sensitivity value of

motion detection setting. (0…100)

Triggered: The event is triggered

or not (0: not triggered, 1:

triggered)

IOParam Status Only return interested value of

Input / Output status

41
TamperingParam Enable, Triggered Get interested value of tampering

event(T0)

Enabled: The tampering alarm

function is enabled or not ( 0:

disabled, 1: enabled)

Triggered: The tampering alarm

function is triggered or not (0: not

triggered, 1: triggered)

Syntax:

http://<servername>/cgi-bin/admin/eventdata.cgi?action=get[&<parameter>=<value>...]

Example: Get Motion current status.

http://myserver/cgi-bin/admin/eventdata.cgi?action=get&group=Motion

HTTP/1.0 200 OK\r\n

Content-type: text/plain\r\n

Content-length: 20\r\n

\r\n

Motion:Enabled=0;\r\n

Motion (Event.E1) is not enabled.

Example: Get Motion, Motion2 current status.

http://myserver/cgi-bin/admin/eventdata.cgi?action=get&group=Motion,Motion2

HTTP/1.0 200 OK\r\n

Content-type: text/plain\r\n

Content-length: 77\r\n

42
\r\n

Motion:Enabled=0;\r\n

Motion2:Enabled=1;Level=15;Sensitivity=80;Triggered=0;\r\n

Motion (Event.E1) is not enabled.

Motion2 (Event.E11) is enabled, but the motion is not triggered.

Example: Get Motion, Motion1 and IO status in one query.

http://myserver/cgi-bin/admin/eventdata.cgi?action=get&group=Motion,Motion1,IO

HTTP/1.0 200 OK\r\n

Content-type: text/plain\r\n

Content-length: 101\r\n

\r\n

Motion:Enabled=1;Level=0;Sensitivity=80;Triggered=0;\r\n

Motion1:Enabled=0; \r\n

IO:Status=00000100000000;\r\n

\r\n

The definition is IO status is explained below.

<XX0><XX1><XX2><XX3><XX4><XX5><XX6>

Digit Value Description

<XX0> 00 ~ ff Input1 ~ Input8 is enabled or not.

It stands for b7b6b5b4b3b2b1b0 in binary Ex: a2 => 10100010 means

0: disable / 1: enable Input8, 6, and 2 are enabled.

Input7, 5, 4, 3 and 1 are disabled.

<XX1> 00 ~ ff Input1~Input8 is open or closed.

It stands for b7b6b5b4b3b2b1b0 in binary

0: open / 1: closed

<XX2> 00 ~ ff Output1~OUtput8 is open or closed.

It stands for b7b6b5b4b3b2b1b0 in binary

0: open / 1: closed

<XX3> 00 ~ ff Input1~Input8 setting (Normal

It stands for b7b6b5b4b3b2b1b0 in binary Open / Normal Closed)

0: Normal open/ 1: Normal closed

43
<XX4> 00 ~ ff Output1~Output8 setting (active

It stands for b7b6b5b4b3b2b1b0 in binary status of the Output)

0: active status open/ 1: active status closed

<XX5> 00 ~ ff Input1~Input8 active or inactive

It stands for b7b6b5b4b3b2b1b0 in binary

0: inactive/ 1: active

<XX6> 00 ~ ff Output1~Output8 active or inactive

It stands for b7b6b5b4b3b2b1b0 in binary

0: inactive/ 1: active

Example: Get Motion, Motion1 status of Enabled and Triggered.

http://myserver/cgi-bin/admin/eventdata.cgi?action=get&group=Motion,Motion1&

MotionParam=Enabled,Triggered

HTTP/1.0 200 OK\r\n

Content-type: text/plain\r\n

Content-length: 51\r\n

\r\n

Motion:Enabled=1;Triggered=0; \r\n

Motion1:Enabled=0; \r\n

\r\n

Syntax:

http://<servername>/cgi-bin/admin/eventdata.cgi?action=monitor[&<parameter>=<value>...]

Example: Get information of first and second motion window event data continuously.

http://myserver/cgi-bin/admin/eventdata.cgi?action=monitor&group=Motion,Motion1

44
HTTP/1.0 200 OK\r\n

Content-type: multipart/x-mixed-replace;boundary=<boundary>\r\n

\r\n

--<boundary>\r\n

Content-Type: text/plain\r\n

Content-Length: 74\r\n

\r\n

Motion:Enabled=1;Level=0;Sensitivity=80;Triggered=0; \r\n

Motion1:Enabled=0; \r\n

\r\n

--<boundary>\r\n

Content-Type: text/plain\r\n

Content-Length: 75\r\n

\r\n

Motion:Enabled=1;Level=15;Sensitivity=80;Triggered=0; \r\n

Motion1:Enabled=0; \r\n

\r\n

……

5.5 Video and Audio

5.5.1 Connect video and audio stream

Connect a video and audio stream by UDP or TCP with default resolution and compression as defined in

the system configuration.

Syntax: connect to H.264

rtsp://<servername>/h264

Syntax: connect to 2nd H.264 streaming in quad H.264 mode.

rtsp://<servername>/h264_2

Syntax: connect to 3rd H.264 streaming in quad H.264 mode.

45
rtsp://<servername>/h264_3

Syntax: connect to 4th H.264 streaming in quad H.264 mode.

rtsp://<servername>/h264_4

Syntax: connect to MJPEG

rtsp://<servername>/jpeg

5.5.2 Connect video stream by http

Connect a video stream by HTTP with default resolution and compression as defined in the system

configuration.

Syntax: connect to MJPEG

http://<servername>:8008

46
5.5.3 RTSP

This document specifies the external RTSP-based application programming interface of the camera and

video servers.

The RTSP URL is rtsp://<server name>/h264 where <server name> is the host name or IP address of

the server. The DESCRIBE, SETUP, OPTIONS, PLAY, PAUSE and TEARDOWN methods are supported. The

RTSP protocol is described in RFC 2326.

Request syntax:

COMMAND URI RTSP/1.0<CRLF>

Headerfield1: val1<CRLF>

Headerfield2: val2<CRLF>

...

<CRLF>

Response syntax:

RTSP/1.0 ResultCode ResultString<CRLF>

Headerfield3: val3<CRLF>

Headerfield4: val4<CRLF>

...

<CRLF>

The following header fields are accepted by all commands. Other header fields are silently ignored

(unless stated otherwise in the sections below).

Field Description

CSeq Request sequence number.

Session Session identifier (returned by server in SETUP response).

Content-Length Length of content.

The following header fields can be generated for all responses by the RTSP server:

47
Field Description

CSeq Response sequence number (matches the sequence number of the

request).

Session Session identifier.

5.5.3.1 RTSP DESCRIBE

The DESCRIBE command returns the SDP (RFC 2327) description for the URI. The DESCRIBE command

accepts the following additional header field:

Accept List of content types that client supports (application/sdp is the only

supported type).

The DESCRIBE command generates the following additional header fields:

Content-Type Type of content (application/sdp).

Content-Length Length of SDP description.

Content-Base If relative URLs are used in the SDP description, then this is the base URL.

Example:

DESCRIBE rtsp://192.168.0.200/h264 RTSP/1.0

CSeq: 0

Accept: application/sdp

Response example:

RTSP/1.0 200 OK

CSeq: 0

Date: Thu, Jun 20 2013 09:12:51 GMT

Content-Base: rtsp://192.168.0.200/h264/

Content-Type: application/sdp

48
Content-Length: 641

v=0

o=- 1371534426547402 1 IN IP4 0.0.0.0

s=Session streamed by "nessyMediaServer"

i=h264

t=0 0

a=tool:LIVE555 Streaming Media v2010.04.09_dyna_modi_2010.05.05

a=type:broadcast

a=control:*

a=range:npt=0-

a=x-qt-text-nam:Session streamed by "nessyMediaServer"

a=x-qt-text-inf:h264m=video 0 RTP/AVP 99

c=IN IP4 0.0.0.0

a=rtpmap:99 H264/90000

a=fmtp:99 packetization-mode=28;profile-level-id=4D0029;

sprop-parameter-sets=Z00AKZpigPAET8uAtQEBAUAAAPoAADqYOhgAQAAABAAG7y40MACAAAAIAA3

eXCgA,aO48gA==

a=control:track1

a=cliprect:0,0,1920,1080

a=framerate:30.000000

m=audio 7878 RTP/AVP 0

a=rtpmap:0 PCMU/8000/1

a=control:track2

49
5.5.3.2 RTSP OPTIONS

The OPTIONS command returns a list of supported RTSP commands.

Example:

OPTIONS * RTSP/1.0

CSeq: 1

Response example:

RTSP/1.0 200 OK

CSeq: 1

Date: Fri, Jan 05 2007 18:32:15 GMT

Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE

5.5.3.3 RTSP SETUP

The SETUP command configures the delivery method for the data. The SETUP command requires and

generates the following additional header field:

Transport Specifies how the data stream is transported. Supported variants:

RTP/AVP;unicast;client_port=port1-port2

RTP/AVP;multicast;client_port=port1-port2

RTP/AVP/TCP;unicast

The response returns a session identifier that should be used with stream control commands to the server

(PLAY, PAUSE, TEARDOWN). If the Session header includes a timeout parameter, then the session needs

to be kept alive. This can be done by sending RTSP requests to the server containing the session identifier

(e.g. OPTIONS) within the specified timeout time or through the use of RTCP. The RTSP server does not

support reconfiguring of the transport parameters.

Example:

SETUP rtsp://192.168.0.200/h264/track1 RTSP/1.0

CSeq: 1

50
Transport: RTP/AVP;unicast;client_port=6300-6301

Response example:

RTSP/1.0 200 OK

CSeq: 1

Date: Thu, Jun 20 2013 09:12:51 GMT

Transport:

RTP/AVP;unicast;destination=192.168.0.102;source=192.168.0.200;client_port=6300-6301;server

_port=6970-6971

Session: 1

Example:

SETUP rtsp://192.168.0.200/h264/track2 RTSP/1.0

CSeq: 2

Transport: RTP/AVP;unicast;client_port=6302-6303

Response example:

RTSP/1.0 200 OK

CSeq: 2

Cache-Control: must-revalidate

Date: Thu, Jun 20 2013 09:12:51 GMT

Transport:

RTP/AVP;unicast;destination=192.168.0.102;source=192.168.0.200;client_port=6302-6303;server

_port=6972-6973

Session: 1

51
5.5.3.4 RTSP PLAY

The PLAY command starts (or restarts if paused) the data delivery to the client. The PLAY command

generates the following additional header fields:

Range Specifies the range of time being played. Since only live streams are used,

the specified time will always begin now and have no stop time.

RTP-Info Information about the RTP stream. More specifically, it includes the next

RTP sequence number that will be used.

Example:

PLAY rtsp://192.168.0.200/h264/ RTSP/1.0

CSeq: 3

Session: 1

Range: npt=0.000-

Response example:

RTSP/1.0 200 OK

CSeq: 3

Date: Thu, Jun 20 2013 09:12:51 GMT

Range: npt=0.000-

Session: 1

RTP-Info:

url=rtsp://192.168.0.200/h264/track1;seq=41182;rtptime=1985344790,url=rtsp://192.168.0.200

/h264/track2;seq=55405;rtptime=3572879460

52
5.5.3.5 RTSP PAUSE

The PAUSE command pauses the data delivery from the server.

Example:

PAUSE rtsp://192.168.0.200/h264 RTSP/1.0

CSeq: 5

Session: 1

Response example:

RTSP/1.0 200 OK

CSeq: 5

Date: Fri, Jan 05 2007 19:03:59 GMT

Session: 1

5.5.3.6 RTSP TEARDOWN

The TEARDOWN command terminates the data delivery from the server.

Example:

TEARDOWN rtsp://192.168.0.250/h264 RTSP/1.0

CSeq: 6

Session: 1

Response example:

RTSP/1.0 200 OK

CSeq: 6

Session: 1

53

You might also like