Aastra Telecom 41-001343-02 manual Example of a SIP Notify with XML Content

Operational Features

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/SampleText- Screen.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 AastraIPPhoneExe- cute is used, the embedded URI(s) can not be HTTPS based.

Example of a SIP NOTIFY without 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: 0

When the phone receives the SIP NOTIFY, it will trigger the action uri xml sip notify parameter, if it has been previously configured using the configuration files or the Aastra Web UI. If the action uri xml sip notify parameter is not configured, the phone does not do anything.

On the phone side, a System Administrator can enable or disable this SIP NOTIFY feature using the configuration files or the phone Web UI.

41-001343-02 REV04 – 05.2014 5-259