The following are examples of subscribe and notify events using UA-profile:
SUBSCRIBE sip:service@1.2.3.4:5060 SIP/2.0 Via: SIP/2.0/TCP 5.6.7.8:5060 From: <sip:user1@5.6.7.8:5060>;tag=1 To: <sip:john.doe@us.example.com> Call-ID: 1.4192.3.4.5.6@call.id Event: ua-profile;profile-type="application" Max-Forwards: 70 CSeq: 1 SUBSCRIBE P-Asserted-Identity: "John Doe" <sip:john.doe@us.example.com> Privacy: none Expires: 3600 Accept: application/xcap-diff+xml Contact: sip:user1@5.6.7.8:5060 Content-Length: 0
Change notification for UA-profile events are enabled by the sendUAProfileChangeLog resource environment provider, which is disabled by default. UA-profile events subscriptions and notifications are limited to XDMS documents and any change in a document will result in a notification.
<add sel="resource-lists/list"><entry uri="buddy1@us.example.com"></entry></add>
NOTIFY sip:user1@5.6.7.8:5060 SIP/2.0 Event: ua-profile;profile-type="application";vendor="ibm";model="xdms";version="7.0"; auid="resource-lists";document="users/sip:joe@us.example.com/mydocument.xml" From: <sip:john.doe@us.example.com>;tag=6211624529223376_local.1149543099406_2_2 To: <sip:user1@5.6.7.8:5060>;tag=1 Call-ID: 11.4192.3.4.5.6@call.id Max-Forwards: 70 CSeq: 1 NOTIFY Content-Type: application/xcap-diff+xml Content-Length: 285 Via: SIP/2.0/TCP 1.2.3.4:5060;branch=z9hG4bK655017094028370 Contact: <sip:1.2.3.4:5060;transport=tcp> Subscription-State: active <?xml version="1.0" encoding="UTF-8"?> <xcap-diff xmlns="urn:ietf:params:xml:ns:xcap-diff" xcap-root="http://MyHost:9080/services/"> <document new-etag="MTE0OTU0MzIxNjkxNQ==" doc-selector="resource-lists/users/sip:john.doe@us.example.com/MyBuddies.xml" previous-etag="MTE0OTU0MzIxNjkxNQ=="> <change-log> <add sel="resource-lists/list"><entry uri="buddy1@us.example.com"></entry></add> </change-log> </document> </xcap-diff>