[OpenSIPS-Users] A little XCAP schema help

duane.larson at gmail.com duane.larson at gmail.com
Thu Apr 5 18:03:03 CEST 2012


I am having the following issue

Jitsi phone user 9016XX6XX4 is configured with Presence to monitor  
9013XX3XX6 Snom Phone. I used Soap-Simple-Proxy to set up XCAP rules so  
that both users have permissions to view each others presence. Because I  
used Soap-Simple-Proxy to create rules everything works fine. Here is what  
is in XCAP

| 1555 | 9013XX3XX6 | irock.com | <?xml version="1.0" encoding="UTF-8"?>
<ruleset xmlns="urn:ietf:params:xml:ns:common-policy"  
xmlns:pr="urn:ietf:params:xml:ns:pres-rules"  
xmlns:cp="www.counterpath.com/privacy-lists"><rule  
id="pres_whitelist"><conditions><identity><one  
id="sip:9016XX6XX4 at irock.com"/></identity></conditions><actions><pr:sub-handling>allow</pr:sub-handling></actions>
<transformations>
<pr:provide-services>
<pr:all-services/>
</pr:provide-services>
<pr:provide-persons>
<pr:all-persons/>
</pr:provide-persons>
<pr:provide-devices>
<pr:all-devices/>
</pr:provide-devices>
<pr:provide-all-attributes/>
</transformations></rule></ruleset> | 2 | 1def73bc3d7e509b840d5d96292e12c7  
| 0 | index.xml | 0 |


| 1554 | 9016XX6XX4 | irock.com | <?xml version="1.0" encoding="UTF-8"?>
<ruleset xmlns="urn:ietf:params:xml:ns:common-policy"  
xmlns:pr="urn:ietf:params:xml:ns:pres-rules"  
xmlns:cp="www.counterpath.com/privacy-lists"><rule  
id="pres_whitelist"><conditions><identity><one  
id="sip:9016XX6X54 at irock.com"/><one  
id="sip:9013XX3XX6 at irock.com"/></identity></conditions><actions><pr:sub-handling>allow</pr:sub-handling></actions>
<transformations>
<pr:provide-services>
<pr:all-services/>
</pr:provide-services>
<pr:provide-persons>
<pr:all-persons/>
</pr:provide-persons>
<pr:provide-devices>
<pr:all-devices/>
</pr:provide-devices>
<pr:provide-all-attributes/>
</transformations></rule></ruleset> | 2 | 23318e100042f0084231b010d44eb00f  
| 0 | index.xml | 0 |



So here is the issue I see.....
Yesterday I had a Jitsi phone user 9016XX6X54 add a buddy (9016XX6XX4). So  
this time I didn't create the permission rules for user 9016XX6X54 with  
Soap-Simple-Proxy but instead let the Jitsi client create the rules and PUT  
the rules in the XCAP server. When 9016XX6X54 makes a call the 9016XX6XX4  
user doesn't see that he is making a call. The same thing happens if  
9016XX6XX4 makes a call, 9016XX6X54 doesn't see that the other user is not  
on the phone. I see that they NOTIFY messages are being sent to the Jitsi  
client and the client replies back with 200 OK but the Jitsi client doesn't  
change the users icon to show they are being called or on the phone.

Here is the XCAP entry that the Jitsi client created

| 1559 | 9016XX6X54 | irock.com | <?xml version="1.0" encoding="UTF-8"  
standalone="no"?><ruleset  
xmlns="urn:ietf:params:xml:ns:common-policy"><rule  
id="pres_whitelist"><conditions><identity><one  
id="sip:9016XX6XX4 at irock.com"/><one  
id="sip:5XX5XX6XX5 at irock.com"/></identity></conditions><actions><sub-handling  
xmlns="urn:ietf:params:xml:ns:pres-rules">allow</sub-handling></actions><transformations><provide-devices  
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-devices/></provide-devices><provide-persons  
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-persons/></provide-persons><provide-services  
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-services/></provide-services><pr:provide-all-attributes  
xmlns:pr="urn:ietf:params:xml:ns:pres-rules"/></transformations></rule></ruleset>  
| 2 | 28f8580993ab4502aa0565605c055907 | 0 | index.xml | 0 |

So obviously there are a lot of differences between the entry that  
Soap-Simple-Proxy created and what the Jitsi client created (like in the  
Jitsi ruleset it only has "common-policy" and not "pres-rules"). So I am  
thinking that Jitsi's schema is missing some stuff. Would I be correct in  
my thinking?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120405/cae64f09/attachment.htm>


More information about the Users mailing list