[asterisk-bugs] [JIRA] (ASTERISK-24729) Outbound registration not occuring on new registrations after reload.

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-24729:
---------------------------------------

    Status: Open  (was: Triage)

> Outbound registration not occuring on new registrations after reload.
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-24729
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24729
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_outbound_registration
>    Affects Versions: 13.1.0
>            Reporter: Richard Mudgett
>
> Performing a {{module reload}} of all modules where there are new outbound registrations defined in {{pjsip.conf}} frequently results in the new registrations not happening.
> For example:
> {noformat}
> testpbx-1*CLI> pjsip show registrations
> <Registration/ServerURI..............................>  <Auth..........>  <Status.......>
>  ========================================================= 
> siptrunk/sip:siptrunk at 192.168.81.2                      siptrunk          Registered      
> {noformat}
> Then re-write {{pjsip.conf}} without the registration object defined and do a {{module reload}} command:
> {noformat}
> testpbx-1*CLI> pjsip show registrations
> No objects found.
> {noformat}
> Then re-write {{pjsip.conf}} with the registration object defined and do a {{module reload}} command.  Frequently the registration object will not show in the list and the registration does not happen as seen below:
> {noformat}
> testpbx-1*CLI> pjsip show registrations
> <Registration/ServerURI..............................>  <Auth..........>  <Status.......>
>  =========================================================
> {noformat}
> Repeat the above example steps and it will eventually happen.



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