Bugs item #1882625, was opened at 2008-01-30 15:47
Message generated for change (Settings changed) made by staipale
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1882625&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.3.x
Status: Open
Resolution: None
Priority: 5
>Private: Yes
Submitted By: Taiffu (staipale)
Assigned to: Nobody/Anonymous (nobody)
Summary: Presence watcher are not setting active

Initial Comment:
We do have a problem when using the presence with OpenXCAP 0.97 and OpenSER 
(currently development release from SVN date: 17.01.2008). When sending the 
SUBSCRIBE message from the Client 1 the OpenXCAP updates the xcap and watchers 
tables in database, but the watchers.status for the subscribe request is set as 
"2" which is pending state. Once the Client 2 gets the subscibe request, it 
allows the buddy request and the database updates xcap and watchers tables, and 
the watchers.status is updated to be "1" which is "active", just like it should 
be.

The problem is that the Client 1's, which actually tries to add Client 2 to 
it's buddy, watchers.status is set to pending and never set to active. If I 
have understood this correctly, the status should be set to "1" automatically, 
because the Client 1 is the one which makes the SUBSCRIBE message. The result 
is that the Client 2 sees the status of Client 1, but Client 1 can not see 
status of Client 2.

Could this be OpenSER configuration error in our servers or could this be error 
in Clients SUBSCRIBE message ?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1882625&group_id=139143

_______________________________________________
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/devel

Reply via email to