[SR-Users] Presence with RLS and integrated XCAP on Kamailio 3.3

Hello All, Does anyone have presence working on Kamailio 3.3 with integrated XCAP. In theory my setup should work. I have two clients: Client A: Registers with the presence server Subscribe 1 - event = reg Subscribe 2 - event = presence.winfo Subscribe 3 - event = presence Publishes its status I see entries in the foll databases for A: Active Watchers DB: presence, presence.winfo, and reg event entries Watchers DB: No entries Presentity: presence, reg, and presence???? entries PUA list: 1 entry RLS watchers: No entries RLS presentity list: No entries XCAP List: 3 entries - rls services, resource list, and pres rules Client B: Registers with the presence server Subscribe 1 - event = presence.winfo Subscribe 2 - event = presence Subscribe 3 - event = message-summary Publishes its status I see entries in the foll databases for B: Active Watchers DB: message-summary, presence.winfo Watchers DB: 1 entry - with B as the presentity and A as the watcher Presentity: reg, presence PUA list: 1 entry RLS watchers: No entries RLS presentity list: No entries XCAP List: 2 entries resource-lists, pres rules My first question is - Is this all correct or is something going missing? Now the real problem: When Client A adds Client B to it's contact list, on Client A I see the following message: Client B Package (presence), Pending (Subscribe). This information from what I gather is coming back from the periodic notifies for the server because of the presence.winfo event. However, the notify going out to Client B does not have any indication that Client A is a watcher and needs to be authorized. This should be the case per RFC 3857. Excerpts from notifies to client A and client B: Client A NOTIFY sip:8475551001@10.51.2.181:58150;transport=udp SIP/2.0 Via: SIP/2.0/UDP 10.50.251.12;branch=z9hG4bKdcef.e5df11e.0 To: sip:8475551001@10.50.251.12;tag=1988526 From: sip:8475551001@10.50.251.12;tag=a6a1c5f60faecf035a1ae5b6e96e979a-c52c CSeq: 3 NOTIFY Call-ID: 19607474-addd-0ffb-a9da-031235052e9d Content-Length: 347 User-Agent: kamailio (3.3.1 (x86_64/linux)) Max-Forwards: 70 Event: presence.winfo Contact: <sip:10.50.251.12:5060;transport=udp> Subscription-State: active;expires=3180 Content-Type: application/watcherinfo+xml <?xml version="1.0"?> <watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="2" state="partial"> <watcher-list resource="sip:8475551001@10.50.251.12" package="presence"> <watcher id=&quot;9e65d804dbc4fc269c5f1d2f6eae0650(a)0.0.0.0&quot; event="subscribe" status="pending">sip:8475551002@10.50.251.12</watcher> </watcher-list> </watcherinfo> Client B: NOTIFY sip:8475551002@10.50.0.113:5060;transport=udp;registering_acc=10_50_251_12 SIP/2.0 Via: SIP/2.0/UDP 10.50.251.12;branch=z9hG4bK7f71.6fca9e81.0 To: sip:8475551002@10.50.251.12;tag=a30db42f From: sip:8475551002@10.50.251.12;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6692 CSeq: 3 NOTIFY Call-ID: f71666432f236f38c7c4dc467b4483e0(a)0.0.0.0 Content-Length: 195 User-Agent: kamailio (3.3.1 (x86_64/linux)) Max-Forwards: 70 Event: presence.winfo Contact: <sip:10.50.251.12:5060;transport=udp> Subscription-State: active;expires=3600 Content-Type: application/watcherinfo+xml <?xml version="1.0"?> <watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="2" state="full"> <watcher-list resource="sip:8475551002@10.50.251.12" package="presence"/> </watcherinfo> Also the frequency of notifies to client B is a lot less for event: presence.winfo. Any help is greatly appreciated since I've been trying to get presence to work for a few weeks now and keep running into new problems. Thanks, Sangeeta -- Sangeeta Shah