Filter
Top Products
Operational Features
41-001160-03, Rev 00, Releaes 2.4 5-329
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
$$CALLDIRECTION$$
Note: This variable allows for
enhanced information in call
records and billing applications.
Specifies whether the current/last call was incoming or outgoing. This
variable is associated with:
• onhook
$$REGISTRATIONSTATE$$ Specifies the state of the phone’s registration. Registration states can
be:
•registered
• unregistered
•expired
• refused
• timeout
$$REGISTRATIONCODE$$ Specifies the code generated during the registration process.
Registration code can be:
"xxx"
where xxx is the 3 digit code; for example, "403". Possible codes are:
• 001 (registration successful)
• 403 (registration failed)
Variable Description
Draft 1