ATT DEFINITY Communications System Generic 3 Instructions Manual

							Names Re gistration
Issue  3   March 1996
3-917
Names Registration
Feature Availability
This feature is available with all Generic 3 releases.
Description
Automatically sends a guest’s name and room extension from the PMS to the 
switch at Check-In, and automatically removes this information at Check-Out. In 
a d dition, the guest’s call coverage path (for example, a coverage path that 
terminates at a voice mail adjunct or a hotel operator) will also be sent from the 
PMS to the Switch during Check-In, and set to the ‘‘Default Coverage Path for 
Client Rooms’’ at Check-Out.
The information provided by the Names Registration feature may be displayed 
on any attendant console or disp lay-equipped voice terminal located at various 
hotel personnel locations (for example, Room Service, Security, and so on).  This 
allows p ersonnel at these locations to provide personalized greetings to calling 
guests. For example, if John Smith called room service, the restaurant personnel 
with a display-equipped voice terminal, would see John’s name and room 
extension and could answer with a personalized greeting.
Since the updates are sent automatically from the PMS to the switch, the System 
Manager does not have to manually a dd guest names into the switch via  the 
Management Terminal.  Normally, in a hotel environment where the d aily turnover 
of g uests is large, manual administration of the updates using  a Management 
Terminal would be a full time administrative task, and would be duplicating the 
information already resident in the PMS. By linking the automatic updates to the 
check-in and check-out sequences, the hotel can provide personalized displays 
more efficiently. 
Check-In and Check-Out
During the check-in procedure, information about the guest is obtained and 
stored in the hotel’s PMS. At this time, the PMS  sends a check-in message to the 
switch.  When the check-in message is sent, the switch removes the outward  
restriction on  the telephone in the guest room,  changes the status of the room to 
occupied, clears any previous wake up calls and message waiting lamp 
indications, and deactivates Do Not Disturb. Guest Name Registration d uring 
checkin would add two more operations to those already being performed.  
These operations would be to update the PBX names internal table and  the call 
coverage path for the guest station. Names Re gistration enhances the above list 
of o perations  by automatically sending a guest’s name, extension (room) 
number,  and  preferred  call coverage path upon check-in.  Also, at check-out, 
Names Re gistration automatically changes the call coverage path to the 
administered ‘‘Default Coverage Path for Client Rooms.’’ 
						

							Feature Descriptions
3-918Issue  3   March 1996 
The Check-In and Check-Out functions are d isc ussed in the PMS description 
elsewhere in this document.
Guest Information Input/Change
Guest Information Input/Change, allows  g uest information (name or coverage 
path) to be entered or altered subsequent to the check-in message.  Hotel 
personnel can change this information at the PMS and it is automatically sent to 
the switch.
The Guest Information In put/Change function  is used in those situations when 
the guest’s name associated with an extension must be changed, input of a 
guest’s name must b e ma de after the checkin sequence has taken place, or a 
change in call coverage arrangement must be made.  For examp le, a hotel may 
check in airline personnel prior to their arrival at the hotel in order to g uarantee 
their reservation.  However, hotel personnel may be unaware of the guests’ 
names until their actual arrival.  The names of the airline p ersonnel could be 
updated using the  Guest Information Input/Change function upon actual arrival.
Names Registration Information Format
For both Names Registration and Guest Information Input/Change formats, the 
guest’s name may consist of as many as 15 characters.
The format use d by the PMS (last name first, plus first initial and title, and so on) 
will be sent to the switch and is displayed as it is stored within the switch.  All 
spaces and commas within the name disp lay must also b e encoded within the 15 
characters.  In a d dition to the 15 character guest name, an extension numb er 
(normally up to five digits, but may be up to six digits with prefixed extensions), 
which  corresponds to the guest’s room numb er, will a ppear on display-equipped 
voice terminals at hotel service desks.
The guest’s name may be in all u pper-case letters, all lower-case letters or a 
mixture of upper- and lower-case. If a hotel would like to be able to use the 
Inte grated Directory feature (described elsewhere in this document), the  guest’s 
name must be entered using one of the following methods: 
nLast Name, comma, First Name (for example, Jones,Fred)
nLast Name, comma, First Name, space, Title/Middle Initial/Name (for 
example, Jones,Fred Mr)
nLast Name Only (for example, Jones)
nFirst Name, space, Mi d dle Name, space, Last Name (Will appear as 
Jones,Fred A)
Only alphanumeric characters, c ommas and spaces may be used in the “Name” 
field when Integrated Directory is desired. When  the  feature is not in use, the 
guest name may be sent to the switch using the above methods and may use 
periods. However, the p eriods will not be displayed.  
						

							Names Re gistration
