multiserver setup carrier does not register

[sayantandas]

i have two machines with vicidial installed on Ubuntu 10.04 64 bit nistall. both are standalone servers on the same subnet. below is the confiugration

Vicidial: VERSION: 2.6-370a BUILD: 120529-2112 | Asterisk 1.4.39.1 | PHP5 v5.3.6 | Ubuntu 10.10 x86_64| Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Pentium(R) Dual-Core CPU E5700 @ 3.00GHz | 1 TB Hard Drive

now i want to use one of them as a DB server and the other for asterisk+webserver. so here is the setup

server 1 - 192.168.1.15 - DB server (this server is currently being used as a standalone server for dialing)
server 2. 192.168.1.30 - Vicidial+Asterisk+ Web server( new server with vicidial installed)

I followed the steps of the pound team cluster server guide. I have changed the db ip address to server 1, updated server ip using perl script , After follwoing the guide, when I try to register any sip account or carrier , it does not get registered in server 2. Instead, it still gets registered with server 1 if i change the server ip address. i cannot figure out what i am missing. any help would be very helpful

[DomeDan]

look in the asterisk CLI and post the response you get when the registration fails

[uperformkarthick]

Did you made necessary changes Admin servers sections?

Thanks
Karthik Raja

[sayantandas]

look in the asterisk CLI and post the response you get when the registration fails

There is no response of failure. it gets registered with asterisk in DB server no matter what!

Did you made necessary changes Admin servers sections?

Thanks
Karthik Raja

I have added a new server, and set it as active. The funny thing that is happening is that whenever i make any changes or additions to the phones or carriers on the DB server , sip-vicidial.conf is changed in the DB server ( 192.168.1.1) instead of the asterix server ( 192.168.1.30)

For reference, the servers are below.

server 1 - 192.168.1.15 - DB server (this server is currently being used as a standalone server for dialing)
server 2. 192.168.1.30 - Vicidial+Asterisk+ Web server( new server with vicidial installed)

[williamconley]

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).

Back to your problem, there are several possibilities, but lets start with a quick test.

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"?

[sayantandas]

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).

http://wiki.vicidial.org/index.php/VICI:UbuntuInstall

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?)

Yes, both servers reflect the changes if i make changes on either server on vicidial gui.

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)

for db server
VARDB_server => 127.0.0.1

for dialer
VARDB_server => 192.168.1.30

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)

Yes

4) In Admin->Servers are there two entries: one for .15 and one for .30?

yes there are two entries , one for .15 and one for .30. I have a question here, should both these severs be enabled?

5) When you added the carrier for the dialer, does the IP for that carrier (under admin->carriers) show ".30"?

Now, here is the problem. I have two servers in the dropdown. If I select the dialer server, .30, the config files get saved in the db server .15 not the dialer server. And I cannot understand why.

[williamconley]

yes there are two entries , one for .15 and one for .30. I have a question here, should both these severs be enabled?

Yep. (For now, after it's up and running you can play with turning that off.)

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?

Wait a minute:

for db server
VARDB_server => 127.0.0.1

for dialer
VARDB_server => 192.168.1.30

VARDB_server should be .15, not .30 if .15 is the db ...

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).

[sayantandas]

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?

The dialplan reloads twice on db server when the TestAsterisk server is submitted and the dialplan reloads twice on the dialer server when the new server is updated.

Here is the releoad for the dialer server

Code: Select all

== 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


for dialer
VARDB_server => 192.168.1.30

VARDB_server should be .15, not .30 if .15 is the db ...

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).

sorry, my mistake, the VARDB_server ip is .15 on the dialer server. Server ip is correctly typed in.

Also, I have added
in dialer server (.30)
VARactive_keepalives => 12345678

and in db server (.15)
VARactive_keepalives => 123468


And rebooted the server, still nothing is registereing on the dialer server. All changes from vicidial still gets appended to sip-vcidiail.conf on the db server(.15)

on asterisk on dialer server:

Code: Select all

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]

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.

[sayantandas]

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.

Ok. Thanks for your input willaim. I will try the debug mode. I have a question though. currently the db server (.15) is being used as a standalone server, agents are dialing from that server. Should I disable any service on the db server to make the multiserver setup work?

[williamconley]

No. In fact it is entirely possible to use ALL services on ALL servers simultaneously except that mysql will only be used on one of the servers for the data.