Lucent Technologies Guestworks SErver 1079984G3 User Manual

GuestWorks™

server

Feature Descriptions

Issue 3.0

555-231-207 Comcode 107998403 Issue 1 April 1997

Notice

Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change.

Your Responsibility for Your System’s Security

Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party, for example, persons other than your

company’s employees, agents, subcontractors, or persons working on your company’s behalf. Note that there may be a risk of toll fraud associated with your telecommunications system and, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

You and your system manager are responsible for the security of your system, such as programming and configuring your equipment to prevent unauthorized use. The system manager is also responsible for reading all installation, instruction, and system administration docu ments pro vided wi th this pr oduct in order to fully understand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk. Lucent Technologies does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunication services or facilities accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use.

Lucent Technologies Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need technical support or assistance, call the Lucent Technologies National Customer Care Center support line at 1-800-643-2353. Outside the continental United States, contact your local Lucent Technologies authorized representative.

Federal Communications Commission Statement Part 15: Class A Statement. This equipment has been tested and

found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.

Part 68: Network Registration Number. This equipment is registered with the FCC in accordance with Part 68 of the FCC Rules. It is identified by FCC registration number AS593M-13283-MF-E, ringer equivalence 3.0A.

Canadian Department of Communications (DOC) Interference Information

This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of the Canadian Department of Communications.

Trademarks

DEFINITY, MERLIN, TERRANOVA and AUDIX are registered

trademarks of Lucent Technologies. GuestWorks and INTUITY are trademarks of Lucent Technologies. Teledex is a registered trademark of Teledex Corporation.

Ordering Information Write or Call:

Lucent Technologies BCS Publications Center P.O. Box 4100, Crawfordsville, IN 47933 Voice 1-800-457-1235 Intl Voice +1-317-361-5353 Fax 1-800-457-1764 Intl Fax +1-317-361-5355

Order: Document No. 555-231-207

For more information about Lucent Technologies documents, refer to the section entitled “Related Documents” in “About This Document.”

GuestWorks server Support

To receive support on your GuestWorks server, call 1-800-242-2121. Outside the continental United States, contact your local Lucent Technologies authorized representative. To receive support for Teledex room telephones, call 1-813-824-6003.

European Union Declaration of Conformity

Lucent Technologies Business Communications Systems declares that GuestWorks equipment specified in this document conforms to the referenced European Union (EU) Directives listed below: Single-Carrier Cabinet (SCC), AC Powered with 25 Hz ring generator EMC Directive 89/336/EEC Low Voltage Directive 73/23/EEC

Comments

To comment on this document, return the comment form.

Lucent Technologies Web Page

The World Wide Web home page for Lucent Technologies is http://www.lucent.com

Acknowledgment

This document was prepared jointly by the Lucent Technologies Customer Training & Information Products Organization and the BCS Product Documentation Development group, Bell Laboratories, Denver, CO 80234-2703.

Comcode 1079 98403 Issue 1, April 1997

The “CE” mark affixed to the equipment means that it conforms to the above Directives.

Contents

About This Document 1

■ Introduction 1

■ Reasons for Reissue 3

■ Conventions 3

■ Related Documents 6

Feature Descriptions 7

■ General Info rmation 7

■ ASCII Data Over the Server-to-PMS

Link 10

■ Attendant Backup 11

■ Attendant Crisis Alert 16

■ Attendant Split Swap 21

■ Authorization Codes 22

■ Automati c Rou te Selection 24

■ Automatic Wakeup 26

■ Busy Verification 31

■ Call Accou nti n g 32

■ Call Coverage 34

■ Call Park 37

■ Check-In/Check-Out 38

■ Client Room Class of Service 40

■ Controlled Restrictions 41

Issue 1 April 1997 i

Contents

■ Dial by Name 45

■ Dire c t Acce ss Calling 52

■ Display Client on Redirection 56

■ Display Room Information on

Call Display 58

■ Do Not Disturb 59

■ Emergency Access to the Attendant 61

■ Maid Status/Housekeeping Status 63

■ Message Waiting Notification 65

■ Mixed Extension Numbering 68

■ Names Registration 71

■ Prefixed Extension Numbering 73

■ Property Management System (PMS)

Interface 77

■ Recorded Announcements 83

■ Room Change/Swap 87

■ Room Occupancy 88

■ Server/INTUITY/PMS Link Integration 89

