Juha Heinanen writes: i stole some code from opensips and normalized the rls-services uri. after that, the match was found: May 1 22:15:45 siika /usr/sbin/pres-serv[29546]: INFO: rls [subscribe.c:213]: searching document for user sip:jh@test.tutpro.com May 1 22:15:45 siika /usr/sbin/pres-serv[29546]: INFO: rls [subscribe.c:298]: rls_services document:#012<?xml version='1.0' encoding='UTF-8'?>#012<rls-services xmlns="urn:ietf:params:xml:ns:rls-services"><service uri="sip%3Ajh%2Bpresence%40test.tutpro.com"><resource-list&… uri="sip%3Ajh%2Bdialog%40test.tutpro.com"><resource-list>… May 1 22:15:45 siika /usr/sbin/pres-serv[29546]: INFO: rls [subscribe.c:149]: comparing xcap doc uri <sip:jh+presence@test.tutpro.com> to uri <sip:jh+presence@test.tutpro.com> May 1 22:15:45 siika /usr/sbin/pres-serv[29546]: INFO: rls [subscribe.c:154]: uris matched that, however, didn't get me much further. next i got error: May 1 22:15:45 siika /usr/sbin/pres-serv[29546]: ERROR: rls [notify.c:1171]: resource list 'http%3A//192.98.102.10%3A8080/xcap-root/resource-lists/users/sip%3Ajh%40test.tutpro.com/index/%7E%7E/resource-lists/list%5B%40name%3D%22sipsimple_presence_rls%22%5D' is unidentifiable the reason this time is escaped http uri, because uri scheme comparison does not take into account escaped : char. in rls/notify.c: #define HTTP_PREFIX "http://" #define HTTP_PREFIX_LEN 7 ... if(strncmp(uri, HTTP_PREFIX, HTTP_PREFIX_LEN) == 0) looks like there is lots of work to be done on rls module before these things are sorted out. -- juha

On 5/2/13 7:16 PM, Juha Heinanen wrote: You statement is simply misinforming and creates confusion without a real foundation ... with a minimum effort you could have spotted a large amount of development that happened lately related to presence extensions, some of then not existing in any other server side software (to my knowledge). Over the past two years, presence probably accounts more than 30% of the development activity. I run presence services in quite large deployments, going smooth for past few years. I never used rls due to lack of client side support, but presence, xcap server and the other related modules work stable and are up to date. If you find an issue that you cannot solve, fire a report on the bug tracker. It will be picked up by a developer at some point in spare time, if you are under pressure, you can get to other solutions like finding software consultant to do it for you, it is open source. That will never happen. My business model is to deploy Kamailio based solutions meeting requirements specified by customers, meaning that most of them come when they are sure Kamailio is the right application and there is no better alternative, that happened with last presence services deployments. Try to actually look at the features and even more, do some performance and stability tests of such services over tcp/tls. Personally I rarely develop features that I don't need, but I fix issues that don't affect me as much as the time allows. My spare time doesn't go in comparing other similar products, there is always something more interesting to do, but I am pretty sure there is no better framework at this time to deploy SIMPLE presence extensions than Kamailio. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013 * http://asipto.com/u/katu *

Juha Heinanen writes: i just committed a patch to rls module (master version) that added support for escaped chars in rls services document. is it ok to cherry-pick the commit also to 4.0? to me it looks like a bug fix. -- juha

Daniel-Constantin Mierla writes: i tested it with xcap documents generated by sipclients, which should be available also for macosx if you need access to rls capable sip client. -- juha