MySQL Clustering / Load Balancing / Replication

[bghayad]

telephony nodes - At first I'll just setup a maximum of 40 phones per node, with a backup node configured on each phone . Eventually I'd like to look at using Opensips or OpenSER to manage all my phone SIP connections across all the vicidial telephony nodes, but I haven't started looking at this properly yet.

* And you have to do the configuration manual or if you configured one IP Phone at one node, it will be replicated at the other node automatically? Or need to be added manually?

The telephony node will take its configuration from the conf files or from the database server. This really I am interesting to understand, so I appreciate to understand.

Regards
Bilal

[bghayad]

Any advise?

Thx
Regards
Bilal

[bghayad]

So I can understand that the vicibox-install will do a cluster only for the telephony servers and not for the sql and web servers? Correct?
Because what I understood that mysql clustered need to be done separately (not through the vicibox-install) and samething for the webserver (there is no clustering because we have to update scripts manual and we have to use load balancer), please correct me.

From the other side, if I used the pl install.pl (this in case I decided to do the installation manually and not using the vicibox CD), in this case: I can not have a clustering for the telephony servers (again, I am assuming that it is the only possible cluster until now as I mentioned above)? Or still I can have the clustering even if I used pl install.pl? HOW? Any document that describes this?

I faced a problem when I used the vicibox-install that it did not find the file "agc_2.2.0" to do the installation, so I have to use the trunk. And when I used the trunk, I found there is a problem in loading dahdi (after restarting the machine, I have to type manually modprob), so I believe it is something related to the version I got from the trunk, it might be not the stable one?

How I can be sure that it is downloading the stable version? Again, why it did not find the file "agc_2.2.0"?

Maybe the below lines need to be midified in the vicibox-install to be able to overcome the So I can understand that the vicibox-install will do a cluster only for the telephony servers and not for the sql and web servers? Correct?
Because what I understood that mysql clustered need to be done separately (not through the vicibox-install) and samething for the webserver (there is no clustering because we have to update scripts manual and we have to use load balancer), please correct me.

From the other side, if I used the pl install.pl (this in case I decided to do the installation manually and not using the vicibox CD), in this case: I can not have a clustering for the telephony servers (again, I am assuming that it is the only possible cluster until now as I mentioned above)? Or still I can have the clustering even if I used pl install.pl? HOW? Any document that describes this?

I faced a problem when I used the vicibox-install that it did not find the file "agc_2.2.0" to do the installation, so I have to use the trunk. And when I used the trunk, I found there is a problem in loading dahdi (after restarting the machine, I have to type manually modprob), so I believe it is something related to the version I got from the trunk, it might be not the stable one?

How I can be sure that it is downloading the stable version? Again, why it did not find the file "agc_2.2.0"? Maybe the below lines need to be modified to find it, but i am not able to know what is the correct one?

### Put us in the right directory for system-specific install stuff
if [ "$USESVN" == "y" ]; then
cd /usr/src/astguiclient/trunk
else
cd /usr/src/astguiclient/agc_2.2.0
fi

I search for agc_2.2.0 at my machine and did not find it !! What could be the reason?

Let me say:
I would like to install the components separately, but I am afraid that for clustering, I have to use vicibox-install (as it is the only method)? Or it can be done separately, and there is a documentation to do a clustering after finishing the components installations (compile and install)?

Appreciate if someone can help me and advise me.
Regards
Bilal

[will_brook]

Hi bghayad,

So we're a bit further down the road of setting up our cluster. To answer you question on how to load balance the phones.

So we use Alias's to help us with this. We're able to setup 1 phone on each telephony node (same password on each phone), then create an alias that combines them all and is used by agents at the logon screen. We use Aastra IP phones which you can configure up to 6 SIP lines on (other models up to 9), we configure each Vicidial telephony node on each SIP line. For example:

Phone: 403a Create on telephony node 1 register on IP Phone
Phone: 403b Create on telephony node 2 register on IP Phone
Phone Alias: 403X Point to Phone extensions 403a & 403b Used as phone registration at agent login.


When I've tested the failover by shutting down a node we noticed that the call will obviously cut off and the advisor will have to shutdown the browser and login again then it'll call the other available SIP extension.

We've yet to see exactly how the phone connections will be managed across nodes when maxed out but I know the system setting PLLB Grouping Limit should enable me to limit connections per node.

Will

[bghayad]

Dears;

There is two branches and the data link bandwidth between them is only 1 Mbps, so is it possible to have one VICIDIAL box in branch 1 and another VICIDIAL box in branch 2, and the database to be replicated (or clustered)? Or the bandwidth is not enough?

Regards
Bilal
GoAutoDial CE 2.1, Communication controller: Digium, Inc. Wildcard TE220 dual-span T1/E1/J1 card 3.3V, Asterisk 1.4.39.1-vici

[randy_delgado_03]

Its still possible for replication. Even if you use mixed in binlog format config, 1mb can carry it on ...