Search found 199 matches

by Telium Support
Sun Nov 27, 2016 6:56 pm
Forum: Configuration & Optimization
Topic: SecAst ignoring attacker
Replies: 1
Views: 1633

Re: SecAst ignoring attacker

The most likely cause is that Asterisk is not providing enough information about an account violation. If you are running Asterisk 13 or later, then you should tell SecAst to use the AMI for talking to Asterisk (don't use a security log file). This exposes a lot more information to SecAst. If you mu...
by Telium Support
Sun Nov 27, 2016 6:55 pm
Forum: Configuration & Optimization
Topic: Attacker IP is not available and can't be blocked
Replies: 1
Views: 1921

Re: Attacker IP is not available and can't be blocked

The attacker is providing a fake IP address (your server) as the source IP address in the SIP header, and this confuses Asterisk and results in the above error. SecAst is able to detect this type of attack and block the attacker at the network edge. Digium is aware of the underlying issue and has re...
by Telium Support
Sun Nov 27, 2016 6:54 pm
Forum: Configuration & Optimization
Topic: Incomplete startup email
Replies: 1
Views: 1584

Re: Incomplete startup email

The SecAst executable has started, but a critical connection to Asterisk has not been successful. This in turn is preventing SecAst from protecting the Asterisk server. A delay in starting Asterisk, or a delay in Asterisk responding to SecAst may be the root cause, and no action is needed as the con...
by Telium Support
Sun Nov 27, 2016 6:52 pm
Forum: Configuration & Optimization
Topic: SecAst shuts down unexpectedly with AMI error
Replies: 1
Views: 1709

Re: SecAst shuts down unexpectedly with AMI error

Confirm that your Asterisk (AMI) configuration in secast.conf matches the AMI configuration in manager.conf. If you are certain the interface credentials, port, and settings are correct, please contact support for further assistance.
by Telium Support
Sun Nov 27, 2016 6:52 pm
Forum: Configuration & Optimization
Topic: SecAst logs not rotating
Replies: 1
Views: 1613

Re: SecAst logs not rotating

The SecAst log file or its parent directory has world write permissions, and newer versions of logrotate do not allow this to rotate. Manually running logrotate shows the results below: $logrotate -d -v secast reading config file secast Handling 1 logs rotating pattern: /var/log/secast after 1 days ...
by Telium Support
Sun Nov 27, 2016 6:49 pm
Forum: Installation & Upgrade
Topic: Shared library error on start
Replies: 1
Views: 1618

Re: Shared library error on start

One or more shared libraries are not installed. The solution is to ensure that all prerequisite libraries are installed. First, use the “ldd” command to show what libraries SecAst needs, and are available. You should see something like this: root@pbx~$ ldd secast-0.345.3.0-x86_64-ub12/secast linux-v...
by Telium Support
Sun Nov 27, 2016 6:46 pm
Forum: Installation & Upgrade
Topic: GLIBC error
Replies: 1
Views: 1622

Re: GLIBC error

The wrong SecAst package has been installed. SecAst is looking for libraries that are more modern (recent) than those offered by your Linux distribution. If you are sure you downloaded the right SecAst package then try a system wide update using your package manager (eg: “yum update”). Otherwise, re...
by Telium Support
Sun Nov 27, 2016 6:45 pm
Forum: Installation & Upgrade
Topic: Error untarring package
Replies: 1
Views: 1612

Re: Error untarring package

The archive you downloaded is incomplete and/or contains errors. The solution is to try again to download the file again. Before expanding the archive, check the md5sum value and compare it to that shown on the Telium website for that file. Some browsers / locations have difficulty downloading large...
by Telium Support
Sun Nov 27, 2016 6:42 pm
Forum: Configuration & Optimization
Topic: Warning on sync completion
Replies: 1
Views: 1575

Re: Warning on sync completion

The solution is to enable debug for the sync id which is generating the warning, then examine the /tmp/haast.sync.XXX.debuglog file for details of the warning. If the warning is correct or acceptable then no further action is required. If you wish to eliminate the warning completely you can edit the...
by Telium Support
Sun Nov 27, 2016 6:41 pm
Forum: Configuration & Optimization
Topic: Logs not rotating
Replies: 1
Views: 1555

Re: Logs not rotating

The HAAst log file or its parent directory has world write permissions, and newer versions of logrotate do not allow this to rotate. Manually running logrotate shows the results below: $logrotate -d -v haast reading config file haast Handling 1 logs rotating pattern: /var/log/haast after 1 days (7 r...