Tag Info

New answers tagged

0

I've found solution: Simply adding certain extensions to IVR respond options and making them hangup call does the trick. For some reason I was thinking this things where accepting one symbol input only, apparently it's not. It could be used to intercept dialed extensions as well.


1

Try it with quotes, like this: "username":"password"@server


0

FreePBX is at version 2.11 now, with 2.12 imminent. You really want to update your system. In current versions you can specify a list of extensions that can be direct dialed from an IVR by creating a directory containing the appropriate extensions. I believe older versions only have a checkbox to allow or disallow direct dialing. If you disallow direct ...


0

Have you tried some simple tests to determine what the latency is between the 2 locations? If you haven't got anything there right now you could try using speedtest.net (a bit brutal but it will give you an idea) and choosing an ISP in the right city. Obviously whatever ISP you end up with may vary. From http://www.voip-info.org/wiki/view/QoS - Callers ...


0

Simple setup like this: In sip.conf set bind=192.168.254.1 Add route to your voip provider via eth2 All other setup require checks of how your packets really go and what asterisk send in sip packets. Not think you can get answer on that in stackoverflow format.


0

There can be many reasons for this (and I can assure you SecAst isn't pulling addresses out of thin air). Geofencing: SecAst can block source IP's based on their geographic location. Do you have geogencing setup in the secast.conf file? If so, go to the telnet interface of SecAst and test the blocked IP's to see if they originate in a restricted ...


1

In general we don't recommend exposing the SecAst telnet interface beyond the local machine. You can secure the telnet interface by either: In the secast.conf file tell the telnet interface to listen on the localhost only, and then SSH into the pbx when you need access to SecAst control. Setup an iptables rule to allow access only from your laptop's IP ...


2

First off, you probably want to switch your system to "Device and User" mode (see here). It is a little more complicated than the default "extensions" mode, but substantially more flexible. In Device and User mode you will have an option on the User page to enable voicemail: (I believe you'll have the same option on the "Extension" page). Set the ...


0

The comments below all support that this is not SecAst related, something else is going wrong on your computer. Have a look at: Insufficient memory causing issues The BASH issues (and LDD issues from your other post) all could be memory related, or a bad install of Linux....nothing SecAst related.


0

The comments below all support that this is not SecAst related, something else is going wrong on your computer. Have a look at: Insufficient memory causing LDD issues The LDD issues and BASH issues all could be memory related, or a bad install of Linux....nothing SecAst related.


0

I think you've misread the manual...You'll notice that the instructions contain different steps for different operating systems. You are performing the steps in the box marked "Red Hat 6" and the steps in the box marked "Ubuntu". You should only be performing one OR the other.


1

Correct solution - ask provider all ips and add all as trunk1-trunk2...trunkX


0

You will find that hackers/scanners are also reducing their brute force attempts to even just a single attempt every day (again to avoid detection). If you wanted to tighten your security you could reduce the max intrusions to 1, and expand the interval to 2 days or more. (That is why the attack shown in your logs likely stops at 2 attempts). Based on ...


0

Before you worry about the API (which just layers upon the Asterisk AMI), I would suggest you telnet to the AMI port and try interacting directly with the AMI. There you can learn about the command structure and responses - then the above will make more sense to you!


0

I tried a Ubuntu 12 64bit installation and the -v parameters seems to work fine: root@ubuntu:~# cd /tmp root@ubuntu:/tmp# touch testfile root@ubuntu:/tmp# cp -v testfile testfile2 'testfile' -> 'testfile2' root@ubuntu:/tmp# and it seems to work equally well on Red Hat 6. I'm wondering if there is something else going on in your shell. Can you post ...


0

The message "not a dynamic executable" means that either you are checking the wrong file, or something is wrong with the secast executable. First make sure you are checking the right file. Did you unpack the package in Windows and then copy to Linux? If not, post the results of running 'ls' in your /usr/local/secast folder. There was a typo in the ...


1

SecAst is stopping because it is receiving the HUP signal from Linux, note the line in your log: 2014-06-25T15:14:45, 00000102, I, General, Received shutdown request via HUP signal Apps must shutdown when receiving the HUP signal. So the question is why is SecAst receiving a HUP signal. Most likely, SecAst received a shutdown request from the secast ...


0

Use "sip set debug on" and see on consoel how EXACTLY come that packet. Very likly it go not to s extension,but other one.


0

You have use localnet=192.168.3.0/255.255.255.0 localnet=192.168.30.0/255.255.255.0 in sip.conf in general section. Also you need ensure no nat applied


1

You need allow busy message in extensions tab AND press APPLY CHANGES button on top


1

The attacker at 176.58.69.112 is spacing out his connection attempts to avoid detection. Be sure you set the maxintrusioninterval high enough to see multiple attempts, and maxintrusions set low enough to trigger the detection in that interval. Can you post your settings from the [credentials] stanza of secast.conf ? (or email the entire config file to ...


0

Got the answer. My manager.conf now looks like this: [general] enabled=yes port=5038 bindaddr=0.0.0.0 displayconnects=yes ;only effects 1.6+ [admin] secret = abc123 deny=0.0.0.0/0.0.0.0 permit=127.0.0.1/255.255.255.0 read = system,call,log,verbose,command,agent,user,originate write = system,call,log,verbose,command,agent,user,originate Also, when ...


0

We confirmed a bug related to encryption in our smtp library, which only affected some SMTP hosts (including google). We have temporarily switched smtp libraries and confirmed that SecAst can now send through google using TLS and SSL. SecAst version 1.0.4 is now available for download on the www.generationd.com website, and should work fine with google. ...


0

The penalty is set when the member is added to the queue. If you want to control this you may remove and re-add the member to the queue, but maybe this can cause some misbehaviour. If you really want to do this, you may consider using realtime agents. Then you will be able to control the penalty without the need for removing member from the queue. [edited] ...


0

I think you can set host=dynamic and restric access with permit/deny clauses, as in: [trunk] ... host=dynamic deny=0.0.0.0/0.0.0.0 ; deny access permit=192.168.0.0/255.255.255.0 ; allow 192.168.0.0/24 subnet ... Also, you can easily setup an iptables chain to restrict access to the 5060 port (or whatever your SIP port is), which you should do ...



Top 50 recent answers are included