■ Terminal Translation Initialization 94

■ Trunk Identification 96

■ Voice Messaging 97

ii Issue 1 April 1997

Contents

Hardware De s c riptions 101

■ GuestWorks server 102

■ TN2214 — Digital Line (24-Port) 103

■ TN2215 — Analog Line (16-Port) 104

■ TN791 — Guest Line (16-Port) 105

■ TN796B — Processor 106

■ Attendant Console 107

■ Voice Terminals 107

■ Recorded Announcement Equipm ent 109

■ Administration Terminal 109

■ Printers 110

■ Property Management System 111

■ Voice Messaging and Call Accounting System 112

Reports 113

■ Administration Reports 113

■ Printer Reports 118

Index 121

Issue 1 April 1997 iii

Contents

iv Issue 1 April 1997

About This Docu ment 0

Introduction 0

This document contains the following information about the GuestWorks™

server

■ A general description of hospitality services

■ Feature descriptions (including user operation, administration, and

required hardware) for the following features:

— ASCII Data Over the Server-to-Property Management System

(PMS) Link — Attendant Backup — Attendant Crisis Alert — Attendant Split Swap — Authorization Codes — Automatic Route Selection — Automatic Wakeup (with Dual Wakeup) — Busy Verification — Call Accounting — Call Coverage — Call Park — Check-In/Check-Out — Client Room Class of Service

Iss ue 1 April 19 97 1

Introduction

— Controlled Restrictions — Dial by Na me — Direct Ac ce ss Ca lling — Display Client on Redirection — Display Room Information on Call Display — Do Not Disturb — Emergency Access to the Attendant — Maid Status/Housekeeping Status — Message Waiting Notification — Mixed Extension Numbering — Names Registration — Prefixed Extension Numbering — Property Management System Interface — Recorded Announcements — Room Change/Swap — Room Occupancy — Server/INTUITY/PMS Link Integration — Terminal Translation Initialization — Trun k Id enti fication — Voice Messaging

■ Hardware Descriptions

■ Reports

2 Issue 1 April 1997

About This Document

Reasons for Reissue 0

This document replaces the

GuestWorks™ server Feature Description

(555-231-204, Issue 2) that was used on Issue 2.0 and earlier systems. This document is reissued for the following reasons:

■ To update all information related to Issue 3.0 of the GuestWorks

■ The user operation for some features has been moved to

DEFINITY®

Business Communications System and GuestWorks server Issue 3.0 Console Quick Reference Issue 3.0 Hospitality Operations

■ New features have been added, such as Attendant Split Swap, Dual

, (555-231-735), and

, (555-231-741).

GuestWorks server

Wakeup, Dial by Name, and Wakeup Activation via Tones.

■ To change the command path structure to match existing DEFINITY

products.

Conventions 0

The following conventions are used in this document:

■ The terms “attendant console” and “backup voice terminal” are used in

this document. The attendant console is the Model 302B, 302C, or PC console that is usually found at the front desk. T he backup voice t erminal can be either a Model 8410 or Model 8434 voice terminal with attendant-type feature buttons. Other multiappearance voice terminals can be used, but the preferred models are the 8410 and 8434.

server

Iss ue 1 April 19 97 3

Conventions

■ Buttons you press on the console or backup voice terminal are shown as

follows:

Release

The buttons shown in this document use label designations provided by Lucent Technologies. Since the button labels can be customized for each site, some button labeling may have different designations.

Some button labels, such as , span two lines. Because of line

Serial

Call

spacing in this document, they are shown across one line of text, such as

Serial Call

■ Administration command paths and options you enter in the administra-

tion fields are shown as follows:

change system-parameters hospitality

■ Field names shown on the administration screens are shown as follows:

Extension of PMS

■ The term “dial keypad” refers to the touch-tone keypad where you dial

(enter) telephone numbers and feature access codes.

■ When a procedure refers to a “room number,” the procedure is referring

to the extension number of the room. Extension numbers and room numbers do not always match.

■ Times entered for features, such as Automatic Wakeup and Do Not Dis-

turb, must consist of the hour followed by minutes in a multiple of 5 minutes; minute entries that do not meet this requirement will be rounded off by the server to the nearest multiple of 5. For example, to enter

7:00 a.m., dial . To enter 11:30 a.m., dial . To enter 10:15 p.m., dial .

0 0 1 1 3 0

2 2 1 5

