Blue.

Box Multidomains (Multi-Tenant) Virtual IP Based PBX FreeSWITCH

BY Ignat Kudryavtsev September 29, 2011 Note: This post was originally written in Russian and has been roughly translated into English.

The first decision of multi-domain ( multi-tenant ) Virtual IP PBX based on FreeSWITCH C license Open Source. One of the most popular and sought after services to IP-based telephony to date a virtual IP PBX. This is beneficial for both service provider and customer, as for the first solution is cheap, about the same physical server cluster, there are dozens or hundreds of virtual IP PBX with a large package of services, it reduces maintenance costs, infrastructure complexity, and thus facilitates the support system. For the customer is a large and expensive package, and he has the ability to connect and pay for only those services that he really enjoys. Obviously, no need to purchase your PBX, and perhaps not the cheapest, because often a set of services provided by Virtual IP PBX support is not the cheapest "iron" IP PBX. Summing up, it becomes clear that the service "Virtual IP PBX" is beneficial to all. Many service providers and network operators are constantly looking for different solutions that implement the model. But! Until recently, no ready-made business decisions (ie, free, free, etc.) on the market was not represented. Usually used for virtualization IP PBX Asterisk with which, using different contexts, we can realize the virtual exclusion of clients (Daila their plans) within one copy of the process of Asterisk . But here there is a problem, the complexity of the administration - as customers are constantly asking me to call processing logic, appear and disappear new VoIP trunks and numbers Daila plan is complicated, the number of clients is growing, to give access to clients independently edit configuration

files is absurd and impossible, and not one customer does not want to deal with Daila plan, so the only out in such a situation to write Asterisk configuration management system and display it in the form of Web-based interface, which made some providers. The second option: to use the GUI for Asterisk, FreePBX-example to try to isolate customers with modules custom-context, such an option would work, but still very conventional insulation. Yes, and access to the interface FreePBX again not to give the clients, but the administrator to manage a "virtual PBX" easier. The third option: virtualization at the operating system: There has spread copies of Asterisk virtualisation with OpenVZ package allows you to create virtual containers with copies of the operating systems and run them on Asterisk, such as distribution Elastix, and then give the client full control over the copy of the container, but in this arrangement increases dramatically the complexity and high costs appear to govern. This scheme is suitable only for a small number of customers. And the following is not a free solution Thirdlane - full virtualization Asterisk using a set of scripts. In my opinion a successful implementation with a convenient web interface. Web interface - specially written module to Webmin. Users can have the same extensions in different domains, but the SIP User ID and Web Login must be unique within the entire system. That is, multi-tenant is not implemented with the help of DNS, and unique imenami.Kazhdy tenant (tenant) is completely isolated web interfaces, with which you can configure all the parameters, including the numbering plan and SIP trunks to the operators. Resources limits the tenant is a superadministrator owner of the system. And then there was 3 version FreePBX, which fully supports the alternate phone "engine" Freeswith.Installing Freeswitch and FreePBX v3 devoted a separate article. Now web-configurator FreePBX version 3 is called the Blue Box and fully supports Multi-Tenant, in contrast to the second version. Another important difference, focus on Freeswitch, Asterisk and not as in previous versions. At the moment, support for Asterisk declared, but is deep in the test - with the final distribution ISO now it does not turn on, a warning that the manufacturing operation, it is no good and may be used only for testing and development. Thus, theowner of the project company 2600hz offers two solutions:

A WHISTLE - The commercial solution (license MPL1.1), VoIP platform - driven through the API, scalable and distributed solution is written in the language Erlang, for large loads up to millions of calls per hour. That is the kernel as it is written by developers 2600hz, unlike 2 BLUE.BOX - Open (open source) solution License Mozilla Public License, MultiTenant web-interface for configuring Freeswith and Asterisk, it is written mostly in PHP. Multi-tenant support is implemented through DNS. Blue.box can download the developer's site as a ready-ISO image preconfigured distribution, there are versions for x64 CPU arhetektur and i386. As with all telephone distributions is based on CentOS. ISO includes: blue.box 1.0.2, CentOS 5.5, FreeSWITCH 1.06, FreeSWITCH Sound files, Apache 2.2.3, MySQL 5.1.46, and PHP 5.3.3. Root password: bluebox Access the web-interface http:// (ip address of new machine) / bluebox You can download as an image for Virtual Box or establish of RPM. The source code is available at cd / path to webroot / git clone git: / / github.com/2600hz/bluebox.git bluebox Support for the project as is usually done through a wiki, IRC, maillist, bug tracker (based on Jira) Documentation for configuring http://wiki.2600hz.org/display/bluebox/Home It is interesting that among other things on youtube there are videos on configuration:http://www.youtube.com/user/synapseglobal