Page 1 of 1

for the forum

PostPosted: Thu Nov 22, 2007 8:20 pm
by eliasferreyra
hello can anybody helpme i need to know why does it happend each time i install a server
i hope anybody can helpme

problem connecting to "localhost", port 5038: Connection refused at
+/usr/share/astguiclient/AST_conf_update.pl line 188


problem connecting to "localhost", port 5038: Connection refused at
+/usr/share/astguiclient/AST_vm_update.pl line 188

PostPosted: Thu Nov 22, 2007 11:34 pm
by richo2007
The script is trying to open a telnet session to the port 5038 of the Asterisk server.

That port is the default for the Asterisk remote manager

make sure that you have updated your /etc/asterisk/manager.conf file acording to the instructons in SCRATCH_INSTALL.txt:

Code: Select all
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

... etc.


Remember that reloading the manager module after this modification is not enough; you need to shut down the * server and start it again.

look my manager config config

PostPosted: Fri Nov 23, 2007 7:18 am
by eliasferreyra
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

[cron]
secret = 1234
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

[updatecron]
secret = 1234
read = command
write = command

[listencron]
secret = 1234
read = system,call,log,verbose,command,agent,user
write = command

[sendcron]
secret = 1234
read = command
write = system,call,log,verbose,command,agent,user
[/i]

my manager conf

PostPosted: Fri Nov 23, 2007 7:18 am
by eliasferreyra
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

[cron]
secret = 1234
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

[updatecron]
secret = 1234
read = command
write = command

[listencron]
secret = 1234
read = system,call,log,verbose,command,agent,user
write = command

[sendcron]
secret = 1234
read = command
write = system,call,log,verbose,command,agent,user

PostPosted: Fri Nov 23, 2007 8:29 am
by richo2007
Make sure then that your firewall (iptables) is not enabled.

PostPosted: Thu May 15, 2008 9:35 am
by brainwhistler
I just re-intall ViciDial following the SCRATCH_INSTALL file, then replaced my old files to ' /etc/asterisk/ ' folder. After that i keep getting message


problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 188


problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_vm_update.pl line 188


My Asterisk is working greate when manually started, as well as i can make calls to external numbers. But when i try to start asterisk using the command,

/usr/share/astguiclient/start_asterisk_boot.pl

Asterisk does not start and i receive the above connection refused messages.

The CLI output for manually started asterisk is :

*CLI>
*CLI>
*CLI> == Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1


Asterisk 1.2.24
ViciDial 2.0.4

I have RedHat AS4 server, firewall is disabled. Even i can telnet to port 5038 remotely and it can connects to ' Asterisk Call Manager'.

Any idea, i have reinstalled everything twice but the result is same.

Thanks

PostPosted: Thu May 15, 2008 9:50 am
by mflorell
what is the server_ip set to in astguiclient.conf?

PostPosted: Thu May 15, 2008 10:20 am
by brainwhistler
This is Single server setup, Asterisk , Apache, Mysql and Vicidial all installed on the same server.

Server IP is the IP of the machine where all the above are installed.

Thanks

PostPosted: Thu May 15, 2008 10:53 am
by mflorell
I meant that you should check the server_ip and possibly try another one of the server's IP addresses(like 127.0.0.1) some systems do not have Asterisk listening on all IP addresses for some reason.

PostPosted: Thu May 15, 2008 11:21 am
by brainwhistler
For Server IP (127.0.0.1) it says

unknown remote host: at /usr/share/astguiclient/AST_conf_update.pl line 188

PostPosted: Thu May 15, 2008 12:18 pm
by mflorell
have you tried all IP addresses for the machine?

Have you tried connecting through telnet port 5038 to the manager interface yourself?

PostPosted: Thu May 15, 2008 7:40 pm
by Op3r
check your /etc/astguiclient.conf

also check your firewall it may be blocking localhost but not remote host.

do this

iptables -L

and also check your settings at admin -> Server Settings

PostPosted: Fri May 16, 2008 12:08 am
by brainwhistler
Mett,

I have only one IP Address on this machine. Also, as i mentioned in my earlier post that i can telnet to port 5038 both localhost interactively as well as remotely to IP address and was able to connect to Asterisk Call Manager.


Op3r:

Firewall on this machine disabled, also ' iptables -L ' does not show any result, it is empty.

thanks

PostPosted: Fri May 16, 2008 4:20 am
by mflorell
I believe there might be a trigger in the scripts to log telnet output to a file.

Also, check the servers table settings for the Manager User entries.

PostPosted: Fri May 16, 2008 10:18 am
by brainwhistler
What is the purpose of this script

/usr/share/astguiclient/AST_manager_kill_hung_congested.pl

When I start Asterisk with scipt

/usr/share/astguiclient/start_asterisk_boot.pl

Asterisk seems to be started but does not show at ' ps -ax ' , instead the above script appears as a process.

PostPosted: Fri May 16, 2008 10:23 am
by mflorell
The kill congested process removes channels that are stuck in Congestion status, not really much of a problem anymore, but it can happen still.

The start asterisk script will start Asterisk in a screen so that you can attach to it and see the REAL Asterisk CLI output.

PostPosted: Thu May 22, 2008 1:09 am
by brainwhistler
The problem was with the 'screen' installation. Somehow it was not correctly installed while following SCRATCH_INSTALL document. I found the below post and eventually got the 'Connection refused on port 5038' resolved.

http://www.eflo.net/VICIDIALforum/viewt ... en+command

Thanks to Matt.

Matt:

Can you please shed some light on ViciDial's dependency on 'Screen'.

Also, i tried to install Vicidial using both 2.0.4 and 2.0.4rc2 SCRATCH_INSTALL documents several times, but the connection refuse error was same. As soon as i link the screen following the procedure you mentioned earlier its started working. This seems that Screen-4.0.2 is not being properly installed using ./configure, make and make install.

Please note that all the installations were done on RedHat AS4 at my end.

PostPosted: Thu May 22, 2008 5:23 am
by mflorell
We do not test our installs on RedHat-family systems, only Slackware and OpenSUSE. The dependance on screen is so that an administrator can attach to any of the running processes to debug what is going on on the system at any time. This is especially important with Asterisk because there is some output that is only viewable from the Real Aserisk CLI.

PostPosted: Sat Jun 07, 2008 9:01 am
by seaq
In Red Hat/ CentOS / Fedora systems is better to install the distro packages with the exception from asterisk itself.

So is better not to compile the thing as stated in the SCRATCH install, instead install all the packages required via yum or up2date

PostPosted: Sun Jun 08, 2008 3:10 pm
by Op3r
all you needed was to yum everything which we did to the VicidialNOW distro. Well except we used rpm on the perl modules and such.

Also when you install on red hat or centos better modify the kernel preemption to SERVER from DESKTOP.


Installing in Centos is easier, but we all have our own preferences on doing it right.

PostPosted: Sun Jun 08, 2008 4:34 pm
by mflorell
I haven't checked your latest VICIDIALnow version, but what version of the astersk-perl module are you using?

There is still a bug in the 0.10 version which we cannot seem to get the creator to fix, so we are still loading the 0.08 version.