Times entered in the range from 13:00 to 00:59 represent 1:00 p.m. to 12:59 a.m. Times entered in the range from 01:00 and 12:59 could represent either a.m. or p.m., so the server prompts you to designate the correct time.

In all of the procedures where you enter the time of day, 12:00 a.m. is midnight and 12:00 p.m. is noon.

4 Issue 1 April 1997

About This Document

■ You will hear the following tones during normal operation:

— Dial tone — a steady tone you hear when you select an idle call

appearance. — Ringback tone — the normal ringing tone you hear after you dial a

guest room or outside number. — Busy tone — a slow on-off-on-off tone you hear when the person

you are calling is busy on the telephone. — Reorder tone — a fast on-off-on-off tone you hear when calling

facilities are not available or are out of order. — Confirmation tone — a three-burst tone you hear after success-

fully using a feature access code. — Intercept tone — a high-to-low tone you hear when a call or fea-

ture access code is not accepted.

■ The following table lists the features described in this document. Ask your

administrator for these codes and write them down in this table.

Feature Feature Access Code

Announcement Terminal Translation Initialization

Activation Deactivation

Security Code Trunk Answer Any Station Verify Wakeup Announcement

Iss ue 1 April 19 97 5

Featu re Descr iption s 0

General Information 0

The GuestWorks

server

supports an impressive number of hospitality features.

For a complete list of the non-hospitality features available on the GuestWorks

server

, see the

Issue 3.0 Overview,

DEFINITY Feature Description

see

■ ASCII data over the server-to-PMS to provide flexibility and compatibility

DEFINITY Business Communications and GuestWorks server

(555-230-027). For a detailed description of the features,

, (555-230-204).

with a larger base of PMS vendors

■ Attendant Backup for answering overflow calls to the attendant console

■ Attendant Crisis Alert to notify hotel personnel when someone has called

the local emergency service agency, such as dialing 911

■ Automatic Route Selection (ARS) and World Class Routing (WCR) that

assures you that your guests’ calls are being routed over the lowest cost facility providing a larger margin on telephone service to the hotel

■ Guest-activated or attendant-activated Autom atic Wake up service; this

feature provides time-of-day wakeup announceme nts using a speech synthesizer circuit pack, customized messages using an integrated announcement circuit pack, and dual wakeup calls

■ Guest-activated Automatic Wakeup when no speech synthe sizer circuit

pack is installed; guests use call progress tones to enable one or two wakeup calls

■ Busy verif ic a ti on of trunk facilities to e ns ur e th a t all out sid e lines are

available for your guests and staff

Iss ue 1 April 19 97 7

General Information

■ Connectivity to a Lucent Technologies INTUITY Lodging Call Accounting

system or to your call accounting system

■ Automated display at the attendant console of room status; this provides

a more efficient check-in procedure, whether the PMS is active or not

■ Call restrictions based on individual room numbers or groups of rooms

■ Direct Access Calling to give incoming callers direct access to guest

rooms by entering either the guest’s name or the room extension number, access to the front desk, or access to other services and information

■ Guest- or attendant-activated Do Not Disturb service

■ Emergency Access to the Attendant from a guest room by going off hook;

after a short interval an alarm will ring at the attendant console and display the room number

■ Maid status for each room displayed on the attendant console

■ Message Waiting lamps, either LED or neon, on guest room telephones

■ Names Registration from the PMS (if available)

■ Server/INTUITY/PMS link integration to provide standard message deliv-

ery between the Lucent INTUITY and the PMS by sending the message through the server

■ Meeting room telephone service (without concern about telephone fraud

when the rooms are vacant) by using the Terminal Translation Initialization (TTI) feature

■ Trunk identification to troubleshoot bad connections

■ Secure Lucent INTUITY Lodging voice messag ing system where guests

can retrieve messages up to 24 hours after checkout

■ Connectivity to compatible PMS products

■ Lower-cost local and long distance by using bulk digital facilities in place

of individual trunk lines

■ Answer detection to provide more accurate long distance call records

8 Issue 1 April 1997

Feature Descriptions

■ Multiappearance display telephones for attendant backup where cus -

tomer service is essential

■ Support for Integrated Services Digital Network (ISDN) access using Pri-

mary Rate Interface (PRI) and Basic Rate Interface (BRI) voice terminals and adjuncts

■ Toll Fraud Security to help protect against illegal use of telecommunica-

