Configuration via Web Interface
Commend SIP Series
56
2.0/0612
Remote Control
To be able to control different operating states for automated processes (or without the authorisation
of a “full access” onto the web interface), the possibility for establishing a “remote control account”
for following actions of the respective station is available:
Switching Relay outputs
Establish Call
Simulation of keypress
Take over / Cancel / Refuse Call
The remote control to the SIP station is enabled by
sending HTTP strings
.
The
HTTP string
is made up of
2 parts
:
The
1st part
of the
HTTP string
is universally valid and required for all actions to be carried out
<User>: User name for remote access (see “Remote control User Login” on
page 54
)
<PW>: Password for remote access (see “Remote control User Password” on
page 54
)
<IP address>: IP-Address of SIP station
The
2nd part
of the
HTTP string
is made up of action-specific parameters:
Parameters for Switching Relay Outputs
<1 or 2>: value
1
for relay 1, value
2
for relay 2
<Trigger>: desired trigger mode of relay (see also
page 51
):
on
: close relay output (activate)
off
: open relay output (deactivate)
flashing:
switch relay output to blinking
dooropener&dooropenertimer=
<time in sec>
–
door opener function: relay output is closed
for a definable time (“
dooropenertimer
” e.g. 3 seconds).
toggle:
invert current state of the relay output (switch on/off)
Example:
Closing (activating) relay 1 of SIP station 192.168.123.234 (User: Hudson, PW: Saul):
Switching relay 2 of SIP station 192.168.11.22 to blinking (User: Ian, PW: Fraiser):
Closing (activating) relay 1 of SIP station 172.16.9.222 for a (door opener) time of 4 seconds:
Parameter for Simulation Keypress
The remote control account for the “remote control user” is established via the
web interface
see ”User Accounts” on page 54
.
http://<User>:<PW>@<IP-Adr.>/cgi-bin/remotecontrol/
...
Note:
It is not necessarily required to enter the user name and password in the HTTP string. If the user and
password is not included in the HTTP string, then this data has to be entered after copying (and acknow-
ledging) the string into the browser.
http://<User>:<PW>@<IP-Adr.>/cgi-bin/remotecontrol
/
relais.cgi?relais=<1od.2>&action=<Trigger>
http://
Hudson
:
Saul
@
192.168.123.234
/cgi-bin/remotecontrol/relais.cgi?relais=
1
&action=
on
http://
Ian
:
Fraiser
@
192.168.11.22
/cgi-bin/remotecontrol/relais.cgi?relais=
2
&action=
flashing
http://
172.16.9.222
/cgi-bin/remotecontrol/relais.cgi?relais=
1
&action=
dooropener&dooropenertimer=4
http://<User>:<PW>@<IP-Adr.>/cgi-bin/remotecontrol
/
button.cgi?button=<button>
