Aastra Telecom REV 06 SIP Notify Triggers an XML Event, Example of a SIP Notify with XML Content

5i Series IP Phone Release Notes

Features in Release 2.2

XML Features

SIP NOTIFY Triggers an XML Event

In order for an XML push to bypass the NAT/firewall, in Release 2.2 the phone now supports a proprietary SIP NOTIFY event (aastra-xml) with or without XML content.

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.

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.

RN-001029-00, Rev 06, Release 2.2 91