Went the safe/simple way by adding comma in regex.

Here’s an example from the asterisk PJSIP config.sample.conf

So we do need to be able to use a , in the values.

This kind of regex is to be sure that a user cannot inject new configurations with a key like bind 0.0.0.0\n\n#exec rm -rf / In the case of PJSIP transport the admin already “owns” the system so I don’t have an objection to remove the regex completely from the transport resource. But newlines should probably be stripped or prohibited

About the solution:
The regex is here::

Since we bypass regex for pjsip endpoint, we may want to totally remove this regex (only used by sip transport), because value seems safety escaped
Or we could move the regex to transport sip option only to be more explicit in the code

What do you think about removing totally this regex? Is it worth it, or we only add ,