GoAutoDial GUI Connection Problems. Can See Dialer Fro

[Travis Lambert]

GoAutoDial GUI Connection Problems. Cant See Dialer From Inside Network, But can access dialer from the outside fine.

GoAutoDial 2.1 ISO, Vicidial 2.4 CentOS5, No Special Hardware.

OK here this is a new one on me. I have spend several days trying to figure out why I can access the Vicidial Admin page, what is really strange is that I can hit the box from the outside all day long. But when I am inside the network, Firefox times out.

Things I have Tried:

ping my 99.125.x.x from inside the network = good
ping my gateway 99.125.x.142 = pings are good
tryed stopping iptables = didnt help

Checked IPTABLES Settings:

#VICIDIAL FIREWALL RULES
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
# Uncomment line below if you have 2 NICs and eth1 is public
#-A RH-Firewall-1-INPUT -i eth0 -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 5060 -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 4569 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
#-A RH-Firewall-1-INPUT -m tcp -p tcp --dport 3306 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10000 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 5038 -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 10000:65000 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A INPUT -p tcp -m tcp --dport 25 -j ACCEPT
-I INPUT -s 173.x.x.x -j DROP
-I INPUT -s 200.x.x.x -j DROP
-I INPUT -s 140.x.x.x -j DROP
-I INPUT -s 173.x.x.x -j DROP
-I INPUT -s 82.x.x.x -j DROP
-I INPUT -s 210.x.x.x -j DROP

COMMIT

Ran update_server_ip= when I had to change the IP = Static address is 99.125.x.140
changed sever ip address from the 192.168.x.x to 99.125.x.140 under the Admin >Server
submitted my change and even rebuild the configuration file once saved.

Hardware Specs On The Box

box has a 64 Bit processor, Dual-core (2 Core), 1.30 GHz,4 GBRam 500Gig HDD. <-- This could very well be the problem, but not real sure.

My inside network can not access the server from any pc with a 192.168.1.x , or the Fire Fox Page say " Connection was reset", outside the network no problem.

Nat is turned off in my router.

I am really thinking its somewhere in the IPTables, maybe routing issues
or the system is a 64bit system and the GoAutoDial2.1.ISO is for 32bit systems, but not real sure

Thanks Guys..

[williamconley]

1) it's not iptables, just turn them off to prove that.

2) it will be a basic understanding of the network that causes the problem. Try using two network cards as discussed here: viewtopic.php?f=4&t=25085&p=86520#p86520

[Travis Lambert]

Yea I was thinking on adding two NIC cards.
One with inside address, the other outside. Lol
Yea the only thing I was thinking was routing. But I
always turn off iptables first, .... Using the

service iptables stop ...

So I will set those.. when I am done I will update
the results to the forum.

Thanks Willliam and yes I am still on board. Lol

[williamconley]

routing is simple:
the external nic connection will have a "gateway". the internal will not. all internet (non-local) traffic will go through the external gateway (since it's the only gateway).

[Travis Lambert]

Yea I was going to set all staic up on one NIC, then
Set the ip address with just a 192.168.x.x and subnet
, not assigning a gate way. Just hoping when I install the
New NIC, Linux doesn't freq out and throw a kernal panic. Lol

[Travis Lambert]

Sorry for not replying sooner, I promise I will post my steps
To the forum. Thanks for all ur help, been really busy
Trying to support the dialer. Lol

[williamconley]

in vicibox, there is nothing to post really. all you have to do is enter yast network and add a new ip/subnet to the newly visible card after you physically install it. and *poof* you're on a second network. too easy. no freq

so:
1) yast network
2) note the existing network card
3) shut down
4) add new nic
5) start up
6) yast network
7) locate the new nic
select the new nic and add ip/subnet
9) save and exit

You are now on two networks.

IF your new network is not a normal private network, you may need to modify sip.conf local networks list so it recognizes it as local and asterisk responds accordingly ... but i've only had one client who had a non-standard private network ip range and needed that.

[Travis Lambert]

Ok William, I have it running, starting to have trouble with the snom phones
not registering. Asterisk CLI keeps saying wrong phone password.
Everything connects fine from the remote end just fine with softphone.
SNOM phones I am going to set the host pointing to the 192.168.X.X, instead
of pointing to the outside ip . I have deleted and recreated the phone. Still same issue,
I am also going to check to see if I can use use AIX instead of SIP, to see if that has some barring. Lol
But othere than that the dialer works good.

Note: when getting a second Ethernet adapter. Make sure the card is compatiple with Linux. Lol