SecAst not recognizing some excluded trunks in config

Installing SecAst, prerequisites, basic configuration, and troubleshooting performance and technical issues. As well, upgrades to SecAst and any underlying software.
Post Reply
User avatar
CRM User
Posts: 175
Joined: Sun Nov 27, 2016 3:41 pm

SecAst not recognizing some excluded trunks in config

Post by CRM User » Fri Dec 16, 2016 9:19 pm

I have a large number of trunks I need to exclude in the secast.conf file in the [channelvolume] stanza, which I have entered like this:

exclude= \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/1234567890 | \
IAX/trunkin000 | \
IAX/trunkin000 | \
IAX/trunkin000 | \
IAX/trunkin000 | \
IAX/trunkin000 | \
IAX/trunkin000

(NOTICE: Actual trunk names obfuscated by Telium support. Requested customer send secast.conf file to support for analysis)

After the fifth line my excludes are ignored. Why?
Account for questions transferred from CRM system
User avatar
Telium Support
Posts: 235
Joined: Sun Nov 27, 2016 3:27 pm

Re: SecAst not recognizing some excluded trunks in config

Post by Telium Support » Fri Dec 16, 2016 9:22 pm

The problem is that you have a space character after the backslash on line 5 (based on analyzing the config file sent). Unfortunately the prebuilt library we use for reading the config file treats any character after a backslash to mean 'escape' as opposed to 'continuation'. So SecAst stops reading your excludes at line 5.

The solution is to ensure you have no characters following the backslash character. We consider the behavior of the library to be a bug and we will report it to the manufacturer.
Post Reply