Difference between revisions of "Multi-Tenant"
(→To convert old Systems) |
(→To convert old Systems) |
||
| Line 24: | Line 24: | ||
==To convert old Systems== | ==To convert old Systems== | ||
| + | The easiest way to go is start a system with multi-tenant. However if you find that you need to switch and 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 | *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 | *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. | *Need to re-save gateways so that they use the new domain. You may need to manually remove the gateway xml files. | ||
Revision as of 17:10, 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.
Contents
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.
System -> Variables
Disable the domain variable so that it is not applied system wide.
To convert old Systems
The easiest way to go is start a system with multi-tenant. However if you find that you need to switch and 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.
