Page 1 of 1
All in one setup to Cluster setup
Posted:
Thu Mar 06, 2014 8:12 am
by richardroi
Support,
I wanted to ask, will it work if I Restore the database from all in one server to a cluster setup? Do i need to backup all? what are my options? We are adding agents and i want to do the cluster.
My existing server is running on ViciBox v.5.0.2-130807 | BUILD: 130809-1410 | Asterisk: 1.8.23-vici |64bit Single Server/ ISO Preload Install Version: 2.8b0.5 SVN Version: 2016|DB Schema Version: 1355
Thank you.
Re: All in one setup to Cluster setup
Posted:
Fri Mar 07, 2014 5:46 pm
by richardroi
Anyone? Need advice. Thank you.
Re: All in one setup to Cluster setup
Posted:
Fri Mar 07, 2014 9:39 pm
by williamconley
yes it's possible.
but: why don't you just add servers to the existing standalone?
be sure to use the standard install for the cluster additions, not the preload.
Re: All in one setup to Cluster setup
Posted:
Mon Mar 10, 2014 9:57 am
by richardroi
I wanted to separate the database/web server to telephony servers.
"1 database/webserver + 2 0r 3 telephony + 1 archive server (+ 1 backup for archive---still planning)"
if i wanted to backup the database of my standalone and use it on a cluster setup, what are the things needed to backup? --help (which one)
or
If I'm going to add servers on my standalone what are my options? Can i still do my planned setup above? how can i disable the telephony on standalone? should i disable it?
Thank you William as always!
Re: All in one setup to Cluster setup
Posted:
Mon Mar 10, 2014 4:42 pm
by richardroi
got it running thank you william!
Question again: our DID provider is using IP based routing, on 1 standalone + 2 telephony setup, 2 nics each, should I gave them all public ips for it to register? im lost on extenip setings.
Thank you in advance!
Re: All in one setup to Cluster setup
Posted:
Mon Mar 10, 2014 6:33 pm
by williamconley
um ... you just asked what ips to give them for ip based routing and in the same question mentioned "register". The concept of ip based routing means registration is not necessary. i've never met a carrier that required both, but I think it would be cool if they did. LOL
externip settings are not related to that at all. externip=xxx.xxx.xxx.xxx is necessary if you have a private IP address ONLY for your dialer and the value of xxx.xxx.xxx.xxx is then set to the external IP address to assist the sip protocol handlers with routing the calls back to your server (instead of trying to send the audio or other packets to a private IP address when the sending server is NOT on that private network). If you have a public IP for your dialer (directly, not through a router), this is not necessary. if you do not have a public IP, this is necessary.
Re: All in one setup to Cluster setup
Posted:
Tue Mar 11, 2014 5:22 am
by richardroi
Sorry...but still lost.
Ok my running standalone has 2nics. One local and one public. I have my public ip on externip settings. This is correct right? If im going to add 2 telephony servers, will incoming calls route to agents using the new 2 telephony servers? Because i have to setup same carriers on the new servers with different id right?
Need your advice. Thank you.
Re: All in one setup to Cluster setup
Posted:
Tue Mar 11, 2014 11:43 am
by williamconley
public ip does not require externip. the purpose of externip is to broadcast the proper External IP in the sip packets. If you are using the external IP directly on the server, this serves no purpose. However, it also does not hurt anything. Just be sure to change it if you change the external IP address.
This is in no way related to whether or not calls will route to other servers properly, of course. That would require each of them to be set up properly (preferably each with its own external IP).
The only way these intermingle or affect each other is if Registration is involved as the act of registration often says to the VOIP Provider "Send inbound calls here ...". So if you have multiple servers registering to the same voip account ... they can confuse the carrier by all registering to the same account. Generally a bad idea to use the same registration string (account) on more than one server. If you are using IP authentication, then registration is not in use (as a rule).