Difference between revisions of "Multi-Tenant"
From FusionPBX
(→Advanced -> System Settings) |
|||
| Line 1: | Line 1: | ||
| − | Mutli-tenant is done using Fully Qualified domain names. Often sub-domains are used. The domains help separate the information between tenants. The domains need to be pointed to the FusionPBX server. | + | 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== | ==Advanced -> System Settings== | ||
To setup multi-tenant all domains under advanced -> system settings need to use the following convention. | 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/ | The paths below assumes that the FreeSWITCH conf directory is installed to /usr/local/freeswitch/conf/ | ||
| Line 17: | Line 18: | ||
==Internal Profile== | ==Internal Profile== | ||
| − | + | In internal.xml comment out the 3 entries that force the domain. | |
| + | |||
| + | |||
| + | ==To convert old Systems== | ||
| + | *The context for each extension needs to be changed to the domain name | ||
| + | *system -> variables you need to drop the domain because it is set on inbound routes | ||
| + | *On old system you have to either add some additional variables or recreate your inbound and outbound routes | ||
Revision as of 16:53, 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
Internal Profile
In internal.xml comment out the 3 entries that force the domain.
To convert old Systems
- The context for each extension needs to be changed to the domain name
- system -> variables you need to drop the domain because it is set on inbound routes
- On old system you have to either add some additional variables or recreate your inbound and outbound routes
