From FusionPBX
Jump to: navigation, search

Mutli-tenant is done using Fully Qualified domain names (FQDN). They can be full domains or sub-domains are used. The domains separate the information between tenants. The domains need to be pointed to the FusionPBX server.

Advanced -> System Settings

To setup multi-tenant in FusionPBX 3.x or higher add more than one domain under advanced -> domains. Choose a domain name that you are not planning on changing. It is possible to change a domain name but requires the domain to be changed in several places. After adding the second domain restart the internal sip profile this can be done at Status -> SIP Status then restart the Internal SIP Profile.


When adding a new tenant the domain alias will not show up until an extension has been added to the tenant and the internal sip profile has been rescanned or restarted. The alias can be viewed in Status -> SIP Status.

This is done automatically for new domains.

XML Editor -> directory -> default.xml (a.k.a. /usr/local/freeswitch/conf/directory/default.xml) Change the following from...

	<!--the domain or ip (the right hand side of the @ in the addr-->
	<domain name="$${domain}">


	<!--the domain or ip (the right hand side of the @ in the addr-->
	<domain name="<IP>">

Where <IP> is the public, private IP or domain of your FreeSWITCH/FusionPBX install.

User Manager

Accounts -> User Manager when adding a user you have the domain select option that assigns the user to the domain. Tenant admin's highest level of access should not exceed the 'admin' group. Users in the 'superadmin' group are able to view and manage all tenants.

Convert Old Systems

The easiest way to get started with multi-tenant is to begin using it before configuring the system. However if you find that you need to switch an existing system to multi-tenant you will need to do the following.

  • Each extension needs to be changed to use the correct domain name
  • Each dialplan entry will have to have its context adjusted to use the correct domain name.
  • Need to re-save gateways so that they use the new domain. You may need to manually remove the gateway xml files.
  • On old system you have to either add some additional variables or rebuild your inbound and outbound routes


If transfering calls (blind) aren't working for you...

to top of: conf/dialplan/

  <context name="">
    <extension name="setdomain" continue="true">
    <!-- The channel variable isn't passing on calls
             Not sure why, but this is a workaround -->

      <condition field="destination_number" expression="^.*$">
        <action application="info"/>
        <action application="set" data=""/>
        <action application="set" data="domain_name=${domain}"/>
        <action application="log" data="INFO NOW WE HAVE SET domain_name"/>
        <action application="info"/>

ABOVE fixes for all calls generated internally, for inbound calls we need to fix the public profile:

Change in conf/dialplan/public.xml:

    <extension name="public_extensions">
      <condition field="destination_number" expression="^(10[01][0-9])$">
        <action application="info"/>
<!--    <action application="transfer" data="$1 XML default"/> changed to get inbound calls to transfer properly-->
        <action application="transfer" data="$1 XML ${domain_name}"/>

You still cannot transfer to internal conferences (*3000). Probably need to set something up under conf/diaplan/public/ or some such.

Otherwise, just use a conference that you did set up through apps->Conferences, and add it to the inbound routes page... could also add a *3000 whatever route there too. For *3000 add something like this to public.xml

    <extension name="public_extensions_conf">
      <condition field="destination_number" expression="^^(\*300[0-9])$">
        <action application="info"/>
        <action application="transfer" data="$1 XML ${domain_name}"/>

If you changed your extensions from the default 1000-1019, you will need to edit these as well.