[asterisk-bugs] [JIRA] (ASTERISK-18763) Different behaviour in case of usage of "#include file" instead of direct config pars
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Tue Dec 19 06:29:08 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-18763:
-----------------------------------
Affects Version/s: 13.18.4
> Different behaviour in case of usage of "#include file" instead of direct config pars
> -------------------------------------------------------------------------------------
>
> Key: ASTERISK-18763
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-18763
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Channels/chan_dahdi
> Affects Versions: 1.8.7.1, 13.18.4
> Environment: Linux
> Reporter: reinerotto
> Severity: Minor
>
> In case of wrong configuration of chan_dahdi using "#include dahdi-channels.conf" the error messages are different to the same misconfiguration, but with explicitly edited commands.
> The error messages because of wrong configuration using "#include ..." are not obvious.
> Example:
> /etc/asterisk/chan_dahdi.conf
> ;This is an excerpt from misconfigured chan_dahdi.conf:
> ........
> ; they mean or you know you should change them.
> ; Next line should be after [channels] instead, here it is misplaced.
> #include dahdi-channels.conf
> [trunkgroups]
> ;
> .........
> This will result in the following error messages from asterisk:
> /var/log/asterisk/messages:
> ......
> [Oct 28 10:20:24] WARNING[2836] loader.c: Error loading module 'chan_mgcp.so': /usr/lib/asterisk/modules/chan_mgcp.so: undefined symbol: ast_pktccops_gate_alloc
> [Oct 28 10:20:24] WARNING[2836] loader.c: Module 'chan_mgcp.so' could not be loaded.
> [Oct 28 10:20:24] WARNING[2836] config.c: parse error: No category context for line 11 of /etc/asterisk/dahdi-channels.conf
> [Oct 28 10:20:24] WARNING[2836] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 23.
> So, in this case, a WARNING only, which is misleading to the casual user (like me).
> Opposed to explicitly edited, misconfigured chan_dahdi:
> /etc/asterisk/chan_dahdi.conf
> ........
> ;
> ;#include dahdi-channels.conf
> ;Instead of using include, all statements here
> group=0,11
> context=from-isdn
> overlapdial=yes
> switchtype = euroisdn
> signalling = bri_cpe_ptmp
> channel => 1-2
> context = default
> group = 63
> [trunkgroups]
> ........
> This results in a much more obvious error message:
> /var/log/asterisk/messages:
> [Oct 28 10:24:07] WARNING[2884] config.c: parse error: No category context for line 22 of /etc/asterisk/chan_dahdi.conf
> [Oct 28 10:24:07] ERROR[2884] chan_dahdi.c: File chan_dahdi.conf cannot be parsed. Aborting.
> The behaviour of using an #include is different to explicitly typed config statements. Worrying ....
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list