ATT DEFINITY Communications System Generic 3 Instructions Manual

							System Measurements
Issue  3   March 1996
3-1125
Administration
Measurements for the Coverage Paths, Coverage Principals, Route  Patterns, 
Trunk Group Hourly, and Wideband Trunk Group Hourly reports  are only 
collected for objects that have been administered using the 
change 
meas-selection
 commands.
Hardware and Software Requirements
System administration terminals are required to monitor system measurements. A 
system printer is required to generate paper copies of the reports. No a dditional 
software is required. 
						

							Feature Descriptions
3-1126Issue  3   March 1996 
System Status Report
Feature Availability
This feature is available with all Generic 3 releases.
Description
Allows the user to view data associated with attendants, major and minor alarms, 
and traffic measurements. The information  is displayed on the  Management 
Terminal, and presents a basic picture of the System condition. The report can 
only be displayed by the System Manager and maintenance personnel.
The Status Report is displayed by entering one of the commands listed below.  
Once the command is entered, the system continually displays the report until it 
is canceled.
NOTE:
Cancelling a monitor system view1 or monitor system view2 report 
results in automatically logging the user off the system.
nmonitor system view1 
This command displays the following information:
— Activation status of all attendants (updated every minute) 
— Maintenance status which includes major and minor alarms for 
trunk ports, terminal ports, and all maintained objects in the system 
except  terminals and trunks (updated every minute)
— Traffic measurements for trunk groups, hunt groups, and attendant 
groups (updated every hour)
nmonitor system view2 
This report is a subset of the view1 report and displays the same  
information listed for the view1 report except the last hour’s measurement 
for the hunt groups.
nmonitor traffic trunk-groups (update d every minute)
This command displays the following information:
— Trunk group numb er
— Number of members in each trunk group
— Number of members in each trunk group that are active on a call
— Length of group queue
— Number of calls waiting in the group queue 
						

							System Status Re port
Issue  3   March 1996
3-1127
nmonitor traffic hunt-group (V3 and  later releases only) (updated every 
minute)
This command displays the following information:
— Hunt group number
— Number of members in each hunt group
— Number of members in each hunt group that are active on a call
— Length of group queue
— Number of calls waiting in the group queue
— Length of time the oldest call in queue has been waiting to be 
serviced
When a CO call enters a full ACD split queue, CDR and the CMS may show 
different measurements.  CDR measurements indicate the maximum number of 
calls allowed in the queue, whereas the CMS measurements indicate all calls in 
the queue plus any call on the CO trunk waiting to enter the split queue.
Considerations
In a ddition to providing status reports, this feature also provides an indication 
that the administration terminal is functioning.  Any attempt to stop the ‘‘monitor 
system view1/view2’’ reports logs the administration terminal off the system.  
Therefore, no unauthorized administration can be performed.
Interactions
None.
Administration
None required.
Hardware and Software Requirements
No a d ditional hardware or software is required. 
						

							Feature Descriptions
3-1128Issue  3   March 1996 
Temporary Bridged Appearance
Feature Availability
This feature is available with all Generic 3 releases.
Description
Allows multiappearance voice terminal users in a Terminating Extension  Group 
(TEG) or Personal Central Office Line Group (PCOLG) to bridge onto an existing 
group call. If a call has been answered using the Call Pickup feature, the 
originally called party can bridge onto the call. Also allows a called party to 
bridge onto a call that redirects to coverage before the called party can answer 
it.
A call incoming to a TEG or PCOLG is not a call to an individual, although one 
particular member of the group may be the most qualified person to handle the 
given call.  If this individual did not answer the call originally, then he or she can 
simply bridge onto the call.  The call does not have to be transferred.
A call to an individual can be answered by a Call Pickup group member. If the 
called person returns while the call is still connected, he or she simply bridges 
onto the call and the answering party hangs up.
Call Coverage provides redirection of calls to alternate answering positions 
(covering users).  A Temp orary Brid ged Appearance is maintained at the called 
voice terminal.
The called party can answer the call at any time, even if already answered by a 
covering user.  If the c alled p arty does not bridge onto the call, the covering user 
can use the Consult function of Call Coverage to determine if the called party 
wants to accept the call.  The Consult function uses the Temp orary Bridged 
Appearance maintained on the call. When the consult call is finished, the 
Temporary Bridged Appearance is removed.
Stations that normally have a temporary b rid ged  appearance with their coverage 
point, do not have a temp orary bridged appearance if the coverage point is 
AU DIX .
Considerations
Temporary Bridged Appearance permits the desired party to bridge onto a call 
without manually transferring the call. This provides convenience of operation 
and also saves time. 
						

							Temporary Bridged Appearance
