From 5c03a5f2e792635a3e61886df94e52802ef40371 Mon Sep 17 00:00:00 2001 From: Matthew Jordan Date: Sat, 14 Mar 2015 02:28:56 +0000 Subject: [PATCH] main/frame: Don't report empty disallow values as an error In realtime, it is normal to have a database with both 'allow' and 'disallow' columns in the schema. It is perfectly valid to have an 'allow' value of '!all,g722,ulaw,alaw' and no 'disallow' value. Unlike in static conf files, you can't *not* provide the disallow value. Thus, the empty disallow value causes a spurious WARNING message, which is kind of annoying. This patch makes it so that a 'disallow' value with no ... value ... is ignored. Granted, you can still screw this up as well, as technically specifying 'disallow=all,!ulaw' allows only ulaw, and then you would have no 'allow' value in your database. But really, why would you do that? WHY? ASTERISK-16779 #close Reported by: Atis Lezdins ........ Merged revisions 432970 from http://svn.asterisk.org/svn/asterisk/branches/11 git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@432971 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- main/format_cap.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/main/format_cap.c b/main/format_cap.c index 364c924bfd..177652efbd 100644 --- a/main/format_cap.c +++ b/main/format_cap.c @@ -319,6 +319,10 @@ int ast_format_cap_update_by_allow_disallow(struct ast_format_cap *cap, const ch int res = 0, all = 0, iter_allowing; char *parse = NULL, *this = NULL, *psize = NULL; + if (!allowing && ast_strlen_zero(list)) { + return 0; + } + parse = ast_strdupa(list); while ((this = strsep(&parse, ","))) { int framems = 0; -- 2.47.2