[Devel] [ openser-Bugs-1684036 ] PRESENCE module and multiple transports issue

[SourceForge.net]

Bugs item #1684036, was opened at 2007-03-20 00:26
Message generated for change (Comment added) made by amr42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1684036&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.2.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Aron Rosenberg (amr42)
Assigned to: anca (anca_vamanu)
Summary: PRESENCE module and multiple transports issue

Initial Comment:
The new PRESENCE module does not seem to take into account the transport, socket or port that a user iniated the SUBSCRIBE on. Consider the following two scenarios that appear to be broken

Server Setup:

IP: 1.1.1.1 udp port 5060
IP: 1.1.1.1 udp port 5062
IP: 1.1.1.1 tcp port 5060

User A connects to the server on 1.1.1.1 udp port 5060, and requests a SUBSCRIBE to User A (himself) and User B


User B connects to the server on 1.1.1.1 tcp port 5060, and requests a SUBSCRIBE to USER A and USER B (himself)


If User A sends a PUBLISH (with 1.1.1.1 udp port 5060), then the subsequent NOTIFY's (to A and B) will go out on 1.1.1.1 udp port 5060 even though User B requested the SUBSCRIPTION via tcp port 5060.

If User B sends a PUBLISH (with 1.1.1.1 tcp port 5060), then both subsequent NOTIFY's will be sent via 1.1.1.1 tcp port 5060.

Summary: Presence module is not saving the transport that the subscribe arrived on and is not using that detail to send out the NOTIFY.

Solution: Add a new column to the active_watchers table called socket (exactly like REGISTRAR module has with location table) and store the incoming socket for the SUBSCRIBE request. This socket would then need to be used when sending out a NOTIFY request.


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

>Comment By: Aron Rosenberg (amr42)
Date: 2007-03-20 17:33

Message:
Logged In: YES 
user_id=43318
Originator: YES

Anca,

 There is a socket member for the dlg_t* that you can pass that would seem
to specify which socket to use.

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

Comment By: anca (anca_vamanu)
Date: 2007-03-20 17:27

Message:
Logged In: YES 
user_id=1614776
Originator: NO

Hello,

The api in tm will have to be extended for this.
Thanks for reporting.

Best regards, 

Anca Vamanu

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

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