Tenants: Difference between revisions

From MiRTA PBX documentation
Jump to navigation Jump to search
(Created page with "There is no limits on the number of tenants that can be defined (except if you are running the single tenant license, in that case, the max number of tenants is two). file...")
 
No edit summary
Line 8: Line 8:
'''# Ext''' shows the number of extensions defined / the maximal number of extensions allowed for the tenant
'''# Ext''' shows the number of extensions defined / the maximal number of extensions allowed for the tenant
'''#DID''' shows the number of DIDs defined / the maximal number of DIDs allowed for the tenant
'''#DID''' shows the number of DIDs defined / the maximal number of DIDs allowed for the tenant
Parking lots numbers can be changed, but you need to restart the res_parking module. You can do it using the Admin/PBX Nodes, choosing the “Parking” icon. No calls are needed to be parked to restart the res_parking module.


[[file:toptenant.png|400px]]
[[file:toptenant.png|400px]]
Line 16: Line 14:


'''Allow onnet calls from this tenant''' defines if calls made by this tenant to numbers hosted in the system will be delivered directly (On NET) or if they will be delivered to the provider
'''Allow onnet calls from this tenant''' defines if calls made by this tenant to numbers hosted in the system will be delivered directly (On NET) or if they will be delivered to the provider
'''Allow onnet calls to this tenant''' defines if calls made by other tenants to numbers hosted in this tenant will be delivered directly (On NET) or if they will be delivered to the provider. These options can be useful to obey to telecommunication laws or when setting up a tenant while migrating it from other systems.
'''Allow onnet calls to this tenant''' defines if calls made by other tenants to numbers hosted in this tenant will be delivered directly (On NET) or if they will be delivered to the provider. These options can be useful to obey to telecommunication laws or when setting up a tenant while migrating it from other systems.
''' Allow any Caller ID usage when dialing out''' permits to the tenant to use any Caller ID for dialing out. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first DID will be used as Caller ID.
''' Allow any Caller ID usage when dialing out''' permits to the tenant to use any Caller ID for dialing out. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first DID will be used as Caller ID.
'''Allow any Caller ID usage when dialing out an emergency number''' permits to the tenant to use any Caller ID for dialing out an emergency route. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first Emergency enabled DID will be used as Caller ID.
'''Allow any Caller ID usage when dialing out an emergency number''' permits to the tenant to use any Caller ID for dialing out an emergency route. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first Emergency enabled DID will be used as Caller ID.
'''Alert email''' permits to specify an email to be used to alert on any anomaly of the system, like low credit, call loops or abuse detected
'''Alert email''' permits to specify an email to be used to alert on any anomaly of the system, like low credit, call loops or abuse detected
'''Default timezone''' specify the timezone used by the tenant. Take in mind the Call History is still shown in the server timezone.
'''Default timezone''' specify the timezone used by the tenant. Take in mind the Call History is still shown in the server timezone.
'''Routing profile''' sets the routing profile to be used for the tenant
'''Routing profile''' sets the routing profile to be used for the tenant
'''Call campaign routing profile''' if specified, allows to use a different routing profile for call campaigns
'''Call campaign routing profile''' if specified, allows to use a different routing profile for call campaigns
'''SMS routing profile''' specifies the routing profile for SMS
'''SMS routing profile''' specifies the routing profile for SMS
'''Cronjob server''' assigns a server to execute cronjobs scheduled for the tenant
'''Cronjob server''' assigns a server to execute cronjobs scheduled for the tenant
'''Campaign server''' defines the server on which execute call campaigns scheduled for the tenant
'''Campaign server''' defines the server on which execute call campaigns scheduled for the tenant
'''Status'''' can be used to disable the tenant. No calls will be possible once the tenant is disabled. An expiration date can be set, so the tenant will be disabled past that date.
'''Status'''' can be used to disable the tenant. No calls will be possible once the tenant is disabled. An expiration date can be set, so the tenant will be disabled past that date.
[[file:parkinglots.png|400px]]
Parking lots numbers can be changed, but you need to restart the res_parking module. You can do it using the Admin/PBX Nodes, choosing the “Parking” icon. No calls are needed to be parked to restart the res_parking module.

Revision as of 23:15, 10 December 2016

There is no limits on the number of tenants that can be defined (except if you are running the single tenant license, in that case, the max number of tenants is two).

Tenants.png

In the main screen you can have a general view of your tenants.

# Channels shows the number of channels currently in use (only outbound or inbound calls are counted, internal calls are not counted) / the maximal number of channels allowed for the tenant # Ext shows the number of extensions defined / the maximal number of extensions allowed for the tenant #DID shows the number of DIDs defined / the maximal number of DIDs allowed for the tenant

Toptenant.png

When defining a tenant you need to provide the tenant code that will be used to create all username for the tenant. It is really important to choose a good tenant code. Please avoid using numbers or any characters different than normal alphabetic letters (mixing upper case and lower case is good). The reason for avoiding any number or character signs is due to some phone limitation to manage BLF and speed dial keys when associated with non numeric characters.

Allow onnet calls from this tenant defines if calls made by this tenant to numbers hosted in the system will be delivered directly (On NET) or if they will be delivered to the provider

Allow onnet calls to this tenant defines if calls made by other tenants to numbers hosted in this tenant will be delivered directly (On NET) or if they will be delivered to the provider. These options can be useful to obey to telecommunication laws or when setting up a tenant while migrating it from other systems.

Allow any Caller ID usage when dialing out permits to the tenant to use any Caller ID for dialing out. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first DID will be used as Caller ID.

Allow any Caller ID usage when dialing out an emergency number permits to the tenant to use any Caller ID for dialing out an emergency route. If a different Caller ID usage is attempted, an alert will be shown in the Call History and the first Emergency enabled DID will be used as Caller ID.

Alert email permits to specify an email to be used to alert on any anomaly of the system, like low credit, call loops or abuse detected

Default timezone specify the timezone used by the tenant. Take in mind the Call History is still shown in the server timezone.

Routing profile sets the routing profile to be used for the tenant

Call campaign routing profile if specified, allows to use a different routing profile for call campaigns

SMS routing profile specifies the routing profile for SMS

Cronjob server assigns a server to execute cronjobs scheduled for the tenant

Campaign server defines the server on which execute call campaigns scheduled for the tenant

Status' can be used to disable the tenant. No calls will be possible once the tenant is disabled. An expiration date can be set, so the tenant will be disabled past that date.

Parkinglots.png

Parking lots numbers can be changed, but you need to restart the res_parking module. You can do it using the Admin/PBX Nodes, choosing the “Parking” icon. No calls are needed to be parked to restart the res_parking module.