Add Main Tenant to Live Platform

Enter the name of the Service Provider account.

Defines the default tenant. Only one tenant can be the default.

Note: it is mandatory to configure a default tenant as its required for using the Auto Detection mechanism for adding devices automatically to One Voice Live.

This drop-down list shows all the 'tenant' operators with Admin privileges assigned to this tenant. To manage the Fixed License Pool, it  is  mandatory to select one of these 'tenant' operators from  the drop-down. After selecting a 'tenant' operator, the association cannot be removed (and they're automatically displayed under the Operators tab (see following).

Enter a tenant description to facilitate effective management later.

Enter an encrypted SNMP read community string. The default value for the SNMP read community string is taken from the SNMP main template.

Enter an encrypted SNMP write community string. The default value for the SNMP write community string is taken from the SNMP main template.

Enter a name for SNMP v3. Example: OVOC User.

From the drop-down, select one of the following:

From the drop-down, select either:

Enter an Authentication Key. The default is taken from main SNMP template.

Select one of the following:

Enter the device Web server user name. Example: Admin. Password - "Admin".

The default is taken from the main HTTP template.

Enter the Web server password. Example: Admin.

The default is taken from the main HTTP template.

From the drop-down, select an operator from the list of operators. Only operators configured as 'tenant' type operators are displayed. The list will be empty if no such operator has been configured, in which case you can click the button described next, to add a 'tenant' type operator. The parameter lets you assign an operator – or operators – to the tenant. see Adding Local System Operators (Optional) for more information about configuring 'tenant' type operators.

Operator authentication can be configured locally, in the OVOC (see "Configuring Operator Authentication Locally" in the OVOC User’s Manual).

Click the button to add a new 'tenant' type operator; the 'Tenant Operator Details' screen opens (see ). The operator is then assigned to the tenant and displayed in the drop-down list.

Enter the total number of devices that can be managed by this tenant's License Pool, i.e., CloudBond 365 devices, SBC devices, gateway devices and MSBR devices allowed by your license. The parameter only defines systems. It does not include phones.

Enter the number of SIP endpoints that can register with the SBCs allowed by your license.

Enter the number of concurrent call sessions supported by the SBCs in your deployment.

Enter the number of SBC signaling sessions supported by the SBCs in your deployment.

Enter the number of SBC transcoding sessions supported by the SBCs in your deployment.

Support pending. Currently unsupported.

Support pending. Currently unsupported.

Enter the number of CloudBond 365 users per tenant. Divide the total number of CloudBond 365 users allowed by your license, by the number of tenants in your deployment. If you purchased a license for 1000 CloudBond 365 users and you have four tenants in your deployment, 250 users can be allocated to each tenant. You cannot exceed the total number of CloudBond 365 users covered by your license. It's your decision how to distribute them over tenants.

Support pending. Currently unsupported.

Voice Quality

Enter the number of SBCs, gateways and MSBRs that can be mon- itored in this tenant.

Enter the number of endpoints that can be monitored in this tenant.

Enter the number of concurrent call sessions the SBCs deployed in this tenant.

Enter the number of users supported by the SBC/s deployed in this tenant.

Select the number of reports to allocate to the tenant. In the example here, a total of 5 can be allocated. If 6 are chosen, the indication bar turns red alerting you that the total has been exceeded.

Endpoints Management