Specifications

PA-001011-03-04 Aastra July 2014
215
sip notify aastra-xml 200 201….
Where 200, 201… are the SIP peers for the Aastra SIP phones.
This will trigger the action uri xml sip notify if it has been enabled and properly configured.
6.3 “Answer” and “Ignore” keys for action uri incoming
When a UI XML object is displayed as an answer to an action uri incoming, the regular contextual
keys (“Answer” and “Ignore”) are not displayed as the display is managed by the XML object, the
user can only take the call by pressing the blinking line key or go off-hook.
To keep a consistent behavior of the phone after an action uri incoming, the “allowAnswer” tag
allows the native interactive keys “Answer” and “Ignore” to be displayed and allow the user to
answer the call.
Once the call is answered or ignored, the 2 keys disappear automatically.
6.4 “Drop”, “Xfer” and “Conf” keys for XML apps in connected state
When a UI XML object is displayed as with the phone in a connected state, the regular contextual
keys (“Drop”, “Xfer” and “Conf”) are overridden by the XML object, the user cannot access anymore
to these telephony features.
To keep a consistent behavior of the phone when the phone is connected, 3 tags have been
introduced:
 allowDrop
 allowXfer
 allowConf
When they are enabled the native interactive keys are displayed on top of the XML object.
Once the call is ended, the 3 keys disappear automatically.
6.5 Applications
Action URIs are very powerful as they allow an external application to take control of the display
when an event occurs.
Here are some examples of potential applications.
Self-configuration
Using the startup URI, it is possible to develop self-provisioning on the phone. If a new phone boots
and gets its configuration server IP address (through DHCP option 66 for example), it can
download the aastra.cfg file with a startup URI set to an XML application, as it is a new phone
the <MAC>.cfg config files does not exist. At the end of the boot, the phone will go to this XML
application which can identify the phone and then generate the <MAC>.cfg file “on the fly” and ask
the phone to reboot using the PhoneExecute object.
Screen pop
Using the action uri incoming, it is possible to display extra information on the phone for an
incoming call. For instance, the XML application that is called when there is an incoming call can
do a database lookup (Microsoft Exchange or any database) and display information on the caller.
Basically it is like having a screen pop application directly on the phone.