Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
DomeDan wrote:look in the asterisk CLI and post the response you get when the registration fails
uperformkarthick wrote:Did you made necessary changes Admin servers sections?
Thanks
Karthik Raja
williamconley wrote:Before I begin: Please post a link to your installation instructions since you did not install from .iso (so that others using that same link may help YOU and perhaps benefit from your question/answers if it turns out to be installation related).
If you log on to Vicidial on the DB server (.15) and on the new dialer (.30), is the information the same? (IE: If you make a change on one, is that change reflected in the other? Sharing data?)
2) You stated that .15 is the db and .30 is the dialer. If you check /etc/astguiclient.conf for the value of "db server" in each, do they both show ".30"? (the .30 server may show "localhost" instead, of course)
3) If you check "server ip" in each of the, do they show their own ip? (ie: the .15 server should show .15 and the .30 server should show .30)
4) In Admin->Servers are there two entries: one for .15 and one for .30?
5) When you added the carrier for the dialer, does the IP for that carrier (under admin->carriers) show ".30"?
Yep. (For now, after it's up and running you can play with turning that off.)yes there are two entries , one for .15 and one for .30. I have a question here, should both these severs be enabled?
VARDB_server should be .15, not .30 if .15 is the db ...for db server
VARDB_server => 127.0.0.1
for dialer
VARDB_server => 192.168.1.30
Under Admin->Servers change "Rebuild conf files" to "Y" for each of them while observing the asterisk CLI. At roughly the :01 mark the asterisk CLI should reflect a "reload" of the asterisk dialplan on each. If this only happens on one server *twice* and never on the other server at all ... one of them is confused. There must be an entry in astguiclient.conf on the confused server that makes it believe it is the wrong machine. What do you have for VARserver_ip for each?
== Parsing '/etc/asterisk/asterisk.conf': Found
== Parsing '/etc/asterisk/extconfig.conf': Found
Connected to Asterisk 1.4.39.1-vici currently running on vicidial2 (pid = 962)
Verbosity was 0 and is now 5
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on 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
== Manager 'sendcron' logged off 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
williamconley wrote:VARDB_server should be .15, not .30 if .15 is the db ...for dialer
VARDB_server => 192.168.1.30
VARserver_ip should be .15 on the .15 and .30 on the .30 ... but the VARDB is meant to identify the DB server on all servers in the cluster (the exception is the DB server itself which may say 127.0.0.1 or localhost, otherwise the DB server's IP should be here).
vicidial2*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
0 sip peers [Monitored: 0 online, 0 offline Unmonitored: 0 online, 0 offline]
williamconley wrote:it would appear you are either incorrect about one of the values in astguiclient.conf or your installation has a flaw.
when the keepalive script (and any of the others) run, they first load the astguiclient.conf file so they know "which server they are". based on this information, they gather data from the database and take action. if your .15 (DB) server takes action meant for .30 ... either it has a reason to believe it is .30 or the system is broken.
try runing the keepalive script in debug mode and consider causing it to expose variables during execution to see if it believes it is .30 or that it has no ip and just executes everything by default for some reason.
Users browsing this forum: Google [Bot] and 81 guests