Clustering trixbox boxes

dorient
Posts: 4
Member Since:
2009-02-25

Hi guys,

Sorry if this is in the incorrect forum. But I was hoping someone could help point me in the right direction. I was wanting to setup trixbox to a similar fashion as how you can setup Cisco Call Managers. As I was thinking of hosting my main trixbox in a datacentre, and just having a smaller trixbox setup in my office, so that all my VOIP phones do not need to traverse my WAN to get the trixbox, and also providing a fail-over/backup box incase the main centre goes down, my phones are still able to make calls.

Any help would be great! Just simplifies and creation of managing different trixboxes at each of my different sites.

Regards,
D



syadnom
Posts: 52
Member Since:
2009-03-21
a mesh or a central point?

For a central point cluster, you can just setup all your trixbox systems and if you are using pro get a link server licenses for each and an the remote systems IP address.

I use CE myself and use a layout something like this:

1 "master" PBX system which has IAX2 trunks to each of the other systems. It has dial patters for direct dialing of remote extensions via the appropriate trunk

trunk to store 1 (has extentions 1XX)
outbound route to store 1 via dial rules 1XX via trunk to store 1
trunk to store 2 (has extentions 2XX)
outbound route to store 2 via dial rules 1XX via trunk to store 2
trunk to store 3 (has extentions 3XX)
outbound route to store 3 via dial rules 1XX via trunk to store 3

I put a matching trunk on the remote systems and name that trunk "cluster". now the "master" PBX can dial all the cluster members.

on the remote machines I put an outbound route that says

[1-9]XX
[1-9][0-9]XX
X
XX

to go via trunk "cluster"

now any remote system can dial the remote system extention which is (site=s and extension=X) sXX or ssXX for 10-99 and so on.

I also put the X and XX in there as I us the site number as the main "ring all" group in each store allowing each site to dial the site # to call the other sites. site 3 can call site 1 by dialing 1.

I just make sure that I have a 911 outbound route as route 0, the IAX2 trunk as 2, and the ZAP trunk for analog lines as 3.

additionally, If I want a more direct link between two sites that are more likely to call each other I add an IAX2 trunk between them and put their dialing pattern in above the "cluster" trunk and put the cluster trunk as the backup route.

This leaves me with a system that requires little engineering as the dialpattern assumes that calls with 3 or 4 digits are either a)they are a local extension as that is matched before outbound routes, b)911 and go out the first trunk, c)they are an intercompany call or d) there are more digits and they should be dialed out the POTS line.

I can add a site and I only need to build the trunk between the new site and the master PBX.

In case it is not clear to you, when site 1 dials 205, it is routed through the outbound route to the master PBX which then applies its dialing rules and sends 205 over the trunk that matches the pattern and proxies the call to site 2 where the extension rings. site 3 can dial 2 and it is routed similarly except rings the ring group "All" at site 2.

This is a very functional system for up to 99 locations which the site would be 99 and extensions 01-99 or a total extension range of 101 to 9999. There would be an issue above that number of branches as one site may have an extention that matches another stores ringall group such as site 101 would not have a dialable ringall group as it would be matched to site 1 extension 1. This could be worked around but I would guess that the vast majority of installs are less than 99 locations.

for initial configuration I typically just backup my /etc/asterisk directory and some other select files from /etc and drop them onto the new system and run system-config-network, install-aastra/snom/linksys/granstream etc as well as setup-sangoma as I use only sangoma cards.

I also am an old linux hacker so use sed on many of the files to replace the base extension numbers so I dont need to edit everything by hand but that is just a quick timesaver.

good luck



syadnom
Posts: 52
Member Since:
2009-03-21
mesh

I didnt mention a mesh setup. I would suggest using the center point managed and then post a few config files on a webserver that has a complete trunk map for the mesh. Then do some scripts is assemble the appropriate config files from this map.

I did a little bit on experimenting with this and it should work well. I am not sure of a package that handles this.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.