[asterisk-bugs] [JIRA] (ASTERISK-30022) res_pjsip_registrar: Refreshing with old Path

[Joshua C. Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258820#comment-258820 ] 

Joshua C. Colp commented on ASTERISK-30022:
-------------------------------------------

Thanks for the report and debug. However we also need protocol specific debug captured at the time of the issue. Please include the following:

* Asterisk log files generated using the instructions on the Asterisk wiki [1], with the appropriate protocol debug options enabled, e.g. 'pjsip set logger on' if the issue involves the chan_pjsip channel driver.
* Configuration information for the relevant channel driver, e.g. pjsip.conf.
* A wireshark compatible packet capture, captured at the same time as the Asterisk log output.

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> res_pjsip_registrar: Refreshing with old Path
> ---------------------------------------------
>
>                 Key: ASTERISK-30022
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30022
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip, Resources/res_pjsip_registrar
>    Affects Versions: 18.11.1
>         Environment: Centos 7
>            Reporter: Neimar Avila
>
> In a scenario where there are two or more Kamailio acting as proxy, and there is a dns exchange, pjsip does not validate the path field change and keeps sending OPTIONS to the previous address.
> Enabling debug mode, I see the line:
> res_pjsip_registrar.c: Refreshed contact 'sip:4247FCDBE148 at domain.com:5060' on AOR '4247FCDBE148' with new expiration of 300 seconds
> however the qualify goes to the original address of the register and not changed it.
> I imagine that the remove_existing function doesn't happen because the contact is the same, changing only the Path and Via.



--
This message was sent by Atlassian JIRA
(v6.2#6252)