Wiki source code of Multi-Tenant Configuration

Last modified by Scott Gagan on 2021/09/10 22:35
Show last authors
1 iSymphony supports multi-tenant environments via context based routing and a peer naming convention. Each tenant will have it's own context with it's respective name. Once configured, iSymphony will allow individual users of these tenants to login without seeing the other tenant's extensions.
2
3 = (% style="color: rgb(0,0,0);" %)**Example**(%%) =
4
5 Lets say we have the following situation:
6
7 * One Asterisk server with two tenants
8 * Peers are named in with the convention : SIP/<ext>-<tenant id>. Where <ext> is the extension number and <tenant id> is the identifier of the tenant.
9 * Main context entries for each tenant are created with the convention from-inside-<tenant id> where <tenant id> is the identifier of the tenant.
10 * The tenant ID's are "tenant1" and "tenant2"
11 * Both tenants contain two extensions, each with the extension number 100 and 200, for a total of 4 extensions.
12
13 {{info}}
14 (% style="color: rgb(51,51,51);" %)The peer and context structure does not have to follow the structure in the example. The peer names simply have to contain the tenant identifier.
15 {{/info}}
16
17 Note that the Parking lot will be disabled in multi-tenant mode.
18
19 The properties for the tenants would be as follows. Besides these values all other configuration is the same as any Asterisk install. (see the [[doc:iSymphony 2\.8 Documentation.iSymphony Administrator's Guide.iSymphony Configuration (Advanced).Tenant Configuration.WebHome]] section for more details):
20
21 **Tenant1:**
22 Name : tenant1
23 Redirecting Context : from-inside-tenant1
24 Originating Context : from-inside-tenant1
25
26 **Tenant2:**
27 Name : tenant2
28 Redirecting Context : from-inside-tenant2
29 Originating Context : from-inside-tenant2
30
31
32
33

Search

Navigation

iSymphony