#128 Presence SUBSCRIBE returns in-correct CONTACT header in 200O

1.4.x
closed-invalid
Anca Vamanu
modules (454)
5
2009-08-03
2009-04-07
Jim Burke
No

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

Discussion

  • Jim Burke
    Jim Burke
    2009-04-07

    Bad Subscribe

     
    Attachments
  • Anca Vamanu
    Anca Vamanu
    2009-04-08

    • assigned_to: nobody --> anca_vamanu
     
  • Anca Vamanu
    Anca Vamanu
    2009-04-08

    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

     
  • Anca Vamanu
    Anca Vamanu
    2009-08-03

    • status: open --> open-invalid
     
  • Anca Vamanu
    Anca Vamanu
    2009-08-03

    • status: open-invalid --> closed-invalid