[Home]

Summary:ASTERISK-29504: PJSIP deltree contact still sending qualify packets
Reporter:Joseph Nadiv (yois)Labels:
Date Opened:2021-06-30 14:06:12Date Closed:2021-06-30 15:40:54
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:16.17.0 Frequency of
Occurrence
Related
Issues:
Environment:FreePBX-SNG7-2104Attachments:( 0) contacts.txt
( 1) debug_log.txt
Description:PJSIP max_contacts > 1, PJSIP remove_existing = no.

Using database deltree to remove unavailable contacts does not affect outbound qualify OPTIONS packets, and Asterisk will continue to attempt to qualify those deleted contacts indefinitely.

See attached debug log, as well as the attached output of 'pjsip show contacts'

In the attachment, 1.1.1.1 is the Asterisk server, 8.8.8.8 is the defunct contact, 4.4.4.4 is the current contact IP.

it is clear that pjsip_options.c is qualifying contacts that don't exist.
Comments:By: Asterisk Team (asteriskteam) 2021-06-30 14:06:15.899-0500

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/].

By: Joshua C. Colp (jcolp) 2021-06-30 14:33:33.395-0500

You stated on the forum that you restarted Asterisk. Is this correct? What is the uptime of Asterisk (core show uptime)?

By: Joseph Nadiv (yois) 2021-06-30 15:08:43.946-0500

Hmmm.  Uptime was 5 days 22 hours, which is correct since I didn't report this right away.  But I just restarted Asterisk again to verify and the problem cleared.

Is this still a bug or is this behavior expected?  Deleting contacts from the database will not stop qualifying the AOR until Asterisk is restarted.  So deleting contacts directly from AstDB is not the same as waiting for expiration.

By: Joshua C. Colp (jcolp) 2021-06-30 15:40:54.853-0500

This is expected behavior. OPTIONS does not constantly query the database, that creates a large bottleneck. It reacts to events as they happen on the AOR, which you bypassed. Looking deeper at things there is the "pjsip reload qualify aor <name>" CLI command which may resynchronize things if it is modified externally/directly in the AstDB.