Adding Service Provider Tenants

Enter the name of the Service Provider account.

This operator manages services running on devices that connect directly to Live Platform over HTTP. Connection requests sent to Live Platform by these devices are managed through this operator. In the example below, the assigned HTTP Operator is 'irOperator' for the Interaction Insights service (the Operator name should logically identify the service).

This operator is used by the following services:

This parameter facilitates generating statistics on calls made exclusively from URIs in a specific tenant. Operators can run a regional expression to find the URIs associated with the specific tenant and then generate statistics exclusively on them.

Enter the tenant's subnet mask. Must be in prefix format x.x.x.x/y. For example: 255.255.0.0/16. For any region under the tenant, subnet mask is not mandatory, but if it is configured, its subnet mask must be within the tenant's, for example, 255.255.0.0/1.

Service Provider Azure Tenant ID.

This option can be configured when Live Platform is deployed behind a different NAT to customer tenants. It allows the configuration of an applicative level NAT interface for each tenant domain; Devices’ incoming communication like SNMP traps, license reports and file upload/download will communicate via the tenants’ NAT interface.

The name of the tenant domain that is used for connecting devices to Live Platform. When defined and the parameter "FQDN Support for Auto-Detection" is enabled (see Global Configuration), devices that are connected to Live Platform are automatically added under the relevant tenant instead of to the default Auto Detection region.

If your enterprise uses Live Platform's internal email server for Alarms Forwarding, use this parameter to configure the internal mail server’s 'From Address'. For example, if you configure adelev@TrunkOperator.com for this parameter and you configure 'Adele Vance' for the parameter following in this table ('Internal Mail Server Real Name'), then all alarms forwarded from Live Platform by email from rules configured with 'Use Internal Mail Server' will be from address: adelev@TrunkOperator.com

The corresponding name of the System Administrator configured for the 'Internal Mail Server from Address' above.

Enter a tenant description to facilitate effective management later.

The number of digits to mask from phone numbers in the Calls details.

Enables the Onboarding and management of Compliance Recording customers.

Enables the Onboarding and management of Device Manager customers.

Source email of the tenant.

The Directory (tenant) ID for the Operator Connect Azure registration (see Deploying Microsoft Synergy Application).

The Application Registration (client) ID for the Operator Connect Azure registration (see Deploying Microsoft Synergy Application).

Configure the client secret that was generated in Deploying Microsoft Synergy Application.

Landing Page URL of the Service Provider. Default: Operator Connect.

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

Title

Display name in Live Platform portal.

First Name

Last Name

Work Email address

SIP alias

Primary Work phone number.

Second Work phone number.

List of countries for activating calling.

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. The operator is then assigned to the tenant and displayed in the drop-down list.

Applies to 'tenant' type operators. When an operator logs in to OVOC, OVOC (before allowing the operator access) checks with the enterprise's Azure Active Directory if the User Group which the operator is associated in OVOC is compatible with the User Group defined in Azure Active Directory . If they match, then when logged in, the operator is assigned to this tenant.

Note: this parameter must be configured with the name of the Security Group that you added in Adding Main Tenant Operators and Assigning to Azure GroupsRegistering Live Platform Operation Center Application in Main Tenant.

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 SBC devices 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.

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.

The maximum number of calls that can be stored on the Live Platform server.

The maximum number of calls together with Call Flow that can be stored on the Live Platform server.

The maximum number of Device statistic data entries that can be stored on the Live Platform server.

The maximum number of SIP Connection statistic data entries that can be stored on the Live Platform server.

The maximum number of Sites statistic data entries that can be stored on the Live Platform server.

The maximum number of Endpoints statistic data entries that can be stored on the Live Platform server.

The maximum number of Users statistic data entries that can be stored on the Live Platform server.

The maximum number of URI statistic data entries that can be stored on the Live Platform server.

The maximum number of Location statistic data entries that can be stored on the Live Platform server.

The maximum number of Customer statistic data entries that can be stored on the Live Platform server.