Issue  3   March 1996
3-1129
Temporary Bridged Appearance does not provide any call originating cap a bility 
or the capability to answer another party’s calls. These capabilities are provided 
by the Bridged Call Appearance feature.
If two parties are bridged together on an active call with a third party, and if the 
conference tone feature is enabled, the conference tone is heard.
The Brid ged Call Ap pearance feature enhances Temporary Bridged 
Appearance b y allowing more than one call to an extension to b e bridged and b y 
allowing calls to be originated from bridged appearances.
Interactions
Privacy — Manual Exclusion, when activated, prevents other users from b rid ging 
onto a call. A user who attemp ts to bridge onto a call with the Privacy — Manual 
Exclusion feature active is d rop p ed.
Calls redirected to Call Coverage maintain a Temporary Bridged Ap pearance on 
the called voice terminal if a call ap pearance is available to handle the call. The 
called party can bridge onto the call at any time. The system can be 
administered to allow a temp orary b rid ged a p pearance of the call to either 
remain at or be removed from the covering voice terminal after the principal 
bridges onto the call. If two parties are bridged together on an active call with a 
third party, and the bridging tone is administered to yes, all three p arties hears 
the bridging tone.
Consult calls use the Temporary Bridg e d Appearance maintained on the call.  At 
the conclusion of a c onsult call, the b rid ged appearance is no longer maintained.  
If the principal chooses not to talk with the calling party, the principal cannot 
bridge onto the call later.
If a call has, or has had, a Temporary Bridged Appearance, is conferenced or 
transferred, and redirects to coverage again, a Temporary Bridged Ap pearance 
is not maintained at the conferenced-to or transferred-to extension.
Administration
The only required administration is to administer whether or not a temporary 
bridged appearance is maintained by the covering user after the principal 
bridges onto the call. (‘‘Keep Held SBA at Coverage Point’’ field on the 
“ Feature-Relate d System Parameters  Screen”  form.)
Hardware and Software Requirements
No a d ditional hardware or software is required. 
						

							Feature Descriptions
3-1130Issue  3   March 1996 
Tenant Partitioning
Feature Availability 
Tenant Partitioning is available with G3V4 and later releases.
Description 
Provides telecommunications services to multiple independent groups of users 
through a single PBX.  Most commonly, Tenant Partitioning is used to provide 
telecommunications services from a single provider to multiple tenants of an 
office comp lex. It eliminates the need for each tenant to purchase services 
separately, while giving each tenant the a p pearance of a dedicated PBX. The 
feature can also b e used to provide group services, such as departmental 
attendants, on a single-customer PBX.
Services that can be provided to tenants include: telephone equipment; building 
wiring; public and private network access; and attendant services. In addition, a 
full range of PBX features can be provided to even the smallest tenant office, 
including  Call Coverage, Call Forwarding, Remote  Ac cess,  Night Service 
Routing, Listed Directory Numbers (LDNs), Trunk Answer Any Station (TAAS), 
Call Center features, distinctive music on hold and others. Tenants can also 
purchase PBX  adjunct  features  if they are available on the switch, such as voice 
mail, or CMS activity reporting.
Tenant Partitioning provides advantages to both the telecommunications service 
provider and to the individual tenants.
nShared  resources offer enhanced services at lower cost to the tenant, with 
increased profit for the service provider.
nThe tenant is provided with the a ppearance of a dedicated PBX without 
the expense.
nAttendant services can be provided to all tenants.
nInstallation, a dministration, and maintenance of the PBX can b e delegated 
to a trained, full-time staff.
nWith proper administration, tenant resources, including trunking facilities, 
and all other switch endpoints can be protected from access by other 
tenants.
Partitioning Tenants
The Tenant Partitioning feature is delivered with one universal tenant. This tenant 
partition, partition 1, is usually reserved for the service provider. By default it has 
access to all facilities and can be accessed by any other tenants. 
						

							Tenant Partitioning
