BUG? - Dialog module timeout BYE is not ok. - sr-users

25 Apr 2013

IMO the timeout-triggered BYE should have identical From/To
headers as the initial request - otherwise it may cause issues
with clients that are strict, or rely on identical headers (like
in your setup).

regards
Klaus

On 25.04.2013 13 <tel:25.04.2013%2013>:30, Uri Shacked wrote:

    Hi,

    Following this issue, and the issue "BYE dialog timeout bad
    syntax" from
    Julia.

    I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and
    sends it
    to srv2 that forwards the BYE to the next sip server (some
    other server...).

    I can definitely see that the BYE that is being forward is
    malformed.
    The TO header info is not complete (the port section for example).

    When a "normal" bye is received from srv1 (not dlg_timeout)
    all works fine.

    One thing that i do in this scenario, on srv2 i use
    uac_replace() on the
    TO header. So, it is OK that the final destination is
    different (i do
    translations).

    I attached the BYE from both servers.

    Any ideas?

    Thanks,

    Uri

    You probably meant the To and From headers, I'm guessing.
    Yeah, as long
    as there is no display name component, URIs in headers like
    that don't
    have to go in <>s. The way Kamailio sends it is grammatically
    valid, per
    RFC 3261. The user agents are at fault for not understanding it
    correctly. Alex Balashov <abalashov at evaristesys.com
    <http://evaristesys.com>
    <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
    wrote:
     >/"BYE headers"? Which headers? />//>/Uri Shacked <ushacked at
    gmail.com <http://gmail.com>
    <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
    wrote:
    />//>>/Hi, />>//>>/I think there is a bug with the BYE that is
    sent to
    the caller and />>/callee />>/when dialog timeout happends.
    />>//>>/The
    BYE headers are sent with no "<" or ">". />>/So, some sip
    singaling
    points decline the BYE. />>//>>/BR, />>/Uri
    />>//>>//>>/------------------------------------------------------------------------
    />>//>>/_______________________________________________
    />>/SIP Express
    Router (SER) and Kamailio (OpenSER) - sr-users mailing />/list
    />>/sr-users at lists.sip-router.org <http://lists.sip-router.org>
    <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
    />>/http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
    />//>/-- />/Sent from my mobile, and thus lacking in the
    refinement one
    might />/expect from a fully-fledged keyboard. />//>/Alex
    Balashov -
    Principal />/Evariste Systems LLC />/235 E Ponce de Leon Ave
    />/Suite
    106 />/Decatur, GA 30030 />/United States />/Tel:
    +1-678-954-0670 <tel:%2B1-678-954-0670>
    />/Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
    />//>/_______________________________________________ />/SIP
    Express
    Router (SER) and Kamailio (OpenSER) - sr-users mailing list
    />/sr-users
    at lists.sip-router.org <http://lists.sip-router.org>
    <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
    />/http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
    / --

    Sent from my Nexus 10, with all the figments of autocorrect
    that might
    imply. Alex Balashov - Principal Evariste Systems LLC 235 E
    Ponce de
    Leon Ave Suite 106 Decatur, GA 30030 United States Tel:
    +1-678-954-0670 <tel:%2B1-678-954-0670>
    Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
    -------------- next part -------------- An HTML attachment was
    scrubbed... URL:
    <http://lists.sip-router.org/pipermail/sr-users/attachments/20130422/0c752722/attachment.html>

    _______________________________________________
    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
    mailing list
    sr-users@lists.sip-router.org
    <mailto:sr-users@lists.sip-router.org>
    http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users