NEAX2400 ICS Business Features and Specifications
Page 520
NDA-24143, Issue 4
T-12 Tenant Service
T-12 Tenant Service
General Description
This feature provides for more than one organization (tenant) to share the same PBX. Through system
programming, each organization may be restricted to its own Central Office trunks, ATTENDANT
CONSOLEs [A-3], and extension links. In addition, incoming calls are directed to the specific organization
(tenant).
Operating Procedure
No manual operation is required.
Service Conditions
1. An Attendant Console is normally provided for each tenant. However, when required, a single
common console may be shared by two or more tenants.
2. Inter-office calling between tenants may or may not be restricted, depending on System Data.
3. Different tenants may share a common group of trunks, where required.
4. When a tenant station dials “0” (Operator Call Code), it will be connected to that tenant’s console.
5. Different tenants cannot use the same numbering plan.
6. The same station numbers cannot be assigned among different Tenants (for example, stations
numbered 2XXX can be associated with only one Tenant).
7. STATION-TO-STATION [S-11], CALL TRANSFER [C-11] THREE-WAY CALLING [T-2], TAS [T-
8] and CALL FORWARDING [C-2, 3, 5] calls between Tenants can be restricted or allowed.
8. SMDR [S-10] includes Tenant identification.
9. The same access code can be assigned among Tenants for service features (for example, CALL
HOLD [C-6], CALL BACK [C-1], CALL PICKUP - GROUP [C-7], CALL FORWARDING - ALL
CALLS - D
term
[C-5D], SPEED CALLING [S-3], TAS [T-8], etc.).
10. The SIM (ICS) and IMG
x
can provide TENANT SERVICE [T-12] to a maximum of 15 tenants.
The IMG
xh
, IMG
dxh
, MMG (ICS), and UMG (ICS) and UMG
x
can provide this service to a
maximum of 63 tenants.
Interactions
1. To provide TENANT SERVICE, features need not be separated. Whenever possible, keep
features common to use data memory as economically as possible. When commands are
separated, they must be programmed for each tenant accommodated in System Data 2.
2. FORCED ACCOUNT CODES [F-7] and AUTHORIZATION CODES [A-20] do not require
separate tenant service for AMND, System Data 1, Index 93, Bit 6.
3. Each tenant may have its own Attendant Console(s), unless that number exceeds system
capacity; for example, five tenants in a two-PIM configuration. The number of consoles per
tenant is not limited by programming but is limited by the system configuration.
4. Different tenants may or may not share the same CO trunks. Termination of a trunk is a function
of the ARSC command. DID trunks can be assigned to any tenant. However, the Listed Directory
Number, as assigned in the ALDN command, determines where the call terminates. If the
incoming LDN digits are assigned against Tenant 2, the call terminates to the Tenant 2 Attendant
Console, even if the digits come on a Tenant 1 trunk.
To Next Page
Loading...
