[SR-Users] pua 'Could not convert temporary dialog into a dialog' error

Juha Heinanen jh at tutpro.com
Sun Sep 9 15:00:22 CEST 2012


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:jh at test.fi subscribe on sip:jh-buddies at test.fi, it does NOT generate
notify to it before it has subscribed both  members of the list
(sip:test at test.fi and sip:foo at test.fi) and gotten notify from both of
them:

Sep  9 13:41:42 siika /usr/sbin/sip-proxy[7469]: INFO: SUBSCRIBE <sip:jh-buddies at test.fi> by <jh at test.fi> as <sip:jh at 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-buddies at test.fi> to presence server
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: Handling SUBSCRIBE <sip:jh-buddies at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7692]: INFO: Routing locally generated SUBSCRIBE <sip:test at test.fi> to <sip:test at test.fi> from <sip:jh at 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:foo at test.fi> to <sip:foo at test.fi> from <sip:jh at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling SUBSCRIBE <sip:test at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Routing locally generated NOTIFY <sip:rls at 127.0.0.1:5082;transport=tcp> to <sip:jh at test.fi> from <sip:test at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: presence [notify.c:1581]: NOTIFY sip:jh at test.fi via sip:rls at 127.0.0.1:5082;transport=tcp on behalf of sip:test at test.fi for event presence
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling SUBSCRIBE <sip:foo at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Routing locally generated NOTIFY <sip:rls at 127.0.0.1:5082;transport=tcp> to <sip:jh at test.fi> from <sip:foo at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: presence [notify.c:1581]: NOTIFY sip:jh at test.fi via sip:rls at 127.0.0.1:5082;transport=tcp on behalf of sip:foo at test.fi for event presence
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling in-dialog NOTIFY <sip:rls at 127.0.0.1:5082;transport=tcp> from <sip:test at test.fi> to <sip:jh at test.fi>
Sep  9 13:41:42 siika /usr/sbin/pres-serv[7693]: INFO: Handling in-dialog NOTIFY <sip:rls at 127.0.0.1:5082;transport=tcp> from <sip:foo at test.fi> to <sip:jh at test.fi>
Sep  9 13:41:44 siika /usr/sbin/pres-serv[7690]: INFO: Routing locally generated NOTIFY <sip:rbjfhkmc at 192.98.103.10:40359;alias=192.98.103.10~41792~2;transport=tcp> to <sip:jh at test.fi> from <sip:jh-buddies at 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 at 192.98.103.10:40359;transport=tcp> from <sip:jh-buddies at test.fi> to <sip:192.98.103.10:41792;transport=tcp>

the notify to sip:jh at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcap2.pcap
Type: application/octet-stream
Size: 17064 bytes
Desc: rls test with rls db_mode=2
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120909/bcf6e41d/attachment-0001.obj>


More information about the sr-users mailing list