Operational Features
41-001160-03, Rev 00, Releaes 2.4
5-345
Configuring Operational Features
XML Softkey URI
In addition to specifying variables for the Action URIs, you can also specify
variables in the XML softkey URIs that are bound when the key is pressed. These
variables are the same as those used in the Action URIs.
When an administrator enters an XML softkey URI either via the Aastra Web UI
or the configuration files, they can specify the following variables:
•
$$SIPUSERNAME$$
•
$$SIPAUTHNAME$$
•
$$PROXYURL$$
•
$$LINESTATE$$
•
$$LOCALIP$$
•
$$REMOTENUMBER$$
•
$$DISPLAYNAME$$
•
$$SIPUSERNAME$$
•
$$INCOMINGNAME$$
•
$$CALLDURATION$$
•
$$CALLDIRECTION$$
When the softkey is pressed, if the phone finds a URI configured with variables
(in the form $$VARIABLENAME$$), they are replaced with the value of the
appropriate variable. After all of the variables are bound, the softkey executes a
GET on the URI.
Example
For example, if the administrator specifies an XML softkey with the value:
http://10.50.10.140/script.pl?name=$$SIPUSERNAME$$
This softkey executes a GET on:
http://10.50.10.140/script.pl?name=42512
assuming that the sip username of the specific line is 42512.
Note:
For a description of each variable in the above list, see
“Variable Descriptions”
on
page 5-327
.
Draft 1
Summary of Contents for 675i Series
Page 4: ...D r a f t 1 ...
Page 26: ...Non Blocking HTTP Connections F 90 XML SIP Notify F 91 Limited Warranty D r a f t 1 ...
Page 30: ...D r a f t 1 ...
Page 70: ...D r a f t 1 ...
Page 90: ...D r a f t 1 ...
Page 745: ...D r a f t 1 ...
Page 1026: ...D r a f t 1 ...
Page 1068: ...D r a f t 1 ...
Page 1072: ...D r a f t 1 ...
Page 1076: ...D r a f t 1 ...
Page 1182: ...Index 12 41 001160 00 Release 2 2 Rev 05 Index D r a f t 1 ...
Page 1183: ...D r a f t 1 ...