Aastra 9000i Series Administrator's Manual page 593

XML SIP Notify Events
In order for an XML push to bypass the NAT/firewall, the phone supports a proprietary SIP
NOTIFY event (aastra-xml) with or without XML content. An Administrator can enable/disable
the SIP NOTIFY event using a specific parameter in the configuration files (sip xml notify
event) or the Aastra Web UI (XML SIP Notify).
If XML content is provided in the SIP NOTIFY, it is processed directly by the phone as it is done
for an 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
Max-Forwards: 70
Event: aastra-xml
Content-Type: application/xml
Content-Length: 115
<AastraIPPhoneExecute><ExecuteItem URI="http://10.30.100.39/XMLtests/
SampleTextScreen.xml"/></AastraIPPhoneExecute>
When the phone receives the SIP NOTIFY, the XML content is processed as any XML object. In
the above example, the phone calls http://10.30.100.39/XMLtests/SampleTextScreen.xml after
reception of the SIP NOTIFY.
5-316
Note:
The phone supports all the current XML objects with all
the existing limitations. For example if an
AastraIPPhoneExecute is used, the embedded URI(s) can not be
HTTPS based.
41-001343-01 Rev 02, Release 3.2.2