tions resources

■ PC-based TERRANOVA® ECS Administration software to gain access to

the server admini s tration.

Iss ue 1 April 19 97 9

ASCII Data Over the Server-to-PMS Link

ASCII Data Over the Server-to-PMS Link 0

The server communicates with the PMS using a message set that contains guest status information such as the room number and the Call Coverage path. There are two ways that the guest data can be encoded:

■ Using a combination of Binary Coded Decimal (BCD) encoding and the

ASCII character set

■ Using only the ASCII character set.

Through administration, the server can now use this new ASCII message set exclusively instead of the mixed BCD/ASCII message set.

server

This ASCII message set makes the GuestWorks server still works with existing PMS vendors who use a combination of BCD and ASCII, but now also works with newly-developed PMS products that support ASCII guest data.

For more information about the message set and guest data specifications, see

DEFINITY Enterprise Communications Server (ECS), GuestWorks server, and System 75 PBX Property Management Syst em Interface Spe cifications,

(555-231-601).

more flexible. The

User Operation 0

There is no special user operation required for this feature.

Administration 0

change system-parameters hospitality

■ On Page 1 of this form, enter transparent in the PMS Protocol Mode

field and y in the ASCII mode? field.

10 Issue 1 April 1997

Feature Descriptions

Requir ed Ha r dw are 0

There is no special hardware required for this feature.

Requir ed So ft w are 0

To take advantage of this new feature, the PMS software must be compatible with the ASCII-only guest data message set. Contact your PMS vendor and request upgraded software that complies with the ASCII-only guest data message set as documented in

(ECS), GuestWorks server, and System 75 PBX Property Management System Interface Specifications,

DEFINITY Enterprise Communications Server

(555-231-601).

Attendant Backup 0

The Attendant Backup feature allows you to access most attendant console features from one or more specially-administered multiappearance voice terminals. Using this backup mode, you can answer calls faster, thus providing better service to your guests and prospective clients.

The recommended voice terminals are the Lucent Technologi es Model 8434 and Model 8410. When calls terminate at the attendant console during normal operation, users at the backup voice terminals can answer overflow calls by pressing a button or dialing a feature access code. You can then process the calls as if you are at the attendant console. Procedures for basic feature operation are documented in the quick reference guides for each voice terminal.

NOTE:

The Attendant Backup features cannot be used from guest rooms adm in-

istered as “client” rooms even if they have a multiappearance voice terminal.

Issue 1 April 1997 11

Attendant Backup

Queue Time

When the attendant console is in the day mode (the lamp is off), you

Night

cannot answer overflow calls at the backup voice terminals until the number of calls waiting in the attendant queue has reached an administered threshold. Until the threshold is reached, the only indication the backup voice terminals receive about calls waiting in queue is when the and the

lamps go on. You can press the button to see how long

the call has been waiting, but you cannot answer the call. The lamp

Queue Calls

Queue Time

starts flashing when the time in queue warning level has been reached (this is usually set for 15 seconds). When the calls waiting in queue threshold has been reached, the backup voice terminals will beep every 10 seconds as long as the number of calls waiting stays above the threshold. You can then answer calls using the Trunk Answer Any Station (TAAS) feature access code _____ or an automatic dialing button administered with that feature access code.

When the attendant console is in the night mode (the lamp is on), all calls

Night

to the attendant console immediately beep at the backup voice terminals and

Queue Calls

the and the lamps go on. You can then answer calls using the TAAS feature access code _____ or an automatic dialing button administered with that feature access code.

You can also install an external ringing device that sounds whenever the attendant queue limit is reached and when calls can be answered with the TAAS feature access code. This is an optional feature.

User Operation 0

12 Issue 1 April 1997

The Attendant Backup feature has no specific user operation procedures. The user operation for basic console features using the attendant console or a backup voice terminal is documented in

System and

GuestWorks server Issue 3.0 Console Quick Reference,

DEFINITY Business Communications

(555-231-735). The user operation for hospitality features is documented in

GuestWorks server Issue 3.0 Hospitality Operations,

(555-231-741). For basic

voice terminal operation, see the quick reference guide for the voice terminal.

Feature Descriptions

Administration 0

change stat ion XXXX (XXXX is the extension number of the voice terminal)

■ Add the following required feature buttons to the backup voice terminal:

— atd-qcalls (this button causes backup voice terminals to ring

when the queue warning level is reached)

