Difference between revisions of "Multi-Tenant"

From FusionPBX
Jump to: navigation, search
(Internal Profile)
Line 17: Line 17:
 
  /usr/local/freeswitch/recordings/example1.domain.com
 
  /usr/local/freeswitch/recordings/example1.domain.com
  
==Internal Profile==
+
==Advanced -> SIP Profiles -> Internal==
In internal.xml comment out the 3 entries that force the domain.
+
Edit the internal.xml file and add the following comments <!-- and --> for the following 3 entries.
 +
 
 +
*force-register-domain
 +
*force-subscription-domain
 +
*force-register-db-domain
 +
 
 +
<!--all inbound reg will look in this domain for the users -->
 +
<param name="force-register-domain" value="$${domain}"/>
 +
<!--force the domain in subscriptions to this value -->
 +
<param name="force-subscription-domain" value="$${domain}"/>
 +
<!--all inbound reg will stored in the db using this domain -->
 +
<param name="force-register-db-domain" value="$${domain}"/>
  
 
==System -> Variables==
 
==System -> Variables==

Revision as of 17:44, 28 June 2011

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

Advanced -> System Settings

To setup multi-tenant all domains under advanced -> system settings need to use the following convention.

The paths below assumes that the FreeSWITCH conf directory is installed to /usr/local/freeswitch/conf/

Set the paths

Extensions Directory:

/usr/local/freeswitch/conf/directory/example1.domain.com

Dialplan Public Directory:

/usr/local/freeswitch/conf/dialplan/example1.domain.com

Recordings Directory:

/usr/local/freeswitch/recordings/example1.domain.com

Advanced -> SIP Profiles -> Internal

Edit the internal.xml file and add the following comments for the following 3 entries.

  • force-register-domain
  • force-subscription-domain
  • force-register-db-domain
<param name="force-register-domain" value="$${domain}"/>
<param name="force-subscription-domain" value="$${domain}"/>
<param name="force-register-db-domain" value="$${domain}"/>

System -> Variables

Disable the domain variable so that it is not applied system wide.

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.

  • The context for each extension needs to be changed to the domain name
  • On old system you have to either add some additional variables or recreate your inbound and outbound routes
  • Need to re-save gateways so that they use the new domain. You may need to manually remove the gateway xml files.