Just as Tenant Number (TN) assignment determines the attendant group to which calls are terminated, the TN assignment also determines the VDN to which calls are redirected. If a VDN is administered, attendant group calls are redirected to the VDN rather than the attendant group. If a VDN is not assigned, calls terminate to the associated attendant group.
The selected TN for calls that are covered to an attendant group is the called user’s TN, not the calling user’s TN. When Tenant Partitioning is not administered, the system can have only one partition and attendant group. All attendant group calls are directed to attendant group 1. The screen to administer TN associations is not accessible, so system-wide console assignments apply. To follow the existing principals of this administration, the attendant vectoring VDN assignment appears on the Console Parameters screen when partitioning is turned off. When it is turned on, the field is removed from the console screen and the contents are automatically copied to TN 1.
Note:
Covered calls can be rerouted to an attendant group for a different tenant partition B when the call does not queue to the attendant group for tenant number A or for the out of hours case, and so on. The vector assigned to the attendant vectoring VDN for tenant A needs to include a failure branch to a route-to ldn_number with cov y if unconditionally
step to route to the LDN extension of tenant B. The with coverage
parameter of the route-to step must be set to cov y
and the original coverage path that covers to the tenant A attendant vectoring VDN must have the Cvg Enabled for VDN Route-to party?
field set to y
.
