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

[Ross Beer (JIRA)]

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

Ross Beer commented on ASTERISK-28258:
--------------------------------------

Looking at the file res/res_pjsip/pjsip_options.c it appears that the default status is 'Created' but I can't see this being changed when 'qualify_frequency=0'.

The ps_aor and ps_contacts table has 'qualify_frequency=0' and 'qualify_timeout=0'.

The issue with status not showing available started with commit https://gerrit.asterisk.org/#/c/asterisk/+/7710/, I raised a ticket at the time ASTERISK-27899

At line 501 the status is set:

{noformat}
        contact_status->rtt = 0;
	contact_status->status = CREATED;
	contact_status->last_status = CREATED;
	res = ast_string_field_set(contact_status, uri, contact->uri);
	res |= ast_string_field_set(contact_status, aor, contact->aor);
	if (res) {
		ao2_unlock(sip_options_contact_statuses);
		ao2_ref(contact_status, -1);
		return NULL;
	}
{noformat}

One thing that is different from the standard is we use 'allow_unqualified_fetch=error' on 'contact' and 'aor' in sorcery.conf. Would this make a difference when creating the initial status?

{noformat}
contact/cache=memory_cache,expire_on_reload=yes
contact=realtime,ps_contacts,allow_unqualified_fetch=error

aor=config,pjsip.conf,criteria=type=aor
aor/cache=memory_cache,expire_on_reload=yes
aor=realtime,ps_aors,allow_unqualified_fetch=error
{noformat}

> 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
>            Assignee: 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)