Issue  3   March 1996
3-1131
It is the function of the service provider to create additional partitions based on 
tenant requirements. When deciding which tenant partitions to create, 
remember:
nEach switch endpoint can be assigned to one and only one tenant 
partition. An d, each switch endpoint must be assigned to a partition. For 
example, each voice terminal, attendant console, trunk, and virtual 
endpoint, such as an LDN or VDN, must be assigned to a tenant p artition.
nMost tenant p artitions are discrete, separate units. By default, all tenants 
except partition 1 are prevented from accessing stations or trunking 
facilities belonging to other tenants. 
nHowever, the system administrator can change this default to p ermit or 
forbid any individual tenant to access any other specified tenant. For 
example, tenant 6 could be given permission to call tenants 9 and 16 only.
Note that if a tenant has permission to call another tenant, it has  access to 
every endpoint belonging to that tenant. For example, if tenant 6 has 
permission to call tenant 9, tenant 6 can also use any trunking facilities 
present in tenant partition 9.
NOTE:
Even if two extensions are blocked from calling each other by Tenant 
Partitioning restrictions, either extension can still reach the other by 
dialing the extension’s Direct Inward Dialing (DID) number via the 
public network.
nIf any facilities are to be shared among tenants who do not want c omplete 
access to each other’s facilities, then the shared facilities must be 
grouped in a separate partition. For example, if two tenants are going to 
share a trunk but not have direct access to each other’s voice terminals, 
then that trunk will need to be placed in its own partition so that both 
tenants can be given access to it.
NOTE:
Tenant Partitioning restrictions do not override COR restrictions. COR 
restrictions are independent of tenant partitions.
It is also important to consider the following constraints and requirements of 
access control, attendant services, music sourc es on hold and route selection 
when establishing or assigning partitions.
Access Control
By default, tenant partitions are prevented from accessing or b eing accessed by 
other partitions. Explicit permission must be given for one tenant to access 
another. The exception is the universal tenant who has p ermission to call or be 
called by any tenant.
PBX features, such as call coverage, are limited by tenant-to-tenant access 
restrictions. For examp le, sup p ose tenant 1 included a voice terminal from tenant  
						

							Feature Descriptions
3-1132Issue  3   March 1996 
2 in its coverage path. If tenant 3 had p ermission to call tenant 1 but not tenant 2, 
a call from tenant 3 to tenant 1 would skip the tenant 2 coverage point.
It may also be desirable to set up tenants with special access privileges. For 
example, a restaurant in an office complex could be given permission to be 
called by any other tenant. Likewise, permission to call or b e called by other 
tenants would be helpful for building security or PBX administration or 
troubleshooting.
Another example would be to assign all central office trunks to one tenant 
partition that could then  be accessed by all other tenants.
Attendant Services
One of the advantages of Tenant Partitioning is being able to provide 
personalized attendant services to each tenant.
There is one Principal and one Night or Day/Night Attendant p er attendant group. 
Each tenant is assigned an attendant group for service. Each attendant group 
has a separate q ueue. Queue warning lamps remain dark when Tenant 
Partitioning is active. However, the information displayed when a queue status 
button is pressed reflects the status of the attendant group queue. The total 
number of calls queued for all tenants cannot exceed the system limit.
Attendant groups may serve more than one tenant. In this case, the attendant 
group is not able to extend a call from one tenant via facilities belonging to 
another tenant unless the former tenant is permitted to access the other’s 
facilities.
Each tenant may have a designated night service station. Calls to an attendant 
group in night service are directed to the night service station of the appropriate 
tenant (when a Night Attendant is not available). When an attendant group is put 
into night service all trunk groups and hunt groups that belong to tenants served 
by that attendant group are placed into night service and incoming calls are 
routed to the night service destination of the a ppropriate tenant. Each tenant can 
have its own Listed Directory number (LDN) night d estination, Trunk Answer on 
Any Station (TAAS) port, or Night Attendant.
An attendant can specify that access to a trunk group is under attendant control 
if the trunk  group is assigned to a tenant served by that attendant’s group. In this 
case, any valid user attemp t to access the trunk group is directed to the 
attendant group serving the tenant to which the trunk group is assigned.
Multiple Music on Hold
With Tenant Partitioning, each tenant can be assigned a unique source for music 
to be heard when a call is placed on hold. Customers hear music most 
appropriate to the business of the tenant, including type of music and special 
advertisements.  
						

							Tenant Partitioning
