Hello,
On 6/19/12 4:49 PM, Min Wang wrote:
Hi
Here is another similar case which does not work. maybe it is related the above issue as well.
Jitsi 1.1 client: 101/103 , with xcap as storage proxy: kamailio 3.3 ip network is: 192.168.122.0
the setup is like the following:
101(.224) --- proxy (.32) --- 103 (.1)
After all presence related db are truncated, kamailio was restart. then bring 101,103 online.
On 101 add 103, 103 prompt up authorization window, click ok. now on 103, I can see 101 online status
but on 101, I can not see 103 status <----the first trace file: the jitsi-101-add-103-confirm-2.pcap
(it is grey, even manually change 103 status from online to away etc, on 101, the 103 always showed grey. <--- second trace file: jitsi-101-103-change.pcap)
Please see the attached pcap files.
the watcher table shows:
id presentity_uri watcher_username watcher_domain
event status reason inserted_time 1 sip:103@192.168.122.32 101 192.168.122.32 presence 2 1340114579 2 sip:101@192.168.122.32 103 192.168.122.32 presence 1 1340114582
the first record above shows that the status is 2, which means 'pending'. The subscription of 101 was not accepted yet by presentity 103.
For the second record, status is 1, which means active subscription.
Cheers, Daniel
HI
the watcher table shows:
id presentity_uri watcher_username watcher_domain
event status reason inserted_time 1 sip:103@192.168.122.32 101 192.168.122.32 presence 2 1340114579 2 sip:101@192.168.122.32 103 192.168.122.32 presence 1 1340114582
the first record above shows that the status is 2, which means 'pending'. The subscription of 101 was not accepted yet by presentity 103.
Yes. but Why ?
min
For the second record, status is 1, which means active subscription.
Cheers, Daniel -- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw
Hello,
On 6/20/12 12:08 PM, Min Wang wrote:
HI
the watcher table shows:
id presentity_uri watcher_username watcher_domain
event status reason inserted_time 1 sip:103@192.168.122.32 101 192.168.122.32 presence 2 1340114579 2 sip:101@192.168.122.32 103 192.168.122.32 presence 1 1340114582
the first record above shows that the status is 2, which means 'pending'. The subscription of 101 was not accepted yet by presentity 103.
Yes. but Why ?
accepting a new watchers is done via http/xcap, have you seen that operation done by 103 for 101? You have to call also the function to update and refresh the watchers.
Cheers, Daniel
HI On 06/20/2012 12:20 PM, Daniel-Constantin Mierla wrote:
accepting a new watchers is done via http/xcap, have you seen that operation done by 103 for 101? You have to call also the function to update and refresh the watchers.
According to the trace, jitsi (103) did not send out any xcap after it authorized/accepted/added the contact.
see: http://lists.sip-router.org/pipermail/sr-users/2012-June/073664.html
so it is jitsi bug?
or should we call update and refresh the watchers after the handle_subscribe()?
min
Cheers, Daniel