[asterisk-bugs] [JIRA] (ASTERISK-30401) PJSIP Realtime - If an endpoint/aor is created after PJSIP is loaded, device state for that endpoiont is locked to unavailable

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-30401:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> PJSIP Realtime - If an endpoint/aor is created after PJSIP is loaded, device state for that endpoiont is locked to unavailable
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30401
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30401
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: GIT, 18.9.0
>         Environment: Prod: RHEL 8 (some Kubernetes thing that I couldn't possibly describe)
> Test: Ubuntu 22.04 on Intel NUC Skull Canyon with 16GB of RAM and a simple SSD
>            Reporter: Jonathan Rose
>            Severity: Major
>
> Realtime PJSIP endpoints/aors have a bit of a crippling problem right now... if I have a pair of endpoint/aor present at the point when res_pjsip.so is loaded and register afterwards, registration works fine and device state is set to 'Not In Use' as you would expect it to.
> If, however, I add a new pair of endpoint/aor to the realtime backend and register *that* user, the registration will appear to work correctly from a SIP perspective, but within Asterisk the device state will be locked to unavailable. I can unregister and reregister any number of times at that point and the device state will remain unavailable.
> Issuing 'module reload res_sip.so' from the CLI will 'fix' the issue, but this is realtime... that's not really an acceptable workaround. I'd argue that it violates the whole concept of Realtime and I'm kinda shocked I couldn't find any reports of this happening already.
> I've confirmed that this problem seems to be backend agnostic, having used both odbc and curl as the realtime backends.
> I will provide minimalist configuration for reproducing the issue.



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