— atd-qtime

Other buttons related to hospitality features should be added to the backup voice terminal. Those include the following:

— ext-dn-dist — auto-wkup

— night-serv (only one backup voice terminal can have this button)

— ringer-off —check-in —check-out

—busy-ind (assign a busy indicator button for the attendant console

extension and for the extensions of other backup voice terminals)

change attendant X (X is the console number; usually 1)

■ Use this form to administer the attendant console parameters. On Page 1

of this form, the console Type field must be set to principal.

change feature-access-codes

■ Use this form to add the Trunk Access Any Station feature access code.

This feature is used to answer attendant calls that overflow the attendant call waiting queue.

Issue 1 April 1997 13

Attendant Backup

change console-parameters

On Page 1 of this form, administer the following Attendant Backup parameters:

■ The Calls in Queue Warning level should be set to 1 if the

customer uses the backup voice terminals for most call handling. If the customer uses the attendant console, you can set this level to a higher threshold.

■ The Ext Alert Port (TAAS) field must have an analog circuit

equipment location administered even if you do not have external ringing equipment connected to the circuit. This is required to allow the Attendant Backup feature to work properly.

■ The No Answer Timeout controls when ringing at the console

will stop after a call is waiting in queue. When the timeout occurs, the consol e sto ps ri ngin g, but the call can still be answe re d. A good value to begin with is 10.

■ The Alerting field controls the timeout limit before the console

automatically goes into Night mode and Position Busy when calls are not answered. This is a good feature to administer in the situation where the attendant takes a break or leaves at the end of the day, and forgets to put the console into Night service. For example, if the No Answer Timeout field is set to 10 seconds and the Alerting field is set to 10 seconds, the following occurs: a call rings at the console, after 10 seconds the console ringing shuts off, the call continues to queue for 10 seconds, then the console goes into Night mode and Position Busy. The call can now be answered from a backup voice terminal.

14 Issue 1 April 1997

Feature Descriptions

change cos

■ For the COS used by the backup voice terminals, enter y for Console

Permissions.

SECURITY ALERT:

Do not assign Console Permissions to any Class of Service except for the attendant consoles and backup voice terminals.

change system guestworks-bcs-options

■ Enter y in the Day Mode TAAS Pickup & Backup Station Audi-

ble Alerting field. This option defaults to y, and can be changed only

by Lucent Technologies personnel.

Requir ed Ha r dw are 0

The Attendant Backup feature can be used from any supported multiappearance voice terminal. The recommended models for GuestWork s are the Model 8434 and Model 8410.

If you are using the TAAS external alerting port, you must use an approved ringing device.

Issue 1 April 1997 15

Attendant Crisis Alert

Attendant Crisis Alert 0

The Attendant Crisis Alert feature provides a visual, audible, and printed record when guests or hotel staff place a call to the local emergency service agency. This gives hotel personnel the ability to assist emergency personnel when they arrive at the hotel by identifying where the call came from and when the call was made. This feature uses the Automatic Route Selection (ARS) feature to allow routing of any emergency service access code (such as 911) to the appropriate emergency service agency, while also identifying the call for crisis alerting.

For example, the hotel publishes that in emergencies, guests should dial 911 to reach the local emergency service agency. When the call is placed and successfully routed to the local emergency service agency, the attendant console is notified immediately by a special emergency alerting tone and a special emergency display (the emergency call itself cannot be answered at the attendant console, but the call information is displayed). The attendant can then note the room number and contact the appropriate personnel at the hotel to assist with the emergency.

NOTE:

Each subsequent emergency notification is queued with a 5-second delay to allow the attendant to finish processing the current emergency notification.

The Attendant Crisis Alert feature can be used for any type of emergency such as a medical emergency from a guest room, a fire in the kitchen, or a burglary.

User Operation 0

The user operation for Attendant Crisis Alert is documented in

ness Communications System and Reference,

(555-231-735).

GuestWorks server Issue 3.0 Console Quick

DEFINITY Busi-

16 Issue 1 April 1997

Feature Descriptions

Administration 0

change attendant 1

■ On Page 2 of this form, add the crss-alert feature button. Using a blank

button label, create a button label and install it on the attendant console. The button can be added only to the attendant console, not any of the attendant backup voice terminals.

change ars analysis X (X is the first digit of the dialed digit string)

■ On this form, assign a routing pattern and the alrt Call Type to the

