Using the WebUI
80
VSP736 Administrator and Provisioning Manual
Server Application
On the Server Application page, you can enter Action URIs to allow the VSP736 to interact
with a server application by using an HTTP GET request. The action URI triggers a GET
request when a specified event occurs. Action URIs allow an external application to take
control of the display when an event occurs. These pre-defined events are listed under
on the Server Application page.
Action URIs are typically used in conjunction with the XML Browser, which can be
customized to deliver an appropriate user experience.
The VSP736 supports both push and pull server applications. Note that Action URI events
are not “push” events as it is the phone that requests a URI when triggered by certain
states. You can enable push server applications under
Action URI Syntax
To access an XML application, the phone performs an HTTP GET on a URL.
An HTTP GET request may contain a variable name and variable value, which are
separated by "=". Each variable value starts and ends with "$$" in the query part of the URL.
Action URI variables pass dynamic data to the server. The valid URL format is:
http://host[:port]/dir/file name?variable name=$$variable value$$
where:
host is the hostname or IP address of the server supporting the XML application
port is the port number the phones are using for the HTTP request
At the time of the HTTP call, the variable value field is populated with the appropriate data.
For example, the following URL passes the SIP Account User Identifier to the server:
http://10.50.10.140/script.pl?name=$$SIPUSERNAME$$
A GET request then passes along the following information:
http://10.50.10.140/script.pl?name=42512
Assuming that the User Identifier is 42512.
Variable names are defined by the particular XML application being called.
Variable values are predefined and depend on the status of the phone. If the variable has
no meaning in the current status, then the phone sends an empty string.
The table below lists all possible variable values. Note that variables applicable during an
Incoming or Active Call (such as INCOMINGNAME and REMOTENUMBER) are initialized
at the beginning and at the end of the call.
Variable value
Description
SIPUSERNAME
SIP Account User Identifier
DISPLAYNAME
SIP Account Display Name