Issue  3   March 1996
3-919
Call Coverage
Both Names Re gistration and Guest Information Input/Change messages contain 
call coverage path numbers. These numb ers are not displayed but are used to 
configure the appropriate call coverage arrangements for guest phones.  Path 
arrangements for voice mail, text messages, any available coverage point, or no 
coverage at all is sent by the PMS for automatic call coverage reconfiguration. 
The Call Coverage paths are established at the switch and are then used by the 
PMS to alter the call coverage arrangement for a g uest. If a customized 
arrangement is desired, the PMS must send a coverage path number (one 
through 600), and manual administration of the specific path can be performed 
through the  Management Terminal.
Considerations
The guest information p rovid e d by the Names Registration feature allows hotel 
personnel to provide personalized greetings to calling guests. Since guest 
information updates are sent automatically from the PMS to the switch, the 
System Manager does not have to manually ad d guest names into the switch via  
the Management Terminal.  By linking the automatic updates to the check-in and 
check-out sequences, the hotel can provide personalized displays more 
efficiently. 
A maximum of 15 characters can be entered as a guest’s name on the PMS.
The call coverage path numbers sent by the PMS to the switch for automatic 
reconfiguration should be limited to those a dministered in the switch and stored 
in the PMS. 
The guest’s room extension number can have a maximum of five digits.
The PMS controls the format of the name displayed on display-equipped voice 
terminals.
Interactions
The following features interact with the Names Registration feature.
nCall Coverage
Establishing call coverage arrangements is not limited to the automatic 
update during checkin messages sent from the PMS. Hotel personnel 
require alternate coverage points other than those designated for guests.  
The switch can still be used to manually a dminister call coverage paths 
through the Management Terminal, while automatic updates can still b e 
sent from the PMS for guests’ extensions.  
						

							Feature Descriptions
3-920Issue  3   March 1996 
nCOS 
If an extension has Client Room COS, the save translation operation clears 
the station name and sets the coverage path to the Default Coverage Path 
for Client Room when stored on tape.  The existing information in memory 
is not affected.  However, if the translations are read in, existing 
extensions will be affected until a database swap synchronizes the switch 
and PMS.
nInterface
During a Room Change/Room Swap, the name originally associated with 
the first station numb er is changed/swapped to the second room station 
along with call coverage path,  automatic wake-up entries, messa ge 
waiting status and controlled restrictions.
Administration
PMS administration as described in the Property Management System (PMS) 
Interface description, elsewhere in this chapter, is required.  In addition to this, 
the items in the following paragraphs should be taken into consideration.
To maintain necessary guest security, hotels do not divulge guests’ room 
numbers to other guests or callers. For this reason, display-equipped voice 
terminals should not be assigned to guests’ rooms. A guest with this capability 
would be able to dial another extension  and view the g uest’s name at that 
extension.
Call Coverage paths must b e administered on the switch, and the associated 
path numbers must be used by the PMS to establish coverage arrangements. If 
only one coverage arrangement is used by a hotel, this number must be used. 
For suite rooms, prearranged paths can be administered on the switch and the 
numbers stored  within the PMS  that would allow one room in the suite to be the 
coverage point for the other. Special customized arrangements at time of check 
in (coverage from one g uest room to another) are performed by sending  the 
coverage path numb er from the PMS then manually administering  the attributes 
of the path at the switch.
Both the PMS and the switch are able to alter guests’ names stored in the switch 
The last change that is made (by either system) is the change that is used.
The communication protocol used between the switch and the PMS must be 
administered as ‘‘transparent.’’
The Default Coverage Path for Client Rooms must be a dministered. 
						

							Names Re gistration
Issue  3   March 1996
3-921
Hardware and Software Requirements
A PMS, if used, can be connected through an MPDM and port on a Digital Line 
circuit pack or through an ADU and a port on a Data Line circuit pack. A journal 
printer can be used and also requires an MPDM and a p ort on a Digital Line 
circuit pack or an ADU and a port on a Data Line circuit pack.
O ptional Hospitality Services software is required to provide the PMS Interface 
feature. 
						

							Feature Descriptions
