Interactions for Tenant Partitioning

Last Updated : Oct 04, 2016 |
Prolog information
Metadata
Keywords:
This section provides information about how the Tenant Partitioning feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of Tenant Partitioning in any feature configuration.
Tenant-partition identification is not passed between servers. A network of servers that run Communication Manager does not enforce Tenant Partitioning restrictions without special administration. For example, Tenant Partitioning on a network of servers that run Communication Manager does not enforce tenant-specific tie trunks.
Administration of the following features requires special care to avoid unintended access between tenants.
  • Bridging
  • Call Pickup
  • Call Vectoring
  • Controlled Restriction
  • Facility Busy Indication
  • Facility Test Calls
  • Integrated Directory
  • Inter-PBX Attendant Calls
  • Main/Satellite/Tributary
  • Malicious Call Trace
  • Personal central office (CO) line
  • Private Networking - Automatic Alternate Routing (AAR)
  • Service Observing
  • Uniform Dial Plan
Specific information about how the Tenant Partitioning feature interacts with other features follows.

Automatic Alternate Routing (AAR) and Automatic Route Selection (ARS)

The Tenant Partitioning feature is not the same as the Time-of-Day Plan Numbers or the Partition Groups in AAR and ARS.
However, if you use the Tenant Partitioning feature, you can use the Time-of-Day Plan Numbers and the Partition Groups in AAR and ARS.

Attendant and Attendant Group features

The Tenant Partitioning feature creates multiple attendant groups. Attendant operations such as direct-station or direct trunk group select (DTGS) are subject to tenant-to-tenant restrictions, both at selection time and at split time.
All the calls that an attendant within an attendant group places on hold hear the music source from the attendant group.

Attendant Control of Trunk Group Access

An attendant group controls access to the trunk groups of the tenants that the attendant group serves. An attendant does not control access to any other trunk groups.

Communication Manager Messaging

The system applies the same tenant-to-tenant restrictions to Communication Manager Messaging voice and data ports that the system applies to any other endpoints.
Communication Manager Messaging can restrict one group of subscribers from sending voice mail to another tenant partition group.
Those who control the tenant partitions can:
  • Create 10 different communities within each Communication Manager Messaging
  • Allow voice message access across the community boundaries
  • Deny voice message access across the community boundaries

Authorization Codes

Authorization codes are associated with class of restriction (COR). If you want to assign a unique set of authorization codes to a tenant, you create a unique set of CORs. You only assign the CORs to objects that are within the partition that the tenant uses.

Automatic Wakeup

Those who control a tenant partition assign a music source to the partition. The system uses this music source as the wakeup music for users in the partition.

Bridged Call Appearance

Assign all stations with bridged call appearances to the same tenant.

Call Coverage

The tenant-to-tenant access restrictions apply to coverage paths. The system does not allow a call to cover to a tenant if the tenant-to-tenant access restrictions do not allow the user to call the tenant.
When you specify an attendant in a coverage path, the system accesses the attendant group of the called tenant. The system does not access the attendant group of the calling tenant.
When the system uses the Call Coverage feature for a call, and a user answers the call and then places the call on hold, the system plays the music-on-hold music that is assigned to the original called party.

Call Detail Recording (CDR)

CDR does not report the tenant partition number of the extension or the trunk group that the system uses. You must infer the tenant partition number from the extension or the trunk-group number.

Call Pickup

Assign all stations in a call-pickup group to the same tenant. The system supports Call Pickup only if the caller and the called party can both call the pickup user. The caller and the called party do not need to be in the same pickup group.

Call Vectoring and Vector Directory Number (VDN)

When the system routes a call to a new destination as a result of a vector step, the caller hears the music that is assigned to the last active VDN.
While a call is in vector processing, the system uses the tenant number that is assigned to the active VDN, as determined by VDN Override, to select the music source for callers on hold. Note the following exception. If you use a wait-time <time> hearing <extension>then <treatment 2> command, where the <extension> is a music source, that music source plays instead of the music source that is associated with the active VDN.
The COR that is assigned to the VDN must allow music-on-hold.

Call Management System (CMS)

You can administer CMS to provide CMS reports to each tenant. You can restrict each CMS login to control, on a permission basis, only those entities that are assigned to a particular tenant. Outputs to separate printers allow any tenant to print their own CMS reports. The tenant-partitioning provider must administer CMS to provide this separation of tenant permissions.

Call Coverage and Tenant Partitioning

If a covered call does not route to an attendant in the first tenant group, you can route it to an attendant group of a different tenant partition. For example, you can reroute a call to Tenant Group B if the call is to cover to an attendant for Tenant Partition A  but does not route to the attendant or is received out of hours when Attendant Group A is unstaffed.
To reroute the covered calls to another tenant attendant group, Tenant Attendant group B in this example,
  1. In the vector for the tenant A attendant vectoring VDN, add a failure branch to a route-to ldn_number with cov y if unconditionally step for the LDN extension for the tenant group B TN number.
  2. Set the with coverage parameter of the route-to step must be set to cov y because the calls are covered. Else, the calls don’t route to the VDN. Also, set the Cvg Enabled for VDN Route-to party? field of original coverage path, which covers to Tenant A Attendant vectoring VDN, to y.

Dial Access to Attendant

When a tenant dials an attendant, the tenant accesses the attendant group to which the tenant is assigned.

Emergency Access to the Attendant

When a tenant dials the emergency access, the tenant accesses the attendant group to which the tenant is assigned.

Expert Agent Selection (EAS)

The COR that you assign to the logical agent ID in the EAS system determines whether callers that are on hold hear music. The COR that you assign to the physical extension does not control whether callers that are on hold hear music.

Hunt groups

The tenant number that you assign to the hunt group extension determines the music source that the callers to the hunt group hear while the callers are in queue or on hold.

Intercept Treatment

When access to the attendant is designated as intercept treatment, the caller accesses the attendant group to which the caller is assigned.

Malicious Call Trace (MCT)

The system assigns MCT extensions to tenant partition 1 as the default for the system. If MCT is enabled, any user who has permission to call tenant partition 1 can use MCT.

Multiple Listed Directory Numbers (LDNs)

Assign a tenant partition to each LDN.

Multiple Audio and Music Sources for Vector Delay

When you specify the audio source by a wait-time <time> hearing <treatment> vector step, the audio source that is assigned to the tenant number of the active VDN is the audio source that plays.
If you use a wait-time <time> hearing <extension>then <treatment 2> command where the <extension> is an audio source, that audio source plays instead of the audio source that is associated with the active VDN. For information on administering multiple audio sources, see the Avaya Aura® Call Center 5.2 Call Vectoring and Expert Agent selection (EAS) Reference, 07-600780.

Music-on-Hold Access

You can assign a unique source for music to each tenant.

Night Service

Each tenant can have a listed directory number (LDN) night destination, a trunk answer on any any station (TAAS) port, or a night attendant that only the tenant uses.

PC Interfaces

You must assign each PC interface to a tenant partition.

PC/PBX Connections

You must assign each PC/PBX Connection to a tenant partition.

PC/ISDN

You must assign each PC/ISDN to a tenant partition.

Remote Access

You must assign each remote access barrier code to a tenant.

Traffic Studies

Traffic studies do not report the tenant partition number of the extension or the trunk group. You must infer the tenant partition number from the extension or trunk-group number.

Uniform Dial Plan (UDP)

If a UDP is in place between servers, the system does not pass tenant partition identification between the servers. The system does not enforce tenant-partition restrictions between the servers unless you provide special administration.
Tenant Partitioning restrictions do not override COR restrictions. COR restrictions are independent of tenant partitions.