Issue  3   March 1996
3-1133
With the exception of calls placed to the attendant group, the caller hears the 
music source of the tenant partition that he or she called. The caller continues to 
hear this same music source for the duration of the call regardless of transfers, 
call forwarding, or call coverage.
One of the following music on hold types can be assigned to each tenant 
partition:
For information on a dministering Multiple Music on Hold see “Tenant Partitioning” 
in the 
DEFINITY Communications System Generic 3 Version 4 Im plementation, 
555-230-655, or 
DEFI NI TY Com munications System Generic 3 V2/V3 
Implementation
, 555-230-653.
NOTE:
If you use e quipment that rebroadcasts music or other copyrighted 
materials, you may b e required to obtain a copyright license from or pay 
fees to a third party such as the American Society  of  Composers,  Artists 
and Producers (ASCAP) or Broadcast Music Incorporated (BMI). You can 
purchase a Magic on Hold ® system, which does not require such a 
license, from AT&T.
Network Route Selection
Network route selection takes account of the tenant p artition number assigned to 
the caller and to each trunk group. This means that trunk groups belonging to 
different tenants  can be included in the same route p attern. Calls routing to that 
pattern will select the first trunk group in that pattern that is permitte d access by 
the calling tenant (subject to normal constraints).
Sample Tenant Partitioning
The following is a simple example of how Tenant Partitioning could work in an 
office comp lex.
Tenant partition 1, the universal tenant, is assigned to the service provider. All 
other tenants can call and be called by the service provider. Extensions 
assigned to this partition are used for a variety of purposes including PBX 
troubleshooting and administration, and building security.
Tenant partitions 2-15 are each assigned to individual businesses located in the 
complex. Default restrictions are left in place for these tenants. That is, tenants  none A caller placed on hold hears silence
tone A caller placed on hold hears a system-wide administered 
tone.
music A caller placed on hold hears the music associated with the 
administered port. The number of possible music sources 
equals the number of possible tenant partitions. Each p artition 
can have its own music source. 
						

							Feature Descriptions
3-1134Issue  3   March 1996 
are prevented from accessing voice terminals, trunking facilities or other switch 
endpoints belonging to other tenants.
Tenant partition 16 is assigned to the restaurant locate d in the building complex. 
All tenants are permitted to call this tenant. However, to prevent the restaurant 
from accessing trunks and other facilities b elonging to tenants, the restaurant is 
not given permission to call any other tenants.
Tenant p artition 17 is assigned to all Central Office (CO) trunk groups. All tenants 
are given permission to call this tenant.
Tenant partition 18 is assigned to a trunk group that tenants 3 and 7 want to 
share. Tenants 3 and 7 are given access to this partition, all other tenants are 
denied access. To  prevent  toll fraud, tenant 18 is not allowed to call itself.
The ARS route pattern can be the same for all tenants. In this examp le, the 
trunk(s) for tenant p artition 18 (the private trunk shared by tenants 3 and 7), is 
placed first in the route pattern. Tenant partition 17 is placed second in the 
pattern. Tenants 3 and 7 route first to p artition 18 and then as a second choice to 
partition 17. All other tenants are denied access to partition 18 and so are routed 
directly to partition 17.
All facilities that are not shared, including trunk groups, VDNs, voice terminals, 
attendant consoles and other endpoints, are assigned to the tenant partition they 
serve.
The following table summarizes the calling permissions for the different 
partitions. Yes  indicates that the partitions have permission to call and be called 
by each other, no indicates that partitions cannot call or b e called by each other.
Table 3-82. Sample Calling Permissions
Calling 
Tenant 
Partition 
NumberCalled Tenant Partition Number
1 2, 4-6, 8-15 3,7 16 17 18
1yes yes yes yes yes yes
2, 4-6, 8-15yes Each partition 
can call itself but 
not the othersno yes yes no
3,7yes no Each partition c an 
call itself but not 
the othersyes yes yes
16yes no no yes yes no
17yes yes yes yes yes no
18yes no yes no no no