3-922Issue  3   March 1996 
Network Access — Private
Feature Availability
This feature is available with all Generic 3 releases.
Description
Allows calls to be connected to the following types of networks:
nCommon Control Switching Arrangement (CCSA)
nDistributed Communications Systems (DCS)
nElectronic Tandem Network (ETN)
nEnhanced Distributed Communications Systems (EDCS)
nEnhanced Private Switched Communications Service (EPSCS )  
(G3i-Global, G3V2, and later releases)
nTandem Tie Trunk Network (TTTN)
nTGU/TGE/TGI
A p rivate network provides call routing over facilities dedicated to the customer. 
Considerations
With Private Network Ac cess,  calls can be made to other switching systems 
without having to use the public network.
Unless prohibite d b y the COR, all incoming Private Network trunks exc ept CCSA 
can access outgoing trunks without attendant or terminal user assistance.  All 
incoming CCSA calls must route to an attendant or a terminal user.
When off-network calling is specified as part of the CCSA and EPSCS service, 
long-distance calls route as far as possible over these networks b efore 
terminating on the p ublic network.  Thus, charg es for toll calls are reduced. The 
COR administered to individual system users d etermines whether access to this 
capability is allowed or denied.
In Italy, the Traslatore Giunzione Uscente/Entrante/Interno trunks are supported 
to provide Private Network Access between two systems and also provide some 
feature transparency for COR (Inward Restriction), DID (when reaching busy 
stations), and Intrusion features. 
						

							Network Access — Private
Issue  3   March 1996
3-923
Interactions
nAttendant Call Waiting
G3i-Global, G3V2, and later releases provide Call Waiting via Italian TGU/ 
TGE (main/satellite) trunks. Call Waiting is also provided in Italy and all 
other countries through DCS.
nAttendant Intrusion
G3i-Global, G3V2, and later releases provide Attendant Intrusion on 
Satellite PBX stations via TGU/TGE trunks.  Attendant Intrusion is also 
provided through DCS.
Administration
Private Network Access is administered by the System Manager. The following 
items require administration:
nTie trunk groups used with private networks.
nWhether or not access to CCSA and/or EPSCS off-network calling is 
provided. (This assignment is made on a per-COR basis.)
Hardware and Software Requirements
Requires one p ort on an analog or DS1 Tie Trunk circuit pack for each trunk 
assigned. No additional software is required. 
						

							Feature Descriptions
3-924Issue  3   March 1996 
Network Access — Public
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides voice terminal users and attendants with access to and from the p u blic 
network.
Outgoing access is provided to the following:
nCOs
nFX offices (distant COs)
nWATS offices (COs receiving toll-free calls)
Incoming access is provided from the following:
nLocal COs
nFX offices
n800 Service office (COs sending toll-free calls)
Considerations
The ARS feature can be used to select the most-preferred route, where possible, 
for outgoing calls to the public network. Alternatively, trunk access codes can be 
dialed for manual route selection. Long-distance carrier access codes can be 
dialed to select particular carriers.
Some central offices do not provide disconnect supervision and this information 
must be provided on the trunk group administration screen.
Interactions
None.
Administration
Public Network Ac c ess is administered by the System Manager.   All trunk 
groups used for Public Network Access must be administered. 
						

							Network Access — Public
Issue  3   March 1996
3-925
Hardware and Software Requirements
Requires one p ort on a TN747B CO Trunk circuit pack or TN767 DS1  circuit 
pack (TN464B/C/D support A-law) for each trunk assigned. No additional 
software is required. 
						

							Feature Descriptions
3-926Issue  3   March 1996 
Night Service — Hunt Group
Feature Availability
This feature is available with all Generic 3 releases.
Description
Hunt Group Night Service allows an attendant or a split supervisor to individually 
assign a hunt group or split to the night service mode. All calls terminating on the 
hunt group or sp lit  in the night service mode are redirected to the hunt group or 
split’s designated Night Service Extension (NSE).
Considerations
The Hunt Group Night Service feature gives added flexibility to attendants and 
designated voice terminal users who are responsible for activating or 
deactivating individual hunt groups/splits at various times.
The system can have both Hunt Group Night Service and Trunk Group Night 
Service features at the same time. An incoming trunk call is redirected to the 
trunk group’s designated NSE.  If this NSE happens to be a hunt group or split 
that happens to be in the Hunt Group Night Service mo de, the call is redirected 
to the hunt group or split’s designated NSE.
Calls in progress, such as talking, on hold, or waiting in q ueue, on the hunt group 
or split are not affected when  the hunt group or split is put in the Hunt Group 
Night Service mo de.
Once the hunt group is in the Hunt Group Night Service mode, all calls are 
prevented from entering into the hunt g roup or split queue.
All new calls terminating on the hunt group or split in the Hunt Group Night 
Service mode are redirected to its designated NSE.
When the hunt group queue becomes emp ty, all idle members are be put in a 
busy condition.
If Night Service is activated for a hunt group or split, and a power failure occurs, 
the hunt group or split automatically returns to the Night Service mo de.