Indexer: Format message types may not exist

In Asterisk 13+, any given message type is not guaranteed to exist even
if Asterisk comes up correctly since creation of the message type could
be declined. The indexer should not prevent Asterisk from starting
under these conditions.
........

Merged revisions 424833 from http://svn.asterisk.org/svn/asterisk/branches/13


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@424834 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Kinsey Moore
2014-10-08 14:54:54 +00:00
parent d8bbf1ec1d
commit 3dfc485e35

View File

@@ -302,17 +302,21 @@ int ast_sounds_index_init(void)
return -1;
}
res |= stasis_message_router_add(
sounds_system_router,
ast_format_register_type(),
format_update_cb,
NULL);
if (ast_format_register_type()) {
res |= stasis_message_router_add(
sounds_system_router,
ast_format_register_type(),
format_update_cb,
NULL);
}
res |= stasis_message_router_add(
sounds_system_router,
ast_format_unregister_type(),
format_update_cb,
NULL);
if (ast_format_unregister_type()) {
res |= stasis_message_router_add(
sounds_system_router,
ast_format_unregister_type(),
format_update_cb,
NULL);
}
if (res) {
return -1;