it turned out that presence rls module does not work unless pua module is configured to use database mode and database is postgre. the issue is serious, since besides not working, it makes presence/rls server not to accept any new requests.
since there is no easy cure, should i go and write a warning in rls readme file so that others don't stumble on this?
-- juha
Hi,
It is worth noting that the PUA/RLS behaviour is no worse than it was previously. It's just now you get error messages out where previously you'd have had silent failures.
As I mentioned before, I believe that the "temporary dialog" error you are seeing when not in DB only mode can easily be resolved by moving a couple of locking functions around.
Regards,
Peter
On Tue, 2012-09-11 at 13:26 +0300, Juha Heinanen wrote:
it turned out that presence rls module does not work unless pua module is configured to use database mode and database is postgre. the issue is serious, since besides not working, it makes presence/rls server not to accept any new requests.
since there is no easy cure, should i go and write a warning in rls readme file so that others don't stumble on this?
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Peter Dunkley writes:
As I mentioned before, I believe that the "temporary dialog" error you are seeing when not in DB only mode can easily be resolved by moving a couple of locking functions around.
i don't mind the error message, but if it is that easy to make rls in non-DB mode to work and not lockup presence/rls server, then it would be worth doing. otherwise, in my opinion, a warning is justified.
-- juha
I'm happy to put a candidate fix in, but I won't have time to do any testing of it (and I don't use non DB only mode on any of my systems).
If I get the fix put in sometime today or tomorrow will you be able to test it?
Regards,
Peter
On Tue, 2012-09-11 at 14:13 +0300, Juha Heinanen wrote:
Peter Dunkley writes:
As I mentioned before, I believe that the "temporary dialog" error you are seeing when not in DB only mode can easily be resolved by moving a couple of locking functions around.
i don't mind the error message, but if it is that easy to make rls in non-DB mode to work and not lockup presence/rls server, then it would be worth doing. otherwise, in my opinion, a warning is justified.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Peter Dunkley writes:
I'm happy to put a candidate fix in, but I won't have time to do any testing of it (and I don't use non DB only mode on any of my systems).
If I get the fix put in sometime today or tomorrow will you be able to test it?
peter,
sure, weather is not currently good enough for a fishing trip, so i'm able to give your patch a try immediately.
-- juha
Hi,
There is a candidate fix under this Commit: b0d642016cca83c519ea9aa0e04aa9bf353e07e4
Regards,
Peter
On Tue, 2012-09-11 at 14:40 +0300, Juha Heinanen wrote:
Peter Dunkley writes:
I'm happy to put a candidate fix in, but I won't have time to do any testing of it (and I don't use non DB only mode on any of my systems).
If I get the fix put in sometime today or tomorrow will you be able to test it?
peter,
sure, weather is not currently good enough for a fishing trip, so i'm able to give your patch a try immediately.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Juha Heinanen -
Peter Dunkley