IP Phone Release Notes 1.4.1
New Features in 1.4.1
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
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=
You can configure this feature via the configuration files or the Aastra Web UI.
Configuring via the Configuration Files
You use the following parameters in the configuration files to configure the XML: action URI.
Parameter – | Aastra Web UI | Advanced |
action uri startup | Configuration Files | aastra.cfg, <mac>.cfg |
Startup |
|
|
(in Web UI) |
|
|
|
| |
Description | Specifies the URI for which the phone executes a GET on when a startup | |
| event occurs. |
|
|
|
|
Format | Fully qualified URI |
|
|
|
|
Default Value | Not Applicable |
|
|
| |
Range | Up to 128 ASCII characters | |
|
| |
Example | action uri startup: http://10.50.10.140/startup | |
|
|
|
26 |
