@jgiebler wrote:
We have multiple sites (currently 8). We have a Mesh style VPN connecting all sites. Therefore each PBX can directly contact each other PBX. We have a 6 digit extension plan that accommodates our projected growth.
For intersite calling we are using IAX2 trunks to connect each site to each other site.
Our struggle is every time we add a new site, we then have to connect to every other site and add an IAX2 trunk to connect to the new site. When we have say 50 offices, this means that all 50 PBXs will have to have IAX2 trunks to talk to the other 49 sites. Is this scale-able?
We currently like having onsite PBXs at each site. it gives us reliability. It is currently part of our model. PBX, AD, FS and Print Server at each site.
Is there a better way? We considered routing all calls to our central server (in a colo), but many of our sites are on Cable connections. We are concerned that routing all Intersite calls to the central server and then to the destination site could increase latency and jitter to an unacceptable point.
Is there some sort of a "Router" approach? Some central location that looks up which server the dialed extension sits on and then directs the call directly to that server, without actually routing the call through the intermediary server?
If there is not a "router" type approach, is there a scripting resource that we could leverage to "Auto-Add" the new IAX2 trunk (when we bring on a new site) to all existing servers? it would save our team hours of work.
Posts: 1
Participants: 1