<div dir="ltr">I moved rls_handle_notify() to top of route - it helped. First test is ok.<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 25, 2012 at 8:05 PM, Dmytro Bogovych <span dir="ltr"><<a href="mailto:dmytro.bogovych@gmail.com" target="_blank">dmytro.bogovych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi.</div>I still try to setup RLS capable kamailio instance.<div>Now the server accepts my services and resource list documents.</div>
<div>It generated backend subscriptions - i can see it in pua table.</div>
<div>When another peer publish its presence - presence tries to send notify to sip address specified in modparam("rls", "server_address", "<a href="mailto:sip%3Arls@sip.voipobjects.com" target="_blank">sip:rls@sip.voipobjects.com</a>").</div>
<div><br></div><div>But the notify does not come back to rls - it is rejected by somewhere in core or other module with error 404.</div><div><br></div><div>I tried to create the <a href="mailto:rls@sip.voipobjects.com" target="_blank">rls@sip.voipobjects.com</a> user - it did not help.</div>
<div><br></div><div>May anyone give me advice?</div><div><br></div><div><br></div><div><br></div></div>
</blockquote></div><br></div>