[ opensips-Bugs-2740829 ] Presence SUBSCRIBE returns in-correct CONTACT header in 200O

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[ opensips-Bugs-2740829 ] Presence SUBSCRIBE returns in-correct CONTACT header in 200O

SourceForge.net
Bugs item #2740829, was opened at 2009-04-07 17:13
Message generated for change (Comment added) made by anca_vamanu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2740829&group_id=232389

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: 1.4.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jim Burke (jimbohamez)
>Assigned to: Anca Vamanu (anca_vamanu)
Summary: Presence SUBSCRIBE returns in-correct CONTACT header in 200O

Initial Comment:
This is a follow-up from bug 2354984.  

version: opensips 1.4.5-tls (i386/linux)

Testing presence with Eyebeam and Xlite and found this patch is causing an issue due to the CONTACT header returned from a SUBSCRIBE message.

In sending 200OK with a contact header equal to the opensips server, any subsequent SUBSCRIBE messages use this contact header in the URI and result in 481 Subscription does not exist.  See attached messages.

I'm not sure what the driver was for changing this behaviour, however I think it needs some more investigation.  If you need any further info please advise.

Regards,
Jim



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

>Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-04-08 13:59

Message:
Hi Jim,

There is no problem with the fact that the server puts his contact in
200Ok and the client uses it as R-uri in subsequent Subscribe messages,
This is according with the RFC and works with opensips.
You have interpreted wrongly the trace that you sent. If you look closely,
the two subscribe messages are not inside the same dialog - check for the
To tag which is different in the second Subscribe from the one in 200 OK.
There is another reason why that subscribe is not recognized by the server
- maybe you have stopped the server and cleaned up the database ..

regards,
Anca

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

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2740829&group_id=232389

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel