[asterisk-bugs] [JIRA] (ASTERISK-28258) DUNDi Does Not Register chan_pjsip Realtime Endpoints On Register

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28258:
------------------------------------------

The code works by dynamically adding the extension to the regcontext when the endpoint goes "online" and dynamically removing the extension when the endpoint goes "offline". The endpoint's status is aggregated by the contact and aor statuses. So yes, if one is marked "Unavailable" then I'd expect the endpoint to be "offline", thus the extension not existing in the "regcontext".

I guess the question is why is it not available? The reliable transport connection is still up? For the associated aor what's the output of:
{noformat}
*CLI> pjsip show aor <aor id>
{noformat}
Also please provide an Asterisk log with a SIP trace of the endpoint registering.

> DUNDi Does Not Register chan_pjsip Realtime Endpoints On Register
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-28258
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28258
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_dundi
>    Affects Versions: 13.24.1
>         Environment: CentOS 7.6
>            Reporter: Ross Beer
>            Severity: Minor
>              Labels: pjsip
>
> DUNDi does not register PJSIP endpoints when the configuration is stored in a Realtime database.
> Settings are all stored in the database, including AORs, contacts and endpoints.
> Endpoints show as 'Unavailable' state when registered if qualify is not used, due to a recent change to the qualify process.
> Any endpoints stored in the text config do register with DUNDi and show as available.



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