Invalid global setting in pjsip breaks all future configs

Hi,

I was taking another try at my issue posted here Allow user and peers from the same IP

In my global settings I had

[global]
user_agent=MyPBX
foo=bar
endpoint_identifier_order=username,ip,anonymous

If I then did pjsip show settings it would show the order as ip,username,anonymous. If i were to comment out the foo=bar line then it would show correctly. Is it a bug that Asterisk stops parsing the rest of the configs if there is an invalid item being set?

Also I noticed that if I did a module reload it would show the correct order however I would still not work. I needed to restart asterisk in order to get it to follow that order. I am using asterisk 22.2.0 built from source on Rocky 9.

No, it’s to stop invalid configuration from being applied. The same happens if you do it with an endpoint. The endpoint won’t load.

@jcolp Thanks. I spent a good amount of time on it. If I submitted a patch to update the docs so there is less pain for the next person what the odds of it being taken? Also is it a bug that pjsip show settings will show the correct settings after a module reload but it wont work till Asterisk is restarted?

Everything depends on the patch itself and the review.

Global options for the most part can’t change during runtime, due to limitations in PJSIP or due to implementation details. Being more clear about that would be good.