[asterisk-bugs] [JIRA] (ASTERISK-30109) no contact-status AMI event on register of prune-on-boot contact that uses the same URI as before Asterisk restart

[Michael Neuhauser (JIRA)]

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

Michael Neuhauser commented on ASTERISK-30109:
----------------------------------------------

Moving the call of ast_sip_location_prune_boot_contacts() from ast_res_pjsip_initialize_configuration() in res/res_pjsip/pjsip_configuration.c to load_module() in res/res_pjsip.c, *after* the call to ast_res_pjsip_init_options_handling() fixes the problem, but I am not sure if that has unintended consequences - I will create a gerrit review.

> no contact-status AMI event on register of prune-on-boot contact that uses the same URI as before Asterisk restart
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30109
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30109
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 16.26.1
>            Reporter: Michael Neuhauser
>
> TLS endpoint with rewrite_contact=true is registered. Asterisk is restarted. Contact is pruned by ast_sip_location_prune_boot_contacts(). If the endpoint registers again using the same remote address and port as before (i.e., same URI), then no AMI ContactStatus event is sent.
> This happens because ast_sip_location_prune_boot_contacts() is called before res/res_pjsip/pjsip_options.c registers its contact sorcery observer so the contact is not removed from sip_options_contact_statuses when it is pruned.



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