Add a reloadable option for sorcery type objects
authorKevin Harwell <kharwell@digium.com>
Fri, 30 Aug 2013 19:55:56 +0000 (19:55 +0000)
committerKevin Harwell <kharwell@digium.com>
Fri, 30 Aug 2013 19:55:56 +0000 (19:55 +0000)
commit9bad1dabcf52db0a75b3dfb7c0c27f613402a01b
tree8a4b5f2a47df2dbe6fcc8ac29f64ca67affeb9e0
parent16b8d0cb5a3b15eae8db19c99223170ebed79fef
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/
........

Merged revisions 398139 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@398140 65c4cc65-6c06-0410-ace0-fbb531ad65f3
include/asterisk/sorcery.h
main/sorcery.c
res/res_pjsip.c
res/res_pjsip/config_transport.c
res/res_pjsip_outbound_registration.c