KUMARULLAL
Guru
- Joined
- Feb 20, 2008
- Messages
- 243
- Reaction score
- 28
Just for fun, I wanted to try out the multi tenant scenario on incrediblepbx platform.
Here is the idea.
Create 2 sets of extensions for 2 tenants on freepbx.
For tenant 1 start with extensions 1000, 1001, 1002 etc.
For tenant 2 start with extensions 2000, 2001, 2002 etc
Create separate ring groups, call pick up groups and paging for each tenants.
Create directories for extensions 1xxxx and extens 2xxx. (This is because when you create IVR for the 2 tenants, the caller will not be sent to other set of extensions if the caller dials wrong extensions by mistake.
Create a dial plan so that extensions falling under 1xxx cannot dial 2xxx and vice a versa.
Create 2 trunks from voipms or any other provider and create inblound and outbound routes for them.
Make sure the outbound route ment for tenant 1 should use trunk for tenant 1 as the 0 priority. Then add trunk for tenant 2 as 1 priority.
Inbound routes for tenant 1 should only route calls to tenant 1.
Inbound routes for tenant 2 should only route calls to tenant 2.
Then from the module admin, download and install "custom context" module from unsupported repo.
Create 2 custom context for tenat 1 and 2 respectively.
In the route only select the outbound route for tenant 1 and deny route for tenant 2 and vice a versa.
Finally, edit all extensions with 1XXX and select the custom context meant for tenant 1 and vice a versa.
That is it.
Try it out.
Here is the idea.
Create 2 sets of extensions for 2 tenants on freepbx.
For tenant 1 start with extensions 1000, 1001, 1002 etc.
For tenant 2 start with extensions 2000, 2001, 2002 etc
Create separate ring groups, call pick up groups and paging for each tenants.
Create directories for extensions 1xxxx and extens 2xxx. (This is because when you create IVR for the 2 tenants, the caller will not be sent to other set of extensions if the caller dials wrong extensions by mistake.
Create a dial plan so that extensions falling under 1xxx cannot dial 2xxx and vice a versa.
Create 2 trunks from voipms or any other provider and create inblound and outbound routes for them.
Make sure the outbound route ment for tenant 1 should use trunk for tenant 1 as the 0 priority. Then add trunk for tenant 2 as 1 priority.
Inbound routes for tenant 1 should only route calls to tenant 1.
Inbound routes for tenant 2 should only route calls to tenant 2.
Then from the module admin, download and install "custom context" module from unsupported repo.
Create 2 custom context for tenat 1 and 2 respectively.
In the route only select the outbound route for tenant 1 and deny route for tenant 2 and vice a versa.
Finally, edit all extensions with 1XXX and select the custom context meant for tenant 1 and vice a versa.
That is it.
Try it out.