| Summary: | ASTERISK-30113: ari: Loading PJSIP config wizard causes duplicated Endpoints, AORS, Auths created by push | ||||
| Reporter: | Vitezslav Novy (vnovy) | Labels: | |||
| Date Opened: | 2022-06-17 01:44:48 | Date Closed: | 2022-06-17 04:07:18 | ||
| Priority: | Minor | Regression? | No | ||
| Status: | Closed/Complete | Components: | Core/Sorcery | ||
| Versions: | 18.10.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Debian 11 | Attachments: | |||
| Description: | With sorcery configuration in sorcery.conf
[res_pjsip] endpoint=astdb,ps_endpoints auth=astdb,ps_auths aor=astdb,ps_aors objects created by ARI push are shown twice in cli Analysis: Module res_pjsip_config_wizard registers sorcery memory wizard for endpoint, aor, auth and maybe other pjsip sorcery object types. With sorcery configuration shown above, we end with 2 sorcery wizards (astdb, memory) for these objects. When ARI is used to create object, function ast_sorcery_create stores the object using both wizards. Retrieval functions like ast_sorcery_retrieve_by_regex or ast_sorcery_retrieve_by_prefix fetch objects from all wizards, but there is no deduplication. Workaround: if not needed do not load module res_pjsip_config_wizard or delete config file pjsip_wizard.conf | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-06-17 01:44:49.439-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/]. | ||||