asked on

Asterisk Not Starting Correctly

I've just done new install - asterisk 1.8.xxx + Ubuntu 11.xxx, I'm trying to run the AMI so I can connect with a switchboard, here's my manager.conf:
[general]
enabled = yes
port = 5038
bindaddr = 127.0.0.1
[admin]
secret = xxxx
deny = 0.0.0.0/0.0.0.0
permit = 127.0.0.1/255.255.255.0
read = all
write = all
#include "manager.d/*.conf"
The switchboard can't connect, and when I run this line:
sudo netstat -lnp | grep 5038 nothing is listening. Where am I going wrong?
But when I run this l

SOLUTION

Ron Malmstead

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Silas2

ASKER

I'm pretty sure there is no firewall anywhere (its on a sort of DMZ, only asterisk box->ISP, nothing else)

Ron Malmstead

No I meant Ubuntu firewall.

ASKER CERTIFIED SOLUTION

José Méndez

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

FishMonger

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

FishMonger

Are making the AMI connection directly from the asterisk server, or from another system on your network? If it's from another system, then your should/need to specify your network address instead of your loopback address.

Silas2

ASKER

xuserx2000: Definately, IPtables blank, new install, and I didn't make any rules.
FishMonger: Swapped the 'all'' for the explicit values
re loopback. Its all one server, its really the simplest it could be, ISP->asterisk/ubuntu box->ISP, the AMI is being (or not being) accessed by fop2 resident on the asterisk box, so I guess that 127.0.0.1 is right, isn't it?

Silas2

ASKER

+ willlywilburwonka, yes did a reboot (or three), still no:
sudo netstat -lnp | grep 5038

Silas2

ASKER

Ah, I think I found it. Does that line, which was in before
#include "manager.d/*.conf"
the hash is not a comment, so it is maybe looking in that location for manager info overriding the stuff in this file? I took it out and is now listening on 5038.