ASTERISK-28189: configured pjsip endpoints go offline when a new endpoint registers

[Home]

Summary: ASTERISK-28189: configured pjsip endpoints go offline when a new endpoint registers

Reporter: Gergely Dömsödi (doome) Labels: pjsip

Date Opened: 2018-11-29 07:37:46.000-0600 Date Closed: 2018-11-29 08:50:03.000-0600

Priority: Major Regression? Yes

Status: Closed/Complete Components: pjproject/pjsip

Versions: 16.0.0 Frequency of
Occurrence Frequent

Related
Issues:
duplicates ASTERISK-28056 res_pjsip: Incorrect endpoint status after endpoint synchronization for a specific AOR

Environment: Fedora 29 Attachments: ( 0) debug.log

Description: I have several PJISIP endpoints defined in pjsip configuration and a realtime postgresql database. All realtime endpoints are dynamic, they register to us. We are using queues, where these endpoints are dynamically added.

After upgrading to Asterisk 16.0.0, I noticed that from time to time, every queue member is listed as 'Unavailable' in 'queue show'. After some fiddling and debugging, it seems that after a previously unseen endpoint sends a REGISTER to us, all of our online endpoints state switches to offline, and remains that way - even after successful OPTIONS qualifies -, until a 'module reload res_pjsip'

Comments: By: Asterisk Team (asteriskteam) 2018-11-29 07:37:49.270-0600

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.

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].
By: Gergely Dömsödi (doome) 2018-11-29 07:43:34.824-0600

Attached a log, which is taken from the point where an enpoint REGISTER is just finished. Near the end of the file, there can be seen that every currently registered endpoint's state is set to offline, despite of their current reachability.