The PJSIP parsing functions provide a nice concise way to check the length of a hostname in a SIP URI. The problem is that in order to use those parsing functions, it's required to use them from a thread that has registered with PJLib. On startup, when parsing AOR configuration, the permanent URI handler may not be run from a PJLib-registered thread. Specifically, this could happen when Asterisk was started in daemon mode rather than console-mode. If PJProject were compiled with assertions enabled, then this would cause Asterisk to crash on startup. The solution presented here is to do our own parsing of the contact URI in order to ensure that the hostname in the URI is not too long. The parsing does not attempt to perform a full SIP URI parse/validation, since the hostname in the URI is what is important. ASTERISK-25928 #close Reported by Joshua Colp Change-Id: Ic3d6c20ff3502507c17244a8b7e2ca761dc7fb60 |
||
---|---|---|
.. | ||
include | ||
config_auth.c | ||
config_domain_aliases.c | ||
config_global.c | ||
config_system.c | ||
config_transport.c | ||
location.c | ||
pjsip_cli.c | ||
pjsip_configuration.c | ||
pjsip_distributor.c | ||
pjsip_global_headers.c | ||
pjsip_options.c | ||
pjsip_resolver.c | ||
presence_xml.c | ||
security_events.c |