desired emergency service access code. For example, if your emergency service access code is 911, assign the 911 digit string to a routing pattern and assign it the alrt Call Type. This takes care of the condition when the guest dials 9 (for local access) and then 911. If a guest dials only 911, you also want the call to route to the emergency service agency. You must assign a dialed string of 11 with a different routing pattern that removes the dialed digits 11 and inserts the dialed digit string 911. The following screens show these two examples administered as part of the ARS Digit Analysis Table.

Crisis Alert

change ars analysis 9 Page 1 of 2

Dialed Total Rte Call Nd ANI Dialed Total Rte Call Nd ANI String Mn Mx Pat Type Num Rq String Mn Mx Pat Type Num Rq

911 3 3 5 alrt n n

ARS DIGIT ANALYSIS TABLE

Partitioned Group Number: 1 Percent Full: 6

nn nn nn nn nn nn nn nn

Issue 1 April 1997 17

Attendant Crisis Alert

change ars analysis 1 Page 1 of 2

Dialed Total Rte Call Nd ANI Dialed Total Rte Call Nd ANI String Mn Mx Pat Type Num Rq String Mn Mx Pat Type Num Rq

11 2 2 6 alrt n n

ARS DIGIT ANALYSIS TABLE

Partitioned Group Number: 2 Percent Full: 6

nn nn nn nn nn nn nn nn

18 Issue 1 April 1997

Feature Descriptions

change route-pattern X (X is the routing pattern)

■ On this form, assign a routing pattern for the emergency service access

code. In this first example, Preference 1 of Pattern 5 is used when guests

dial 9911 (9 for the ARS access code, and 911 for the emergency service agency).

change route-pattern 5 Page 1 of 1

Grp. FRL NPA Pfx Hop Toll No. Del Inserted IXC

No. Mrk Lmt List Digits Digits 1: 5 0 2: 3: 4: 5: 6:

BCC VALU E TSC CA-TSC ITC BCIE Service/Feature Numberi ng

0 1 2 3 4 W Reque st Format 1: y y y y y n n rest 2: y y y y y n n rest 3: y y y y y n n rest 4: y y y y y n n rest 5: y y y y y n n rest 6: y y y y y n n rest

Pattern Number: 5

Issue 1 April 1997 19

Attendant Crisis Alert

In this second example, Preference 1 of Pattern 6 is used when guests dial 911. Pattern 6 deletes the two digits dialed after the ARS access code (11), and inserts the correct digit string (911).

change route-pattern 6 Page 1 of 1

Grp. FRL NPA Pfx Hop Toll No. Del Inserted IXC No. Mrk Lmt List Digits Digits

1: 5 0 2 911 2: 3: 4: 5: 6:

BCC VALU E TSC CA-TSC ITC BCIE Service/Feature Numberi ng

0 1 2 3 4 W Reque st Format

1: y y y y y n n rest 2: y y y y y n n rest 3: y y y y y n n rest 4: y y y y y n n rest 5: y y y y y n n rest 6: y y y y y n n rest

Pattern Number: 6

change system-parameters hospitality

■ On Page 1 of this form, administer the data module extension for the jour-

nal/schedule printer in the Extension of Journal/Schedule Printer field.

Requir ed Ha r dw are 0

There is no special hardware required for this feature.

20 Issue 1 April 1997

Feature Descriptions

Attendant Split Swap 0

The Attendant Split Swap feature allows the attendant to alternate between active and split calls. This operation may be useful when the attendant may need to transfer a call, but first must talk with each party before completing the transfer. This operation is done using the new button.

User Operation 0

Split Swap

The user operation for Attendant Split Swap is documented in

ness Communications System and Reference,

(555-231-735).

GuestWorks server Issue 3.0 Console Quick

Administration 0

change attendant X (X is the console number; usually 1)

■ On Page 2 of this form, add the split-swap feature button.

Requir ed Ha r dw are 0

There is no special hardware required for this feature.

DEFINITY Busi-

Issue 1 April 1997 21

Authorization Codes

Authorization Codes 0

The Authorization Codes feature allows hotel staff to access additional ca lling features of the server when making toll calls or accessing the server remotely. Authorization codes may be used for any or all of the following reasons:

■ To allow a calling user to override the FRL assigned to the originating sta-

tion or trunk

■ To restrict individual incom ing tie trunks from accessing an outgoing

trunk

