[Home]

Summary:ASTERISK-30229: PJSIP Configuration Wizard documentation should include mention necessary sorcery configurations
Reporter:Marcel Wagner (chingucoding)Labels:
Date Opened:2022-09-14 14:28:55Date Closed:2022-09-23 03:56:01
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip_config_wizard
Versions:18.14.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) asterisk_session.txt
( 1) messages.txt
( 2) modules_show.txt
Description:After following the documentation around the PJSIP Configuration Wizard (https://wiki.asterisk.org/wiki/display/AST/PJSIP+Configuration+Wizard?focusedCommentId=32376558#comment-32376558), I am stuck with these wizards not taking effect and seeing errors about missing wizards for different object types (in my case auth, aor and endpoint). It would be good to include documentation around the necessary dependencies since this would make onboarding this feature a lot easier and also help understand this better.

If I had more knowledge around this I would be happy to contribute more information on the necessary configurations, however I am still stuck with it not working.
Comments:By: Asterisk Team (asteriskteam) 2022-09-14 14:28:59.499-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) 2022-09-14 14:36:59.943-0500

Are you selectively loading modules or doing other things? Out of the box it should just work and not require anything additional.

By: Marcel Wagner (chingucoding) 2022-09-15 11:40:27.305-0500

I tried both loading the modules manually and also setting autoload to yes in the modules.conf, however in both cases I get three errors:

[Sep 15 16:38:16] ERROR[1]: res_pjsip_config_wizard.c:1067 object_type_loaded_observer: There was no wizard for object type 'auth'
[Sep 15 16:38:16] ERROR[1]: res_pjsip_config_wizard.c:1067 object_type_loaded_observer: There was no wizard for object type 'aor'
[Sep 15 16:38:16] ERROR[1]: res_pjsip_config_wizard.c:1067 object_type_loaded_observer: There was no wizard for object type 'endpoint'



By: George Joseph (gjoseph) 2022-09-16 07:59:50.114-0500

Are there any other errors during startup?  Can you attach a log of the startup?
*  stop asterisk
*  rm /var/log/asterisk/messages
*  start asterisk
* When you get to "Asterisk Ready" stop asterisk.
*  Attach /var/log/asterisk/messages to this issue.

Things to check...
Have you made any changes to sorcery.conf?
Is the res_pjsip module itself loading?
Are at least the res_sorcery_config, res_sorcery_memory and res_sorcery_memory_cache modules loaded?

By: Marcel Wagner (chingucoding) 2022-09-16 20:44:50.761-0500

I set autoload=yes so I suppose it res_sorcery_config, res_sorcery_memory and res_sorcery_memory_cache are being loaded.

By: Marcel Wagner (chingucoding) 2022-09-20 07:36:42.963-0500

Also regarding res_pjsip loading I assume it did given that I didn't see an error indicating otherwise.

By: Michael Bradeen (mbradeen) 2022-09-22 11:16:10.810-0500

Please attach the output from the asterisk console of 'module show' so we can confirm what is loaded.

By: Marcel Wagner (chingucoding) 2022-09-22 12:18:36.962-0500

Of course, see modules_show.txt attached on this issue. If there is anything else I can do to help debug this, let me know.

By: Michael Bradeen (mbradeen) 2022-09-22 12:28:40.064-0500

Thank you, it appears from the show command that the modules [~gjoseph] referenced modules are not loaded.  Please check that these are included in the modules directory as part of your install.


By: Michael Bradeen (mbradeen) 2022-09-22 12:29:34.907-0500

example:
module show like res_sorcery_
Module                         Description                              Use Count  Status      Support Level
res_sorcery_astdb.so           Sorcery Astdb Object Wizard              3          Running              core
res_sorcery_config.so          Sorcery Configuration File Object Wizard 26         Running              core
res_sorcery_memory.so          Sorcery In-Memory Object Wizard          9          Running              core
res_sorcery_memory_cache.so    Sorcery Memory Cache Object Wizard       0          Running              core
res_sorcery_realtime.so        Sorcery Realtime Object Wizard           0          Running              core
5 modules loaded

By: Marcel Wagner (chingucoding) 2022-09-22 12:53:58.061-0500

Running the command you provided, I got the same result:

b100a4ba5604*CLI> module show like res_sorcery_
Module                         Description                              Use Count  Status      Support Level
res_sorcery_astdb.so           Sorcery Astdb Object Wizard              3          Running              core
res_sorcery_config.so          Sorcery Configuration File Object Wizard 20         Running              core
res_sorcery_memory.so          Sorcery In-Memory Object Wizard          8          Running              core
res_sorcery_memory_cache.so    Sorcery Memory Cache Object Wizard       0          Running              core
res_sorcery_realtime.so        Sorcery Realtime Object Wizard           0          Running              core
5 modules loaded

By: Michael Bradeen (mbradeen) 2022-09-22 12:57:09.839-0500

This is from the same asterisk instance that had the errors and the module_show was from?  The modules_show.txt only shows the realtime sorcery module loaded.

By: Marcel Wagner (chingucoding) 2022-09-22 13:05:10.860-0500

This is indeed the same instance, I've uploaded the complete asterisk -r log (asterisk_session.txt). It seems the loaded modules changed during runtime.

By: Marcel Wagner (chingucoding) 2022-09-22 13:06:46.866-0500

Not sure if it makes a difference but I'm running the asterisk inside a docker image. If it helps, I can try upload the necessary files with the hope of reproducability.

By: Michael Bradeen (mbradeen) 2022-09-22 13:09:22.278-0500

If you try a 'core reload' now, with the modules loaded, does it load your endpoint(s)?

Is the image built straight from a dockerfile or is the install separate?

By: Marcel Wagner (chingucoding) 2022-09-22 13:39:19.053-0500

Running core reload does not load the endpoints, I get the same errors again. The image where the asterisk is installed from is a separate one: https://github.com/azielke/docker-asterisk. I'm basing my image off of that and just copying configs and the opus codec into it.

By: Michael Bradeen (mbradeen) 2022-09-22 18:00:47.338-0500

I tried running the azielke container and was able to load the pjsip wizard configuration copied from the wiki.  Perhaps there is some issue with the conf?  

By: Marcel Wagner (chingucoding) 2022-09-23 03:37:50.047-0500

Thanks for all your help, it seems this was caused by a faulty sorcery.conf.