peter, when rls db_mode=2, the test described in previous email works fine and very differently as in the case when db_mode=0.
the difference is that after presence/rls server receives from sip:j...@test.fi subscribe on sip:jh-budd...@test.fi, it does NOT generate notify to it before it has subscribed both members of the list (sip:t...@test.fi and sip:f...@test.fi) and gotten notify from both of them: Sep 9 13:41:42 siika /usr/sbin/sip-proxy[7469]: INFO: SUBSCRIBE <sip:jh-budd...@test.fi> by <j...@test.fi> as <sip:j...@test.fi> from <192.98.103.10> is authorized Sep 9 13:41:42 siika /usr/sbin/sip-proxy[7469]: INFO: Routing SUBSCRIBE <sip:jh-budd...@test.fi> to presence server Sep 9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: Handling SUBSCRIBE <sip:jh-budd...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: Routing locally generated SUBSCRIBE <sip:t...@test.fi> to <sip:t...@test.fi> from <sip:j...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: <core> [tcp_main.c:2787]: quick connect for 0x7f091036c340 Sep 9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: Routing locally generated SUBSCRIBE <sip:f...@test.fi> to <sip:f...@test.fi> from <sip:j...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling SUBSCRIBE <sip:t...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Routing locally generated NOTIFY <sip:rls@127.0.0.1:5082;transport=tcp> to <sip:j...@test.fi> from <sip:t...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: presence [notify.c:1581]: NOTIFY sip:j...@test.fi via sip:rls@127.0.0.1:5082;transport=tcp on behalf of sip:t...@test.fi for event presence Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling SUBSCRIBE <sip:f...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Routing locally generated NOTIFY <sip:rls@127.0.0.1:5082;transport=tcp> to <sip:j...@test.fi> from <sip:f...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: presence [notify.c:1581]: NOTIFY sip:j...@test.fi via sip:rls@127.0.0.1:5082;transport=tcp on behalf of sip:f...@test.fi for event presence Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling in-dialog NOTIFY <sip:rls@127.0.0.1:5082;transport=tcp> from <sip:t...@test.fi> to <sip:j...@test.fi> Sep 9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling in-dialog NOTIFY <sip:rls@127.0.0.1:5082;transport=tcp> from <sip:f...@test.fi> to <sip:j...@test.fi> Sep 9 13:41:44 siika /usr/sbin/pres-serv[7690]: INFO: Routing locally generated NOTIFY <sip:rbjfhkmc@192.98.103.10:40359;alias=192.98.103.10~41792~2;transport=tcp> to <sip:j...@test.fi> from <sip:jh-budd...@test.fi> Sep 9 13:41:44 siika /usr/sbin/pres-serv[7690]: INFO: <core> [tcp_main.c:2787]: quick connect for 0x7f09103bad18 Sep 9 13:41:44 siika /usr/sbin/sip-proxy[7475]: INFO: Routing in-dialog NOTIFY <sip:rbjfhkmc@192.98.103.10:40359;transport=tcp> from <sip:jh-budd...@test.fi> to <sip:192.98.103.10:41792;transport=tcp> the notify to sip:j...@test.fi thus contains real presence status of both of the list members. why the behavior changes depending on rls db_mode? pcap of this db_mode=2 test is enclosed. -- juha
pcap2.pcap
Description: rls test with rls db_mode=2
_______________________________________________ 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
