#168 rls_handle_subscribe() doesn't allow RURI parameters

trunk
open
modules (454)
2
2009-10-14
2009-08-11
No

Typical conf:
--------------------
modparam("rls", "to_presence_code", 5)

[...]

rls_handle_subscribe();
if ($retcode==5) {
#RLS indicated that message should be processed by presence.
handle_subscribe();
}
exit;
--------------------

If the SUBSCRIBE arrives with a parameter in the RURI (i.e; sip:alice@example.org;transport=tcp) then "rls_handle_subscribe()" doesnt' return 5 and the normal subscription is not performed.

Of course, removing the RLS stuf the normal subscription works perfectly as it should.

Discussion

  • Anca Vamanu

    Anca Vamanu - 2009-08-11

    Hi Inaki,

    Can you check if there is an error message in the log?

    regards,
    Anca

     
  • Anca Vamanu

    Anca Vamanu - 2009-08-11
    • assigned_to: nobody --> anca_vamanu
     
  • Iñaki Baz Castillo

    I've added a xlog to display the $retcode after rls_handle_subscribe():

    *** rls_handle_subscribe() for sip:eyebeam2@example.net => rc = 5 ***
    *** rls_handle_subscribe() for sip:alice@example.net => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:eyebeam@example.net;transport=tcp => rc = 5 ***
    *** rls_handle_subscribe() for sip:xlite@example.net => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:eyebeam@example.net => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:meetme200@example.net;transport=tcp => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:bob@example.net => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:alice@example.net;transport=tcp => rc = 18446744073709551615 ***
    *** rls_handle_subscribe() for sip:eyebeam2@example.net => rc = 5 ***
    *** rls_handle_subscribe() for sip:eyebeam@example.net;transport=tcp => rc = 5 ***

    It's strange as it doesn't always fail (!=5). Note that I don't have rls created.

    No error in the log.

     
  • Anca Vamanu

    Anca Vamanu - 2009-08-12

    Hi Inaki,

    That retcode corresponds to -1, it is in fact 111...11 in binary (64 bits). So it seems that there is an error with no error message printed. Could you raise the debug level and check which are the log messages corresponding to the processing of the Subscribe in rls module?

    regards,
    Anca

     
  • Anca Vamanu

    Anca Vamanu - 2009-10-14
    • priority: 5 --> 2
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks