One VoIP SIP trunk carrier multiple asterisk servers

[racosta79]

Hello, I had successfully installed a multi server Vicibox Redux system. I have the following configuration:
1 Web Server
2 Asterisk Servers
1 Database Server
1 Archive Server
My problem is that I need to have both Asterisk Servers working with only one SIP carrier, both online and being redundancy of each other.
In normal operation they will handle calls 50-50, but if one goes down, the other will take all the calls.
I forgot to mention, calls are all inbound now, we are planning to make outbound in the future.
Any ideas?

Thank you in advance.

[Michael_N]

You could have opensips as a frontend to your voip
http://opensips.org/

[williamconley]

Hello, I had successfully installed a multi server Vicibox Redux system. I have the following configuration:
1 Web Server
2 Asterisk Servers
1 Database Server
1 Archive Server
My problem is that I need to have both Asterisk Servers working with only one SIP carrier, both online and being redundancy of each other.
In normal operation they will handle calls 50-50, but if one goes down, the other will take all the calls.
I forgot to mention, calls are all inbound now, we are planning to make outbound in the future.
Any ideas?

Thank you in advance.

get more carriers. you should have three for full production to avoid downtime.

be sure you are backing everything up and TESTING your backups (so you know they will work if they are ever needed! especially the database)

[racosta79]

That will be the opensips after the asterisk servers (inside where my phones will register) or you mean before them to register my carriers?

[DarknessBBB]

Is opensips installable on a vicidial machine??

[GaD]

Although this is a bit old, I'd like to ask if this 'feature' could be added: Add/Remove/Modify one single carrier (on the web management page) that affects all asterisks involved in the cluster instead of having to duplicate the settings of the carrier per asterisk in the cluster.

[williamconley]

It could be added, but there is already a "copy carrier" button that makes this fairly simple. And remember that many facilities use this "feature" to allow each dialer to use a different carrier. So even though all four dialers are using "91NXXNXXXXXX", each of the four dialers sends this traffic through a different carrier to spread the load out among them.

But to answer your question: Yes it would be very possible to write a routine that would allow a carrier addition to apply to all dialers on a cluster instead of just one. Assuming someone is willing to pay for it.

If you want it as a feature, you should post it as a Feature Request on the Feature board with a link to the Vicidial Issue Tracker that you are about to create with the details of how you want this to work. And seriously consider sponsoring this feature with The Vicidial Group (or paying a 3rd party to write the modification).

[GaD]

Well, I already did my own modification, it was no major problem I'm already rsyncing some scripts, I'll just add another thing to rsync and that's it and reload after the rsync. No biggie. It would be a big deal for people that are not so skilled or knowledgeable on Linux...

[williamconley]

rsync? seems like a hammer where a screwdriver was required ... but if it works for you it works. LOL

Just remember that the files in question are wiped clean by Vicidial when generating phones or carriers. So the rsync will need to "repeat" when that happens.

It may be easier to run a sql query that copies the database entry (or modifies it) for one IP when a request is made to the "Master IP" so VICIDIAL will create the carriers on the other servers just as it normally does. The sql query would just be added to the create carrier / modify carrier routines. Then there would be no "oops" if someone changes a phone record and your rsync hasn't run yet. (which will result in "missing" phone calls because there is no carrier ...)

[GaD]

Well..., I already use rsync to sync a bunch of scripts among the servers. Adding one or two more files to move is just like... whatever... so. I will add a cron that will reload the sip/iax/dialplan at least once a day (maybe not even necesary). What I do not want is to have (on the web interface) copies of the same carrier for every dialer I have. My Vici system is one asterisk system among other seven asterisk non-vici and other 4 telephony servers where each performs it's own thing. Although I do not wish to 'star-connect' my Vici I do need to connect Vici to at least 3 other servers; multiply three times the ammount of dialer servers in the Vici 'cluster'....., it's crazy! ....see my point..?

[williamconley]

i'm just sayin that the first time someone makes a change to a "phone" on your vicidial server, the machine to which that phone is attached will rewrite it's configuration file and reload the dialplan and the rsync file will have been overwritten. to disable this feature would mean that you have disabled the ability to modify phones in the admin gui.

[GaD]

Well..., not really. I would be adding the SIP/IAX entries on the sip.conf or iax.conf directly which don't get overwritten with the addition of any extension. Another option could be to add a separate conf file and call it from the sip or iax .conf files directly.

[williamconley]

that would work, but now you have to create the original sip.conf and then let rsync copy it. sounds like a lot of manual work to allow automatic work to take place which is counter-intuitive ... not how we like to set up our automatic stuff. LOL

We lean towards mysql solutions before anything else as those scripts can be external to the system and survive an upgrade. (if you upgrade, it is best to accept the new sip.conf etc files to be sure that any changes in them are accounted for.) so be careful when you upgrade. also, with a mysql solution it can become quite simple to add the mysql queries to the main code with a diff (and said diff would then apply to any upgrades, still upgrade safe).