7.11 Tenant Service
The tenant service feature is implemented using existing features. This means that it is not necessary for users to explicitly configure subsystems.
Users can control permitted and barred connections between individual stations and trunks via traffic restriction groups.
The functionality of all features remains unchanged.
Features in tenant service include:
 |
Intercept |
 |
System number |
 |
Caller list |
 |
Busy override |
 |
DISA |
 |
Speaker call |
 |
Call detail recording |
 |
Hotline destinations |
 |
Text messages, advisory messages |
 |
Internal calls |
 |
Internal directory |
 |
CDB printout |
 |
Night answer |
 |
Hicom Assistant P Office |
 |
Park slot |
 |
Prime Line |
 |
Traffic restriction groups |
 |
Voice mail |
 |
Toll restriction |
7.11.1 Tenant Service Configuration
Definition
The Hicom 150 E Office system can be used as a tenant service, which allows it to be used simultaneously by more than one customer. All features have the same functionality for all customers.
However, certain resources must be divided among the tenants (customers). They can be assigned to one, several, or all tenants. The resources to be divided are:
 |
Stations |
 |
Trunk groups |
 |
PC-AC (Hicom Attendant P) |
 |
Intercept position |
 |
Announcement devices, voice mail |
 |
Traffic restriction matrix (ITR matrix) |
 |
Door opener |
 |
Hotline |
 |
DISA trunks |
 |
Traffic restriction groups determine the ability of tenants to access each other. |
 |
Hotline destinations can be configured for each system. |
 |
A PC-AC can be assigned to each tenant. |
 |
As of Release 2.2 SMR-J, six MOH devices can be defined for six possible ITR groups. This means that the analog interfaces used for connection are part of the ITR groups. Which MOH device is used depends on the ITR group of the station that places the call on hold. You cannot use the logical port "0" as an MOH source. |
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel. 1.0 or later |
- |
- |
Number of tenant service systems |
3 |
3 |
3 |
- |
- |
Hotline destinations |
6 |
6 |
1 |
- |
- |
Announcement devices |
16 |
4 |
1 |
- |
- |
MOH-devices |
6 |
6 |
6 |
- |
- |
Trunk groups |
16 |
16 |
8 |
- |
- |
Number of trunk group keys per optiset E telephone |
6 |
6 |
6 |
- |
- |
Max. number of entrance telephones |
4 |
4 |
4 |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
Call detail recording central (CDRC) |
Only one CDRC exists for all tenants. |
Internal calls |
Internal calls are possible between stations in different systems if allowed by the traffic restriction groups. |
Prime Line |
Prime Line can be configured only for the entire system. |
CDB printout |
The database can only be printed for the entire system. |
Internal directory |
The internal directory displays the names of all stations and speed-dialing numbers in the system. |
Switch |
It is not possible to transfer undialed trunks. |
Simplified dialing |
Simplified dialing is not possible. |
Speed transfer |
Speed transfer is not possible. |
Intercept |
Intercept can be configured only for the entire system. |
Tenant |
Users can configure a maximum of three different tenants. |
System configuration |
The system configuration can be changed from only one telephone (programming telephone). |
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Action |
1. |
Assign trunks to stations via an ITR group 18-3-1-1 => Traffic restriction - ITR groups - Group assignment - Stations |
2. |
18-3-1-1 => Traffic restriction - ITR groups - Group assignment - Stations |
3. |
18-3-1-2 => Traffic restriction - ITR groups - Group assignment - Trunks |
4. |
18-3-2-1 => Traffic restriction - ITR groups - Connection matrix - Matrix |
5. |
Configure toll restrictions per tenant 15-1 => Toll restriction - Restriction, day |
6. |
15-2 => Toll restriction - Restriction, night |
7. |
Delete intercept position 16-12 => Incoming calls - Intercept, day |
8. |
16-13 => Incoming calls - Intercept, night |
9. |
Enter call allocations 16-16 => Incoming calls - Call alloc. day |
10. |
16-17 => Incoming calls - Call alloc. night |
11. |
Enter trunk groups 17-12 => Networking - Assign trk group |
12. |
17-13 => Networking - Overflow trk grp |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
1. |
Options |
2. |
Classes of service, CON matrix |
3. |
Classes of service, Group assignment |
4. |
Classes of service, Station |
5. |
Classes of service, Day |
6. |
Classes of service, Night |
7. |
System parameters, Diversion/Attendant |
8. |
Incoming calls, Ringing assignment per line |
9. |
Lines/networking, Trunks |
10. |
Lines/networking, Routes |
|
For a detailed description of how to configure two tenants, refer to Section 8.50, Tenant Services (Not for U.S.), on page 8-179 or Section 8.51, Tenant Services (for U.S. Only), on page 8-185. |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
1. |
Customer A has trunks 1 and 2. |
2. |
Customer B has trunks 3 and 4. |
3. |
Both customers should be able to seize the trunk using "0." (9 in U.K. and U.S.) |
4. |
The trunks are assigned to stations via an ITR group. |
5. |
Customer A's stations are entered in ITR1 and customer A's trunks are entered in ITR2. |
6. |
Customer B's stations are entered in ITR3 and customer B's trunks are entered in ITR4. |
7. |
The ITR groups for customer A's stations and trunks receive mutual ITR. |
8. |
For its own stations, customer A receives mutual ITR for customer B's stations. |
9. |
For its own stations, customer A receives incoming ITR for customer B's trunks. |
10. |
The ITR groups for customer B's stations and trunks receive mutual ITR. |
11. |
For its own stations, customer B receives incoming ITR for customer A's trunks. |
12. |
Customer A's trunks must receive mutual ITR. |
13. |
Customer B's trunks must receive mutual ITR. |
14. |
Trunk 1 and trunk 2 are placed in trunk group 1. |
15. |
Trunk 3 and trunk 4 are placed in trunk group 2. |
16. |
Overflow from trunk group 1 to trunk group 2. |
17. |
Customer A receives incoming and outgoing class of service for trunk group 1 and incoming class of service for trunk group 2. |
18. |
Customer B receives incoming and outgoing class of service for trunk group 2 and incoming class of service for trunk group 1. |
19. |
The intercept is removed in system settings, and for each trunk the intercept position for "0" (9 in U.K. and U.S.) is entered in the call allocation for trunks. |