Specifications

Aastra July 2014 PA-001011-03-04
202
Variable Name
Value
CALLDIRECTION
Direction of the current call (“Incoming” or “Outgoing”)
REGISTRATIONCODE
3 digits registration code for the registration coming from the SIP Proxy
server.
REGISTRATIONSTATE
Registration state available from the Registration event, values are:
 “REGISTERED",
 "UNREGISTERED",
 "EXPIRED",
 "REFUSED",
 "TIMEOUT".
LINESTATE
Information on Disconnect event, values are
 “IDLE”
 “DIALING”
 “CALLING”
 “OUTGOING”
 “INCOMING”
 “CONNECTED”
 “CLEARING”
At the time of the HTTP call, the variables are replaced with the value of the appropriate variable.
The variables are available in all the HTTP URL for programmable/soft keys as well as for the
action URI. They can also be used in the XML objects themselves (TextMenu, InputScreen…) but
not in a PhoneExecute command.
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.
The variables can be used, for instance, in a context where the phone has multiple SIP
registrations and the XML application need to know which SIP registration the phone is currently
using.
Note: the value of a variable depends on the status of the phone, if the variable has no
meaning in the current status; the phone sends an empty string. For example, if the URL is
“http://myserver.com/script.pl?number=$$REMOTENUMBER$$&key=5”, the phone will call
“http://myserver.com/script.pl?number=”&key=5” if the phone is idle.
5.2.1 Variables related to the active line
The following variables are related to the active line
 $$SIPUSERNAME$$ Active line user name
 $$DISPLAYNAME$$ Active line display name