Hi Patrick,

Thanks for testing - I did the backport to 1.11 too.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 08.10.2014 23:12, Patrick Wakano wrote:
Hi Bogdan!
Just tested your patch and it worked!!!

Thanks a lot for your support!!

Patrick

On Wed, Oct 8, 2014 at 6:22 AM, Bogdan-Andrei Iancu <[email protected] <mailto:[email protected]>> wrote:

    Hi Patrick,

    Shortly, I found a flow in the logic of validating the send socket
    (the dialog module is forcing an send socket for the OPTIONS,
    taken from the dialog info).

    I made a fix on trunk/master - see:
    
https://github.com/OpenSIPS/opensips/commit/c95ddd8f282c8809a0fae233bdb57b4dddb3c628.patch

    Could you test to see if this solves your problem ?

    If you need to backport the patch and have problems applying it,
    just let me know.

    Regards,

    Bogdan-Andrei Iancu
    OpenSIPS Founder and Developer
    http://www.opensips-solutions.com

    On 24.09.2014 14:45, Patrick Wakano wrote:
    Hello list,

    I was having a problem in which my Opensips was not sending the
    Options of the dialog ping mechanism. After debuging I found out
    that Opensips could not send it because it was not listening to
    the primary IP of the interface. I am in a mhomed scenario and
    using Linux-HA so the virtual IP managed by the heartbeat is the
    one Opensips listens to. If I configured Opensips to listen to
    both IPs then the dialog ping works. Also the problem only
    happens in UDP, if I use TCP then it works fine too.

    I found this thread that may be related, but with the drouting
    module:
    http://opensips.org/pipermail/users/2013-November/027203.html
    So is this an Opensips error in the dialog module or should I
    face it as a linux restriction?

    The following lines are printed on the log when the dialog ping
    fails:
     /sbin/opensips[28392]: DBG:dialog:ref_dlg: ref dlg 0xb4e8e37c
    with 1 -> 4
     /sbin/opensips[28392]: DBG:dialog:send_leg_msg: sending
    [OPTIONS] to caller (0)
     /sbin/opensips[28392]: DBG:tm:t_uac:
    next_hop=<sip:[email protected]:38283
    <http://sip:[email protected]:38283>>
     /sbin/opensips[28392]: DBG:core:mk_proxy: doing DNS lookup...
     /sbin/opensips[28392]: ERROR:core:get_out_socket: no socket found
     /sbin/opensips[28392]: ERROR:tm:t_uac: no corresponding socket
    for af 2
     /sbin/opensips[28392]: ERROR:dialog:send_leg_msg: failed to send
    the in-dialog request
     /sbin/opensips[28392]: ERROR:dialog:dlg_ping_routine: failed to
    ping caller
     /sbin/opensips[28392]: DBG:dialog:unref_dlg: unref dlg
    0xb4e8e37c with 1 -> 3 in entry 0xb4d24d74
    ....
     /sbin/opensips[28392]: DBG:dialog:dlg_ping_routine: dialog
    0xb4e8e37c-1537054613 has expired
     /sbin/opensips[28392]: DBG:dialog:init_dlg_term_reason: Setting
    DLG term reason to [Ping Timeout]
     /sbin/opensips[28392]: DBG:dialog:send_leg_bye: sending BYE to
    caller (0)
     /sbin/opensips[28392]: DBG:dialog:ref_dlg: ref dlg 0xb4e8e37c
    with 1 -> 4
     /sbin/opensips[28392]: DBG:tm:t_uac:
    next_hop=<sip:[email protected]:38283
    <http://sip:[email protected]:38283>>
     /sbin/opensips[28392]: DBG:core:mk_proxy: doing DNS lookup...
     /sbin/opensips[28392]: ERROR:core:get_out_socket: no socket found
     /sbin/opensips[28392]: ERROR:tm:t_uac: no corresponding socket
    for af 2
     /sbin/opensips[28392]: ERROR:dialog:send_leg_bye: failed to send
    the BYE request

    Thanks!

    Patrick


    _______________________________________________
    Users mailing list
    [email protected]  <mailto:[email protected]>
    http://lists.opensips.org/cgi-bin/mailman/listinfo/users



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to