Send Request Via Http/Https (V2) - Siemens OpenStage 15 Administration Manual

3.6.19

Send Request via HTTP/HTTPS (V2)

With this function, the phone can send a specific HTTP or HTTPS request to a server. The func-
tion is available at any time, irrespective of registration and call state. Possible uses are HTTP-
controlled features on the SIP server, e. g. hunt group login/logout, or functions on a web server
that can only be triggered by HTTP/HTTPS request, e. g. login/logout for flexible working hours.
The Protocol parameter defines whether HTTP or HTTPS is to be used for sending the URL
to the server.
The Web server address is the IP address or DNS name of the remote server to which the
URL is to be sent.
The Port is the target port at the server to which the URL is to be sent.
The Path is the server-side path to the desired function, i. e. the part of the URL that follows
the IP address or DNS name. Example: webpage/checkin.html
In the Parameters field, one or more key/value pairs in the format "<key>=<value>" can be
added to the request, separated by an ampersand (&).
Example: phonenumber=3338&action=huntGroupLogon
The question mark will be automatically added between the path and the parame-
>
ters. If a question mark has been entered at the start of the parameters, it will be
automatically stripped off.
The Method parameter determines the HTTP method to be used, which can either be GET or
POST. If GET is selected, the additional parameters (Parameters) and the user id/password
(Web server user ID/Web server password) are part of the URL. If POST is selected, these
data form the body of the message.
In case the web server requires user authentication, the parameters Web server user ID and
Web server password can be used. If not null, the values are appended between the server-
side path (Path) and the additional parameters (Parameter).
If the LED controller URI is given, the LED associated with this key indicates the state of the
call number or SIP URI specified here. This function is similar to the LED function of the BLF
key described in Section 3.6.18, "Monitoring Another Extension Via BLF Key".
Data required
• Key label <n>: Label for the key.
• Protocol: Transfer protocol to be used.
Value range: "HTTP", "HTTPS".
• Web server address: IP address or DNS name of the remote server.
• Port: Target port at the server.
• Path: Server-side path to the function.
A31003-S2000-M102-2-76A9, 28/05/2009
OpenScape Voice - OpenStage Family, Administration Manual
administration.fm
Administration
Programmable Keys
3-73