Filter
Top Products
Operational Features
41-001160-01, Rev 00, Release 2.3 5-313
Configuring Operational Features
How it works
When a startup, successful registration, incoming call, outgoing call,
offhook, or onhook call event occurs
on the phone, the phone checks to see if
the event has an action URI configured. If the phones finds a URI configured, any
variables configured (in the form $$VARIABLENAME$$) are replaced with the
value of the appropriate variable. After all of the variables are bound, the phone
executes a GET on the URI. The Action URI binds all variables and is not
dependant on the state of the phone.
For example, if you enter the following string for the action uri outgoing
parameter:
action uri outgoing: http://10.50.10.140/
outgoing.pl?number=$$REMOTENUMBER$$
and you dial out the number 5551212, the phone executes a GET on:
http://10.50.10.140/outgoing.pl?number=5551212
You can configure this feature via the configuration files or the Aastra Web UI.
Configuring XML Action URIs
Use the following procedures to configure XML Action URIs using the
configuration files or the Aastra Web UI.
Note: If the phone can’t find the Action URI you specify, it returns a
“NULL” response. For example,
http://10.50.10.140/outgoing.pl?number=
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Action URI
Settings” on page A-130.