■ To identify certain calls on CDR records for cost-allocation purposes

■ To provide additional security control for the system.

When an authorization code is dialed, the FRL assigned to the extension number, attendant console, incoming trunk group, or remote access trunk group being used for the call is replaced by the FRL assigned to the authorization code. The new FRL functions the same as the one it replaces; however, the new FRL may represent greater or lesser calling privileges than the FRL that it replaces. Access to any given facility depends on the restrictions associated with the authorization code FRL.

For example, a supervisor may be at a desk of another user and want to make a call that is not normally allowed by the FRL assigned to that extension. The supervisor, however, can still make the call by dialing an authorization code that has been assigned an FRL that is not restricted from making that type call.

For security reasons, authorization codes range from four to seven digits. The number of digits in the codes must be a fixed length.

Each authorization code is assigned a COR that contains an associated FRL. Within a system, access privileges are determined by the FRL assigned to the facility where the call is originated. When an ARS call is dialed, the system allows or denies the call based on the FRL of the originating station. COR is used to restrict internal or non-ARS calls.

22 Issue 1 April 1997

Feature Descriptions

When an authorization code is required on some, but not all, trunk groups, the system prompts for an authorization code when the originating FRL is not adequate to access the next available trunk group in the routing pattern.

When a remote access caller dials the assigned remote access number and establishe s a connect ion to the system, the system may request the cal ler to dial an authorization code and/or a barrier code. The authorization code defines the caller’s call in g p riv ile ges within the sys t e m.

If entry of an authorization code is required, it applies to all remote access trunk groups in the system. If a remote access user must dial an authorization code to gain access to the system facilities, an authorization code is not requested again even if the user places a call that routes through ARS.

For security reasons, Authorization codes must be assigned randomly. This also makes it difficult for one user to guess the authorization code assigned to another user.

User Operation 0

When an authorization code is required, users are prompted to enter the authorization code after they dial the called number. Users receive a second dial tone and that is when they enter the authorization code.

Administration 0

change system-parameters feature

■ On Page 3 of this form, enable authorization codes for the server. You

also set the code length (four to seven digits), the attendant timeout flag, and other parameters.

Issue 1 April 1997 23

Automatic Route Selection

change authorization-codes

■ Use this form to add authorization codes to the server. You can add up

to 1,500 codes on the server. Administer only the authorization codes required. Do not add random authorization codes as this may cause a breach in system security.

Requir ed Ha r dw are 0

There is no special hardware required for this feature.

Automatic Route Selection 0

Automatic Route Selection (ARS) World Class Routing (WCR) is used to ensure that calls use the lowest-cost facility. ARS can also deny calls to specific numbers or groups of numbers (for example, 976-xxxx or 900 numbers). ARS rout-

ing patterns can be designed so that the calling party’s COR will dictate the type of facility for this c all, and what to d o if all of those faciliti e s are bu s y .

ARS partitioning is used to provide a method to segregate the guest usage from the administrative usage. Calls for each group can be routed over different facilities for an identical dial string. This is accomplished by Class of Restriction (COR). Guest rooms could be in COR 1, while the hotel staff could be in COR 2. The COR also defines the Facility Restriction Level (FRL), or calling privileges, for that class of user. There must be an ARS analysis table for each partition. The analysis table will provide unique routing of calls made by each group of callers. Long distance calls made by the administrative users may be routed over SDN trunks, while a guest who dialed the same dial string could be routed over a “Time and Charges” type of trunk (required in some states).

User Operation 0

There is no special user operation required for this feature.

24 Issue 1 April 1997

+ 100 hidden pages

Lucent Technologies Guestworks SErver 1079984G3 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About This Docu ment 0

Introduction 0

Reasons for Reissue 0

Conventions 0

Related Documents

Featu re Descr iption s 0

General Information 0

ASCII Data Over the Server-to-PMS Link

User Operation 0

Administration 0

Requir ed Ha r dw are 0

Requir ed So ft w are 0

Attendant Backup 0

User Operation 0

Administration 0

Requir ed Ha r dw are 0

Attendant Crisis Alert

User Operation 0

Administration 0

Requir ed Ha r dw are 0

Attendant Split Swap 0

User Operation 0

Administration 0

Requir ed Ha r dw are 0

Authorization Codes

User Operation 0

Administration 0

Automatic Route Selection

Requir ed Ha r dw are 0

User Operation 0