Kevin Harwell 8cc162df5e Add a reloadable option for sorcery type objects ...

Some configuration objects currently won't place nice if reloaded.
Specifically, in this case the pjsip transport objects.  Now when
registering an object in sorcery one may specify that the object is
allowed to be reloaded or not.  If the object is set to not reload
then upon reloading of the configuration the objects of that type
will not be reloaded.  The initially loaded objects of that type
however will remain.

While the transport objects will not longer be reloaded it is still
possible for a user to configure an endpoint to an invalid transport.
A couple of log messages were added to help diagnose this problem if
it occurs.

(closes issue ASTERISK-22382)
Reported by: Rusty Newton
(closes issue ASTERISK-22384)
Reported by: Rusty Newton
Review: https://reviewboard.asterisk.org/r/2807/


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@398139 65c4cc65-6c06-0410-ace0-fbb531ad65f3

2013-08-30 19:51:48 +00:00

..

include

Expose res_pjsip threadpool options

2013-08-06 13:08:13 +00:00

config_auth.c

…

config_domain_aliases.c

…

config_global.c

…

config_system.c

Expose res_pjsip threadpool options

2013-08-06 13:08:13 +00:00

config_transport.c

Add a reloadable option for sorcery type objects

2013-08-30 19:51:48 +00:00

location.c

…

pjsip_configuration.c

Add rtpengine configuration parameter

2013-08-25 01:08:35 +00:00

pjsip_distributor.c

Fix dialog matching in the SIP distributor.

2013-08-28 15:40:25 +00:00

pjsip_global_headers.c

…

pjsip_options.c

Update config framework/sorcery with types/options without documentation

2013-08-23 15:21:40 +00:00

pjsip_outbound_auth.c

…

security_events.c

…