Specifications

PA-001011-03-04 Aastra July 2014
213
6.2.7 Action uri startup
The action uri startup is triggered at the end of the phone boot sequence.
6.2.8 Action uri registered
The action uri registered is triggered the first time the phone registers successfully a line to its SIP
proxy/registrar.
If the phone has multiple SIP registration, the action uri registered is triggered for each line.
6.2.9 Action uri registration event
The action uri registration event is triggered every time there is a registration state change, the
registration states are:
 Registered
 Unregistered
 Registration timed out
 Registration refused
 Registration expired
The action uri registration event is not triggered when the same event is repeated.
Two URI variables have also been added to complement this feature
 $$REGISTRATIONSTATE$$
 $$REGISTRATIONCODE$$
See chapter 5.2 for more details on these variables.
6.2.10 Action uri poll
The action uri poll is called each time the configured timer (action uri poll interval parameter)
expires.
The first timer starts at the end of the phone boot sequence.
6.2.11 Action uri xml sip notify
The action uri xml sip notify is triggered when the phone receives an authorized SIP Notify aastra-
xml event with an empty content. The XML call is triggered only if the sip xml notify event
parameter is set to 1 (enabled). See chapter 6.2.11 for more details on the configuration.
 If a XML content is provided in the SIP NOTIFY, it is processed directly by the phone as it
is done for a XML PUSH
 If the content is empty in the SIP NOTIFY, the phone automatically triggers a new pre-
configured action uri (action uri xml sip notify).
Example of a SIP NOTIFY with XML content
NOTIFY sip:200@10.30.100.103:5060 SIP/2.0
Via: SIP/2.0/UDP 10.30.100.103:5060;branch=z9hG4bK7bbc1fac;rport
From: <sip:201@10.30.100.103:5060>;tag=81be2861f3
To: Jacky200 <sip:200@10.30.100.103:5060>
Contact: <sip:201@10.30.100.103>
Call-ID: 59638f5d95c9d301
CSeq: 4 NOTIFY