Logging when no transport defined in PJSIP


While working on enabling a feature, I created a new Asterisk instance, using Debian Bullseye package. This installs an empty pjsip.conf without any transport defined.

When I edited this pjsip.conf, I forgot to define any transport.
After running several times “pjsip reload”, I got the following answer:

Feb 16 13:43:27] NOTICE[2224]: sorcery.c:1348 sorcery_object_load: Type ‘system’ is not reloadable, maintaining previous values
[Feb 16 13:43:27] ERROR[2224]: res_sorcery_config.c:422 sorcery_config_internal_load: Could not create an object of type ‘registration’ with id ‘foobar’ from configuration file ‘pjsip.conf’

While I shouldn’t have forgotten to add a transport section in my pjsip.conf, do you think logging should somehow changed to signal the fact no transport is defined ?
Current messages lead me to look into sorcery config.

Best regards

“should” is a strong word. I think it would be an improvement and beneficial for some, yes.

Yes, I agree “should” is a bit too strong.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.