Coral PI 16.03

Eliezer Katzenstein
Israel
Eliezer Katzenstein .
Program Interface
Database Reference Manual
(Version 16)
Document Edition 25
Creating a new world of IPportunities

The information contained in this document is proprietary and is subject to all relevant
copyright, patent and other laws protecting intellectual property, as well as any specific
agreement protecting TADIRAN TELECOM (TTL) L.P.'s (herein referred to as the
“Manufacturer”) rights in the aforesaid information. Neither this document nor the information
contained herein may be published, reproduced or disclosed to third parties, in whole or in part,
without the express, prior, written permission of the Manufacturer. In addition, any use of this
document or the information contained herein for any purposes other than those for which it
was disclosed is strictly forbidden.
The Manufacturer reserves the right, without prior notice or liability, to make changes in
equipment design or specifications.
Information supplied by the Manufacturer is believed to be accurate and reliable. However, no

responsibility is assumed by the Manufacturer for the use thereof nor for the rights of third
parties which may be effected in any way by the use thereof.
Any representation(s) in this document concerning performance of the Manufacturer's

product(s) are for informational purposes only and are not warranties of future performance,
either express or implied. The Manufacturer's standard limited warranty, stated in its sales
contract or order confirmation form, is the only warranty offered by the Manufacturer in
relation thereto.
This document may contain flaws, omissions or typesetting errors; no warranty is granted nor
liability assumed in relation thereto unless specifically undertaken in the Manufacturer's sales
contract or order confirmation. Information contained herein is periodically updated and
changes will be incorporated into subsequent editions. If you have encountered an error, please
notify the Manufacturer. All specifications are subject to change without prior notice.
© Copyright by TADIRAN TELECOM (TTL) L.P., 1993-2012.

All rights reserved worldwide.
Protected by U.S. Patents 6,594,255; 6,598,098; 6,608,895; 6,615,404
All trademarks contained herein are the property of their respective holders.
Foreword
Welcome to the Coral system Program Interface and Database
Reference Manual. Flexibility is one of the great strengths of the Coral
Systems. This manual is a highly detailed explanation of the core of
the Coral™ FlexiCom 400 (with HDC controller), 5000, 6000;
Coral™ IPx Office; Coral™ IPx 500, 800, 3000, 4000; CDRS 200E,
the Program Interface (PI). By means of the PI, virtually all present
and future communication needs can be customized for each site or
location. The Program Interface is an integral part of the Coral product
and is designed to allow you to serve your client creatively.
Record of Changes
Issue No. Issue Date Brief Description Entered by:
25 Mar 2012 Includes Software Version 16.03.00 Tadiran

The following features, hardware and products Telecom
were added: (TTL) L.P.
• Silent Monitoring enabled for SIP Phones
(such as: P-Series, T300 Series, and Sea-
Beam softphone)
• Boss/ELA Line Keys on T300 SIP Phones
• Send proper ANI to Call Forward PSTN
Destination Enhancements (Route: SFE,0:
SEND_ORIGINAL_ANI_TO_CFWD_DEST and
SEND_INTERNAL_ORIGINAL_ANI_TO_CFWD_DEST
Parameters)
• IP Telephony Gateway Enhancements
(Route: IP,2: ACTIVATE_RSIP parameter)
See New Developments Summary
(Version 16 Edition 4) for complete list of
features and changes.
24 Oct 2011 Includes Software Version 16.01.16 Tadiran
were added: (TTL) L.P.
• SIP Trunk Enhancements
• SIP Terminals Enhancements
• SeaMail on PC
• LxCMC on PC
• Private/Public Library Enhancement (E7)
• Numbering Plan (removed #1986)
• P-Series (such as: P-335, P-450) SIP Phones
• Resources Cards do not include a MODEM
(8DRCM-2, U-MR Office, IPx 500M with
MSBipx Hardware Issue-0230X1003 or
higher)
23 Feb 2011 Includes Software Version 16.01.12 Tadiran
Telecom
LTD.
Record of Changes
22 Nov 2010 Includes Software Version 16.01.09 Tadiran

were added: LTD.
• BLF Conversion to SIP Phones (Allow stan-
dard BLF for all SIP terminals)
• Feature Control - Enhancement (The follow-
ing features were added: load ID, Login/
Logout, Released Resumed All, Wrap Up
Time, Primary Login ,Message)
• ELA Group Enhancements (Personal and
Department ELA group with FlexAir hand-
sets)
• SMDR Enhancements to reports including
the filtered digits that were dialed on the out-
going trunk
• ISDN Card (PRI/BRI) Signalig Enhance-
ments (One parameter was added for Name
sending on outgoing PRI calls to Telco)
• T1,PRI,TBR,30T/x,2DT Synchronization
• T300 Series (SIP) Phones Enhancements
• VOIP Enhancements
21 May 2010 Includes Software Version 16.00.07 Tadiran
were added: LTD.
• SIP Trunk Enhancements
• Partial ANI Available for Small Displays
• T.38 (FoIP) Fax over IP via PUGW
• iAPA
• Callback (IRSS/Freedom Enhancements)
• PI Terminal Enhancements
• New Authorization Parameters
• T300 Series ( T322, T328) SIP Phones
• 2DT Card Enhancement
Record of Changes
20 January 2010 Includes Software Version 15.85.37 Tadiran

See New Developments Summary Telecom
(Version 15.8 Edition 6) for complete list of LTD.
(Version 15.8 Edition 5) for complete list of LTD.
18 September 2008 Includes Software Version 15.85.04 Tadiran
Telecom
The following hardware and products were LTD.
added:
• Station Analog peripheral cards:
8/24SA, 8/16/24SAipx, 4/8/16/24SA Office
• Digital Trunk cards (one interface only):
2DT, 2DTipx, 2DT Office
(Due to logistical requirements, the cards are
labelled: "PRI-2DT", “PRI-2DTipx" or "PRI-
2DT Office”, on the front panel)
• 8SMipx (Magneto for CDRS 200E)
• 8DTMF (replaces the 4/8DTR)
• Coral SeaBeam softphone
• Coral IPx SeaMial
• SIP trunk enhancements

(Version 15.8 Edition 4) for complete list of
Record of Changes

Telecom
The following features were added: LTD.
• Enhanced ACD/UCD HUNT Group
• Transferring O/G PRI Calls while Ringing
• Disabling Re-route for Net-IP Calls
• Zone Page by Group Call (IPx Office)
• Keeping RTP after 3WAY Calls
• Multi-UGW Hub
• Touch-Tone Dialing (DTMF) from:
FlexSet 121S/281S, FlexSet-IP 280S,
T207M, T208M, T207M/NP, T208M/BL
• Continuous Conference Enhancements
The following hardware was added:

• MCP-ATS (SBS-CT9) Cards
• CoraLINK (CLA) on MAP
See New Developments Summary (Version

15.5 Fourth Edition) for complete list of
changes.
Record of Changes
16 March 2007 Includes Software Version 15.5 Tadiran

Telecom
The following features were added: LTD.
• Soft Keys Supported by System
• Call Log Supported by System
• FlexiCall and Freedom (IRSS) HELP
• Enhanced SMS Messaging
• Extension Line Appearance (ELA)
• TBCT — US Market
• Touch-Tone Dialing (DTMF) from IP Phones
• IP Faxing
• SIP Re-invite
• SIP CLA Support
• IP Port Type
• Restrict Internal CID

• T207M, T208M, T207M/NP, T208M/BL,
T207S, T208S, T207S/NP, T208S/BL, TEM
(IP Telephone)
• FlexSet 121S and 281S
• Sentinel Pro10/25/75/150(v6)
• Management Application Platform (MAP)
• Coral Navigator
• PEX-FS and PEX/APA-FS
See New Developments Summary (Version 15.5

First Edition) for complete list of changes.
15 December 2005 Coral Version 15 Tadiran
See New Developments Summary (Version 15) Telecom
for complete list of changes. LTD.
14 June 2005 Coral Version 14.67 Tadiran
(Version 14.67) for complete list of changes. LTD.
13 April 2004 Coral Version 14.66 Tadiran
(Version 14.66) for complete list of changes. Business
• Italian Defaults added Systems,
• PS Ringer Shelf Defaults for IPx systems added LTD.
• various new parameters added
Record of Changes
12 January 2004 Includes Software Version 14.65 with the Tadiran

following new features: Telecom
• Voice Over IP (Phases II) Business
• Turret Console support Systems,
LTD.
• ALI on Trunk Groups
• APA Authorization
• Enhanced (short) calling message
• Priority Preemption
• Internal SMDR
• Voice Page FlexSet-IP Numbers
• 4TWL-Rotary
• Coral System Directory
• FlexiCall (Phases II)
• Individual Remote System Services (IRSS)
• Overlap Dialing over PRI
• Extended CID
• Extended iCMC Voicemail Support
(Version 14.65) for complete list of changes.

• MCP-IPx card
• Coral IPx 500,800,3000,4000
Record of Changes
11 November 2002 Includes Software Version 14.1 Tadiran

The following features were added: Telecom
• Voice Over IP Business
• Hot Standby system Systems,
• Caller ID on SLTs -receiving over analog LTD.
trunks (no extraneous hardware needed)
• Look Ahead Routing (LAR)
• Call Duration Limit
• Call Forwarding Internal/External
• UGW card
• MG module
• IP Keysets (FlexSet-IP 280S)
• 8DRCF modem (56 Kbps)
• Coral FlexiCom 6000 Control Cards: MCP-
ATS, FMSD, CFD, 16/32GC
• iCMC-200
• 4/8T-CID
• iDSP
• MEX-IP
• MCP-IPsl
• IPG
The DX Version was cancelled.

10 May 2002 Includes Software Version 11.10 with the Tadiran
following new features: Telecom
• Auto Set Relocate Business
• FlexiCall (Phase 1) Systems,
• VIP Ring LTD.
• Second Party Speaker Status
9 December 2001 Includes Software Version 11.08 Tadiran
• Coral FlexiCom Telecom
• FlexSet Business
• SFT cards Systems,
See New Developments Summary LTD.
Record of Changes
8 September 2000 Includes Software Version 10.38. ECI

• E911 - CAMA support (USA) Telecom
• R2MFC supported on 30TM card. LTD.
• VFAC on Dial Service
• Retain Music Sources throughout Network.
• IVR-ACD
• Voicemail on Keyset
• New Network Rerouting options
• 4IAA discontinued {V10.21}
• HDC - High Density Controller For Coral II-
HT {V10.21}
• RSIS-HD - For Coral II-HD/R and Coral III-
HD/R {V10.21}
(Version 10.21 and 10.38) for complete list of
changes.
7 November 1999 Includes Software Version 10.19. ECI
Telecom
• No Data Connectivity to VDK,VDM and
TIM
• Collect Call Reject Tone, Whisper Page, Sec-
ond Ringback Tone (i.e. Call Waiting or Call
Offer), Caller ID on Analog Trunks, 4TWL
card
• GKT and Fonetasy
• PI Baud Rate Max: 38400 bps
• FLASH: MEX
• SVC24 replaces SVC
• Call Independent Signalling Connection
Support

(Version 10.19) CN 7244-7121901 for complete
list of changes.
6 July 1997 Coral SL, 8DRCM, Malicious Call Trace, NPL Tadiran
Default change (add # to default dial numbers
beginning with 1).
Includes Software Version 9.87
Record of Changes
5 November 1997 Feature Updates with Wireless Station, SLS, Tadiran

SKW and SDT cards, Coral ISDNet replaces
Coral QNET.
Includes Software Version 9.5x
4 February 1996 Includes Software Version 9.35 Tadiran
3 June 1995 Software Version 9.2x, Preliminary Draft 1 Tadiran
Feature updates with CoraLINK, CoralQNET,
4VSN card, 8VSN card, APA, VDM, and
Backup for large systems. Includes Version 9.2x
2 January 1995 Feature updates with TBR, 4TEMP, includes Tadiran
V8.60 and new comprehensive index
1 January 1994 Software Version 8.3x, Preliminary Draft 2 Tadiran
0 September 1993 Software Version 8.3x, Preliminary Draft 1 Tadiran
PI Reference Manual
Table of Contents
TOC-1
PI Reference Manual
1 Introduction
General Description .............................................................................................. 1-2
PI Terminal Device................................................................................................. 1-4
Hardware Setup ..................................................................................................... 1-5
Access to the Programming Interface .................................................................. 1-11
PI Terminal Control Function Commands ............................................................ 1-14
Conventions Used in this Document .................................................................... 1-17
Country Codes ..................................................................................................... 1-19
2 Programming Requirements
Default System....................................................................................................... 2-2
Typical Site-Specific Programming ........................................................................ 2-3
Additional Programming......................................................................................... 2-4
Programming and Entering Time Units .................................................................. 2-6
Programming Functions ......................................................................................... 2-7
Locating Data Fields .............................................................................................. 2-8
Direct Access Abbreviations (DAA)........................................................................ 2-9
Entering Yes/No and Remove.............................................................................. 2-10
Authorization Items .............................................................................................. 2-11
3 Installation
Installation .............................................................................................................3-2
Feature Authorization ............................................................................................3-5
TOC-2
PI Reference Manual
4 Sizes/URC/Music/Units Definition
Sizes Definition ......................................................................................................4-2
Sizes Tab ............................................................................................................4-24
URC-Card (IPx Office, IPx 500 and CDRS 200E) ...............................................4-33
URC-Default Configuration ..................................................................................4-35
URC-Current Configuration .................................................................................4-37
URC-Card Database ...........................................................................................4-40
System Engineering Options ...............................................................................4-41
Music Sources .....................................................................................................4-44
Units ....................................................................................................................4-47
5 Numbering Plan
General Numbering Plan .......................................................................................5-3
General Numbering Plan (Alphabetical Order) ......................................................5-7
General Numbering Plan (Field/Index Order) ......................................................5-17
Special Feature Codes ........................................................................................5-50
FlexiCall/IRSS (Freedom) Feature Codes ...........................................................5-53
SHOW TYPE of NUMBER ..................................................................................5-55
TOC-3
PI Reference Manual
6 System
Feature Timers ......................................................................................................6-2
System Features ...................................................................................................6-7
System Features - Outgoing Trunks .....................................................................6-8
System Features - Incoming Trunks ...................................................................6-19
System Features - Station Options .....................................................................6-20
System Features - Intercept/Incomplete .............................................................6-34
System Features - Call Forwarding .....................................................................6-39
System Features - Camp-On ..............................................................................6-41
System Features - Hotel ......................................................................................6-42
System Features - Messaging .............................................................................6-44
System Features - Tones ....................................................................................6-51
System Features - Diagnostics ...........................................................................6-53
System Features - ISDN .....................................................................................6-55
System Features - Network .................................................................................6-56
System Features - Wireless ................................................................................6-57
Card List ..............................................................................................................6-60
Port List ...............................................................................................................6-68
Port List - Physical Location ................................................................................6-69
Port List - Dial Numbers ......................................................................................6-74
Digital Port Bus List .............................................................................................6-92
Tone Plan ............................................................................................................6-96
Ringers ..............................................................................................................6-103
7 Class of Service
Station and Trunk COS .........................................................................................7-2
Attendant Class of Service ..................................................................................7-33
Tenant Class of Service ......................................................................................7-44
TOC-4
PI Reference Manual
8 Trunk Controls
General Trunk Timers ...........................................................................................8-3
Trunk Timers .........................................................................................................8-7
MFR Card Database ...........................................................................................8-10
General Trunk Definitions ....................................................................................8-11
Trunk Group Definition ........................................................................................8-18
Alternate Route ...................................................................................................8-34
DID/E&M Groups .................................................................................................8-36
Offset Filters ........................................................................................................8-42
Power Fail Trunk Definition .................................................................................8-44
LS/GS (Loop/Ground Start) Trunks .....................................................................8-46
4T/8T LGS Port Database ...................................................................................8-50
4T/8T Card Database ..........................................................................................8-52
4TEM - E&M Continuous .....................................................................................8-58
E&M Continuous Timers .....................................................................................8-59
4TEM (E&M Continuous) Card Database ...........................................................8-62
4TEMP (E&M Pulsed) .........................................................................................8-64
............................................................................................................................8-64
4TEMP (E&M Pulsed) Port Database .................................................................8-65
4TEMP (E&M Pulsed) Card Database ................................................................8-67
4TWL Trunk Card Database ...............................................................................8-84
E&M Trunk Definition ..........................................................................................8-87
DID Trunk Definition ............................................................................................8-90
8DID Card Database ...........................................................................................8-91
T1 and 30T/x Card Configuration ........................................................................8-95
T1, PRI, TBR, 30T/x, 2DT Synchronization ........................................................8-98
2DT Card Database ..........................................................................................8-102
2DT Card Database: DEFAULT Configuration ..................................................8-103
2DT Card Database: CURRENT Configuration ................................................8-105
T1 and 30T Card Database ...............................................................................8-108
T1 and 30T Port Database ................................................................................8-111
30T/M Cards ......................................................................................................8-113
30T/M Card Database .......................................................................................8-114
30T/M DDI/DDO/BI-D Port Database ................................................................8-120
30T/M DDI Port Database .................................................................................8-122
30T/M Timers ....................................................................................................8-123
TOC-5
PI Reference Manual
30T/E Cards ......................................................................................................8-124

30T/E Card Database ........................................................................................8-125
30T/E DDI Port Database ..................................................................................8-130
30T/E DDO Port Database ................................................................................8-132
30T/E NonDDI Port Database ...........................................................................8-133
ALS70 Cards .....................................................................................................8-135
ALS70 Card Configuration ................................................................................8-136
ALS70 Card Database ......................................................................................8-138
ALS70 Port Database ........................................................................................8-141
ALS70 Loop Start Port Database ......................................................................8-142
ALS70 DID Port Database ................................................................................8-143
ALS70 NonDID Port Database ..........................................................................8-144
ALS70 Trunk Timers .........................................................................................8-145
BID Cards ..........................................................................................................8-146
BID Trunk Port Database ..................................................................................8-147
BID Trunk Timers ..............................................................................................8-149
GID Cards .........................................................................................................8-150
GID Card Database ...........................................................................................8-151
GID Port Database ............................................................................................8-155
GID Timers ........................................................................................................8-157
9 Station Controls
Station Timers .......................................................................................................9-2
SLT Definition ........................................................................................................9-5
SLT: iDSP Card (Caller ID Type Bellcore/ETSI) Database .................................9-19
SLT Card Database .............................................................................................9-20
Keyset Timers .....................................................................................................9-27
Keyset Ring Cadence ..........................................................................................9-29
Keyset Definition .................................................................................................9-31
Keyset Button - Programming .............................................................................9-76
Keyset Fixed System Keys - Programming .......................................................9-102
Keyset Soft Keys Idle Set ..................................................................................9-103
Keyset Preference - Programming ....................................................................9-117
APA, PEX/APA and APDL RS-232 Setup .........................................................9-119
Wireless Stations - CoralAIR .............................................................................9-122
Magneto 8SM Card Database ...........................................................................9-125
TOC-6
PI Reference Manual
10 Groups
Hunt Group ..........................................................................................................10-2
Boss Group .......................................................................................................10-18
Pickup Group .....................................................................................................10-23
Zoned Voice Page Group ..................................................................................10-24
Bell/UNA Group .................................................................................................10-25
Group Calls .......................................................................................................10-26
ELA Group .........................................................................................................10-38
11 Libraries
Public Library .......................................................................................................11-2
Private Library .....................................................................................................11-9
Serial Library .....................................................................................................11-12
Large Public Library - Overview ........................................................................11-18
Large Public Library Numbering Plan ................................................................11-20
Large Public Library Contents ...........................................................................11-22
Directory ............................................................................................................11-25
Directory - Systems (Shared) Directory Entries ................................................11-26
Directory - Personal Directory ...........................................................................11-29
12 Night Service
Night Service - Timers .........................................................................................12-2
Night Service- Definition ......................................................................................12-5
Weekend Timers .................................................................................................12-6
Holiday Timers ....................................................................................................12-7
13 Toll Barriers
Toll Barrier ...........................................................................................................13-2
TOC-7
PI Reference Manual
14 SMDR
SMDR Control .....................................................................................................14-2
Report Control ...................................................................................................14-10
Format Params ..................................................................................................14-11
Auto On-Line .....................................................................................................14-13
Charge Table .....................................................................................................14-16
15 Routing & Cost Calculation

Routing System Parameters ...............................................................................15-3
Routing Access General Definitions ....................................................................15-5
Routing Class of Service .....................................................................................15-9
Dial Services .....................................................................................................15-11
Route Elements .................................................................................................15-25
Routing Numbering Plan ...................................................................................15-28
Routing Translators ...........................................................................................15-31
Look Ahead Routing Triggers ............................................................................15-32
Cost Calculation Elements ................................................................................15-38
Cost Calculation Numbering Plan .....................................................................15-40
Cost Calculation Parameters .............................................................................15-41
16 Room Status/
User Canned Messages
Names .................................................................................................................16-3
Status/Message Select ........................................................................................16-5
Status_Display/Message .....................................................................................16-6
Busy Display ........................................................................................................16-7
Terminal ..............................................................................................................16-8
TOC-8
PI Reference Manual
17 Service Terminals
Password and Site Name ....................................................................................17-2
Message Control .................................................................................................17-4
Message Select ...................................................................................................17-6
Terminal Destination ...........................................................................................17-8
CoralVIEW Traffic (CVT) Terminal Destination ...................................................17-9
Call Trace ..........................................................................................................17-10
Terminal Setup ..................................................................................................17-11
KB0 Setup Through Attendant Console - Feature .............................................17-29
Terminal Reset ..................................................................................................17-30
Terminal Clear ...................................................................................................17-31
iVMF Remote Maintenance ...............................................................................17-32
18 Features
Feature Control ...................................................................................................18-2
19 Voice Transmission Controls

Gains - General Description................................................................................. 19-2
Gains Tables .......................................................................................................19-3
Feature Control .................................................................................................19-17
Personal Port Gain, Compensation: Ports ........................................................19-22
Personal Port Gain, Compensation: Comp .......................................................19-23
Balancing Network ............................................................................................19-24
20 Wakeup
Wakeup Control ...................................................................................................20-2
Wakeup Report ...................................................................................................20-4
21 Special System Options-
TOC-9
PI Reference Manual
Database Control
& Duplication Systems
Database Control ................................................................................................21-2
First Initialization ..................................................................................................21-3
Backup ................................................................................................................21-4
Database Control: Disk (FlexiCom 6000, IPx 4000) ...................................................21-5
Save Database (FlexiCom 6000 and IPx 4000) ........................................................................21-6
Load DBS (FlexiCom 6000 and IPx 4000) ..................................................................................21-7
Copy Files (FlexiCom 6000 and IPx 4000) .................................................................................21-8
Show Dir (FlexiCom 6000 and IPx 4000) ..................................................................................21-10
Auto-Backup (FlexiCom 6000 and IPx 4000) ..........................................................................21-11
Database Control: FLASH (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS
200E) ............................................................................................................................................21-12
FLASH: Save (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS 200E) .....21-14
FLASH: LOAD DBS (IPx Office, FlexiCom 400, 5000, IPx 500, 800, 3000, CDRS 200E) ....21-15
FLASH: SHOW FILE INFO (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS
200E) ..................................................................................................................21-16
ROOT,0,10,2,2,2 ...............................................................................................21-16
FLASH: AUTO BACKUP (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) 21-17
FLASH: ERASE (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) ..............21-18
FLASH: INIT DUMP (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) .......21-19
Duplication (FlexiCom 5000 and IPx 3000 dual control) ..........................................................21-20
HSB (FlexiCom 6000/R and IPx 4000/R redundant control) ......................................................21-25
22 Diagnostics
Diagnostic Tests ..................................................................................................22-2
Diagnostic Alarms ...............................................................................................22-5
TOC-10
PI Reference Manual
23 Special Port Facilities

DVMS Port ..........................................................................................................23-2
Conference ..........................................................................................................23-4
Public Address/Page ...........................................................................................23-7
Modem ................................................................................................................23-9
Bell/UNA ............................................................................................................23-10
Page_Q/Music ...................................................................................................23-11
24 VFAC
Verified Forced Account Code ............................................................................24-2
25 Time/Date Set and Adjust

Time Set ..............................................................................................................25-2
Time Adjust .........................................................................................................25-5
26 ISDN
System Features - ISDN .....................................................................................26-2
BCCOS Templates ..............................................................................................26-3
BCCOS Control ...................................................................................................26-5
NSF .....................................................................................................................26-6
Call by Call ..........................................................................................................26-8
Alternate Line ID ..................................................................................................26-9
ISDN Card Signaling .........................................................................................26-11
ISDN Card Signaling: Signaling Channel ..........................................................26-12
ISDN Card Signaling: Card location ..................................................................26-13
TOC-11
PI Reference Manual
27 MAP, CLA and CoraLINK™

MAP .....................................................................................................................27-2
CoraLINK .............................................................................................................27-8
CoraLINK: CLA_STATUS .................................................................................27-11
CoraLINK: CLA_SIZES .....................................................................................27-15
CoraLINK: WAIT_QUE ......................................................................................27-16
28 ISDNet™
System Features - Network .................................................................................28-3
Node NPL ..........................................................................................................28-10
Node Content ....................................................................................................28-12
Special Numbering Plan Functions ...................................................................28-15
TOC-12
PI Reference Manual
29 IP — Voice Over IP
UGW (Universal Gate Way) ................................................................................29-7
UGW: Default Configuration ................................................................................29-9
UGW: Current Configuration .............................................................................29-13
IP Ports ..............................................................................................................29-27
IP_Keyset ..........................................................................................................29-28
IP_SLT ..............................................................................................................29-36
IP_LGS ..............................................................................................................29-38
IP_Net ...............................................................................................................29-40
SIP Ports ...........................................................................................................29-41
SIP Terminal ......................................................................................................29-43
SIP Trunk ..........................................................................................................29-52
IP: Telephony Gateway (Coral Teleport) ...........................................................29-62
IP: General ........................................................................................................29-68
IP: Statistics .......................................................................................................29-79
IP: NET ..............................................................................................................29-80
IP: ZONE ...........................................................................................................29-82
IP: SIP DOMAINS .............................................................................................29-88
IP: SENTINEL Pro .............................................................................................29-89
Software Upgrade .............................................................................................29-93
UGW Software Upgrade: Activate .....................................................................29-94
UGW Software Upgrade: Cancel ......................................................................29-97
IP Keyset Software Upgrade: Activate ..............................................................29-99
IP Keyset Software Upgrade: Activate by Dial Number ..................................29-100
IP Keyset Software Upgrade: Activate by IP Address .....................................29-102
IP Keyset Software Upgrade: Cancel ..............................................................29-103
IP Keyset Software Upgrade: Cancel by Dial Number ....................................29-104
IP Keyset Software Upgrade: Cancel by IP Address ......................................29-105
Sentinel Software Upgrade: Activate ...............................................................29-106
Sentinel Software Upgrade: Activate by Index Number ..................................29-107
Sentinel Software Upgrade: Activate by IP Address .......................................29-109
Sentinel Software Upgrade: Cancel ................................................................29-110
Sentinel Software Upgrade: Cancel by Index Number ....................................29-111
Sentinel Software Upgrade: Cancel by IP Address .........................................29-112
TOC-13
PI Reference Manual
30 Coral Traffic Report (CTR)

Internal Traffic: Definition ....................................................................................30-4
Internal Traffic: Features and Events Control ......................................................30-6
Internal Traffic: Reports: Format Parms ............................................................30-10
Internal Traffic: Reports: View ...........................................................................30-14
TOC-14
1 Introduction
The Program Interface (PI) is a detailed, menu-driven, interface system for

programming the Coral System.
This chapter gives general information on how to use the Program Interface and
how to set-up the PI software and hardware equipment. The PI terminal commands
are listed in tabular form for easy reference. Other conventions and shorthand
notations used in this manual are also listed at the end of the chapter.
The chapter contents include the following:
General Description ......................................................................................1-2
PI Terminal Device.......................................................................................1-4
Hardware Setup ............................................................................................1-5
Access to the Programming Interface ........................................................ 1-11
PI Terminal Control Function Commands .................................................1-14
Conventions Used in this Document..........................................................1-17
Country Codes ............................................................................................1-19
1-1
Introduction PI Reference Manual
General Description
The Program Interface (PI) is a detailed, menu-driven, interface system for
programming the Coral System. It also provides access to the diagnostic facilities
contained within the system software.
The PI can be accessed through any of the following types of connecting devices:
• video display data terminal
• keyboard send/receive (KSR) printer data terminal
• a data terminal and modem
• PC with VT emulator
• PC with CoralVIEW Designer (CVD)
• PC with CoralVIEW Administrator (CVA)
• PC via Telnet Terminal Emulation (requires STIP, MAP or LIU)
An additional PI function allows saving and restoring the entire database contents
to a binary disk file, using a personal computer (PC) and save/restore software.
Backups are also updated to the IMC-8/16 or CFD flash memory cards.
See Database Control: Disk (FlexiCom 6000, IPx 4000) beginning on page 21-5.
See Database Control: FLASH (IPx Office, FlexiCom 200,300,400,5000, IPx
500,800,3000, CDRS 200E) beginning on page 21-12.
In the Coral FlexiCom 400,5000,6000 and Coral IPx 800, 3000,4000 the PI data
terminal is connected to the Coral through one of the three RS-232 interfaces on
the RMI card (RS-232C) or 8DRCM-2/8DRCM/ 8DRCF card (RS-232E) at the
cable pinouts on the Main Distribution Frame (MDF) or through the internal
modem interface on the card. One RS-232E interface is provided at the front panel
of the MEX-IP2, or MCP-ATS card in the Common Control (see Figure 1-1).
In the Coral IPx Office Main Unit the PI is connected to one RS-232E interface.
One KB0 is provided at the front side of the Coral IPx Office.
Additionally, the PI can be connected through an internal modem (KB4) located on
the U-RMI Office or RMI Office card.
For Coral IPx Office Systems with optional IPx 800X expansion unit the PI data
terminal is connected to the Coral through one of the three interfaces (KB5,6,7) on
the RMI card (RS-232C), or 8DRCM/8DRCF/8DRCM-2 card (RS-232E) at the
modem interface (KB8) on the card.
In the CDRS 200E and Coral IPx 500M Main Unit the PI is connected to one of
four RS-232E interfaces. One KB0 is provided at the front side of the MCP-IPx2
card. Another three interface connectors, KB1, KB2 and KB3 are provided at the
upper left side at the auxiliary I/O entry of the main cage (MSBipx card).
Additionally, the PI can be connected through an internal modem (KB4) located on
the MSBipx card.
1-2
PI Reference Manual Introduction
For Coral IPx 500 Systems with optional IPx 800X expansion unit the PI data
terminal is connected to the Coral through one of the three interfaces (KB5,6,7) on
the RMI card (RS-232C), or 8DRCM-2/8DRCM/8DRCF card (RS-232E) at the
modem interface (KB8) on the card.
Multiple but simultaneous, independent PI sessions from different monitors are
possible, though this practice is not recommended.
Access to the PI is restricted to trained and qualified technicians. Uncertified
personnel can unknowingly cause serious damage to the communication system
database.
The terminal or printer displays Coral-generated prompts (questions, instructions,
options, etc.) in plain English; the programmer can make an entry, skip to the next
prompt, or exit the programming function. The various card functions can be
accessed using a written command, e.g. NPL to “jump” directly to the Numbering
Plan or accessed stepwise, e.g. (0,0,5).
Entries are made using a standard keyboard; the keyboard DELETE
(not BACKSPACE) key is used on most terminals to erase incorrect characters.
Entries are displayed as they are keyed. Changes entered, take effect in “real time”;
i.e., as soon as the ENTER key is pressed, the change is entered into the system
memory, and immediately takes effect.
1-3
PI Terminal Device
The Program Interface (PI) terminal device should be either an asynchronous,
ASCII video display data terminal, a Personal Computer (PC) with terminal
emulator software, a KSR printer equipped with a serial interface (RS-232E), a
Bell 103/212A/V.90 compatible data modem (see Table 1-1 below). Either one of
two popular video display terminal emulations are supported for character
attributes, cursor positioning and screen refresh. If the video display terminal
connected to the Coral system does not emulate one of the two supported
emulations, or a portable data printer is used instead of a video display terminal,
use the Printer definition in Terminal Setup beginning on page 17-11. The Modem
setup definition is described in the same branch.
Table 1-1: Programming Interface Terminal Communications
Terminal Type DEC VT-100 (Default)

Qume QVT-101 (or ADM-3A/5, TV1900)
Standard KSR Data Printer
Standard PC (also for CVT, CVA or CVD)
CID terminal (not KB0 not 8DRCM-2 and not 8DRCF)
RS-232 Data Transfer Rate 9,600 bps Default Baud Rate for all systems.
8DRCM-2, 8DRCF, 8DRCM, RMI, See BAUD RATE (page 17-26) for a detailed list when changing
MEX-IP2, MCP-ATS, MCP-IPx2, baud rates.
MSBipx (Coral IPx 500M and CDRS 200E),
MCB Office (Coral IPx Office)
Modem Compatibility 56 Kbps (V.90 ITU-T)

8DRCF,
Coral IPx 500M and CDRS 200E (with
lower),
Coral IPx Office (with RMI Office or U-RMI
Office)
Modem Compatibility Bell 103/212A Answer-300/1200 bps

8DRCM, CCITT V.21/V.22 Answer Mode-300/1200 bps
RMI
Parity None (Default), Odd, Even, Mark or Space
Data Word Length 7 or 8 (Default) bits
Stop Bits 1 bit
Format Asynchronous data

Standard ASCII character set
 To use the “SNAP” (real time display) functions available in some programming
areas, the PI device must emulate a Digital Equipment Corporation VT-100 or a
Qume Corporation QVT-101. This function is not essential for programming;
however, it is beneficial when the PI device is also used for system diagnostics.
While the PI terminal device communication specifications may be altered, the
default values listed in the above table, default upon first initialization, and must be
used in order to initially enter the Coral system programming interface. Afterwards
they may be changed.
1-4
Hardware Setup
The PI terminal device can be connected to:
• Telnet Terminal Emulation via an LIU, STIP or a MAP card
• An RS-232 type interface on the system; KB0 in all Coral systems, and KB1,
KB2, KB3 in IPx 500 and CDRS 200E systems or to the RMI/8DRCM/8DRCF
internal modem.
All features and functions are available through either connection.
Telnet Terminal Emulation via a MAP Connection
The MAP card (IP port 11010) offers integrated Coral system IP
connectivity with:
• Faster and more reliable connections than the serial RS-232
connections or even the LIU IP connections
• Up to four concurrent users can connect via the same TCP/IP network
socket.
In the Coral IPx Office the MAP card is embedded as a software only application
on the MCB Office (main board of the Coral IPx Office).
In the Coral IPx 500 and in the CDRS 200E the MAP card is installed on the
MCP-IPx2 main control processor card.
In the Coral IPx 800,3000 and FlexiCom 400,5000 the MAP card is installed on
the MEX-IP2 main control processor card.
For further information about the MAP card refer to Chapter 6 of the Coral
Control Cards (for CDRS 200,200E; IPx 500,800,3000 and FlexiCom
200,300,400,5000) Manual.
 The MAP does not support Initialization messages, GP messages and other
online Alarm messages, when used to communicate with the PI (Program
Interface) over IP.
Telnet Terminal Emulation via an LIU Connection
The LIU card (IP port 11001) enables the MCP-IPx2 and the MEX-IP2 main
control processor card to communicate with the PI via the RJ-45 LAN
connector. Without this card, communication via the RJ-45 connector cannot
take place, and all interaction with the PI must occur via the KB0 RS-232 port
(unless a MAP card is installed. When a MAP card is installed, communication
via the RJ-45 connector can take place and the LIU card is redundant).
The LIU card translates the RS-232 protocol used by the KB0 to the IP
protocol. In order for the LIU to function, it is necessary to move DIP switch
1-5
#1 on the front panel of the MCP-IPx2 and the MEX-IP2 cards to the left and
do one of the following. (See Figure 1-1):
• To connect the RJ-45 port to the LAN, connect an ordinary cable between the
RJ-45 port and the LAN outlet.
• To connect the RJ-45 port directly to a workstation, connect a cross-over cable
between the RJ-45 port and the workstation.
For further information about the LIU card refer to Chapter 7 of the Coral
Control Cards (for CDRS 200,200E; IPx 500,800,3000 and FlexiCom
200,300,400,5000) Manual.
Telnet Terminal Emulation via a STIP module Connection
The STIP module enables all Coral main control processor cards to
communicate with the PI via the RJ-45 LAN connector.
The STIP is a Serial RS-232 to IP translator. The STIP enables serial devices to
connect to the Internet. The STIP provides transparent serial data-to-Internet
protocol conversion and Internet protocol to serial conversion. Connection of
the STIP to a serial device (Coral systems) and modem makes the Coral
systems IP-compatible. The STIP connects with any device that has a serial
RS-232 port that requires communication with an IP interface.
For further information about the STIP refer to the STIP Reference (Installation
and Configuration) Manual.
On-Site RS-232 Connection
The PI terminal is connected to the MEX-IP2/MCP-IPx2/MCP-ATS/Coral IPx
Office front panel DB9 connector, KB0. Note that the connector is wired as a Data
Terminal Equipment (DTE) device. Verify that electrical connections between the
KB0 port and PI terminal reflect a DTE to DTE or Null Modem connection.
Many video display terminals require only the Transmit Data (Tx), Receive Data
(Rx) and Signal Ground conductors to be connected between the PI terminal
device and the KB0/KB1 or 8DRCM/8DRCF/8DRCM-2/RMI serial data port. The
Qume QVT-101 terminal requires that the Clear to Send conductor be active or
high (+3 to +12Vdc) to display received data.
Figure 1-2 shows the connections for using a standard PC (COM1 or COM2) with
the KB0 interface.
Figure 1-3 shows the connections for using a VT-100 or Qume QVT-101 with the
KB0 interface.
Some portable data printer terminals require that one or more status conductors
(e.g. Carrier Detect or Clear to Send) of the terminal be high, active, or asserted
for the terminal to be on-line or in a communications mode. The Request to Send
and Data Terminal Ready conductors of the KB0 connector are kept high and may
be connected to conductors of the terminal device for this purpose. If the terminal
device appears unresponsive after it is connected to the Coral, consult the
1-6
manufacturer’s operating manual in order to determine if the selected terminal

device required any status conductor to be active.
Figure 1-1. Control
Cards- MEX-IP2
MEX-IP2
Front Panel M
C
P
-
I
P
x
2
Option
Option Switches
Switches
Set DIP Switch# 1
KB0 to the Right for
KB0
KB0 Connections
Reset
Reset
RESET
IMC-4/8
FMsl IMC-8 /16
Release
Button
IMC-4/8
Release Button IMC-8/16
KB0
RS-232 E
Set DIP Switch# 1

to the Right for LAN LAN
KB0 Connections
KB0
SAU SAU
Reset
Indicator
Lights
HS
MCP-IPx2 MEX-IP2 MCP-ATS
Coral IPx 500 Coral IPx 800, 3000 Coral IPx 4000
FlexiCom 200 FlexiCom 300, 400V, 400, 5000 FlexiCom 6000
CDRS 200, 200E
Coral IPx Office
CPU
UGW
GC
FAN
MAINT.
MRC
GC ACT.
POWER
KB0 UGW LAN 2 4 6 8 WAN PRINTER N.C.
COM RESET
SYS.
MEMORY DISK RESET
1 3 5 7
IMC-x IMC-x KB0 RESET

Release
Button
1-7
KB0: Data Terminal Port: RS232-E DTE Interface.

Default configuration: 9600 bps, No parity, 8 data bits, 1 stop bit,
VT-100. Table 1-2 describes the KB0 RS-232 pin connections to
the PI terminal.
Option Switches: MEX-IP2 and MCP-IPx2:

Switches 1-8 Always Set to the Right
Switch 1 LEFT for PI-LAN (LIU) Connections Only
Switch 1 RIGHT for KB0 Connections
Switch 3 (MCP-IPx2) LEFT for IMC4
Switch 7 should be set to OFF (RIGHT) so that the system will
respond after a power failure.
Coral IPx 4000 and Coral FlexiCom 6000 systems: The
Option switches are located on the 32GC control card, not
shown here. There are only 4 switches (0-3) and Switch 3
should be set to OFF (Right) so that the system will respond
after a power failure.
Reset Button: Forces the CORAL system to restart.

CAUTION! Pressing this button will cause
partial initialization and drop all calls.
Additionally, all keyset call logs will be cleared.
7-Segment Display: For alarms and diagnostics.

Coral IPx Office, Coral IPx 4000 and Coral FlexiCom 6000
systems: 7-segment display is not used.
SAU Software Authorization Unit is attached here.

Coral IPx 4000 and Coral FlexiCom 6000 systems: The SAU
socket is located on the 32GC control card, not shown here.
Coral IPx Office: The SAU socket is located on the right panel.
Table 1-2: KB0 RS-232 Interface Pin Functions
Pin #* Signal Mnemonic Function
1 N/A ---
2 RX (Receive) Receives serial data input fro

communications link
3 Tx (Transmit) Sends serial output to

communications link
4 DTR Data set is ready to establish a

communications link
5 GND Ground
6 DSR Data set is ready
7 RTS Indicates to data set that UART is

ready to exchange data
8 CTS Data set is ready to exchange data
9 N/A ---
* Pins 2, 3 and 5 are sufficient to connect the Coral system.
1-8
Figure 1-2. PI DB9

Terminal to KB0
5 SIGNAL GROUND - 5
Connection 9 9
4 DATA TERMINAL READY - 4
3 TRANSMIT DATA - 3
2 RECEIVE DATA - 2
6 6
1 CARRIER DETECT - 1
KB0
PROGRAMMING PORT 9 PIN PC ASYNC. SERIAL PORT
(USE FEMALE CABLE 9 PIN CONNECTOR) (USE FEMALE CABLE CONNECTOR)
Figure 1-3. PI DB25

Terminal to KB0
13
Connection 25
5 - SIGNAL GROUND SIGNAL GROUND - 7

DATA SET READY - 6
4 - DATA TERMINAL READY
CLEAR TO SEND - 5
3 - TRANSMIT DATA
REQUEST TO SEND - 4
2 - RECEIVE DATA RECEIVE DATA - 3

TRANSMIT DATA - 2
1 14
1
KB0 PC Async. Serial Port

PROGRAMMING PORT or Async.Data Terminal
(USE FEMALE CABLE 9 PIN CONNECTOR) (USE FEMALE CABLE CONNECTOR)
1-9
Remote Connections
Remote connections are made by connecting the PI terminal device to a modem
and establishing a voice call from the remote terminal modem to the Coral Modem.
Coral IPx Office system requires the installation of a U-RMI Office or RMI Office
card to accommodate remote access, or the installation of an external, customer
provided modem to the KB0 interface.
Coral IPx 500 and CDRS 200E systems are equipped with a built in modem.
Coral FlexiCom 400, 5000, 6000 and Coral IPx 800, 3000, 4000 systems require
the installation of an 8DRCM, 8DRCF, 8DRCM-2 or RMI card to accommodate
remote access, or the installation of an external, customer provided modem to the
KB0 interface.
Figure 1-4 illustrates the necessary connections between the KB0 interface and a
typical external modem, however, the connections to some modems may vary.
 When an external modem is connected to KB0, before first initialization,

the option switches located on the control card must be set up for the
required baud rate (see BAUD RATE on page 17-26).
Figure 1-4. External Signal Ground

Modem to KB0 Data Set Ready
Connection
5 - Signal Ground To Typical
4 - Data Terminal Ready Request To Send Modem Device
3 - Transmit Data Receive Data
2 - Receive Data Transmit Data
1
KB0 SERIAL PORT

(USE FEMALE CABLE
9 PIN CONNECTOR)
See the relevant Coral Installation Guide and Hardware Reference
Manual for precise modem setup instructions.
1-10
Access to the Programming Interface

Secure
Multi-level access control (Extensive rights are defined for different users).
Access to the Programming Interface facility is controlled by passwords. There are
four PI password levels. The programmer requires Level 2. This password is
provided only for qualified personnel.
PI Software Structure
The PI software is a menu-driven and branch oriented system. The programmer can
select a specific branch, which branches out into more detailed lists. In addition,
the programmer is able to jump from one menu to another with no restrictions,
except those demanded by specific password levels.
When the PI software is first accessed, the ENTER PASSWORD prompt appears.
After a valid password is entered, the Root Menu appears.
1-11
Root Menu Variations

The Root Menu is the main menu in the PI structure, from which the rest of the PI
issues. The PI software is part of the system software. The Root Menu reflects the
installed software version by listing the available items specific to the installed
software version.
 Entering the word ROOT anywhere within the PI, will take you to this
menu.
Figure 1-5.
PI Interface
Root Menu (ROOT)
CCS 16.03.00
Copyright (c) 2001-2012 Tadiran Telecom (TTL) L.P. (“Tadiran”)
(M) or (S)
or (Active)
NAME -
SAU # -
0-CONFIG
1-DIAGN
2-TABLES
3-ADMIN
4-ROUTING/COST
5-ISDN
6-DATA
7-CoraLINK
8-NETWORK
9-IP
• This manual describes all of the root menu options except 1-Diagn and
2-Tables. Tables programming is reserved for the manufacturer’s internal
use.
• In Coral FlexiCom 5000 and Coral IPx 3000 with Dual Control systems, the
letter M (Master) or S (Slave) appearing after the version number indicates the
PI side definition.
• In Coral FlexiCom 6000 and Coral IPx 4000 systems, the letter A (Active), S
(Standby) (if feature authorization is present for duplication) or M
(Maintenance) or the word “Faulty” appear after the version number indicating
the PI side definition.
• SAU shows the Software Authorization Unit (SAU) unique serial number
(without the leading zeros). This number is verified during system operation.
When a mismatch is detected during operation, a system alarm is issued and an
error message is displayed.
1-12
Access to Specific Menus

Access to the root menu may be done from anywhere within the PI, by entering the
word ROOT.
Access the menu items by keying a sequence of digits from the root menu that route
the user to the required branch, such as 0,6,0 which will route to Public Libraries.
An alternative method for accessing items is to type the alpha or alphanumeric code
for the item, such as LIB which provides direct access to Speed Calling Libraries.
 An advantage of using the alphanumeric code is that this method allows

access to a specific branch from anywhere in the system, except from the
NAME field. While the numeric digit method allows access only from the
Root Menu. Alternatively, ROOT,0,6,0 routes to LIB from anywhere within
the system.
1-13
PI Terminal Control Function Commands

The PI terminal keyboard is used to enter data and to instruct the PI software to
perform specific functions. Several special function commands are available, and
executed by simultaneously pressing the [CTRL] (Control) key and a specific letter
key. The commands and their functions are listed in the following table.
Table 1-3: PI Control Characters and Escape Functions
Code Description Remarks

[CTRL] B Causes the previous field within the menu or list to be displayed.
[CTRL] C Cancels the current process; returns PI to previous menu or list.
[CTRL] D Often a displayed mode contains too many entries or tables to be

displayed on one screen.
To view a subject one entry (screen) at a time, use the [CTRL] D
switch.
To cancel, use [CTRL] D again as a toggle switch. While this
mode is active, after displaying the first screen of entry, the PI
pauses. To continue viewing the next screen of entry, press
<CR>. When the [CTRL] D switch is activated, the following
messages are displayed:
activate: ***ENTRY BY ENTRY DISPLAY***
cancel: ***SCROLLING DISPLAY***
[CTRL] E Causes the End-of-Table message to be shown, after the last

field in Update mode. When activated End-of-Table allows the
[CTRL] B switch to jump to the last field. This switch toggles
between the default Normal Display and the End-Of-Table
display.
[CTRL] H Defines a new “Escape” or Home menu; The ASCII character code defines
When [CTRL] H is entered the following message appears: [CTRL] H as the BACKSPACE
ESC will place you in this Node character. Some terminal keyboards
This PI menu is now displayed whenever pressing [ESC]. can be configured to send a DELETE
Note: character when backspacing. When
Entering ROOT from anywhere within the PI will always place available on the terminal, select this
you in the Root menu. option to avoid changing the Escape
menu.
[CTRL] N For Use by Manufacturer Only.

Toggles the display of memory pools in chain order. When
activated the following messages are displayed:
*** CHAIN DISPLAY ***
*** NORMAL DISPLAY ***
1-14

[CTRL] O For Use by Manufacturer Only. Recommendation:
Return to the Master side before
ending a PI session (with [CTRL] P).
Coral FlexiCom 5000 or IPx 3000 -Duplication only.
Toggles terminal communication between the Slave and the
Master side. When full duplication is invoked (i.e., in the U and U'
configurations, see MASTER on page 21-20, [CTRL] O enables
the technician to operate the PI from the
8DRCF/8DRCM/8DRCM-2/RMI or KB0 master terminals as if
s/he is physically located at the slave location.
Coral FlexiCom 6000/R or IPx 4000/R Dual Control

only.
Toggles terminal communication between the Standby and the
Active side. See HSB on page 21-25.
After connecting (or disconnecting) the terminal to (or from) the

KB0/8DRCF/8DRCM/8DRCM-2/RMI Slave/Standby side or KB0
Master/Active side, one of the following messages appear:
terminal connected or
terminal disconnected.
The following terminal status messages appear while the terminal
is being connected between sides:
FlexiCom 5000
switching terminal to slave side or
switching terminal to master side.
FlexiCom 6000
switching terminal to Standby side or
switching terminal to Active side.
[CTRL] P Ends the PI session; password entry is required to start a new PI There is an automatic logout upon
session. Pressing [CTRL] P is recommended when exiting in inactive terminal (see AUTO_LOGOUT
order to prevent unauthorized operators from entering the PI and and AUTO_LOGOUT_TIME on page
causing damage. When changes are made to systems that do 17-25).
not include an automatic backup, the following message appears:
CAUTION!!! Auto backup NOT available
<<DATABASE SAVE Recommended After Changes>>
Quit Anyway (Y/N)? Y
Typing N(o) returns to the current PI mode. Typing Y(es) will
leave the session.The default is Y(es) [CR].
[CTRL] Q Turns off the [CTRL] S command (below). [CTRL] Q and [CTRL] S functions are
commonly referred to as X-On/X-Off or
DC1/DC3. Some terminal keyboards
include a SCROLL LOCK key, which
alternately sends a [CTRL] S and
[CTRL]Q to toggle scrolling.
[CRTL] R Shows the current menu path from the Root Menu.
Utilized by KB0 only.
[CTRL] S Causes the display to stop scrolling.
[CTRL] T Displays current system status: Installation name, current time

and date, terminal number, password level, system software and
card version and system type HDC/4GC/16GC/32GC, HSB &
MCP-ATS, etc.
[CTRL] U Causes the previous menu or list to be displayed.
1-15

[CTRL] V Terminates the display of stimuli code messages. Same as entering MSG,2,0,N.
[CTRL] W Toggles the 25-line scroll function on (display scrolls 25 lines and
stops) and off (display scrolls to the end of the menu, list, etc.).
RESTART Begins a RESTART procedure. This command is used when the

[CTRL] Y PI is not properly responding. Type RESTART in upper case.
ESC Pressing the Escape key in any location returns the session to
the PI Home Menu as defined by [CTRL] H. The Root Menu is
the default; any menu or list may be specified by moving to the
desired menu and entering [CTRL] H.
1-16
Conventions Used in this Document

Routes
Branch headings (starting in Chapter 3) always show the subject and the route
keyed from the Root Menu to reach that subject, for example:
Installation ç ROOT [0,0,0,0]
Many option headings offer alternative routes; the first route given is the shortest
route and may be used from any point in the PI menu structure. An example is:
Feature Timers ç FE.T [0,0,1,0]
“FE.T” (also called Direct Access Abbreviation) may be keyed to access the
feature timers from any location in the PI structure. FE.T cannot be accessed when
in Name fields.
The route shown by digits and commas is used only from the Root Menu.
 Digits must be separated by commas or spaces. 0,0,0 and 0 0 0 are

acceptable; 000 is not acceptable.
Ranges and Defaults
The ranges and defaults available for a given programming option are presented
immediately after the parameter name on the same line.
The range default is designated with an arrow on top of default item. For example,
the range for SUSPECT SEIZE TIME in Trunk Definitions can be listed as:
50..80..500 ms or 0..80
where 80ms is the default in both cases and is designated by a pointed arrow on top
of the number.
When no default is designated, the default is Not Applicable.
For ranges that may include more than one default, the defaults are listed
separately. For example, the defaults for the PAGE parameter in Station and Trunk
COS, is shown as:
Yes/No
Yes: COS 0-9
No: COS 10-15
Explanation:
• The range is Yes or No.
• For COS 0-9 the default is Yes.
• For COS 10-15 the default is No.
1-17
When a system range is not relevant, None is shown as the entry. In addition, when
a range specification is not applicable for a specific option, the abbreviation N/A is
given instead of data.
When a system default is not available or not applicable, no arrows are shown and,
thereby, no default designated.
Display Only Parameters
Parameters which are read-only options, (i.e. Display Only) appear with the
following icon before the Range. The example below indicates that the parameter
value may vary between 0 and 60 units. The actual value is indicated on the PI
screen.
 0..60
Database Forms
A document called Database Forms is provided for writing down the various site
programming definitions that differ from the defaults presented in this manual.
Database Forms provides a convenient notebook for programmers to record
specific site data and information. This information can then be used in order to
redefine the various PI parameters. The headers of each major option in the
Database Forms mirror the titles of each Coral branch i.e., major options in this
document.
1-18
Country Codes
The Coral incorporates two different system types. System Type 0 and System Type 2.
System Type 0, designated as CC (Contry Code), is used for most countries. The countries that use System
Type 0, but with slight differences for their ranges and/or default values are listed as CCn types (where n is
a number). The relevant country type is listed below.
System Type 2, designated as Eu, is generally used for European countries. The countries that use System
Type 2, but with slightly different ranges and/or defaults are listed as Eun, where n indicates the specific
country.
Table 1-4: Country Codes
System Type Country Code Country
System Type 0 CC0 USA
Country Codes: CCn (n CC1 Israel
= any number) CC2 Mexico
CC3 Brazil
CC4 Venezuela
CC5 Argentina
CC6 China
CC7 Poland
CC8 India
CC9 ROW (Rest Of World), i.e. all other
countries not included in this list.)
CC10 Russia
System Type 2 Eu European systems
Country Codes: Eun (n = Eu0 Netherlands
any number) Eu1 Belgium
Eu2 Germany
Eu3 Spain
Eu4 Hungary
Eu5 Greece
Eu6 Australia
Eu7 New Zealand
Eu8 Czech Republic
Eu9 Italy
Eu10 Caribbean Islands
System type and Country Code (CC) numbers are displayed during Installation or
in the Install branch, see SYSTEM_TYPE and COUNTRY on page 3-2.
 When the word “European” or “Eu”, without a specific country, is given

this means that the system parameters or specifications are general for
European systems. If no country or area is indicated then the parameter is
valid as presented. 30T/E, ALS70, BID & GID trunk cards are used only in
European systems.
1-19
1-20
2 Programming Requirements
This chapter describes the PI programming requirements. Basic shorthand notation

used throughout the PI is also described in this chapter.
Default System .............................................................................................2-2
Typical Site-Specific Programming .............................................................2-3
Additional Programming ..............................................................................2-4
Programming and Entering Time Units .......................................................2-6
Programming Functions ...............................................................................2-7
Locating Data Fields ....................................................................................2-8
Direct Access Abbreviations (DAA) ...........................................................2-9
Entering Yes/No and Remove ....................................................................2-10
General Rules for Entering Names ............................................................2-10
Authorization Items ....................................................................................2-11
 Default System defines the default databases according to the country, system
type and Common Control card type.
 Typical Site-Specific Programming and Additional Programming describe

Coral programming for all the different PI branches.
 Programming and Entering Time Units defines the PI time unit notation.
 Programming Functions describes the different PI functions available at the

branches or options.
 Locating Data Fields and Direct Access Abbreviations will help you locate
the desired parameter, data field or branch needed to program the PI.
 Entering Yes/No and Remove Range and General Rules for Entering
Names describe the general rules for entering Yes, No, Remove and Names in
the parameter range.
 Authorization Items list the specific features that need software authorization
before they can be implemented.
Programming Requirements PI Reference Manual
Default System
The configuration of the Common Control cards determines the default database
that is installed upon First Initialization, as shown below.
Coral IPx Office, Coral FlexiCom 400, 5000, 6000 as well as the
CDRS 200E, Coral IPx 500, 800, 3000 and 4000 systems default to a
Coral system with 4GC, with authorized features defined by the SAU unit.
Should a particular parameter impact upon a different option, the relation between
the two is explained in the relevant description.
 The SIZES parameters must be programmed before all other parameters.

Changing the SIZES parameters causes the system to revert to the
manufacturer's default program.
2-2
PI Reference Manual Programming Requirements
Typical Site-Specific Programming

Depending on the site, the default database may require some programming. When
it is necessary to modify the default database, this information should be entered in
the Programming Forms. The programming parameters most often changed are
found in the following branches:
Sizes/URC/Music/System Engineering/Units Definition (Chapter 4)
Sets the maximum number of various system services, such as ports, libraries,
stations, trunks, etc.
Numbering Plan (Chapter 5)
Modifies the numbering plan for the specific site.
System (Chapter 6)
Modifies system timers, system features, system tones and identifies the hardware
assigned to specific physical locations.
Class of Service (Chapter 7)
Defines access to system features and functions.
Trunks (Chapter 8)
Defines trunks and trunk groups; individual menus are provided for Central Office
(loop/ground start), E&M, DID, T1, E1 (30T, 30T/E, 30T/M), TWL,
PRI (PRI-23/30 and IPG), BRI (TBR), SIP trunk and power fail trunks.
Stations (Chapter 9)
Defines all SLT, Magneto, FlexSet, FlexSet-IP, P-335, P-450, T207M, T208M,
T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL, T322, T328,
FlexIP SoftPhone, SeaBeam softphone, and third-party SIP terminal and keyset
requirements.
Power Fail stations are identified in the database using the Power Fail Trunk form
in Chapter 8 (Trunks).
2-3
Additional Programming
Depending upon site requirements, the following major options may need
additional programming.
Groups (Chapter 10)
Defines ACD/UCD Hunt Groups, Boss Groups, Pickup Groups, Zoned Voice Page
Groups, Bell/UNA (Night Answer Groups), Group Calls and ELA Groups.
DID/E&M Groups and Trunk Groups are defined in Trunks Chapter 8.
Libraries (Chapter 11)
Defines public (system-wide) and private (station-related) speed call libraries as
well as the parameters for the System Directory.
Night Service (Chapter 12)
Defines night service timers as well as incomplete and intercept call destinations.
Toll Barrier (Chapter 13)
Sets toll restrictions (barriers) on outgoing calls.
Station Message Detail Recording (Chapter 14)
Controls the system’s detailed call reporting to external SMDR systems.
Routing (Chapter 15)
Defines Routing and Cost Calculation parameters.
Room Status (Chapter 16)
Controls the system’s room status feature.
Service Terminals (Chapter 17)
Defines the various system parameters for service terminals.
Features (Chapter 18)
Defines port features which can be activated from either the PI terminal or the
Attendant Console.
Voice Transmission Controls (Chapter 19)
Controls voice transmission across ports and cards. Also included in this chapter is
the Network Balancing System.
Wakeup (Chapter 20)
Defines the Wakeup controls and Wakeup report production.
Special System Options (Chapter 21)
Defines those features that control the database, duplication system as well as the
Hot Standby Coral Systems.
Diagnostics (Chapter 22)
Defines those options that perform the various diagnostic tests and check the
system alarms.
2-4
Special Port Facilities (Chapter 23)

Defines those special options that are available for tenant members, plus defining
DVMS ports.
Verified Forced Account Code (VFAC) (Chapter 24)
Describes the various options that are available for VFAC.
Time/Date Set and Adjust (Chapter 25)
Describes the way in which the system time and date are set and adjusted.
Integrated Services Digital Network (Chapter 26)
Describes the various ISDN system options.
MAP, CLA and CoraLINK (Chapter 27)
Describes the MAP and CoraLINK database options.
ISDNet (Chapter 28)
Defines and allocates the Nodes and Node Contents in a Private Coral Network and
also includes the special General Numbering Plan functions for the Network
Nodes.
Voice Over IP (Chapter 29)
Manages the Coral VoIP (Voice calls over Internet Protocol) details. IP Ports are
managed from the branches included in this chapter, as well as general
system-wide IP parameters. Remote upgrades to the
PUGW/CUGW/UGW-E/UGW card as well as to IP Keysets and Sentinel Pro units
may be implemented via the PI as well.
SIP entities are also covered in this chapter.
Coral Traffic Report (Chapter 30)
Enables the technician to create customized internal Coral Traffic Reports f. A total
of ten different report templates may be defined. Additionally, the technician
decides which entities are to be monitored and for how many days.
2-5
Programming and Entering Time Units

The following table presents the 12 hour to 24 hour conversions for programming
and entering time units in the PI. Exceptions to the required 24 hour format are
described below.
AM Hours PM Hours
Time Enter Time Enter
Midnight 00 Noon 12
1 01 1 13
2 02 2 14
3 03 3 15
4 04 4 16
5 05 5 17
6 06 6 18
7 07 7 19
8 08 8 20
9 09 9 21
10 10 10 22
11 11 11 23
• Minutes are entered as two digits (00 through 59). All time entries are hh:mm,
where hh = hour (00-23) and mm = minutes (00-59).
• For single-digit hours, 1AM to 9 AM, a leading 0 can be added as required by
the programmer; for example: 8 am can be defined either as 8:00 or 08:00.
• A colon (:) must be entered between the hour and minutes.
2-6
Programming Functions
The following table presents the eight programming functions that can be applied
to the Program Interface. Only functions relevant to a specific branch are available
in that branch or option.
Code Function Description
0 UPDATE Allows changing or modifying the parameter values

or characteristics.
1 DISPLAY Displays all parameters for any specific port or range

of consecutively numbered ports.
2 ADD Instructs the system to make an addition to the

existing parameter or option for a specific port.
3 REMOVE Deletes an existing parameter.
4 SNAP Similar to DISPLAY, but in real-time. Used for on-line

monitoring from a single monitor only.
5 SHOW Generally used for showing Diagnostics and

Numbering Plan tables.
6 DUPLICATE Copies a defined feature or parameter from one port

or station to another port or station. Useful for rapidly
defining new stations or updating existing stations.
7 ERASE Deletes the branch database from memory while in a

specific branch.
2-7
Locating Data Fields

Data fields (parameters) can be located using short-cuts. When the question
Any specific data field (type? for help)
appears, any one of several actions can be taken:
• All Fields: Press <CR> to display or update all fields.
• Single Field: Enter single field name or field number to display or update a
single field.
• Multiple Fields: Enter up to seven field names and or field numbers to display
or update multiple fields. Each field must be separated by either a space or
comma, for example: 2,5,9 or 11 15 24 26 or 0 5 or MAX_RING, EXT.ID are all
valid entries.
• Field Search: Enter single field name/field number and value required for
searching. (field name) = (value). For example: while in the KEY node, to
identify all keysets defined as attendant, enter ATT = Y. All keysets defined
 Two values cannot be entered in the same instance;

with this value appear.
e.g. ATT = Y, PCC = Y is not a valid entry.

Field names can be entered in any of the following methods:
• Full field name, e.g. MAX_RING.
• The least amount of letters that identify a parameter, e.g. Max for MAX_RING.
The system will always start searching from the top of the current node.
• Field index number, this is the number that appears in square brackets after the
field name, e.g. [0]. Field Index is always correct for the most recent Coral
Version (check this handbook’s front cover to determine the most recent Coral
Version). In the more advanced versions, new field names are added. Changes
can occur in their numbering. Compatibility cannot be guaranteed between
field index numbers for different Coral Software versions.
2-8
Direct Access Abbreviations (DAA)

Certain branches and options can be directly accessed from any location in the PI
tree. The entire list of these abbreviations (or mnemonics) can be displayed by
either entering HELP or typing 10 on the main menu. Since HELP is also a Direct
Access Abbreviation (DAA), typing the letters HELP anywhere in the PI tree,
except in NAME field, will bring up the List Of Direct Access Abbreviations to the
PI Tree.
The following table presents the currently available DAA features. This list is
presented in alpha-numeric order, as opposed to the actual PI on-line list, which has
a slightly different arrangement.
Entering ROOT anywhere in the PI returns the system to the Root (Main) Menu.
Branch DAA Branch DAA BRANCH DAA

4T/8T CARD_DB TKDB GROUPS GROUP SMDR CONTROL SMDR
ALT ROUT TK.GROUP ROUT GROUP CALLS CALL Soft Keys Idle Set SKEY
BELL/UNA GROUP BELL HUNT GROUP HUNT STATION TIMERS ST.T
BOSS GROUP BOSS IP Ports KEYSET IPKEY SYSTEM GEN. SYSGEN
BUSY PORTS BUSY IST/SLT CARD_DB STDB SYS FEATURES SFE
CARD DATABASE CDB IST/SLT DEF. SLT (or IST) SYS TIME SET-UP TIME
CARD LIST CLIS LCR/ROUTING LCR TERMINAL SET-UP TERM
CLASS OF SERVICE COS LIBRARIES LIB TOLL BARRIER TOLL
COST CALCULATION COST NETWORK NET TONE PLAN TON
DATA SERVICES DATA NIGHT SERVICE NIGHT TRUNK DEFINITION TRK
8 DID CARD_DB DIDB NODES NODE TRUNK GROUP TKGP
DID/E&M TRUNK DIDG NUMBERING PLAN NPL TRUNK GROUP DEF. TGDEF
GROUP
DIGITAL BUS LIST DLIS PI MESSAGES MSG TRUNK PORTS TRUNK
DIGITAL TRUNK DTDB PICK-UP GROUP PICK TRUNK TIMER TK.T
Extension Line ELA PORT DATABASE PDB UGW Configuration UGWC
Appearance
KEYSET DEFINITION KEY PORT LIST PLIS VERIFIED FORCED VFAC
ACCOUNT CODE
or
EKT
KEYSET PROG PREFERENCE PREF Voice over IP IP
PROGRAMMING
KEYSET TIMERS EK.T WAKEUP WAKEUP
FEATURES PORTS FEAT RINGER P.S. RPS WIRELESS ST (PDB) WST
FEATURE TIMERS FE.T SIZES DEF. SIZ ZONED GROUPS VPZ
 The layout and order of the Direct Access Abbreviations shown above is
slightly different from the on-line version; this is for the sake of clarity
only.
2-9
Entering Yes/No and Remove

Entering the Yes or No answer to any option can be done in several ways, any of
which is accepted by the system:
YES NO Remove
YE N Remove
Y NON Rem
NONE R
The letters can be entered in either upper or lower case or in combination.

However, if any other letters are entered the following message appears:
SYNTAX ERR, TRY AGAIN.
General Rules for Entering Names
The following rules apply for entering names in the various PI features that require
such a definition. These naming rules are generally applicable for most options.
However, when special considerations are required these are mentioned along with
the option description.
Naming Rules
1. The number of characters allowed in names is determined according to the
option requirements.
2. Control characters are ignored and should not be used.
3. Names cannot have spaces or tab characters. Any character entered after an
inadvertent space or tab is ignored.
4. For space/blank, enter underscore: “_”.
5. Upper and lower case letters can be used in any combination. Letters are
displayed exactly as entered. In the following cases, however, the names are
displayed in Uppercase:
• Idle keyset/FlexSet displays
• Site Name
• Password
6. Direct Access Abbreviations may be used for names. While entering names,
DAA access is blocked.
7. In Semitic systems, letters appear right to left.
8. Each port/group/library has a set of two names, SHORT and FULL, which
appears on a KEYSET according to the following:
• DSP32 SHORT name
• DSP48 SHORT name or first 9 characters of full name (the selection
between Short and Full, is defined system-wide.
• DSP80 FULL name
• DSP160 FULL name
9. To remove a defined name, use R.
Entering R displays the default BLANK.
2-10
Authorization Items
Software Upgrades, new Feature Activations and increasing Feature Sizes, require
Software Authorization.
Generic software and feature activation, features sizes and software authorization
information are all included on the IMC8 or CFD flash memory card.
The Authorization set includes a serial number which must match the Software
Authorization Unit (SAU) physically installed on the following cards:
• MCB Office (Coral IPx Office right panel)
• MCP-IPx2 (Coral IPx 500 and CDRS 200E)
• MEX-IP2 (Coral FlexiCom 400 and Coral IPx 800)
• MEX-IP2 (Coral FlexiCom 5000 and Coral IPx 3000)1
• 32GC (Coral FlexiCom 6000 and Coral IPx 4000)2
A unique SAU number is assigned per system. The SAU information determines
the feature implementation capabilities or feature access authorization for a
customer.
Loading unauthorized updates will cause the system to shut down after 14 days
unless the proper authorization (SAU) is provided.
Authorization allows for up to 50 software subversion upgrades, allows increasing
the system sizes and activating specific features.
The latest software version allowed for the site is verified by the Coral prior to the
complete software installation. Attempting to install an unauthorized version, the
Coral will abort the process without overwriting the current software version.
Any attempt to exceed limited or maximum numbers, e.g. sizing, results in an error
message.
When a feature is not authorized in the system, any attempt to access that feature
results in the following message:
(feature name) is not authorized in the system.
In the following pages all options that are controlled by the authorization system
are assigned Authorization Limit or Authorization Control.
1. For the FlexiCom 5000 and Coral IPx 3000 systems with duplicated control, an identical yet sep-
arate IMC8 is required for each system side. Each IMC8 includes its own unique Software
Authorization number.
2. For the FlexiCom 6000/R and Coral IPx 4000/R systems with dual redundant control, an identi-
cal yet separate CFD is required for each system side. Each CFD includes its own unique Soft-
ware Authorization number.
2-11
2-12
3 Installation
This branch presents certain system defaults, based on the Software Authorization
Unit (SAU), at the time of initial installation. Installation parameters configure the
system logic, allocate memory, establish default system sizes and set port and
feature defaults; all according to the type of system specified.
Installation and Feature Authorization display fields are described on the following
pages:
Installation ....................................................................................................3-2
Feature Authorization ...................................................................................3-5
! Installation parameters are programmed automatically by the

manufacturer before all other parameters are programmed.
3-1
Installation PI Reference Manual
Installation ç SYSGEN,0 [0,0,0,0]
The following fields show the presently defined system type, and country of
installation. Used for display purposes only.
SYSTEM_TYPE 0..2
0 (Most Countries),
1 (Special Applications),
2 (European system);
See Table 3-1 below.
This parameter defines a set of countries or authorities with similar specifications.
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l
COUNTRY See Table 3-1 below

Determines the country in which the system is installed. “USA” includes countries
using the North American standard.
This parameter determines several defaults including display and grammar
conventions, whether central office trunks default to loop start or ground start, port
dialing default is rotary or DTMF, special timers, ring frequency (20/25Hz) for SA
cards, etc.
Table 3-1: System Type and Country of Installation
Country System Type
0 1 2
0 USA Consult Factory Netherlands
1 Israel Consult Factory Belgium
2 Mexico Consult Factory Germany

Installation SYSGEN,0 [0,0,0,0]
3 Brazil N/A Spain
4 Venezuela N/A Hungary
5 Argentina N/A Greece
6 China N/A Australia
7 Poland N/A New Zealand
8 India N/A Czech Republic
9 International-ROW N/A Italy
10 Russia N/A Caribbean Islands
See Country Codes on page 1-19.

3-2
PI Reference Manual Installation
CABINET_TYPE 0..1
0 (Coral FlexiCom 400 (with HDC controller), 5000, 6000)

1 (Coral IPx 500, 800, 3000, 4000)
1 (Coral IPx Office)
1 (CDRS 200E)
Determines the type of cabinets this Coral is housed in.
EXPANSION_TYPE 0..3 (see Table 3-2 below)

Coral IPx Office only
This parameter describes the expansion units connected to the IPx Office system.
 Notes!
• Upgrading from Version 15 sets this parameter to 0-None!
• A value of 0-None indicates that there is no expansion unit integrated in
this IPx Office system and prevents the peripheral cards in the
expansion units from initializing.
Table 3-2: IPx Office Expansion Unite Types
Entry Type Description
0 None There is no expansion unit integrated in this IPx

Office system.
1 IPx Office Identifies the expansion units attached to the

system as IPx Office/EX units
2 IPx 500X/800X Identifies the expansion units attached to the

system as being any combination of IPx 500X
and/or IPx 800X cages.
3 FlexiCom 200 Identifies the expansion units attached to the

CSLX system as being FlexiCom 200 CSLX cabinets.

Before the peripheral cards can be installed and initialized, it is necessary for the
Coral system to identify each unit or cage within the system. Therefore, this
parameter must be modified immediately after powering the system and
performing all power-up tests.
After defining the expansion unit in this parameter, the system must be
re-initialized (soft re-boot) in order to initialize the cards.
3-3
UPDATE? Yes/No
** WARNING **: System initialization will be performed **
ARE YOU SURE? is a prompt to help protect against accidentally initializing the
system. This allows backing out of the initialization procedure at the last moment.
! Entering Y initializes the system causing:

1. The system to reset.
2. All calls to be dropped.
3-4
Feature Authorization ç FEAT,1

Displays the feature implementation capabilities on feature access authorization.
DISPLAY CURRENT determines whether the feature is available.
To activate Coral Features requiring Authorization, use the FMprog utility.
FMprog is a tool for Coral dealers who install, upgrade and maintain Coral
FlexiCom systems using Flash Memory cards.
Coral System Control Card Flash Memory Card
IPx Office MCB Office IMC8 or IMC16
IPx 500 MCP-IPx2 IMC8 or IMC16

CDRS 200E
FlexiCom 400 (with HDC controller), 5000 MEX-IP2 IMC8 or IMC16

IPx 800, 3000
FlexiCom 5000 MEX-IP2 IMC8 or IMC16

IPx 3000
FlexiCom 6000 MCP-ATS CFD

IPx 4000
 When the Coral database exceeds 1.5MB requires replacing the IMC8
Flash Memory card with an IMC16 Flash Memory card.
Whenever an updated version of the Coral software is released, the upgrade is
delivered to the sites either on 3.5” diskettes, e-mail, or via other electronic media
file transfer. The upgrade is contained in a self-extracting compressed file, specific
for the site. The upgraded generic feature software and authorization must be
extracted by a PC via the FMprog utility, and then written from the PC hard disk
into the memory card.
The SAU number on the memory card must match the SAU number on the physical
Feature Authorization FEAT,1

SAU attached to the Control card.
For duplication systems (Coral IPx 3000 and FlexiCom 5000), only one SAU
number is used per side. Therefore, the SAU number on the physical SAU device
must match the SAU number on the IMC8/16 memory card for that side.
 New Coral IPx 3000 and Coral FlexiCom 5000 (0/0 systems) are supplied
with an IMC16 card.
For redundant systems (Coral IPx 4000/R and FlexiCom 6000/R), only one
SAU number is used per side. Therefore, the SAU number on the physical SAU
device must match the SAU number on the CFD memory card for that side.
For more information, see Authorization Items on page 2-11.
 Contact the manufacturer’s representative for the proper upgrade.
3-5
0 - DISPLAY Displays the current authorization set, limitations and feature capabilities.
CURRENT (see Table 3-3 below)
1 - DISPLAY NEW Not used.

(DISKETTE) l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l
In the following
table:
RANGE The maximum RANGE* depends on the authorization file in the

IMC8/IMC16/CFD memory card for the particular system.
The number presented is the maximum for the largest Coral system.
XXXX indicates that the limit is equivalent to the number of PORTS.
FEATURE The following FEATURE parameters (Ports, Stations, SLTs, SLT-IPs, Keysets,
Keysets_IP, SIP_Terminals, Wireless, Trunks, etc.) may be defined in excess of
their Authorization Limit in the Sizes Definition (page 4-2) branch (SIZ) in order to
avoid a First Init when adding stations. However, attempting to use equipment in
excess of its Authorization Limit results in the UNAUTHORIZED message and
the attempt fails.
3-6
Table 3-3: Software Authorization Items Descriptions
FEATURE RANGE DESCRIPTION
1 PORTS 6000 (max) Shows the maximum ports (stations and trunks)
336: IPx Office allowed in the system.
200: IPx 500 The total number (sum) of the following types of
ports must be less than the number of PORTS:
144: CDRS 200E
• 2-KEYSETS
• 3-SLTS
• 4-TRUNKS
• 5-FlexSets
• 6-KEYSETS_IP
• 7-T2xxM
• 8-FLIPS (SOFTPHONE)
• 9-SENTINEL
• 10-SLT_IP
• 11-LGS_IP
• 12-NET_IP
• 13-SIP TERMINAL
• 14-TADIRAN SIP TERM (former T2xxS)
 The total number of

• 15-SIP TRUNK
KEYSETS_IP, T2xxM, FLIPS

(SOFTPHONE), SENTINEL, SLT_IP, LGS_IP, NET_IP, SIP
TERMINAL, TADIRAN SIP TERM (former T2xxS) and SIP
TRUNK cannot exceed 1950.
 Max. 6000 ports -

This depends on the authorization file in the IMC/CFD flash memory
card for the particular system.

The number presented is the maximum for the largest
Coral IPx 3000, 4000 and FlexiCom 5000, 6000 systems.
3-7
2 KEYSETS XXXX (or 1-3400*) Shows the maximum number of available Coral
whichever is smaller Keyset units for this system. The total number
(sum) of the following types of keysets must be
less than the number of KEYSETS:
• FlexSet
• FlexAPDL
• APDL
• CPA
• EKT
• DKT
• DST
• GKT
• VDK
• VM keyset ports
• FlexAir Wireless handsets
• CoralAIR Wireless handsets
Therefore, for example, if you have 100 DKTs and
100 FlexSets in your system, KEYSETS would have
to be at least 200 and FlexSets (below) would have
to be at least 100.
XXXX indicates that the KEYSETS limit is equivalent
to the number of PORTS.
3 SLTS XXXX (or 1-4000*) Standard Single Line (SLT or FXS) telephones
whichever is smaller includes the following types of stations:
• Magneto (8SM and 8SMipx cards)
• Type 500
• Type 2500
10-SLT_IP is not included here and must be defined
below for SLT IP sets.
XXXX indicates that the SLTS limit is equivalent to

the number of PORTS.
3-8
4 TRUNKS XXXX (or 1-3400*) Includes the following types of trunks:

whichever is smaller • Analog trunk
• Digital trunk (30T / T1 / PRI)
• Loop Start (FXO)
• Ground Start
• E&M
• PRI (see 2DT WITH 2 CKTS on page 3-18 and PRI on page 3-20)
• BRI
• DID
11-LGS_IP is not included here and must be
defined below for LGS IP trunks.
12-NET_IP is not included here and must be
defined below for NET IP trunks.
15-SIP TRUNK is not included here and must be
defined below for SIP IP trunks.
XXXX indicates that the TRUNKS limit is equivalent
5 FlexSets XXXX (or 1-3400*) Includes the following types of Coral FlexSet
whichever is smaller models:
• Coral FlexSet 120
• Coral FlexSet 120D
• Coral FlexSet 120L
• Coral FlexSet 120S
• Coral FlexSet 280
• Coral FlexSet 280D
• Coral FlexSet 280D-Z
• Coral FlexSet 280D-HS

• Coral FlexAPDL
• iCMC (each iCMC card requires 24 entries)
The number of FlexSets must be smaller than the
number of KEYSETS.
6-KEYSETS_IP is not included here and must be
defined below for Coral FlexSet-IP 280S keysets.
7-T2xxM is not included here and must be defined
below for Coral T207M, T208M, T207M/NP,
T208M/BL keysets.
14-TADIRAN SIP TERM (former T2xxS) is not included
here and must be defined below for Coral
SeaBeam, P-335, P-450, T207S, T208S,
T207S/NP, T208S/BL, T322, T328 keysets.
XXXX indicates that the FlexSets limit is equivalent
3-9
6 KEYSETS_IP XXXX (or 10-1950) Includes the following types of IP Keyset models:
whichever is smaller • Coral FlexSet-IP 280S
• Coral Sentinel (Terminal/I/II)
7-T2xxM is not included here and must be defined
below for Coral T207M, T208M, T207M/NP,
2: IPx Office T208M/BL (MGCP IP) keysets.
14-TADIRAN SIP TERM (former T2xxS) is not included
here and must be defined below for Coral
SeaBeam, P-335, P-450, T207S, T208S,
T207S/NP, T208S/BL, T322, T328 (SIP IP)
keysets.
XXXX indicates that the KEYSETS_IP limit is
equivalent to the number of PORTS,
but the total number of KEYSETS_IP, T2xxM, FLIPS
7 T2xxM XXXX (or 2-1950) Includes the following types of Coral MGCP IP
whichever is smaller Keyset models:
• Coral T207M
• Coral T208M
• Coral T207M/NP
• Coral T208M/BL
XXXX indicates that the T2xxM limit is equivalent to
the number of PORTS,
XXXX (or 2-1950)

8 FLIPS Includes the following types of Softsets:

(SOFTPHONE) whichever is smaller • Coral FlexIP SoftPhones
XXXX indicates that the FLIPS (SOFTPHONE)s limit is
14-TADIRAN SIP TERM (former T2xxS) (below) must be
defined for Coral SeaBeam softphones.
3-10
9 SENTINEL XXXX (or 1-1950) Displays the maximum number of

whichever is smaller • Sentinel Pro (10/25/75/150) units
that are authorized for use with this Coral system.
XXXX indicates that the SENTINELs limit is
equivalent to the number of PORTS.
Each Sentinel Pro unit needs one IP port.
10 SLT_IP XXXX (or 0-1950) Includes all Type 500 or Type 2500 standard
whichever is smaller Single Line Telephones (SLTs) connected via
Third Party MGCP gateways, Coral Teleport/FXS
MGCP gateways units to the Coral IP Network.
XXXX indicates that the SLT_IP limit is equivalent
to the number of PORTS,
11 LGS_IP XXXX (or 0-1950) Includes all CO analog trunks (loop start and
whichever is smaller ground start) connected via Third Party MGCP
gateways, Coral Teleport/FXO MGCP gateways to
the Coral IP network.
XXXX indicates that the LGS_IP limit is equivalent
12 NET_IP XXXX (or 0-1950) Includes all Coral IP QSIG Network connections
whichever is smaller for this Coral system via PUGW, UGW and
UGW-E cards.

41-NETWORKING (below) must be set to YES in
order to use IP QSIG in the system.
XXXX indicates that the NET_IP limit is equivalent
3-11
13 SIP TERMINAL XXXX (or 0-1950) Includes several third-party SIP terminals
whichever is smaller (of the shelf), such as:
• Third-party SIP PC-SoftPhones
• Third-party SIP IP-Phones
• Third-party FXS SIP gateways
• SLT/IST stations (behind Coral Teleport/FXS SIP gateway)
• Third-party SIP Voicemail
• LxCMC (Repartee LX) Unified Messaging
 SeaMail and LxCMC systems require:

• SeaMail (T3) Unified Messaging
• One license for each SIP voicemail port

• One license for MWI operation.
Example:
Enter 5 licenses for SeaMail or LxCMC with 4 voice ports
 SeaMail on PC versus SeaMail on IPx

Office:
• Can go higher then 8 ports.
• Does not use the SeaMail Controller. The
technician can browse directly to it for
administration.
10-SLT_IP (above) is not included here and must
be defined for SLT Type 500 or Type 2500
standard Single Line Telephones (SLTs) connected
via Third Party MGCP gateways.
14-TADIRAN SIP TERM (former T2xxS) (below) is not
included here and must be defined for
Coral SeaBeam, P-335, P-450, T207S, T208S,

T207S/NP, T208S/BL, T322, T328 (SIP)
terminals.
24-SIP VOICE MAIL (below) must be defined for
Coral SeaMail ports and LxCMC.
XXXX indicates that the SIP TERMINALs limit is
• Contact the Coral manufacturer's representative
for the approved list of tested third-party
equipment and along with their test data.
3-12
14 TADIRAN SIP XXXX Includes the following types of Tadiran SIP

TERM (or 0..2-1950) terminals:
whichever is smaller • Coral P-335 (that start with MAC address 000a6b)
(former T2xxS)
• Coral P-450 (that start with MAC address 000a6b)
• Coral T207S
• Coral T208S
• Coral T207S/NP
• Coral T208S/BL
• Coral T322
• Coral T328
XXXX indicates that the TADIRAN SIP TERM
(former T2xxS) limit is equivalent to the number of
PORTS,
 NOTE
• P-335 and P-450 are Tadiran branded
Polycom SIP Terminals.
• T322 and T328 are Tadiran branded
Yealink SIP Terminals.
• T207S, T208S, T207S/NP and T208S/BL
are Tadiran branded Tecom SIP Terminals.
• A branded SIP terminal has the Tadiran
Logo and is equipped with a Tadiran MAC
address. This SIP terminal requires the

“TADIRAN SIP TERM” license.
• A non-branded Polycom/Yealink/Tecom
SIP Terminal does not have the Tadiran
logo and is equipped with a
Polycom/Yealink/Tecom MAC address.
This SIP terminal requires the SIP
TERMINAL license.
3-13
15 SIP TRUNK XXXX (or 0-1950) Displays the maximum number of SIP trunks (from
whichever is smaller a public service provider or behind FXO/BRI/PRI
SIP gateways) that are authorized for use in this
 In Coral versions 15.85.34 or lower:

Coral system.
41-NETWORKING (below) must be set to YES

in order to use SIP trunks in the system.
XXXX indicates that the SIP TRUNKs limit is
16 MEDIA_CHAN. XXXX (or 0-3400*) Defines the maximum number of Media Channels
whichever is smaller supported throughout this Coral system:
• MG
• MRC
This number should not exceed the number
defined in IP_MEDIA_CHANNELS (page 4-28) (Sizes
Tab branch (SYSGEN,2)).
3-14
17 APA XXXX (or 1-3400*) Includes the following types of APA and iAPA ports
whichever is smaller allowed throughout this Coral system.
iAPA (IP) may be installed for these units:
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
• DKT 1000 series
• DKT 2000 series
• FlexSet 120, 120D, 120L, 120S, 121S
• FlexSet 280, 280D, 280D-Z, 280S, 281S
APA (Serial RS-232) may be installed on these

units:
• FlexSet 280S with APA-F, PEX/APA-F or PEX/APA-FS
• FlexSet 281S with PEX/APA-FS
• FlexSet 280 with PEX/APA-FS
• FlexSet 280D with PEX/APA-FS
• FlexSet 280D-Z with PEX/APA-FS
• FlexAPDL (issue 9 and below) with APA-F
• FlexAPDL (issue 10 and higher) with APDL-FS
• FlexSet 80S (GKT 4320)
• FlexSet 80P (GKT 4321)
• DKT 2322
• DKT 2000 Series with APA
• DKT APDL
XXXX indicates that the APA limit is equivalent to
the number of PORTS.
Note:
More than 100 APA units may be installed and
work simultaneously when CAP_MSG_DESTINATION

[43] (page 6-31) in Station Options (SFE,2) is set to
Specific enabling a Primary and Secondary
Busy/Idle message destination.
18 DAYS 0 Feature Time Limitation: For Future Use
3-15
19 URC DTMF 8/XXXX DTMF receivers applicable for:

• Coral IPx 500 systems with MSBipx Hardware
Issue-0200X1000 or higher
• Coral IPx Office systems with MRC (software
version 7 or higher)
• Coral IPx Office systems with
U-RMI Office or U-MR Office cards
• Coral systems (version 15 or higher) with MRC
(software version 7 or higher) on PUGW or
PUGWipx cards
• CDRS 200E
Defines the maximum number of URC (and MRC)
DTMF Receiver (DTR) resources authorized for
this Coral system, see URC-Card (IPx Office,
IPx 500 and CDRS 200E) beginning on page 4-33.
XXXX indicates that the URC DTMF limit is
equivalent to a maximum based on the URC
configuration (0....24) and on the MRC type.
20 URC CLID 0/XXXX FSK (Frequency Shift Keying) tone transmitters for
displaying Caller ID (CLID) on SLT phones,
applicable for:
• Coral IPx Office systems with U-RMI Office or
U-MR Office cards
• CDRS 200E
Defines the maximum number of URC CLID
(Caller ID) iDSP resources authorized for this

Coral system, see URC-Card (IPx Office, IPx 500
and CDRS 200E) beginning on page 4-33.
XXXX indicates that the URC CLID limit is
configuration (0..16..32).
See 48-CALLER ID below.

See 58-SLT-CID below.
3-16
21 URC 3WAY 6/XXXX 3-WAY circuits, applicable for:

• Coral IPx Office systems withU-RMI Office or
U-MR Office cards
• CDRS 200E
Defines the maximum number of URC 3-WAY
conference resources authorized for this Coral
system, see URC-Card (IPx Office, IPx 500 and
CDRS 200E) beginning on page 4-33.
XXXX indicates that the URC 3WAY limit is
22 URC CONF 1/XXXX Multi party conference circuits, applicable for:

• Coral IPx Office systems with U-RMI Office or
U-MR Office cards
• CDRS 200E
Defines the maximum number of URC CONF
(meet-me conference bridge) resources authorized
for this Coral system, see URC-Card (IPx Office,
IPx 500 and CDRS 200E) beginning on page 4-33.
XXXX indicates that the URC CONF limit is
23 URC MFR 0/NA MFC-R2 receivers, applicable for:

• Coral IPx Office systems with MRC modules
(version 7 or higher)
• Coral systems (version 15 or higher) with MRC
modules (version 7 or higher) on PUGW or
PUGWipx cards
Defines the maximum number of MRC MFR
(MFC-R2 Receiver) resources authorized for this
Coral system.
XXXX indicates that the URC MFR limit is equivalent
to a maximum based on the MRC type.
3-17
24 SIP VOICE MAIL 0/XXXX Defines the maximum number of SIP ports
dedicated for Voicemail.
Includes the following types of SIP Voicemail port
connections:
• Third-party Voicemail
• LxCMC (Repartee LX) Unified Messaging
 SeaMail and LxCMC systems require:

• SeaMail (T3) Unified Messaging
• One license for each SIP voicemail port

• One license for MWI operation.
Example:
 SeaMail on PC versus SeaMail on IPx

Office:
• Can go higher then 8 ports.
• Does not use the SeaMail Controller. The
technician can browse directly to it for
administration.
XXXX indicates that the SIP VOICE MAIL limit is
equivalent to the number of SIP TERMINAL.
25 2DT WITH 2 Number of 2DT Defines the maximum number of 2DT cards with
 24 or 30 trunks per circuit,

CKTS cards in the system two circuits to function.
maximum 2 circuits per 2DT card

3-18
26 CLA_XML_ 0-1000  NOTE: Check availability.

MONITORS Authorizes the maximum number of CoraLINK
application monitors that work with XML protocol
 Each "OCS client seat" (user) needs one

(like OCS seats).
monitor.
The integration of Coral systems and Microsoft Office
Communications Server (OCS) 2007 present enterprise users
with a solution that consists of a real-time multimedia
communication system with web conferencing (sharing data,
audio, and video), instant messaging, and audio/video
conversations.
Microsoft OCS and Exchange Server 2007 Unified Messaging
(UM) work together to provide users with Outlook Voice
Access. This makes email messages and voice messages
accessible from Outlook both locally or over the phone via an
access number assigned by the Exchange UM administrator.
Coral in conjunction with the Communicator 2007 client,
provides users with an easy way to communicate with users
from other locations using a wide range of communication
options.
27 ROUTING YES/NO When set to Yes, enables Routing Access and

Cost Calculation features.
See Routing & Cost Calculation (page 15-1).
28 DATA FEATURES NO Not Applicable
29 SMDR BACKUP YES/NO This parameter is only relevant when SMDR data
is transmitted through a predetermined RS-232
port (RMI, 8DRCM, 8DRCM-2, 8DRCF, or MSBipx
card) and when SMDR_DEST [14] (page 14-6) is set to

1-24.
Provides the system with a memory buffer for
storage of SMDR on-line records whenever the
printer or log device are unable to accept records
from the Coral RS-232 serial port.
See Chapter 14 SMDR (page 14-1)
10. When Coral system includes a MAP
application, and SMDR_DEST [14] (page 14-6) is
set to “99” (configured via IP port), then the
SMDR backup memory is automatically
provided by the MAP, even when the SMDR
BACKUP feature is not authorized.
In this case the SMDR_BACKUP on page 4-16
can be reduced to 0. Therefore the Coral
system memory allocated for this feature can
can be released for other resources.
3-19
30 2nd LANGUAGE YES/NO Defines the other languages that may be used by
the KEYSET displays.
31 3rd LANGUAGE YES/NO
32 4th LANGUAGE YES/NO
33 VFAC YES/NO: Coral Defines VFAC feature for outgoing calls.
34 PRI YES/NO Enables PRI operation, when set to Yes.

Requires one of the following cards to be installed
in the system:
• 2DT (PRI-23/30), see 2DT WITH 2 CKTS on page 3-18
• IPG
• PRI-23
• PRI-30
(includes: ipx, Office and sl cards).
27-ROUTING (above) must be set in order to use
PRI and IPG in the system.
35 ACD YES/NO Defines the ACD Hunt Group type features. When
the authorization is not present, only UCD groups
are available.
36 HOTEL/MOTEL YES/NO Determines whether the following features are

accessible when set to Yes:
• Room Status
• Check In/out
• Wakeup
• Call Charge
NOTE: This feature is mutually exclusive with the
65 - CANNED MESSAGE feature. Therefore, using
this feature preempts the use of CANNED MESSAGE
in the same Coral system.
37 CAP YES/NO Enables a Computerized Attendant Position (CAP).

(CSTS Protocol) When Authorization is not present, only PCC is
available.
CSTS (Coral Supported Telephony Services)
38 Traffic (CVT) YES/NO Enables the installation of the Traffic Application

Package: CoralVIEW Traffic (CVT).
3-20
39 TBR YES/NO Enables BRI operation, when set to Yes.

Requires one of the following cards to be installed
in the system:
• 4TBR
• 4TBRP
• 8TBR
• 8TBRP
(includes: ipx, Office, sl) cards.
40 CoraLINK YES/NO: Coral Enables the following cards to activate the

CoraLINK operation when set to Yes:
• MAP
• CoraLINK in IPx Office via embedded MAP
• CLA-ATS
• F-CLA 686 (10/100Base-T via RJ-45)
• CLA 486 (10Base-T via RJ-45)
• CLA 386 (10Base-2 via Coax) [this type is discontinued]
These cards are used in order to operate the
CoraLINK feature for CTI, COMPOSIT and FlexCT
applications.
 NOTE: When Coral IPx 4000 and

Coral FlexiCom 6000 systems include
CoraLINK authorization and a 4/8XMM
daughterboard, then 2MB of the 4/8XMM
memory is allocated for the CoraLINK
application, even when a CLA-ATS card is
not installed.

41 NETWORKING YES/NO Enables ISDNet Setup and IP QSIG.
NET_IP and QSIG trunk calls are enabled only
with Networking Authorization.
12-NET_IP (above) must be defined in order to use
IP QSIG networking via PUGW, UGW or UGW-E
cards.
42 HSB YES/NO/NA This parameter is relevant for Coral IPx 4000 and
Coral FlexiCom 6000 systems only.
Enables the following systems operation with Dual
Common Control:
• Coral IPx 4000/R
• Coral FlexiCom 6000/R
3-21
43 FlexAIR SKK YES/NO Enables installation of the following SKK (FlexAIR)

or SKW (CoralAIR) cards, thus providing service
for wireless telephones.
• 16SKK
• 8SKK
• 8SKKipx
• 2SKW
• 4SKW
• 2SKWsl
• 4SKWsl
44 4VS NO YES/NO/NA Decides whether the Coral sends an answer signal

ANSWER to the CO upon receiving incoming calls from the
CO depending on whether the call was answered
by a System Message (see WITH_ANSWER [2] on
page 23-3).
45 CONF YES/NO on the following cards:

• 8DRCM-2
• 8DRCF
• 8DRCM
• CNF
• Coral IPx 500
• CDRS 200E
• U-MR Office
• U-RMI Office
Also enables the conversion of a CNF card from
an 8 port 3-Way Conference Card (max: 8
simultaneous calls of 3 members) to a 2 port
Conference Card (max: 2 simultaneous calls of 15
members).
46 ST.-V.M. YES/NO Allows the incorporation of Voicemail on FXS

station ports.
47 CALL TRACE YES/NO Malicious Call Trace allows the Called Party or an
Attendant to compile a list of all incoming calls to
the “Called” station. The Attendant can compile a
list for more than one station.
3-22
48 CALLER ID YES/NO Enables the identification of the calling party’s

number (CID) over Loop-Start analog trunks
provided by the following cards:
• 4/8TPF with external CID trunk box
• 4/8T-CID
• 4/8T-CIDipx
• 4/8T-CID Office
See 20-URC CLID above.
See 58-SLT-CID below.
49 SL SAU YES/NO/NA  This parameter is relevant for CDRS 200 and

CONTROL Coral FlexiCom 200 (version 14 or lower)
systems only.
Describes whether a Software Authorization Unit
(SAU) is required for the following systems:
• Coral FlexiCom 200
• CDRS 200
50 HIGHEST nn.xx Describes the highest software version upgrade

VERSION possible. Where nn is the software Version
number and xx is the version upgrade.
The highest software version for V. 16 is 16.49.
Trying to load a higher version than authorized
causes the A message on the seven segment
display on the front panel of the controller card
and results in the following message:
Unauthorized Version, CORAL will shut
down soon.

Your version is mm.xx, Highest
authorized version is nn.xx
The Coral will shut down after 14 days if proper
authorization is not established.
51 E911 YES/NO When set to Yes, the system enables MF tone

transmission via specific trunks to public and local
(Emergency emergency centers using E911 protocols. This
feature also allows E911 program activation over
Calls) PRI trunks.
52 SPLIT MONITOR YES/NO When set to Yes, the system enables the
authorized user to silent monitor only one party of
a conversation at a time.
Default feature code: #1448
3-23
53 CVA YES/NO When set to Yes, this parameter enables access to

the Coral View Administrator (CVA) Application.
The CVA is mostly used by entry-level operators
and supervisors.
54 CVD YES/NO When set to Yes, this parameter enables access to

the Coral View Designer (CVD) Application.
55 CVD_PRO. YES/NO When set to Yes, this parameter enables access to

the Coral View Designer Pro. Application.
56 AUTO SET YES/NO When set to Yes, the Auto Set Relocate
RELOCT. (Portability) feature enables swapping telephone
profiles.
57 FlexiCall YES/NO Determines accessibility of the FlexiCall feature.

When set to Yes, enables designating any non-
Coral system phone as an additional station
destination thus ringing both Coral and non-Coral
phone simultaneously as well as enabling certain
Coral features at the non-Coral phone.
58 SLT-CID YES/NO Affords Caller ID information for FXS/SLT stations

equipped with a display or external box display.
Requires FSK compatible CID display unit for
FXS/SLT.
• The feature requires a 8/16/24SLS (software
version 3 or higher) or 8/24SA peripheral card and
iDSP card.
• In the Coral IPx Office systems the feature
requires a U-RMI Office or U-MR Office card.
• In the IPx 500 systems the feature requires an

MSBipx Hardware Issue-0200X1000 or higher.
• In the CDRS 200E systems the feature is
embedded.
See 20-URC CLID above.
See 48-CALLER ID above.
59 DIRECTORY YES/NO Enables creating a public and personal directory

via the Coral database port Names.
Default feature code: #1994
3-24
60 Freedom YES/NO Enables using non Coral telephones as virtual

Coral stations thereby affording these external (off
premises) telephones the vast array of Coral
services.
The Freedom feature is also known as IRSS.
61 FlexAIR SMS YES/NO For FlexAir systems:

Enables sending Coral SMS messages to/from the
Coral’s FlexAir Portable (handset) units.
62 SILENT YES/NO Enables the Silent Monitor feature.

MONITOR Corresponding default feature code:
• #1981 Silent Monitor (2-Way)
• #1448 Silent Monitor (Split 1-Way)
63 MLPP YES/NO Multi Level Priority and Preemption allows the

ranked user to prioritize calls on a per call basis.
64 MUSIC YES/NO When set to Yes, enables defining a music source

DIALTONE instead of Dial Tone for Coral stations.
See DIAL_TONE MESSAGE SOURCE [78] (page 7-23) in
COS,0 to define the music source to be used.
65 CANNED YES/NO Predefined, “canned”, text messages are displayed

MESSAGE on the calling party’s keyset until the call is
answered. The text messages may be used to
define the called party’s status (Out to Lunch, In
Meeting Room 6, etc.).
NOTE: This feature is mutually exclusive with the

Room Status 36 - HOTEL/MOTEL feature. Therefore,
using this feature preempts the use of the
HOTEL/MOTEL feature in the same Coral system.
66 Not in use NO Not used
67 CFM YES/NO Authorizes the system to send diagnostic and

alarms messages to the Coral Fault Manager
(CFM) application.
68 INTERNAL YES/NO This parameter must be set to Yes to enable the

TRAFFIC Coral system to produce internal traffic reports.
See Coral Traffic Report (CTR) on page 30-1.
69 IPx Office YES/NO Determines whether this Coral system is a

Coral IPx Office system.
3-25
70 Not in use NO Not used

* This depends on the authorization file in the IMC8/IMC16/CFD memory card for the particular system. The number
presented is the maximum for the largest Coral system.
3-26
4 Sizes/URC/Music/Units Definition
This chapter defines the system size parameters. In order to allocate the memory
resources efficiently, the SIZE topics are divided as follows:
Sizes Definition ............................................................................................4-2
Sizes Tab.....................................................................................................4-24
URC-Card (IPx Office, IPx 500 and CDRS 200E) ...................................4-33
URC-Default Configuration................................................................ 4-35
URC-Current Configuration ............................................................... 4-37
URC-Card Database............................................................................ 4-40
System Engineering Options ......................................................................4-41
Music Sources.............................................................................................4-44
Units............................................................................................................4-47
 Sizes Definition and Sizes Tabulation relate to the parameter sizes, updating,
displaying and tabulating the parameter sizes based on the different types of
keysets and system ports available.
 System General Speed Calls (Not Used).
 Universal Resources Card (URC) branch allows updating the Card

Configuration for the URC card system-wide.
 Music Sources defines the music source set-up for the system and for
individual keyset users. Up to four different music sources are available.
 Units describes the number of time slots used system-wide as well as allows
the user to know which PB card and Power Supplies exist and on which system
shelf.
4-1
Sizes/URC/Music/Units Definition PI Reference Manual
Sizes Definition ç SIZ [0,0,0,1]
Sizes Definition is used to set the system size parameters. Sizes must be
programmed before all other parameters.
! Changing the “Size Def” parameters causes:

1. The system database (excluding installation, size table and the
MAX_DVMS_MSG field in SFE messaging) to return to its default
values.
3. The interruption of all calls.
4. All keyset (FlexSet 120S, 280S, 121S, 281S
and T207M, T208M, T207M/NP, T208M/BL)
call logs will be cleared.
Size parameters allocate the Coral memory resources efficiently for a particular
installation. Modifying the size table utilizes unused memory space for active
features.
The maximum size allowed per parameter is listed in parenthesis on the terminal
screen. The listings in this manual may differ from actual maximums usually
indicating a recommended maximum.
 Note:
Sizes may be defined in excess of their corresponding authorization limit
in order to enable system growth without the need for a First Initialization
procedure (i.e. returning all Sizes to their system defaults).
CURRENT_Config  Default/Modified
 To return to the DEFAULT configuration, First Initialization must be
Sizes Definition SIZ [0,0,0,1]
performed, see First Initialization beginning on page 21-3.

Shows whether or not a change was made in SIZE. If a change was made, the word
MODIFIED is shown. If no change was made, then the word DEFAULT appears.
SYSTEM TYPE,  See SYSTEM_TYPE and COUNTRY on page 3-2

COUNTRY
Shows the recently defined system type and country of the system.
4-2
PI Reference Manual Sizes/URC/Music/Units Definition
CURRENT MEMORY 
SIZE INFORMATION
Displays the memory details for the current database and Coral Software version.
The information is accurate and can be used for relevant calculations, such as
increasing or decreasing the database sizes.
xxxxxx BYTES USED BY DATABASE, AUTO BACKUP AVAILABLE
xxxxxx BYTES USED BY RAM
 For systems where Auto backup has not been defined, then the first
xxxxxx BYTES LEFT IN MEMORY
message would be displayed as follows:

xxxxxx BYTES USED BY DATABASE, AUTO BACKUP NOT AVAILABLE.
then, the database memory stores have been exceeded. The technician should try to
reduce the values of less important table parameters to free memory for the recent
updates. If this is not possible, additional memory cards (see table below) should
be purchased. The technician can also try to perform a manual backup depending
on the database size.
Coral system type Memory card type Capacity
IPx Office DBM-2/4/8 2, 4 or 8 MB
FlexiCom 400 (with HDC controller), 5000 DBX (discontinued) 1 MB

IPx 500, 800, 3000 DBM-2/4/8 2, 4 or 8 MB
CDRS 200E
FlexiCom 6000 4XMM or 8XMM 4 or 8 MB

IPx 4000
4-3
DISPLAY Pending_ P (Preserve Changes) / No (Previous Changes Not Saved)

Changes?
This field is only relevant after making changes in the features listed in the
following fields, and after entering No for the UPDATE field at the end of the table
(i.e., for system changes that are still pending and have not been saved).
Modifications of Size Definition are written to the backed-up RAM when the
system is updated. If an update is not performed the system remains at its previous
values and the changes are stored in a temporary memory.
To restore the pending changes, enter P. Pressing any other key causes the pending
changes to be erased upon system initialization.
! IMPORTANT!
The sizes listed in this database are established by program default and
can be changed.
The sizes are, however, ultimately limited by the SAU.
Changes may affect other sizes or operational relationships within the
system.
Max Ports  6000

Shows the maximum stations and trunk capacity.
The number of Maximum Stations and Max Trunks cannot be changed. The total
number of current STATIONS and TRUNKS cannot exceed the Max Ports value.
 Max. 6000 ports -

This number is limited by the authorization file in the IMC/CFD flash
memory card for the particular system. The number presented is the
maximum for the largest Coral IPx 3000, 4000 and FlexiCom 5000, 6000
systems.
4-4
STATIONS:
Maximum Stations  6000 - Defined automatically by System Type
Shows the maximum station capacity for all FlexSet, IP Keyset, SLT, EKT, DKT,
DST, GKT, and Wireless stations. The maximum number of stations cannot be
changed.
 Notes:
• The total number of SLT, SLT_IP, KEYSETS 1, KEYSETS 2, KEYSETS 3,
KEYSETS_IP, SIP_TERMINAL and WIRELESS cannot exceed Maximum
Stations.
• The total number of current SLTs, KEYSETs and TRUNKs cannot
exceed the Max Ports value.
Max SLTs 4000

Shows the maximum number of Single Line Telephone ports that may be defined
for this Coral system.
 The total number of SLT and SLT_IP ports cannot exceed Max SLTs.
SLT 4..16..4000
Defines the current capacity for Magneto and Type 500 or Type 2500 standard
Single Line Telephones (SLTs) connected via the SLT station cards:
• Full size: 8SM, 8/24SA, 8/16/24SLS, or 4/8/16SH card
• IPx 500 and CDRS 200E: 8SMipx, 8/16/24SAipx or 8/16SLSipx card
• IPx Office: 4/8/16/24SA Office, 4/8/20S Office, 4SA+8Fx Office,

4SA+16Fx Office, 8SA+8Fx Office or 8SA+16Fx Office card
SLT_IP 0..8..1950
 Default= 0 when upgrading from non-IP systems.

The total number of SLT_IP, KEYSETS_IP, SIP_TERMINAL, LGS_IP, NET_IP
and SIP_TRUNK cannot exceed 1950.
Defines the current capacity for Type 500 or Type 2500 standard Single Line
Telephones (SLTs) connected via Coral Teleport/FXS MGCP gateways.
These units require PUGW, PUGWipx, UGW-E, UGW-Eipx, UGW or UGWipx
card support, see UGW (Universal Gate Way) beginning on page 29-7.
4-5
Max Keysets  3400

Shows the maximum keyset capacity for all FlexSet, Wireless, EKT, DST, DKT
and GKT units.
Contact your dealer to change the maximum number of keysets.
• The total number of KEYSETS 1, KEYSETS 2, KEYSETS 3, KEYSETS_IP,
SIP_TERMINAL and WIRELESS cannot exceed Max Keysets.
• The total number of current SLT, KEYSETS and TRUNKS cannot
KEYSETS 1 0..3400
Shows the current keyset capacity for the following sets:
• FlexSet 120/120D/120D-Z/120L/120S/121S
• DKT21XX, DKT1XXX
• DST
• CPA
• EKT1XX
• VDK121
• iVMFipx, IPC/SFC and uCMC card ports are also allocated by this parameter
KEYSETS 2 0..3400
• EKT2XX
• VDK221
KEYSETS 3 0..16..3400
• FlexSet 280/280D/280D-Z/280D-HS/280S/281S (also with PEX or APA)
• FlexSet 80S/80P (GKT)
• DKT23XX
• EKT3XX
• VDK321
• FKT
• APDL
• iCMC (each iCMC card requires 24 KEYSET1 allocations)
4-6
KEYSETS_IP 0..60..1950

Shows the system wide current keyset capacity for Internet Protocol (IP) keysets
such as:
• Coral T207M, T208M, T207M/NP, T208M/BL
• Coral FlexSet-IP 280S
• Coral FlexIP SoftPhone (FLIPS)
• Coral Sentinel Pro (10/25/75/150)
• Coral Sentinel Terminal/I/II
These units require PUGW, PUGWipx, UGW-E, UGW-Eipx, UGW or UGWipx
4-7
SIP_TERMINAL 0..60..1950

Shows the maximum number of SIP Terminals that can be defined for this system,
such as:
• Coral P-335, P-450 (that start with MAC address 000a6b)
• Coral T207S, T208S, T207S/NP, T208S/BL
• Coral T322, T328
• Third-party SIP PC-softphones
that have been approved by Tadiran for use with the Coral system
• Third-party SIP IP-phones
• Third-party SIP voicemail
• LxCMC requires one entry for each voicemail port, plus one port for MWI
Example:
Enter 5 for LxCMC with 4 voice ports
• SeaMail requires one entry for each voicemail port, plus one port for MWI
(SeaMail on PC can go higher than 8 voicemail ports)
Example:
Enter 5 licenses for SeaMail with 4 voice ports (SeaMail on IPx Office and on PC)
Enter 9 licenses for SeaMail with 8 voice ports (SeaMail on IPx Office and on PC)
 Contact the Coral manufacturer's representative for the approved list of

Enter 13 licenses for SeaMail with 12 voice ports (SeaMail on PC)
tested third-party equipment and along with their test data. Authorized
partners can view the list by accessing the interoperability.aspx file under
the partners section of the manufacturer's website at
http://www.tadirantele.com.
These units require PUGW or PUGWipx card support, see UGW (Universal Gate
Way) beginning on page 29-7.
4-8
WIRELESS 0..50..3400
Shows the current capacity for portable handsets, such as:
• CoralAIR handsets
• FlexAir handsets
TRUNKS:
Max Trunks  Defined automatically by Coral System Type
3400: FlexiCom 6000 or IPx 4000
1500: All other systems
Shows the maximum trunk capacity for all PRI, TBR, LGS, LGS IP, NET IP, E&M
and DID trunks. The maximum number of trunks cannot be changed.
 Notes:
• The total number of LGS, E&M, DID, PRI, TBR, LGS_IP, NET_IP and SIP_
TRUNK cannot exceed the Max Trunks value.
• The total number of current SLT, KEYSETS and TRUNKS cannot
LGS 0..8..Max (Defined by Max Trunks above)

Shows the current CO loop and ground start trunk capacity for the following card
types: 4T, 4T-C, 4T-CID, 8T, 8T-C, 8T-CID, 4TMR, 4TPF, 8TPF, 4TWL,
T1-LS/GS, 30T-DOD, 30TE-NONDID, GID, ALS70-LS/DID/NONDID.
E&M 0..4..Max (Defined by Max Trunks above)

Shows the current E&M trunk capacity for the following card types:
4TEM, 4TEMP, T1-E&M, 30T-E&M.
DID 0..8..Max (Defined by Max Trunks above)

Shows the current Direct Inward Dial (DID) trunk capacity for the following card
types: 8DID, 30T-DID, 8BID.
4-9
PRI 0..Max (Defined by Max Trunks above)1

Shows the current max number of PRI or B-channel ports for ISDN. This
parameter affects the maximum IPG and PRI-23/30 cards on PRI channels that can
be installed (see ISDN Card Signaling: Signaling Channel beginning on page
26-12).
• Enter 24 for each PRI-23, 2DT(PRI-23) or UDT(PRI-23) card.
Each PRI-23 requires 24 allocations. The card provides 23 B channels plus one
D channel that also needs to be allocated.
• Enter 32 for each PRI-30, 2DT(PRI-30) or IPG card.
Each PRI-30 requires 32 allocations. The card provides 30 B channels plus two
D channel that also needs to be allocated.
TBR 0..Max (Defined by Max Trunks above)1

Shows the current Basic Rate Interface (BRI) Trunk circuits for ISDN, or the
number of B channels. This parameter affects the maximum 4TBR and 8TBR cards
that can be installed for defining BRI channels (see ISDN Card Signaling:
Signaling Channel beginning on page 26-12).
• Enter 8 for each 4TBR or 4TBRP card.
• Enter 16 for each 8TBR or 8TBRP card.
LGS_IP 0..8..Max (Defined by Max Trunks or 1950, whichever is less)

Shows the maximum capacity of CO analog trunks (loop start and ground start)
connected via Coral Teleport/FXO MGCP gateways to the Coral IP network.

These trunks require PUGW, PUGWipx, UGW-E, UGW-Eipx, UGW or UGWipx
1. The maximum number of D-Signalling channels for PRI and BRI (TBR) trunks combined
may not exceed 254.
Every two BRI ports provide one D-channel, every 24 PRI-23 ports provide one D-channel
and every 30 PRI-30 or IPG ports provide two D-channels.
4-10
NET_IP 0..Max (Defined by Max Trunks or 1950, whichever is less)

Shows the maximum capacity of Coral IP QSIG Network ports.
These ports require PUGW, PUGWipx, UGW-E, UGW-Eipx, UGW or UGWipx
SIP_TRUNK 0..Max (Defined by Max Trunks or 1950, whichever is less)

Shows the maximum number of SIP trunks (from a public service provider or
behind FXO/BRI/PRI SIP gateways) that can be defined for this system.
These trunks require PUGW or PUGWipx card support, see UGW (Universal Gate
Way) beginning on page 29-7.
4-11
LIBRARIES:
Maximum Libraries  14096, Defined automatically by System type
Shows the maximum number of PRIVATE and PUBLIC libraries. The maximum
number of libraries cannot be changed.
The total number of PRIVATE and PUBLIC Libraries cannot exceed the maximum
value listed here.
PRIVATE 0..500..10000
Shows the current capacity for station related private speed call numbers on Coral
Main Database Storage.
PUBLIC 0..500..4096
Shows the current capacity of the system public libraries.
When LARGE_PUB Library (below) is used, it is advisable to reduce PUBLIC
capacity to the minimum required.
LARGE_PUB 0..65000
Shows the current capacity of the system Large Public Libraries.
LARGE_NPL 0..1000
Shows the available number of memory units for the Large Public Library
Numbering Plan.
The values entered into LARGE_NPL define the quantity of memory units available.
They do not define the number of entries. Each entry may use more than one
memory unit. The relationship between the value entered and the number of entries
is defined by the following formula:

NUM_PLAN:
# of memory units used = (2 x # of From/To Dial# entries) + the # of (From Dial # =
To Dial #) entries.
Where:
• From/To Dial # is used when the From Dial# is different from the To Dial#.
• From Dial # =To Dial # is used when the From Dial# is equal to the To Dial#.
4-12
LARGE_PUB_DIGITS 0..MAX_DGTS_ON_TK [5] in SFE, 0

Determines the maximum number of digits available for dialing out on a trunk via
the Large_Public Lib. The number entered here cannot exceed the number defined
in MAX_DGTS_ON_TK [5] on page 6-8 (Route: SFE,0) in System Features-Outgoing
Trunks.
DIRECTORY Yes/No
Set this parameter to Yes to enable the Coral System Directory. This feature enables
the keyset user to have the names of external parties appear on the keyset display
instead of the calling number, when it exists in the directory.
A public directory is automatically created, from which a personal directory can be
derived at each user station.
 Tip: Check the system memory sizes before enabling this feature, 61 bytes
are needed per directory entry.
• Shared Directory Memory =
[Public Library+Hunt Group+Boss Group+N_Stations] x 61 bytes.
• Personal Directory Memory =
[ N_Stations x 42 bytes] + [ENTRIES PER USER x 61 bytes x N_Keysets].
• Public Library = PUBLIC (page 4-12) parameter value
• Boss Group = BOSS (page 4-14) parameter value
• Hunt Group = HUNT (page 4-14) parameter value
• N_Stations = the total number stations defined for: SLT + SLT_IP +
KEYSETS 1 + KEYSETS 2 + KEYSETS 3 + KEYSETS_IP + WIRELESS.
• N_Keysets = the total number of stations defined for: KEYSETS 1 +
KEYSETS 2 + KEYSETS 3 + KEYSETS_IP + WIRELESS

ENTRIES PER USER Range: Any number;
Default = 0
 This parameter appears only if DIRECTORY, above, is set to Yes.

Defines the maximum number of Personal Directory entries per station. Setting this
parameter to 0, disables the use of Personal Directory, system-wide.
4-13
GROUPS:
BELL/UNA 0..3..6
Shows the current capacity for Bell/Universal Night Answering (UNA) groups.
ZONE PAGE 0..10..250

Shows the current capacity for Zoned Voice Page groups.
ELA 0..3000
Shows the current capacity for ELA groups.
The number should be the number of users plus the number of departmental
groups.
MAX_ 0..1024
SIMULTANEOUS_
ELA_CALLS
 The total for MAX_SIMULTANEOUS_ELA_CALLS and BOSS cannot
exceed 1024.
Defines the maximum number of simultaneous active ELA calls and active Boss
group calls allowed for this Coral system.
BOSS 0..80..1024
 The total for MAX_SIMULTANEOUS_ELA_CALLS and BOSS cannot exceed

1024.
Shows the current capacity for Boss Groups.
PICKUP 0..60..512
Shows the current capacity for Pickup Groups.

HUNT 0..30..500
Shows the current capacity for UCD/ACD Hunt Groups.
GRP_CALL 0..250
Shows the current capacity for Conference Group calls.
MAX_ 0..Max defined in GRP_CALL

SIMULTANEOUS_ Default = 10 when GRP_CALL, above, is not 0;
GRP_CALLS For Coral upgrades, the default is CONF_CKTS (page 4-17) if GRP_CALL
is not 0.
Shows the current capacity for simultaneous GRP_CALLs (see above).
4-14
TRUNKS 0..31..250
Defines the maximum number of Trunk Groups.
PEM/DPEM/TEM 0..64..240
Shows the current capacity of the Programmable Expansion Modules:
• DPEM and PEM for DKT keysets
• FlexSet 40B for FlexSet 280/281 series
• TEM for T207M, T208M, T207M/NP, T208M/BL modules
The PEM/DPEM/TEM size must be less than, or equal to, the number of keysets.
TURRET CONSOLE 0..20..50

Shows the system-wide maximum capacity for Turret Consoles.
See TURRET Console extended DPEM [84] on page 9-69.
8DRCF/8DRCM/RMI/ 1..2..6
ASU
Shows the current capacity for U-RMI/U-MR/RMI/MR Office cards, 8DRCF,
8DRCM, 8DRCM-2, RMI or ASU cards (and MSBipx in the Coral IPx 500, or
CDRS 200E).
NUM_PLAN 0..200..32000: FlexiCom 6000

0..200..32000: IPx 4000
0..200..8000: All other systems
Shows the available number of memory units for the system Numbering Plan.
The values entered into NUM_PLAN define the quantity of memory units available.
They do not define the number of entries. Each entry may use more than one
memory unit. The relationship between the value entered and the number of entries

is defined by the following formula:
# of memory units used = (2 x # of From/To Dial# entries) + the # of (From Dial # =
To Dial #) entries.
Where:
• From/To Dial # is used when the From Dial# is different from the To Dial#.
• From Dial # =To Dial # is used when the From Dial# is equal to the To Dial#.
OFFSET_FILTER 0..4..250
Shows the current number of offset filters defined.
4-15
N_FILTER_ELEMENTS 0..32..64
PER OFFSET FILTER
Defines an identical number of elements for each offset filter used system wide.
See also Offset Filters on page 8-42.
COS 16..250
Shows the current number of Classes of Service.
SMDR_BACKUP 0..100..950
Shows the available number of records for SMDR backup buffer when SMDR data
is transmitted through a predetermined RS-232 port (RMI, 8DRCM, 8DRCM-2,
8DRCF, or MSBipx card) and when SMDR_DEST [14] (page 14-6) is set to 1-24.
 When Coral system includes a MAP application, and SMDR_DEST

[14] (page 14-6) is set to “99” (configured via IP port), then the SMDR backup
memory is automatically provided by the MAP.
In this case the SMDR_BACKUP parameter can be reduced to 0. Therefore
the Coral system memory allocated for this feature can be released for
other resources.
TBCT_SMDR 0..10,000
 This number must be defined (a number other than 0) in order to continue

the SMDR billing as if no TBCT is used.
When the TBCT feature (TBCT_TO_B_CHANNEL_TRANSFER_ALLOWED
[13] (page 28-8) in System Features, Network, SFE,11) is set to Yes, this parameter
allows the field service engineer to reserve a number of SMDR records for
continued billing of the TBCT calls even though the calls have been transferred out
of the Coral system.

4IAA_PORTS 4..32..128
Shows the current number of ports available for the 4IAA card. Each 4IAA card
requires 8 entries. Set this parameter to the total number of 4IAA cards installed
multiplied by 8.
TOLL_BAR_DIGITS_ 1..7..51
(AVG)
Defines the maximum number of digits for a Toll Barrier Element. This parameter
is linked to the next parameter, TOLL_BAR_ELEMENTS_(AVG), by the following
formula: ((Toll Bar Digits x 2) +5) x Toll Bar Elements < 32,000.
4-16
TOLL_BAR_ 0..78..1680
ELEMENTS_(AVG)
Defines the maximum number of system Toll Barrier Elements. This parameter is
linked to the previous parameter, TOLL_BAR_DIGITS_(AVG), by the following
formula:
((TOLL_BAR_DIGITS_(AVG) x 2) +5) x TOLL_BAR_ELEMENTS_(AVG) < 32,000.
CONF_CKTS 0..10..100
Shows the available number of multi-party Conference ports that can be utilized
per Coral system.
Required # of
Card Type #
Entries per Card
CNF (defined as CONF in Card List on page 2
6-59)
8DRCF 1
8DRCM, 8DRCM-2 1
U-MR Office (Coral IPx Office only) URC2 1-6*
U-RMI Office (Coral IPx Office only) URC2 1-6
*
IPx 500M main Cage (MSBipx Hardware 1-6

*
Issue-0200X1000 or higher, RMI-F/URC2)
IPx 500M main Cage (MSBipx Hardware 1
Issue-0100X1000, 8DRCF)
CDRS 200E 1-6
* For the required entry, see Meet Me on page 4-38.
DYNAMIC_CONF 0..100
 These conference ports require URC-CONF authorization.

 Dynamic Conference is not applicable in the current version.

DVMS_PORT 0..4..960
Shows the available number of DVMS ports that can be utilized (one 4VSN card
is equipped with four DVMS ports).
PAGE_Q 0..10..2000
Defines the maximum number of software identification numbers (index) that can
be assigned to the Page Queue numbering plan.
VFAC_ACCT 0..65000
Shows the available number of Account Codes that can be utilized in VFAC. The
total number is also dependent on #ACCT_DGTS in [SFE].
4-17
WAIT_QUE 0..5..128
Shows the maximum number of destinations for calls waiting for routing access.
CALL_SERVICES 0..25..N_CALLS (page 4-26) or 500 (whichever is less)

Defines the maximum number of Network and OAI Resources. CoraLINK and
ISDNet use these resources to implement such Network features as Call Transfer
and OAI features such as MakeCall or FlexiCall.
CAMP_ON 1..30..500;
FlexiCom 5000, 6000: 1..60..500
Defines the maximum number of stations that can simultaneously camp-on to busy
or unanswered network stations or Boss Groups defined as a network stations. This
feature is not relevant for external calls.
The Camp On duration is defined in Feature Timers, see CAMP_ON_DURATION [5]
on page 6-2.
 Recommendation:
For large systems, this parameter should be
set to 5% of the number of stations.
4-18
INTERNAL
TRAFFIC:
NO_OF_TRAFFIC_ 0..10..27
EVENTS_AND_
Define the maximum number of traffic events and features combined that are to be
FEATURES used in the Internal Traffic reports. A maximum of 28 traffic events and/or features
can be monitored and reviewed per report.
TOTAL_NO_OF_ 0..1..7
DAYS_TO_STORE_
Enter the maximum number of days for which the traffic data must be stored. Data
TRAFFIC can be stored for a maximum of 7 days/periods.
IP:
EXTERNAL_GW 0..2..250
Defines the maximum number of different types of Coral Teleport MP-1xx analog
VoIP gateway units allowed in this system.
Coral Teleport gateway units include the FXO and FXS external units used to
connect SLTs and LGS trunks to the Coral IP network.
ZONE 0..8..32
Defines the maximum number of IP Zones allowed for this system.
SIP:
MAXIMUM_ 0..10..20
PERSONAL_
Define a maximum length for personal passwords to be used by the P-335, P-450,
PASSWORD_LENGTH
T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam softphone,
third-party SIP terminals and SIP trunks. Relevant for the following parameters:

• SIP Terminal: PASSWORD [5] on page 29-45.
• SIP Trunk: PASSWORD [4] on page 29-56.
FOREIGN_PROXY 0..4..30
Defines the maximum number of providers that can be defined as a SIP trunk. See
SIP_TRUNK [23] under LCR,3 [ROOT,4,0,3]
4-19
NETWORKING:
NETWORK Yes/No
Defines whether this Coral system is part of a Private Network.
If Yes - a default for NET_NODES and NET_FEATURES is set.
If No - NET_NODES and NET_FEATURES are set to 0 by the system.
NET_NODES 0..10..250
 Relevant only if NETWORK (above) is set to Yes.

Shows the available number of Network Nodes.
NET_FEATURES  0..150% of the Stations

 Relevant only if NETWORK (above) is set to Yes.
Shows the current capacity for simultaneously active ISDNet features.
ISDN:
NETWORK_ 0..16..250
FACILITIES
Shows the available number of Public Network Service Facilities (NSF). For
example: MCI, SPRINT, AT&T.
NUMBER OF 0..64..10,000
ALTERNATE ID
Shows the number of Alternate Line Identification (ALI) numbers
 For Personal ELA group:

Outgoing calls from the selected handset in Personal ELA group will be
sent to the called party with the main station’s personal CID. (This
requires an ALI record to be available for each of the ELA members.)
 For the E911 feature, 2 ALI numbers are required for each station.
N_SPID_DN_PER_DSL 0..8
CC0: 2..8
 Relevant only if PROTOCOL_ID [6] (page 26-15) is set to AT&T.

Defines the maximum number of SPID devices per DSL on the 4/8TBR card. See
SPID on page 26-23.
4-20
ROUTING:
ROUTING ACCESSES 0..1..4
Shows the current capacity for Routing Accesses and defines the different
numbering plans for programming ISDN.
DIAL SERVICES 0..30..255

Shows the current capacity for Dial Services.
ROUT ELEMENTS 0..50..250

Shows the current capacity for Route Elements.
COST_ELEMENTS 0..10..50
Shows the available number of Cost Calculation Elements.
ROUTING_ELEMENT_ 0..5..MAX2
NPL_SIZE
Calculate the average size (average amount of digits per Element) of all the
Routing Numbering Plan Elements.
ROUTING_NPL_ 0..100..MAX2
ELEMENTS
Estimate the number of Routing Numbering Plan elements used in the system.
2. MAX: (Both parameters) are defined by and limited by the following equation:
ROUTING_ACCESSESx[ROUTING_NPL_ELEMENTS x ((ROUTING_
ELEMENTS_NPL_SIZ x 2) + 5)] <32,000
4-21
CHECK MEMORY ? Yes/No

Instructs the system to display the database memory status. When the System Size
table is displayed without modification, CHECK MEMORY? displays how much
memory remains in the system database as follows:
XXXXX BYTES USED BY RAM.
XXXXX BYTES LEFT IN MEMORY.
When changes are made to the System Size table, CHECK MEMORY? the following
system memory status message is displayed as if changes made to the current sizes
were updated:
Cannot update. Parameters exceed total ports allowed.
 This message appears in versions 15.84.19 and higher. From versions

Please reduce system sizes.
lower than 15.84.19, the following message is displayed:

MEMORY EXCEEDED BY XXXXX BYTES, CAN’T UPDATE.
This message indicates that the memory tables have been exceeded. The technician
should try to reduce the values of less important table parameters thus freeing
memory for the recent updates. If this is not possible, additional memory cards (see
table below) should be purchased.
XXXXX BYTES USED BY DATABASE, AUTO BACKUP AVAILABLE.
XXXXX BYTES USED BY DATABASE, AUTO BACKUP NOT AVAILABLE.
When the system database memory is exceeded, the technician should try to
reconfigure the size values assigning smaller values for less significant parameters.
The technician can also try to perform a manual backup depending on the database
size as described in Chapter 21.
Coral system type Memory card type Capacity
IPx Office DBM-2/4/8 2, 4 or 8 MB

FlexiCom 400 (with HDC controller), DBX (discontinued) 1 MB

5000
DBM-2/4/8 2, 4 or 8 MB
IPx 500, 800, 3000
CDRS 200E
FlexiCom 6000 4XMM or 8XMM 4 or 8 MB

IPx 4000
 When Coral IPx 4000 and Coral FlexiCom 6000 systems include
CoraLINK authorization (CoraLINK on page 3-21) and a 4/8XMM
daughterboard, then 2MB of the 4/8XMM memory is allocated for the
CoraLINK application, even when a CLA-ATS card is not installed.
4-22
UPDATE? Yes/No (*Warning*: Upon Update, database is lost.)

Loads the modified SIZE information, initializes the database and resets the
system.
When making changes in the features listed in the above fields, the changes are
temporary. The changes are only made permanent after entering Y.
When N is entered, all previous entries are ignored and the system remains at the
previously programmed sizes.
Upon returning to Size Definition, enter P in the DISPLAY_Pending_Changes
parameter (at the beginning of the section) to restore the pre-recorded changes.
Otherwise, the changes are erased and the current system parameter values will be
displayed.
4-23
Sizes Tab ç SYSGEN,2 [0,0,0,2]
When entering this branch, the following message is displayed:
! Attention:
The sizes in this database are established by Program default and may
be changed.
system.
Sizes Tabulation relate to the parameter sizes, updating, displaying and tabulating
the parameter sizes based on the different types of keysets and system ports
available.
CURRENT_Config Default/Modified
Shows whether or not a change was made in SIZ. If a change was made, the screens
displays the MODIFIED message. If no change was made, then the screen will
show the DEFAULT message.
CURRENT MEMORY  Display Only

SIZE INFORMATION
Displays the current database memory information.
xxxxxx BYTES LEFT IN MEMORY.
Sizes Tab SYSGEN,2 [0,0,0,2]
4-24
RESOURCES 0..64..250
Defines the number of ports needed for all the Shared Service cards together in the
system.
Required Number of
Card Type
Ports per Card
16MFR (MFC-R2) 16
4DTR 4
8DRCF 22
8DRCM, 8DRCM-2 22
8DTD 8
8DTMF 8
8DTR 8
CNF card (defined as C3Way in Card List 8
on page 6-59)
iDSP 64
MR Office 0
RMI 0
RMI Office 0
U-MR Office (Coral IPx Office URC2) 64 - 112*
U-RMI Office (Coral IPx Office URC2) 64 - 112*
URC2 (IPx 500M and CDRS 200E)† 64 - 112*
‡
MRC-8 (up to 32 DTR and MFR) 32
* For the URC2 resources, see Meet Me on page 4-38
† MSBipx Hardware Issue-0200X1000 or higher

‡ MRC module, is a daughter board installed on PUGW card, PUGWipx card
and MCB Office card. It provides DTMF (DTR) receivers and MFC-R2 (MFR)
receivers. Requires Coral software version 15 or higher and MRC firmware
version 7 or higher.
4-25
N_CALLS 0..256..1024: IPx Office

0..256..2048: IPx 4000
0..256..2048: FlexiCom 6000
0..256..512: All other systems
Defines the maximum number of calls that can be simultaneously made within the
system.
CALLS_Q 0..150..1000
Defines the number of calls that can be simultaneously placed on Hold, Page_Q,
Park or Multi-Appearance.
ACD_STATISTICAL_ Yes/No
SEARCH?
In order to enable the statistical search feature in ACD Hunt groups, this parameter
must be set to Yes. The statistical search procedure requires an idle time counter
for every group member. This parameter, when set to Y, allows you to define ACD
groups with statistical search type (see Hunt Group, Chapter 10).
PARTY_NUM/NAME 0...500 or (number of trunks: (LGS+E&M+DID)/2)+PRI+ISDN)->only if less

than 500
Defines the maximum number of records used for saving the CPN (Calling Party
Number) and Name and the Connected Party Number and Name. Each record can
be accessed at any time during the call. The CPN is displayed on the SMDR.
ISDN_TRANSIT_ 0..50..250
SETUPS
Defines the maximum number of ISDN call setup information to be stored
simultaneously. ISDN call information is used for completing the call setup.
IP Networks:
Note: This number should be increased when IP Network ports are defined for the
system in the UGW card(s). The increase is traffic dependent and should be at least
2 times the estimated maximum number of calls setup per second.
For Example: For systems where 20 calls can be expected to be setup per second,
increase this parameter by 40.
NETWORK_SERVICES 0..50..500
Defines the maximum number of Network Supplementary Feature procedures that
can be performed simultaneously. Network Call Transfer is one example of a NSF
procedure.
4-26
QSIG Signalling 0..64..256

Connections
 This parameter applies only when NETWORK (page 4-20) in Sizes Definition
branch (SIZ) is set to Y.
Defines the maximum number of possible simultaneously CISC network calls. If a
caller from network node A is connected to a caller in node B using a network
feature that requires CISC signaling (e.g. camp-on, follow-me), two QSIG
Signalling Connections are being used simultaneously. If the callers are in the same
node, then only one QSIG Signalling Connection is used.
INTERNAL_SMDR_IN_ Yes/No
SYSTEM
Set this parameter to Yes to instruct the system to allocate memory to support the
display of internal calls on the SMDR report.
NO_OF_CALL_ 0..100..32000
TRACE_RECORDS
Defines the maximum number of incoming calls that may be recorded and listed
(“traced”) for the entire system.
NO_OF_SILENT_ 0..8..128
MONITORS
SAU Requirement
The Silent Monitor features require Software Authorization. Corresponding
default feature dial number:
• #1448 Split Silent Monitor (1-Way).
This parameter defines the maximum number of simultaneous silent monitors in
the system.
SKW_BASE_ 0..128..256

STATIONS_NUM
Defines the maximum number of radio base stations (RBS) in the system.
Required # of
Card Type # base stations
per Card
8SKKipx 8
FlexAir 8SKK 8
16SKK 16
2SKW 2
CoralAIR
4SKW 4
4-27
IP_MEDIA_ 0..60..3400
CHANNELS Note: Default = 0 when upgrading from non-IP systems
 To add IP resources to a non-IP system, IP sizes must be updated and

First Initialization performed.
Defines the maximum number of IP media channels that can be used system-wide.
A UGW/PUGW card(s) with MG/MRC daughter board(s) must be installed in the
system as follows.
MRC* Provides max. # of media channels

Module MRC uses Voice CODEC:
G.729 G.723 T.38 G.711

NET_IP
Firmware V. Coral Version Coral Version
14 15 or higher
10 or higher
MRC-8 8 8 8 8 32
MRC-16 16 16 16 16 64
MRC-32 32 24 32 32 64
MRC-64 64 64 32 64 128
* MRC module, is a daughter board installed on PUGW card, PUGWipx card and MCB Office
card.
MG Module Provides max. Module installed on:

# of media channels
MG-15 15
UGW, UGWipx,
MG-30 30
UGW-E, UGW-Eipx
MG-60 60
MG-24 24
MG-48 48 UGW-E, UGW-Eipx
MG-72 72
Certain Coral features require the intervention of media channels. The MG and
MRC modules provide media channels used to convert PCM calls to IP Packets.
Media channels are also needed when one of the calling parties is not an IP host.
No media channels are needed for pure IP-to-IP (peer-to-peer) connections
(direct-connects).
4-28
NO_OF_LAR_ 0..40..526;
SERVICE_TIMERS IPx 4000 and FlexiCom 6000: 0..40..1096
Defines the maximum number of LAR timers available in the system.

The LAR timer is activated when a failed trunk or Dial service is blocked by the
LAR blocking mechanism. The timer counts blocking duration and instructs the
main software to release the trunk or Dial Service when the blocking time expires.
PENDING_SMS_MSG_ 0..20..250
POOL

This parameter is relevant only for FlexAIR systems.
Defines the maximum number of SMS messages that the system can buffer
simultaneously for the Wireless handsets.
SOFT_KEYS_MENU Fixed/Selectable
Defualt:
• Coral version 15.85.17 or higher: Selectable
• Coral version 15.85.16 or lower: Fixed
This system-wide parameter controls the Soft Keys display menu options for the
following keysets:
• FlexSet 120S, 280S (installed with Key software versions 3.50 or higher)
• FlexSet 121S, 281S
• T207M, T208M, T207M/NP, T208M/BL
This parameter is irrelevant for:
• FlexSet 120S, 280S (installed with Key software versions 3.49 or lower)
• FlexSet-IP 280S
• FlexSet 80 (GKT)

• For FlexSet 120S, 280S (installed with software versions 3.50 or higher):
• Choose Fixed to have the third line display continue to be controlled by the
phone’s software version (and not by the Coral main software).
• Choose Selectable to enable customizing the third line display by using one
of the Soft Key Idle sets defined in the Keyset Soft Keys Idle
Set (page 9-104) branch (Route: SKEY).
• For FlexSets 121S, 281S and T207M, T208M, T207M/NP, T208M/BL:
Choose Selectable to enable the bottom line display by using one of the Soft
Key Idle sets defined in the Keyset Soft Keys Idle Set (page 9-104) branch
(Route: SKEY).
Otherwise, if Fixed is selected, no bottom line display is shown.
When Selectable is chosen, the DISPLAY_SIZE [55] (page 9-56) parameter in the
Keyset Definition branch (Route: KEY) defines the phones as either 6-DSP72 or
7-DSP120.
4-29
N_CALL_LOGS_ Range: 0....130,000 for IPx 4000 and FlexiCom 6000 systems
RECORDS Range: 0....32,000 for all other systems
Default: Total number of Keysets, excluding SIP terminals and wireless
handsets, multiplied by 20/3
This parameter is displayed only when SOFT_KEYS_MENU, above, is set to
Selectable and is relevant only for the following keysets:
• FlexSet 120S, 280S (installed with Key software versions 3.50 or higher)
• T207M, T208M, T207M/NP, T208M/BL
Defines the maximum number of Call Log records that can be saved in this Coral
system. Each call log record can be a maximum of 60 bytes. The number of system
Call Log records is dependant on system hardware (DBX, DBM or XMM
expansion memory cards). The records are allocated only during system
initialization. If the number of call log records exceeds the available memory
resources, a warning is displayed.
 Adding extra call logs substantially increases the memory requirements of

the Coral system to the extent that an expansion memory card could be
required. Do not exceed the call log requirements of the system.
N_CALL_LOG_PER_ 0..20..100 (max depends on system resources)

USER
This parameter is displayed only when SOFT_KEYS_MENU, above, is set to
Selectable and 3RD_LINE_CONTROL [95] (page 9-74) in Keyset Definitions is set to
MCP. It is relevant only for the following keysets:
• FlexSet 120S,280S (installed with Key software versions 3.50 or higher)
• FlexSet 121S,281S
• T207M, T208M, T207M/NP, T208M/BL
! Caution:
Changing this value, erases all Call Logs for the above keysets.
This parameter enables the Coral to allocate memory resources for keysets using
the Call Log feature and defines the maximum number of Incoming and Outgoing
Call Logs permitted per keyset. If all the call records for the keyset has been fully
 Notes:
utilized, no more call logs are saved.
• The total # of N_CALL_LOG_PER_USER will be divided evenly between

Incoming calls and Outgoing calls.
• In case of an odd number, the Incoming call will have an Extra record.
The technician should verify whether an additional memory card (DBX, DBM or
XMM memory modules) needs to be added to the system.
4-30
NO_OF_SIP_ 0..65000
SUBSCRIPTIONS
Defines the number of resources needed for all the SIP endpoints together in the
system.
Required Number of
SIP Endpoint
Subscriptions per Endpoint
Coral SeaBeam softphone 0
T207S, T208S, T207S/NP, T208S/BL 1
P-335 0
T322, T328, P-450, P-560, P-670 Number of DSS* buttons
Third-party SIP IP-phones used for BLF feature and
number of buttons used for
Boss/ELA group Line,
as defined in SIP Terminal
as defined in SIP Terminal
definitions N_BLF_BUTTONS
[13] (Coral version 16.01
or higher) parameter on page
29-48
Third-party SIP PC-softphones 0
Third-party FXS SIP gateways 0
SLT/IST station (behind Coral Teleport/FXS 0
SIP gateway)
SIP Trunk 0
Required Number of
Telephony Feature
Subscriptions per System
Call Transfer feature 20% of the total number of
SIP endpoints in the system
Message Waiting Indicator (MWI) feature Number of SIP terminals
defined with MWI
Total:

* BLF - Busy Line Field
DSS - Direct Station Selection
Default:
20% of all SIP ports (trunks + terminals) + number of SIP terminlas (1 entry
for MWI) + 2*number of Coral SIP terminals (for T207S, T208S, T207S/NP,
T208S/BL standard BLF).
4-31
CHECK MEMORY? Yes/No
! The sizes listed in this database are established by program default and
can be changed.
Changes can affect other sizes or operational relationships within the
system.
Instructs the system to display the database memory status. When the System Size
table is displayed without modification, CHECK MEMORY? displays how much
memory remains in the system database. When changes are made to the System
Size table, CHECK MEMORY? displays the system memory status as if changes
made to the current sizes were updated.
UPDATE? Yes/No (*warning*:Upon update, system init)

(Yes or No must be entered)
! Updating the size table initializes the system causing:

Loads the modified Size information and resets the system. When No is entered,
all previous entries are ignored and the system SIZES remain as previously
programmed.
4-32
URC-Card (IPx Office, IPx 500 and CDRS 200E) ç CDB, 11
The following parameters are used to define the resources ports on:
• Coral IPx Office (URC2: Slot #7, Shelf # 1) U-RMI and U-MR Office cards
• IPx 500M: MSBipx Hardware Issue-0200X1000 (X= Country Initial) or
higher (URC2: Slot #14, Shelf # 0)
• CDRS 200E (URC2: Slot #14, Shelf # 0)
The URC (Universal Resources Card) is configured with 2DSPs, such that its
current card name, as shown in Card List on page 6-59, is URC2 and includes the
following resources:
• DTMF Receivers (DTR)
• Dial Tone Detectors (DTD)
• Caller ID (CID) FSK iDSP transmitters for SLT stations
• Meet Me (CONF) 14 party Conference Bridge:
Enables a conference of a maximum of 84 participants.
• 3-Way Conference (C3WAY)
Enables 3-way conferences of Digital and IP Channels, FlexSet-IP 280S,
T207M, T208M, T207M/NP, T208M/BL and FlexAir/CoralAIR wireless sets.
SAU Requirement, (see page 3-16)
Separate Software Authorization is required to allocate the DTMF, 3WAY, CONF
(Meet-Me), CID – URC and MFR resources.
URC Features
The URC is completely managed by its own PI Card Database - Current and
URC-Card (IPx Office, IPx 500 and CDRS 200E) CDB, 11

Default Branches located in CDB,11. Sizes and maximums must be configured to
match the imposed URC time-slots limit.
Gains
The URC DTMF Receiver (DTR) and DTD Gains may be adjusted in URC Card
Database (URC,11,2) and not in the Feature Control branch as with other cards, see
DTMF GAIN and DTD GAIN (page 4-40).
Meet Me Conference
Conference Modes
The Meet-Me conference can be defined to operate in one of two different modes:
• Summation:
Enables all conference participants to be heard simultaneously during the
conference.
• Strongest Win:
Enables only the loudest speaker to be heard during the conference.
The technician is able to define a maximum number of participants when using the
Summation mode. When this maximum is exceeded, the system automatically
4-33
switches the conference to the Strongest Win mode (see CONF MEMBERS and
CONF SWITCH DELAY (page 4-40), in URC,11,2).
Chained Meet Me Conference Groups
 Requires URC Software Versions 1.29 or higher.
The URC has 6 circuits that may be allocated as Conference ports. Each of these
ports can enable one conference of 14 participants. Alternatively, these conference
ports can be chained together internally by the URC, without using extra time slots,
so that a conference with a maximum of 84 participants can be created. The “chain”
definition is created via the PDB branch, see LINKED TO CONF DIAL#
[4] (page 23-6).
URC Database Programming
The configuration option is used to determine the number of circuits for individual
resource types on a URC card.
Access is accomplished by entering the physical location of any current card (shelf
and slot), or before installing the card, by defining the default.
Once this route is selected the following option menu is available:
Option Description
URC-Default This option is used to display or modify the default

Configuration (page 4-35) configuration of the URC cards. It determines the
number of circuits for individual resource types on
the URC cards. This default is given to the URC card
that will be installed in the future. For URC cards
URC-Card (IPx Office, IPx 500 and CDRS 200E) CDB, 11
already installed, the configuration can be modified

by using the CURRENT Configuration option.
Each resource type can be separately configured
according to any of the ranges listed in Table 4-1 on
page 4-35.
URC-Current This option is used to display or modify number of
Configuration (page 4-37) circuits for individual resource types for each
installed URC card according to card location, by
entering the card’s physical location in the system.
Each card can be separately configured according to
any of the ranges listed in Table 4-1 on page 4-35.
URC-Card This option is used to display or modify the DTMF
Database (page 4-40) Receiver (DTR) and DTD Gains. It is also used to
define the Conference Modes.
4-34
URC-Default Configuration ç CDB,11,0

This branch determines the default number of circuits for individual resource types
(DTMF, Meet Me Conference, C3WAY, CID and DTD) be allocated on the URC
cards. This default will be given to the URC card that will be installed in the future.
For URC cards already installed, the configuration can be modified by using the
URC-Current Configuration on page 4-37 below.
Each resource type can be separately configured according to any of the following
ranges.
Maximum URC Resources
Each system resource circuit uses Coral times slots (resource points). The Coral
enables a maximum of 120 resource points per URC2. The following table lists the
resource points needed per circuit and enables the technician to plan accordingly
when configuring the current and default URC2 configurations.
Table 4-1: PI defaults per URC2 Resource
Resource Max Circuits per Resource Default

URC2 Points Configuration
(Full Assembly)* Needed per
Circuit (CKT) Range Resource
Max Points
Needed
DTMF Receiver (DTR) 24 1 24 1x24
DTD 32 1 16 1x16
3-WAY 24 4 8 4x8
CONF (Meet Me) 6 16 2 16x2
URC-Default Configuration CDB,11,0

Caller ID (CID) iDSP 32 1 16 1x16
TOTAL 66 120
* A maximum of 120 Resource Points is allowed per URC2 card. Therefore, the Full Assembly is
never used. Allocate your resources such that you use a maximum of 120 Resource Points. For
example, increasing the number of 3-way circuits, forces you to decrease one or more of the
other resources.
DTMF 0..24
SAU Requirement
Defines the default maximum number of DTMF Receiver (DTR) resources to be
enabled by the system URC cards. Each DTMF receiver requires one (1) resource
point, see Note! in UPDATE, below.
4-35
Meet Me 0..2..6
 Meet-Me circuits are named CONF in Port List on page 6-67.

SAU Requirement
Defines the default maximum number of Multi-Party (Meet-Me) conference bridge
resources to be enabled by the system URC cards. Each Meet Me conference
circuit requires 16 resource points, see Note! in UPDATE, below.
C3WAY 0..8..24
 The three-way resource is listed as C3WAY in Port List on page 6-67.

SAU Requirement
Defines the default maximum number of 3-way Conference bridge resources to be
enabled by the system URC cards. Each 3-way conference circuit requires 4
resource points (therefore, eight 3-way circuits require 32 resource points), see
Note! in UPDATE, below.
CID 0..16..32
 CID Transmitters are named iDSP in Port List on page 6-67.

SAU Requirement
Defines the default maximum number of Caller ID (CID) transmitter resources to
be enabled by the system URC cards. Each CID transmitter circuit requires one (1)
resource point, see Note! in UPDATE, below.
DTD 0..16..32
Defines the default maximum number of Dial Tone Detector (DTD) resources to
be enabled by the system URC cards. Each DTD circuit requires one (1) resource
URC-Default Configuration CDB,11,0
point, see Note! in UPDATE, below.

UPDATE Yes/No
Updates system with the current changes that were entered when entering Yes in
this parameter.
 Note!
The card configuration is limited to a total maximum of 120 resource
points! A configuration error is displayed and the card cannot be
configured (see Table 4-1 for Resource Point computations) if more than
120 resource points are used.
4-36
URC-Current Configuration ç CDB,11,1

This branch is used to display or modify number of circuits for individual resource
types for each installed URC card according to card location, by entering the card’s
physical location in the system.
Physical Location: (Shelf/Slot) is used to display or modify URC information by
entering the port’s physical location in the system.
 For Coral IPx 500 systems (MSBipx Issue-0200X1000 or higher):

The URC is automatically defined in shelf 0, slot 14.
For CDRS 200E systems:

The URC is automatically defined in shelf 0, slot 14.
For Coral IPx Office systems (U-RMI Office and U-MR Office cards):
The URC is installed in shelf 1, slot 7.
Each URC card can be separately configured according to any of the ranges listed
in Table 4-1 on page 4-35.
FROM/TO SHELF# All available shelves;

1: Coral IPx Office
0: Coral IPx 500 and CDRS 200E
Enter the required range of shelf numbers; FROM the lowest TO the highest shelf
number.
FROM/TO SLOT# All available slots;

7: Coral IPx Office
14: Coral IPx 500 and CDRS 200E
URC-Current Configuration CDB,11,1

Enter the required range of slot numbers; FROM the lowest TO the highest slot
number.
4-37
DTMF 0..24
Default is defined in URC-Default Configuration - DTMF on page 4-35 and is
ultimately limited by its SAU requirement.
SAU Requirement URC DTMF (page 3-16).
Enter the number of URC DTMF receivers to be allocated from this card. Each
DTMF receiver requires one resource point, see Note! in SEND TO CARD below.
Meet Me 0..2..6
Default is defined in URC-Default Configuration - Meet Me on page 4-36 and is
SAU Requirement URC CONF (page 3-17)
Enter the number of URC Meet Me conference circuits to be allocated from this
card. Each Multi-Party (Meet-Me) conference circuit requires 16 resource points,
see Note! in SEND TO CARD below.
C3WAY 0..8..24
Default is defined in URC-Default Configuration - C3WAY on page 4-36 and is
SAU Requirement URC 3WAY (page 3-17)
Enter the number of URC 3Way conference circuits to be allocated from this card.
Each 3-way conference circuit requires 4 resource points, see Note! in SEND TO
CARD below.
CID (iDSP in Port List) 0..16..32

Default is defined in URC-Default Configuration - CID on page 4-36 and is
SAU Requirement URC CLID (page 3-16)
Enter the number of URC CID transmitter circuits to be allocated from this card.
Each CID transmitter circuit requires one resource point, see Note! in SEND TO
CARD below.
DTD 0..16..32
Default is defined in URC-Default Configuration - DTD on page 4-36
Enter the number of URC DTD circuits to be allocated from this card. Each DTD
circuit requires one resource point, see Note! in SEND TO CARD below.
4-38
SEND TO CARD Yes/No

Transfers the updated card database immediately to the URC2 and the card resets
temporarily freezing all URC2 activity. This parameter is used only in the Update
Mode.
• Note!
The card configuration is limited to a total maximum of 120 resource

points! A configuration error is displayed and the card cannot be
configured (see Table 4-1 on page 4-35 for Resource Point computations)
if more than 120 resource points are used.
A warning is issued before updating the card: Warning: Update will
reset current card.
Enter Yes to accept updates or No to cancel.
4-39
URC-Card Database ç CDB,11,2

URC Card Database establishes the card database for the following cards:
• Coral IPx Office: U-RMI Office and U-MR Office cards (URC2: Slot #7, Shelf
# 1)
• IPx 500M: MSBipx Hardware Issue-0200X1000 (X= Country Initial) or
higher (URC2: Slot #14, Shelf # 0)
• CDRS 200E: (URC2: Slot #14, Shelf # 0)
DTMF GAIN -12dB.. 0..+12 dB (increments of 0.5dB)

Allows defining transmission value level for URC DTMF receiver ports.
Programs the receiving level gain of incoming DTMF tones.
DTD GAIN -12dB.. 0..+12 dB (increments of 0.5dB)

Allows defining transmission value level for URC DTD receiver ports.
Programs the receiving level gain of incoming Call Progress tones.
CONF MEMBERS 1..8..14

1: Strongest Win conference mode (only the loudest speaker is heard)
2..14: Summation conference mode (all participants are heard simultaneously)
Define the maximum number of Meet-Me participants for conferences in
Summation mode, allowing every participant to hear all other speaking
participants.
When the number of conference participants exceeds this maximum, the
conference automatically switches to the Strongest Win mode where only the
loudest speaker in the conference is heard.
Set this parameter to one (1) for conferences requiring the Strongest Win mode.
URC-Card Database CDB,11,2
CONF SWITCH DELAY 0..7..255 (1 unit = 10 ms)
 Relevant only for Strongest Win conference mode (see CONF MEMBERS).
Define the time delay required before switching from summation to strongest win
and vice versa (i.e., before switching from the previous loudest party to the new
loudest party). This time delay allows the URC card to avoid switching speakers
because of sudden spikes heard by the conference circuit.
SEND TO CARD Yes/No

Transfers the updated card database immediately to URC cards. Regardless of
entry, routine diagnostics periodically resend the card database to the cards,
including any update which has been made. This parameter is used only in the
Update Mode.
4-40
System Engineering Options ç SYSGEN,3 [0,0,0,3]
Access to the System Engineering Options is allowed only for qualified personnel
and is controlled by password Level 2.
Once this route is selected the following System Engineering Optionsoption menu
is available:
 For manufacturer’s use, only.

Option Description
0 Partial Initialization
Process
• BOSS_AND_UCD_NEW_TS_ALGORITHM
(Y/N)
For IPx Office systems, if this parameter is
set to Y, then CYCLIC_TIME_SLOT_ALLOCATION on
page 4-42 must be set as N=Terminal.
See CAUTION: below.
• LINK_TRAPS_ON (Y/N)
• ** WARNING ** update will cause system init
 For manufacturer’s use, only.

(Y/N)?
1 First Initialization
Process
• BUILD POOL5_DEF
• ** WARNING ** : update will cause first init
with current sizes(Y/N)?
2 Others See Other System Engineering Options (page 4-42).
System Engineering Options SYSGEN,3 [0,0,0,3]

.
! CAUTION:
Relevant for Coral IPx Office systems !!!
Never define the following two parameters as Yes.
If one is defined as Yes the other must be defined No.
Always refrain from the following programming combination:
• BOSS_AND_UCD_NEW_TS_ALGORITHM (Y/N) = Y
• CYCLIC_TIME_SLOT_ALLOCATION =Y (Cyclic)
Using this combination may cause unexpected audio problems and
therefore should be avoided.
4-41
Other System Engineering Options ç SYSGEN,3,2 [0,0,0,3,2]
Access to this branch requires a password level-2 or higher.
CYCLIC_TIME_SLOT_ Y=Cyclic, N=Terminal

ALLOCATION

For manufacturer’s use, only.
For Coral IPx Office systems, if this parameter is set to Y=Cyclic,
then BOSS_AND_UCD_NEW_TS_ALGORITHM (Y/N) on page 4-41 must be set as No.
See CAUTION: on page 4-41.
ACD_NEW_ Yes/No
ALGORITHM

LAR_BLOCK_ Yes/No
OVERRIDE_CONTROL

MLPP_BLOCK_ Yes/No
FEATURE

ALLOW_TRUNK_ Yes/No
GROUP_IN_
When defined as Yes, this parameter allows the EXTENDED INTERNAL DIAL_
EXTENDED_
SERVICE [8] parameter (on page 15-13) to be applied for a trunk group. When
System Engineering Options SYSGEN,3,2 [0,0,0,3,2]
INTERNAL_DIAL_ EXTENDED INTERNAL DIAL_SERVICE [8] is also defined as Yes, calls can be
SERVICE re-routed externally AND via trunk groups.
PREFIX#_FOR_ NONE, R(Remove), or any number that meets the following conditions:
LEADING_ZERO • First digit  0
• Defined value + dialed number  8 digits
• Defined value + dialed number has not already been defined in the
Numbering Plan on page 5-1
Defines the prefix number to be automatically added to the dialed numbers by the
Coral if the first digit is a 0 (leading zero). Leading zero dial numbers are not
displayed when entered in the FROM_DIAL# field. They are automatically
displayed in the TO_DIAL# field.
For example, if this parameter is defined as 46, a phone number defined within the
numbering plan as 005805 becomes 46005805. Leading zero dial numbers will not
be shown in the "From" or "To" fields. They must be entered manually.
4-42
REBUILD_SYSTEM_ Yes/No
DIRECTORY_INDEX?

System Engineering Options SYSGEN,3,2 [0,0,0,3,2]
4-43
Music Sources ç SYSGEN,4 [0,0,0,4]
The system supports up to four different music sources.

Coral IPx 500M and CDRS 200E
In the main unit two music sources are supported without additional hardware.
Source #0 is connected to Music-1 (pin 19/44) and source #1 is connected to
Music-2 (pin 18/43) at the Auxiliary connector.
U-RMI/U-MR/RMI/MR Office cards
In the Coral IPx Office system, Source #0 is connected to M1 and source #1 is
connected to M2/P (at the card front panel).
8DRCF, 8DRCM, 8DRCM-2 or RMI card
The other systems require an 8DRCF, 8DRCM, 8DRCM-2 or RMI card interface
which can enable up to 2 external music sources. In order to determine the I/O
connections, see the corresponding tables in Chapter 5 of the corresponding Coral
Installation and Hardware Reference Manual.
Each music source may be fed from one of the following sources:
External Sources:
• Radio
• Tape Recorder
• Message Announcer
Internal Tones:
• Ringback
• Busy
• Silence
The music sources are numbered 0,1,2 and 3. The total number of music sources is
Music Sources SYSGEN,4 [0,0,0,4]
fixed by defining # OF MUSIC SOURCES defined below.

Any music source may be used for keyset Background Music, Hunt Groups,
Transferred, Dial Tone, Hold/Park, Announcers, Page_Q and Wait-Que features.
The keyset user can choose the type of background music required via the
telephone. The user can also choose the music source for the Hunt and Page_Q
feature when he/she wants the caller to hear a different tone than currently chosen.
The Wakeup Announcer feature does not include a music source choice. Therefore,
it will always be fed from MUSIC SOURCE #0.
 Using a second music source on the same RMI, ASU or

U-RMI/U-MR/RMI/MR Office card prevents using the Public Address
feature of the same card.
Never connect the sole music source to M2 in these cards.
4-44
# OF MUSIC 1..4
SOURCES (1-4) IPx 500 and CDRS 200E: 1.. 2
Determines the total number of music sources, external and internal, that can be
used for the multiple music source feature.
FROM 0..3;
TO 0..3;
MUSIC-SOURCE Coral IPx 500: 0(Music-1, pin 19/44), 1(Music-2, pin 18/43)
CDRS 200E: 0(Music-1, pin 19/44), 1(Music-2, pin 18/43)
RMI and ASU: 0(M/P1), 1(M/P2)
8DRCF, 8DRCM, and 8DRCM-2: 0(M1), 1(M2)
Coral IPx Office U-RMI/U-MR/RMI/MR: 0(M1), 1(M2/P)
Enter the required range of music sources index numbers. FROM indicates the
lowest source index number; TO indicates the highest source index number.
The range is limited by the # OF MUSIC SOURCES (1-4) (page 4-45) parameter above.
LOCATION (Shelf #,Slot #,MP-1/2)/Remove

Default: (--,--,--)
When external music is required, enter the physical location of the
U-RMI/U-MR/RMI/MR Office, RMI/ASU or 8DRCF/ 8DRCM/8DRCM-2 card,
and MP-1 or MP-2 port to which the music is connected.
Information must be entered between parentheses, in ascending order and
separated by a space or comma. Shelf and slot locations describe the hardware
position of the card in the system cabinet.
(Coral IPx 500: Shelf #0, Slot #13).

(CDRS 200E: Shelf #0, Slot #13).
(Coral IPx Office: U-RMI/U-MR/RMI/MR Office: Shelf #1, Slot #6)
MUSIC 1/2 represents the order of the music sources, enter 1 when connected to
MP-1, enter 2 when connected to MP-2 (see the relevant tables in Chapter 5 of the
corresponding Coral Installation and Hardware Reference Manual).
Entering R removes the (Shelf, Slot, Music 1/2) reference.
When Remove is entered or (--,--,--) is displayed, the system always selects the
TONE TYPE automatically.
TONE TYPE Ringback/Busy/Silence

Determines the internal tone type that is sounded when (--,--,--) is displayed or
when the U-RMI/U-MR/RMI/MR Office, RMI/ASU or
8DRCF/8DRCM/8DRCM-2 card is removed or is malfunctioning.
4-45
MUSIC SELECTION Music/Tone

Maintenance Purposes
Interrupts the External Music Source periodically when the Music Source Supply
Only
is malfunctioning or the maintenance card (U-RMI/U-MR/RMI/MR Office,
8DRCF, 8DRCM, 8DRCM-2, RMI or ASU) is malfunctioning.
• Enter Music to hear the External Music Source.
• Enter Tone only if the External Music Source is not functioning properly. The
Tone is selected in the TONE TYPE parameter above.
UPDATE *warning* Yes/No

system init (Y/N)?
Updating # of MUSIC SOURCES and/or LOCATION initializes the system,
! causing:
Loads the modified Music information, initializes the database, and resets the
system. When No is entered, any previous updates are ignored and the system
remains at its pre-programmed sources.
4-46
Units ç SYSGEN,5 [0,0,0,5]
Units describes the number of time slots used system-wide as well as which PB
card and Power Supplies are installed in the system and also describes their
location in the system via the shelf number.
This branch indicates whether the unit is local or remote.
The following pages describe the Units branch for the following systems:
Coral IPx Office: Systems Only on page 4-48.
Coral IPx 500, 800, CDRS 200E and FlexiCom 400: HDC Systems Only on page 4-49.
Coral IPx 3000 and FlexiCom 5000: 4GC Systems Only on page 4-50.
Coral IPx 4000 and FlexiCom 6000: 32GC Systems Only on page 4-52.
Units SYSGEN,5 [0,0,0,5]
4-47
Coral IPx Office: Systems Only

From/To 0..7
UNIT# 0..7;
(Coral IPx Office: 0..1)
Enter the required range of UNIT numbers. FROM the lowest UNIT number TO
the highest.
For Coral IPx Office systems, enter 0 and/or 1 only.
Unit 0, includes Shelves # 1 and 2.
Unit 1 can include only one shelf (Shelf # 3).
Shelf 4: Not Used

Unit 1
Shelf 3: Exp.2
Coral IPx Office
Shelf 2: Exp.1
Unit 0
Shelf 1: IPx Office
SHELVES [0] (0,1),(2,3): Coral IPx Office systems (Read-Only)

Displays the system shelves
(1,2) shown as (0,1); (3,4) shown as (2,3) that define this Unit.
ACTIVE_UNIT [1] Yes/No

Unit 0 is not updatable, it is always active.
Unit 1 may be set to No (if no second expansion exists) to improve call processing.
NUMBER OF 128/256/512 (Read-Only)

TIME-SLOTS [2]
The iGC provides 512 time slots for the Coral IPx Office systems.
UNIT_TYPE [3] 0 (Normal) / 1 (Remote) (Read-Only)

The Unit Type for all Coral IPx Office systems is 0 (Normal).
4-48
Coral IPx 500, 800, CDRS 200E and FlexiCom 400: HDC Systems Only
From/To 0..7
UNIT# 0..7;
(0..0: Coral FlexiCom 400);
(0..1: Coral IPx 500, 800, CDRS 200E)
the highest.
For Coral FlexiCom 400 systems, enter 0 only. The system can have a maximum
of one shelf, Shelf # 0, and therefore only one Unit (a Unit is comprised of two
shelves).
For Coral IPx 500, 800 and CDRS 200E systems, enter 0 and/or 1 only.
Unit 0, includes Shelves # 0 and 1.
Unit 1 can include only one shelf (Shelf # 2).
Shelf 3: Not Used
Unit 1
Shelf 2: Exp.2
Coral IPx 500 or 800
Shelf 1: Exp.1
Unit 0
Shelf 0: Main
SHELVES [0] (0,1): FlexiCom 400 (with HDC controller) systems (Read-Only)
(0,1),(2,3): IPx 500, 800 and CDRS 200Esystems
Displays the system shelves that define this Unit.

Not Relevant for FlexiCom 400 (with HDC controller) systems

For Coral IPx 500, 800 and CDRS 200E systems:
• Unit 0 is not updatable, it is always active.
• Unit 1 may be set to No (if no second expansion exists) to improve call
processing.
NUMBER OF 128/256/512 (Read-Only)

TIME-SLOTS [2]
The HDC provides 512 time slots for the
Coral FlexiCom 400 (with HDC), Coral IPx 500, 800 and CDRS 200E systems.
UNIT_TYPE [3] 0 (Normal) / 1 (Remote) (Read-Only)

The Unit Type for all FlexiCom 400, IPx 500, 800 and CDRS 200E systems is
0 (Normal).
4-49
Coral IPx 3000 and FlexiCom 5000: 4GC Systems Only

From/To 0..7
UNIT# 0..7;
(0..3: Single 4GC;
0..7: Duplicated 4GC)
the highest.
Each UNIT comprised of two system shelves and contains one PB24 card.
UNIT SHELVES Description
0 (0,1) Single 4GC
1 (2,3) Single 4GC
2 (4,5) Single 4GC
3 (6,7) Single 4GC
4 (8,9) 2nd 4GC
5 (10,11) 2nd 4GC Only for

Duplication
6 (12,13) 2nd 4GC systems
7 (14,15) 2nd 4GC
The system can have a maximum of 16 shelves or 8 UNITs. When a UNIT is not
installed, only the SHELVES [0] and ACTIVE_UNIT [1] parameters (see below) are
displayed for that UNIT.
SHELVES [0]  (0,1)..(14,15) (Read-Only) (see table above)

(0..7: Single 4GC, 0..15 Duplicated 4GC)
Displays the system shelves that define this Unit.

Set this parameter to Yes when at least one of the two shelves exist and includes a
PB24 card. If the shelves are not installed, set this parameter to No to improve the
system call processing (this also avoids unnecessary alarm messages).
! Do not set this parameter to No when there are active cards located on
the Unit’s shelves!
Setting this parameter to NO when there are active cards in this

Peripheral Shelf Unit, causes the following message to be displayed:
WARNING! There is at least one card active in the unit,
ARE YOU SURE?-(Y/N)
4-50
 When ACTIVE_UNIT [1] is set to No the following parameters are not displayed.
NUMBER OF 128/256/512 (Check the LED indicator on the PB24 Card front Panel)
TIME-SLOTS [2]
Enter the number of time slots to be used per PB24 card: 128, 256 or 512. The
number of time slots is defined in the PBD24M card hardware. One of the three
LEDs on the PB24 card front panel, marked with 128, 256 and 512, indicates (when
plugged in) how many time slots should be defined.
The Coral FlexiCom 5000 and IPx 3000 can be configured for the maximum
number of ports in use simultaneously, according to the telephony traffic volume.
There are three options available:
• 128 time slots per one or two peripheral shelves
UNIT_TYPE [3] 0 (Normal)

1 (Remote)
Defines the Unit type as Normal or Remote Coral FlexLITE.
 If the time slots was changed in this branch, the following message is displayed
before an UPDATE can be performed:
! ATTENTION, TS (time slots) UPDATES

256 & 512 times slots are valid options with 24 ports High Density (HD)
systems only!
This must be consistent with PB24 card indication.
UPDATE *warning* Yes/No

system init (Y/N)?
! Updating this parameter causes the interruption of all calls.

Loads the modified time slot and UNIT information. When No is entered, updates
are ignored and the system remains at its pre-programmed sources.
4-51
Coral IPx 4000 and FlexiCom 6000: 32GC Systems Only

From/To (0..7)
UNIT#
the highest.
Each UNIT is comprised of two system shelves and contains at least one PB-ATS
card, of which only one is active at any current time.
Peripheral Shelf UNIT Shelf Numbers
0 (0,1)
1 (2,3)
2 (4,5)
3 (6,7)
4 (8,9)
5 (10,11)
6 (12,13)
7 (14,15)
The system can have a maximum of 16 shelves or 8 UNITs. When a UNIT is not
installed, only the SHELVES [0] and ACTIVE_UNIT [1] parameters (see below) are
displayed for that UNIT.
SHELVES [0]  (0,1)..(14,15) Read-Only

Displays the system peripheral shelves that define this Unit.
ACTIVE_UNIT [1] Yes/No (Read-Only)

If the UNIT is installed (i.e. a PB-ATS or FLMS card is installed on the even shelf),
then the system sets this parameter to Yes, defining this Peripheral Shelf Unit as an
Active Unit.
PB_STATUS_#1 [2] Exists/No Card/No Clock/PCM Fault (Read-Only)

Displays the status of the PB-ATS card installed in:
• Slot 1 - FlexiCom 6000
• Slot 2 - IPx 4000XE
Both PB-ATS cards are located on the even shelf. If no PB-ATS card is installed,
then the parameter displays No Card.
If the card exists and is not functioning properly, then the parameter displays either
No Clock or PCM Fault depending on the fault.
4-52
PB_STATUS_#2 [3]  Exists/No Card/No Clock/PCM Fault (Read-Only)

Displays the status of the PB-ATS card installed in:
• Slot 2 - FlexiCom 6000
• Slot 1 - IPx 4000XE
Both PB-ATS cards are located on the even shelf. If no PB-ATS card is installed,
then the parameter displays No Card.
If the card exists and is not functioning properly, then the parameter displays either
No Clock or PCM fault depending on the fault.
PB_SELECT [4] 1 (Slot1) or 2 (Slot 2)

The technician can select which PB-ATS card should be used currently.
 Before the technician can remove a PB-ATS card, a working PB-ATS card
must be defined in this parameter.
If the selected PB-ATS does not exist or is faulty, the following error message
appears: SELECTED PB IS NOT ACCESSIBLE. TRY AGAIN!
POWER_SUPPLY_  OK/Faulty (Read-Only)

STATUS_#1 [5]
Displays the status for Peripheral Power Supply #1 (PS19/PPS 1). One, two or no
Power Supplies can be installed per shelf.
POWER_SUPPLY_  OK/Faulty (Read-Only)

STATUS_#2 [6]
Displays the status for Peripheral Power Supply #2 (PS19/PPS 2). One, two or no
Power Supplies can be installed per shelf.
RING_POWER_  OK/Faulty (Read-Only)

SUPPLY_STATUS_#1
 This field is only relevant for Coral FlexiCom 6000 systems.

[7]
Displays the status for the Ringer Power Supply #1 (RPS 1).
RING_POWER_  OK/Faulty (Read-Only)

SUPPLY_STATUS_#2
[8]
 This field is only relevant for Coral FlexiCom 6000 systems.
Displays the status for the Ringer Power Supply #2 (RPS 2).
4-53
NUMER OF TIME 128 or 512 (Read-Only)

SLOTS [9]
Defines the number of time slots for this Unit. The number of time slots is factory
set and cannot be changed.
• 128 - Coral FlexiCom 5000 Peripheral shelves (field upgrades)
• 512 - Coral FlexiCom 6000 Peripheral shelves
• 512 - Coral IPx 4000 Peripheral shelves (384 time slots in use)
UNIT_TYPE [10] 0 (Normal) or 1 (Remote)

Each unit is capable of operating as:
• 0 (Normal) via a PBD-ATS card for local peripheral shelves
• 1 (Remote) via an FLIA-ATS card for FlexLITE remote shelves
Defines the Unit type as Normal or Remote Coral FlexLITE shelf.
SEND TO 32GC? [11] Yes..No

Loads the modified UNIT information. When No is entered, updates are ignored
and the system remains at its pre-programmed definitions.
4-54
5 Numbering Plan
The Numbering Plan (NPL) is used to determine the Coral system-wide numbering
scheme. Two types of numbering Plans are given, a General Numbering Plan and
a Special Numbering Plan. The General Numbering Plan establishes the system
pattern dialing plan. It is the System Dialing Plan that determines all hardware and
many software identifiers used for programming purposes. The Special NPL
defines and identifies special feature codes. Details for the Numbering Plans are
found on the following pages.
General Numbering Plan ..............................................................................5-3
General Numbering Plan (Alphabetical Order) ...........................................5-7
General Numbering Plan (Field/Index Order) ...........................................5-17
Special Feature Codes ................................................................................5-50
FlexiCall/IRSS (Freedom) Feature Codes .................................................5-52
 On the following pages, sample General Numbering Plans are given.

SHOW TYPE of NUMBER.......................................................................5-54
Dialing digits via the keypad or programmed buttons on the keyset, is the user’s
method of instructing the Coral system to call another user, access a Trunk and dial
out, access internal facilities or activate features.
The specific structure of the digit patterns used in the Coral for various system
instructions is defined in the Numbering Plan.
The Numbering Plan includes two parts, the main plan: GENERAL NPL and the
secondary numbering plan: SPECIAL NPL.
The main Numbering Plan defines the access codes of each of the physical ports in
the system. Additionally, the Numbering Plan defines the access codes for Groups,
Speed Calling Libraries and features.
A dial number is assigned to each Coral feature. The access codes are changed by
the UPDATE function. There are also feature access codes that need to be
REMOVED or ADDED. In such cases, the system programmer must have a
reference tool to relate a dial number to a specific feature. That reference tool is an
internal software number which is also known as the index number which relate
features to dial numbers, e.g. index number 51 relates Call Forward All to a dial
number (141 is the Call Forward All dial number default).
For example, assume Call Forward All is not defined in the system and it is
requested. Such a change is accomplished in the PATTERN NUMBERING PLAN.
The system programmer selects ADD, and then DIAL NUMBER 141,chooses
FEATURE and then enters the requested INDEX NUMBER, 51 which actually
relates 141 to Call Forward All.
5-1
Numbering Plan PI Reference Manual
The Special Feature Codes (page 5-50) establish the dial codes used for certain
system features typically dialed following a hookswitch flash (for example:
Camp-On, Snooze, or Break-In).
The FlexiCall/IRSS (Freedom) Feature Codes (page 5-52) establish the dial codes
used for the FlexiCall and IRSS Freedom features allowing non-Coral stations to
access Coral services and systems by creating a virtual Coral station via the
established connection between the Coral and non-Coral stations.
5-2
PI Reference Manual Numbering Plan
General Numbering Plan ç NPL,0 [0,0,5,0]
The General Numbering Plan is used to assign system dial numbers to the system
hardware (shelf, slot, circuit) and software (index numbers) in the flexible
numbering scheme. The general numbering plan also assigns Network numbers to
the Network nodes.
SHELF, SLOT, CKT: The port’s physical location.

A shelf, slot, circuit hardware identification (HID) number represents a hardware
position in the system cabinet, and must be accompanied by the correctly installed
equipment at the start position of the range.
The Shelf, Slot and Circuit numbers are only relevant for dial numbers with
physical locations such as trunks and stations.
The card type can be viewed in Card List on page 6-59.
INDEX NUMBER: An index number is a software identification number (SID) which identifies a
feature, speed dial library, node number or group.
Each system feature and key function is identified by a specific index number
regardless of the dial number assigned to it by the Numbering Plan. The first
feature is identified by index 0.
Similarly, each group of any group type, whether Hunt, Pick-up, or Trunk, etc., and
each number of the public speed dial library is identified with a specific index
number regardless of the dial number assigned to it. Thus, the first trunk group is
index 0, the first hunt group is index 0, the first public library number is index 0,etc.
In general, the number of groups or libraries established in the System Sizes
determines the quantity of index numbers allocated. The first 100 public speed dial
General Numbering Plan NPL,0 [0,0,5,0]

library numbers for instance, require index numbers 0 through 99 (inclusive), the
second 100 would require index numbers 100 through 199 (inclusive).
NODE NUMBER: Each private exchange in a network represents a network node and is designated
by a corresponding network node number. The network node number is limited to
8 digits and is not part of the general numbering plan.
The network has its own network numbering plan used for network
communications.
INDEX/CKT: This is a virtual address for IP SLT and IP LGS stations serviced by IP gateways.
The index number represents the IP gateway number as known to the Coral. The
Circuit number (CKT) represents the station on the gateway.
5-3
SYSTEM DIAL The system dial number is used to access the related equipment or feature. The dial
NUMBER: number range (START to END numbers) may be greater or smaller, depending on
the information entered in the NUM_PLAN (page 4-15) in the Sizes Definition from
branch (SIZ). START and END numbers must have the same number of digits
(e.g., 0-9, 00-99, 000-999...).
The following arrow symbol Ô appears when the range END number depends on
the maximum number listed in the database as defined in Sizes Definition (page 4-2)
branch (SIZ). Hence, a number listed after Ô is not necessarily the exact END
number for the range and only a suggestion. No number listed after Ô indicates that
the END number is defined in the SIZES database.
 1 to 8 digits may be used in place of the 3 or 4 digit defaults, however,

using less than 3 digits severely restricts the flexibility of the Numbering
Plan.
Selecting the NPL branch displays the following menu:
OPTION Description
0 - UPDATE Allows updating the numbering plan.

1 - DISPLAY Displays the entire numbering plan.
2 - ADD Adds a number to the numbering plan.
3 - REMOVE Removes selected numbers from the numbering plan.
5 - SHOW Shows a specific part of the numbering plan according to type.
7 - ERASE Erases all numbers in the numbering plan.
5-4
Table 5-1: Numbering Plan Options-Full Explanation
0- FROM OLD DIAL#: Enter the first existing dial number of the range that requires
UPDATE updating.
TO OLD DIAL#: Enter the last existing dial number that requires updating. If only
a single number is required, enter the same number as FROM
OLD DIAL #.
FROM NEW DIAL#: Enter the first new dial number, in the range that was defined
under the old dial number. (Once the first number is entered the
rest of the defined range is automatically calculated).
1- FROM DIAL#: Displays the first dial number defined in the display range.
DISPLAY
TO DIAL Displays the last dial number defined in the display range.
NUMBER#:
TYPE: Displays the port, feature or type of group for which dial
numbers are assigned.
INDEX#/ Displays the index number of first library, feature or group, or

SHELF,SLOT,CKT/ physical shelf, slot and circuit position of the first port in the
range, or the Network node number.
NODE#:
2 - ADD FROM NEW DIAL#: Enter the first new dial number of the range that is to be added.
TO NEW DIAL#: Enter the last new dial number to be added. If only a single
number is required, enter the same number as FROM NEW
DIAL #.
NUMS ALREADY Enter Y to assign an additional dial number to a port, feature or

DEF? (Y/N): group, which already has an assigned (old) dial number. Yes
also allows assigning additional dial numbers.
Enter No to assign the first dial number to a port, feature or
group which currently has no assigned dial number.

If No is selected then the table of all Numbering Plan types
(items) appears.
FROM OLD DIAL#: Appears when Yes is selected. Enter the old dial number.
CHOOSE TYPE: Enter the number of the port, feature or group to which dial
numbers are assigned.
When a port type is selected, the following message appears:
-ENTER (SHELF,SLOT,CKT)
Enter the physical location of the first new dial number.
When any other type is selected the following message appears:
- ENTER INDEX #
Enter the index of the first new dial number.
5-5
Table 5-1: Numbering Plan Options-Full Explanation
3- FROM OLD DIAL#: Enter first existing dial number of the range that requires
REMOVE removal.
TO OLD DIAL#: Enter last existing dial number that requires removal. If only a
single number is required, enter the same number as FROM
OLD DIAL #. After the number is typed and [CR] pressed, if the
number was successfully removed the following message
appears:
NUMBERS REMOVED
The requested dial numbers are immediately removed from the
numbering plan.
Option 4 is not used in the General Numbering Plan.
5 - SHOW When SHOW is selected, the table of currently available

Numbering Plan types (items) appears.
CHOOSE TYPE: Enter the type (item) number of the port, feature or group to
which dial numbers are assigned. Once this type number is
selected an informative table showing the dial numbers, type
and location of the requested item will appear.
Press [CR] to display a list of all items, as in the Display option.
Option 6 is not used in the General Numbering Plan.
7- ** WARNING ** : all Caution!

ERASE dial numbers will Entering Yes immediately and permanently removes all currently
be lost ! defined numbers from the Numbering Plan.
ARE YOU SURE The default is No.
(Y/N)? N Press [CR] to return to the main General Numbering Plan menu.
5-6
General Numbering Plan (Alphabetical Order)
Use the following table to locate features by name. To view a list of features by
feature number, see Table 5-3 on page 5-22
Table 5-2: Default Feature Numbers-in Alphabetical Order
Feature Field Index/CKT Default Dial No.J

ACCOUNT CODE 9 109 #1990
ACD (HUNT GROUP) NUMBERS 5 0 see page 5-19
ACD - MAX CALLS WAITING for BUSY (Attendant) 9 209 #1746
ACTIVATION CODE 10 3 #*1, #11
ALARM (Attendant) 9 148 #1997
AUTO ANSWER ON/OFF 9 18 #138
AUTOGUARD TRUNK 9 154 #1998
AUTO REDIAL (ACNR) 9 88 #178
AUTO REDIAL - ASSIGN PRIORITY 10 0 #*8
AUTO REDIAL - CANCEL PRIORITY 10 1 #*9
AUTO REDIAL - RESTART NUMBER 10 9 #*7
AUTO REDIAL - STOP NUMBER 10 8 #*6
AUTO SET RELOCATE 9 220 Not Available
BELL/UNA RELAY 11 24: U-RMI Office (RMI-F) 7050Ô7059

24: RMI Office (RMI-F)
24: U-MR Office (MR)
General Numbering Plan (Alphabetical Order) NPL,0

24: MR Office (MR)
24: 8DRCF
24: 8DRCM
24: 8DRCM-2
8: RMI
8: ASU
24: IPx 500M main Cage
24: CDRS 200E MainCage
BLOCK STATION 9 63 #153
BOSS/SECRETARY GROUP NUMBERS 6 0Ô see page 5-19
BOSS/SECRETARY LINE KEY 9 6 #126
BREAK-IN special 3
BREAK-IN KEY 9 4 #124
BUSY OUT TRUNK 9 65 #155
CALL CHARGE PRINT 9 162 #1972
CALL CHARGE RESET WITH PRINTOUT 9 168 #1978
J Default Dial Numbers for Eu0, Eu1 & Eu2 systems are defined as: #( Index number + 100).
For Example: Call Forward All (Station) is defined for all systems with Index 51. Therefore, its default dial number for
these systems is defined as #151.
5-7

CALL ELAPSED TIME DISPLAY KEY 9 9 #129
CALL FORWARD ALL (Attendant or Boss Group) 9 78 #168
CALL FORWARD ALL (Station) 9 51 #141, #8
CALL FORWARD ALL - External (Attendant or Boss Group) 9 227 #17707
CALL FORWARD ALL - External (Station) 9 222 #17702
CALL FORWARD BUSY (Attendant or Boss Group member) 9 77 #167
CALL FORWARD BUSY (Station) 9 50 #140
CALL FORWARD BUSY - External (Attendant or Boss Group) 9 226 #17706
CALL FORWARD BUSY - External (Station) 9 221 #17701
CALL FORWARD BUSY/NO-ANSWER (Station) 9 57 #147, #2
CALL FORWARD BUSY/NO-ANSWER - External (Station) 9 225 #17705
CALL FORWARD NO-ANSWER (Attendant) 9 79 #169
CALL FORWARD NO-ANSWER (Station) 9 52 #142
CALL FORWARD NO-ANSWER -External (Attendant) 9 228 #17708
CALL FORWARD NO-ANSWER -External (Station) 9 223 #17703
CALL FORWARD TIMED (Attendant) 9 174 #1984
CALL FORWARD TIMED (Station) 9 175 #1985
CALL FORWARD TIMED - External (Attendant) 9 229 #17709
CALL FORWARD TIMED - External (Station) 9 224 #17704

CALL FORWARD UNDEFINED 9 239 #17717
CALL PICKUP: DIRECTED 9 90 #180, 77
CALL PICKUP: GROUP 9 91 #181,76
CALL PICKUP: NIGHT ANSWER, BELL/UNA GROUP 9 102 #192, 78
CALL TRACE- Activation Station 9 203 #1740
CALL TRACE- Print Station 9 204 #1741
CALL TRACE- Activation Attendant 9 205 #1742
CALL TRACE- Print Attendant 9 206 #1743
CALLING ID CONTROL 9 193 #1444
CAMP ON - Call Back 9 86 #176
CAMP ON - Call Back special 2
CAMP ON - Call Waiting/Call Offer special 8
5-8

CANCELLATION CODE 10 2 #*0,#10
CHECK IN/OUT 10 157 #1970
CO BLOCKED DISPLAY 9 67 #157
CONFERENCE LOCK KEY 9 190 #1441
CONFERENCE PORTS 30 7098Ô7099
CONFERENCE RELEASE/INSPECT 9 173 #1983
CONTINUOUS CONFERENCE from 3way 9 35 #1306
COS SWITCHOVER 9 59 #149
CPA (Coral Paging Adapter) 2 see page 5-18
DAY/NIGHT TRANSFER (Auto/Manual) 9 144 #1993
DAY/NIGHT-1 TRANSFER 9 95 #185
DAY/NIGHT-2 TRANSFER 9 94 #184
DEFINE GROUP CALL OPERATOR 9 238 #17716
DC NO CALL 9 179 #1989
DIAL CALL PICKUP: DIRECTED 9 90 #180, 77
DIAL CALL PICKUP: GROUP 9 91 #181, 76
DIAL SERVICE 36 0Ô 4850Ô
DID TEST NUMBER 9 186 CC1: 3999

DID TRUNKS 14 see page 5-41

DIRECT IN LINE: DAY SERVICE 9 74 #164
DIRECT IN LINE: NIGHT-1 SERVICE 9 73 #163
DIRECT IN LINE: NIGHT-2 SERVICE 9 75 #165
DIRECTORY 9 145 #1994
DIRECTORY-Access Personal Directory 9 #1994, #9
Directory-Lower/Upper Case (CAPS LOCK) 9 45 Not Available
Directory-Alphanumeric Mode (NUM LOCK) 9 37 Not Available
DIVERT CALL KEY 9 194 #1445
DO NOT DISTURB/UNATTENDED 9 55 #145
DON'T DISTURB for Station by Attendant 9 155 #1999
DROP NO DIAL TRUNK 9 72 #162
DTMF Touch-Tone Dialing for Other Common Carrier (OCC) 9 7 #127
5-9

DUMP 9 178 #1988
DVMS MSG 31 0Ô see page 5-43
DVMS PORTS 32 see page 5-44
ELA Line Key — Programming 9 240 #17718

ELA Personal/Departmental Log IN/Out
EXCLUDE DESTINATION KEY 9 22 #1322
EXCLUDE SOURCE KEY 9 21 #1321
EXCLUSIVE HOLD (Boss Group) 9 97 #187
EXECUTIVE PRIVILEGE 9 80 #170
FLASH ON TRUNK 9 60 #150
FlexiCall All 9 230 #17710
FlexiCall Internal 9 231 #17711
FlexiCall External 9 232 #17712
FlexSet NUMBERS 2 see page 5-18
FlexSet ZONE PAGE NUMBERS 20 0Ô see page 5-42
FlexSet VOICE PAGE NUMBERS 3 see page 5-19
FlexSet-IP 280S NUMBERS 41 0Ô see page 5-46
FlexSet-IP VOICE PAGE NUMBERS 0Ô see page 5-47
FOLLOW ME 9 99 #189
FOLLOW ME - External 9 233 #17713
FORCED RELEASE KEY 9 3 #123
GROUP CALL -Access Code 35 0Ô 5600Ô
GROUP CALL-Add New Member 9 33 #1304
GROUP CALL-Release New Member 9 34 #1305
GROUP CALL -Release Single Participant 9 195 #1446
GROUP CALL-Temporary Group Call Activation 9 198 #1449
GROUP CALL -Terminate Conference 9 196 #1447
HANDSET/SPEAKER KEY 9 23 #1323
HEADSET ONLY-ON/OFF 9 31 #1302
HELP KEY 9 192 #1443
HOLD 9 81 #171, #4
HOT STATION DELAY 9 92 #182
5-10

HOT STATION IMMEDIATE 9 76 #166
HOT TRUNK DELAYED 9 71 #161
HOT TRUNK IMMEDIATE 9 70 #160
HUNT GROUP (ACD/UCD) NUMBERS 5 0 see page 5-19
IDLE DISPLAY ON/OFF 9 17 #137
INCOMING ONLY TRUNK 9 68 #158
IP-FlexSet/Keyset NUMBERS 41 0Ô see page 5-46
IP-FlexSet/Keyset VOICE PAGE NUMBERS 44 0Ô see page 5-47
IP-LGS NUMBERS (requires Coral Version 14.6x) 43 see page 5-47
IP-SLT NUMBERS (requires Coral Version 14.6x) 42 see page 5-46
IRSS (Individual Remote System Services) Freedom 9 234 #17714
KB0 SETUP 9 147 #1996
KEYSET NUMBERS 2 see page 5-18
KEYSET-IP NUMBERS 41 0Ô see page 5-46
KEYSET VOICE PAGE NUMBERS 3 see page 5-19
KEYSET-IP VOICE PAGE NUMBERS 44 see page 5-47
KEYSET ZONE PAGE NUMBERS 20 0Ô see page 5-42
LAR BLOCK 9 169 #1979
LARGE PUBLIC LIBRARY PREFIX 9 199 N/A

LAST NUMBER REDIAL 9 53 #143, *
LAST PARTY RELEASE (multi-party conference only) 9 32 #1303
LED ON/OFF KEY 9 30 #1301
LGS IP NUMBERS 43 see page 5-47
LIBRARIES PRIVATE 19 0Ô see page 5-41
LIBRARIES PRIVATE: PROGRAMMING 9 103 #193
LIBRARIES PUBLIC 7 0Ô 6000Ô
LIBRARIES PUBLIC: PROGRAMMING (Attendant) 9 104 #194
LIBRARY PUBLIC LARGE PREFIX 9 199 N/A
LOAD ID (ACD) 9 163 #1973
LOCK Phone 9 58 #148
LOG-IN PRIMARY (ACD) 9 191 #1442
5-11

LOG-IN/OUT (ACD) 9 164 #1974
LOOP KEY 9 1 #121
LOOP ORIGINATING ONLY KEY 9 5 #125
MALICIOUS CALL TRACE- Activation Station 9 203 #1740
MALICIOUS CALL TRACE- Print Station 9 204 #1741
MALICIOUS CALL TRACE- Activation Attendant 9 205 #1742
MALICIOUS CALL TRACE- Print Attendant 9 206 #1743
MESSAGE CANCEL 9 54 #1440
MESSAGE WAITING (Attendant) 9 66 #156
MESSAGE WAITING (Attendant) special 7
MESSAGE 9 85 #175, #5
MESSAGE special 5
MLPP 9 237 #17715
MODEM 13 26: U-RMI Office (RMI-F) see page 5-41

 Modem is not available on 8DRCM-2 card.

26: 8DRCF
26: 8DRCM
3: RMI
 IPx 500M with MSBipx Hardware

3: ASU
(applicable for MSBipx
Issue-0230X1003 or higher does not include Hardware Issue
a MODEM. The modem was standard in 0220X1003 or lower)

lower.
MULTILINGUAL DISPLAY 9 28 #1328
MUSIC MULTIPLE SOURCE SELECTION 9 29 #1329
MUSIC ON/OFF 9 15 #135
MUTE KEY 9 20 #1320
NAME TO DIAL NUMBER DISPLAY KEY (Name/Number) 9 8 #128
NETWORK 39 0Ô see page 5-45
NIGHT ANSWER, BELL/UNA PICKUP GROUP 9 102 #192, 78
NIGHT/DAY TRANSFER (Auto/Manual) 9 144 #1993
NIGHT1/DAY TRANSFER 9 95 #185
NIGHT2/DAY TRANSFER 9 94 #184
NODE ID# for Current Node 9 219 None: see page 28-14
5-12

OCC KEY: Touch-Tone Dialing (DTMF) for Other Common 9 7 #127
Carrier (OCC)
ORIGINATE ONLY STATION 9 61 #151
OUTGOING ONLY TRUNK 9 100 #190
OUTGOING RESTRICTION STATION 9 64 #154
PAGE_Q 33 0Ô 7060Ô
PAGE PUBLIC ADDRESS 12 23: U-RMI Office (RMI-F) 7074Ô7079

23: MR Office (MR)
23: 8DRCF
23: 8DRCM
23: 8DRCM-2
7: RMI
7: ASU
PAGE-DOWN (SCROLL) IN DISCRETE STEPS 10 6 #*4
PAGE-DOWN FAST (SCROLL) 10 7 #*5
PAGE-UP (SCROLL) IN DISCRETE STEPS 10 4 #*2
PAGE-UP FAST (SCROLL) 10 5 #*3
PARK 9 93 #183, #7, 79
PARTY INFORMATION ON PORTS 9 177 #1987
PASSCODE CHANGE 9 89 #179

PHONE LOCK 9 58 #148
PORT INFORMATION (Not Applicable used from Coral 9 176 #1986

version 16.01.16)
PREFERENCE 9 11 #131
PRIMARY LOGIN (ACD) 9 191 #1442
PRIVACY (Boss Group) 9 96 #186, #6
PRIVATE LIBRARIES 19 0Ô see page 5-41
PRIVATE LIBRARY: PROGRAMMING 9 103 #193
PROGRAMMING BUTTON 9 19 #139
5-13

PUBLIC ADDRESS (Paging, Loudspeaker) 12 23: U-RMI Office (RMI-F) 7074Ô7079
23: MR Office (MR)
23: 8DRCF
23: 8DRCM
23: 8DRCM-2
7: RMI
7: ASU
PUBLIC LIBRARIES (Station) 7 0Ô 6000Ô
PUBLIC LIBRARY: PROGRAMMING (Attendant) 9 104 #194
PUBLIC LIBRARY LARGE PREFIX 9 199 N/A
REDIAL AUTO (See AUTO REDIAL) 9 88 #178
REDIAL LAST NUMBER 9 53 #143, *
REDIAL SAVED NUMBER 9 106 #196, #9
RELAY 21 25: U-RMI Office (RMI-F) 7086Ô7097

25: MR Office (MR)
25: 8DRCF
25: 8DRCM
25: 8DRCM-2
9: RMI
9: ASU
RELEASE FROM ALL ACD/UCD GROUPS 9 165 #1975
RELEASE/RESUME FROM UCD GROUP 9 142 #1991
REMINDER 9 82 #172
RESERVE TRUNK 9 69 #159
RING LEVEL Adjustment 9 16 #136
ROOM STATUS / CANNED MESSAGES (Attendant) 9 110-125 7010-7025
ROOM STATUS / CANNED MESSAGES (Station) 9 126-141 7026-7041
ROUTING ACCESS 37 0Ô 80
SAVED / REPEAT NUMBER 9 106 #196, #9
SCROLL ADVANCES IN DISCRETE STEPS 10 4 #*2
SCROLL BACKWARD IN DISCRETE STEPS 10 6 #*4
SCROLL FAST ADVANCE 10 5 #*3
5-14

SCROLL FAST BACKWARD 10 7 #*5
SECURITY 9 87 #17700
SERIAL LIBRARY PREFIX 9 161 N/A
SERIES 9 105 #195
SILENT MONITOR (2-Way) 9 171 #1981
SILENT MONITOR (2-Way) special 9
SILENT MONITOR (1-way) Splitting 9 197 #1448
SLT NUMBERS 1 see page 5-18
SLT IP NUMBERS 42 see page 5-46
SNOOZE (WAKEUP/REMINDER) special 4
SPEAKER KEY 9 0 #120
STOP DIAL KEY 9 10 #1300 (or # -permanent

key)
T207M, T208M, T207M/NP, T208M/BL Numbers 41 0Ô see page 5-46
T207M, T208M, T207M/NP, T208M/BL Voice Page Numbers 0Ô see page 5-47
TERMINATING ONLY STATION 9 62 #152
TIME/DATE SETTING 9 98 #188
Touch-Tone Dialing (DTMF) for Other Common Carrier (OCC) 9 7 #127
TRUNK AUTOGUARD 9 154 #1998

TRUNK DROP NO DIAL 9 72 #162
TRUNK GROUP 4 0-15 see page 5-19
TRUNK NUMBERS 0 see page 5-18
UCD (HUNT) GROUP NUMBERS 5 0 see page 5-19
UNATTENDED STATION DESTINATION 9 56 #146
UNATTENDED/DO NOT DISTURB 9 55 #145
UNLOCK Phone 9 58 #148
VOICEMAIL SEQUENCE (Version 10.19 only) 9 24 #1324
VOICE PAGE ACTIVATION special 6
VOICE PAGE ACTIVATION from IDLE 9 101 #191, #3
VOICE PAGE AUTO ANSWER 9 13 #133
VOICE PAGE FlexSet 120/280/121/281 series Numbers 3 see page 5-19
5-15

VOICE PAGE T207M, T208M, T207M/NP, T208M/BL and 44 0Ô see page 5-47
FlexSet-IP 280M Numbers
VOICE PAGE ON/OFF 9 14 #134
WAIT QUEUE 38 0Ô see page 5-45
WAITING CALLS DISPLAY (ACD) 9 172 #1982
WAITING CALLS DISPLAY KEY 9 25 #1325
WAKEUP REPORT (ATTENDANT) 9 158 #1971
WAKEUP (STATION) 9 83 #173
WAKEUP (ATTENDANT) 9 108 #1980
WHISPER PAGE-Announcing 9 207 #1744
WHISPER PAGE - (DND) Receiving Turning ON/OFF 9 208 #1745
WIRELESS STATION 40 see page 5-45
WRAP UP CODE (ACD) 9 167 #1977
WRAP UP TIME (ACD/UCD) 9 166 #1976
XFER (TRANSFER) KEY 9 2 #122
5-16
General Numbering Plan (Field/Index Order)
NPL Type The following list includes all the different NPL types that the Coral supports. An
NPL type must be defined for each dial number in the system. There are many
different NPL types which include among others: dial numbers, trunk numbers,
features, group numbers, dial services, and more. A complete list is given below.
Numbers shown in square brackets ([ ]) are field numbers used while in the Add (2)
or Show (5) submenu of the General Numbering Plan. These bracketed numbers
allow quick access to the various numbering plan types (the parameter name) by
immediately skipping to the requested field.
Note on NPL Type Range Definitions:
When the default range/s in the following parameters define a range of dial
numbers, the dial number is used to access the related equipment or feature. The
dial number range (START to END numbers) may be greater or smaller, depending
on the information entered in Sizes Definition (page 4-2) branch (SIZ) and the
number of ports authorized by the SAU (see Chapter 3). START and END dial
numbers must have the same number of digits (e.g., 0-9, 00-99, up to eight digits
00000000-99999999).
The following arrow symbol Ô appears when the range END number depends on
the maximum number listed in the database as defined in Sizes Definition (page 4-2)
branch (SIZ). Hence, a number listed after Ô is not necessarily the exact END
number for the range and only a suggestion. No number listed after Ô indicates that
the END number is defined in the SIZES database.
 Note:
General Numbering Plan (Field/Index Order) NPL,0

• 1 to 8 digits may be used in place of the 3 or 4 digit defaults, however,
using less than 3 digits severely restricts the flexibility of the Numbering
Plan.
• # or * may be used only at the beginning of NPL Types FEATURE [9]
and EDIT [10] and may not be used at the beginning of any other NPL
Type dial number.
• # or * may not be used in the middle of a dial number.
! Warning:
Modifying any NPL port number (not feature number) causes:
1. An initialization of the CLA or CLA-ATS card.
2. CoraLINK applications to be interrupted (calls are unaffected).
Before the update is performed, the following message prompts:
INIT CLA CARD WITH UPDATED NPL (Y/[N])?
Enter Y to complete the update and wait for the following message to be
shown:
CLA initialization completed successfully.
5-17
TRUNK [0] 7100Ô
 In European systems Trunk is also designated ALS70/GID.

Designates a range of LS/GS, TWL and E&M trunk dial numbers beginning at a
trunk hardware ID number in the system. Numbers are given as a range
commencing with a START number and concluding with an END number.
(Enter Physical location: Shelf, Slot, CKT)
SLT [1]
Coral System Default Dial #s
Coral IPx Office 2000..2015
(Eu2: 3000..3015)
(Eu9: 4000-4015)
FlexiCom 400, 5000, 6000 2000..2319
IPx 500, 800, 3000, 4000 (Eu2: 3000..3319)
CDRS 200E (Eu9: 4000-4015)
Designates a range of Single Line Telephone station dial numbers for Magneto and
type 500 or 2500 SLT equipment, beginning at an SLT hardware ID number in the
system. Numbers are given in a range commencing with a START number and
concluding with an END number. (Enter Physical location: Shelf, Slot, CKT).
KEYSET [2]
Coral IPx Office 4000 Ô 4015
(Eu2:1000 Ô 1015)
(Eu9: 2000 Ô 2015)
FlexiCom 400, 5000, 6000 4000 Ô 4159
IPx 500, 800, 3000, 4000 (Eu2:1000 Ô 1159)

CDRS 200E (Eu9: 2000 Ô 2149)
Attendant (1st Keyset) 0
(Eu0, Eu3, Eu9: 9)
(Eu1: 11)
(Eu2: 99)
 FlexSet-IP 280S sets are defined in IP_KEYSET [41] (page 5-46).
Designates a range of keyset station dial numbers for FlexSets, CPA, DKT, DST,
EKT, AA, iCMC and GKT station equipment, beginning at station hardware ID
number in the system. Numbers are given in a range beginning with a START
number and concluding with an END number.
(Enter Physical location: Shelf, Slot, CKT).
5-18
KEYSET_V_PAGE [3]
Coral IPx Office 7400 Ô 7415 (Eu9:7400 Ô 7415)
FlexiCom 400, 5000, 6000 7400 Ô 7559 (Eu9:7400 Ô 7599)
IPx 500, 800, 3000, 4000
CDRS 200E
Designates a range of keyset voice page dial numbers (used to voice page a station),
beginning at a FlexSet, CPA, DKT, DST, EKT or GKT hardware ID number in the
system.
 FlexSet-IP 280S sets have their own Voice Page numbers defined by the
IP_KEY_VPG [44] (page 5-47) NPL type.
Numbers are given in a range commencing with a start number and concluding
with an END number. (Enter Physical location: Shelf, Slot, CKT).
TRUNK GRP [4] Any valid Trunk Group number (max: 8 digits);
Index # Default Dial #s

0 9 (Eu: 0)
1..9 81..89
10..15 7081..7085
Designates a range of trunk group dial numbers beginning with a Trunk Group
software ID number (Enter index number).
HUNT GRP [5]


FlexiCom 400, 5000, 6000
IPx 500, 800, 3000, 4000
CDRS 200E
Designates a range of hunt group dial numbers (ACD/UCD Groups) beginning at
a Hunt Group software ID number (Enter index number).
BOSS GRP [6]

FlexiCom 400, 5000, 6000
IPx 500, 800, 3000, 4000
CDRS 200E
Designates a range of boss group dial numbers beginning at a Boss Group software
ID number (Enter index number). Numbers are given in a range commencing with
a START number and concluding with an END number.
5-19
PUBLIC LIB [7]

FlexiCom 400, 5000, 6000
IPx 500, 800, 3000, 4000
CDRS 200E
Designates a range of numbers dialed to access specific public (system-wide)
speed call numbers, beginning at a Public Library software ID number (Enter index
number). Numbers are given as a range commencing with a START number and
concluding with an END number.
5-20
FEATURE [9] Designates a range of feature dial numbers beginning at a Feature software ID
number (enter index number). Dial the feature dial number to access or activate the
specific feature. The dial number can also be used to identify the feature for Keyset
button programming purposes.
Changing the dial number of a feature that can only be accessed or activated by a
Keyset/FlexSet button serves no useful purpose.
The following table presents the PI features currently available. Although the
default dial number can be changed, the index number remains as the feature
identification (this index number cannot be changed).
The table below lists the default feature dial and index numbers by dial numbers.
To view a list of the features by name in alphabetical order see Table 5-2.
 General notes for the table below:

• Features listed in bold type can only be operated by using a
programmed key.
• In Eu2 systems (Germany), all feature default dial numbers that
normally begin with the digit “1” are replaced with the “*” symbol as
the first digit.
• N/A (Not Applicable) means that the Default Dial Number is currently
not defined and therefore not in use.
*Station Type:
1. SLT: the feature is available for
SLT, FlexSet, FlexSet-IP 280S, P-Series, T207M, T208M, T207M/NP,
T208M/BL, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam,
third-party SIP terminal, DKT, DST, GKT, EKT and Attendant Stations.
2. Keyset: the feature is available for

FlexSet, FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL, DKT,
DST, GKT, EKT and Attendant Stations.
3. Attendant (ATT): the feature is available for
Attendant Stations only.
4. DSP: the feature is available for
Keysets with display units only.
5. Prog. Key: the feature is available for
Keysets and requires a programmed button.
5-21
Table 5-3: Feature Default Dial & Index Numbers
Default Index Feature Station Description

Dial codeJ num Type*
Not 219 Node ID# for N/A Defines a single and unique Node ID dial number
Available current node for the current Coral Network Node. This dial
number is used for the Path Replacement feature
and cannot be used by a station user.
Once this Node ID# is defined, it must be added to
the NPL of each of the other Network nodes as a
NETWORK [39] (page 5-45) number.
Not 220 Auto Set SLT Allows swapping station profiles between similar
Availablec Relocate sets, either temporarily or permanently.
See Auto Set Relocate (Portability) List per Device Type
on page 18-11.
#120 0 Speaker Keyset This function has a dual purpose and is dependent
Prog. Key upon system programming:
- Activates/Deactivates the speakerphone.
- Acts as a connect/release (on/off) key.
#121 1 Loop Keyset Defines a two-way loop key used to originate calls
Prog. Key or answer calls directed to the station number.
#122 2 XFER (Transfer) Keyset Initiates a transfer or a three-way conference call.

Prog. Key
#123 3 Forced Keyset Enables an attendant position to force the release

Release Prog. Key of a call after breaking in.
#124 4 Break-In Keyset Enables a user to break-in to an existing call (after

warning tone) by forcing a three-way conference
Prog. Key
call.
#125 5 Loop Originating Keyset Defines a one-way loop key to be used for
Only Prog. Key originating calls only.
#126 6 Boss/Secretary Keyset Defines a line key that is reserved for Boss Group
Line Prog. Key use.
#127 7 OCC or Tone Keyset Touch-Tone Dialing (DTMF) for Other Common
Prog. Key Carrier (OCC).
Enables a user to send additional digits (DTMF
tones) using the dial pad over non-DTMF trunks
and stations during any call (to trunk, to keyset,
3-Way Conference, Meet-Me Conference, etc.).
* see notes above on page 5-21
J Default Dial Numbers for Eu0, Eu1 & Eu2 systems are defined as:#( Index number + 100).

Not Available for T207M, T208M, T207M/NP, T208M/BL and FlexSet-IP 280S.
c
Not Available for SIP terminals (P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam softphone)
5-22

#128 8 Name to Dial Keyset Converts the displayed name to a dial number.
Number DSP
Display
Prog. Key
#129 9 Call Elapsed Keyset Shows the time elapsed since the origination or
Time Display DSP answer of a trunk call.
#1300 10 Stop Dial Keyset Forces the termination of a dial out situation,
Prog. Key thereby enabling an outgoing call to transfer to
another station and avoid the inter-digit delay.
#c N/A Stop Dial SLT
(during dialing)
#1303 32 Last Party Keyset Enables any one of the multi-party conference
Release Prog. Key members to release the last party that was added to
(Multi-Party the conference (excluding himself).
Conference
Only)
#1304 33 Group Call Keyset Allows the Group Call Operator, while still a
Operator-Add member of the group call, to add members to the
Member ongoing group call.
#1305 34 Group Call Keyset Allows the Group Call Operator, while still a
Operator- member of the group call, to release members from
Release the ongoing group call.
Member
#1306 35 Continuous Keyset Enables a 3way call group member to create a

Conference Prog. Key multi-party conference call regardless of the
from 3way initiator’s COS transfer key definition. Further
members may be added by using the Transfer key.
#131 11 Preference Keyset Enables a keyset station, while off-hook, to

select a specific line, trunk, trunk group or library
number.
N/A 12 Not Used
#133 13 Voice Page Keyset Enables control of the incoming voice page auto
Auto Answer answer feature. Allows the user to answer a voice
page call manually or handsfree.
#134 14 Voice Page Keyset Enables the incoming voice page feature to be
On/Off switched on or off (Do Not Disturb for voice page).

#135 15 Music On/Off Keyset Enables background music to be switched on or off.

c Not Available for SIP terminals (P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam softphone)
5-23


#136 16 Ring Level Keyset Used with station VOL keys to set the
ring level, cadence and ring type.
#137 17 Idle Display Keyset Enables switching the clock/date and station
On/Off DSP number display on or off, while the station is idle.
#138 18 Auto Answer Keyset Enables a keyset to control the auto answer feature
(auto answer on/off).
#139 19 Programming Keyset Enables the programming of keyset buttons. This

Button code may also be programmed directly by using the
key.
#1320 20 Mute Keyset Enables a keyset user to disable the handset or

Prog. Key speakerphone microphone during a call.
#1321 21 Exclude Keyset Enables a user to switch between a 3-way

Source Prog. Key conference and private conversation, with second
party, for split calls.
#1322 22 Exclude Keyset Enables a user to switch between a 3-way

Destination Prog. Key conference and private conversation, with
third-party, for split calls.
#1323 23 Handset/ Keyset Enables switching between the handset and

Speaker Prog. Key speakerphone.
#1324 24 Voicemail Keyset Enables the keyset user to program a button for
(Used only Sequence contacting Voicemail on an SLT. The sequence
in Version includes the SLT (Voicemail) dial number + #1324 +
10.19) the DTMF digits required by Voicemail device.
#1325 25 Calls Waiting Keyset Enables a keyset user with display to view the
Display DSP number of calls waiting to be answered.
Prog. Key
#1326 26 Not Used
#1327 27 Not Used
#1328 28 Multilingual Keyset Enables the user to set the keyset display
Display DSP language.

#1329 29 Multiple Music Keyset Enables the user to select the background music
Source from the multiple music sources.
Selection
J
Default Dial Numbers for Eu0, Eu1 & Eu2 systems are defined as:#( Index number + 100).

c
5-24

#1301 30 LED On/Off Keyset Enables the user to program a key to operate a
Prog. Key series of features while having the LED controlled
by the key pressing order.
#1302 31 Headset Only Keyset Enables the headset and disables the keyset
microphone and loudspeaker.
Note: Relevant for IP Keysets only when Headset
is connected.
N/A 32-49 Not Used
#140 50 Call Forward SLT Enables the user to forward calls to a defined
Busy destination if the user station is busy.
#141, #8 51 Call Forward SLT Enables the user to forward all calls to a another
All destination.
#142 52 Call Forward SLT Enables the user to forward calls to a another
No-Answer destination if a call to the user station remains
unanswered.
#143, (c) 53 Last Number SLT Enables the user to automatically redial the last
Redial external or internal number dialed. (The system can
redial the last internal number dialed only when
INTERNAL_LAST_NUMBER (Station Options,
[SFE,2]) is set to Yes.
#1440 54 Message SLT Enables the originator of a message to cancel the

Cancel message.

#145 55 Unattended ATT Enables an attended to implement the Do Not
Disturb feature. Since the user is defined as an
attendant, the display changes to unattended and
calls are rerouted to an unattended destination.
#145 55 Do Not Disturb SLT Enables a user to block calls to the station.
#146 56 Unattended ATT Enables an attendant to designate a station to

Station which calls are routed when the attendant station is
Destination Unattended.
#147, #2 57 Call Forward SLT Enables the user to forward calls to a designated
Busy/No Ans station if the user is busy or a call remains
unanswered.
#148 58 Phone Lock SLT Enables the user to lock the station dial (the entire
keypad is locked).

5-25

#149 59 COS Switchover SLT Enables the user to switch his Class of Service
between primary and secondary.
#150 60 Flash on trunk SLT Enables the user to send a hookflash signal
(Calibrated (Calibrated Opening) over a trunk.
Opening) Not available for P-Series, T207S, T208S,
T207S/NP, T208S/BL, T322, T328,
SeaBeam softphone, and third-party SIP terminal.
#151 61 Originate Only ATT Enables an attendant to permit any system station
Station the ability to make, but not receive calls.
#152 62 Terminate Only ATT Enables an attendant to permit any system station
Station the ability to receive, but not make calls.
#153 63 Block Station ATT Enables an attendant to block any station from
making or receiving any calls.
#154 64 Station ATT Enables an attendant to block any station from

Outgoing making any trunk calls.
Restriction
#155 65 Trunk Busy Out ATT Enables an attendant to “busy out” any system
trunk, effectively blocking all incoming or outgoing
calls on a specific trunk.
#156 66 Message ATT Enables an attendant to set Message Waiting at

Waiting any designated system station. The designated
station can then be defined as a “Hot Station” to the
attendant that initiated the Message Waiting feature.
#157 67 Trunk CO ATT Enables an attendant to display the trunks that are
Blocked Display blocked by the central office.
#158 68 Trunk Incoming ATT Enables an attendant to define a trunk as Incoming

Only only.
#159 69 Reserve Trunk ATT Enables an attendant to reserve any trunk or trunk
group to any designated station or station group.
#160 70 Hot Trunk ATT Enables an attendant to set a designated trunk to

Immediate this status. Trunk Operation is dependent upon the
Central Office.
#161 71 Hot Trunk ATT Enables an attendant to set a designated trunk to

Delayed this status. Trunk Operation is dependent upon the
Central Office.

5-26

#162 72 Trunk Drop No ATT Enables an attendant to implement this status at

Dial any designated trunk. The trunk is released if no
digits are dialed before the
time-out interval.
#163 73 Direct In Line: ATT Enables an attendant to designate a station, station

Night 1 group, or library as the destination for incoming
calls on each trunk when the system is in Night 1
mode.
#164 74 Direct In Line: ATT Enables an attendant to designate a station, station

Day Service group, or library as the destination for incoming
calls on each trunk when the system is in the Day
mode.
#165 75 Direct In Line: ATT Enables an attendant to designate a station, group,

Night 2 or library as the destination for incoming calls on
each trunk when the system is in the Night 2 mode.
#166 76 Hot Station ATT Enables an attendant to define a station as a “Hot

Immediate Station Immediate” (immediate ringdown), and
designate a destination station.
#167 77 Call Forward ATT/Boss Enables an attendant or boss group member

Busy Group forward all calls of a busy station or boss group to
Destination another destination.
#168 78 Call Forward All ATT/Boss Enables an attendant or boss group member to
Destination Group forward all calls of a station or group
(ACD/UCD/Boss) to another destination.

#169 79 Call Forward ATT/Boss Enables an attendant or boss group member to
No-Answer Group forward unanswered calls of a station or boss group
Destination to another destination.
#170 80 Executive SLT Enables a station user to temporarily apply his/her

Privilege station’s Executive Privilege COS.
This dial number, when defined as a DID group dial
number, can also be used in conjunction with the
Freedom feature (IRSS) to enable IRSS calls from
off-site phones that do not possess a Caller ID
number, see EXEC_PRIV [34] (page 7-13).
#171c, #4c 81 Call Hold SLT Enables a station user to place a call on hold.
Not available for P-Series, T207S, T208S,
T207S/NP, T208S/BL, T322, T328, SeaBeam
softphone, and third-party SIP terminals.

5-27

#172 82 Reminder SLT Enables a station user to ring the station at specific
times.
#173 83 Wakeup SLT Enables a station user to ring the station at specific
times.
#174 84 Not used
#1740 203 Malicious Call SLT Enables the station user to activate a Call Trace
Trace record.
#1741 204 Malicious Call SLT Enables the station user to print the Call Trace
Print record.
#1742 205 Malicious Call ATT Enables the Attendant to activate Call Trace records
Trace for one or more stations.
#1743 206 Malicious Call ATT Enables the Attendant to print Call Trace records for
Print one or more stations.
#1744c 207 Whisper Page - SLT Enables a user to Whisper Page another party
Announcing engaged in an ongoing conversation.
T207S/NP, T208S/BL, T322, T328,
SeaBeam softphone, and third-party SIP terminals.

#1745 c 208 Whisper Page - SLT Enables a user to deny any Whisper Pages to
Do Not Disturb his/her station.
#1746 209 ACD Group, ATT Enables the Attendant to define the maximum
Max Calls number of waiting calls for an ACD group.
Waiting for Busy

ACD
#175, #5 85 Message SLT Enables a station user to leave a message

indication at any designated station. Also allows
keyset users access to the message list.
#176 86 Camp On - SLT Enables a station user to queue to a busy or ring-no

(Call Back) answer (RNA) station or busy trunk.
#17700 87 Security SLT Enables a station user to block against trunk

camp-on or break-in to his station.
#17701 221 CF Busy SLT Enables the user to forward external calls only to
- External another destination if the station is busy.
#17702 222 CF All SLT Enables the user to forward all his/her incoming
- External external calls to a another destination.
J
 Not Available for T207M, T208M, T207M/NP, T208M/BL and FlexSet-IP 280S.
c
5-28

#17703 223 CF No Answer SLT Enables the user to forward his/her incoming
- External external calls to another destination when the user’s
station is not being answered.
#17704 224 CF Timed SLT Enables the user to forward all his/her incoming
- External external calls to another destination during system
defined time periods.
#17705 225 CF Busy/NoAns SLT Enables the user to forward all his/her incoming
- External external calls to another destination when the
station is not answering or is busy.
#17706 226 CF Busy ATT/Boss Enables an attendant or boss group member to

- External Group forward external calls of a busy station or boss
group to another destination.
#17707 227 CF All ATT/Boss Enables an attendant or boss group member to

- External Group forward all external calls of a station or group
(ACD/UCD/Boss) to another destination.
#17708 228 CF No Answer ATT/Boss Enables the attendant or boss group member to
- External Group forward external calls of a non-answering station or
boss group to another destination.
#17709 229 CF Timed ATT/Boss Enables the attendant or boss group member to
- External Group forward external calls of a station or group
(ACD/UCD/Boss) to another destination at
pre-determined system time intervals.
#17710 230 FlexiCall All SLT Enables a station user to define an additional Coral
or non-Coral system telephone as a remote

destination. This feature causes all the station
user’s calls to arrive at both destinations. Answering
the call at one destination stops the other
destination from ringing.
#17711 231 FlexiCall SLT Enables a station user to define an additional Coral
Internal or non-Coral system telephone as a remote
destination. This feature causes all the internal calls
arriving at the station to arrive also at the remote
phone destination. Answering the call at one
destination stops the other destination from ringing.

5-29

#17712 232 FlexiCall SLT Enables a station user to define an additional Coral
External or non-Coral system telephone as a remote
destination. This feature causes the all the external
calls arriving at the station to arrive also at the
remote phone destination.
Answering the call at one destination stops the
other destination from ringing.
#17713 233 Follow-Me SLT Enables a user to collect his/her external calls at
-External another system station.
#17714 234 Individual SLT The IRSS feature, also known as Freedom, allows a
Remote System user to define an off-site phone with the capability
Services (IRSS) of dialing into the Coral and becoming a virtual
Freedom Coral station for the duration of the call.
#17715c 237 Multi-Level SLT The Multi Level Precedence and Preemption
Precedence and (MLPP) service allows ranked Coral users (graded
Preemption from 1 to 4) to prioritize calls causing calls with a
(MLPP) lower priority to be dropped when resources are low
or when the call is of higher precedence than
routine calls on a per call basis.
T207S/NP, T208S/BL, T322, T328,
#17716 238 Group Call- SLT Defines a Group Call Operator that can continue to
Define Operator be an active member of the group call when adding
or releasing members.
#17717 239 Call Forward SLT Assigns a Call Forward Destination for stations in
Undefined an Undefined call state (cannot be defined by ATT):
• FlexIP SoftPhone or IP stations/trunks which have
lost their Primary Call Agent because of Network or
UGW card problems.
• FlexIP SoftPhone users not currently connected to
a Network
• Unplugged FlexSets/Keysets
• SLTs connected to extracted Line Cards or
Malfunctioning Cards
c
5-30

#17718 240 ELA Line Key - Keyset Enables the ELA group member to program ELA
Programming Line Keys at his station.
ELA SLT Enables an ELA group member to login to a

Personal/Depart Personal or Departmental group, in order to
mental Log activate/de-activate a station membership.
IN/Out
#178 88 Auto Redial Keyset Enables a station user to activate the system
(ACNR) automatic redial feature.
• Version 16 or higher (applicable on PRI and SIP
trunks, while other trunk type requires an an 8DTD,
8DRCM, 8DRCM-2, 8DRCF or
U-RMI/U-MR Office card with dial tone detectors
installed in the system to activate this feature).
• Version 15 (all trunks type require an 8DTD,
8DRCM, 8DRCM-2, 8DRCF or
U-RMI/U-MR Office card with dial tone detectors
installed in the system to activate this feature).
• Version 14 or lower (all trunks type require an
8DTD, 8DRCM, 8DRCF or U-RMI/U-MR Office
card with dial tone detectors installed in the system
to activate this feature).
#179 89 Passcode SLT Enables a station user to change the 4 digit

Change passcode.

#180, 77 90 Dial Call Pickup: SLT Enables a station user to answer a ringing station
Directed by dialing this code and then the ringing station dial
number.
#181, 76 91 Dial Call Pickup: SLT Enables a station user to answer a ringing station
Group by dialing a group code.
#182 92 Hot Station ATT Enables an attendant to define a station as “Hot

Delay Station Delay” (ringing after first digit time-out).
#183, #7, 93 Call Park SLT Enables a station user to park a call and pick it up
79 at any system station.
P-Series, T207S, T208S, T207S/NP, T208S/BL,
T322, T328, SeaBeam softphone, and
third-party SIP terminals cannot “Park” a call.
However, they may pick up the parked call.

c
5-31

#184 94 Night-2/Day ATT Enables an attendant to switch the system between

Transfer Day and Night 2 mode.
#185 95 Night-1/Day ATT Enables an attendant to switch the system between

Transfer Day and Night 1 mode.
#186, #6 96 Privacy SLT Enables a member of a Boss Group to activate

(Boss Group) Boss line privacy at the user station, preventing
another member of the Boss Group from joining an
in progress call on a Boss line.
#187 97 Exclusive Hold SLT Enables a member of a Boss Group to

(Boss Group) activate the Boss line exclusive hold at the user
station, to be answered only at the user station.
T207S/NP, T208S/BL, T322, T328,
#188 98 Time and Date ATT Enables an attendant to set the system time and
Setting date.
#189 99 Follow Me SLT Allows a station user to reroute calls intended for a
designated station to the station invoking this
feature.
#190 100 Trunk Outgoing ATT Enables an attendant to limit a trunk's use to
Only outgoing calls only.
#191, #3 101 Voice Page SLT Enables a station user to voice page any other
system keyset station.
#192, 78 102 Night Answer SLT Enables a group member to answer a call directed
Bell/UNA Pickup to the UNA bell.
Group
#193 103 Private Library: SLT Enables a station user to add, delete, or change
Programming information in the Private (station speed call)
Library.
#194 104 Public Library: ATT Enables an attendant to add, delete, or change
Programming information in the Public (system-wide speed call)
Library.
5-32

#195c 105 Series SLT When transferring a call, use the Series function to
have the caller return to you after the transferred
call is completed.
T207S/NP, T208S/BL, T322, T328,
#196c, #9c 106 Saved / Repeat SLT Enables saving and/or redialing the last number
Number dialed.
T207S/NP, T208S/BL, T322, T328,
N/A 107 Not used
#1980 108 Wakeup ATT Enables an attendant to set a wakeup time for any
designated system station.
#1990 109 Account Code SLT Enables the user to dial an account code per client,
before or during the call, in order to print out call
statistics. The code designated calls are assigned to
a particular client account, instead of to a telephone
number.
Keyset To enter an Account Code during a conversation

Prog. Key without placing the caller on hold:
• Create a DSS key for this feature to be used during
a call.
• Set ON LINE ACCOUNT CODE [29] (page 6-27) in SFE,2

to Yes.
7010-7025 110 - Room Status / ATT Enables an attendant access to the

125 Canned Room Status/Canned Messages features.
Messages NOTE: see Table 16-1 Room Status / Canned Message
- Names and Access Codes on page 16-4.
7026-7041 126 - Room Status / SLT Enables a user access to the Room Status/Canned
141 Canned Messages features.
Messages NOTE: see Table 16-1 Room Status / Canned Message
- Names and Access Codes on page 16-4.
#1991 142 Release/Resume SLT Enables a member of a Hunt Group to temporarily

from UCD Hunt remove their station (release) from a designated
Group
group, and also add the station back (resume).

5-33

#1992 143 Not used
#1993 144 Day/Night ATT Enables an attendant to switch the system between
Transfer manual and automatic (on time) day/night transfer.
(auto/manual)
#1994 145 Directory Keyset Enables the user to search the Directory as well as
DSP to use its contents to place calls.
Not 37 Directory: Keyset Enables the keyset user to toggle between entering
Available Alphanumeric DSP digits or characters via the Keyset dial pad for use
(only from Mode with the Directory.
Directory) This feature requires a programmed button.
Not 45 Directory: Keyset Enables keyset users to toggle between upper and
Available Lower/UpperCase lower case letters being entered via the keyset dial
CAPS LOCK DSP
(only from pad for use with the Directory.
Directory) This feature requires a programmed button.
N/A 146 Not Used
#1996 147 KB0 Setup ATT Enables a technician to reconfigure the KB0
Keyset program interface data terminal port.
DSP
Prog. Key
#1997 148 Alarm ATT Enables an attendant access to the system alarm
Keyset message list.
DSP
Prog. Key
N/A 149 - Not used

153
#1998 154 Trunk ATT Enables an attendant to activate/deactivate

Autoguard autoguard on a trunk.
#1999 155 Don't Disturb ATT Enables an attendant to activate Do Not Disturb on
any designated station.
N/A 156 Not used
#1970 157 Check In/Out ATT Enables an attendant to set room station to
check-out or check-in state.

c
5-34

#1971 158 Wakeup Report ATT Enables an attendant to send existing

wakeup reports to a printer.
N/A 159 - Not used

160
N/A 161c Serial Library SLT Enables the addition of a fifth digit to a public library
Prefix numbering plan.
#1972 162 Call Charge ATT Enables an attendant to send the Call Charge Print.
Print
#1973 163 Load ID SLT Enables an ACD member to enter his ID when
(ACD Hunt entering the system.
Group)
#1974 164 Log In/Out SLT Enables an ACD group member to Log In/Out of the
(ACD Hunt system.
Group)
#1975 165 Release from all SLT Reinstates an ACD/UCD group member that was
ACD/UCD Hunt automatically released (if AUTO_RELEASED_ALL
Groups [19] (page 9-9)-SLT or AUTO_RELEASED_ALL
[19] (page 9-36)-KEY is set to Yes) while the member
was inactive for one call or more.
#1976 166 Wrap Up Time SLT Enables an ACD/UCD group member to

(ACD/UCD Hunt activate/deactivate Wrap-Up Time on his station.
groups)
#1977 167 Wrap Up Code SLT Enables ACD group member to send a Wrap-Up

(ACD Hunt code to the PC-ACD or FlexCT Server.
Group)
#1978 168 Call Charge ATT Enables an attendant to reset and print the
Reset with accumulated call charge table.
Printout
#1979 169 LAR Block ATT Enables an attendant to block/unblock trunks and/or
Dial Services and thereby reroute calls.
N/A 170 Not used

5-35

#1981 171 Silent Monitor SLT Enables authorized station users to silently monitor
(2-Way) other ports (both conversing ports are monitored
 From Coral version 16.02.03 it is available

simultaneously).
also for P-Series, T300 Series, and

SeaBeam softphone.
#1982 172 ACD Calls Keyset Enables the station user to view the number of
Waiting Display DSP waiting calls on an ACD group.
#1983 173 Conference SLT Enables the station user to release a conference
Release/Inspect participant.
#1984 174 Call Forward ATT/Boss Enables an attendant or boss group member to
Timed Group forward all calls of a station or group
(ACD/UCD/Boss Group) to another destination at
pre-determined system time intervals.
#1985 175 Call Forward SLT Enables a user to forward calls to a designated
Timed station according to system-wide defined periods.
#1986 176 Port Information Keyset Enables manufacturer’s programmers to display
 Not Applicable used from Coral version

DSP relevant information about a specific port.
16.01.16
#1987 177 Party Keyset Enables manufacturer’s programmers to display
Information on relevant information about parties connected to a
DSP
Ports specific port.
#1988 178 Dump SLT Enables manufacturer’s technicians to download

defined memory areas.
#1989 179 DC No Call SLT Enables manufacturer’s technicians to activate a

single cycle of corrective diagnostics.
N/A 180 - Not used

185
CC1: 3999 186 DID Test DID Used by the CO in order to check the DID line. A
(Eu1,Eu2: Number successful test results in a 3-second DIAL_TONE.
#286) Used only in CC1, Eu1 and Eu2 systems when either
8DID, 8BID or 8GID cards are installed.
J

c
5-36

N/A 187 - Not used

189
#1441 190 Conference Keyset Locks out additional members from joining an
Lock ongoing regular Meet-Me conference.
This feature requires a programmed button.
#1442 191 Primary Login SLT Enables an ACD group member to login to a
(ACD Hunt primary group in order to receive all queuing calls
Group) on that group before receiving calls from other
groups.
#1443 192 HELP Keyset Enables a keyset station user to call another keyset
Prog. Key station equipped with a display for help, without
disrupting the call in progress.
This programmed button is used also for “Request
to Speak” in a Group Call Conference.
#1444c 193 Calling ID SLT While making outgoing ISDN calls, Calling ID
Control Control allows/restricts presentation of the calling
party's phone number, possibly with additional
address information to the called party.
T207S/NP, T208S/BL, T322, T328,
#1445 194 Divert Call Keyset Enables a keyset station user to divert an incoming
Prog. Key call to another destination without answering the
call.

#1446 195 Group Call- SLT Enables authorized station users (COS: LARGE_
Release of a CONF_FORC_REL [52] on page 7-17) to force release
Participant a Group Call Participant.
#1447 196 Group Call- SLT Enables authorized station users to terminate (force
Release release) a Group Call (all the chained Group Calls
or just one of the Group calls in the chain).
To use this feature, NEXT GROUP (page 10-36) must be
defined for the Group calls involved.
J

c
5-37

#1448c 197 Silent Monitor- SLT Enables authorized station users to silently monitor
(1-way) Splitting one conversing port at a time.
SAU Requirement SPLIT MONITOR on page 3-23
to enable this feature .
 From Coral version 16.02.03 it is available

also for P-Series, T300 Series, and
SeaBeam softphone.
#1449c 198 Group Call- SLT Enables authorized station users to establish a
Temporary temporary Group Call containing no predefined
Group Call members. The members are added by the call
initiator while initiating the call. To use this feature,
ADD_ON (page 10-32) must be set to Yes.
N/A 199 Large Public SLT Enables the addition of up to eight digits to a large
Library Prefix public library numbering plan.

5-38
EDIT [10] The manufacturer recommends no change to defaults.

Edit functions may be used:
• to activate or deactivate codes
• for system dial format commands
• with the scanner feature
Enter the required editing function index number.
Table 5-4: Edit Feature Default Dial & Index Numbers
Default Dial Index Feature Station Description

No. No. Type*
#8 0 Assign Priority Keyset Enables assigning a priority level to an

(ACNR) automatically repeated dialing number (ACNR).
#9 1 Cancel Priority Keyset Enables canceling a priority level to an

(ACNR) automatically repeated dialing number (ACNR).
#0, #10 2 Cancellation Code SLT Cancels the activation of a feature.

(#0, 0,
Eu1,Eu2)
#1, #11 3 Activation Code SLT Activates a feature.

(#1, 1,
Eu1,Eu2)
#2 4 Scroll advances in Keyset Advances through a scroll list one step at a
discrete steps time. Use the up VOL key on a keyset.
Used to scroll forward (Next) port by port
through available ports. While scrolling, the
port name/number appears on the top line.

#3 5 Fast scroll advance Keyset Advances rapidly (FastUp) to the next
assigned feature in a scroll list.
#4 6 Scroll backward in Keyset Advances backwards through the scroll list one
discrete steps step at a time. Use the down VOL key on a
keyset.
Used to scroll backward (Previous) port by port
through available ports. While scrolling, the
port name/number appears on the top line.
#5 7 Fast scroll backward Keyset Allows rapidly going backward (FastDown) to
the previously assigned feature in a scroll list.
#6 8 Stops (freezes) Keyset Temporarily bans redial access an

(ACNR) number dialing automatically repeated dialing number (ACNR).
#7 9 Restarts Keyset Allows restarting a number that has been

(ACNR) number dialing previously frozen by pressing #*6 when repeat
dial is activated.
* see notes on page 5-21.
5-39
BELL [11] 7050 Ô 7059

Central Bell/UNA Relay, RLY2 designates a range of bell dial numbers. One Bell
circuit per card. (Enter Physical location: Shelf, Slot, CKT).
CKT Card Type
24 8DRCM-2
24 8DRCM
24 8DRCF
8 ASU
24 IPx 500M main Cage on the motherboard (Shelf #0, Slot #13)
24 CDRS 200E on the motherboard (Shelf #0, Slot #13)
8 RMI
24 IPx Office U-RMI/U-MR/RMI/MR (Shelf #1, Slot #6)
PAGE [12] 7074 Ô 7079

Public Address/Page Port, RLY1 designates a range of external page dial numbers.
One Page circuit per card. (Enter Physical location: Shelf, Slot, CKT).
CKT Card Type
23 8DRCM-2
23 8DRCM
23 8DRCF
7 ASU
24 IPx 500M main Cage on the motherboard (Shelf #0, Slot #13)
24 CDRS 200E on the motherboard (Shelf #0, Slot #13)
7 RMI
23 IPx Office U-RMI/U-MR/RMI/MR Office (Shelf #1, Slot #6)
• The PAGE number is irrelevant when the 2nd Music Source is used by
the RMI, U-RMI/U-MR/RMI/MR Office card. The caller receives an
ILLEGAL message and a reorder tone.
5-40
MODEM [13] 7070 Ô 7073 (CC0: NONE, Eu9: 7070 Ô 7071)

Designates a range of modem dial numbers in the system. (Enter Physical location:
Shelf, Slot, CKT).
CKT Card Type
26 8DRCM*
26 8DRCF
26 IPx 500M† main Cage (Shelf #0, Slot #13) on the motherboard
(applicable for MSBipx Hardware Issue-0220X1003 or lower)
3 RMI
26 IPx Office (Shelf #1, Slot #6) U-RMI Office/RMI Office
* Modem is not available on 8DRCM-2 card.
† IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not include a MODEM.
The modem was standard in MSBipx Hardware Issue-0220X1003 or lower.
DID_NUMS [14]
FlexiCom 400, 5000, 6000 (Eu2: 76XX)
IPx 500, 800, 3000, 4000 (Eu9: 7600 Ô 7607
CDRS 200E
 8GID and ALS70-DID (Eu systems) are defined in TRUNK [0] (page 5-18).
Designates a range of direct inward dial (DID) trunk numbers beginning with a
DID trunk hardware ID number in the system. These numbers are used exclusively

for identifying the trunk for system programming purposes, and do not affect
incoming trunk digits. Numbers are given in a range beginning with a START
number and ending with an END number. (Enter physical location: Shelf, Slot, CKT).
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l.
DATA_PORT [16] Not Used (No Longer Available)

PRIVATE_LIB [19] 7000 Ô 7009

Eu1: 90 Ô99
Designates a range of private library dial numbers used to access private

(station-specific) speed call numbers, beginning at a Private Library software ID
number (Enter index number). Numbers are given as a range commencing with a
START number and concluding with an END number.
5-41
KEYSET_Z_PAGE [20] 7300Ô7309

Eu9: 5500 Ô 5509
Keyset Zone Page designates a range of zone page dial numbers to voice page a
group of EKT, VDK, DKT, DST, GKT, CPA, FlexSet 120/280/121/281 series,
FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL, beginning at a Zone Page
software ID number (enter index number). Numbers are given as a range
commencing with a START number and concluding with an END number.
RELAY [21] 7086 Ô 7097
 Numbers 7092-7097 are not used; these numbers can be removed if

required for other features.
Designates a range of dial select/alarm relay RLY3 dial numbers in the system. One
Relay per Card. (Enter physical location: Shelf, Slot, CKT).
CKT Card Type
25 8DRCM-2
25 8DRCM
25 8DRCF
9 ASU
25 IPx 500M main Cage (Shelf #0, Slot #13) on the motherboard
25 CDRS 200E main Cage (Shelf #0, Slot #13) on the motherboard
9 RMI
25 IPx Office (Shelf #1, Slot #6) U-RMI/U-MR/RMI/MR Office
DATA_USER [22] Not Used (No Longer Available)
DATA_GRP [23] Not Used (No Longer Available)
5-42
CONF [30] 7098 Ô 7099

Designates a range of multi-party conference port dial numbers. The conference
ports are used also to establish Group calls (see CONF # on page 10-31).
(Enter physical location: Shelf, Slot, CKT).
CKT Card Type
16 8DRCM-2
16 8DRCF
16 8DRCM
0, 1 CNF Card (defined as CONF in Card List on page 6-59)
48-53 IPx Office (Shelf #1, Slot #7: URC2) U-RMI/U-MR Office.
For the range of CKTs, see Meet Me on page 4-38.
16 IPx 500M main Cage (Shelf #0, Slot #13) 8DRCF
(MSBipx Hardware Issue-0100X1000, 8DRCF)
48-53 IPx 500M main Cage (Shelf #0, Slot #14) URC2
(MSBipx Hardware Issue-0200X1000 or higher, RMI-F/URC2).
48-53 CDRS 200E main Cage (Shelf #0, Slot #14) URC2
N/A MRC (Not applicable the the current version)
DVMS_MSG [31] 5400 Ô 5499 (Eu2, Eu9: 79XX)

CC1: FlexiCom200: N/A
 When installing a 4VSN card, it is advisable to reduce the default range

to 32 numbers, by removing numbers 5432 Ô 5499, so that the default is
5400 Ô 5431
Designates a range of DVMS messages denoted by ID numbers (Enter index
number) used to hear the messages. Numbers are given in a range commencing
with a START number and concluding with an END number. The END number is
limited by MAX_DVMS_MSG [9] on page 6-46 [SFE,7]. For additional information,
see Chapter 23 Special Port Facilities.
For Example: The default number 5403 is the access dial number for the 4th
message (i.e. index #3) on all installed 4VSN cards.
5-43
DVMS_PORTS [32]
FlexiCom 400, 5000, 6000
IPx 500, 800, 3000, 4000
CDRS 200E
Designates a range of 4VSN (Voice Synthesizer Facility) dial number card ports
with four ports per card. (Enter physical location: Shelf, Slot, CKT). For additional
information, see Chapter 23, Special Port Facilities.
PAGE_Q [33] 7060 Ô 7069

Designates a range of page queue dial numbers beginning at a Page Queue software
ID number (Enter index number). The maximum amount of Page_Q ID numbers is
limited by PAGE_Q (page 4-17).
P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam softphone,
and third-party SIP phones cannot place call in Page Que. However, they may pick
up the call.
MODEM_POOL [34] Not Used (No Longer Available)
GROUP CALL [35] 5600 Ô 5603

Designates a range of numbers assigned for preset conference calls. Group Calls
consist of one or more Conference Ports and up to 100 stations or trunks.
(Enter index number).
DIAL_SERV [36] 4850 Ô 4865

Eu2: 9250 Ô 9265
Eu9: 7020 Ô 7035
CC1 (all other systems): 7020 Ô 7035
Designates a range of dial service dial numbers (used for outgoing calls) beginning
at a DIAL SERVICE Software ID number (enter the index number).
ROUTING_ACC [37] 80, 7080

Designates a range of Routing Access Dial numbers (used for making outgoing
calls) beginning at a ROUTING ACCESS software ID number (enter the index #).
5-44
WAIT_QUE [38] Range: Any valid Dial Number (max: 8 digits); No Default values
Eu9: 5605 Ô 5609
Designates a range of WAIT_QUE dial numbers beginning at a WAIT_QUE

Software ID number (enter the index number) for CoraLINK applications. Calls
are routed to this destination while awaiting routing access (from an external or
internal source).
! Warning:
Modifying the NPL (port numbers only-not feature numbers) causes:
1. An initialization of the CLA or CLA-ATS card.
Before the update is performed, the following message prompts:
INIT CLA CARD WITH UPDATED NPL (Y/[N])?
Enter Y to complete the update and wait for the following message to be
shown:
CLA initialization completed successfully.
NETWORK [39] Any valid Dial Number (max: 8 digits);

Designates a range of NETWORK dial numbers. The dial numbers are displayed
against the Node # that they relate to within the Coral Network.
A Node # must be entered for each dial number added as this NPL type.
The Node # must be defined first, see Node NPL (page 28-10).
WIRELESS [40] Any valid Dial Number (max: 8 digits);

No default is presented when WIRELESS is defined as 0 in Sizes;
5701 Ô 57xx where xx=WIRELESS (page 4-9)
Designates a range of dial numbers for the following wireless handsets:
• CoralAIR
• FlexAir
An index number is assigned (by the system) for each dial number. Each handset
comes with a specific Electronic Serial Number (ESN) that belongs to the
particular handset. The handset ESN must also be entered in the Wireless Stations
- CoralAIR (page 9-123) branch (WST, 0), otherwise the handset is inoperable.
 At each handset, the specific index number assigned by the Coral system
must be entered into the HID # 0 field in the SYSTEM CONFIG. menu of
the handset (See the relevant Coral Installation Manual for details).
5-45
IP_KEYSET [41] Any valid Dial Number (max: 8 digits);

No default is presented when KEYSETS_IP is defined as 0 in Sizes;
5800 Ô 5859
Designates a range of dial numbers for the following IP Keysets:
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
An index number is assigned (by the system) for each dial number (no shelf, slot
and circuit numbers are needed for IP Keysets).
Additionally, each IP Keyset has its own hardware identification MAC address.
The MAC numbers must be previously defined in the IP Stations branch (see IP_
Keyset beginning on page 29-28) to initialize the keysets.
IP_SLT [42] Any valid Dial Number (max: 8 digits);

No default is presented when IP_SLT is defined as 0 in Sizes;
5860 Ô 5879
Designates a range of dial numbers for IP SLT, via Third Party MGCP gateways,
Coral Teleport/FXS interface unit circuits. An NPL index and circuit number is
assigned (by the system) for each dial number. The NPL index number is the
ENTRY # for the FXS unit defined in IP: Telephony Gateway (Coral
Teleport) (page 29-62). One circuit number is assigned for each port on the FXS
unit.
For Example: The first FXS box entered is labeled ENTRY#=3 and includes 4
ports (i.e. IP: Telephony Gateway (Coral Teleport): TYPE [1] = 2 or 3). The NPL
automatically assigns 4 dial numbers for this NPL type displayed as follows:
DIAL NUMBER INDEX/CKT

5860 3/0
5861 3/1
5862 3/2
5863 3/3
Additionally, each FXS unit has its own hardware identification MAC address. The
MAC numbers must be defined in IP: Telephony Gateway (Coral
Teleport) (page 29-62) to initialize the units.
5-46
IP_LGS [43] Any valid Dial Number (max: 8 digits);

No default is presented when IP_LGS is defined as 0 in Sizes;
5880 Ô 5899
Designates a range of dial numbers for IP LGS, via Third Party MGCP gateways,
Coral Teleport/FXO interface unit circuits. An NPL index and circuit number is
assigned (by the system) for each dial number. The index number is the ENTRY #
for the FXO unit defined in IP: Telephony Gateway (Coral Teleport) (page 29-62).
One circuit number is assigned for each port on the FXO unit.
For Example: The first FXO box entered is labeled ENTRY#=2 and includes 4
ports (i.e. IP: Telephony Gateway (Coral Teleport): TYPE [1] = 2 or 3). The NPL
automatically assigns 4 dial numbers for this NPL type displayed as follows:
DIAL NUMBER INDEX/CKT
5880 2/0
5881 2/1
5882 2/2
5883 2/3
Additionally, each FXO unit has its own hardware identification MAC address.
The MAC numbers must be defined in IP: Telephony Gateway (Coral
Teleport) (page 29-62)) to initialize the units.
IP_KEY_VPG [44] Any valid Dial Number (max: 8 digits);

No default
Index numbers begin at 0 and end at one less than the number of
IP keysets defined in KEYSETS_IP (page 4-7) in Sizes.

Relevant only for the following IP Keysets:
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
Designates a range of IP keyset voice page dial numbers (used to voice page a
station) based on the IP keyset’s index number in the system (and not according to
its physical location, because the physical port is a virtual one on the UGW card).
5-47
IP_NET [45] Any valid Dial Number (max: 8 digits);

No default is presented when NET_IP is defined as 0 in Sizes;
Default: 5900 Ô 5929
Defines IP Network trunk type dial numbers. IP_NET (also known as NET_IP)
stands for Tadiran proprietary QSIG over IP solution. IP_NET has the same
functionality as the QSIG except IP_NET ports are used instead of a PRI card.
Programming a QSIG network with UGW is virtually the same as with PRI trunks.
The only difference is that the PRI Trunks are replaced with IP_NET ports on the
UGW cards. These IP_NET ports accept regular Trunk numbers that can be
defined in a regular Trunk Group. Dial Service is the same as in a regular QSIG
application, except that the destination will be an IP address.
There are two ways in which the IP_NET can be implemented on an IP network.
One is within the LAN/WAN, and the other is on the public Internet.
Designates a range of dial numbers for IP Network ports. An index number is
assigned for each dial number (no shelf, slot and circuit numbers are needed for IP
trunks).
SIP_TERMINAL [46] Any valid Dial Number (max: 8 digits);

No default is presented when SIP_Terminal is defined as 0 in Sizes
Define the following SIP terminals type dial numbers:
• P-335, P-450 (that start with MAC address 000a6b)
• T207S, T208S, T207S/NP, T208S/BL
• T322, T328
• LxCMC (voicemail)
• SeaMail (voicemail)
• SeaBeam softphone
 Relevant only for P-335, P-450, T207S, T208S, T207S/NP, T208S/BL,T322,

T328 sets, SeaBeam softphone and other third-party SIP phones approved
by the Coral manufacturer.
Designates a range of dial numbers for SIP Terminals. An index number is assigned
for each dial number (no shelf, slot and circuit numbers are needed for SIP
terminals).
5-48
SIP_TRUNK [47] Any valid Dial Number (max: 8 digits);

No default is presented when SIP_Trunk is defined as 0 in Sizes
Define SIP Trunk type dial numbers.
Designates a range of dial numbers for SIP Trunks. An index number is assigned
for each dial number (no shelf, slot and circuit numbers are needed for SIP trunks).
DYNAMIC_CONF [48] Any valid Dial Number (max: 8 digits);

No default is presented when DYNAMIC_CONF (on page 4-17) is defined as
0 in Sizes
 Dynamic Conference is not applicable in the current version.

Designates a range dial numbers for Dynamic Conference ports supported and
allocated by the MRC (Media Resource Card). An index number is assigned for
each dial number (shelf, slot and circuit numbers are not used).
5-49
Special Feature Codes ç NPL,1 [0,0,5,1]
This option is used to set the dial numbers for special features such as Camp on,
Snooze, Message, etc. Any single dial number can be used only once.
 Notes:
• A special feature code is always activated in response to an
implemented feature or after a hookflash (not applicable for P-Series,
T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam softphone,
and third-party SIP terminals) to initiate a feature. Therefore, no
conflict exists between the Special Feature number and the General
Numbering Plan.
• Only one number (between 0 and 9 or * and #) can be utilized per
feature. When an attempt is made to define another feature with an
existing code, the feature code is erased and a question mark (?) is
displayed instead. This allows you to then enter another number.
• If you attempt to define a feature with a number that was previously
used, the following message appears:
# Plan Err, TRY AGAIN
Enter an undefined number and continue.
BREAK_IN Any one (single digit) of the following: , #, 0..3..9 inclusive, or N (for none)
Used to activate the break-in (forced 3-way conference) feature to an existing
conversation following warning tone. This option is also used to activate DND
override.
CAMP_ON (Callback) Any one (single digit) of the following: , #, 0..2..9 inclusive, or N (for none)
Special Feature Codes NPL,1 [0,0,5,1]
Used to activate the camp-on feature to a busy or unanswered (Ring/No Answer)

station or busy trunk. Also used for queue on-hook for Routing Access or network
purposes.This is generally known as a Callback feature.
MSG Any one (single digit) of the following: , #, 0..5..9 inclusive, or N (for none)
Used to allow the user to leave a message at a busy or unanswered station (Ring/No
Answer).
SNOOZE Any one (single digit) of the following: , #, 0..4..9 inclusive, or N (for none)
Instructs the system to repeat a wakeup or reminder ring after the time-out interval
set in the Feature Timer option.
5-50
ATT_MSG Any one (single digit) of the following: , #, 0..7..9 inclusive, or N (for none)
Attendant Stations Only
Used when leaving a message indication from the Attendant Console at a busy or
unanswered station.
V_PAGE Any one (single digit) of the following: , #, 0..6..9 inclusive, or N (for none)
Used to voice page a busy or idle keyset.
For Voice Paging Network Stations, dial its Voice Page number (Hookflash 6
cannot be used to activate Voice Page for Network stations).
SILENT_MON Any one (single digit) of the following: , #, 0..9 inclusive, or N (for none)
SAU Requirement
Silent Monitoring (2-Way) is used to monitor any system port (except data and
conference) in any state, without audio or visual warning to the monitored party.
CAMP_OFFHK Any one (single digit) of the following: , #, 0..8..9 inclusive, or N (for none)
Used to camp-on a busy station as multi-appearance.
This feature is also known as CALL WAITING or Call Offer by other
manufacturers.
Special Feature Codes NPL,1 [0,0,5,1]
5-51
FlexiCall/IRSS (Freedom) Feature Codes ç NPL,2 [0,0,5,2]
This option defines the FEATURE_PREFIX dial number and the special feature
codes (such as NEW_CALL, TRANSFER, DIVERT, etc.) used to establish the
FlexiCall and IRSS (Freedom) features.
• The FlexiCall feature allows a user to define an off-site phone as a
supplementary phone which rings simultaneously with his/her Coral station.
Only when the call is answered at the remote phone, are these Coral features
enabled at the remote phone.
• The IRSS feature, also known as Freedom, allows a user to define an off-site
phone with the capability of dialing into the Coral and becoming a virtual Coral
 Notes:
station for the duration of the call.
• A special feature code is always activated after a FEATURE_PREFIX to

initiate a feature. Therefore, no conflict exists between the Special
Feature number and the General Numbering Plan.
• Only one digit (between 0 and 9 or * and #) can be utilized per special
feature code.
• When an attempt is made to define another feature with an existing
code, the following message appears:
# Plan Err, TRY AGAIN
Enter an undefined digit and continue.

FlexiCall/IRSS (Freedom) Feature Codes NPL,2 [0,0,5,2]
FEATURE_PREFIX Any 1, 2, 3 or 4 digit combination of the following characters: , #, 0..9,

or R (for remove)
Default: 
Define the dial number/character prefix for all the special FlexiCall/IRSS features.
NEW_CALL Any one (single digit) of the following: 0..1..9, or , #, or R (for remove)
Define the dial number for the remote phone user to initiate a new call via the Coral
system. The feature dial number must be preceded by the FEATURE_PREFIX
defined above.
TRANSFER Any one (single digit) of the following: 0..2..9, or , #, or R (for remove)
Define the dial number for the remote phone user to initiate a call transfer via the
Coral system. The Transfer type is based on the station’s COS Call Transfer and
3-way definition. The feature dial number must be preceded by the FEATURE_
PREFIX defined above.
5-52
DIVERT Any one (single digit) of the following: 0..3..9, or , #, or R (for remove)
Define the dial number for the remote phone user to divert the answered call to any
Coral station. The feature dial number must be preceded by the FEATURE_PREFIX
defined above.
VM_ACCESS Any one (single digit) of the following: 0..4..9, or , #, or R (for remove)
Define the dial number for the remote phone user to enable DTMF dialing to the
Voicemail system (or IVR) and circumvent the Coral DTMF receivers (such as
8DTMF and 8DTR cards). The feature dial number must be preceded by the
FEATURE_PREFIX defined above.
DIVERT_TO_LOCAL_ Any one (single digit) of the following: 0..5..9, or , #, or R (for remove)
STATION
Define the dial number for the remote phone user to divert the answered FlexiCall
call to his/her Coral station. The feature dial number must be preceded by the
FEATURE_PREFIX defined above.
CALL RECORDING / Any one (single digit) of the following: 0..6..9, or , #, or R (for remove)
HELP REQUESTING
Defines the dial number for the remote phone user to activate the HELP
REQUESTING feature (keyset default feature code: #1443) via the Coral system.
The feature dial number must be preceded by the FEATURE_PREFIX defined above.
The HELP REQUESTING destination for all FlexiCall and Freedom callers is
defined in FLEXICALL/FREEDOM HELP DEST [3] (page 6-43), in Station Messaging
(SFE,7).
FlexiCall/IRSS (Freedom) Feature Codes NPL,2 [0,0,5,2]

Also defines the dial number for Start/Stop Recording an IRSS/FlexiCall/Freedom
call when using the Coral Navigator application.
5-53
SHOW TYPE of NUMBER ç NPL,3 [0,0,5,3]
This NPL branch enables the technician to display requested dial numbers against
their NPL types.
FROM/TO Range: Any valid NPL dial number

DIAL# Default:All NPL dial numbers
Enter the requested range of dial numbers from the lowest to the highest dial
number.
Only dial numbers that are already exist in the numbering plan can be entered.
The PI displays a range of entered dial numbers against their NPL Types.
• Optional TYPEs:
BOSS_GRP, DID_NUM, HUNT_GRP, DVMS_MSG, GROUP-CALL,
WIRELESS, IP-KEYSET, IP-SLT, IP-NET, SIP-TERMINAL, SIP-TRUNK,
PUBLIC-LIB, PRIVATE-LIB, DIAL-SERV, DVMS-PORT, BELL, PAGE-Q,
MODEM, PAGE, ROUTING-ACC, TRUNK, TRUNK-GRP, RELAY, CONF,
KEYSET-V-PA, KEYSET-Z-PA, WAIT-QUE, FEATURE, NETWORK,
FEATURE, KEYSET, SLT, etc.
• The Net_Node column shows the Node numbers assosiated with each
NETWORK number. This column is only relevant for NETWORK numbers.
 For Example:
Other type of numbers are shown as “--”.
Dial # TYPE Net_Node

=====================================================
9 TRUNK --
SHOW TYPE of NUMBER NPL,3 [0,0,5,3]
220 SLT --
420 KEYSET --
55055 NETWORK 0
7000 PRIV LIB --
5-54
6 System
This chapter is used to program the system-wide parameters and contains the
following sections:
Feature Timers ..............................................................................................6-2
System Features............................................................................................6-7
Card List .....................................................................................................6-59
Port List ......................................................................................................6-67
Digital Port Bus List...................................................................................6-91
Tone Plan ....................................................................................................6-95
Ringers ......................................................................................................6-102
 Feature Timers establish the time intervals related to each feature.
 System Features allow, deny or modify the feature operations system-wide.

Many of these features, when implemented, may also be restricted by the Class
of Service defined (see Chapter 7).
 The Card List parameters determine the system hardware configuration, while
the Port List parameters identify the equipment location, port by port.
 Tone Plan determines the tone frequencies and duration of each tone.
 Ringer parameters are used to define and protect the Ringer Power Supplies
from overloading.
• RPS units are installed in Coral FlexiCom 5000 and 6000 systems
• PS19 DC-D units are installed in Coral IPx 800, 3000, 4000 systems
6-1
System PI Reference Manual
Feature Timers ç FE.T [0,0,1,0]
Feature Timers are used to define the timer intervals used in the different Coral
feature operations for the entire system.
Field numbers appear in square brackets ([ ]).
AUTO_REDIAL [0] 1..30..3780 seconds

Determines the time interval between automatic redial attempts by a keyset, to an
external number previously busy.
REMIND_SNOOZE [1] 1..60..3780 seconds

Determines the time interval between dialing the “Snooze” code and a Remind
re-ring.
WAKEUP_SNOOZE [2] 1..60..3780 seconds

Determines the time interval between dialing the “Snooze” code and a Wakeup
re-ring.
WAKEUP_RING [3] 1..300..65534 (1 unit = 0.1 second)

Determines the duration of each Wakeup call attempt.
NET_FEATURE_ACK 1..40..65534 (1 unit = 0.1 second)

[4]
Determines the time period that the system waits for a signal acknowledgment to
activate a Network feature.
CAMP_ON_ 1..12..168 (1 unit = 1 HOUR)

Feature Timers FE.T [0,0,1,0]
DURATION [5]
For Networks:
Define this timer identically for all the network PABXs.
Determines the duration of the CAMP-ON feature. After this time-out interval,
camp-on feature is automatically canceled.
DELAY_BEFORE_PR 1..60..600 (1 unit=1.0 second)

[6]
This parameter defines the time interval after which the PATH REPLACEMENT
[7] (page 28-5) feature is aestivated.
6-2
PI Reference Manual System
SUSP_OFFHK [7] 3..5..10 (1 unit = 0.1 second)

Determines the maximum time that the system waits for an offhook or seize
message from a port after a Suspect Offhook or Suspect Seize signal.
 SUSP_OFFHK time must be greater than any MIN_SZE and/or MIN_OFFHK

recognition timer in the entire PI (see Chapter 8).
BELL_RING Defines the cadence of both internal (station-to-bell) and external (trunk-to-bell)
Central Bell/UNA calls. Related equipment: RMI, 8DRCM, 8DRCM-2, 8DRCF,
U-RMI Office, U-MR Office, RMI Office, MR Office, IPx 500M, CDRS 200E.
ON_BELL [8] 1..10..65534 (1 unit = 0.1 second)

Determines the duration of Bell/UNA relay contact closure.
OFF_BELL [9] 1..20..65534 (1 unit = 0.1 second)

Determines the duration for which the Bell/UNA relay contact is open, i.e. between
Bell Ring On cycles (above).
ATT. MSG [10] 1..50..600 (1 unit = 0.1 second)

Determines the ring burst duration used to indicate Attendant Message Waiting.
EXPENSIVE_ROUTE_ 1..10..20 (1 unit = 0.1 second)

TONE [11]
Determines the duration of an Expensive Route Tone.
 EXPENSIVE_ ROUTE_TONE programming is also required in the Routing

Class of Service (Warning Tone) and for Routing Dial Services
(EXPENSIVE TONE, See Chapter 15).

RING [12] 50..100..600 (1 unit = 0.1 second)

Determines the silence period after offhook to answer a feature ring (for example,
Wakeup, Reminder, Camp-on, etc.), the system waits for a “Snooze” or “Activate”
dial code. Time-out after ring for feature activation.
6-3
SUPV_RECALL [13] 300..3600..7200 (1 unit = 0.1 second)

PWDS Supervision Recall determines the time interval in which a trunk-to-trunk
call, of two connected trunk ports without disconnect supervision (determined by
trunk port definition) is terminated or recalled to the Incomplete Calls destination
for monitoring and supervision, see System Features - Intercept/Incomplete
beginning on page 6-33.
 Also operates on magneto-to-magneto stations or magneto-to-trunk and

DISA by external trunk-to-trunk port.
CONF_SUPV_RECALL 300..1800..7200 (1 unit = 0.1 second)

[14]
Conference Supervision Recall determines the time interval in which a trunk or any
port without disconnect supervision is connected to a conference and is recalled to
the Incomplete Calls destination for monitoring and supervision.
WHISPER_PAGE_ 1..6..60,000 (1 unit = 0.1 second)

TIMER [15]
Defines the duration of the whisper page tone sent before the whisper page. The
tone is heard by the whispering side and by the side whispered to. The other side
engaged in the conversation does not hear any tone.
BREAK_IN/OUT [16] 1..10..30 (1 unit = 0.1 second)

Break In/Out Alert determines the duration of the alert or warning tone when
break-in/out occurs.
The tone cadences are defined in Tone Plan beginning on page 6-95.
 This timer is irrelevant for Group Call and Meet-Me conference calls. The
duration of the conference call alert tone (i.e. when an additional user
joins or leaves the call) is set to one second and cannot be modified.
6-4
BREAKIN_ Defines the background tone that is heard by the two parties engaged in a call
WARNING during the entire break-in period. The tone warns the conversing parties that a third
party is listening. This tone can only be activated when the BREAK-IN_WARNING
[1] (page 6-50) is set to Yes. The combination of OFF/ON periods determines the
tone character.
ON [17] 1..65534 (1 unit = 0.1 second)

Eu9 (Italy): Default = 2 (200 ms)
Determines the duration of the break-in warning tone.

OFF [18] 1..20..65534 (1 unit = 0.1 second)

Eu9 (Italy): Default = 98 (9800 ms)
Determines the duration that the break-in warning tone is off.

DTMF_TONE The following two parameters define the character of the DTMF tone administered
by the Coral system over a DTMF trunk when placing outgoing calls.
ON [19] 4..10..50 (1 unit = 10ms)

Determines the duration of the DTMF tone.
OFF [20] 4..10..50 (1 unit = 10ms)

Eu3: 16
Determines the minimum silence period between DTMF tones.

GRP_CALL_RING [21] 1..30..120 seconds
 Relevant only for Group Calls.

Defines the time that all the stations defined as registered members of a Group Call

Conference continue ringing before the conference is locked against additional
members. This duration starts when a caller dials the group call dial number, at
which time all the station member keysets ring. The members can off-hook and join
the conference. Stations that go unanswered, continue ringing until this GRP_
CALL_RING times out. Members who did not answer are now blocked from joining
the group call, depending on the Group Call definitions. For more information on
Group Calls, see Chapter 10-Groups.
V.M_SLT/KEY_ 1..120 (1 unit = 0.1 second)

DELAY_BEFORE_
When a station dials a Voicemail system (or any other system requiring DTMF
DIAL [22]
tones), this parameter defines the time delay before the Coral station can send the
DTMF digits. During this time delay, the Voicemail System is expected to send an
answer signal to the Coral station.
6-5
CCR_TONE_ 0..130 (1 unit = 0.1 second)

DURATION [23]
Defines the duration of the Collect Call Reject Tone defined in SLT or KEY.
This parameter is relevant only if COLLECT_CALL_REJECT_TONE [40] on page
9-17 (for SLTs) or page 9-65 (for Keysets) is set to Yes.
The tone frequency is defined in TONE_PLAN, see page 6-97.
SPEAK_REQ_ 10..50..100 (1 unit = 0.1 second)

RINGBACK [24]

Relevant only for the Group Operator’s keyset of a Group Call defined to
admit participants only in mute mode. See JOIN MEMBERS IN MUTE on
page 10-32.
Defines the duration within which the speech request message, from group call
participants, is displayed at the Group Operator’s keyset. The related DSS buttons
(those stations which requested to speak) wink on the Group Operator’s keyset for
this time duration. After this time, all message and DSS lamps relating to the
speech request are cleared.
CALL_DURATION_ 1..600..65534 sec

LIMIT [25]
Defines a maximum duration for outgoing external calls when required. The
stations must be defined with a COS that includes the outgoing trunks, trunk groups
or Routing Access’ used to initiate the call.
The related COS Call Duration Limit parameters include: CALL DURATION LIMIT:
TK_GRPS/ROUTING ACCESS [9] (page 7-5) and CALL_DURATION_LIMIT: DIAL_
SERVICE [10] (page 7-6).
MLPP_PREEMPTION_ 150..300..450 (1 unit = 0.1 seconds)

ACK [26]
Defines the maximum duration for the called party that hears a continuous
Precedence tone to onhook in order to clear though the MLPP call.

MLPP_STOP_CONF_ 1..20..65534 (1 unit = 0.1 seconds)

TONE [27]

It is advisable not to define an inordinately large number for the tone, as
the tone interrupts call progress.
Defines the Stop Conference Tone duration for MLPP calls to one member of a
3-Way call (see PL CONF (page 6-99) tone for tone description).
The 3-way call member hears a preemption tone and is disconnected from the
3-Way call. The other members hear the MLPP Stop Conference Tone indicating
that the member is disconnecting from the call because of an MLPP preemption
call.
6-6
System Features ç SFE [0,0,4,1]
System Feature parameters allow, deny, or modify the feature operations at the
system level. The following SFE options are available:
SFE Option MNEMONIC PAGE #
0 - Outgoing Trunks SFE, 0 6-8
1 - Incoming Trunks SFE, 1 6-18
2 - Station Options SFE, 2 6-19
3 - Intercept/Incomplete SFE, 3 6-33
4 - Call Forwarding SFE, 4 6-38
5 - Camp-On SFE, 5 6-40
6 - Hotel SFE, 6 6-41
7 - Messaging SFE, 7 6-43
8 - Tones SFE, 8 6-50
9 - Diagnostics SFE, 9 6-52
10 - ISDN SFE, 10 6-54
11 - Network SFE, 11 6-55
12 - Wireless SFE, 12 6-56
System Features SFE [0,0,4,1]
6-7
System Features - Outgoing Trunks ç SFE,0 [0,0,4,1,0]
The following parameters apply only to outgoing trunk calls.
TK_TO_TK_CONNECT Yes/No
[0]
Allows or denies trunk to trunk connections. For example, trunks can remain
connected after the station originating a 3-way conference call, involving two
trunks, goes onhook (disconnects); or an incoming E&M dial trunk call can
continue dialing out on another trunk once the station has disconnected.
 To override a prohibited trunk to trunk connection on a specific trunk

group, use TK_TK_CONNECT_OVERRIDE (page 8-23) in Trunk Group
Definition (TGDEF).
To override the trunk to trunk prohibition on specific stations, use TK_TK_

XFER_OVERRIDE [67] (page 7-20) in COS.
TK_TO_TK_TO_ST [1] Yes/No

Eu: No
Trunk To Trunk To Station Connection allows or denies all stations the ability to
establish a 3-way conference call using two trunks. After the station goes onhook,
the trunks are disconnected.
PASS_TK [2] Yes/No

System Features - Outgoing Trunks SFE,0 [0,0,4,1,0]
Allows or denies all stations the ability to transfer an established trunk call to
another station. (This feature is also restricted in station Class Of Service.)
PASS_TK_DIAL_ Yes/No
TONE [3]
Allows or denies ll stations the ability to pass the trunk dial tone to another station.
(This feature is also restricted in station Class Of Service.)
HF_ON_ALERTING_ Yes/No
ISDN [4]
Allows outgoing ISDN calls to the PSTN (via PRI trunks) to be transferred in alert
(while ringing) without waiting for the call to be answered by the external
destination.
MAX_DGTS_ON_TK 0..51
[5]
Determines the maximum number of digits available for dialing out on a trunk
(applies also to Routing, SMDR and Toll Barrier Analysis). This does not affect the
numbers dialed after a calibrated opening instruction.
6-8
SAVE_&_SEND_DTMF Yes/No
[6]
Determines whether the system will store DTMF digits before the trunk dial tone
is present. The system transmits the stored digits after dial tone is detected when
this parameter is set to Yes.
#ACCT_DGTS [7] 1..4..16

Eu:16
Determines the length (number of digits) of the system call account codes that are
used for call charges (billing). Selecting a number between 5 and 16 causes the
SMDR On-Line report to print two lines per call record, the second line includes
the dial number. Changes made in this parameter will also change all codes in the
VFAC table. The total number of VFACs is dependent on: VFAC_ACCT in SIZ (see
Chapter 4- Sizes Definition), which must be defined first, and #ACCT_DGTS as
shown in the following table.
#ACCT_DGTS Maximum Number of

Codes per
Digit Definition
4 100
5, 6 1,000
7 10,000
8-16 65,000
 When VFAC. (below) is set to Yes, its range is between 4 and 16; when

VFAC. is set to No, its range is between 1 and 16 (see below).
6-9
PASS_ACCT_CODE_ Yes/No
FOR_TK_TO_TK_
Determines whether an account code that was defined for the 1st trunk will
XFER [8]
automatically be passed to the 2nd trunk upon transferring.
An extension is connected with trunk no. 1. The extension user defines an ACCT_
CODE. The extension user transfers trunk no. 1 to another trunk, no. 2, and
disconnects. This parameter defines whether the ACCT_CODE that was defined
for trunk no. 1 will be automatically defined for trunk no. 2 and is printed in the
SMDR record.
Mainly for Caller ID application, see MFC_CALLER_ID [17] (page 6-12). Transfer
the extension # (account code), on Outgoing trunk for CLI SMDR. The extension
# (account code) is originated by the Coral.
VFAC. [9] Yes (All account numbers are checked and verified)
No (Account numbers are neither checked nor verified)
Determines whether or not the VFAC feature is used for making outgoing calls.
Additionally, defining VFAC. to Yes ensures that all dialed Account Codes are
checked and verified according to the VFAC Code table. If #ACCT_DGTS above is
set to less than 4, then VFAC. must be defined as No (see Chapter 24).
CHARGE_TYPE [10] M (Metering pulses and AOC), C (cost calculation based on call duration)
Default: C, Eu and CC1: M
Meter Pulse/Cost - Call Duration determines whether charge calculation is based
upon a Metering Pulse (Mtr and AOC) or the Call Duration (Cost calculation
feature).
For advice of charge (AOC) feature, enter M.
METER_BEFORE_ Yes/No
CONNECT [11] Eu and CC1: Yes
 Not used in North America (CC0 systems).

Determines whether metering pulses before a trunk call is established are relevant
for call charging.
6-10
AOC  Advice of Charge includes the following three parameters when CHARGE_
TYPE [10] (above) is set to Meter and METERING_UNIT_CHARGE (page 8-31) is
not set to N.
C O S T $ $ $ x x x x x . y y
C O S T $ $ $ z z z z z z z z
C O S T x x x x x . y y $ $ $
C O S T z z z z z z z z $ $ $
$$$= Currency unit (3 characters)

xxxxx.yy: xxxxx = Cost 00,000 to 99,999 yy = Cents 00 to 99
zzzzzzzz = Cost 00,000,000 to 99,999,999
 Upon termination of a call, the call cost is displayed in one of the above
options according to the following three parameters:
CURRENCY_UNIT [12] Enter 3 printable keyboard characters.
Any lower case letters entered will be displayed as a capital letters.
For space/blank, enter underscore: “_”
Default: “$_ _” , Eu2: “DM_”, CC1: “NIS”
Defines the three characters of currency unit, used in a country. These characters
that represent the currency unit, appear on a caller’s keyset display, along with the
outgoing call price.
 The currency unit for SMDR and CHARGE records is defined by the
SMDR/CHARGE_CURRENCY_UNIT [13] (Coral version 15.85.30 or higher)

parameter (Route: SMDR,0) on page 14-6 and is in no way relevant to
this parameter.
CURRENCY_SIGN_ L (left), R (right);

PLACEMENT [13] CC1: Left
Defines the location of currency unit, to the left or right of the outgoing call price.
The currency unit appears on a caller’s keyset DISPLAY and in the CHARGE field
of an SMDR record along with the outgoing call price.
CURRENCY_FORMAT 1 (xx,xxx.y 5 digits for integer number, with a decimal point for ten’s digit)
[14] 2 (zz,zzz,zzz 8 digits for integer number, without decimal point)
 The CHARGE field format of an SMDR record cannot be changed.

Defines the outgoing call price display format, with or without a decimal point.
This parameter is applicable to the price which appears on a caller’s keyset display
along with the currency unit.
6-11
DGTL_TRK ANS_AS_ Yes/No

MTR [15]
Not used in North America (i.e. T1 trunks)
Determines whether an E1 Digital Trunk outgoing call charge is started (metering
pulse) when an answer is detected. When answer is detected, an additional
metering pulse is charged.
MAX_AUTO_REDIAL_ 1..15, N (No Limit)

ATTEMPTS [16] CC0: 15
Eu2: 5
Determines the number of automatic redialing attempts.

The Coral system will redial until the external phone rings or up to the number of
attempts defined (here) system-wide, before the outside number is erased from the
scanner list.
MFC_CALLER_ID [17] S (station #), A (account code)
 For Caller ID application, see PASS_ACCT_CODE_FOR_TK_TO_TK_XFER

[8] on page 6-10.
Defines whether the caller ID number, sent by the Coral on MFC trunks to another
exchange in order to identify the calling exchange, is based on station number or
account code. (When A is selected and account code not applied by the user, the
number 6666 is sent by default).
DEFAULT_SECOND_ Any Number (up to 16 digits)/R (Remove for None)

ALI [18]

This parameter is relevant for outgoing trunks routing calls to Emergency
or E911 centers.
Define a default second alternate line ID number to be used for calls routed via a
dial service that requests a Second Alternate Line ID but the caller’s number is
unavailable or the Second ALI is not defined (see SEC_ALTERNATE_LINE_ID [67]
on page 9-62 for Keyset definitions or SEC_ALTERNATE_LINE_ID [29] on page 9-13
for SLT definitions).
When no ANI is provided for the specific call (e.g., for calls that do not have a dial
number from the Coral Numbering Plan “NPL”), this parameter defines an
alternate Line ID for the PSTN.
6-12
MEET-ME PAGER ( ) = Meet-Me Mode Always, (x), (x,y)

PREFIX [19] x, y can be any digit between 0 and 9;
This parameter is used when dialing over an E&M trunk group connected to the
paging system known as ESPA (European Selective Paging Manufacturers
Association). All ranges are entered within parentheses. No digits in parentheses
indicate a Meet-Me Mode. Up to a maximum of two digits are allowed, separated
by a comma.
NUMBER_OF_CAMA_ 7 or 10
ANI_DIGITS [20]

CCO only
Only 7 or 10 can be entered, all other entries will result in an error

message.
Defines the number of ANI digits to be sent over the CAMA trunk. Set this
parameter according to local regulations.
LOOK AHEAD Yes/No

ROUTING [21]
Defines whether or not LAR (Look Ahead Routing) functionality is activated on
Dial Services (see Look Ahead Routing Triggers beginning on page 15-33).
When set to Yes, the LAR will re-route a call to the next Dial Service whenever
asynchronous failure occurs. The failed Dial Service is blocked for a system-wide
defined period.
When set to No, Dial Services are not be handled by the LAR functionality.

An asynchronous failure occurs when the signaling sequence that sets up the call
is completed before the connection establishment confirmation has been received
from the terminating end.
6-13
SEND_ORIGINAL_ Range: Yes/No

ANI_TO_CFWD_DEST Default:Yes
[22] CC1: No
 If this parameter is set to No, then SYSTEM_WIDE_NAME_RETENTION

[23] (page 6-26) (SFE,2), is inoperable.
For outgoing calls that originated from an external destination, set this parameter
to Yes to have the original external caller’s ID sent to the station’s external call
forward destination (for Coral Call Forward All, Busy, No-Answer, Timed,
Undefined, Internal, External, and their combinations).
 For version 16.01 or lower, the parameter does not operate on Call
Forward No-Answer.
If this parameter is set to No, the external call forwarded destination views the
caller ID for the Coral station that activated call forward, as opposed to the original
external caller’s ID.
SEND_INTERNAL_ Range: Yes/No

ORIGINAL_ANI_TO_ Default:Yes
CFWD_DEST [23] CC1: No

{V16.02.03 or Higher}
If this parameter is set to No, then SYSTEM_WIDE_NAME_RETENTION
For outgoing calls that originated from an internal destination, set this parameter to
Yes to have the original internal caller’s ID sent to the station’s external call
forward destination (for Coral Call Forward All, Busy, No-Answer, Timed,
Undefined, Internal, External, and their combinations).

If this parameter is set to No, the internal call forwarded destination views the caller
ID for the Coral station that activated call forward, as opposed to the original
internal caller’s ID.
6-14

ANI_TO_FlexiCall_ Default:Yes
DEST [24] CC1: No

to Yes to have the original external caller’s ANI sent to the station’s forwarded
FlexiCall destination. in addition, the ANI of the originator will be sent to the
external call forward destination for Call forward No Answer.
If this parameter is set to No, the forwarded destination views the caller ANI for
the Coral station that activated the FlexiCall feature, as opposed to the original
external caller’s ANI. In addition, the ANI of the forwarding party will be sent to
the external call forward destination for Call forward No Answer.

ANI_TO_FREEDOM_ Default:Yes
DEST [25] CC1: No

to Yes to have the original external caller’s ID sent to the station’s Freedom (IRSS)
destination.
If this parameter is set to No, the external call forwarded destination views the

caller ID for the Coral station that activated the Freedom feature, as opposed to the
original external caller’s ID.
CIRCUIT ASSURANCE None / ISDN / Analog / Both

[26]
Circuit Assurance reroutes a call over a failed trunk. The failed trunk is blocked for
a system-wide defined period and the next consecutive trunk is used.
When set to ISDN, Circuit Assurance is activated on ISDN trunks.
When set to Analog, Circuit Assurance is activated on analog trunks.
When set to Both, Circuit Assurance is activated on both ISDN and analog trunks.
When set to No, Circuit Assurance is not activated on any trunk.
6-15
CALLBACK ROUTING Any valid Routing Access or R (Remove for None)

DESTINATION [27] Default: First Routing Access defined in the Coral Numbering Plan
(Route: NPL,0) ROUTING_ACC [37] on page 5-44.
When dialing out to an external destination defined in the Shared or Personal
Directory or to an incoming number from the call log, the system uses this outside
line routing access.
 This parameter is NOT relevant for outgoing numbers in the call log. (i.e.,
numbers dialed by the user. Outgoing call log numbers are routed as
originally dialed.
For example, if the user dialed 80 and then 1234567, Coral will route the
number as 801234567, even if the CALLBACK ROUTING DESTINATION [27]
parameter is defined differently.
ACNR_Requires_DTD Yes/No
[28]
Defines whether the ACNR (Automatic Called Number Redial, also known as
(V. 16.01.10 or higher)
ADNR) feature functions with or without DTD installed in the Coral system.
 Note: The ACNR requires DTD only when used on analog

Loop-Start/Ground-Start (LS/GS) trunks.
DTD ACNR_Requires_DTD ACNR functions for Trunk type

Installed in [28] (V. 16.01.10 or
System higher) PRI SIP LS/GS T1/30T
parameter
Yes Yes Yes Yes Yes Yes
No Yes Yes No Yes
No Yes No No No No
No Yes Yes No Yes
6-16
BUSY TRUNK
GROUP
SKIP_AVAILABLE_ Yes/No
TRUNK_CHECK [29]
Defines, system-wide, whether or not the system searches a trunk group for an
available trunk after finding all trunks busy in a previous search.
The system searches the trunk group again if one of the trunks in the trunk group
becomes available or if the number of dialing attempts on the trunk group exceeds
the value defined in MAX_SKIPS [30], the next parameter.
MAX_SKIPS [30] 1..10..250
 This parameter appears only if the previous parameter was set to Yes.
When the system is programmed to skip the search for available trunks, (see
parameter above), the system will search again only when one of the trunks in the
trunk group is freed or when the number of dialing attempts on the busy trunk
group exceeds the value specified by this parameter.
6-17
System Features - Incoming Trunks ç SFE,1 [0,0,4,1,1]
The following parameters apply only to incoming trunk calls.
DISA_SUSTAIN_DGT 0-9, #, *(asterisk)

[0]
Direct Inward System Access Sustain Digit determines the single digit which must
be transmitted from an external DTMF telephone to maintain a Remote Access
connection. The digit must be sent before the end of each time period, as
determined by the SUPV_RECALL [13] (page 6-4) timer in Feature Timers.
DISA_NEW_CALL_ Range: 0-9, #, *

DGT [1] Default: #
DISA New Call Digit determines the single digit that must be transmitted from an
external DTMF telephone to permit the caller to dial another system number after
completing the previous Remote Access call. After pressing the digit, the system
sends a new system dial tone to the Remote Access trunk, and is prepared to receive
additional digits.
DID_DIAL_TONE [2] Yes/No

DID Second Dial Tone determines whether dial tone is sent in response to an
incoming DID trunk seizure before the dialed digits are received from the Central
Office, when set to Yes.
E&M_CONT_DIAL_ Yes/No
System Features - Incoming Trunks SFE,1 [0,0,4,1,1]
TONE [3]
E&M Continuous Second Dial Tone determines whether a dial tone is sent in
response to an incoming seizure on incoming E&M continuous trunks before the
digits are received from a distant PABX.
E&M_PULSE_DIAL_ Yes/No
TONE [4]
E&M Pulsed Second Dial Tone determines whether a dial tone is sent in response
to an incoming seizure on incoming E&M pulsed trunks before the digits are
received from a distant PABX.
OPERATOR_ACCESS S/D
(Single-0/Double-0X)
Defines whether an incoming GID trunk can dial a single digit “0” (zero) or leading
[5]
“0” (zero) followed by an additional digit as defined by the DID Group Filter, see
Eu2 only DID/E&M Groups beginning on page 8-36, and the System Numbering Plan for
attendants.
6-18
System Features - Station Options ç SFE,2 [0,0,4,1,2]
ALL The following parameters apply to all station types.
MAX_RING [0] 1..20

1..20..33: Coral IPx 800, 3000, 4000 per PS19 DC-D
Determines the maximum number of single line telephones SLTs (and Magneto)
which can ring simultaneously as follows:
Coral System Description
FlexiCom 400 (with Defines the total number of SLTs which can ring
HDC controller) simultaneously
FlexiCom 5000, 6000 • Defines the number of SLTs which can ring
simultaneously per Peripheral Shelf Unit.
• See Ringers beginning on page 6-102 to
properly define the Ringer software
configuration depending on the Ringer
hardware configuration.
IPx Office, IPx 500 and MAX_RING_PER_CARD [2] Coral IPx 500,
CDRS 200E CDRS 200E and IPx Office only below
replaces this parameter
IPx 800, 3000, 4000 Defines the number of SLTs which can ring
systems supported by simultaneously per shelf
PS19 AC or PS19 DC
System Features - Station Options SFE,2 [0,0,4,1,2]

IPx 800, 3000, 4000 • Defines the number of SLTs which can ring
systems supported by simultaneously per shelf.
PS19 AC or PS19 DC
• This system wide parameter must be consistent
with the capabilities of any connected
expansion unit.
IPx 800, 3000, 4000 • Defines the number of SLTs which can ring
systems supported by simultaneously per shelf or per two adjacent
PS19 DC-D shelves depending on their hardware
configuration.
• See Ringers beginning on page 6-102 to
properly define the Ringer software
configuration depending on the Ringer
hardware configuration.
6-19
MAX_RING_PER_ 1..6 (Display Only)

CARD [2]
Defines the number of SLTs (and Magneto) that can ring simultaneously per card
Coral IPx 500,
as follows.
CDRS 200E and
IPx Office only Coral System Description
IPx 500 and 8/16/24SAipx, 8/16SLSipx, and 8SMipx card

CDRS 200E
IPx Office 4/8/16/24SA Office, 4/8/20S Office,

4SA+8Fx Office, 4SA+16Fx Office,
8SA+8Fx Office or 8SA+16Fx Office card
A maximum of 6 simultaneously ringers per card SLT is supported.

MAX_BOSS_RING [4] 1..20..255

Determines the maximum number of stations in a Boss Group which can ring
simultaneously.
DIGIT_ONE_AS_H.F. Yes/No
[5]

In noisy areas this parameter should be set to No.
Defines the digit 1 as a hookflash (Enter Y) or a 1 digit that is ignored (Enter N).
This parameter applies to any SLT, keyset, or trunk port during internal or QSIG
network calls or when the ring/busy tone is heard.
INTERNAL_LAST_ Yes/No
NUM_REDIAL [6]
Defines the LAST NUMBER REDIAL feature to include internal numbers as well as
external numbers.
Internal numbers include any legal station destination within the system. It does not
include feature codes and Page-Q.
CLIR on Internal Calls Yes/No

[7]
This parameter is used to allow users to block caller ID information for internal
calls.
When this parameter is set to No, a station’s caller ID is available to all internal
called keyset parties.
When this parameter is set to Yes, the caller’s ID can be restricted to internal called
keyset parties based on the combination of SEND_CALLER_ID in its station
definition (for SLTs: SEND_CALLER_ID [27] on page 9-12, for KEY:SEND_
CALLER_ID [65] on page 9-61) and/or the station user’s implementation of Control
Caller ID (Default dial number: #1444) from their station set.
6-20
TEMPORARY_AUTO Yes/No
SET RELOCATE [8]
When this parameter is set to Yes, stations are allowed to activate the Auto Set
Relocate feature either temporarily or permanently by defining
Permanent/Temporary_AUTO SET RELOCATE [34] (page 9-15) in the SLT Definition
branch (SLT) or
Permanent/Temporary_AUTO SET RELOCATE [72] (page 9-64) in the Keyset
Definition branch (KEY).
When set to No, this parameter allows stations, system-wide, to activate the Auto
Set Relocate feature only on a permanent basis and disables temporary relocation.
PREEMPTION TYPE Intrude/Release

[9]

This parameter is relevant only for Public Libraries defined with
PRIORITY_PREEMPTION_CALL? (page 11-4) set to Yes, in Coral system in
which the emergency destination resides.
Defines whether the emergency call that is preempting the established
non-emergency call:
• breaks into the existing non-emergency call (Intrude), or
 Previously established emergency calls are not disconnected. The new

• disconnects the non-emergency established call (Release).
emergency call camps on the busy trunk and waits until the trunk is freed.
This parameter is irrelevant for Coral systems that serve as transit nodes leading to
the Coral with the emergency destination. Regardless of the PREEMPTION TYPE
settings in the Coral assigned for emergency purposes, a transit emergency call will

disconnect busy trunks leading to the “emergency” Coral.
MAX_DIGITS_TO_ 5..16
VERIFY_IRSS_
Defines the maximum number of digits required by the system to identify an
CALLER [10]
external caller’s number as that of an IRSS (Freedom) destination. The Coral
checks the last few digits (5 to 16 digits, defined in this parameter) of the external
calling number to verify that it is an IRSS destination.
6-21
CALL_BACK_ None, Wait Que,

ANNOUNCEMENT [11] Keyset port #, SLT port #,
DVMS (4VSN) port # defined with special message,
FlexSet 120/280, FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL,
SIP port on SeaMail, Boss Group, Hunt Group, Trunk, and Trunk Group or
Public Library with one of the previous items.
Identifies the announcer (dial number to which the announcement is relayed)
that is heard before an incoming IRSS callback request is disconnected. After the
message is completed, the caller has to on-hook and await for the callback ring.
Such messages can provide general information to the caller or advertisements, as
required.
 The offsite caller pays for the portion of the call during which the
announcement is heard. SMDR records are generated (to the user's
internal phone) for incoming trunk calls that are answered by the callback
announcer. See DISPLAY_IN [1] on page 14-2 in SMDR Control.
The announcer is a device with a prerecorded message. This device can be
connected either to a SLT port, DVMS port, SeaMail SIP port, iVMFipx keyset
port, IPC/uCMC or IPC/SFC keyset port, etc.
• When defined as NONE, the call is disconnected immediately, and callback is
activated.
• When defined as Wait Que, the Coral sends a simple tone as notification
without answering.
• In order to install an ANNOUNCER device in an SLT port, the SLT Definition
must be defined as ANNOUNCER [23]=YES, (see page 9-10).
• In order to use a DVMS port, special DVMS MSG must be programmed (see page
23-2).
• When using iVMFipx keyset ports as announcers (Coral IPx 500 and CDRS
200E systems), update the ANNOUNCER [34] (page 9-42)=Yes in the Keyset
Definition branch.
• When using IPC/uCMC, or IPC/SFC keyset ports (Simplicity) as
announcers, update the ANNOUNCER [34] (page 9-42)=Yes in the Keyset
Definition branch.:
CALL_BACK_DELAY_ 1...3...20 secondsYes/No

TIME [12]
Defines the time interval between the instant the incoming IRSS callback request
is disconnected (by the Coral or by the off-site phone), until the callback is dialed
by the Coral system.
During this time delay, the off-site user can complete or reject other calls (such as:
calls waiting, calls on hold, etc.) thus leaving the off-site phone in idle state, ready
for receiving the awaiting callback.
6-22
SHORT_CALL_MSG Yes/No
[13]
Defines a shortened message display on the user’s keyset.
Setting this parameter to No, enables the full keyset display for incoming calls in
the format: A call B. The following example of a keyset display shows the trunk
number followed by the ANI of the calling party. Susan is the called internal
station.
78840 5553067 CALL Susan
Setting this parameter to Yes, enables a shortened display where only the caller ID
is presented while the called station number, or name, is omitted. The following
example of a keyset display shows that only the external number is display during
the call.
78840 5553067
This shortened format allows users with smaller keyset displays (FlexSet 120
series) to view the entire calling party’s ANI.
When used together with NAME_NUM_DISPLAY [14], this parameter defines the
combinations of names and numbers viewed on the display panel of the phone.
NAME_NUM_DISPLAY Yes/No
[14]
Enables both the name(s) and number(s) of a call to be seen on the display panel of
the phone. When N (No) is displayed, either the name or the number of the party is
displayed. When Y (Yes) is displayed, the name AND the number of the party is

displayed.
When used together with SHORT_CALL_MSG [13], this parameter defines the
combinations of names and numbers viewed on the display panel of the phone.
Table 6-1: Name and Number Viewed on Display Panel
Parameter Setting SHORT_CALL_MSG (Y) SHORT_CALL_MSG (N)
Name or number of caller and

NAME_NUMBER_DISPLAY (N) Name or number of caller
Name or number of called party
Name and number of caller and

NAME_NUMBER_DISPLAY (Y) Name and number of caller
Name and number of called party
6-23
KEYSET: The following parameters apply to all FlexSet, FlexSet-IP, DKT,

FlexAir wireless handset, T207M, T208M, T207M/NP, T208M/BL, and Keyset
stations.
ACD PROTOCOL Both / ACD / CSTS_ACD

TYPES [15]
Defines the protocol type for connecting the Coral system (via APA) to an external
CTI server for ACD applications that monitor call center activities.
CSTS - Coral Supported Telephony Services.
ACD Protocol Type Usedf For:
ACD ACD systems supporting non-CSTS protocol.

(Applicable for CCM version 2)
CSTA_ACD ACD systems supporting CSTS protocol.

Applicable for CCM version 3 or higher.
Both Coral systems supporting both CSTS and

non-CSTS protocols.
DATE_MODE E (European)/U (USA)

(Eu/USA) [16] Eu: E
The date display on the keyset can be set to either the European standard
(dd/month/yy - 26 May 2052), or the USA standard (month/dd/yy - 05/26/52). This
parameter also influences how the LAST POWER FAIL time is displayed, as well as
enables an AM/PM option in Time Set (page 25-2) which also enables the AM/PM
display on Keysets/FlexSets.
EXT.ID. [17] Yes/No

Displays the station name and dial number on the second line of the keyset display
window, when set to Yes. This information is shown on idle stations when the Idle
Display Feature is activated and a name has been entered into the system port
database, see Port List - Physical Location on page 6-68.
HOLD_AUTO_ACTIVE Yes/No
[18]
When defined as Yes, the keyset user can press the hold key to automatically
recover a call already placed on hold (i.e., there is no need to dial the activation
code: 11 or *1).
6-24
MSG_AUTO_ACTIVE Yes (activation code not required)/ No (activation code required)

[19]
Message Auto Active enables retrieving the pending message by pressing the
Message key without the need to dial an activation code. When set to No, the user
must dial the activation code after pressing the message key, before the pending
message can be retrieved.
V.P.RING_AFTER_ Ring After Transfer (Yes)/Transfer to Speaker (No)

XFER [20]
Voice Page Ring After Transfer determines whether a call transferred to a keyset,
which has Voice Page On, will ring (Yes), or is immediately connected to the
station when the party originating the transfer disconnects (No).
USER_CANNED_ Yes (Enables User Canned Messages feature);

MESSAGES [21] No (Enables Room Status feature)
SAU Requirement
Defines whether the system enables either the User Canned messages feature or the
Room Status feature for this Coral system.
Both features are mutually exclusive, and cannot be activated simultaneously in the
same Coral system. See the Feature Authorization branch in the Feature
Authorization branch (FEAT, 1),HOTEL/MOTEL (page 3-20) and CANNED
MESSAGE (page 3-25)) to determine which feature is available in your system.
The Unauthorized Err message appears when setting this parameter to Yes
in unauthorized systems.
USER_CANNED_ Yes/No

MESSAGES_
OVERRIDE_2nd_LINE
 This parameter is only available when the above parameter is set to Yes.
[22] Set this parameter to Yes to enable the canned text message to override the second
line of the calling party’s display which sometimes displays other information
about the call.
This is necessary for callers to destinations where the second line display is
occupied with call information (such as ACD Hunt groups or other transferring
destinations).
This parameter overrides the next parameter, SYSTEM_WIDE_NAME_RETENTION
[23].
6-25
SYSTEM_WIDE_ Yes/No
NAME_RETENTION
[23]

If SYSTEM_WIDE_NAME_RETENTION [23] is set to Yes, the next parameter,
ACD/LIB_NAME_RETENTION [24], does not appear.
Set this parameter to Yes in order to firstly present the calling party’s name on all
system keyset displays as well as to retain the name/number when the call is
transferred on to further stations or groups.
Also, set this parameter to Yes in order to use a Public Library name as a message.
Create the Public Library in LIB, 0 (see page 11-2).
ACD/LIB_NAME_ Yes/No
RETENTION [24]
Set this parameter to Yes in order to present the calling party’s name on the keysets
of all direct calls to ACD Hunt Groups and Public Library groups and to retain the
name/number when the call is transferred.
NAME_RETENTION_ Yes/No
OVERRIDE_2nd_LINE
[25]

This parameter does not appear if the above two parameters, SYSTEM_
WIDE_NAME_RETENTION [23] and ACD/LIB_NAME_RETENTION [24] are
both set to No.
Defines whether the second line of the keyset can be overridden with the name of
the calling party name and/or number when either SYSTEM_WIDE_NAME_
RETENTION [23] or ACD/LIB_NAME_RETENTION [24] is set to Yes.
PI-LANGUAGE [26] D/S/T/F (Default, Second, Third, Fourth)

SAU Requirement 2nd LANGUAGE, 3rd LANGUAGE, 4th LANGUAGE on page

3-20
Defines which language will be used by the PI system during Names programming
(for a list of the languages used in each system see LANGUAGE [56] on page 9-57).
A maximum of four languages may be loaded onto each Coral system. When the
selected language is written from right to left, all keyset displays are automatically
set to display that language and the multilingual display is blocked.
The correlation between the Default, 2nd, 3rd and 4th Languages is fixed by the
manufacturer for each system before First Initialization is performed.
TWO_WAY_HOLD [27] Yes/No
 Boss Groups Only

Defines whether or not two-way hold can be activated in the system.
Set this parameter to Yes so that the members of two different Boss Groups can
access their boss group line, place the two calls on hold and allow the two other
“Boss” members to speak directly with each other by picking up the held line.
6-26
FROM_3WAY_BOSS_ Yes/No
TO_CONF_CALL [28]

Boss Groups Only
When a boss group line is engaged in a 3-way conversation, set this parameter to
Y in order to allow a fourth participant to join the conversation. The system does
this by transferring the line to an available conference circuit.
ON LINE ACCOUNT Yes/No

CODE [29]
Set this parameter to Yes to enable dialing the online account code during a call
without placing the called party on hold.
The account code must be entered after pressing a DSS key programmed with the
account code feature dial number (default code: #1990).
CONTINUOUS_ A (any party of the conference parties),

CONFERENCE_ I (initiator of the multi-party conference)
CONTROL [30]
 After the initiator leaves the conference, any party may add further
members.
Defines which party is allowed to add further members to a Continuous Conference
(i.e. a multi-party conference created from a 3way call) A or I.
FLASH_CALL_ Yes/No
BUTTON_IN_
Defines whether or not a keyset call buttons (DSS, LINE, TRUNK or LOOP button)
OUTGOING_CALLS
can be configured to flash when a call is made and during ringback tone. When set
[31]

to Y (yes), a programmable button is enabled to flash until a call is answered.
In order for a programmable button to flash, one of the items listed below must be
programmed. If more than one number or feature code has been programmed, only
one programmed button will flash, in the following order of preference:
• The dialled destination (DSS station or trunk only)
• Loop (121)
• Outgoing loop (125)
• Line (126)
Buttons that dial public libraries always flash when pressed.
INTERNAL/EXTERNAL Yes/No
_EQUAL_RING [32]
When set to Y (Yes), all keysets and SLT ring will be identical for internal and
external incoming calls. And will be as internal call.
When set to N (No), all keysets and SLT ring will be different for internal and
external incoming calls.
6-27
DKT: The following parameters apply to T200M series, DKTs and FlexSets:
MILITARY_TIME [33] Yes (24 hour clock)/ No (12 hour clock)

Determines whether the T200Ms, DKTs and FlexSets time display uses the
military standard (24 hour clock) or the USA standard (12 hour clock).
DSP48_NAME_FIELD S/F
(Short/Full) [34]
 This parameter applies only to T207Ms, DKTs, FlexSet 120D equipped
with a DSP48 module (2 rows x 24 characters).
and to FlexSet 120S and 121S
Each Port is given a Short name-up to 5 characters and a Long name-up to 16
characters (see page 6-72). This parameter defines the Name Field characteristics
by determining whether the Port Names are Short or Full names. A Short Name
includes all five characters of the Short Name and a Full Name includes the first
nine (or 16 when available) characters of the Long Name.
DSP48_ELAPSE_ Short/Full
TIME_MODE [35]
Defines whether the Keyset Elapsed Time Display (feature code: #129) is shown
in Short (S) or Full (F) mode.
The Full display leaves the ANI displayed on the left and the Elapsed Time in
hour:minute:seconds format on the right. If the ANI is too long the words EXT
ANSWER may be shortened and the ANI may be shortened or deleted.
This display mode is used for DSP80 units.
EXT ANSWER C0-03 12125551234 00:12:10

John Doe 2264
The Short display deletes the ANI. The Elapsed Time remains in its
hour:minute:second format on the left side of the display and the word “ELAPSE”
appears on the right side of the display.
This display is used for DSP48 or DSP32 units.
00:12:10 ELAPSE
John Doe 2264
6-28
SLT: The following parameters apply only to SLTs.
MAGNETO_DISC_ Yes/No
RING [36]
Magneto Disconnect Ring determines whether or not a Magneto Station (8SM and
8SMipx card ports) is disconnected after sending a ring voltage to the Coral, while
a call is established (see RING_SIG_RJCT [9] on page 9-127).
RECALL_TK_AFTER_ Yes/No
HKFLS [37] CC1: No
An extension is connected with a trunk. When the extension implements a
hookflash and replaces the handset; this parameter defines whether to return the
trunk to the extension or to release the trunk. Because of spikes on the telephone
line, the Coral first identifies a hookflash and afterwards an onhook.
This parameter is designed to prevent “arbitrary ringing” when the extension is connected
with the trunk; the extension decides to disconnect and replaces the handset.
Enter Y to return the trunk to the extension.
Enter N to release the trunk.
HF_FOR_HOT_ST_ Yes/No
INTERNAL_SERVICES
Defines, system wide, whether a Hot-Immediate SLT user can access internal dial
[38]
tone when set to Yes. This immediate releases the trunk seized so that it may be
used by other users.
The Hot Immediate station user hears one of the following when lifting the

receiver:
• External Dial Tone when defined for the Hot Immediate destination.
• Busy - if Hot Immediate trunk is busy
• Illegal - if the station COS does not allow connecting to or dial on the Hot
Immediate station destination (trunk/trunk group).
When this parameter is set to Yes, the user can press Flash or Xfer to obtain
internal dial tone. The internal dial tone can be useful for using other Coral features
and accessing other internal services.
For example, when this station user hears an illegal tone, the user can change the station
COS by receiving an internal dial tone and thus enable the Hot Immediate feature.
6-29
SLT (DTMF/Hookflash) D (Dial out digit); H (Hookflash)

[39] Eu: H
This parameter applies only to Rotary/Pulse SLTs (type 500) connected to:
• SLT ports defined DTMF in TYPE [22] on page 9-10 or
• trunk ports defined DTMF in TYPE [4] on page 8-12
Controls the interpretation of the digit “1” dialed from a rotary (pulse) SLT as a
hookflash request (Enter H) or a dial out digit (Enter D).
CID_NAME_SUPPORT Yes/No
[40]
Enables the caller name (up to 15 characters) in addition to the number to be
displayed on SLT sets or Caller ID display devices.
CID_NUMBER_ 1..10..16
LENGTH [41]
Defines the maximum number of digits that may be displayed on an SLT with
built-in display or Caller ID external device.
N_CID_ON_IDSP_ 0..32..128
CARD [42]
Defines the maximum number of FSK tone generators out of the maximum
available on each one of the following cards:
• iDSP
• U-RMI Office
• U-MR Office
• IPx 500M (MSBipx Hardware Issue-0200X1000 or higher)
• CDRS 200E
This setting determines the maximum number of Caller IDs that can be
simultaneously transmitted by each card installed in the Coral system for analog
trunks.
6-30
APPLICATION
BUSY/IDLE
EVENT:
CAP_MSG_ A (All), S (Specific)
DESTINATION [43]
When more than 100 APA units are to be installed and used by the system,
this parameter should be set to Specific (S) so that a Primary and
Secondary message destination may be defined.
This parameter defines a universal message destination for busy/idle messages to
units defined as PCC or CAP. In this manner, the messages for all the units may be
concentrated at one Specific destination. Otherwise, the busy/idle messages for all
the PCC or CAP defined units will continue to be sent to each and every unit (All).
When Specific is defined, a Primary and Secondary destination can be defined in
the next two parameters.
 The next two parameters appear only if CAP_MSG_DESTINATION [43], above, is

defined as Specific.
PRIMARY [44] None or Keyset Dial Numbers defined as PCC in PROTOCOL TYPES: PCC
[46] on page 9-47 of the Keyset Definition.
Defines the primary destination for busy/idle messages of all the PCC or CAP
defined units.
SECONDARY [45] None or Keyset Dial Numbers defined as PCC in PROTOCOL TYPES: PCC
[46] on page 9-47 of the Keyset Definition.

Defines alternate destination for busy/idle messages of all the PCC or CAP defined
units when the Primary destination is None, undefined, unavailable or invalid.
ACD_TRK_ All trunks/D.I.L. only

INDICATION [46]
ACD only
ACD applications receive Coral messages regarding the status of the trunks: busy
or idle.
This parameter indicates whether the Coral reports the status of all trunk types or
only of LS/GS trunks defined as Direct In Line.
CAP/ACD_ST_ Yes/No
LOCKOUT_REPORT
Defines, system-wide, whether or not the Coral reports to ACD or PCC
[47]
applications when SLTs are locked out.
When this parameter is set to Yes, the ACD/PCC receives messages when the SLT
station enters Lockout and when it returns to idle.
6-31
APPLICATION
“PRESENT”
EVENT:
CAP_ Yes/No
REINTRODUCTION_
Defines whether or not a CAP application is prompted with a PRESENT message
OF_MA_QUEUED [48]
while a multi-appearance station receives a second (wait) call.
CAP_REPORTS_ Local/Network
STATION_NUMBER
Non-UDP Networks only
[49]
Defines, system-wide, the Coral caller number to be reported to the CAP
application: either the local station number or the network number. The network
number is composed of the local number and the node prefix.
CAP_THIRD_PARTY_ Yes/No
D.N./ANI [50]
When a station in the Coral initiates a call, a PRESENT message is sent to the CAP
via APA. If the caller placed the call on a special hold (“on the back”, by pressing
Xfer), the Coral can include the third party identification in the PRESENT
message. Some CAP applications require the third party information while other
do not.
This parameter defines whether or not the third party information is included in the
PRESENT message if there is a third party held by the calling party.
The third party is identified either by its dial number if it is an internal destination,
or by its ANI, if it is an external destination.
VM SOFTKEYS Yes/No
SUPPORT [51]
This parameter is relevant only when Version Q915, iCMC cards support
FlexSets equipped with softkeys (FlexSet 280S/120S-Version 3.5).
The Q-915 iCMC card does not support the Voicemail controlled by softkeys.
Set this parameter to No to enable Voicemail on FlexSets 280S/120S with version
3.50 supported by the iCMC cards with Version Q915. A full array of Voicemail
features is provided for these FlexSets by using the keypad as opposed to the
softkeys.
6-32
System Features - Intercept/Incomplete ç SFE,3 [0,0,4,1,3]
The Intercept parameters relate only to calls that are intercepted and is divided into
Intercept Origin and Intercept Relevant sections which help define how the
intercepted calls will be routed. The intercept destinations, however, are defined in
System - Night Service - Definition.
Intercept Origin parameters define whether a call will be intercepted, i.e. routed to
another destination or offer a reorder tone (based on where the call originated from:
station or type of trunk). Other relevant parameters for the call, defined in Intercept
Relevant, may also define whether to route the intercepted call to another
destination or only offer a reorder tone.
 EXAMPLE: a caller dials an illegal number over an FXO trunk. To have

this call routed to another destination (e.g. a voice message), LGS in
Intercept Origin must be defined as Yes (Route).
• If the dialed number is defined as illegal because it is not allowed by the
caller’s COS, in order to route this call to a voice message, define COS_FAIL
in Intercept Relevant as Yes (Route).
• However, if the dialed number simply does not exist in the numbering plan,
in order to have this call receive a reorder tone, define DIAL_FAIL in
Intercept Relevant as No (Reorder).
The Incomplete parameters relate only to calls that could not reach their
destination and is divided into three sections.
• On Busy: The call is uncompleted because the destination is busy.
• On Illegal/No Answer: when the destination does not answer or is in DND
mode or is considered an illegal destination.
• After Supv Recall: for PWDS calls after the Supervision Recall timer has
System Features - Intercept/Incomplete SFE,3

expired.
INCOMPLETE_ The following parameters apply only to incomplete calls when the destination is
ROUTING- busy.
ON BUSY
E&M [0] Route (Yes)/ Tone (No)

Determines if an incomplete call, arriving from an E&M trunk to a busy station, is
routed to the incomplete calls destination (see Night Service Definition, Chapter
12) or caller hears a busy tone. The destination is typically the Attendant Console
(the system default).
LGS [1] Route (Yes)/Tone (No)

Determines if an incomplete call, arriving from a a Central Office loop or ground
start trunk to a busy station, is routed to the incomplete calls destination (see Night
6-33
Service Definition, Chapter 12) or caller hears a busy tone. The destination is
typically the Attendant Console (the system default).
DID [2] Route (Yes)/Tone (No)

Determines if an incomplete call, originating from a Direct Inward Dial (DID)
trunk to a busy station, is routed to the incomplete calls destination (see Night
Service Definition, Chapter 12) or caller hears a busy tone.
ISDN [3] Route (Yes)/Tone (No)

Determines if an incomplete call, originating from a PRI or TBR (BRI) trunk (for
ISDN) to a busy station, is routed to the incomplete calls destination (see Night
Service Definition, Chapter 12) or caller hears a busy tone.
6-34
INCOMPLETE The following parameters apply only to incomplete calls defined as when the
ROUTING - ON destination does not answer or is considered an illegal destination or the destination
ILLEGAL station in DND mode or PWDS calls after SUPV_RECALL Time-out.
 The incomplete destination is defined in NIGHT Service, Chapter 12.

NO_ANS
.E&M [4] Route (Yes)/Tone (No)

Determines whether an incomplete call, arriving from an E&M trunk, is routed to
the incomplete calls destination, when set to Yes (see Night Service Definition,
Chapter 12) or the caller hears a reorder tone, when set to No. The destination is
typically the Attendant Console (the system default).
.LGS [5] Route (Yes)/Tone (No)

Determines whether an incomplete call, arriving from a Central Office loop or
ground start trunk, is routed to the incomplete calls destination, when set to Yes
(see Night Service Definition, Chapter 12) or the caller hears a reorder tone, when
set to No. The destination is typically the Attendant Console (the system default).
.DID [6] Route (Yes)/Tone (No)

Determines whether an incomplete call, arriving on a Direct Inward Dial trunk, is
routed to the incomplete calls destination, when set to Yes (see Night Service
Definition, Chapter 12) or the caller hears a reorder tone, when set to No.
.ISDN [7] Yes (Route)/No (Tone)

Determines whether an incomplete call, arriving on a PRI or TBR (BRI) trunk (for
ISDN), is routed to the incomplete calls destination, when set to Yes (see Night

Service Definition, Chapter 12) or the caller hears a reorder tone, when set to No.
AFTER_SUPV_ Yes (Route) /No (Disconnect)

RECALL [8] CC1: No
When two PWDS-type ports are communicating and the SUPV_RECALL time
period terminates (see page 6-4), this parameter will determine the outcome:
Enter No to disconnect the two ports and make them available for other calls.
Enter Yes to transfer the two ports to an incomplete calls destination to renew the
call or disconnect it.
6-35
INTERCEPT The following parameters apply only to intercepted calls.

 Each of these parameters is directly related to the range definition defined
ORIGIN
in INTERCEPT RELEVANT (page 6-37).
ST. [9] Yes (Route)/No (Reorder Tone)

Determines whether an illegal call, defined by the relevant intercept parameters,
that has originated at a station is routed to the intercept call destination, when set
to Yes, or if the caller hears reorder tone when set to No.
E&M. [10] Route (Yes)/Reorder Tone (No)

Eu: Yes
Determines whether illegal calls that originated at an E&M trunk are routed to the
intercept call destination (Y) or if the caller hears reorder tone (N).
DID. [11] Route (Yes)/Reorder Tone (No)

Eu: Yes
Determines whether illegal calls that originated from a Direct Inward Dialing trunk
are routed to the intercept call destination (Y) or if the caller hears reorder tone (N).
ISDN. [12] Route (Yes)/Reorder Tone (No)

Determines whether illegal calls that originated at a PRI or TBR (BRI) trunk (for
ISDN) are routed to the intercept call destination (Y) or if the caller hears reorder
tone (N).
DISA [13] Route (Yes)/Reorder Tone (No)

Determines whether illegal calls that originated at a preassigned trunk are routed to
the intercept call destination (Y) or if the caller hears reorder tone (N).
DISA calls are treated by the Coral as calls from an internal station and are allowed
to dial within the system and access system features using DTMF signaling.
6-36
INTERCEPT The intercept destination is defined in Night Service, Chapter 12.

RELEVANT
The following parameters apply only to intercept relevant calls.
Each of these parameters is directly related to the range route defined in Intercept
Origin. In order to intercept a call, range route must be defined as Yes for both
Intercept Relevant and Intercept Origin.
TOLL_BAR [14] Route (Yes)/Reorder Tone (No)

Eu: (Yes)
When Toll Barriers are in effect, TOLL_BAR routes the call to an intercept
destination when set to Yes. The caller hears a reorder tone, when set to No.
COS_FAIL [15] Route (Yes)/Reorder Tone (No)

Eu: (Yes)
When a call is denied because of Class of Service failure, COS_FAIL defines

whether the call will be routed to an intercept destination (Y) or the caller hears a
reorder tone (N).
DIAL_FAIL [16] Route (Yes)/Reorder Tone (No)

Eu: (Yes)
When an illegal number is dialed, DIAL_FAIL routes the call to an intercept

destination (Y) or the caller hears a reorder tone (N).
ACCOUNT [17] Route (Yes)/Reorder Tone (No)

VFAC Fail defines the destination of an incorrect Verified Forced Account Code.
When an incorrect Account Code number is dialed, ACCOUNT routes the call to an

intercept destination (Y) or the caller hears a reorder tone (N). Station callers are
routed after the third fail. E&M/DISA callers are routed after the first fail.
UNDEFINED [18] Route (Yes)/Reorder Tone (No)

Eu: (Yes)
When a call is sent to an undefined station, UNDEFINED routes the call to an

intercept destination (Y) or the caller hears a reorder tone (N).
6-37
System Features - Call Forwarding ç SFE,4 [0,0,4,1,4]
CF_NO_ANS
INT/EXT
ONE_STEP [0] Yes/No
Eu: Yes
Call Forward No Answer One Step determines whether a call should keep
forwarding when calls reach a “No Answer” situation (N) or the call should be
forwarded only once (Y). Enter Yes to limit an infinite ring condition when two or
more stations defined with CF_NO_ANS call forward each other.
FOR_M.A. [1] Yes/No

Call Forward No Answer For Multi-Appearance determines whether or not call
forwarding with “No Answer” is invoked when a station is defined as
Multi-Appearance.
TIMED_ Determines the system-wide time period for forwarding calls. Two such time
FORWARD periods can be defined. The start and stop times for each period are independently
INT/EXT defined. The user has the option to override the timed call forward by not invoking
it at his or her station. The user can also override any system-wide defined
destinations that are programmed into the database.
Some typical usages for Timed Call Forward include:
• Extended Care Facilities
System Features - Call Forwarding SFE,4 [0,0,4,1,4]
• Geriatric Institutes
• School Dormitories
• Business environments requiring collective calls forward features during lunch
breaks or after normal business hours to Voicemail or other specific
destinations.
• Network applications where calls coming into a remote site after working
hours are automatically forwarded to the hub.
1ST_START [2] None or 24 hour clock (hh:mm)

Defines the beginning of the first call forward period.
Both 1ST_START and 1ST_STOP must be defined for the first time interval to be
defined for Timed Forward.
1ST_STOP [3] None or 24 hour clock (hh:mm)

Defines the end of the first call forward period.
Both 1ST_START and 1ST_STOP must be defined for the first time interval to be
6-38
2ND_START [4] None or 24 hour clock (hh:mm)

Defines the beginning of the second call forward period.
Both 2ND_START and 2ND_STOP must be defined for the second time interval to be
2ND_STOP [5] None or 24 hour clock (hh:mm)

Defines the end of the second call forward period.
Both 2ND_START and 2ND_STOP must be defined for the second time interval to be
System Features - Call Forwarding SFE,4 [0,0,4,1,4]
6-39
System Features - Camp-On ç SFE,5 [0,0,4,1,5]
IMM. CAMP [0] [0] Yes/No

Immediate Camp-On defines the system-wide manner in which the originator of
the Camp-On feature answers the Camp-On call back. When set to Yes, the
originator answers the call-back and the destination station immediately rings.
When set to No, after the originator answers the call, the digit 2 must be dialed or
the Camp-On button must be pressed to activate ringing at the requested
destination. In either case, the camped-on station must first be idle before
activating this feature.
ST_CMP_HUNT [1] Yes/No

Station Camp On ACD/UCD Hunt Group determines whether a station user calling
a busy Hunt Group receives a busy tone (No) or automatically camps-on the busy
group (Yes).
DID_CMP_HUNT [2] Yes/No

DID Trunk Camp On ACD/UCD Hunt Group determines whether a DID trunk
calling a busy Hunt Group receives a busy tone (No) or automatically camps-on the
busy group (Yes).
INTERNAL/EXTERNAL Yes/No
_EQUAL_PRIORITY
When both an internal and external call arrive at a busy station concurrently, this
[3]
parameter defines whether the calls have equal priority to enter the system (Yes) or
System Features - Camp-On SFE,5 [0,0,4,1,5]
unequal priority (No).

When set to Y, then the calls are assigned priority on a first in first out (FIFO) basis.
When set to N, external calls have priority over internal calls.
6-40
System Features - Hotel ç SFE,6 [0,0,4,1,6]
Wakeup
ANN_DEST [0] None (Wakeup Announcer is fed from MUSIC SOURCE #0),
Station Number, Trunk Number, Trunk Group, Routing Access,
Dial Service, Hunt Group, Boss Group, Public Speed Call Library,
DVMS port number
Defines the wakeup announcer destination when answering wakeup calls.
When defined as none, music is played from MUSIC SOURCE #0.
Music is defined at the FROM TO MUSIC-SOURCE on page 4-45 (IP Stations hear
tones and no music).
Wakeup report destination is defined through Wakeup Control beginning on page
20-2.
Simultaneous Wakeup Calls: When required, simultaneous wakeup calls can be
made to individuals requesting “wakeup” at the same time. This is particularly
useful for hotel/motel applications, when guest groups need to wakeup at the same
hour. To program multiple simultaneous wakeup requests, the announcer should be
defined as the destination. The announcer device can be attached to an SLT port or
a dedicated message can be programmed for a DVMS port.
When attached to an SLT port the port should be defined both as ANNOUNCER [23]
and MULTI_APPEARANCE [24] (page 9-11).
When attached to a DVMS port, a specific DVMS wakeup message must be
System Features - Hotel SFE,6 [0,0,4,1,6]

defined for the DVMS Port, see DVMS Port beginning on page 23-2.
Announcer can be provided by SeaMail, IPC/uCMC, IPC/SFC and iVMFipx.
These cards replace the discontinued 4VSN card
Once this set up is arranged, all guests requesting wakeup for the same hour will
hear a waking ring at that hour. If the announcer destination is busy, the awoken
party will hear a ringback tone and enter the announcer queue. When the announcer
goes idle, the queued calls will be routed to the announcer and all the guests will
hear the recorded announcement at the same time.
The system can handle up to ten simultaneous wakeup calls. More than ten such
calls are broken down into groups of ten, with thirty second intervals between each
wakeup response.
INCOMPLETE_ALERT Yes/No
[1]
Determines whether an alert call is generated whenever a wakeup attempt fails.
The fail indication is routed to the designated incomplete call destination.
6-41
CHECK IN/OUT The following parameters are available when the Check-Out or Check-In feature is
activated.
OUT_COS. [2] 0 to maximum as defined in Sizes-Chapter 4

Determines the system COS for stations which are in Check-Out mode. When
check-in is applied, the room (station) returns to its previous COS (defined in PRM_
COS/SEC_COS parameters (see Chapter 9- Station Controls, SLT And Keyset
Definitions).
PCC_UPDATE_COS Yes/No
[3]
Determines whether or not the COS status of the Check-In port can be changed.
When this parameter is set to Yes, then the COS can be changed via the PCC/CAP
terminal.
WHEN_BUSY [4] Yes/No

Permits activating the Check-In or Check-Out features when the station is busy.
SAVE_WAKEUP [5] Yes/No

Determines whether the existing station wakeup request is saved while Check-Out
or Check-In is activated.
CANCEL_CFWD Yes/No
INT/EXT [6]
Determines whether the existing station Call Forward features are canceled while
Check-Out or Check-In is activated.
System Features - Hotel SFE,6 [0,0,4,1,6]
6-42
System Features - Messaging ç SFE,7 [0,0,4,1,7]
ATT_MSG_HOT_LINE Yes/No
[0]
Attendant Message Hot Line determines whether activating an attendant message
causes a station to be defined as a hot line to the attendant. As soon as the user
operates a telephone feature, the station is routed to the attendant who left the
message and the message lamp goes out. When set to No, attendant messages can
only be canceled by the attendant and the feature can be operated only by pressing
a key programmed with this feature.
ATT_MSG_DEST [1] None, Station, Boss Group, Hunt (UCD/ACD) Group

Determines the call back message destination for the attendant message feature.
CLA_MSG_ None, Any valid port or station dial number or Hunt group
ORIGINATOR [2]
Defines the station originator for Attendant Messages from the CoraLINK Adapter
(via CLA or MAP cards).
FLEXICALL/FREEDOM None, Any Coral Keyset station

HELP DEST [3]
Define the Help Requesting destination for all FlexiCall and Freedom/IRSS calls.
When this parameter is defined, FlexiCall and Freedom/IRSS callers can activate
the Help Requesting feature or a third party application (depending on the system
setup) from their telephones by dialing the HELP FlexiCall/Freedom feature code,
see CALL RECORDING / HELP REQUESTING (page 5-53) in FlexiCall/IRSS (Freedom)
Feature Codes menu.
 For FlexiCall/Freedom cellular recording, when Coral Navigator supports
System Features - Messaging SFE,7 [0,0,4,1,7]

the phones:
Define this feature with the IP-APA port station number located on the
IPC2 card.
If a CSTS application is defined here, the Coral notifies the application with a
special event.
6-43
MSG_LAMP_&_RING Yes/No
[4]
For SLTs, the system must be equipped with Single Line Telephone
• Full size: 8/24SA, 8/16/24SLS, or 4/8/16SH card
• IPx 500: 8/16/24SAipx or 8/16SLSipx card
• CDRS 200E and CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
• IPx Office: 4/8/16/24SA Office, 4/8/20S Office, 4SA+8Fx Office, 4SA+16Fx
Office, 8SA+8Fx Office or 8SA+16Fx Office card
With the Jumper Setting in the SH position plus message waiting lamps
physically installed on the telephones.
Message Waiting Lamp With Ring, when set to Yes, the message waiting indication
consists of both an illuminated message lamp and a message ring for SLTs and
Keysets. When set to No, only the message lamp lights. This parameter applies
when ATT_MSG_HOT_LINE (above) is set to Yes.
DKT/DST_MSG_LAMP Yes/No
[5] Eu2: No
 This parameter applies only to the special message lamp for keysets and
does not affect the MSG programmed key LED or any other programmed
LEDs.
Lights a blinking message lamp for all pending messages for Keysets/FlexSets.
MSG_CLEAR_ON_ R(Ring), C(Connect)

RING/CONNECT [6] CC1: R
Activates two options of controlled message erase:

C (upon connect): a pending message status can only be cleared “Upon Connect”
(C), which clears the message when a call is placed to the pending party.
R (upon ring): clears the message status when the pending party rings back. Thus,
a message is never accidentally erased.
6-44
SLT_RECEIVE_MSG_ D (Distinctive Dial Tone), C (Confirmation Tone)

TONE [7]

This feature is of particular concern to SLT Voicemail users because the
SLT has no message lamp. Therefore, a more distinctive Confirmation
Tone alerts the user to check the Voicemail.
This parameter relates to the following SLT card/s:
• CDRS 200E and CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
when programmed or the jumper is set to the SH position.
It determines which tone type is heard when the handset is lifted for messages left
at this station by another station or by Voicemail.
WHISPER_PAGE_ Music/Silence
PARTNER_HOLD [8]
When a user is engaged in a conversation and he receives a whisper page, he can
place the other side of the conversation on hold and answer the whisper page. The
party on hold can hear music or silence as defined in this parameter.
6-45
DVMS: The following parameters apply to systems equipped with a 4VS or 4VSN card.
MAX_DVMS_MSG [9] 4VS: 1..100

4VSN: 1..32
 Each 4VSN card permits a maximum of 32 recorded announcements.

Thus, it is advisable to reduce the default range to 32 (the maximum
number of recorded announcements for this card).
Determines the maximum number of available DVMS messages that can be
utilized. This parameter influences MSG [0] (page 23-2) in [PDB,4], and DVMS_MSG
[31] (page 5-43) in [NPL].
#DVMS_REPEAT [10] 1..255

Determines how many times the user, who is routed to the DVMS message, hears
the message.
FWD_NANS INT/EXT None, DVMS MSG dial number or DVMS Port with Special MSG defined in
[11] PDB, see Chapter 23
Determines which DVMS message is provided before the call is forwarded to the
Call Forward No Answer destination.
FWD_BUSY INT/EXT None, DVMS MSG dial number or DVMS Port with Special MSG defined in
Call Forward when Busy destination.
FWD_ALL INT/EXT None, DVMS MSG dial number or DVMS Port with Special MSG defined in
Determines which DVMS message is provided before the call is forwarded to a
Forward All Calls destination.
INCOMPLETE_NANS None, DVMS MSG dial number or DVMS Port with Special MSG defined in
Incompleted Calls Destination When No Answer.
INCOMPLETE_BUSY None, DVMS MSG dial number or DVMS Port with Special MSG defined in
Determines which DVMS message is provided before a call is forwarded to an
Incompleted Calls Destination when Busy.
6-46
MLPP Special
Announcements
BLOCKED None, any keyset defined ANNOUNCER [34] on page 9-42, SeaMail port,
PRECEDENCE ANN DVMS MSG dial number or DVMS Port with Special MSG defined in PDB
(BPA) [16]
This DVMS message is provided to MLPP calls that could not be pre-empted
because the called party was busy with a call of equal or higher precedence.
UNAUTHORIZED_ None, any keyset defined ANNOUNCER [34] on page 9-42, SeaMail port,
PRECEDENCE_ DVMS MSG dial number or DVMS Port with Special MSG defined in PDB
LEVEL_ANN (UPA)
This DVMS message is provided to station users that try to use a higher MLPP
[17]
precedence level than their COS allows.
BUSY STATION NOT None, any keyset defined ANNOUNCER [34] on page 9-42, SeaMail port,
EQUIPPED FOR DVMS MSG dial number or DVMS Port with Special MSG defined in PDB
PREEMPTION (BNEA)
This DVMS message is sounded to the calling party when the called party is not
[18]
pre-emptable because its station COS is defined with PREEMPTABLE
[80] (page 7-24) set to N.
ISOLATED CODE None, any keyset defined ANNOUNCER [34] on page 9-42, SeaMail port,
ANNOUNCEMENT [19] DVMS MSG dial number or DVMS Port with Special MSG defined in PDB
This DVMS message is used to indicate to the caller that the system is currently
malfunctioning and the call cannot be completed as requested. The user should try
again at a later time.
6-47
SLT/KEY_V.M: The following parameters apply only to systems equipped with Voicemail:
DISCONNECT_SEQ None
[20] Up to an 8 character string comprised of the following 16 DTMF signals:
*, #, 0..9, A-D
Defines the DTMF tone sequence to be sent to the Voicemail on SLT/Keyset
system indicating an onhook situation (disconnect) at the Coral for calls. When
NONE is selected, no keys will transmit DTMF signals. Therefore, in order for
DTMF signals to be sent during disconnect, any option other than NONE must be
selected.
This feature is useful for any application that requires reports to be sent whenever
a station answers or disconnects a call. For example, numerous billing systems
require accurate information regarding the exact time a call was initiated and
completed for the purpose of billing.
ANSWER_SEQ [21] Up to an 8 character string comprised of the following 16 DTMF signals:

*, #, 0..9, A-D
Defines the DTMF tone sequence to be sent to the station that has been defined as
ANSWER_DISCONNECT_SIGNAL [38], indicating an answer situation at the Coral
for calls. When NONE is selected, no keys will transmit DTMF signals. Therefore,
in order for DTMF signals to be sent during answer, any option other than NONE
must be selected.
This feature is useful for any application that requires reports to be sent whenever
a station answers or disconnects a call. For example, numerous billing systems
require accurate information regarding the exact time a call was initiated and
completed for the purpose of billing.

Answer DTMF signals are sent for any internal and external port. Ports that do not
have call supervision will send a DTMF signal when the call reconnects after
timeout. In addition, 3WAY calls also support DTMF Answer signaling for the
third and fourth callers joining the group.
DTMF Answer signals are not sent:
• When parties break into a call
• When calls are disconnected during answer sequence
• When calls are reconnected from HOLD, PARK, PAGE_Q, and Hookflash
• From ports defined as RECEIVE_SPKR_STATUS [13]-Y AND ANSWER_
DISCONNECT_SIGNAL [38]-Answer or Both (Route: SLT and KEY)
.
6-48
DEFAULT_ None;
DESTINATION [22] Any valid internal dial number or network number via Public Library
This parameter determines the system Voicemail center (e.g. SeaMail, LxCMC,
WiCMC, etc.) access code.
This access code also enables a T200M series, FlexSet-IP 280S,
FlexSet 281S/121S/280S/120S user to access the Voicemail by pressing a soft key.
6-49
System Features - Tones ç SFE,8 [0,0,4,1,8]
TICK_TONE [0] Yes/No

Determines whether a tick-tone is heard while dialing, when set to Yes.
BREAK-IN_WARNING Yes/No
[1]
Break In Warning Tone sets a Break-In warning tone to be heard by the conversing
parties during the entire break-in period (when set to Yes). The Break-In tone
cadence is defined in Feature Timers beginning on page 6-2.
ORIGINATOR_CALL_ Yes/No
WAITING_TONE [2] CC1: Yes
Defines which ringback tone is sent to the CALLING station when the busy
destination is defined as Multi Appearance or when using Call Offer (i.e., by
dialing XFER-8 the caller alerts the busy destination that a call is waiting by
sending a tone.)
This parameter defines whether the caller hears a second ringback (see 2nd R.back
on page 6-97), when set to Yes or regular Ringback tone, when set to No.
WP_GAIN_COMP [3] -18..-12..+12 db

Defines the receiving gain compensation value for the volume of the whisper page
voice announcement. This value applies to all system stations.
! Warning:
System Features - Tones SFE,8 [0,0,4,1,8]
For Keysets/FlexSets: Increasing the gain from the default value may
enable the connected side which should not hear the whisper page, to
hear the whisperer.
Decreased Increased
Gain Gain
-18db -12db 0 db +12db
Also, if the whisperer uses a loud voice, the connected side that should
not hear the whisper page, may hear the whisperer.
6-50
M_LAW [4] Yes (M-LAW)/No (A-LAW)

CC0 (USA): Yes
Determines the Pulse Code Modulation (PCM) encoding standard used by the
system to digitize voice signals for digital trunks and PRI trunks.
• A-LAW method is in common use in Europe, Middle East, Africa, Asia,
Australasia, South America, and many countries in other continents.
• M_LAW method (-Law, pronounced M-YOO Law, sometimes spelled
Mu-Law) is the standard used by common carriers in North America.
 Neither method has any particular advantage over the other.
Changing this parameter requires a hardware change to the MCB Office, MSBipx,
HDC, 4GC or 32GC card as well.
For further details, refer to Section 8 in the relevant Coral Installation Manual.
When the 4IAA or iCMC card is installed, the card definition must be identical to
the definition here (see the 4IAA or iCMC manual).
FLEXAIR/SIP_ Tick/Silence
SEARCH_TONE [5]
Define a search tone to be sounded for callers to a FlexAir handset, P-Series,
T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and third-party SIP
terminals.
The Tick Tone, when set, can indicate to the caller that the Coral system is
currently trying to locate the user. A ringback or busy tone is given only after the
station is located or timeout period has expired.
Enter T for a Tick tone.
Enter S for Silence (no tone).
System Features - Tones SFE,8 [0,0,4,1,8]

6-51
System Features - Diagnostics ç SFE,9 [0,0,4,1,9]
MINOR_RLY [0] Relay number (See [NPL,0,5,21]) or None

Minor Alarm Relay defines the relay dial number located on an MSBipx,
U-RMI/U-MR/RMI/MR Office, 8DRCF, 8DRCM, 8DRCM-2, ASU or RMI,
CDRS 200E, or in the IPx 500M Main Cage, that is activated when a minor alarm
condition occurs in the system (see General Numbering Plan, Chapter 5).
MAJOR_RLY [1] Relay number (See [NPL,0,5,21]) or None

Major Alarm Relay defines the relay dial number located on a
U-RMI/U-MR/RMI/MR Office, 8DRCF, 8DRCM, 8DRCM-2, ASU or RMI card
or in the IPx 500M or CDRS 200E that is activated when a major alarm condition
occurs in the system.
MAJOR_RLY may have the same dial number as a minor alarm relay. (See General
Numbering Plan, Chapter 5). If two alarm relays are needed, then two ASU, RMI,
8DRCF, 8DRCM, or 8DRCM-2 cards are required.
For IPx 500M and CDRS 200E Main Cage:
These systems include only one relay. For an additional relay, an ASU, RMI,
8DRCF, 8DRCM, or 8DRCM-2 card must be added to the system.
AUTO_GUARD [2] Yes/No

Determines whether the system automatically tests outgoing trunks for dial tone.
All trunks failing the test are blocked for outgoing calls while incoming calls are
allowed.
System Features - Diagnostics SFE,9 [0,0,4,1,9]
ENABLE_BLOCK_ Yes/No
ON_FAULT [3]
Determines whether the system automatically tests T1/E1 digital trunks (T1, 30T,
T1, 30T/x only
30T/E, 30T/M and all 30T/x) for RED alarms. When set to Yes, all trunk cards
failing the test are blocked for outgoing calls, but incoming calls are allowed. When
set to No, the test is not activated and all trunks are released for outgoing calls.
ON_FAULT [4]
Determines whether the system automatically tests ISDN trunks (4TBR,8TBR) for
4/8TBR only
alarms. When set to Yes, all BRI trunk cards failing the test are blocked for
outgoing calls, but incoming calls are allowed. When set to No, the test is not
activated and all trunks are released for outgoing calls.
6-52
ON_FAULT [5]
Determines whether the system automatically tests ISDN trunks (PRI-23, PRI-30
PRI23/30, IPG only
and IPG) for alarms. When set to Yes, all PRI and IPG trunk cards failing the test
are blocked for outgoing calls, but incoming calls are allowed. When set to No, the
test is not activated and all trunks are released for outgoing calls.
System Features - Diagnostics SFE,9 [0,0,4,1,9]
6-53
System Features - ISDN ç SFE,10 [0,0,4,1,10]
See System Features - ISDN on page 26-2.

System Features - ISDN SFE,10 [0,0,4,1,10]
6-54
System Features - Network ç SFE,11 [0,0,4,1,11]
See System Features - Network on page 28-3.
System Features - Network SFE,11 [0,0,4,1,11]
6-55
System Features - Wireless ç SFE,12 [0,0,4,1,12]
SAU Requirement FlexAIR SKK on page 3-22

The following parameters relate to systems that provide for CoralAIR and FlexAir
wireless telephones. Software Authorization Units (SAU) are required for these
parameters and the wireless telephones in order to operate.
SYSTEM ID# Any 12 digit number
 Notes:
• Not for FlexAir systems.
• Use the SAU device #
• For the Coral FlexiCom 5000 or Coral IPx 3000 systems with
Duplicated Common Control, use the Master Side SAU device #.
• For the Coral FlexiCom 6000/R or Coral IPx 4000/R systems with Dual
Common Control, use the Active Side SAU device #.
Note: A System ID# must be entered before continuing to change the values of the
related parameters.
Enter this system number to identify the system towards each of its wireless
handsets thereby preventing cross-signalling between unrelated systems and
handsets. This system ID number is automatically programmed into each handset
belonging to the particular Coral system.
This system ID number is defined and supplied by the manufacturer’s Service
Center.
Number of Clusters 0..8

System Features - Wireless SFE,12 [0,0,4,1,12]
Enter the number of SKK Clusters to be used in this Coral system. The number of
Clusters determines the number of SKK Master cards installed system-wide.
Each Master card can support 7 additional SKK slave cards physically linked
together.
 The Coral limits the use of SKK cards to a maximum of 32 8SKK and
16 16SKK cards per Coral system. See the FlexAir Installation Manual
for further RBS and Repeater limitations and details.
Enter 0 when no FlexAir system is used in this Coral.
6-56
Cluster #n - Link (Shelf/Slot) location or R for Remove (--, --)

Master Card (n = 1-8)
Shelf Options:
0: Coral FlexiCom 400 (with HDC controller);
0..15: Coral FlexiCom 5000, 6000
2..3: Coral IPx Office Expansion cages IPx 500X/800X

0..2: Coral IPx 500, 800
0..2: CDRS 200E
0..15: Coral IPx 3000, 4000
Slot Options:
1..16: Coral FlexiCom 400 (with HDC controller)
1..10: Coral IPx Office: IPx 500X expansion cages (Shelf #: 2, 3)

1..8: CDRS 200E main cages (Shelf #: 0)

1..10: CDRX 200E expansion cages (Shelf #: 1, 2)
1..8: Coral IPx 500M main cages (Shelf #: 0)
1..10: Coral IPx 500X expansion cages (Shelf #: 1, 2)
1..8: Coral IPx 3000M main cage (Shelf #: 0, 8)
1..12: Coral IPx 3000XE, 3000XO expansion cages (Shelf #: 1-7, 9-15)
1..12: Coral IPx 4000XE, 4000XO expansion cages (Shelf #: 0-15)
 This parameter is only displayed when the Number of Clusters, above is

greater than 0. n is determined by Number of Clusters.
If 2 clusters are required, then this parameter is displayed twice: once with n=1 and
the second time with n=2.
Enter the physical location of this SKK Master Card.
 The SKK physical Master card must be initiated before the other FlexAir
cards. Otherwise, the FlexAir system will not function properly.
6-57
Enter Activation Code Activation code supplied by manufacturer.

CoralAIR CC0 only
 The UTAM code is valid for 2 hours after receiving it.
For CoralAIR systems, enter the 18 digit alphanumeric UTAM code supplied by
the Service Center to activate wireless communication. If this UTAM code is not
entered, SKW cards already installed in the system cannot be activated, accepted
or initialized. This code also incorporates the number of SKW cards installed in the
system. Therefore, a new code must be obtained to activate more SKW cards.
! A system powered-down for more than 8 consecutive hours disables

any wireless activity.
A new UTAM code must be obtained to resume wireless service.
Entering a new code may cause one of the following error messages to appear:
INVALID UTAM CODE: Authorization (SAU#) mismatch error
OUTDATED UTAM CODE: Invalid time and/or date.
# of Base Stations 0..128

Authorized
For CoralAIR systems, defines the number of authorized Radio Base Stations
CoralAIR CC0 only
(RBS) for this system. Each SKW card supports 2 or 4 RBSs depending on the card
type (2/4SKW). The number of SKW cards cannot be increased without obtaining
a new UTAM code (see above parameter).
6-58
Card List ç CLIS [0,1,0]
Card List (CLIS) parameters identify the location, type, logical status and software
version of the various system plug-in cards. Card List is also used for assigning a
database (Card DB) to each card.
FROM/TO SHELF# All Shelves;

1..3: Coral IPx Office

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
0..2: CDRS 200E
Enter the required range of shelf numbers FROM the lowest shelf number TO the
highest shelf number.
FROM/TO SLOT# All Slots

2..11: Coral IPx Office main cage (Shelf #: 1)


Card List CLIS [0,1,0]

Enter the required range of slot numbers FROM the lowest slot number TO the
highest slot number.
SHELF# [0]  see FROM/TO SHELF# above

Identifies the shelf location of the indicated card for display.
SLOT# [1]  see FROM/TO SLOT# above

Identifies the slot location of the indicated card for display.
6-59
P_TYPE [2] Any shared service or peripheral card type. See Tables 6-5 and 6-6.
Present Card Type identifies the Peripheral or Shared Service card type which is
currently located in the designated slot.
 2DT cards (with firmware Version 60 or higher) are displayed with the
number of defined peers (circuits), as follows: 2DT/1 or 2DT/2.
If no card is currently located in the slot, the NO_CARD message appears.
I_TYPE [3] Any peripheral card type or NO_CARD. See Table 6-5 and 6-6.
Identifies the Peripheral card type initialized (first time card identified by system)
in the designated slot. Shared Service cards do not appear in this field since no
memory is reserved for them. This field can be updated even if the slot is currently
empty in order to assign the desired new peripheral card type.
• For a CNF card, to change the card mode from C3Way to Conference,
type CONF.
• To clear an empty slot, type NO_CARD.
• Enter NO_CARD to clear a slot equipped with a P_TYPE Resource
card, or to display a P_TYPE card when equipped with an I_TYPE.
! CAUTION: NO_CARD erases all the port dial numbers associated with
the slot. All these dial numbers are erased from the NPL, Trunk Groups,
Hunt Groups, Boss Groups, etc.
• Check Default Configuration (see page 8-95), before any Digital Card
(2DT, T1 and 30T/x) Installation.
• To assign a slot for a specific peripheral card, although no card is
installed (i.e. P_TYPE is set to No_Card, enter the card type in I_Type.
This is also known as 0/0 DATABASE PROGRAMMING, see below.
0/0 DATABASE The user can program the system without actually installing the peripheral cards.
PROGRAMMING This is a special engineering feature that allows programmers to prepare an entire
customer database at the manufacturer’s premises or at a central staging area,

thereby saving on-site testing time. The system is programmed through the CARD
LIST by entering the card name in the I_TYPE field while the P_TYPE for the card
is defined as NO_CARD. The following example shows how Card List is
displayed. Enter 24SLS in order to add the peripheral card even though there is no
24SLS physically installed.
CARD LIST
0,1
SHELF#- 0
SLOT#- 1
P_TYPE- NO_CARD
I_TYPE- NO_CARD 16SLS
6-60
CARD_DB# [4] 0 (1 for T1 and PRI-23 cards)

See Table 6-5 and 6-6
Identifies the card database (CDB) number assigned to the card type in the
designated slot. Each peripheral card type can be allotted one of the database tables
that are assigned to cards of that type. CDB numbers of different card types are
completely independent of one another, that is, CDB 0 for 8DID is independent of
CDB 0 for 4TEM.
 Notes:
• When CARD_DB# is set to N/A for this card type, "___" is displayed.
• Entering an incorrect CARD_DB# displays an ERROR message.
• Do not change the CARD_DB# of the PRI card.
• This parameter is irrelevant for 2DT cards (with firmware Version 60 or
higher). The CARD_DB# number assigned for 2DT card is defined per
each peer in another branch. See 2DT Card Database on page 8-102.
Table 6-2: Criteria for Installing Card_DB#*
P_TYPE [2] I_TYPE [3] CARD_DB# -

According To:
RESOURCE NO_CARD P_TYPE
PORT NO_CARD P_TYPE
RESOURCE PORT P_TYPE
NO_CARD PORT I_TYPE
PORT PORT I_TYPE
NO_CARD NO_CARD (see Notes 1 & 2, above)
*This table shows the relation between P_TYPE and I_TYPE, which define
the Card Database number.

6-61
VERSION [5] 
Displays the designated card software version.
SUBVERSION [6] 
Displays the designated card software subversion.
STATUS [7] 
Displays the current logical status of the designated slot. Primarily used by
maintenance personnel. Status messages are described in Table 6-3.
Table 6-3: Card Slot Status Messages
Message Description Recommendations

ACTIVE Initialization was successfully completed. None
ACTIVE/P Card is partially active because there are not Readjust SIZES to support
enough resources to support the other sub unsupported sub circuits for the
circuits on an 8DRCM, 8DRCM-2, 8DRCF, card.
8DTMF U-RMI/U-MR/RMI/MR Office cards, on Partial Active for the iDSP/URC2
the CDRS 200E or on the IPx 500M (MSBipx card is not critical.
Hardware Issue-0200X1000 or higher) or not all Readjust the parameter value
tone generators are being used on the only when needed.
iDSP/URC2 card (see N_CID_ON_IDSP_CARD [42] on
page 6-30).
For 2DT card only:

Two peers are configured as defined, but the Use the PLIS branch for
card is partially active as follows: checking and analyzing the
• Peer #0 is Activate problem. Refer to the messages
that may be displayed adjacent
• Peer #1 is Deactivated (its 4 LEDs are lit) to the port type, see Port List on
The Coral system rejects peer #1 because of page 6-67.
missing resources or authorization. Install an updated version of the
The following parameter has exceeded its SAU with the appropriate amount
Authorization Definition: of 2DT peers. Ask your dealer for
an authorized upgrade.
• 2DT WITH 2 CKTS on page 3-18
Readjust Sizes Definition on page
Any of the following trunk parameters 4-2, to support unsupported
has exceeded its Sizes Definition: peers or trunks for peer #1.
• Max Ports on page 4-4,
• Max Trunks on page 4-9
• E&M and DID on page 4-9 (for T1, 30T and
30T/M, requires 2DT firmware 61 - future
option Check Availability)
• PRI on page 4-10.
6-62

REPLACED P_TYPE [2] and I_TYPE [3] are not compatible. Install proper card or enter
NO_CARD in the I_TYPE [3]
option.
WAIT_DB Card has not received database, or has not Continue waiting
reported initialization.
For the UGW card only: • Enter the correct UGW MAC
• UGW MAC address is either incorrectly entered address
or not registered • Check that the network cables
• There is no network connection to Media and/or properly connected
Signalling • Fasten the MRC/MG/ULI/ULI-1
• MG/MRC module is not installed properly modules securely
• ULI/ULI-1 module is not installed properly • Check the network
• Network Configuration problem configuration
6-63

NO_RESOURCES Insufficient system memory to initialize card. Check the default SIZES
definitions (Route: SIZ).
For UGW card only: See Sizes Definition on page 4-2.
• More UGW cards are physically installed or
defined in I_TYPE [3], than the system can
handle
• Any of the following Endpoint port parameters
has exceeded its Sizes Definition:
SLT_IP on page 4-5,
KEYSETS_IP on page 4-7,
SIP_TERMINAL on page 4-8
LGS_IP on page 4-10,
NET_IP on page 4-11, and
SIP_TRUNK on page 4-11
• IP_MEDIA_CHANNELS on page 4-28, Sizes Tab
definition has been exceeded.
For 2DT card only:

Two peers (#0 and #1) are deactivated.
• The number of 2DT cards that are physically
installed or defined in I_TYPE [3] exceeded the
amount that can be handled by the Coral
system.
• Any of the following trunk parameters
has exceeded its Sizes Definition:
Max Ports on page 4-4,
Max Trunks on page 4-9,
E&M on page 4-9,
DID on page 4-9, and
PRI on page 4-10.
System diagnostic LED remaining lit.
All eight peer’s LEDs turn off.
6-64

CONFIG_ERR UGW Card only: Reallocate the Required Capacity
This error is displayed when inserting a UGW of media channels or endpoint
card when the slot I_TYPE [3] is defined as types in the UGW Current
NO_CARD and the UGW Default Configuration Configuration to reflect its
defines any one of the following: Physical Capacity.
• media channels while no MG module is See UGW: Current
installed on the UGW Configuration (page 29-13) branch,
route:UGWC,1 or IP,0,1 [9,0,1].
• more media channels than the card can
physically support
• an endpoint type that is not supported by the
UGW
• a total number of endpoint ports that exceed
the card’s physical capacity
IPx Office expansion cage only: Define the type of the expansion
This error is displayed when inserting a units connected to the IPx Office
peripheral or service card to an expansion cage system.
before the expansion units are properly See EXPANSION_TYPE Coral IPx
recognized by the IPx Office main processor. Office only (page 3-3) under
Installation branch, route:SYSGEN,0
[0,0,0,0].
After defining the expansion unit
in this parameter, the system
must be re-initialized (soft
re-boot) in order to initialize the
cards.
NOT_COMPAT Coral software version 14.5x or higher requires Install a UGW card- Version 2 or
UGW Card only UGW version 2 or higher higher and re initialize the card.
Coral software version 15 or higher requires Install a UGW card- Version 3 or

UGW version 3 or higher higher and re initialize the card.

FAULT HDLC problem Check HDLC wiring
6-65

UNAUTHORIZED SAU Requirement Install an updated version of the
The SAU ports are limited and therefore the SAU with the appropriate amount
card is not authorized for use in this system. of ports added. Ask your dealer
See Authorization Items on page 2-11 and for an authorized upgrade.
Feature Authorization beginning on page 3-5.
For the 2DT card only:

Insufficient SAU ports and therefore the 2DT
card and its two peers (#0 and #1) are not
authorized for use in the system.
System diagnostic LED remaining lit.
All eight peer’s LEDs turn off.
Any of the following parameters has exceeded
its Feature Authorization Definition:
• PORTS on page 3-7
• TRUNKS on page 3-9
• PRI on page 3-20
6-66
Port List ç PLIS [0,2,0]
The Port List (PLIS) parameters identify individual ports on a peripheral card.
The port parameters may be updated either by accessing their:
Physical location (Route: PLIS,0), see Port List - Physical Location below, or their
Dial numbers (Route: PLIS,1), see Port List - Dial Numbers below.
Access Port List by entering the physical location of the port (Shelf, Slot, CKT),
or the dial number assigned to the port. In either case the displayed information is
identical, except for the order of appearance.
When entering the Port List by its mnemonic (PLIS) or the root menu (0,2,0), the
PI prompts the user to enter a “0” for access by physical location or a “1” for access
by dial number.
In both Physical Location and Dial Number, direct access is possible by entering
either the parameter name or the field number enclosed in brackets ([ ]).
Details for the Port List are found on the following pages:
Port List - Physical Location......................................................................6-68
Port List - Dial Numbers............................................................................6-73
Port List PLIS [0,2,0]
6-67
Port List - Physical Location ç PLIS, 0 [0,2,0,0]
PHYSICAL Physical Location is used to display or modify port information by entering the
LOCATION port’s physical location in the system. The name of the port, and in the case of trunk
ports, the port database may be modified.
FROM/TO All Shelves;

SHELF# 0: Coral FlexiCom 400 (with HDC controller)
0..2: CDRS 200E

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
Enter the required range of shelf numbers; FROM the lowest shelf number TO the

2..11: Coral IPx Office: main cage (Shelf #: 1)

Port List - Physical Location PLIS, 0 [0,2,0,0]

Enter the required range of slot numbers; FROM the lowest slot number TO the
FROM/TO CKT# Any valid CKT number, All

Enter the required range of CKT numbers; FROM the lowest circuit number TO
the highest circuit number.
 Each 2DT card includes one or two peers (circuits), the number of trunks
(CKTs) listed per peer is as follows:
Peer#0, CKT 0-31, Peer#1, CKT 32-63
6-68
SHELF# [0] 
0: Coral FlexiCom 400 (with HDC controller)
0..2: CDRS 200E

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
Identifies the shelf, in which the port is located.
SLOT# [1] 



Identifies the card slot, in which the port is located.
CKT# [2] 
0-n, where n = number of ports on card –1
Identifies the circuit (CKT), on the card associated with the port.
For 2DT card only:
Each 2DT card includes one or two peers (circuits), the number of trunks (CKTs)
listed per peer is as follows:
• Peer#0, CKT 0-31
• Peer#1, CKT 32-63
6-69
TYPE [3] 
Any Shared Service or Peripheral card type (see Table 6-5 and Table 6-6)
Identifies the Shared Service (Resources) or Peripheral card type on which the port
is located (e.g., PRI23, PRI30, T1, 4TEM, 8T-C, 8DRCF).
For 2DT card only:
There are two messages that may be displayed adjacent to the 2DT card port type,
as follows:
SHELF/SLOT/CKT TYPE DIAL# PORT_DB# VERS SHORT & FULL NAMES
0 / 1 / 33 PRI23 NO_RSRC 7190 --- --- BLANK :BLANK
0 / 1 / 34 PRI23 UNAUTHR 7191 --- --- BLANK :BLANK
• NO_RSRC - indicates that there are not enough resources allocated for the
relevant port
• UNAUTHR - indicates that the second peer is not authorized or there are
insufficient SAU ports to support all trunks supplied by peer #1
>NOTE [4]  See Table Table 6-4 below

This parameter appears when the condition of a card within a slot is valid, but not
desirable. Such a state could lead to system problems. This state should be
corrected as soon as possible.
Table 6-4: Note Recommendations
P_Type I_Type Type >Note Port_DB Technical

by Recommendations
RESOURCE PORT P_TYPE I_TYPE I_TYPE A Resource card is operating in a
slot reserved for Port cards. If this is
to be a permanent condition, then
release the Port card through the
Card List option.
NO_CARD PORT I_TYPE NO_CARD I_TYPE 0/0 state: The Port card was
initialized in the past, but is not
installed. Install the card. If this is to
be a permanent condition, then
release the slot through the Card List
option.
PORT <>PORT I_TYPE NO_CARD I_TYPE A Port card was initialized for a
certain type of card, but a different
Port card is currently installed.
6-70
DIAL# [5] Any valid Numbering Plan dial #

Identifies the dial number assigned to the port.
PORT_DB# [6] 0, see Table 6-5;

1: T1 Trunks
 Notes:
• When PORT_DB# is not applicable for this port type, “-- --” is
displayed.
• Entering an incorrect PORT_DB# displays an ERROR message.
Identifies the port database number assigned to the port.
VERS [7] Any type of Version number

Identifies the version number of a keyset connected to the reported port.
6-71
NAME
SHORT (5) [8] Maximum of 5 ASCII characters; R (Remove for BLANK);
CO trunks: CO-01..CO-jj
DID trunks: DID00..DIDnn: where nn = number of DID trunks minus 1
All other port types: BLANK
Defines the port short name (up to 5 alphanumeric characters), which appears on
keysets equipped with a display of less than 80 characters that are engaged in a call
with this port. A port name defined as BLANK does not appear on the keyset
display and the keyset displays its dial number. See General Rules for Entering
Names on page 2-10.
FULL (16) [9] Maximum of 16 ASCII characters; R (Remove for BLANK);

Defines the port full name (up to 16 alphanumeric characters), which appears on
keysets equipped with a display of more than 80 characters that are engaged in a
call with this port. A port name defined as BLANK does not appear on the keyset
display and the keyset displays its dial number.
This name is used for the 1-SLT and 2-Keyset and Wireless entries of the system’s
Shared Directory (default feature code: #1994). Full Names defined as Blank are
not copied to the Shared Directory.
See General Rules for Entering Names on page 2-10.
6-72
Port List - Dial Numbers ç PLIS, 1 [0,2,0,1]
Port List parameters display or modify port information by first entering the port
type, and then the port dial number. The port name, and the port database may be
modified. After selecting Port List by dial number, the PI prompts for the type of
port to be listed. By entering a number corresponding to the port type, a specific
type of port may be selected, or all port types may be selected. Each port type is
identified by a number as shown below; all ports may be listed by entering the word
ALL.:
OPTION Description
0 - Trunk • NET_IP (Includes all Coral IP QSIG Network connections for this Coral
system via PUGW, UGW and UGW-E cards)
• LGS_IP (Includes all CO analog trunks, loop start and ground start,
connected via Coral Teleport/FXO MGCP gateways to the Coral IP network)
• SIP trunks (from a public service provider or behind FXO/BRI/PRI SIP
gateways) that are authorized for use in this Coral system
• Analog trunks: E&M (4TEM, 4TEM/S, 4TEM/P)
• Analog trunks: LS/GS, loop start and ground start
(4/8T, 4/8T-C, 4/8T-CID, 4TMR, 4TNI, 4TWL)
• Digital trunks: E1(30T, 30T/M, 2DT-30T, 2DT-30T/M, 30T/E)
• Digital trunks: T1(T1, 2DT-T1, UDT-T1)
• PRI (PRI-23, PRI-30, 2DT-PRI23, 2DT-PRI30, UDT-PRI23, IPG)
 In European systems, includes: GID and ALS70-DID

• BRI (4TBR, 4TBRP, 8TBR, 8TBRP)
1 - SLT • Magneto (8SM, 8SMipx cards)

• Type 500/2500 (8/16/24SLS, 4/8/20S Office, 8/16SLSipx, 4/8/16SH cards)
• Type 2500 (8/24SA, 4/8/16/24SA Office, 8/16/24SAipx cards)
Port List - Dial Numbers PLIS, 1 [0,2,0,1]

• SLT_IP (Includes all Type 500 or Type 2500 stations connected via Coral
Teleport/FXS MGCP gateways units to the Coral IP Network)
6-73
2 - keyset • Type 500 or Type 2500 stations (connected via Coral Teleport/FXS SIP
gateways units to the Coral IP Network)
• Coral FlexIP SoftPhones (FLIPS)
• P-Series
• Coral T207M, T208M, T207M/NP, T208M/BL
• Coral T207S, T208S, T207S/NP, T208S/BL
• Coral T322, T328
• FlexAir Wireless handsets
• Coral FlexSet-IP 280S
• Coral FlexSet 120, 120D, 120L, 120S, 121S
• Coral FlexSet 280, 280D, 280D-Z, 280D-HS, 280S, 281S
• Coral FlexAPDL
• iCMC (each iCMC card requires 24 entries for VM keyset ports)
• Coral Sentinel
• CPA, EKT, DKT, DST, GKT, VDK, APDL
• CoralAIR Wireless handsets
3 - DID • DID (8DID, 8DID/S, 4/8BID)
4 - Data Not Used (No Longer Available)

5 - Modem Ckt 3 - RMI
Ckt 26 - IPx Office, 8DRCM, 8DRCF
Ckt 26 - IPx 500M main Cage (Shelf #0, Slot #13) on the
motherboard (applicable for MSBipx Hardware
Issue-0220X1003 or lower)

 IPx 500M with MSBipx Hardware Issue-0230X1003 or

higher does not include a MODEM. The modem was
standard in MSBipx Hardware Issue-0220X1003 or
lower.
6 - Page Public Address/External Page Port, RLY1
Ckt 7 - RMI
Ckt 23 - IPx Office U-RMI/U-MR/RMI/MR (Shelf #1, Slot #6)
Ckt 23 - 8DRCM, 8DRCM-2, 8DRCF
Ckt 23 - IPx 500M on the motherboard (Shelf #0, Slot #13)
Ckt 23 - CDRS 200E on the motherboard (Shelf #0, Slot #13)
6-74
7 - Bell Central Bell/UNA Relay, RLY2

Ckt 8 - RMI
Ckt 24 - 8DRCM, 8DRCM-2, 8DRCF
8 - Relay Dial select/alarm relay, RLY3
Ckt 9 - RMI
Ckt 25 - 8DRCM-2, 8DRCM, 8DRCF
ALL Entire list
FROM/TO DIAL# Any valid Numbering Plan dial #, All Ranges

Enter the range of the dial number assigned to the required ports; FROM the lowest
port dial number TO the highest port dial number.
TYPE [0] 
Any Shared Service or Peripheral card type (see Table 6-5 and Table 6-6)
Identifies the Shared Service or Peripheral card type on which the port is located
(for example, PRI23, PRI30, 4TEM, 8T-C, 8DRCF, WLESS for Wireless).
For 2DT card only:

There are two messages that may be displayed adjacent to the 2DT card port type,
as follows:
SHELF/SLOT/CKT TYPE DIAL# PORT_DB# VERS SHORT & FULL NAMES
0 / 1 / 33 PRI23 NO_RSRC 7190 --- --- BLANK :BLANK
0 / 1 / 34 PRI23 UNAUTHR 7191 --- --- BLANK :BLANK
• NO_RSRC - indicates that there are not enough resources allocated for the
relevant port
• UNAUTHR - indicates that the second peer is not authorized or there are
insufficient SAU ports to support all trunks supplied by peer #1
>NOTE [1] 
This parameter appears when the condition of a card within a slot is valid, but not
desirable.This condition can cause system problems and should be corrected as
soon as possible. See Table 6-4 for more information concerning >NOTE.
6-75
SHELF [2] 
0..2: CDRS 200E
0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
Identifies the shelf on which the port is located.
SLOT [3] 


Identifies the Slot (card) in which the port is located.

CKT [4] 
0 to n, where n = number of ports on card minus 1
Identifies the circuit (CKT) on the card associated with the port.
For 2DT card only:
Each 2DT card includes one or two peers (circuits), the number of trunks (CKTs)
listed per peer is as follows:
• Peer#0, CKT 0-31
• Peer#1, CKT 32-63
6-76
PORT_DB# [5] 0, see Table 6-5;

(1: T1 trunks)
 Notes:
• When PORT_DB# is set to Not Applicable for this card type, “-- --” is
displayed.
• Entering an incorrect PORT_DB# displays an ERROR message.
Identifies the port database number assigned to the port.
VERS [6] Any type of Version number

Identifies the version number of a keyset connected to the reported port.
6-77
NAME [7]
SHORT Maximum of 5 ASCII characters; R (Remove for BLANK);
Defines the port short name (up to 5 alphanumeric characters), which appears on
keysets equipped with a display of less than 80 characters that place or receiver a
call to or from this port. A port name defined as BLANK does not appear on the
keyset display and the keyset displays its dial number.
FULL [8] Maximum of 16 ASCII characters; R (Remove for BLANK);

Defines the port full name (up to 16 alphanumeric characters), which appears on
keysets equipped with a display of 80 or more characters that place or receiver a
call to or from this port. A port name defined as BLANK does not appear on the
keyset display and the keyset displays its dial number.
This name is used for the 1-SLT and 2-Keyset and Wireless entries of the system’s
Shared Directory (default feature code: #1994). Full Names defined as Blank are
not copied to the Shared Directory.
6-78
Table 6-5: Summary of Ports and Card Types
Card P_Type I_Type Port Card Card

Port Name DB# DB# Slot# Comments
Range Range Range
2DT PRI-2DT 2DT N/A 0(PRI30) 2DT/2 requires Authorization.
(firmware Version 1(PRI23) See 2DT WITH 2 CKTS on page 3-18.
PRI-2DTipx 2DT/1
60 or higher)
or
The CARD_DB# number is defined per
PRI-2DT 2DT/2 8, 10
each peer in 2DT Card Database on
Office page 8-102.
2DT PRI-2DT 30TM 30TM 0-1 0-1

(firmware Version PRI-2DTipx
57 or lower) PRI-2DT 30T 30T 0-3 0-3
Office
PRI23 PRI23 N/A 1
PRI30 PRI30 N/A 0
T1 T1 0-3 0-3
4TWL 4TWL 4TWL 4TWL 0 0-3 New Zealand and India only.
Two Way Loop (DID & DOD)
4TWLipx
4TWLsl 1, 2, 3
ALS70 - trunk 4/8ALS 4/8ALS/S 4/8ALS 0-3 0-3 Holland: European systems only.
ALS70 (Abonnee Lijn Signalering
1970) Trunk circuit card - Netherlands
Standard
4/8ALS/M With Pulse Metering (/M)
CONF 8DRCM-2 8DRCM 8DRCM N/A 0 One Multi-party Conference “bridge”

(6-way) CKT #16
8DRCF 8DRCF 8DRCF N/A 0

8DRCM 8DRCM 8DRCM N/A 0
CNF CONF CONF N/A 0 Two Multi-party Conference “bridge”

(15-way)
DID - trunk 8DID 8DID 8DID N/A 0 Direct Inward Dialing (DID) circuit card
8DID/S 8DID/S
4/8BID 4/8BID 4/8BID 0-3 0 Belgium Inward Dialing (BID)

European systems only
4/8GID 4/8GID 4/8GID 0-3 0-3 German Inward Dialing (GID)

European systems only
DIGITAL - trunk $DPC N/A N/A N/A N/A Digital Protocol Converter
Converter
• See Table 6-6 for Shared Resources Service Cards.
6-79

Range Range Range
DIGITAL - trunk T1, T1 T1 0-3 0-3 24 Digital Trunk circuit card - North
T1 UDT (T1) American Standard
T1ipx, UDT, UDTipx and UDT Office - jumper

UDTipx (T1) set to T1
T1sl 1, 2, 3
UDT Office (T1) 8, 10
DIGITAL - trunk 30T 30T 30T 0-3 0-3 30 Digital Trunk circuit card - CEPT/E1
(E1) 30T European Standard carrying an 2048
30T Office 8, 10 Kbps signal that meets ITU-T
(30T or 30TM Rec.G.703
jumper
selection)
30Tipx
30Tsl 1, 2, 3
30T/M 30TM 30TM 0-1 0-1 30T/M variations:

(DDI/DDO) 30T/M-BZL, 30T/M-PL, 30T/M-ARG,
30T/M-CHI, etc.
30T/M 0 Port DB is not programmable.

(E&M
Continuous)
30T/E 30TE 30TE 0 0-1 European systems only.

(E&M Port DB is not programmable.
Continuous)
30T/E 0-1 European systems only.

(Non-DID/DDI
/DDO)
DVMS 4VS 4VS 4VS N/A N/A Card Discontinued
4VSN Card Discontinued

4VSN card with software V 50.xx -
field installed voice messages.
E&M (Analog 4TEMipx 4TEM 4TEM N/A 0-2 Four Trunk E&M (Ear and Mouth
trunk) Continuous 4TEM/S signaling) Tie-Line (2/4 wire
4TEMsl 1, 2, 3 inter-exchange) circuit card
4TEM
4TEM/S
E&M (Analog 4TEM/P 4TEMP 4TEMP 0-3 0-3 Four Trunk E&M Pulsed Tie-Line (2/4
trunk) Pulsed wire inter-exchange) circuit card
6-80

Range Range Range
IP Gateway IPx Office CUGW UGW N/A N/A Shelf# 6 Universal Gateway - Supports:
Slot# 5 • KEYSETS_IP (FlexSet-IP 280S,
T207M, T208M, T207M/NP,
UGW UGW
T208M/BL)
UGWipx
• SOFTSET/FLIPS
UGW-E (FlexIP SoftPhone)
UGW-Eipx • Sentinel
PUGW PUGW • SLT_IP (Coral Teleport/FXS)
PUGWipx • LGS_IP (Coral Teleport/FXO)
• NET_IP (Coral IP QSIG Network)
• Media Channels (MRC for PUGW
and MCB, MG for UGW and UGW-E)
• P-Series
• T207S, T208S, T207S/NP,
T208S/BL
• T322, T328
• Third-party SIP terminals
• SIP_Trunk
NOTE: T207M, T208M, T207M/NP,
T208M/BL require Coral Version 15.5
or higher, and one of the following:
• UGW Version 3 or higher
• PUGW/CUGW Version 7 or higher
NOTE: P-Series require Coral Version
16.01.12 or higher, and PUGW/CUGW
Version 11 or higher
NOTE: T207S, T208S, T207S/NP,

T208S/BL require Coral Version 15.5
or higher, and PUGW/CUGW Version
7 or higher
NOTE: SeaBeam requires Coral
Version 15.84 or higher, and
PUGW/CUGW Version 7 or higher
NOTE: T322, T328 require Coral
Version 16 or higher, and
PUGW/CUGW Version 10.6 or higher
IPG PRI30 PRI30 N/A 1 Do not change CARD_DB#: ETSI
6-81

Range Range Range
ISDN - BRI trunk 4/8TBR 4/8TBR 4/8TBR 0-3 0-3 Trunk Basic Rate Interface (BRI)
circuit card (ISDN) 2B+D.
4/8TBRipx Supports both S and T reference
points. This means the card will
4/8TBRsl 1, 2, 3
support connections to CO or Terminal
equipment. Supports QSIG Links to
4TBR Office 8, 10
other PBXs
8TBRP 8TBR/P Supplies External Power (P)
8TBRPipx
8TBRPsl 1, 2, 3
ISDN PRI trunk PRI-23, PRI23 PRI23 N/A 1 Do not change CARD_DB#:
UDT (PRI-23) AT&T,4ESS
PRI-23ipx,
UDTipx (PRI) UDT, UDTipx and UDT Office - jumper
set to PRI
PRI-23sl, 1, 2, 3
UDT Office 8, 10
(PRI)
PRI-30 PRI30 PRI30 N/A 0 Do not change CARD_DB#:

ETSI
PRI-30 Office, 8, 10
PRI-30ipx
PRI-30sl 1, 2, 3
LS - trunk 4/8T-Cipx FJ 4T-C 4T-C 0-5 0-3 4 Loop Start trunk ports.
Includes 4 Power Fail circuits.
4T Office 4T-C 10
4T Office and 4T-CID 10 Supports Caller ID

4CID Office
8T Office 8T-C 8T-C 2, 4 8 Loop Start trunk ports.

8T Office and 8T-CID 2, 4 Supports Caller ID

8CID
6-82

Range Range Range
LS/GS - trunk 4/8T-C 4/8T-C 4/8T-C 0-5 0-3 4/8 Loop/Ground Start trunk ports.
4/8T-Cipx
4/8T-Csl 1, 2, 3
4/8T-CID 4/8T-CID 4/8 Loop/Ground Start trunk ports.

4/8T-CIDipx Supports Caller ID.
4/8T-CIDsl 1, 2, 3
4TMR 4TMR 4TMR 4 Loop/Ground Start trunk ports.

4TMR/S 4TMR/S Includes Pulse Metering (50Hz, 12kHz
-12/16/PF/G or 16kHz).
PF = Includes 4 Power Fail circuits.
4TMR-PF-Gipx,
4TMR-PFipx,
4TMR/S-12/16-
PF-Gipx,
4TMR-PFsl, 1, 2, 3
4TMR-PFsl-G
4TMRsl 1, 2, 3
4TNI 4T 4T Russian market only.

Trunk with Numbering Identification.
4/8Tsl PF 4/8T 4/8T 1, 2, 3 Cards Discontinued

4/8 Loop/Ground Start trunk ports.
4/8Tsl 1, 2, 3 PF = Includes 4 Power Fail circuits.
4T PF 4T
8T 8T

8T PF
8T/S 8T/S
8T/S PF
Station (Analog) 8SM 8SM 8SM N/A 0-2 Military Magneto Telephone circuit
Magneto - station card
8SM/S 8SM/S
8SMipx 8SM/S
Station (Analog) 4/8/16S 4/8/16S 4/8/16 S N/A 0-3 Cards Discontinued

SLT
4/8/16S/S 4/8/16S/S
Station (Analog) 4/8/16 SH 4/8/16SH 4/8/16 SH

SLT - with
Message Lamp 4/8/16 SH/S 4/8/16
SH/S
Station (Analog) 4/8 SH/S-LL 4/8 SH/S

SLT (LL) with
Message Lamp 16 SH/S-LL 16 SH/S Long Loop (LL) with MW lamp support
6-83

Range Range Range
Station Analog 4/8/16/24SA 4/8/16/24 4/8/16/24 N/A 0-3
2, 4 4, 8, 16, or 24 port 2-wire SLT
(SA) SLT Office SLS-C SLS
Programmed to (S) 8/24SA 8/24 8/24

SLS-C SLS
8/16/24SAipx 8/16/24 8/16/24 IPx 500 Supports SLT-Caller ID feature.

SLS-C SLS and
CDRS
200E
Only
Station Analog 4/8/16/24SA 4/8/16/24 4/8/16/24 N/A 0-3 4, 8, or 20 port 2-wire SLT and
2, 4
(SA) SLT - with Office SLS/H-C SLS message waiting (MSW) lamp.
Message Lamp
8/24SA 8/24 8/24
Programmed to SLS/H-C SLS
(SH)
8/16/24SAipx 8/16/24 8/16/24 IPx 500 Card version 4.xx and higher supports
SLS/H-C SLS and SLT-Caller ID feature.
CDRS
200E
Only
Station Analog 4/8/20S Office 4/8/20 4/8/20 N/A 0-3

2, 4 4, 8, or 20 port 2-wire SLT
(SLS) SLT SLS-C SLS
Jumper set to (S) 8/16/24 SLS 8/16/24 8/16/24 Card version 3.xx and lower
SLS SLS
8/16/24 Card version 4.xx and higher supports

SLS-C SLT-Caller ID feature.
8/16SLSipx 8/16 8/16 IPx 500 Card version 4.xx and higher supports
SLS-C SLS and SLT-Caller ID feature.
CDRS
200E
Only
6-84

Range Range Range
Station Analog 4/8/20S Office 4/8/20 4/8/20 N/A 0-3 4, 8, or 20 port 2-wire SLT and
2, 4
(SLS) SLT - with SLS/H-C SLS message waiting (MSW) lamp.
Message Lamp
8/16/24 SLS 8/16/24 8/16/24 Card version 3.xx and lower
Jumper set to (SH) SLS/H SLS
8/16/24 8/16/24 Card version 4.xx and higher supports

SLS/H-C SLS SLT-Caller ID feature.
8/16SLSipx 8/16 8/16 IPx 500 Card version 4.xx and higher supports
SLS/H-C SLS and SLT-Caller ID feature.
CDRS
200E
Only
Station (Analog) 8//24 SA 8/24 8/16/24 N/A 0-3 Supports SLT-Caller ID feature and
SLT - with SLS/H-C SLS Message Lamp
Message Lamp
(Coral Version
9.5x - 15.xx)
Station (Digital) 2/8SD 2/8SD 2/8SD N/A N/A VDK

Cards
Discontinued 8SVD 8SVD 8SVD N/A N/A Voice and Data (VDM, 2W-DIM)
8/16 SKD 8/16 SKD 8/16 SKD N/A N/A DKT/DST/GKT
8/16/24 SDT 8/16/24 8/16/24 N/A N/A DKT/DST/GKT

8/16SDTsl SDT SDT Requires Version 5 or higher DKTs &
DSTs

8/16/24 8/16/24 8/16/24 N/A N/A DKT/DST/GKT/ FlexSet
SDT/G SFT SDT
4/8SK 4/8SK 4/8SK N/A N/A EKT
4/8SK/S 4/8SK/S N/A N/A
Station (Digital) 8/16/24SFT 8/16/24 8/16/24 FlexSet/DKT/DST/GKT/APDL

N/A N/A 2, 4
Office SFT SDT
8/16/24SFT 8/16/24 8/16/24 N/A N/A

SFT SDT
8/16SFTipx 8/16 SFT 8/16 SDT N/A N/A IPx 500

and
CDRS
200E
Only
6-85

Range Range Range
4S Office (S) 4SLS-C 4SLS-C 4 port 2-wire SLT
Station N/A 0-3 2, 4
4S Office 4SLS/H-C 4SLS-C
(Analog+Digital) And message waiting (MSW) lamp
(SH)
4S+8Fx
8Fx Office 8SFT 8SDT N/A N/A 3, 5 Supports FlexSet/DKT/DST/GKT/APDL

(SH)
4S+16Fx

(SH)
8S+8Fx

(SH)
8S+16Fx
Voicemail iCMC iCMC 16iCMC/16 24SDT N/A N/A 24 KEYSET1 entries are allocated in
8iCMC/8 SIzes for each iCMC, however, only
16iCMC CKTs 0 to 15, 17 &18 are used.
CKTs 16, & 19-23 are not used and
8iCMC can be removed from the system
database.
iCMCipx
iCMC-200 1, 2, 3
Voicemail iVMF iVMFipx 8SDT N/A N/A
Voicemail SFC IPC/SFC 24SDT N/A N/A
IPCipx/SFC 8SDT
IPC/SFC 24SDT 2, 4
Office
Voicemail uCMC IPC/uCMC uCMC/24 24SDT N/A N/A
IPCipx/uCMC uCMC/8 8SDT
IPC/uCMC uCMC/24 24SDT 2, 4

Office
Voicemail WiCMC IPC/WiCMC 24SDT N/A N/A
IPC/WiCMC 24SDT 2, 4
Office
6-86

Range Range Range
Wireless handset 2/4SKW 2/4SKW 2/4SKW N/A N/A PLIS shows WLESS as station type:
CoralAIR Card Discontinued
2/4SKWsl 1, 2, 3
Wireless handset 8/16SKK 8/16SKK 8/16SKK N/A N/A 8/16 RBS (Radio Base Stations)
FlexAir /M04 or M=master card
8SKKipx S04 S=slave card
04=four channels per RBS
8SKKsl 1, 2, 3
Table 6-6: Shared Resources Service Cards - Summary
Card Type Port DB # Card DB#

Port Range Range Comments
Tone Detector 8DRCM-2, N/A 0 8 Dial Tone Detectors: CKT # 8-15

8DRCM,
8DRCF
8DTD N/A 0 8 Dial Tone Detectors: Card Discontinued
DTMF - Receivers 8DRCM-2, N/A N/A DTMF 8 receivers: CKT # 0-7

8DRCF
8DRCM N/A N/A DTMF 8 receivers: CKT # 0-7

8DTMF N/A N/A DTMF 8 receivers: CKT # 0-7
8DTR/S N/A N/A DTMF 8 receivers: Card Discontinued
8DTR N/A N/A DTMF 8 receivers: Card Discontinued
4DTR N/A N/A DTMF 4 receivers: Card Discontinued
MRC (version N/A N/A DTMF receivers (Coral version 15 or higher)

7 or higher) (for MRC on PUGW, PUGWipx or IPx Office)
see RESOURCES on page 4-25.
C3WAY 8DRCM-2, N/A 0 Six 3-way conference/Silent Monitors (2-Way):

8DRCF CKT # 17-22
8DRCM N/A 0
CNF N/A 0 Eight 3-way conference/Silent Monitors (2-way)
• See Table 6-7 for Coral IPx 500 and CDRS 200E Shared Resources Service Cards.
• See Table 6-8 for Coral IPx Office Shared Resources Service Cards.
6-87
Table 6-6: Shared Resources Service Cards - Summary
Card Type Port DB # Card DB#

Port Range Range Comments
MFC - Receivers 16MFR N/A 0 MFC-R2 16 receivers

(for 8DID, 4/8BID, 30T, 30T/E, 30T/M and 30T/x)
MRC (version N/A N/A MFC-R2 receivers (Coral version 15 or higher)

7 or higher) (for MRC on PUGW, PUGWipx or IPx Office)
see RESOURCES on page 4-25.
4IAA - card 8SD N/A N/A 4-Integrated Automated Attendants with software
version 40.xx: Card Discontinued
iDSP iDSP N/A 0 PLIS shows iDSP/xxx where xxx is the number of
FSK tone generators defined in N_CID_ON_IDSP_
CARD [42] on page 6-30.
MODEM 8DRCM or N/A 0 CKT # 26

8DRCF
RMI N/A 0 CKT # 3: Card Discontinued
PAGE - RLY1 8DRCM-2, N/A 0 Public Address: CKT# 23

8DRCF
8DRCM N/A 0 Public Address: CKT# 23
RMI/ASU N/A 0 Public Address: CKT# 7:

Card Discontinued
Relay - RLY3 8DRCM-2, N/A 0 Auxiliary or Alarm Rely:

8DRCF CKT# 25
8DRCM N/A 0
RMI/ASU N/A 0 Auxiliary or Alarm Rely:

CKT# 9: Card Discontinued
UNA/Bell - RLY2 8DRCM-2, N/A 0 Bell/UNA/Night Answer:

8DRCF CKT# 24
8DRCM N/A 0
RMI/ASU N/A 0 Bell/UNA/Night Answer

CKT# 8: Card Discontinued
• See Table 6-7 for Coral IPx 500 and CDRS 200E Shared Resources Service Cards.
• See Table 6-8 for Coral IPx Office Shared Resources Service Cards.
6-88
Table 6-7: Coral IPx 500 and CDRS 200E: Shared Resources Service Ports
Port DB # Card DB#

Port Card Type Range Range Comments
8DRCF* unit on motherboard (Shelf 0, Slot #13)

DTD 8DRCF N/A 0 CKTs 8-15
DTMF 8DRCF N/A 0 CKTs 0-7
MODEM 8DRCF N/A 0 CKT=26
PAGE - RLY 1 8DRCF N/A 0 CKT=23 Public Address
UNA/BELL - RLY2 8DRCF N/A 0 CKT=24 Bell/UNA Night Answer
RELAY - RLY 3 8DRCF N/A 0 CKT=25 Auxiliary or Alarm Relay
C3WAY 8DRCF N/A 0 CKTs 17-22: Six 3-Way
CONF 8DRCF N/A 0 CKT=16: One Multi-Party Conference

“Meet Me bridge”- 6-way
RMI-F unit on motherboard (Shelf 0, Slot #13)

MSBipx Hardware Issue-0200X1000 or higher
MODEM RMI-F N/A N/A CKT=26
PAGE - RLY 1 RMI-F N/A N/A CKT=23 Public Address
UNA/BELL - RLY2 RMI-F N/A N/A CKT=24 Bell/UNA Night Answer
RELAY - RLY 3 RMI-F N/A N/A CKT=25 Auxiliary or Alarm Relay
Music1/Music 2 RMI-F N/A
SHARED SERVICE CARDS (RESOURCES):

URC2 unit on motherboard (Shelf 0, Slot #14)-
MSBipx Hardware Issue-0200X1000 or higher.

DTR URC2 N/A N/A Ckt # 0 to 23†
†
CONF (Meet Me) URC2 N/A N/A Ckt # 48 to 53
Each “Meet-Me bridge” circuit is a
multi-party conf with a max of 14 mem
†
C3WAY URC2 N/A N/A Ckt # 56 to 79
†
iDSP (CID) URC2 N/A N/A Ckt # 80 to 111
†
DTD URC2 N/A N/A Ckt # 112 to 143
* 8DRCF, RMI-F and URC2 units must be installed for these ports to be defined in Card List.
† The circuit definitions depend on the maximum number of ports defined for each URC resource in CDB, 11,1. For
example, if only 5 DTMF receivers are defined in the card’s current configuration, then only Circuits 0 to 4 are
available for the DTMF receivers.
6-89
Table 6-8: Coral IPx Office: Shared Resources Service Cards
Card Port Card Card

Port Card Name Type DB# DB# Slot# Comments
Range Range Range
U-RMI/U-MR/RMI/MR Office cards

PAGE - RLY 1 U-RMI Office RMI-F/MR N/A N/A 6 CKT=23 Public Address
U-MR Office
UNA/BELL - RLY2 RMI Office RMI-F/MR N/A N/A 6 CKT=24 Bell/UNA Night Answer
MR Office
RELAY - RLY 3 RMI-F/MR N/A N/A 6 CKT=25 Auxiliary or Alarm Relay
Music1/Music 2 RMI-F/MR 6 N/A
MODEM U-RMI Office RMI-F N/A N/A 6 CKT=26

RMI Office
U-RMI/U-MR Office cards

DTR U-RMI Office URC2 N/A N/A 7 Ckt # 0 to 23*
U-MR Office
DTR URC4 N/A N/A 7 Ckt # 0 to 47
Not Used in this version
CONF (Meet Me) URC2 N/A N/A 7 Ckt # 48 to 53*

Each “Meet-Me bridge” circuit is a
multi-party conf with a max of 14 mem
Spare URC2 N/A N/A 7 Ckt # 54 to 55*
C3WAY URC2 N/A N/A 7 Ckt # 56 to 79*
iDSP (CID) URC2 N/A N/A 7 Ckt # 80 to 111*
DTD URC2 N/A N/A 7 Ckt # 112 to 143*
* The circuit definitions depend on the maximum number of ports defined for each URC resource in CDB, 11,1. For example,
if only 5 DTMF receivers are defined in the card’s current configuration, then only Circuits 0 to 4 are available for the DTMF
receivers.
6-90
Digital Port Bus List ç DLIS [0,1,1]
The Digital Port List parameters identify individual digital ports on a Digital
Terminal or Telephone Peripheral card:
8/16/24SFT, 8/16SFTipx, 8/16/24SFT Office, 4/8S+8/16Fx Office, 8/16SFTsl,
8F8Ssl, 8/16/24SDT, 8/16SKD and 8SVD. To access the Digital Port List, enter the
physical location of the port (Shelf, Slot, CKT).
The cards contain eight, sixteen or twenty-four identical ports (CKTs) respectively,
which provide a two-wire interface called UP0. The ports must be connected to
external devices. Up to eight external devices can be connected to each digital port
while the limit is 32 devices per card. Devices that can be connected and are
available with this Coral Software version include FlexSet, GKT, DKT, DST and
DPEM sets and CPA, APDL terminals.
For more information about the physical installation, refer to the Coral Terminal
Equipment - Installation Manual.
The eight external devices relate to the port as if connected to a logical
identification number. The ID numbers range from 0 to 7 in each port.
ISDN convention stipulates that instead of having only one piece of equipment
plugged into the ISDN phone line (point-to-point communication), the multi-drop
feature allows connection of up to eight devices to each single ISDN line.
FROM/TO SHELF# All available shelves

0: Coral FlexiCom 400 (with HDC controller)
0..2: CDRS 200E
Digital Port Bus List DLIS [0,1,1]

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
Enter the required range of shelf numbers, FROM the lowest shelf number TO the
6-91

2..11: Coral IPx Office main and expansion cages

1..10: CDRX 200E expansion cages
1..10: Coral IPx 500X expansion cages
FROM/TO CKT# Any valid CKT number, All

Enter the required range of CKT numbers; FROM the lowest circuit number TO
the highest circuit number.
ID.  0..7
Identifies the logical location of the indicated P_Type and I_Type.
Identifies the logical connection to the port. Every external device is logically
connected to internal Bus UP0. A maximum of eight devices can be connected to
one physical port where each device is associated with a different logical location.
The logical locations are identified by numbers 0 to 7.
P_TYPE  See Table 6-9

Identifies the external terminal device type which is currently installed and located
in the designated ID.
6-92
I_TYPE Any external device type (see Table 6-9) or R (Remove) for --(No device)
Identifies the external device type initialized (first time, the external device
identified by the system - but not necessarily installed) in the designated ID.
This field can be updated, even if the slot or port is currently empty, in order to
assign the desired new device type.

• To clear an empty ID., type R (Remove).
• To assign an ID for a specific external device, although no device is
physically installed, enter the device type according to the table listed
below.
! Caution:
Any entry (R or changing the current ID) erases the database associated
with the CKT. The dial number is erased from the Trunk Groups, Hunt
Groups, Boss Groups, etc. The associated speed call libraries are
erased, etc.
Table 6-9 describes the various options available for connecting external devices
to a digital port. A maximum of eight external devices can be connected per port
and defines the related ID# for the external device.
• The main operating device is always defined as ID# 0.
• The first DPEM is always defined as ID# 4.
• The second DPEM is always defined as ID# 5.
• The third DPEM is always defined as ID# 6.
• A single DPEM connected cannot be defined as ID# 0, 1, 2, 3 or 7.
6-93
Table 6-9: DLIS P_Type and I_Type
ID# P_type* I_type Devices
0 DKT1 DKT1 DKT 1xxx
DKT1N DKT1N FlexSet 120 / 120D
DKT1N* DKT1N FlexSet 120 / 120D – Issue 10 or higher
DKT2 DKT2 DKT 2xxx, iCMC, CPA
DKT2N DKT2N FlexSet 280 / 280D / 280D-Z
DKT2N* DKT2N FlexSet 280 / 280D – Issue 12 or higher
DKT3S DKT3S FlexSet 120S
DKT3S* DKT3S FlexSet 121S
DKT5S DKT5S FlexSet 280S
DKT5S* DKT5S FlexSet 281S
DST2 DST2 2W-DIM, DST
DSTN DSTN FlexSet 120L
GKT GKT FlexSet 80S / 80P
4 DPEM1 DPEM1 1st DPEM (for DKT2xxx),

1st FlexSet 40B (for FlexSet 280x)
5 DPEM2 DPEM2 2nd DPEM (for DKT2xxx),

2nd FlexSet 40B (for FlexSet 280x)
6 DPEM3 DPEM3 3rd DPEM (for DKT2xxx),

3rd FlexSet 40B (for FlexSet 280x)
7 APA APA • FlexSet 280S with APA or PEX+APA

• FlexSet APDL with APA or PEX+APA
• FlexSet 80S
• FlexSet 80P
• GKT 4320, GKT 4321
• DKT 2322
• DKT APDL
7 APA* APA APDL/S

* The * indicates that the phone is based on a SCOUT unit.
6-94
Tone Plan ç TON [0,0,4,2]
The system Tone Plan includes 18 internal tones. These tones are programmed
according to type, number of segments, Basic Tones and Basic Tone duration. Each
tone can be defined as a combination of any of the basic tones.
TONE # 1..23 (excluding: 8, 11, 14, 15)

Defaults: See Tables 6-10 and 6-11
Identifies the name of the tone. The list of default tones is shown in Table 6-10.
Special Tones for different countries are listed in Table 6-11. The various tone
functions are described in Table 6-12.
NAME 
See Tables 6-10 and 6-11
Displays the Tone Name. This name cannot be changed and is for display only.
TYPE 1 (Continuous), 2 (Single Burst), 3 (Multi-Burst)

See Tables 6-10 and 6-11
Defines the tone as continuous, single burst, or multi-burst.
When the tone is defined as Continuous (i.e. TYPE=1), only 1TN (see page 6-95)
is used (2TN to 6TN are irrelevant because the tone is continuous).
# SEG 0 (when TYPE, above, is set at 1)

1..6 (when TYPE, above, is set to 2 or 3)
Defines the number of different segments for each single burst or multi-burst tone.
A segment is defined by a Basic Tone frequency plus its tone duration. Only the
required segments are displayed in Update Mode. For example, defining this
Tone Plan TON [0,0,4,2]

parameter to three, causes the PI to display the next two parameters (TN and MS)
three times, once for each segment.
TN 0..7, see Table 6-13

(1TN: Tone Segment
A maximum of 6 different segments can be defined, therefore, up to 6 different TN
1-
values can be defined, depending on what was defined in TYPE and # SEG.
6TN: Tone Segment 6)
Each TN defines which Basic Tone frequency is being used for the current
segment. There are eight Basic Tones (see Table 6-13) from which to choose. For
example, enter 4 to choose Basic Tone 4 for the current segment. This defines the
frequency for the Tone segment.
The Tone duration, however, can be changed by using the next parameter, MS-TIME.
6-95
MS - Time 0..5100 ms
See Tables 6-10 and 6-11 for default tone durations
and Table 6-13 for the Basic Tone (Tone 0 to Tone 7) Frequency
Defines the duration of each Basic Tone segment in milliseconds.
SEND_TO_CARD? Yes/No
Sends the new tone configuration to the MSBsl/MSBipx/HDC/32GC/4GC Control
cards immediately.
When No is entered, routine diagnostics periodically resend the tone plan to the
card database.
6-96
Table 6-10: Default Tone_Plan
Tone NAME TYPE* #SEG 1TN TIME** 2TN TIME 3TN TIME 4TN TIME 5TN TIME 6TN TIME
#
1 Busy 3 2 3 500 0 500 0 0 0 0 0 0 0 0
2 Dial 1 0 1 0 0 0 0 0 0 0 0 0 0 0
3 Distinct. 1 0 4 0 0 0 0 0 0 0 0 0 0 0
4 Reorder 3 2 3 240 0 240 0 0 0 0 0 0 0 0
5 Ringback 3 2 2 1000 0 3000 0 0 0 0 0 0 0 0
6 Silence 1 0 0 0 0 0 0 0 0 0 0 0 0 0
7 Tick 3 2 5 60 0 1000 0 0 0 0 0 0 0 0
8 PL 3 6 60 100 0 100 60 100 0 100 60 100 0 5100

CWAIT
9 Confirm 3 2 1 100 0 100 0 0 0 0 0 0 0 0
10 BRK_ 1 0 5 0 0 0 0 0 0 0 0 0 0 0
In/Out
11 PL Conf 2 2 61 2000 0 0 0 0 0 0 0 0 0 0
12 V.P Conf 3 2 3 100 5 100 0 0 0 0 0 0 0 0
13 Z.P Warn 3 2 6 300 3 100 0 0 0 0 0 0 0 0
16 LCR_ 2 6 0 120 5 80 0 120 5 80 0 120 5 80

expens
17 LCR_ 2 4 0 120 5 80 0 120 5 80 0 0 0 0

cheap
18 Call Wait 3 4 5 600 0 5000 0 5000 0 5000 0 0 0 0
19 DISA dial 1 0 1 0 0 0 0 0 0 0 0 0 0 0
20 CCR 3 3 61 200 0 200 60 200 0 0 0 0 0 0
21 WP 2 5 7 100 0 100 7 100 0 100 7 200 0 0

22 2nd 3 6 3 100 0 100 3 100 0 100 3 600 0 3000
R.back
23 Speaker 3 6 0 120 5 80 0 120 5 80 0 120 5 80
24 PL 3 2 58 1640 0 360 0 0 0 0 0 0 0 0
R.BACK
25 PL 1 1 59 0 0 0 0 0 0 0 0 0 0 0
Preempt
*TYPE Defintions:
Type 1: Only the first basic tone (1TN) is used for a continuous tone.
TIME is determined by the system according to the actual use of the tone.
Type 2: The relevant basic tones are sounded in turn, only once.
Type 3: The relevant basic tones are sounded cyclically, i.e.one after the other (1TN to 6TN and then beginning
again with 1TN: (multi-burst).
**TIME: milliseconds
 See Table 6-11 for different tone values by country.
6-97
Table 6-11: Default Tone Plan-Special Tones by Country
TONE_PLAN
NO. NAME TYPE #SEG 1TN TIME 2TN TIME 3TN TIME 4TN TIME 5TN TIME 6TN TIME
CC0:
5 Ringback 3 2 2 2000 0 4000 0 0 0 0 0 0 0 0
8 PL CWAIT 3 6 60 100 0 100 60 100 0 100 60 100 0 5100
11 PL Conf 2 2 61 2000 0 0 0 0 0 0 0 0 0 0
24 PL R.BACK TBD
25 PL Preempt TBD
CC2:
1 Busy 3 2 3 260 0 260 0 0 0 0 0 0 0 0
4 Reorder 3 2 3 260 0 260 0 0 0 0 0 0 0 0
5 Ringback 3 2 2 1000 0 4000 0 0 0 0 0 0 0 0
10 Break-In/Out 2 4 5 500 0 180 5 180 0 180 0 0 0 0
18 Call Wait 3 5 5 200 0 600 5 200 0 5000 0 5000 0 0
Eu1:
9 Confirm 3 2 1 40 0 40 0 0 0 0 0 0 0 0
18 Call Wait 3 6 5 200 0 2000 0 2000 0 2000 0 2000 0 2000
17 DISA dial 1 0 7 0 0 0 0 0 0 0 0 0 0 0
Eu2:
2 Dial 3 6 1 180 0 180 1 180 0 180 1 180 0 1000
3 Distinct. 3 6 4 180 0 180 4 180 0 180 4 180 0 1000
Eu9:
2 Dial 1 1 1 0 0 0 0 0 0 0 0 0 0 0
3 Distinct. 1 1 4 0 0 0 0 0 0 0 0 0 0 0
4 Reorder 3 2 1 200 0 200 0 0 0 0 0 0 0 0
5 Ringback 3 2 2 1000 0 4000 0 0 0 0 0 0 0 0
6 Silence 1 1 0 0 0 0 0 0 0 0 0 0 0 0
10 Break-In/Out 3 4 5 200 0 200 5 200 0 1400 0 0 0 0
18 Call Wait 3 2 5 200 0 4900 0 0 0 0 0 0 0 0
19 DISA Dial 1 1 1 0 0 0 0 0 0 0 0 0 0 0
6-98
Table 6-12: Tone Functions
Tone# Tone Name Tone Function

1 Busy Informs the calling party that the called destination is busy.
2 Dial Informs a caller that dialing can take place. The tone is
 Dial tone may be replaced by a Message or Music

activated when offhook or by hands free dialing.
when feature authorization set to Yes (MUSIC DIALTONE

on page 3-25). The parameter DIAL_TONE MESSAGE
SOURCE [78] (page 7-23) in COS,0 is used to define the
music source to be used to be used instead of a Dial
Tone. The music source may also be a taped recording.
3 Distinctive Dial Informs the station user that certain features are in use at
(DDT) the station, for example: Call Forward All, Do Not Disturb,
Messages, Secondary COS. DDT is also used between
patterns of digits when dialing certain types of features, such
as Account Code or Routing Access.
This tone is also sounded during a call after a Hookflash
signal.
4 Reorder Informs a calling party that the call was intercepted because
of either a misdial or an illegal attempt to access a facility
that was blocked by COS definition.
5 Ringback Informs the calling party that the designated station is
ringing.
7 Tick Informs a station user that the system is waiting for
additional digits to be dialed.
8 MLPP Call Wait This tone is heard by the called party to indicate that an
CC0 Only MLPP call with equal precedence is currently waiting to be
answered. This tone is heard only when the called station is
set as a Multi-Appearance station.
9 Confirmation Informs a station user that a feature was successfully

activated.
10 Break-In/Out Informs two parties engaged in a conversation that a third
party is breaking in or is leaving the call. Also informs
parties engaged in a conference call that additional user
joins or leaves the call.
11 PL CONF MLPP Stop Conference Tone.
CC0 Only This tone is used to indicate to members of a 3-way call
when one of the members is preempted by a higher priority
caller.
12 and 13 Voice/Zone Informs station users that Voice/Zone Paging is in progress.
17 and 16 Routing Informs a calling station about the outgoing type of route
Expense/Cheap cost selected by the System Routing.
6-99
Table 6-12: Tone Functions(Continued)
Tone# Tone Name Tone Function

18 Called Waiting Informs an SLT station user engaged in a call that another
(SLT call is waiting for the user. Also known as Multi Appearance
Muted Ring) Call Muted Ring. The presence of the waiting call tone or
muted ring indicates that another call is waiting. It is
received when engaged in a call when help is requested or
on an Operator’s phone during Group Calls when
Permission to Speak is requested.
19 DISA Dial Informs a remote access party that dialing can take place.
20 Collect Call Instructs the operator to reject the collect call request.
Reject (CCR)
21 Whisper Page Informs one party during a conversation that a Whisper
(WP) Page is about to be received from a third party. The second
party does not hear the tone.
22 Second When a caller waits for a port currently engaged in a call,
Ringback he/she will hear a 2nd ringback tone. This tone notifies the
(2nd R.back) caller that the station is currently busy. When the called
party disconnects, the waiting call rings next at the
destination.
23 Speaker Receive Speaker Status Tone. This tone indicates whether
the second party (called or calling) has the speaker turned
on. This tone is heard immediately when the call is
answered.
24 PL R.BACK MLPP Ringback Tone. This tone is heard by the calling
CC0 Only party who is waiting to be answered by the called party
currently engaged in an MLPP call with equal precedence.
25 PL Preempt MLPP Preemption Tone. This tone is heard by the called
CC0 Only party to indicate that an MLPP call will immediately preempt
the call.
6-100
Table 6-13: Basic Tones (in Hz)-By Country Codes
Country Basic Tone #

Code
0 1 2 3 4 5 6 7 60 61
CC0*, 0 Hz 350/440 440/480 480/620 480 440 1000 400 0 0

CC4
CC1,CC7, 0 Hz 350/440 440 440 440 440 1000 400 780/540 660/540
CC9, CC10
Eu3, Eu5
CC2, CC3, 0 Hz 420 420 420 420 420 1000 420 780/540 660/540
CC5
CC6 0 Hz 450 450 450 450 450 1000 450 780/540 660/540
CC8 0 Hz 420/370 420/370 400 420 400 1000 420 780/540 660/540
Eu0 0 Hz 420 420 420 520 420 1000 1170 0 0
Eu1 0 Hz 420 420 420 420 420 1000 1170 0 0
Eu2, Eu3 0 Hz 420 420 420 530 420 1000 400 0 0
Eu6, Eu7 0 Hz 420 400/450 420 420 420 1000 420 780/540 660/540
Eu8 0 Hz 420 420 420 420 420 1000 1170 0 0
Eu9 0 Hz 350/420 420 420 420 420 1000 400 0 0
In CC0 systems these tones are coded using M-Law. All other systems use A-Law (see M_LAW [4]
on page 6-51).
6-101
Ringers ç RPS [0,0,4,3]
Coral IPx 800, 3000, 4000 and FlexiCom 5000, 6000 Systems Only
The parameters for this branch are configured differently for the two different types
of systems:
• See IPx 800, 3000 or 4000 Configuration to define the PS Ringers for IPx
systems.
• See FlexiCom 5000 or 6000 Configuration to define the PS Ringers for FlexiCom
systems.
Ringers RPS [0,0,4,3]
6-102
IPx 800, 3000 or 4000 Configuration

This branch is relevant only for Coral IPx 800, 3000, 4000 systems where the
PS19 DC-D specifically supports SLT cards on two shelves.
This branch is not relevant for Coral IPx systems using the PS19 DC and PS19 AC,
in which case, the Coral defaults are applicable.
The PS19 DC-D may be installed on every shelf or every two shelves. Based on its
hardware configuration, it supplies power to the shelves in the following manners:
System Power Peripheral Shelf Hardware Use this branch to

Mode Configuration distribute
MAX_RING [0]* among:
Normal Power One PS19 DC or PS19 AC supports each shelf.

every system shelf.
NO hard wire connection is possible
between two shelves in this mode.
Double Power One PS19 DC-D is installed on each shelf.

each shelf.
AND
NO H719 DC-D hard wire
connection exists between the
shelves.
Economical One PS19 DC-D is installed in one both shelves.

shelf supporting two shelves by
using an H719 DC-D hard wire
connection between the two
adjacent shelves.
Redundant One PS19 DC-D is installed on both shelves.

each shelf
AND
an H719 DC-D connects two
adjacent shelves, thereby enabling

redundancy in case one PS fails.
* MAX_RING [0] (page 6-19) defines the maximum number of SLTs that can
simultaneously ring per one or two Shelves depending on the hardware configuration.
6-103
FROM/ 0..2 (IPx 800); 15 (IPx 3000, 4000);

TO 0..15
SHELF#
Enter the required shelf number range to display or update, that carry SLS and SA
cards, FROM the lowest shelf number TO the highest shelf number.
RINGER # 0..2 (IPx 800);

0..15 (IPx 3000, 4000);
Default: See Table 6-14 for IPx systems
Defines the shelf number in which there is a PS unit that supplies power to the
current SHELF# (i.e. the one chosen in the parameter FROM/ TO SHELF# above).
Different shelves defined with the same RINGER # cause MAX_RING [0] to be
distributed among all the shelves that share the same RINGER # definition.
! • During installation, inspect the physical setup of the Power

Supply Units and update the Ringer PS table accordingly.
Otherwise, SLTs on some shelves may not be able to ring or
some calls may not processed.
• Do not define the same PS Ringer Shelf # for more than two
shelves.
Table 6-14: Defaults for Coral IPx Systems
Shelf # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ringer P. S. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
located on
Shelf #
By default, MAX_RING [0] (page 6-19) is distributed per shelf, thereby supporting
the Normal Power and Double Power mode.
 Notes:
• Do not change these defaults for the Normal and Double Power modes.
• For Redundancy or Economical power, these defaults must be

modified to reflect the actual hardware setup, thereby ensuring
maximum and efficient use of the Ringer Power Supplies (see Figure
6-1).
Use the following sketches to determine how to define Ringer # for each shelf in a
Coral IPx system based on the system hardware setup.
6-104
Figure 6-1. IPx

Ringer PS
Configurations
PS19 Shelf# X
Double Power:
Max_Ring
DC-D
Shelf #: X Y
PS Ringer: X Y (Coral Default)
PS19 Shelf# Y The PS Ringer defaults for IPx systems is
Max_Ring
DC-D set for Double Power systems.
PS19 Shelf# X
DC-D
Max
_R i n
Economical:
Shelf #: X Y
Shelf# Y g PS Ringer: X X
Shelf# X
Max
_Ri n
Economical:
Shelf #: X Y
PS19
DC-D
Shelf# Y g PS Ringer: Y Y

Redundant:
PS19 Shelf #: X Y
Shelf# X
Max
DC-D PS Ringer: Y Y
_ Ri n or
PS19
DC-D
Shelf# Y g Shelf #: X
PS Ringer: X
Y
X
! Caution! For Economical and Redundant Systems:

The PS Ringer Coral default should be changed to avoid a PS overload
which may prevent some SLTs from ringing or prevent dialing.
6-105
FlexiCom 5000 or 6000 Configuration

The Coral FlexiCom 5000 or 6000 uses RPS Power Supplies to supply ring to the
SLS cards that support SLTs in their systems. The configurations are made per
Peripheral Shelf Unit (even numbered shelf and its odd numbered shelf).
The Peripheral Shelf Units include a built-in hard wire connection between the
even and its odd shelf. There is no option for hard wire connections between even
numbered peripheral shelves or between odd numbered shelves.
The RPS units can be installed in any of the following manners:
System Power Peripheral Shelf UNIT: Use this branch to dis-

Mode Hardware Configuration tribute
MAX_RING [0]* among:
Economical One RPS is installed in the even both shelves of the

shelf and supports the even and Peripheral Shelf Unit.
odd shelves concurrently.
Redundant One RPS is installed on the even both shelves of the

shelf and one on the odd shelf. Peripheral Shelf Unit.
Even Shelves One RPS is installed per even each EVEN shelf.
Only shelf AND no odd shelves exist in
the system.
* MAX_RING [0] (page 6-19) defines the maximum number of SLTs that can
simultaneously ring per one or two Shelves depending on the hardware configuration.
FROM/ 0..15
TO 0..15
SHELF#
Enter the required shelf number range to display or update, that carry SLS cards,
FROM the lowest shelf number TO the highest shelf number.
RINGER # 0..15;
Default: See Table 6-15 for FlexiCom systems
Defines the shelf number in which there is an RPS unit that supplies power to the
current SHELF# (i.e. the one chosen in the parameter FROM/ TO SHELF# above).
Different shelves defined with the same RINGER # cause MAX_RING [0] to be
distributed among all the shelves that share the same RINGER # definition.
! During installation, inspect the physical setup of the Power Supply

Units and update the Ringer PS table accordingly.
Otherwise, SLTs on some shelves may not be able to ring or some calls
may not processed.
! Do not define the same PS Ringer Shelf # for more than two shelves.
6-106
Table 6-15: Defaults for FlexiCom Systems
Shelf # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ringer P. 0 0 0 0 4 4 4 4 8 8 8 8 12 12 12 12
S. located
on Shelf #
By Coral default, MAX_RING [0] (page 6-19) is distributed over every 4 shelves.
Therefore if MAX_RING [0] is set to 20, only 20 SLTs of all the SLTs installed on
shelves 0 to 3 may ring simultaneously.
 These defaults must be modified to reflect the actual hardware setup

thereby ensuring maximum and efficient use of the Ringer Power Supplies.
For example: If an RPS on shelf# 0 supports shelves# 0 and #1, while an RPS
on shelf #2 supports shelves #2 and #3, the table should be updated as follows:
Shelf # 0 1 2 3
Ringer P. S. (located on Shelf #) 0 0 2 2
See Figure 6-2 for examples showing how to define the Ringer PS for the different
FlexiCom Power Modes.
6-107
Figure 6-2. FlexiCom

Ringer PS
Configurations
RPS Shelf# 0
Max
_Ri n
Economical:
Shelf #: 0 1 2 3
Shelf# 1 g PS Ringer: 0 0 2 2
Shelf# 0
Max
_Ri n
Economical:
Shelf #: 0 1 2 3
RPS Shelf# 1 g PS Ringer: 1 1 3 3
Redundant:
Max
RPS Shelf #: 0 1 2 3
Shelf# 0
PS Ringer: 1 1 3 3
_ Ri n or
RPS Shelf# 1
g Shelf #: 0
PS Ringer: 0
1
0
2
2
3
2
Max_Ring
RPS Shelf# 0
Even Shelves Only:
Shelf #: 0 1 2 3
PS Ringer: 0 NA 2 NA
RPS Shelf# 2 NA: Since there is no odd shelf, then the
Max_Ring
definition for the odd shelves are irrelevant.
6-108
7 Class of Service
This chapter describes all Class of Service (COS) parameters. The COS types are
listed below along with the page number where their descriptions appear:
Station and Trunk COS ................................................................................7-2

Attendant Class of Service .........................................................................7-33
Tenant Class of Service ..............................................................................7-44
Routing Class of Service ............................................................................15-9
Class of Service is assigned throughout the system and determines the features that
stations, trunks, attendant console, tenant and Routing Access can access.
All the system ports are normally assigned their Primary (main) Class of Service.
Stations, however, may be assigned a different Classof Service (secondary) during
night service or after COS Change has implemented a feature.
Class of Service also applies to trunks. They are assigned a single class of service
which remains in effect for both Night or Day modes. Trunks cannot be defined as
an attendant.
The number of available COS tables is defined in SIZES (see page 4-16).
 Notes:
• COS #1 default is initialized for stations defined as attendant.
• COS #10 default is initialized for trunks.
• COS #11 default is initialized for DID trunks.
• COS #0, and COS #2-9 default is initialized for stations.
7-1
Class of Service PI Reference Manual
Station and Trunk COS ç COS,0 [0,0,2,0]
Establishes the basic Class of Service table for all stations and trunks.
 The Hunt Group COS is always determined by the COS defined for the
first member of the Group.
FROM/TO COS# 0 to maximum number defined in Sizes, see COS on page 4-16
All
Enter the required COS numbers FROM the lowest TO the highest COS number.
NAME (16) [1] Any ASCII characters: max, 16 characters; R (Remove for BLANK)
Defines the COS name (up to 16 alphanumeric characters). Use the COS name to
indicate what it restricts, for example, “MANAGERS Only”, or “NO_INTL_
CALLS”.
A name defined as BLANK displays only the COS number. Use “_” (underscore)
for space. See General Rules for Entering Names on page 2-10.
Station and Trunk COS COS,0 [0,0,2,0]
7-2
PI Reference Manual Class of Service
TOLL_BAR The following three options, DIGIT_ANLS [2], NO_MATCH (P/B) [3], and PTRN_
TABLE (0-7) [4], apply to stations and incoming trunks when making external calls:
DIGIT_ANLS [2] P (Pass), B (Block), C (Check)
 Applies only to stations and incoming trunks when making external calls.
Digit Analysis determines the toll barrier digits condition as follows:
Pass: All outgoing calls are released without toll barrier checks.
Block: All outgoing calls are blocked.
Check: Check the information of the toll barrier digits based on the elements in the
pattern table as determined by the next two parameters: NO_MATCH (P/B) [3] &
PTRN_TABLE (0-7) [4].
NO_MATCH (P/B) [3] P (Pass), B (Block)
 Applies only to stations and incoming trunks when making external calls.
Defines when the default toll barrier condition passes or blocks digits.
This option is relevant when the dialed number does not match one of the ranges
defined in Toll Barriers (see Chapter 13).
 Relevant only when Check (C) is entered in the DIGIT_ANLS [2] above.
Pass: All digits will be passed except those Blocked in toll barrier elements.
Block: All digits will be blocked except those Passed in toll barrier elements.
PTRN_TABLE (0-7) [4] 0..7
 Applies only to stations and incoming trunks when making external calls

Choose a pattern table (0-7) for this COS. The pattern tables are defined in Toll
Barriers. See SELECT PTRNS on page 13-2.
 Relevant only when Check (C) is entered for the DIGIT_ANLS parameter.
7-3
TK_GRPS/ROUTING Any valid trunk group(s) or Routing Access code(s) or ( ) None;

ACCESS [5] First 4 trunk groups and the first Routing Access number
Identifies the Trunk Groups and Routing Access which may be used for outgoing
calls when this COS is defined for the Station or Trunk.
Enter information under the display line.
• To add a single number or more, enter: (A, number 1, number 2,...)
• To remove a single number or more, enter: (R, number 1, number 2,...)
• To remove all numbers, enter: ( )
F.A.C_TK_ Any valid trunk group(s) and/or Routing Access code(s) or ( ) None
GRPS/ROUTING
Forced Account Code Trunk Groups and Routing Access allows dialing defined
ACCESS
Trunk Groups and Routing Access only after dialing an Account Code. Trunk
[6] Group and Routing Access numbers are entered between parenthesis, with each
group separated by commas or spaces. ACCT [58] (page 7-18) must be set to Yes.
• To add number(s), enter: (A, number, number 2,...)
• To remove number(s), enter: (R, number, number 2,...)
F.A.C_DIAL_SERVICE Any valid Dial Service number or ( ) None

[7]
Defines whether or not the port user is required to enter an Account Code when
using the dial service/s specified in this entry. ACCT [58] on page 7-18 must be
defined as Yes.
To enable emergency (E911) dialing without entering an Account Code, define a
Routing Access with several Dial Services to reach the PSTN, where one Dial
Service is for emergency calls and does not require an Account Code. The other
trunk groups in the Dial Services can be defined to require an Account Code by
defining them in the above parameter F.A.C_TK_GRPS/ROUTING ACCESS [6].
This procedure enables avoiding the necessity to define required Account Codes
for Routing Access’.
 This parameter is enabled only when DIRECT_DIALING_ON_DIAL_SERVICE

[62] (page 7-19) is set to Yes.
Example:
 9 is the Routing Access
• 7020, 7021 and 7022 are the Dial Services used to access the PSTN, that
require an Account Code.
7-4
• 7029 is a Dial Service for E911 calls.

• 81, 82, 83, and 89 are the respective trunk groups.
 Therefore, 81, 82, 83 should be defined in the above F.A.C_TK_GRPS/ROUTING

ACCESS [6] parameter. Trunk Group 89 should not be included.
• This parameter F.A.C_DIAL_SERVICE, should include the 7020, 7021 and
7022 Dial Services.
• The 7029 dial service should not be included in this parameter.
ROOM_STATUS [8] SAU Requirement

All possibilities between 0 and 15, inclusive, combination of any digits, Any
number between 0 and 15 or ( ) for None
Defaults: COS 0-9: (0..15)
COS 10,12-249: (2)
COS 11: ( ) None
Defines which Room Status or User Canned messages (see Chapter16 - Room
Status) are accessible by the station. Room Status and User Canned Messages are
mutually exclusive such that the system can only support one of these features.
Each feature requires Authorization, however, the system defaults to the Room
Status Feature. To change this default, USER_CANNED_MESSAGES [21] (page 6-25)
must be set to Yes in the in the System Features - Station Options branch (SFE, 2).

If no Authorization exists when dialing the Room Status/Message code, the
message ILLEGAL appears on the station user’s keyset.
Room Status/Canned Message numbers are entered between parentheses, with the
numbers separated by a comma or spaces. Enter information under the display line.
Corresponding default feature dial numbers: 7026 to 7041
CALL DURATION Any valid trunk group(s) and/or Routing Access code(s) or ( ) None
LIMIT:
Ensures a maximum duration for outgoing calls initiated by trunks, trunk groups
TK_GRPS/ROUTING
and routing access’ listed here. The call duration is quantified in CALL_DURATION_
ACCESS [9] LIMIT [25] (page 6-6) in the Feature Timers branch (FE.T).
To remove all numbers, enter: ( )
7-5
CALL_DURATION_ Any valid Dial Service number or ( ) for None

LIMIT:
Ensures a maximum duration for outgoing calls initiated by the dial services listed
DIAL_SERVICE [10]
here. The call duration is quantified in CALL_DURATION_LIMIT [25] (page 6-6) in the
Feature Timers branch (FE.T).Enter information under the display line.
1=BROKER, 0..6 (see Table 7-1 below)

2=CONSULT,
4: COS 0-9,11
4 = 3-WAY, 5=ALL,
2: COS 10, 12-249
6=Continuous Conf
[11] Each station/trunk/port user can be set-up to use one of the following three-party
feature capabilities. Each of these features is activated by Xfer/hookswitch button
during an established 2-way call. This parameter defines which multi-party feature
is available by the station or E&M trunk.
Table 7-1: BROKER, CONSULT, 3-WAY, ALL, Continuous Conf
1 Broker Service Allows the user to put a call on hold and then
converse privately with a third party, while
switching between the two calls. The party not in
conversation is put on hold and cannot hear any
other conversation. Xfer/hookswitch can be used
to switch between parties any number of times,
but 3-way conversation is not possible.
2 Consultation Call Allows the user to converse with a third party

while the original (second) party is put on hold.
After consultation is complete the two original
parties (the user and the second party) are
reconnected, while the third party is released.
• iVMFipx card ports must have this
parameter set to 2, Consultation.
• To enable live record via Voicemail
systems, (IPC/IPC2/SFC or
IPC/uCMC) card ports must have this
parameter set to 2, Consultation.
3 N/A Not Applicable
4 Three-Way A third participant can be added to the existing
Conference 2-way call.
7-6
5 All This feature allows the user to change a

(Combination of conversation from broker to consultation to
Consultation/ three-way conference by Xfer/hookflashing
Broker/ Three-way while in conversation.
Conference Call)
• The first Xfer/hookflashing allows the user
to converse privately with a third party.
• The second Xfer/hookflashing allows the
user to speak privately with the original
party, while the third party is put on hold.
• The third Xfer/hookflashing places the user
in a three-way conversation with all parties.
6 Continuous Allows the user to continue adding participants
Conference to an established 3-way call, effectively turning
the call into a multi-party conference call (up to
6 or 15 members, depending on system
hardware) where anyone of the original 3-way
members can add additional conference
participants and have other multi-party
conference features enabled.
Keyset userscan activate the Continuous
Conference feature by using a programmed
button (default feature code #1306), which
enables defining this parameter with another
Xfer/hookflashing definition (1=BROKER,
2=CONSULT, 4=3-WAY, or 5=ALL).
 When choosing 6, Continuous

Conference, it is advisable to reserve
conference circuits for regular conference
calls. See CIRCUIT_RESERVED
[2] (page 23-5) in PDB,3.
7-7
BREAK_IN [12] Yes/No;

No: COS 0, 2-249
Yes: COS 1
Defines whether or not a station user, or incoming E&M trunk, is allowed to break-
in to an existing call on a non-Data Secure line. (A warning tone is sounded before
break-in.)
Corresponding default feature dial number: #124 or hookflash-3.
SILENT_MON [13] Yes/No

SAU Requirement SPLIT MONITOR (page 3-23).
Silent Monitoring defines whether or not a station user, or E&M trunk, is allowed
to monitor any connected system port, station, trunk, conversation in any state
without either monitored party receiving audio or visual warning.
Corresponding default feature dial number:
• #1448 Silent Monitor (Split 1-Way)
When SPLIT MONITOR (page 3-23) is authorized with SAU, then this parameter also
enables the COS authorized user to monitor only one side of the conversation at a
time.
For 2-way monitoring, an 8DRCM-2, 8DRCM, 8DRCF, CNF card for most
systems or U-RMI/U-MR card for IPx Office systems must be installed. When the
CNF card is installed, it must be defined as C3WAY in Card List (see Chapter 6).
SILENT_MON_DENY Yes (Protected) /No (Not Protected);

[14]
Yes: COS 0-9
No: COS 10-249

Silent Monitoring Deny defines whether or not a station user or E&M trunk, is
protected against other users from monitoring its calls by using either the Silent
Monitor (2-Way) or Split Silent Monitor (1-Way) feature.
DND/DATA SEC. Yes/No

OVERRIDE [17]
No: COS 0, 2-249
Yes: COS 1
Do Not Disturb and Data Secure Line Override defines whether or not a station
user, or E&M trunk, is allowed to break into an existing data secured call, and
override a Do Not Disturb condition at the called station.
7-8
CF_BUSY INT/EXT Yes/No

[18]
Yes: COS 0-9;
No: COS 10-249
Call Forward If Station Is Busy defines whether or not a station user can forward
all the station’s calls to another destination determined by the station user when
user station is busy.
Corresponding default feature dial number: #140 and #17701.
CF_ALL INT/EXT [19] Yes/No

Yes: COS 0-9;
No: COS 10-249
Call Forward All Calls defines whether or not a station user can forward all his
calls to another destination determined by the station user.
CF_BSY+NA INT/EXT Yes/No

[20]
Yes: COS 0-9;
No: COS 10-249
Call Forward If Busy Or Not Answered defines whether or not a station user can
forward his calls to another destination determined by the station user when the
user station is busy or unanswered.
Corresponding default feature dial number: #147 or #2, and #17705.
CF_NO_ANS INT/EXT Yes/No

[21]
Yes: COS 0-9;
No: COS 10-249
Call Forward If No Answer defines whether or not a station user can forward his
calls to another destination determined by the station user if the user station is not
answered.
TIMED_FWD INT/EXT Yes/No

[22]
Defines whether or not a station user can forward his calls to another destination
according to system-wide periods.
7-9
FOLLOW_ME INT/EXT Yes/No

[23]
Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can collect all calls from another station.
CF_UNDEF [24] Yes/No

Yes: COS 0-9;
No: COS 10-249
Call Forward Undefined defines whether or not a station user can define a call
forward destination for all calls to the user’s destination when the user’s phone is
in an Undefined state: i.e., SLTs connected to extracted line card, unplugged
Keysets, IP ports with Network or UGW faults.
For IP terminals, set the CF_UNDEF parameter to Yes and program a non-IP
destination, like Voicemail, as the forwarding destination. If the IP link goes down
or the bandwidth limit is exceeded a call routed to the IP terminal will get rerouted
to the CF_UNDEF destination instead of being disconnected.
Corresponding default feature dial number: #17717.
DONT_DIST [25] Yes/No

Yes: COS 0-9;
No: COS 10-249
Do Not Disturb defines whether or not a station user can activate the Do Not
Disturb (block incoming calls) feature. DONT_DIST changes to
ATTENDED/UNATTENDED when the user is defined as an Attendant.

DND_WP [26] Yes/No

Do Not Disturb-Whisper Page defines whether or not a station user can activate the
DND_WP feature thus preventing other users from “whispering” to their station
while engaged in conversation.
 This parameter is irrelevant and can be set to NO, for:

FlexAir handsets (T-402, T-404, T-408, T-304) and
IP stations (T207M, T208M, T207M/NP, T208M/BL, T207S, T208S,
T207S/NP, T208S/BL, P-Series, T322, T328, SeaBeam, and
FlexSet-IP 280S).
7-10
DIAL_LOCK [27] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can lock the telephone in order to prevent
unauthorized station use. Both the keypad and the programmable keys are locked,
thus preventing outgoing calls. Incoming calls are still allowed. The telephone can
be unlocked by entering the dial lock feature code and telephone passcode.
COS_CHANG [28] Yes/No

Yes: COS 0-9;
No: COS 10-249
Change Class Of Service defines whether or not a station user can change his
station COS between primary/secondary classes.
REMINDER [29] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can use the REMINDER feature (station rings
at the user-selected time).
WAKEUP [30] YYes/No

Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not a station user can use the WAKEUP feature (station rings
at the user-selected time). If no Authorization exists when dialing, the message
ILLEGAL appears on the station user’s keyset.
7-11
MESSAGE [31] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11
Defines whether or not a station user, or E&M trunk, may leave a message
indication at a destination station, where the destination is a keyset or an SLT
equipped with a message waiting lamp.
CAMP_ON [32] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11
Defines whether or not a station user can camp on (queue to) to a busy station,
non-answering station and busy outside line. After dialing the camp-on feature
code (while hearing the busy, or no-answer tone), the call is disconnected. The
calling station rings when the called station is no longer busy or the non-answering
station becomes active.
This feature is also known as “Call Back”.
CAMP_OFFHK [33] Yes/No

Yes: COS 0-9;
No: COS 10-249
Camp-On While Offhook defines whether or not an offhook station user, or
incoming E&M trunk, may camp-on to a busy station by hookflashing (or dialing
XFER) followed by dialing 8 and remaining offhook.
When a dialed station is busy, the calling party may send a call-waiting tone to
indicate that his/her call is waiting. The calling party then hears a ringback tone
(see ORIGINATOR_CALL_WAITING_TONE [2] on page 6-50 to see which ringback
tone the caller hears).
This feature is also known as “Call Offer”.
Corresponding default feature dial number: hookflash (or Transfer)-8.
7-12
EXEC_PRIV [34] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11;
No: CC1: COS 0-9
Executive Privilege defines whether or not a station user, or trunk may temporarily
transfer all special features from his/her station to be temporarily used at another
station. (Once the station goes on-hook, the temporary change is canceled.)
Freedom Feature (IRSS)
To enable Freedom calls from non-Coral destinations which do not possess a Caller
ID (ANI) number, a special DID dial number used to activate the Executive
Privilege must be defined in the NPL for use with those IRSS destinations (the
special dial number must be defined with the Executive Privilege Feature Code
Index (80), so that when the user calls this number from an off-site destination, the
Executive Privilege feature is automatically activated to enable the IRSS call. The
Coral station must have its COS defined with Executive Privilege set to Yes.
PASS_CHNG [35] Yes/No

Yes: COS 0-9;
No: COS 10-249
Passcode Change defines whether or not a station user can change the 4 digit
station passcode.
UNA_PICKUP [36] Yes/No

Yes: COS 0-9;
No: COS 10-249
Bell / UNA Pickup defines whether or not a station user can pick up a central bell
or Universal Night Answer (UNA) call by dialing the Night Answer code.
Corresponding default feature dial number: #192 or 78.
DIRECTED_PICKUP Yes/No
[37]
Yes: COS 0-10 and 12-249;
No: COS 11
Defines whether or not a station user, or trunk, can answer any ringing station by
first dialing the directed Pickup code and then dialing the ringing station’s number.
7-13
GROUP_PICKUP [38] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11
Defines whether or not a station user can answer any ringing station in his own user
group, by dialing the Group Pickup code.
PARK [39] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can park an established call and then retrieve
the call from any system station.
Corresponding default feature dial number: #183 or #7 or 79.
HOLD [40] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can place a call on hold.
Corresponding default feature dial number: #171 or #4.
PRIVACY [41] Yes/No

Yes: COS 0-9;
No: COS 10-249
Boss Group Privacy defines whether or not a station user can activate the Boss
Group Privacy feature to prohibit another group member from joining an
in-progress call.
EXCL_HOLD [42] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11
Exclusive Hold defines whether or not a station user can activate the Boss Group
Exclusive Hold in order to prohibit a call that has been placed on hold by the user
station, from being retrieved by another group member.
7-14
V_PAGE [43] Yes/No

Yes: COS 0-10 and 12-249;
No: COS 11
Defines whether or not a station user can voice page a keyset.
WHISPER_PAGE [44] Yes/No

Defines whether or not a station user can use the Whisper page feature. When set
to Y, the station can page one party of an ongoing conversation. The party on the
other end of the ongoing conversation does not hear the whisper page.
• This feature is not available and can be set to NO, for:
P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam,
and third-party SIP terminals.
RELAY [45] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can switch a relay (RLY3) ON or OFF in order
to activate external devices or accessories.
CKT9 on the RMI/ASU or
CKT 25 on the 8DRCM-2, 8DRCM, 8DRCF, U-RMI/U-MR/RMI/MR Office,
CDRS 200E, and IPx 500.
Corresponding default feature dial number: 7086Ô.

UNA [46] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user, or trunk, can access UNA/Bell (RLY2).
7-15
MODEM [47] Yes/No

Defines whether or not a station user, or trunk, can dial the MODEM.
CKT 26 on the 8DRCM/8DRCF, U-RMI/RMI Office, CDRS 200E, and IPx 500.
Ckt 26 - IPx 500M main Cage (Shelf #0, Slot #13) on the motherboard
(applicable on MSBipx Hardware Issue-0220X1003 or lower.)

 IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not
include a MODEM. The modem was standard in MSBipx Hardware
Issue-0220X1003 or lower.
PAGE [48] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can activate the page loudspeaker (RLY1),
typically used for the public address system.
 RMI or U-RMI/U-MR/RMI/MR Office card: This option is relevant only

when a second music source is not connected to M2/P.
CONF [49] Yes/No
 Not relevant for Group Calls.

Defines whether or not a station user, or trunk, can use the Join a Meet-Me
Conference or Progressive Add-On conference features.
CONF_RELEASE [50] Yes/No

Defines whether or not a station user, or E&M trunk, is allowed to release
conference participants from an ongoing regular Meet-Me conference.
7-16
CONF_LOCK [51] Yes/No

Defines whether or not a keyset station user is allowed to block a potential user
from joining an ongoing regular Meet-Me conference.
This parameter has no effect on Group Calls. See LOCK ACTIVE GROUP
CALL (page 10-34) for blocking non-registered members from joining an ongoing
Group Call.
LARGE_CONF_ Yes/No
FORC_REL [52]
Defines whether or not an idle station user is allowed to force release a single
participant from an ongoing Group Call (or chained Group Call).
This parameter must be set to Yes for COS defined Group Call Operators to operate
the release member from an active group call (default feature code #1305).
Corresponding default feature dial numbers:
Any idle station user can release member: #1446
Group Call Operator: Release member from within Group Call: #1305.
GROUP_CALL_ Yes/No
RELEASE_ALL [53]
Defines whether or not a user is allowed to terminate (disconnect) an entire Group
Call (all the chained Group Calls or just one of the Group Calls in the chain).
GROUP_CALL_ Yes/No

OPERATOR [54]
Keysets Only
Stations defined with this COS are able to define themselves or others as the Group
Call Operator. The group call operator may
• mute members or give speaking permission
• add/release members from an ongoing group call
• define another keyset station user (instead of the current operator) as the group
call operator from within the ongoing group call.
The Group Call operator can also be defined via the PI database in the CALL
branch, see GROUP OPERATOR (page 10-35).
Corresponding default feature dial numbers:#17716: Define Operator
7-17
ADD_ON_ Yes/No
CONFERENCE [55]
Defines whether or not a station user is allowed to establish a temporary Group
Call. The Group Call being used for this purpose must have the ADD_
ON (page 10-32) parameter set to Yes.
DVMS [56] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user, or trunk, can activate the DVMS
announcements on the 4VS or 4VSN card.
Corresponding default feature dial number:
DVMS Message: 5400Ô
DVMS Port: 7042Ô.
SAVED [57] Yes/No

Yes: COS 0-9;
No: COS 10-249
Saved Current Dial Number/Redial defines whether or not a station user can save
the currently dialed external number for future redialing by code.
ACCT [58] Yes/No

Yes: COS 0-9;
No: COS 10-249

Defines whether or not a station/trunk user can add the account code (as required)
to the call record before, during or after call.
 This option does not require the station user to dial an account code. To
require a user to dial an account code, F.A.C_TK_GRPS/ROUTING ACCESS
[6] on page 7-4 must be defined.
VFAC_PUBLIC [59] Yes/No

Defines whether or not a station user can use all account codes reserved for a
special station. Even account codes not defined for any users can be entered. When
enabled, this feature essentially transforms the station into a “public telephone”.
7-18
SERIES [60] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user engaged in conversation can activate the
series feature. This feature allows the user to mark a call before transferring it to a
third party. This causes the call to return to the original station after the third party
hangs up. Corresponding default feature dial number: #195.
SECURITY [61] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a station user can activate dataline security in order to
prevent break-in or a call-waiting tone over an in-progress call. This feature is
applicable, for example, while using a modem or facsimile.
DIRECT_DIALING_
ON_DIAL_SERVICE Yes/No;
[62]
Defines whether or not the port user is allowed to access destinations by directly
dialing the dial service number.
Set this parameter to Yes to enable the F.A.C_DIAL_SERVICE [7] (page 7-4)
parameter (i.e. enable VFAC on Dial Service).
PASS_TK_DIAL_TONE Yes/No
[63]
Yes: COS 0-10 and 12-249;

No: COS 11;
No: CC1: COS 2-6
Transfer Trunk Dial Tone defines whether or not a station user or E&M trunk can
seize a trunk and transfer the dial tone to another station (allowing the second
station to dial out).
PASS_TK [64] Yes/No
Yes: COS 0-10 and 12-249;

No: COS 11
Defines whether or not a station user, or E&M trunk, can transfer a trunk call to
another station.
7-19
ACCEPT_COLLECT_ Yes/No; (CC3: No)

CALLS [65]
A collect call is an incoming call where the called party is billed.
CC3 Systems only
This parameter defines whether or not a station user or another trunk can accept an
incoming collect call.
• The called party is not billed for the call, but the system manager is ultimately
billed.
• The protocol is available on incoming MFC lines on 30T/x cards and
8DID/S-Z cards. Similarly, it is available on an incoming analog line on
4T,8T,4TPF,8TPF,4T-C,8T-C cards.
For collect call blocking on incoming analog calls on 4T/8T cards, see COLLECT
CALLS BLOCK [11,12,13] CC3 only on page 8-55.
ACCEPT_TRUNKS_ Yes/No
XFERD [66]
Defines whether or not a station user or trunk can accept a trunk transfer by another
user. The purpose of this option is to deny specific users access to external calls.
TK_TK_XFER_ Yes/No
OVERRIDE [67]
Trunk-to-Trunk Transfer Override allows a station to establish a connection
between two trunks. Entering Yes allows a trunk to remain connected after the
station involved in a 3-way conference, between two trunks, onhooks.
 This parameter is relevant only when TK_TO_TK_CONNECT in SFE is set

to No (see page 6-8) and when TK_TK_CONNECT_OVERRIDE (page 8-23) in
Trunk Group Definition ([TKGDEF]) is set to No.
SMDR_SPLIT [68] S (Source) /D (Destination) / B (Both)

Both: COS 0-9;
Source: COS 10-259
Source: CC1: COS 0-9
Determines which station is charged when a transferred trunk call is made. Charges
can be made to the Source (Originator), the Destination or split between both the
source and destination, according to usage.
Source: Total charge is recorded against the extension that initiated the call.
Destination: Total charge is recorded against the extension where the call
terminates (receiving side).
Both: All parties are charged in proportion to the active call engagement.
7-20
PAGE_Q [69] Yes/No

Defines whether or not a station user or E&M trunk, can place a call on page queue.
The Page-Q parameter does not affect the Paging (ESPA) feature.
DTD [70] Yes/No
Yes: Dial tone must be detected on outgoing calls

No: The user can dial out without waiting for an external dial tone
Dial Tone Detect defines whether or not a station user is prohibited from dialing on
a trunk before the trunk dial tone is detected. This feature can be used only when
the outgoing trunk is not in a trunk group that overrides the dial tone detect
(requires an 8DTD, 8DRCM-2, 8DRCM, 8DRCF or U-RMI/U-MR Office to be
installed in the system), see DTD OVERRIDE on page 8-21.
FLASH_TK [71] Yes/No
Yes: COS 0-10 and 12-249;

No: COS 11
YCalibrated Opening On Trunk defines whether or not a station user, or E&M
trunk, can make a hookflash signal on a trunk.
PRIV_LIB [72] Yes/No; (CC1: COS 0-9: Yes)

Private Library defines whether or not a station user can program or update his own

private speed dial number library (library of frequently dialed numbers, auto dialed
when the speed dial code is entered). Private library numbers relate only to the
particular station and are not available to other station users.
CALL_TRACE [73] Yes/No

Defines whether or not a station user can utilize the “Malicious Call Trace” option.
(A list of incoming calls is recorded and can be printed.)
7-21
AUTO SET Yes/No

RELOCATE [74]
Defines whether or not a station user is allowed to swap phone profiles. This
feature is available only when this parameter is set to Yes for both source and
destination phones.
Corresponding default feature dial number: N/A
No default feature dial number is automatically assigned for this feature. The
system manager must define a default feature dial number corresponding to the
feature index number (220).
FLEXICALL [75] Yes/No

SAU Requirement
Defines whether or not the FlexiCall feature is accessible by the station. When
defined as Yes, this parameter enables defining another station or an off-site
telephone as an adjunct to your station number. Additionally, the off site phone is
enabled with Coral features.
Corresponding default feature dial number: FlexiCall All #17710; FlexiCall
Internal: #17711; FlexiCall External #17712.
IRSS_FEATURE [76] Yes/No

Defines whether or not a station user can dial into the Coral from their Coral
defined Freedom (IRSS) destination and access certain Coral services by becoming
a virtual Coral station.
Corresponding default feature dial number: #17714 + Public or Private
Library #.
IRSS_PASSCODE [77] Yes/No

Defines whether or not a passcode is required when dialing into the Coral from an
IRSS destination to receive Coral Services.
Set this parameter to No only for Freedom (IRSS) destinations which possess a
Caller ID.
7-22
DIAL_TONE 0..3
MESSAGE SOURCE 0..1: IPx 500 and CDRS 200E
[78] R (--): Remove for None
None (--) (Default - normal dial tone is heard)
SAU Requirement
When feature authorization exists (MUSIC DIALTONE on page 3-25), use this
parameter to define which Music Source is to be used instead of a Dial Tone. The
music source may also be a taped recording.
• This source cannot replace Distinctive Dial Tone.
• The music source must be connected via a RMI, 8DRCM-2, 8DRCM,
8DRCF or U-RMI/U-MR/RMI/MR Office. Otherwise only normal dial
tone can be heard.
When None (--) is entered, normal dial tone is heard.
BOSS_GROUP_CFWD Yes/No; (CC1: COS 0-9 = Yes)

INT/EXT [79]
Defines whether or not a Boss Group member can forward Boss Group calls to
another destination. Entering Yes enables the Boss Group member to activate any
type of attendant call forward feature.
Corresponding default feature dial numbers:
Internal/External Call Forward features: #167, #168, #169, #1984 AND
External Call Forward features: #17706, #17707, #17708, #17709.
7-23
MLPP:
PREEMPTABLE [80] Yes/No
Set this parameter to Yes to enable MLPP call preemption by this station user.
An established call where one of the parties is defined with COS Preemption set to
No, cannot be pre-empted.
PRECEDENCE_LEVEL 0..4 (see table below)

[81]
This parameter is only relevant when PREEMPTABLE [80], above, is set to Yes.
This parameter defines the precedence capability of the station user defined with
COS PREEMPTION set to Yes.:
Precedence
Description
Capabilities
0 - Flash Override Highest Precedence: Level 0.

Flash Override allows the highest precedence level. This
enables the user to have any other type of call dropped in
order to place a call over a busy trunk.
1 - Flash Flash allows precedence over all types of calls except
0-Flash Override.
2 - Immediate Lowest Precedence: Level 3.
Immediate allows precedence over all types of calls
except 0-Flash Override and 1-Flash.
3 - Priority Priority allows precedence over all Routine calls only.
4 - Routine No Precedence: Level 4.
Routine defines routine calls which may be placed by

anyone and is not defined as a precedence call.
MLPP SERVICE None or {Domain #}

DOMAIN [82]
This parameter defines the MLPP Service Domain number for this station user.
Station users may implement the MLPP feature only on other station users that
have identical domain numbers. The same domain number may be assigned in
more than one Coral system.
The domain number is a unique number determined by the system administrator.
Unique MFC Category 1..15

Digit [83]
Choose a unique MFC calling category. This category is to be sent to the CO while
the extension makes outgoing calls over MFC/R2 trunks.
7-24
ACD/UCD: The following options apply to ACD/UCD group members:
LOG_IN/OUT [84] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not the ACD group member can log in/out independently
of his/her ACD group. Also defines log-in to a primary group feature.
LOAD_ID [85] Yes/No

Determines whether or not an ACD member can load an ID number.
WRAP_UP_CODE [86] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not an ACD member can activate a wrap-up code, after an
ACD incoming call has been completed.
WRAP-UP TIME [87] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not an ACD/UCD member can activate the wrap-up time

feature.
RELEASE_RESUME_ Yes/No
ALL [88]
Yes: COS 0-9;
No: COS 10-249
Determines whether or not an ACD/UCD group member can independently
Release/Resume to or from all groups of which he or she is a member.
7-25
RELEASE_RESUME_ Yes/No
SINGLE_UCD [89]
Yes: COS 0-9;
No: COS 10-249
Determines whether or not a UCD group member can independently
Release/Resume from a single UCD group.
CALLS_WAIT [90] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not a FlexSet/keyset station user can view the number of
waiting calls for any ACD group.
7-26
KEYSET ONLY:  The following options apply only to the following Keysets.
• FlexSet
• FlexSet_IP 280S
• T207M, T208M, T207M/NP, T208M/BL
• CPA
• Wireless handsets (FlexAir/CoralAIR)
• GKT
• DKT
• DST
• EKT
• VDK
 The PROGRAM and PREFERENCE parameters apply to WSTs as well.

• FKT
V_PAGE_IN [91] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not a keyset station user can activate the voice page on/off
feature (default feature code: #134). This allows blocking or permitting the keyset
from receiving private and/or zoned voice page calls.
AUTO_ANS_V_PAGE Yes/No
[92]
Yes: COS 0-9;
No: COS 10-249
Determines whether or not a keyset station user can activate automatic answer

(open microphone) of incoming voice page calls to the user’s station. V_PAGE_IN
[38] (page 9-44), must be set to Yes and turned on at the keyset, to allow auto
answer.
(Not available to FlexSet 120L and DST users).
AUTO_ANS [93] Yes/No

Yes: COS 0-9;
No: COS 10-249
Auto Answer defines whether or not a keyset station user can activate auto
(handsfree) answer of calls.
7-27
MUSIC [94] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not a keyset station user can activate the background music
on/off feature. This feature requires that an ASU/RMI, 8DRCM-2, 8DRCM,
8DRCF or U-RMI/U-MR/RMI/MR Office card be installed in the system.
In the IPx 500 and CDRS 200E, no additional hardware is required.
A music source(s) must be connected and the music must be programmed (see
Music Sources - Chapter 4).
RING_ADJ [95] Yes/No

Yes: COS 0-9;
No: COS 10-249
Adjust Ring Level, Frequency, Cadence determines whether or not a keyset station
user can adjust ring volume, frequency, and cadence levels.
IDLE_DISPLAY [96] Yes/No

Yes: COS 0-9;
No: COS 10-249
Determines whether or not an idle display (Name, Number, Date and Time) can be
turned on or off at the keyset station. Allows showing or hiding the
clock/date/station identification display. This option is relevant only for key sets
equipped with a display window.

PROGRAM [97] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a keyset or wireless station user can program the
programmable keys (and DPEM/FlexSet 40B when provided).
7-28
PREFERENCE [98] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a keyset or wireless station user can program preference
priorities; to select a specific line, loop, etc. whenever the handset is lifted, the
Speaker key is pressed, or the dial pad is used.
AUTO_REDIAL [99] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not a keyset station user can activate the Automatic Called
Number Redial (ACNR).
• Version 16 or higher (applicable on PRI and SIP trunks, while other trunk type
requires an 8DTD, 8DRCM, 8DRCM-2, 8DRCF or U-RMI/U-MR Office card
with dial tone detectors installed in the system to activate this feature).
• Version 15 (all trunks type require an 8DTD, 8DRCM, 8DRCM-2, 8DRCF or
U-RMI/U-MR Office card with dial tone detectors installed in the system to
activate this feature).
• Version 14 or lower (all trunks type require an 8DTD, 8DRCM, 8DRCF or
U-RMI/U-MR Office card with dial tone detectors installed in the system to
activate this feature).

AUTO_REDIAL# [100] 0 (denied)..3..100 (100 number directory)

CC1: COS 0-9 = 10

Defines the amount of external phone numbers (ACNR) that can be stored for
redialing by the system. Redial is on a one-by-one basis.
7-29
ISDN: The following three parameters, BCCOS [101], ISDN_ONLY [102], and CALLER_ID_
CONTROL [103], apply to ISDN sets or stations that access ISDN features:
BCCOS [101] 0..63

Defines which Bearer Capability COS (BCCOS) is relevant for the specific trunk
or station defined as ISDN when dialing in or out of the Coral system.
BCCOS is defined in Chapter 26.
ISDN_ONLY [102] Yes/No

Defines whether the ISDN call is routed along ISDN trunks for the entire
connection when set to Y, i.e. full end-to-end ISDN connection required. If the
Network routes the call over a non-ISDN service, a message is sent back to the
caller and the call is terminated.
CALLER_ID_ Yes/No
CONTROL [103]
Defines whether or not a station user can access the feature allowing or restricting
(temporarily) the presentation of their telephone number to the called party.
7-30
IP:
SECURED CALLS Yes/No
[104]
Defines whether to secure IP calls by encoding the call. When set to Yes, the call
is encoded according to the highest coding allowed by both sides of the call.
The FlexSet-IP 280S reports its coding abilities in the registration message after
initialization.
USER_ Up to 10 items, between 0 and 13 within parentheses separated by commas

COMPRESSION_LIST or spaces, or ( ) for None
[105] Default: (5)
0=G.711 with 10ms; 7=G.729 with 40ms;
1=G.711 with 20ms 8=G.723 with 30ms+vad;
2=G.711 with 40ms; 9=G.723 with 60ms;
3=G.723 with 30ms; 10=G.729 with 20ms+vad;
4=G.729 with 10ms; 11=G.711 with 80ms
5=G.729 with 20ms; 12=G.723 with 90ms;
6=G.729 with 30ms; 13=G.729 with 80ms;
G.711 defines no compression

G.723 defines compression ratio between 5 and 6
G.729 defines a compression ratio of 8
VAD makes use of silence to gain even better call compression
with x ms defines the delay time between packets
Defines the available Gateway Compressions used for IP calls, in order of
preference, for this COS. Any number of compressions may be entered between
parentheses, separated by commas or spaces. The placement of the numbers

defines their priority. Matching compression values must be found in the COSs of
both calling parties in order to complete the IP call.
If one of the calling sides is not an IP endpoint, then that party assumes the
compressions available for the UGW card (via the MG module) handling the call.
For Example: (1, 5) means that this sets the compression to 1=G.711 with 20 ms
as the primary codec and 5=G.729 with 20 ms as the secondary codec. If a local
SIP terminal were to call another local SIP terminal the call will be established
using the G.711 codec. If a local SIP terminal calls a remote SIP terminal that only
has codec G.729 programmed then the call will be connected at G.729.
For Example: (1, 2, 3, 4) means that compression 1=G.711 with 20 ms is to be
used for all calls defined with this COS number, but only if both IP endpoints have
the same COS.
If both sides do not have compression 1 defined in their COSs, then the system tries
to use the next number on the list, 2 in this case. If both have 2 defined in their COS
definition, then the call is completed in with the compression of 2=G7.11 with
7-31
40ms. The system continues looking for matching compressions within both
COSs.
If no compression matches both COSs, then the call is denied and a CODEC
MISMATCH error ensues.
• To add a single number or more, enter: (A, number 1, number 2,...)
• To remove a single number or more, enter: (R, number 1, number 2,...)
SIP:
TRANSPARENT_SDP Yes/No
[106]
Set this parameter to Yes to do the following:
• Instruct the Coral system to match the Codecs chosen by SIP to SIP stations
(P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and
third-party SIP terminals), without Coral interference, regardless of whether or
not the Coral can support the Codecs (i.e. video, data, or future audio
CODECs).
• Instruct the Coral to accept external fax transmissions via T.38.
Additionally, this SDP mode also enables three terminals to conduct 3-way SIP to
SIP to SIP calls, or video calls with audio CODECs not recognized by the Coral.
7-32
Attendant Class of Service ç COS,1 [0,0,2,1]
The following features apply only to stations defined as Attendant (see ATT [17] on
page 9-8:SLT and on page 9-35:Keysets/FlexSets). The attendant controls are
divided into three categories: Station Controls, Trunk Controls and System
Controls.
FROM/TO COS# 0 to maximum number defined in SIZ (see page 4-16)

All
Enter the COS numbers required for attendant stations.
ST CONTROL: The following parameters determine the ability of an Attendant station user to (a)
change some non-Attendant station definitions (such as originate/terminate only),
(b) establish “hot” destinations, (c) block stations and trunks, (d) set wakeup and
call forward assignments for stations.
CALLS”.
ORIG.ONLY [2] Yes/No

Yes: COS 0-10, 12-249;
Attendant Class of Service COS,1 [0,0,2,1]

No: COS 11
Originate Calls Only defines whether or not an attendant can prohibit a station from
receiving calls.
TERM.ONLY [3] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Terminate Calls Only defines whether or not an attendant can prohibit a station
from making any calls.
7-33
ST_BLOCK [4] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Block Calls To/From Station defines whether or not an attendant can remove a
station from service. In other words, prohibiting the station from both making and
receiving any calls at the station.
O/G_TK_REST [5] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Outgoing Trunk Restriction defines whether or not an attendant can prohibit a
station from originating outgoing trunk calls. (Internal calls are permitted.)
MSG_WAIT [6] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can leave a message waiting indication at a
station (ring or lamp. Message indicator type depends upon station equipment.)
HOT_ST_IMM [7] Yes/No

Yes: COS 0-10, 12-249;

No: COS 11
Hot Station Immediate defines whether or not an attendant can designate a station
to automatically and immediately ring at a predetermined destination when
offhook.
HOT_ST_DELAY [8] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Hot Station Delay defines whether or not an attendant can designate a station to
automatically ring at a pre-determined destination, if no digits are dialed, within a
specified time (see 1st_DIGIT [10] on page 9-3 in Station Timers).
7-34
CF_BUSY INT/EXT [9] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether an attendant can activate Call Forward Busy for other stations.
CF_ALL INT/EXT [10] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether an attendant can activate Call Forward All for other stations and
groups.
CF_NO_ANS INT/EXT Yes/No

[11]
Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can activate Call Forward No Answer for other
stations.
TIMED_FWD INT/EXT Yes/No

[12]
Yes: COS 0-9;
No: COS 10-249

Defines whether or not an attendant can activate Call Forward Timed for other
stations.
DONT_DISTURB [13] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can place a user’s station in Do Not Disturb
mode.
7-35
WAKEUP [14] Yes/No

Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not an attendant can set wakeup time for a user’s station. If no
Authorization exists when dialing, the message ILLEGAL appears on the
attendant’s keyset.
CHECK_IN/OUT [15] Yes/No

Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not an attendant or PMS can change the status of a station from
check-in to check-out or from check-out to check-in. If no Authorization exists
when dialing, the message ILLEGAL appears on the attendant’s keyset.

Defines whether or not the Attendant can create “Malicious Call Trace” records for
any other station user. (A list of incoming calls is recorded.)
CALL_TRACE_PRINT Yes/No
[17]
Defines whether or not the Attendant can print the Call Trace Records created. This
parameter is only relevant when CALL_TRACE above is set to Yes.
7-36
ROOM_STATUS [18] 0..15 or ( ) for None;

Defaults: COS 0-9: (0..15);
COS 11: ( ) None;
COS 10, 12-249: (0, 2..14)
SAU Requirement: HOTEL/MOTEL (page 3-20).
Defines which Room Status or User Canned Messages are accessible by the
attendant to enable at different stations. Room Status and User Canned Messages
are mutually exclusive such that the system can only support one of these features.
Each feature requires Authorization, however, the system defaults to the Room
Status Feature. To change this default, USER_CANNED_MESSAGES [21] (page 6-25)
must be set to Yes in the System Features - Station Options branch (SFE, 2).
Up to 16 unique status categories can be defined in the Coral. Any one or more
Room Status’ may be assigned to a station (room) at any time. Only one User
Canned Message may be assigned to a station at a time.
If no Authorization exists when dialing the Room Status/Message code, the
message ILLEGAL appears on the station user’s keyset.
If no Authorization (SAU) exists when dialing, the message ILLEGAL appears on
the station attendant’s keyset.Room status/User Canned Messages numbers are
entered between parentheses, with the numbers separated by a comma or spaces.
Corresponding default feature dial number: 7010 to 7025.
7-37
TRUNK The following parameters determine an Attendant’s ability to modify certain trunk
CONTROL: operations.
BUSY_OUT [19] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can make a trunk busy, effectively taking it out
of service for incoming and outgoing calls.
CO_BLOCK [20] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can display trunks blocked by the CO.
LAR_BLOCK [21] Yes/No

Defines whether or not an attendant can block and/or release a trunk/Dial Service
blocked by the Look Ahead Routing (LAR).

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can set or reset the Auto Guard status of
individual trunks. When set to Yes, Auto Guard Active automatically checks trunks
for dial tone and removes trunks from service if no dial tone is present (see also,
AUTO_GUARD [2] on page 6-52).
I/C_ONLY [23] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Incoming Only defines whether or not an attendant can prohibit outgoing trunk calls.
7-38
O/G_ONLY [24] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Outgoing Only defines whether or not an attendant can prohibit incoming trunk calls.
RSRVD_TO [25] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can reserve a trunk to a specific station or
group of stations for outgoing calls.
HOT_TK_IMM [26] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Hot Trunk Immediate defines whether or not an attendant can designate an
outgoing trunk to immediately connect when the trunk is seized.
HOT_TK_DELAY [27] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11

Hot Trunk Delay defines whether or not an attendant can designate an outgoing
trunk to connect when no digits are dialed within the time specified by the
Outgoing 1st_DGT timer (see page 8-4).
DROP_NO_DIAL [28] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can instruct the system to disconnect a seized
outgoing trunk if no digits are dialed within the time specified by the Outgoing 1st_
DGT timer (see page 8-4).
7-39
DIR_IN_LINE [29] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Direct In Line (DIL) defines whether or not an attendant can designate the
incoming call destination of a trunk (Direct In Line, or DIL) to a specific
destination when the system is in DAY mode.
NIGHT1_DEST [30] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can designate the incoming call destination of
a DIL trunk to a specific destination when the system is in NIGHT1 mode.
NIGHT2_DEST [31] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can designate the incoming call destination of
a DIL trunk to a specific destination when the system is in NIGHT2 mode.
7-40
SYS(TEM) The following parameters determine an Attendant’s ability to control system

CONTROL: options.
ATT_ST_DEST [32] Yes/No

Yes: COS 0-9; (No: CC1: COS 0-9);
No: COS 10-249
Attendant Station Destination defines whether or not an attendant can route calls to
a specific station when the Attendant station is in the DO NOT DISTURB mode
(unattended).
See AUTO_UNATT_TRANS [18] on page 9-9 for SLTs or AUTO_UNATT_TRANS [18]
on page 9-36 for FlexSets/Keysets.
TIME/DATE_SET [33] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can set the system time and date.
NIGHT1_SELECT [34] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can change the system between DAY and
NIGHT 1 mode (when the change is made it overrides the system time definition

of Night 1 transfer). This type of service is used when the system is programmed
for manual operation.
NIGHT2_SELECT [35] Yes/No

Yes: COS 0-10, 12-249;
No: COS 11
Defines whether or not an attendant can change the system between DAY and
NIGHT2 mode (when the change is made it overrides the system time definition of
Night2 transfer). This type of service is used when the system is programmed for
manual operation.
7-41
AUTO_NIGHT SERV Yes/No

[36]
Yes: COS 0-9;
No: COS 10-249
Automatic/Manual Night Service defines whether or not an attendant can set the
system for manual or automatic (on time) Day/Night mode transfer. (See ON TIME
on page 12-2 in Night Service Timers, for an explanation of automatic or manual
service period transfer).
PUBL_LIBS [37] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can add, change or delete public library
(system wide speed call directory) numbers.
 The Attendant may add, change, or delete public speed call libraries, but
may not change the Toll Barrier Override and Name parameters of an
entry (Public Library). The Toll Barrier Override default is No and can be
changed only via a PI service terminal.
KB0_SET_UP [38] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can change the communications parameters of

PI terminal port KB0 (on Coral IPx Office, MCP-IPx2, MEX-IP2 or MCP-ATS
cards).
ALARM [39] Yes/No

Yes: COS 0-9;
No: COS 10-249
Defines whether or not an attendant can list system alarm messages on an
Attendant keyset station equipped with a display.
7-42
WAKEUP_REPORT Yes/No
[40]
Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not an attendant can send a request to receive a wakeup report
on a monitor or printer. If no Authorization exists when dialing, the message
ILLEGAL appears on the station attendant’s keyset.
Corresponding default feature dial number: #1971
CHARGE_PRINT [41] Yes/No

Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not an attendant can send a request to receive a system Charge
Table printout (detailed station current phone charges). If no Authorization exists
when dialing, the message ILLEGAL appears on the station attendant’s keyset.
CHARGE_PRINT_ Yes/No
AND_RESET [42]
Yes: COS 0-9;
No: COS 10-249
SAU Requirement
Defines whether or not an attendant can send a request to receive a printout and
then reset the system Charge Table. If no Authorization exists when dialing, the

message ILLEGAL appears on the station attendant’s keyset.
ACD_CALLS_FOR_ Yes/No
BUSY [43]
Defines whether or not the attendant is allowed to determine the maximum number
of calls waiting for any ACD group in the system.
7-43
Tenant Class of Service ç COS,2 [0,0,2,2]
The Tenant COS is an optional programming tool which allows the system to be
segmented into as many as 64 (0-63) unique Tenant Groups. Each tenant group is
a “separate virtual system”. It can be independently configured to operate as a key
system, hybrid system or private branch exchange.
Tenant programming is usually applied when one Coral has to serve several groups
of users. Tenant COS allows intra-system calling to be segmented as if each tenant
group owns a dedicated system.
Hierarchical orders can be established through tenant groups. For example, a
manager can be defined to enable placement of calls to assistants, but the assistants
can be defined so that they cannot directly call the manager. Instead, their calls can
be routed to another destination.
The Tenant COS feature may require altering the maximum number of Classes of
Service provided in the system size programming (see Chapter 4 - System Sizes).
The COS entry in system sizes should allow each tenant its own Class of Service.
By assigning different COS numbers to particular ports, groups may be composed
solely of trunks, of stations, or a combination of trunks and stations.
Tenant stations may be allowed or denied access to other group stations and trunks.
Inter-tenant calling may be allowed either one-way only or two-way (by defining
the Tenant Groups and Group Access’s accordingly). When Tenant COS is defined
as one-way, Tenant A stations can call Tenant B stations, but Tenant B stations
cannot call Tenant A stations. When defined as two-way, both tenant groups can
call each other.
COS defaults to tenant group 0. There may be as many as 64 (0-63) unique tenant
Tenant Class of Service COS,2 [0,0,2,2]
groups and as many as 250 Classes of Service, as defined in Sizes (see page 4-16),
allowing an average of up to four different Class Of Services for each tenant group.
Figures 7-1, 7-2, 7-3 and 7-4 below, illustrate typical tenant group applications.
7-44
FROM/TO COS# 0 to maximum defined in Sizes, see COS on page 4-16;

All
Enter the COS numbers required for Tenants.
TNNT_GRP [0] 0..63 (see Figure 7-1)

Ports can receive calls only from other ports whose GRP.ACCESS includes the
number defined in this field (not used for voice page, see VP_TNNT_GRP [5],
below).
GRP. ACCESS Defines the group access, i.e., all ports with the same current COS that can make
calls to other ports whose TNNT_GRP number is defined in this parameter.
The Group Access are divided into four groups, 0-15, 16-31, 32-47, and 48-63.
Each group has its value defined as Multiple.
 Notes:
• Enter information under the display line.
• The number(s) must be entered between parentheses, in ascending order
and separated by a space or comma.
• Closed parentheses indicate that access is denied (no link).
7-45
GRP. ACCESS (0-15) [1]

Range: Any ascending combination
(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
Default: See Table 7-2
GRP. ACCESS (16-31) [2]
(16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31) or ( ) for None;
GRP. ACCESS (32-47) [3]
(32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47) or ( ) for None;
GRP. ACCESS (48-63) [4]
(48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63) or ( ) for None;
Figure 7-1. Tenant

COS 0
Group-Group
Access TNNT_GRP 0
GRP. ACCESS (0-15) (1,2)

GRP. ACCESS (16-31) ()
GRP. ACCESS (48-63) (63)
COS 1 COS 2
TNNT_GRP 1 TNNT_GRP 2
GRP. ACCESS (0-15) (0,1) GRP. ACCESS (0-15) (0,2)

GRP. ACCESS (16-31) () GRP. ACCESS (16-31) ()
GRP. ACCESS (32-47) () GRP. ACCESS (32-47) ()
GRP. ACCESS (48-63) (63) GRP. ACCESS (48-63) (63)
COS 3 and COS 4
TNNT_GRP 63
GRP. ACCESS (0-15) (1)

GRP. ACCESS (48-63) (63)
7-46
VP_TNNT_GRP [5] 0..63 (See Figure 7-2)

Allows placing all keysets with the same COS into a unique tenant group for
incoming voice paging calls (not used for incoming calls, see TNNT_GRP, above).
Keyset users can receive voice page calls only from other ports whose VP.ACCESS
includes the number defined in this parameter.
VP. ACCESS Allows defining all ports with the same current COS that can make voice page calls
to other keysets whose VP_TNNT_GRP number is defined in this parameter.
 Notes:
7-47
VP. ACCESS (0-15) [6]

(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
VP. ACCESS (16-31) [7]
(16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31) or ( ) for None;
VP. ACCESS (32-47) [8]
(32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47) or ( ) for None;
VP. ACCESS (48-63) [9]
(48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63) or ( ) for None;
Figure 7-2.Tenant
Group-Voice Page COS 0
Access
VP_TNNT_GRP 0
VP. ACCESS (0-15) (1,2)

VP. ACCESS (16-31) ()
VP. ACCESS (32-47) ()
VP. ACCESS (48-63) (63)
COS 1 COS 2
VP_TNNT_GRP 1 VP_TNNT_GRP 2
VP. ACCESS (0-15) (0,1) VP. ACCESS (0-15) (0,2)

VP. ACCESS (16-31) () VP. ACCESS (16-31) ()
VP. ACCESS (32-47) () VP. ACCESS (32-47) ()
VP. ACCESS (48-63) (63) VP. ACCESS (48-63) (63)
COS 3 and COS 4
VP_TNNT_GRP 63
VP. ACCESS (0-15) (1)

VP. ACCESS (16-31) ()
VP. ACCESS (32-47) ()
VP. ACCESS (48-63) (63)
7-48
SILENT_MONITOR_ 0..63 (See Figure 7-3)

TNNT_GRP [10]
Allows placing all keysets with the same COS into a unique tenant group for silent
monitoring use.
Ports can be monitored only by other ports whose SM.ACCESS includes the
number defined in this field.
 Defines the Silent Monitor access, i.e. all ports with the same current COS
SM.ACCESS
that can silent monitor other ports whose SILENT_MONITOR_TNNT_
GRP number is defined in anyone of the following four parameters: Notes:
7-49
SM. ACCESS (0-15) [11]

(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
SM. ACCESS (16-31) [12]
(16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31) or ( ) for None;
SM. ACCESS (32-47) [13]
(32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47) or ( ) for None;
SM. ACCESS (48-63) [14]
(48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63) or ( ) for None;
Figure 7-3. Tenant

Group-Silent Monitor
Access COS 0
SILENT_MONITOR_TNNT_GRP 0
SM. ACCESS (0-15) (1,2)

SM. ACCESS (16-31) ()
SM. ACCESS (32-47) ()
SM. ACCESS (48-63) (63)
COS 1 COS 2
SILENT_MONITOR_TNNT_GRP 1 SILENT_MONITOR_TNNT_GRP 2
SM. ACCESS (0-15) (0,1) SM. ACCESS (0-15) (0,2)

SM. ACCESS (16-31) () SM. ACCESS (16-31) ()
SM. ACCESS (32-47) () SM. ACCESS (32-47) ()
SM. ACCESS (48-63) (63) SM. ACCESS (48-63) (63)
COS 3 and COS 4
SILENT_MONITOR_TNNT_GRP 63
SM. ACCESS (0-15) (1)

SM. ACCESS (16-31) ()
SM. ACCESS (32-47) ()
SM. ACCESS (48-63) (63)
7-50
BREAKIN_TNNT_GRP 0..63 (See Figure 7-4)

[15]
Allows placing all keysets with the same current COS into a unique tenant group
for Breaking In to a call.
Ports can accept break-ins into established calls only from those ports whose
BRK.ACCESS includes the number defined in this field.
BRK.ACCESS Defines the Break-In access, i.e. all ports with the same current COS that can
break-in to established calls of other ports whose BREAKIN_TNNT_GRP number
is defined in anyone of the following four parameters:
 Notes:
7-51
BRK. ACCESS (0-15) [16]

(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
BRK. ACCESS (16-31) [17]
(16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31) or ( ) for None;
BRK. ACCESS (32-47) [18]
(32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47) or ( ) for None;
BRK. ACCESS (48-63) [19]
(48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63) or ( ) for None;
Figure 7-4. Tenant

Group-Break-In
Access COS 0
BREAKIN_TNNT_GRP 0
BRK. ACCESS (0-15) (1,2)

BRK. ACCESS (16-31) ()
BRK. ACCESS (48-63) (63)
COS 1 COS 2
BREAKIN_TNNT_GRP 1 BREAKIN_TNNT_GRP 2
BRK. ACCESS (0-15) (0,1) BRK. ACCESS (0-15) (0,2)

BRK. ACCESS (16-31) () BRK. ACCESS (16-31) ()
BRK. ACCESS (32-47) () BRK. ACCESS (32-47) ()
BRK. ACCESS (48-63) (63) BRK. ACCESS (48-63) (63)
COS 3 and COS 4
BREAKIN_TNNT_GRP 63
BRK. ACCESS (0-15) (1)

BRK. ACCESS (48-63) (63)
7-52
Table 7-2: Tenant Access Defaults
Tenant Access Defaults for:

Type
COS 0, COS 1
COS 2-15
GRP.ACCESS(0-15)- (0) (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
GRP.ACCESS(16-31)- () (16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31)
GRP.ACCESS(32-47)- () (32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47)
GRP.ACCESS(48-63)- () (48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63)
VP.ACCESS(0-15)- (0) (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
VP.ACCESS(16-31)- () (16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31)
VP.ACCESS(32-47)- () (32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47)
VP.ACCESS(48-63)- () (48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63)
SM.ACCESS (0-15)- (0) (1)
SM.ACCESS (16-31)- () (16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31)
SM.ACCESS (32-47)- () (32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47)
SM.ACCESS (48-63)- () (48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63)
BRK.ACCESS (0-15)- (0) (1)
BRK.ACCESS (16-31)- () (16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31)
BRK.ACCESS (32-47)- () (32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47)
BRK.ACCESS (48-63)- () (48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63)
7-53
7-54
8 Trunk Controls
This chapter contains the programming instructions for all trunks.

General Trunk Timers...................................................................................8-3
Trunk Timers ................................................................................................8-7
MFR Card Database ...................................................................................8-10
General Trunk Definitions.......................................................................... 8-11
Trunk Group Definition..............................................................................8-18
Alternate Route...........................................................................................8-34
DID/E&M Groups ......................................................................................8-36
Offset Filters ...............................................................................................8-42
Power Fail Trunk Definition ......................................................................8-44
LS/GS (Loop/Ground Start) Trunks...........................................................8-46
4T/8T LGS Port Database ..........................................................................8-50
4T/8T Card Database..................................................................................8-52
4TEM - E&M Continuous .........................................................................8-58
E&M Continuous Timers ...........................................................................8-59
4TEM (E&M Continuous) Card Database.................................................8-62
4TEMP (E&M Pulsed)...............................................................................8-64
4TEMP (E&M Pulsed) Port Database................................................ 8-65
4TEMP (E&M Pulsed) Card Database............................................... 8-67
4TWL Trunk Card Database ......................................................................8-84
E&M Trunk Definition...............................................................................8-87
DID Trunk Definition.................................................................................8-90
8DID Card Database ..................................................................................8-91
T1 and 30T/x Card Configuration..............................................................8-95
T1, PRI, TBR, 30T/x, 2DT Synchronization............................................8-98
2DT Card Database ..................................................................................8-102
2DT Card Database: DEFAULT Configuration ............................... 8-103
2DT Card Database: CURRENT Configuration .............................. 8-105
T1 and 30T Card Database.......................................................................8-108
T1 and 30T Port Database........................................................................ 8-111
30T/M Cards............................................................................................. 8-113
30T/M Card Database ....................................................................... 8-114
30T/M DDI/DDO/BI-D Port Database............................................. 8-120
8-1
Trunk Controls PI Reference Manual
30T/M DDI Port Database................................................................ 8-122

30T/M Timers ................................................................................... 8-123
30T/E Cards..............................................................................................8-124
30T/E Card Database ........................................................................ 8-125
30T/E DDI Port Database................................................................. 8-130
30T/E DDO Port Database ............................................................... 8-132
30T/E NonDDI Port Database .......................................................... 8-133
ALS70 Cards ............................................................................................8-135
ALS70 Card Configuration............................................................... 8-136
ALS70 Card Database ...................................................................... 8-138
ALS70 Port Database........................................................................ 8-141
ALS70 Loop Start Port Database ..................................................... 8-142
ALS70 DID Port Database ............................................................... 8-143
ALS70 NonDID Port Database ........................................................ 8-144
ALS70 Trunk Timers ........................................................................ 8-145
BID Cards .................................................................................................8-146
BID Trunk Port Database ................................................................. 8-147
BID Trunk Timers............................................................................. 8-149
GID Cards.................................................................................................8-150
GID Card Database ........................................................................... 8-151
GID Port Database ............................................................................ 8-155
GID Timers ....................................................................................... 8-157
PRI/TBR/BRI Database............................................................. see Chapter 26
ISDNet Database ....................................................................... see Chapter 28
8-2
PI Reference Manual Trunk Controls
General Trunk Timers ç TK.T,0 [0,0,1,2,0]
General Trunk Timers are used to set the system timers for all trunks. Specific
trunk types (for example, E&M, DID) may have additional timing parameters
which must also be programmed.
RELEASE_BLOCK [0] 1..3..100 (1 unit = 0.1 second)

Eu3: 31;
Eu8: 40
Determines the time interval following release of a trunk, in which an outgoing

seizure on the trunk is prohibited. This option thus provides a guard period after the
trunk is released to ensure that the CO has cleared the existing call before a new
call is attempted. This timer has no effect on the appearance of a new incoming call
on the trunk.
RECALL [1] 100..150..4200 (1 unit = 0.1 second)

Eu0/Eu2: 600
CC1/Eu1: 450
Recall determines the time interval a transferred or camped on trunk call remains
unanswered at the transfer-to station before recalling to the call originator or
rerouting to the Incomplete Call Destination. This feature is not relevant when a
station is defined as Multi-Appearance.
RLS_AFTER_XFER [2] 1..100 (1 unit = 0.1 second)

CC0: 30 (Use 1 unit if the system is not connected to a CENTREX)
Release After Transfer is relevant when the Coral is connected through a trunk to
General Trunk Timers TK.T,0 [0,0,1,2,0]

another exchange such as an electromechanical switch or for CENTREX applications.
Coral station A in Exchange Y is connected through a trunk to station B in
Exchange X. A wants to transfer the call to station C in Exchange X and
disconnect, leaving station B connected to station C. In this case, station A and the
trunk are released to idle.
Station A must send a “Flash On Trunk” (i.e. Calibrated Opening) signal and then
dial the telephone number for station C in Exchange X after which A onhooks.
If station A onhooks before the O/G interdigit time-out period, or while the system
sends digits from a speed dial library or programmed button, the Coral waits a
RLS_AFTER_XFER period before releasing the trunk.
If station A onhooks after the O/G interdigit time-out period, the Coral does not
wait the RLS_AFTER_XFER period and the trunk is immediately released.
The Flash On Trunk signal is activated at a Coral station by using feature code 150
or by programming a speed dial number with code E9.
8-3
MFC_ACK [3] 100..600..3000 (1 unit = 0.1 second)

CC2: 1200
Defines the maximum duration within which an MFC acknowledgment signal is
transmitted to the Central Office. For each digit recognized by the Coral, the Coral
must send an MFC ACK signal until the tone is ceased by the Central Office. If the
tone is not stopped, this parameter determines the time value that MFC ACK sends.
This feature is used mostly for 8BID or 30T/E trunks in European systems, and
30T/M in Mexico. This parameter must be defined in conjunction with the MFR
Card Database beginning on page 8-10.
MLPP_RESERVED_ 50..150..450 (1 unit = 0.1 seconds)

FOR_REUSE [4]
Defines the maximum time period that the trunk can be held after the MLPP station
user cleared the trunk from a previously engaged call.
INCOMING: The following options are relevant for incoming calls only.
DELAY_DISA [5] 10..40..250 (1 unit = 0.1 second)

Eu1: 80
Eu9: 250
Determines the time period that an incoming external caller on a trunk defined as
DISA [0] (page 8-11) must hear a ringback tone before the incoming call is answered
with system dial tone, for further inward dialing.
1st_DGT [6] 10..100..1200 (1 unit = 0.1 second)

Eu1: 650
Determines the maximum system waiting time for receiving the first dialed digit,
on an incoming trunk call on a DID, E&M, or DISA remote access trunk.

INTERDGT [7] 10..60..1200 (1 unit = 0.1 second)

Eu1: 650
Eu2: 200
Determines the maximum system waiting time between any two dialed digits in an
incoming call on a DID, E&M or DISA remote access trunk.
CALLER_ID_TIMEOUT 1..50..600 (1 unit = 0.1 second)

[8]
Defines the maximum system waiting time for information over Loop-Start analog
trunks for CID information. For these trunks, the call handling proceeds after the
CID information is received or the time-out expires.
8-4
OUTGOING: The following options relate to outgoing calls only:
ANSWER_DELAY [9] 100..600..4200 (1 unit = 0.1 second)

Determines the maximum system waiting time, after origination of an outgoing
trunk call, for the called party’s offhook (answer) signal. This timer is relevant only
to trunks which detect an answer supervision signal. The Wait for Answer timer is
initiated at the expiration of the O/G Interdigit timer (defined later in this chapter).
TONE_DELAY [10] 10..600..1000 (1 unit = 0.1 second)

Eu1: 250
Determines the maximum system waiting time to detect tone on outgoing trunks.
The delay operates under the following conditions:
• While waiting for trunk dial tone (if so defined) in order to start outdialing
• After an E6 (#6) command while waiting for second trunk dial tone (speed and
routing dialing).
• While waiting for ringback or busy tone by the Auto Called Number Repeat
feature. Tone detection requires an 8DTD, 8DRCM-2, 8DRCM or 8DRCF in
card installed in the system. These cards are not required in the CDRS 200E
and IPx 500.
1ST_DGT [11] 10..600..1200 (1 unit = 0.1 second)

Eu1: 100
Determines the maximum system waiting time, after trunk seizure, for the first
dialed digit on outgoing trunk calls.

Determines the maximum system waiting time, between any two dialed digits, on
outgoing trunk calls.
BUSY_ON_TRUNK 1..300..65500 (1 unit = 0.1 second)

[13]
When a user (station or E&M trunk) dials an outgoing CO trunk to a busy external
telephone, this feature determines the duration of the external (CO) busy tone
before the Coral system reverts to reorder tone (disconnect). Defines the duration
that the busy tone will be sent by the CO to the extension when the outgoing trunk
is PRI/BRI or MFC and the destination is busy.
PTS_DELAY [14] Contact manufacturer; 600 (1 unit = 0.1 second)

Proceed To Send Delay determines the protection time interval for trunks waiting
for a PTS signal. Also applies to GS and 30T/E/M-DDO trunks. Consult the
manufacturer before changing the default.
8-5
DELAY_TO_VM_ 1..40..65500 (1 unit = 0.1 second)

DIGITS [15]
Defines the maximum time period that the originating PINX waits before sending
Outgoing Network Calls
DTMF digits (such as Voicemail box number, personal passcode, etc.) to the
only destination PINX connected to an external application, usually a Voicemail system.
8-6
Trunk Timers ç TK.T,1 [0,0,1,2,1]
Each trunk port is assigned one of the five Trunk Timers Table profiles (TK TIMER
[2] (page 8-11)). Loop-start/Ground-start (LS/GS) and Direct Inward Dial (DID)
trunks default to values listed in Table 0, E&M trunks default to values listed in the
first Table. Additional timers may be required for specific trunk types.
FROM 0..4
TO 0..4
TK_TIMER#
Enter the required range of trunk timers profiles; FROM the lowest TO the highest.
H. FLASH [0] Range: 2..100 (1 unit = 10 ms)
Defaults:
Timer 0: Timer 1:
CC0: 67 CC0: 60
CC1: 60 CC7: 20
Eu0: 10 Other Systems: 40
Eu1-Eu8:14
Other systems: 6
H.Flash (i.e. Calibrated Opening) determines the duration of the pulse sent as a
hookswitch flash on a trunk.
INCOMING: The following parameters are relevant only during incoming calls on trunks, and
may be adjusted to match the protocol for the terminating end.
E&M_SEIZE_TO_ 1..10 (1 unit = 0.1 second)
Trunk Timers TK.T,1 [0,0,1,2,1]

WINK [1]
E&M Delay from Seize to start of Wink determines the delay period from the
E&M Continuous Only
detection of an incoming Seize signal to the start of the outgoing Seize
acknowledge signal. In addition to this delay, a Wink will not start until system
resources (for example audio link and DTMF receiver) are available to process the
call.
E&M_CONT_WINK_ 1..2..10 (1 unit = 0.1 second)

TIME [2]
Determines the duration of a Wink signal.
E&M Continuous Only
8-7
OUTGOING: The following options are relevant only during outgoing calls on trunks, and may
be adjusted to suit the receiving end protocol.
E&M_CONT_ 10..200 (1 unit = 0.1 second);

WINK/SG_DELAY [3] Timer 0: 1
E&M Continuous Only Timer 1: 45
Timers 2..4: 1
Determines the maximum time system waits for Wink/Start-Go (seize
acknowledge) signal on E&M continuous trunk.
SEIZE_TO_DIAL [4] 1..400 (1 unit = 0.1 second);

CC0: 15
Timer 0: 30
Timer 1: 1
Timers 2..4: 30
Determines the time from trunk seizure, until the first digit is dialed by the system.
See the notes below for system action during specific circumstances.
• If an 8DTD, 8DRCM-2, 8DRCM or 8DRCF card is installed in a Coral
system, the detection of dial tone overrides this timer.
• If a ground start trunk (tip to ground) is not returned by the time-out,
the trunk is considered NOT READY and is released.
• On E&M continuous trunks defined as “Wink Start”, this is the delay
from a received “Wink” signal until digits are transmitted.
• On E&M continuous trunks defined as “Immediate Start”, this is the
delay from seizure until digits are transmitted.
• On E&M continuous trunks defined as “Stop/Go”, this is the delay
between the time a “Go” signal is received until the digits are
transmitted.
8-8
SECOND_DIAL_TONE 1..60..600 (1 unit = 0.1 second);

[5] Eu3: 120
Presets the system waiting time for a second dial tone before sending additional
digits. Second dial tone is applied, for example, when E6 (#6) code is programmed
into Speed Dial numbers (see page 8-5), or ROUTING and SDT parameters in
Trunk Groups.
 Notes:
• If an 8DTD, 8DRCM-2, 8DRCM, 8DRCF or U-RMI/U-MR Office card
is installed in the Coral system, this time is added to TONE_DELAY in
General Trunk Timers (see page 8-5).
• Relevant to Eu3 systems only: After dialing 07 (the first two digits of
outside numbers) the system automatically stops sending digits and
waits for a dial tone from the CO, before sending the remaining
digits.The wait period for sending the remaining digits is defined
through the SECOND DIAL TONE parameter, above. (However, TONE_
DELAY is not added to the wait time.) If the dial tone is not detected
before time-out, the system disconnects the call. This parameter
operates in a manner similar to the E6 key when programmed into
Speed Dial Numbers.
8-9
MFR Card Database ç CDB,6 [0,1,2,6]
The Multi-Frequency Receiver (MFR) is a shared service card that allows defining
the MFR resource card parameters. Field numbers appear in square brackets ([ ]).
 Notes:
• An MFR card must be installed in order to utilize the MFC in the
following cards and countries: 30T-DOD: CC1; 30T/E-DID/DOD and
4/8BID: Eu1; 30T/M-DID/DOD: CC2,CC3,CC5,CC6,Eu4,Eu6; 8DID /S-Z:
CC3,CC4.
• Programming the MFR card must be accompanied by defining MFC_
ACK [3] (page 8-4).
FROM/TO CARD_DB# 0
Enter the card database table number. Currently only zero (0) is allowed, which is
assigned to all MFR cards.
MIN_ON [0] 0..40..2540 ms (in 10 ms increments)

Minimum On Recognition Time defines the minimum time in which the MFR must
detect an active MFC tone sent by the far end (see sketch below) in order to
recognize an MFC tone. If the tone is shorter than the defined time, the signal is not
identified as an MFC tone.
Figure 8-1
ON PERIOD OFF PERIOD

MFR Card Database CDB,6 [0,1,2,6]
MFC TONE MFC TONE

VERIFIED ON VERIFIED OFF
MIN_ON MIN_OFF
MIN_OFF [1] 0..40..2540 ms (in 10 ms increments)

Minimum Off Recognition Time defines the minimum time allowed between the
end of the MFC tone and MFR verification (see sketch above). The Coral will stop
sounding the ACK Tone only after recognizing a silence period within the MIN_
OFF duration.
Transfers the updated data immediately to the card database. This parameter is used
only in Update Mode.
8-10
General Trunk Definitions ç TRK,0 [0,2,1,0,0,0]
Trunk Definitions are used to specify the general trunk definitions per trunk dial
number. The general definition of a Direct Inward Dial (DID) trunk does not
include all fields, although field position numbers do not change. Additional
programming is required for each trunk type. Field Numbers appear in square
brackets ([ ]).
 In this table, a  sign indicates a field used for DID trunk definition.
FROM/TO DIAL# Any valid trunk dial number; Default: All defined trunks
Enter the required range of trunk dial numbers, FROM the lowest trunk dial
number TO the highest trunk dial number.
DISA [0] 0 (E&M Trunks, Not DISA), 1 (DISA/Immediate), 2 (DISA/Delayed)

Not used for DID trunks
Direct Inward System Access (DISA) determines if a LS/GS trunk is DISA, and
the type (immediate/delay). DISA is active only during a DIL/Night1/Night2 mode
in which the trunk incoming destination is None. Thus, for example, incoming calls
on the trunk may be answered by a station during DAY mode, and DISA during
NIGHT 1. The delay period is defined by the DELAY_DISA [5] (page 8-4) timer in
General Trunk Timers.
The DISA feature can be secured by using a Verified Forced Account Code
General Trunk Definitions TRK,0 [0,2,1,0,0,0]

(VFAC). VFAC can be a programmable code, 4 to 16 digits in length.
 COS [1] 0..Maximum defined in Sizes (see COS on page 4-16)

10
DID trunks: 11
Determines the trunk Class of Service. Each trunk is assigned one COS. A COS
defines a list of features which the trunk user is able to use in which certain features
may be denied.
 TK TIMER [2] 0..4

E&M Trunks: 1
Determines the Trunk Timers table profile (0-4) assigned to the trunk, see Trunk
Timers on page 8-7.
8-11
 MFC[3] Yes/No
Determines whether the trunk signaling type is MFC. Generally, the MFC is used
in the following countries and cards:
30T-DOD: CC1; 30T/E-DID/DOD and 4/8BID: Eu1;
30T/M-DID/DOD: CC2, CC3 , CC5 ,CC6, Eu4,Eu6; 8DID/S-Z: CC3,CC4.
When this parameter is set to Yes, the following TYPE parameter is not displayed.
 TYPE [4] 0 (Pulse), 1 (DTMF), 2 (Mix), 3 (CAMA). See table below.

0: Eu2, E&M Pulsed, TBR, PRI
 Notes:
• In European systems this parameter is not used for BID and 30T/E-DDI
trunks; MFC is used instead.
• For 4TWL trunk card version 1.02 and lower, set this parameter to 1
(DTMF). Pulse dialing on the 4TWL requires card version 1.03 or
higher.
Determines the type of trunk signaling method used for dialing.
Type Description
0 For Dial Pulses (rotary trunks)

1 For DTMF trunks
2 Used to block DTMF tones on outgoing rotary trunks (i.e. the caller
sends DTMF tones.)
3 Relevant only for 4T, 4T-PF, 4T-C, 8T,8T-PF, 8T-C or 4TEM cards.
Used to define the trunk as a CAMA trunk, which is used for
emergency 911 dialing. This enables the trunk to send MF tones to

the destinations and is used to send ANI on LS and E&M trunks.
When an E&M trunk is defined as CAMA (this requires Feature
Authorization, see E911 (page 3-23)), the E&M line signaling protocol is
automatically set to Wink by the system (see page 8-87).
 I/C_ONLY [6] Yes/No

DID: Yes;
BID: No
Determines whether a trunk is defined as Incoming Only, thereby prohibiting
outgoing calls. This parameter cannot be changed on DID trunks (except in
European ALS70 and BID systems).
When creating a larger Group Call from more than one Group Call, back to back,
set this parameter to Yes to define the trunks as incoming only.
(Attendant modifiable)
8-12
O/G_ONLY [7] Yes/No; Not used for DID trunks

Determines whether a trunk is defined as Outgoing Only, thereby prohibiting
incoming call recognition. (Attendant modifiable)
When creating a larger Group Call from more than one Group Call, back to back,
set this parameter to Yes for the trunk included in the Public Library used for
establishing a connection between the Group Calls.
 When the Trunk TYPE [4] above is defined as 3-CAMA, then this parameter
should be defined as Y to prevent the trunk from receiving calls and thus
keeping it available for outgoing emergency calls.
 BUSY_OUT [8] Yes/No

Determines whether a trunk is “busied out”, thereby prohibiting outgoing calls and
maintaining a constant seizure to block incoming calls. (Attendant modifiable)

Indicates whether a trunk prohibits outgoing calls because the Auto Guard test
failed (locks trunk dial tone). When set to Yes, the trunk is blocked for outgoing
calls. A technician can only enter No in order to release a locked trunk. (Attendant
modifiable)
HOT_IMMED [10] Yes/No

Not used for DID/PRI trunks

Determines whether a trunk automatically and immediately connects-out upon
trunk seizure. (Attendant modifiable)
HOT_DELAY [11] Yes/No

Not used for DID/PRI trunks
Determines whether a trunk is automatically connected if digits are not dialed
within the Outgoing First Digit timer, see 1st_DIGIT [10] on page 9-3. (Attendant
modifiable)
DROP_NO_DIAL [12] Yes/No

Eu1,Eu2,GID: Yes
Determines whether a trunk is released by the system if digits are not dialed within
the defined Outgoing First Digit timer, see 1st_DIGIT [10] on page 9-3. (Attendant
modifiable)
8-13
RSRVD_TO [13] None,

Any valid station or boss group dial number
Determines whether a trunk is reserved, and identifies the station or group for
which the trunk is reserved, for outgoing calls. (Attendant modifiable)
D.I.L. [14] None

LS/GS Default: First System Keyset (Attendant)
Any valid station, boss/hunt group, public library, Bell/UNA, Modem,

DVMS MSG/Port, group call, Wait-Que, Network #

Direct In Line determines whether incoming calls on the trunk are directed to a
destination during DAY mode, and also identifies the destination. (Attendant
modifiable)
NIGHT1 [15] None

Any valid station, boss/hunt group, public library, Bell/UNA, Modem, DVMS
MSG/Port, group call, Wait-Que, Network #

Determines whether incoming calls on the trunk are directed to a destination during
NIGHT1 mode, and also identifies the destination. (Attendant modifiable)
NIGHT2 [16] None

Any valid station, boss/hunt group, public library, Bell/UNA, Modem, DVMS
MSG/Port, group call, Wait-Que, Network #

Determines whether incoming calls on the trunk are directed to a destination during
NIGHT2 mode, and also identifies the destination. (Attendant modifiable)
8-14
DISC_SUPER [17] Yes/No

Loop Start: No
NonDID: Yes
 Notes:
• Relevant for Loop Start trunks.
• Also relevant in European systems for ALS70-Non DID trunks.
• When the Trunk TYPE [4] above is defined as 3-CAMA, then this
parameter should be defined as Y.
Disconnect Supervision determines if system call processing logic can expect
disconnect supervision from the Central Office. If N is entered, the trunk is
considered a Port Without Disconnect Supervision (PWDS), and when connected
to another PWDS, will recall to the incomplete calls destination periodically to
determine if a conversation is still in progress between the two ports. N should be
entered if disconnect supervision is not provided, or not consistently provided on
the trunk. Should disconnect supervision appear on the trunk, an N in this entry will
inhibit its recognition by the system. If Y is entered, supervision must be provided
by the Central Office.
 0 = IMM, 0 (Immediate Start)/1 (Wink Start or Delay Start)

1 = Wink/Delayed [18]
 Notes:
0 = IMM/BID, • Relevant for DID trunks.
1=Wink/Delayed [18] • In European systems set this parameter to zero (0) for BID and
European Systems only 30T/E-DDI trunks.

Determines whether the signaling (handshaking) protocol of the trunk is Immediate
Start, Wink Start or Delay Start.
Entering 1 allows the trunk to be either Wink Start or Delay Start.
DND_WP [19] Yes/No; Not used for DID trunks
 Relevant only for analog trunks.

Defines whether this trunk can prevent other stations from whisper paging to one
side of a conversation on an engaged trunk. Enter Yes to enable the trunk to prevent
Whisper pages by entering the applicable feature code.
To enable this feature, define DND_WP [26] on page 7-10 in COS,0 to Y.
8-15
RECEIVE_SPKR_ Yes/No
STATUS [20]
When set to Yes, this parameter enables the far-end user over a trunk to receive an
alert tone indicating that the second conversing party (called or calling party) is in
Speaker Mode (activated for handsfree or group conversation).
This feature is only relevant when the second party is a keyset (FlexSet, FlexSet-IP,
DKT, T207M, T208M, T207M/NP, T208M/BL) station user.
IP_FAX_ENABLED Yes/No
[21]

PRI Trunks Only
Defines whether the MG/MRC module should try and detect Fax tones from this
trunk.
The Media Gateway Module is sensitive to certain sounds or tones that can
mistakenly be acknowledged as Facsimile or Modem tones and thereby disrupt
voice calls.
The Coral main software can be configured to indicate, in each call setup, if there
is a chance of Fax/Modem signals by checking if all the call participants have
Fax/Modem abilities. This feature is only relevant for calls using IP components
that ultimately reach a Media Gateway module, such as IP Network trunks, or when
one of the parties is a SIP station or a SIP Trunk. The parameter in irrelevant for
MGCP stations.
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l v91536*/
IP_MODEM_ENABLED Yes/No
[22]
Defines whether the MG/MRC module should try and detect modem Tones from
this trunk.
voice calls.
one of the parties is an IP station.
BLOCK_REORDER_ Yes/No
TONE(VM) [23]
Disable the reorder tone sent to the trunk that continues to seize the 2-way call at
disconnect when the other party has already onhooked.
 Tip: Set this parameter to Yes for trunks ports servicing only Voicemail.
8-16
OUT_OF_SERVICE_  Yes/No (Display Only)

FAR_END [24]
 PRI Trunks Only
This parameter indicates whether the Far End port is out of service (Yes) or not
(No).
The trunk port is out of service when the technician places the trunk in Busy Out
state.
KEEP_RTP_AFTER_ Yes/No
3WAY [25]
This parameter is relevant when a trunk port participates in a 3WAY call where at
least one of the parties is a NET-IP trunk. When Y (Yes) is selected, RTP is
maintained after one of the parties exits the 3WAY call. When N (No) is selected
for all of the ports engaged in a 3WAY call, RTP is discontinued after one of the
parties exits the 3WAY call, and is then re-established for the remaining two
parties.
Figure 8-2 NET- IP trunk NET- IP trunk
A A
3WAY 2WAY
B C C
Any port Any port Any port

RTP during 3WAY call RTP maintained after
a participant left 3WAY call
 Only when the parameter for all three ports that participate in a 3WAY
call is defined as No, will RTP be discontinued (regardless of the branch
under which it is defined). See:
KEEP_RTP_AFTER_3WAY [43] (page 9-18) (SLT Definition (SLT) and
KEEP_RTP_AFTER_3WAY [85] (page 9-70) (Keyset Definition branch (KEY).
8-17
Trunk Group Definition ç TGDEF [0,5,1,0]
Trunk Group Definition defines the features that are relevant for all the trunks
listed in the selected Trunk Group. The features and trunks group members are
defined in this section.
After the trunk group parameters are entered into the database and before they are
updated, the following message is displayed:
ADD/REMOVE MEMBERS MAY EFFECT CLA EVENTS. RESTART CLA IF
NEEDED.
For CAMA (E911) Trunks:
It is strongly recommended to create a trunk group with only CAMA trunks
all having the same parameter definitions for DTD Override (Yes) and
Dialing Method (Enblock) to enable Emergency 911 service.
 The first trunk group in the system is trunk group index 0. The default
Numbering Plan defines this Trunk Group’s dial number as 9 (or 0 for Eu0,
Eu1, Eu2 and Eu9 countries).
FROM/TO Any valid trunk group access code number; Default: All
TK_GRP#
Enter the required range of trunk group dial numbers; FROM the lowest trunk
group number TO the highest trunk group number.
 The first trunk group in the system is trunk group index 0. The default
Numbering Plan defines this Trunk Group’s dial number as 9 (or 0 for Eu0,
Eu1, Eu2 and Eu9 countries).
Trunk Group Definition TGDEF [0,5,1,0]
NAME:
SHORT(5) Maximum 5 ASCII characters, R (Remove for BLANK)
Defines the trunk group’s short name (up to 5 alphanumeric characters), which
appears on keysets equipped with a display when the group is accessed for an
outgoing call. A group name defined as BLANK does not appear on the keyset
Names on page 2-10.
FULL (16) Maximum 16 ASCII characters, R (Remove for BLANK)

Defines the trunk group’s full name (up to 16 alphanumeric characters), which
appears on keysets equipped with a display when the group is accessed for an
outgoing call. A group name defined as BLANK does not appear on the keyset
Names on page 2-10.
8-18
IP_ZONE 0..max defined in Sizes for ZONE (page 4-19) or R for (--) None
Define the IP Zone to be used for this IP Network Trunk group. Only one Zone can
be defined per Trunk Group. (Note: IP_NET [45] (page 5-48) dial numbers may be
defined only in QSIG Trunk groups).
The following warning is issued:
All NET IP calls in this group will disconnect upon
Update!
ISDN ONLY Yes/No

IPG, PRI23, PRI30
and
 Only extensions with ISDN Only COS (see page 7-30) can require ISDN
Only trunk lines.
BRI (4/8TBR) only
Ensures that the ISDN call is routed along ISDN lines for the entire connection
(end to end). When this parameter is set to Y, only stations defined by their COS as
ISDN ONLY can dial out on an ISDN Only trunk.
Only ISDN trunks may be entered as members in this trunk group.
If the Network (Public or Private) routes the call over a non-ISDN service, a
message is sent back to the Coral and the call is terminated.
QSIG Yes/No
 PRI, BRI, IP_Net, and SIP trunks only.

Determines whether or not the trunk group is a QSIG trunk group.
For PRI/BRI trunks, check that the trunk protocol is defined as QSIG in
PROTOCOL_ID (see page 26-15).

For IP_NET (also known as NET_IP) trunks, the trunk protocol is automatically
defined as QSIG. Other QSIG parameters for these trunks may be defined in the
QSIG Definitions section of IP: NET beginning on page 29-80.
 When changing trunk group types from QSIG to non-QSIG, first remove all
the trunks from the trunk group and then change from Y to N or vice
versa.
DTMF_DIGITS_ Yes/No
BEFORE_ANSWER

Relevant only for Network Calls at the outgoing Gateway PINX.
This parameter relates to the PINX connected to an external application (usually a
Voicemail system) or a CO trunk. The technician must check the external
application to determine whether the Coral should send the DTMF digits before or
after an answer signal is received from the external application or CO trunk.
8-19
ANI_SCREENING_ U (Unavailable), S (Site LDN), T (Transparent), O (Omit)

SEND
This parameter screens the Calling Party Number (CPN) of transit calls at the
Gateway PINX and determines its format before being sent to its destination in the
public Network.
This parameter similarly screens the Connected Line Identification Presentation
(COLP) of transit calls sent to the public Network.
CPN x
CPN x
Network QSIG screened
CPN y ANI
Coral Screen ISDN (PRI, BRI) Public
Gateway CPN y
Send Network screened
PINX (Filter)
Public ISDN CPN z
CPN z Network screened
Enter U if no CPN is to be sent.

The UNAVAILABLE information element is sent instead.
Enter S to send the Site LDN number defined for the Routing Access (see SITE LDN
[5] on page 15-7) of the outgoing gateway associated with the call1. (Route: LCR, 1)
Entering T causes the CPN to pass through the Gateway PINX without being
screened2.
Enter O to prevent sending the ANI (on the trunk group members) to the called
party. Use this option to prevent call rejection by the CO when receiving an ANI
that was not requested.
For example: BRI trunks on a 4TBR line are marked with 8 CPNs. The CO
expects to find one of these numbers in the CPN field. When a Coral station uses
one of these trunks, the resulting ANI includes the station number, thus creating an
unidentifiable ANI which is not accepted by the CO.
SEARCH TYPE 0 (Circular), 1 (Terminal)

Trunk Group Index 0: Default = 0
Determines whether outgoing trunk group access always selects the lowest
member number available (terminal), or selects the next available member
following the member last selected in the group (circular).
1. The Site_LDN # (if defined) is sent regardless of the SITE LDN ALL CALLS (Route: LCR, 1)
definition.
2. When the NPID of the received CPN is Private, then the UNAVAILABLE IE is sent.
8-20
DTD OVERRIDE No (Follow originating port COS), Yes (Disregard originating port COS)
• Irrelevant for ISDN (IPG, PRI, BRI) trunks.
• For CAMA trunks, set this parameter to Yes. (It is strongly
recommended to create a separate trunk group for CAMA trunks with
this definition group wide.)
Override Dial Tone Detector determines whether outgoing access to a member of
the group allows dialing on the trunk before dial tone is detected, regardless of the
originating port Class of Service requirement to wait for dial tone before dialing.
Dial tone detection (entering an N) requires an 8DTD, 8DRCM-2, 8DRCM or
8DRCF card to be installed in the system (see DTD [70] on page 7-21).
OGR_OVERRIDE Yes/No
Defines whether a station defined as Outgoing Restricted is allowed to use this
specific trunk group to make outgoing trunk calls, overriding the restriction.
For example: hotel guests who have already checked out can still access Voicemail
connected over an E&M trunk.
COLLECT_TONE_ Yes/No
OVERRIDE?

This parameter is relevant only if COLLECT_CALL_REJECT_TONE [40] on
page 9-17 (SLT) or 9-65 (KEY) is set to YES.
Defines whether or not an incoming collect call arriving via this trunk group to a
station may override the collect call restriction, if defined for the station.
This is relevant when a Coral user needs permission to accept collect calls from a
specific destination only.

SDT Yes/No
EU only
When Second Dial Tone is set to Y, the Coral checks the first digits of an outgoing
call (see Table 8-1 on page 8-22). When a match is found, the Coral sends only
those matched first digits. The system then waits for dial tone from the CO at which
point the rest of the digits of the external number are out-pulsed.
When an 8DTD, 8DRCM-2, 8DRCM or 8DRCF card (with dial tone detectors) is
installed, the outgoing call will be disconnected when the second dial tone is not
detected. However, when the relevant Dial Tone card is not installed, the rest of the
digits are released after a system-wide time-out (see SECOND_DIAL_TONE
[5] (page 8-9) in Trunk Timers).
8-21
PAGING Yes/No
This feature applies to groups of E&M trunks connected to the paging system
known as ESPA protocol (European Selective Paging manufacturers Association)
 Notes:
• This feature is mutually exclusive with SDT, above. If Yes is selected for
PAGING, then SDT must be set to No.
• When selected, the E&M trunk must be defined as DTMF (see page
8-12) or IMMEDIATE (see page 8-87)
Table 8-1: Chart of Second Dial Tones - Europe*
Outpulsing Digits # of digits be-

st nd rd th th
fore SDT is
1 2 3 4 5 checked
Eu0 (Netherlands)
0 6 -- -- -- 2
0 9 -- -- -- 2
0 7 any digit -- -- 3
0 1,2,3,4,5 or 8 0 -- -- 3
0 1,2,3,4 or 5 3 -- -- 3
0 1,3,4,5 or 8 5 -- -- 3
0 3 or 5 8 -- -- 3
0 1 1,6,7 or 8 any digit any digit 5
0 2 1,2,5 or 9 any digit any digit 5
0 3 2 or 4 any digit any digit 5

0 4 1,2,4,7 or 9 any digit any digit 5
0 5 1,2,4,6,7 or 9 any digit any digit 5
0 8 3 or 8 any digit any digit 5
Eu1 (Belgium)
0 0 -- -- -- 2
Eu3 (Spain)
0 7 -- -- -- 2
* Second Dial Tone is not relevant in Eu2 countries.
8-22
TK_TK_CONNECT_ Yes/No
OVERRIDE

When the trunk group includes ISDN trunks defined as NETWORK_SIDE,
this parameter must be set to YES.
Trunk to Trunk Connect Override allows or denies a trunk group member to
connect to another trunk within the same group, as well as within another group.
This parameter is relevant only if TK_TO_TK_CONNECT [0] on page 6-8 is set to No,
and TK_TK_XFER_OVERRIDE [67] on page 7-20 is set to Yes.
BCCOS 0..63
ISDN only
Defines which Bearer Capability COS is applied for trunks defined as ISDN when
dialing in or out of the Coral System. See BCCOS Control beginning on page 26-5.
ROUTING ACCESS Routing Access number (see NPL,0,5,37) or None (80)
 Irrelevant when DIALING METHOD (below) is set to Overlap.

Determines the Routing Access, if any, to be applied to each outgoing trunk
belonging to the trunk group, when the trunk is not accessed by dialing the Routing
Access number.
See Chapter 15 for Routing Access information.
LAR_MAX_ 0..2..10
ASYNCHRONOUS_
Defines the maximum number of Look Ahead Routing (LAR) attempts
FAILS
(undertaken within a specific trunk group) to re-route a call to the trunk next in
order to the one that has failed with an identifiable cause pointing to asynchronous

failure. When the allowed maximum is reached, the connection fails and the system
returns a failure cause message to the originating Coral (see Look Ahead Routing
Triggers beginning on page 15-32).
When the route to the terminating Coral is split into a few legs by having transit
Corals along the routing path, the failure cause message is sent to the originating
Coral for that particular leg.
8-23
LAR SYSTEM Cost/Performance

PREFERENCE
Define the Look Ahead Routing (LAR) system Preference by either Cost or
(COST/
Performance.
PERFORMANCE)
Selecting Performance causes LAR to block the failed trunk for a longer period.
This reduces the number of re-attempts to re-route the call to that trunk, thus
providing a faster response for the user.
Selecting Cost causes LAR to block the failed trunk for a shorter period. This
makes re-attempts to re-route the call to that trunk more frequent, thus increasing
the probability of establishing a connection over the most economical route.
LAR_TRIGGERS_SET 0..3
Defines the Look Ahead Routing (LAR) Trigger set for this Trunk Group.
A LAR trigger set groups together ISDN/QSIG causes launching LAR. Each set
pertains to a specific network, e.g. Public Network, Private QSIG Network, IP
Network or Analog Network. (see NAME (16) [1] (page 15-34) in the Look Ahead
Routing Triggers beginning on page 15-32).
When an asynchronous failure occurs over a call sent via that trunk group the call
is rerouted in the specified network.
TRANSIT ALI 0..3200 (or maximum as defined in SIZ, see Chapter 4) or

R (Remove for no Alternate), None
This parameter provides the Alternate Line ID (i.e. caller number information) for
incoming tandem (transit) calls that do not possess Caller ID information by
marking the call with an ALI index number. The index number given in this
parameter (i.e., 0 to 3200) is defined with Caller ID info in the ISDN/ALI tables in
the Alternate Line ID (page 26-9) branch (ROOT,5,3).
The Caller ID information is displayed at the terminating end and can be used for
call recording systems.
8-24
DIALING METHOD O (Overlap)/E (Enblock)
 For CAMA trunks, set this parameter to Enblock.

Defines which dialing method is used for the related trunk group.
When ENBLOCK is chosen, the Coral sends all digits in a packet.
When OVERLAP is chosen, the trunk is seized first and then the digits are sent.
To set this parameter to Overlap, define the following PRI signaling parameters for
the related trunk group in the ISDN Card Signaling branch (DTDB,4) as follows:
• PROTOCOL_ID [6] (page 26-15) should not be defined as QSIG
• SENDING_COMPLETE for Outgoing Calls [13] (page 26-16) to No.
• SENDING_COMPLETE for Enblock Incoming calls [14] (page 26-16) to No.
QSIG trunk groups should set this parameter to Enblock.
DIAL IN FILTER Table 8-3 on page 8-38
 For incoming calls only.

The filter modifies digits received from the trunks in the group to match the system
numbering plan. Digits may be added, removed (i.e. ignored) or conditionally
removed when they match a specific pattern.
The system numbering plan can only accept a range of one to eight digits. If the
result of a filter directs a call to a station, no additional digits can follow the station
number. A filter can channel an incoming DID/E&M call to an outbound tie line or
CO trunk. Such a filter contains the Public Library dial number to access the
desired trunk or trunk group, not the trunk or trunk group dial number. Digits may
appear in the filter after the Public Library dial number.

DIAL IN/CALLER OUT 0..to Max defined in SIZ (see OFFSET_FILTER (page 4-15);
OFFSET R (Remove for None)
Defines which offset filter is relevant for E&M or DID members when dialing into
the Coral system (see page 8-42). Trunks dialing into the system are interpreted as
the specification of the filter (see Offset Filters beginning on page 8-42).
In the absence of an extended filter (NONE), default, each digit is separately
verified according to the numbering plan without filtering.
When an offset filter is defined, the incoming digits are modified to match the
system numbering plan. Applies also to outgoing calls by reverse defining the ANI.
If DIAL IN FILTER above is defined, then the incoming number is first filtered by
that Dial In filter and then filtered according to this offset filter.
8-25
CALLER # OUT Delete Digits using “Rn”: where n is the number of digits to be removed
FILTER from the beginning of the ANI
 For outgoing calls only.

Defines the filter used to define the outgoing ANI (Automatic Number
Identification). This is the number that is displayed to the network.
If DIAL IN/CALLER OUT OFFSET above is defined, then the outgoing number (ANI)
is first filtered by that offset filter and then by this Caller # Out Filter.
INCOMING ANI Yes/No

FILTERS
 The following two sets of parameters First Incoming ANI Filters: and
Second Incoming ANI Filters: are displayed and can be defined only when
this parameter is set to Yes.
Set this parameter to Yes to enable the system to modify the incoming ANI for calls
on this trunk based on the caller type.
A maximum of two different types of modified ANI may be defined for different
combinations of caller number types (Unknown, International, National, or
Subscriber) where the filters for the first set (First Incoming ANI Filters:) are applied
before the second set (Second Incoming ANI Filters:).
When this parameter is set to No, no filters are applied to the incoming ANI.
The modified ANI can be used for:
• Displays on Keysets, and, SLTs with CID displays
• SMDR Reports
• Reports to external applications (e.g.: billing, CRM or a Directory application)
• Outgoing Calls.
8-26
First Incoming The following parameters define the ANI modification required based on the type
ANI Filters: of the incoming number.
A second, additional, ANI modification can be defined by defining the parameters
for Second Incoming ANI Filters:, below, however, this set of filters are applied to
the ANI before the Second Set.
FILTER None (no filter applied)

See Table below.
The filter modifies the incoming ANI by adding, removing (i.e. ignoring) and/or
conditionally removing part or all of the ANI digits. This filter is applied before the
next, OFFSET filter.
To alter the ANI for a range of stations, use the OFFSET below.
Table 8-2: Incoming ANI Filters - Range of Operation
Filter Operation Example Explanation
ADD/INSERT Digit string from trunk: 156 Defines the required digits to be added to
DIGITS Desired digit string: 4156 the beginning of the ANI call number.
Filter entry: 4
DELETE Digit string from trunk:123456 Enclose the digit pattern that should be
MATCHING DIGITS Desired digit string: 456 matched and deleted between square
(Conditional Extraction) brackets ([ ]).
Filter entry: [123]
DELETE DIGITS Digit string from trunk:396354 Define the number of digits to be deleted
Desired digit string: 354 from the beginning of the ANI call
number by entering R followed by the
Filter entry: R3 quantity of digits to delete.
If more than 9 digits must be removed
using the Rn (where “n” = any digit from

0 to 9, inclusive), or if a delay (Dn, where
“n” = any digit from 0 to 9, inclusive), if
more than 9 seconds is required, enter
the instruction as often as necessary to
accomplish the task. For example, to
delete 12 digits, enter R9R3 (9+3=12); to
add a 30 second delay enter: D9D9D9D3
(9+9+9+3=30).
OFFSET None (no offset filter applied)

0 to Max as defined in SIZ for OFFSET_FILTER (page 4-15),
R (Remove for None)
Enter the index number of the offset filter element used. Each offset filter is defined
in Offset Filters beginning on page 8-42. This offset filter is applied to the ANI only
after the above FILTER is applied.
Offset filters cannot be applied on ANI numbers longer than 8 digits.
8-27
Relevant Define the type/s of ANI number to which the above filters are to be applied.
Number Types: More than one type of number may be defined as Yes.
UNKNOWN Yes/No
Set this parameter to Yes to apply the two filters (FILTER and OFFSET), defined
above, for incoming ANI call numbers of an UNKNOWN type.
INTERNATIONAL Yes/No
 Relevant only for ISDN ANI type numbers.

above, for incoming ANI call numbers of an INTERNATIONAL type.
NATIONAL Yes/No

above, for incoming ANI call numbers of a NATIONAL type.
SUBSCRIBER Yes/No

above, for incoming ANI call numbers of a SUBSCRIBER type.
8-28
Second This is the second set of parameters that define the ANI call number modification
Incoming ANI required, based on the type of incoming number. This set of filters is applied on the
Filters: ANI number only after the first set is applied.
FILTER None (no filter applied)

See Table 8-2 on page 8-27 above
This filter modifies the incoming ANI by adding, removing (i.e. ignoring) and/or
conditionally removing part or all of the ANI digits.
 To alter the ANI for a range of stations, use the OFFSET below.
OFFSET None (no offset filter applied)

0 to Max as defined in SIZ for OFFSET_FILTER (page 4-15),
R (Remove for None)
Enter the index number of the offset filter element used. Each offset filter is defined
in Offset Filters beginning on page 8-42. This filter is applied to the ANI number
only after the above FILTER is applied.
 Offset filters cannot be applied on ANI numbers longer than 8 digits.

8-29
Relevant Define the type/s of ANI number to which the above filters are to be applied.
Number Types: More than one type of number may be defined as Yes.
UNKNOWN Yes/No
above, for incoming ANI call numbers of an UNKNOWN type.
INTERNATIONAL Yes/No

above, for incoming ANI call numbers of an INTERNATIONAL type.
NATIONAL Yes/No
above, for incoming ANI call numbers of a NATIONAL type.
SUBSCRIBER Yes/No
above, for incoming ANI call numbers of a SUBSCRIBER type.
8-30
METERING_UNIT_ 0.00 to 65000.99 (for systems with decimal definitions for cents)
CHARGE 0 to 65000 (for systems defining only integers)
N (number of pulses is displayed, instead of cost)
 Irrelevant when DIALING METHOD (page 8-25) is set to Overlap.

Defines the cost per one metering pulse received from the CO for an outgoing call.
The total price of a call is the price per pulse multiplied by the number of pulses.
Entry can be made with a decimal point for cents or without decimal point for
integer number.
INCOMING_CLI_ Yes/No
REQUEST
Determines if a request should be made to the CO for Calling Line Identification
(CLI) on an incoming call.
Enables the display of incoming caller identification (CID or CLI) to telephone
with a display unit. During ringing, the incoming caller identification display
allows the called party to decide whether to answer the call or not. The CLI number
will remain on display for the call duration, both in the CAP and the SMDR listing.
The incoming CLI can be received via 4/8T-CID Loop-Start analog trunk cards and
via MFC trunks. Likewise in DTMF signaling, only from E&M continuous with
Wink Start trunks.
 Notes:
• To display the incoming call (CLI) in the SMDR listing, ON_LINE
EXTENDED_SMDR_INFORMATION [7] on page 14-4 (SMDR SMDR
Control branch (SMDR,0 [3,2,0])) must be defined.
• This parameter is also defined in the DID/E&M Groups (page 8-36).
• The CLI feature for analog Loop-Start / Ground-Start trunk requires

Authorization for Caller ID.
• The CLI display feature for SLT requires a 8/16/24SLS (software
version 3.xx or higher) or 8/24SA peripheral card, iDSP card,
Authorization for SLT-CID, and an FSK compatible display unit
installed on the SLT port.
• In the Coral IPx Office systems the CLI display feature for SLT requires
a U-RMI Office or U-MR Office card, Authorization for SLT-CID, and
an FSK compatible display unit installed on the SLT port.
• In the IPx 500 systems the CLI display feature for SLT requires an
MSBipx Hardware Issue-0200X1000 or higher, Authorization for
SLT-CID, and an FSK compatible display unit installed on the SLT port.
• In the CDRS 200E systems the CLI display feature for SLT requires
When a particular trunk is defined in both the above tables during an incoming call,
the CLI parameter in the DID/E&M table is the determining factor.
8-31
SEND_ANI_USING_ Yes/No
DTMF/MFC

Not Relevant for QSIG groups or when ANI_SCREENING_SEND, above, is
set to Omit.
 When SDT is defined for the trunk group (Holland-Eu0, Belgium-Eu1 or

Spain-Eu3), set this parameter to No.
Enables sending the ANI over E&M trunks using DTMF. The trunks must use the
E&M protocol that supports ANI transmission.
The ANI is determined by the Coral as a combination of the caller ID and a prefix.
The caller number is based on either the station number or the CPN for incoming
trunk calls. The ANI is defined in OUTGOING ANI (page 15-7).
The offset filters described above apply to this ANI as well.
Set this parameter to Yes if the called PBX or CO expects ANI digits, otherwise,
set this parameter to No.
Tip: When connected in a network with another Coral, one Coral can send ANI if
the INCOMING_CLI_REQUEST (page 8-31) of the relevant trunk group in the called
Coral is set to Yes.
NUMBER OF DIGITS 1..51/R (Remove for None)/None

EXPECTED
Determines the number of digits that are expected to be received by the Coral from
the CO through the incoming trunk. When None (default) is selected, the received
digits are analyzed when the interdigit time-out is over. However, when a number
between 1 and 51 is selected, the received digits are immediately analyzed after all
the expected digits are detected. If the call is on a PRI trunk in ENBLOCK mode,
the parameter need not be defined since the number of digits is sent in the packet.
DISABLE_DTMF_ Yes/No
SUPERVSION
Defines whether DTMF resources will be used to process the incoming digits over
this trunk line. When this parameter is set to Yes, DTMF receivers are not used.
Set this parameter to No if this trunk group will be used to serve applications where
Coral DTMF analysis is required, such as external Voicemail., Answering
Machines and FlexiCall.
Set this parameter to Yes only if this trunk group will be used exclusively to serve
applications where Coral DTMF analysis is not required.
JOIN GROUP CALL IN Yes/No

MUTE
Set this parameter to No for the outgoing trunk that is used for establishing the
connection between Group Calls thus creating a large Group call.
This accommodates the expanded Group Call by providing an open bi-directional
channel between two adjacent Group Calls. See Example (page 10-29) in Groups.
8-32
MEM # Default: Trunk Group Index 0: All LS/GS trunks in ascending order,
equipped at First Initialization,
Default for all Other Groups: None
Range: Any valid outgoing trunk dial numbers;
Max: 95 members
 In European systems all ALS70 and GID trunks are (by default) also
members of trunk group index 0.
Identifies the dial number of each trunk, in ascending order, assigned to the group.
Each trunk can be a member of only one trunk group. A trunk need not be a
member of any group, however outgoing access to a trunk cannot be denied by
Class of Service unless the trunk is a member of a trunk group.
Entering R removes the member currently displayed from the group and
decrements the MEM# of following group members, filling the void left by the
removed member.
 Always remove a trunk from a trunk group before the trunk dial number is
removed from the numbering plan.
 Adding/Removing members may affect CLA events. Restart CLA if needed.'

Entering A allows a new trunk to be added in the existing order, incrementing the
MEM# of the member currently displayed and all that follow, shifting existing
members out of the way to make room for the added trunk.
Always enter a trunk to a similar type trunk group, such as a QSIG trunk to a QSIG
trunk group.
Attempting to enter a QSIG trunk to a non-QSIG trunk group causes the following
error message:

TRUNK GROUP IS NOT QSIG.
Likewise, attempting to enter a non-QSIG trunk to a QSIG trunk group results in a
similar error message:
ONLY QSIG ALLOWED.
8-33
Alternate Route ç ROUT [0,5,1,1]
Alternate Route is used to determine the outgoing call route when all trunks of a
selected trunk group are busy. While not intended to take the place of true Routing
Access (which requires additional authorization), alternate routing is a simple
method of accommodating trunk group overflow conditions.
Each Alternate Route entry specifies a primary trunk group, one or more alternate
trunk groups or public library numbers, and the time of day the alternate route is
available. Each trunk group can have only one alternate route available at any given
time of day. If more than one alternate route is entered, the time period that each
alternate route is available must not overlap or conflict with the time period of any
other entry.
Alternate Route is a type of “cascade route”. If Trunk Group A alternate routes to
Trunk Group B, and Trunk Group B alternate routes to Trunk Group C, when Trunk
Groups A and B are both busy, an outgoing call attempt to Trunk Group A selects
a trunk from Trunk Group C if one is available.
Alternate Route programming is not necessary when routing access is implemented
in the system.
A trunk group is limited to 96 trunks. To add additional trunk groups, the Alternate
Route branch can be utilized to route incoming calls via different trunks (in
addition to outgoing calls).
SELECT TK GRP # Any valid trunk group dial number;

Default: 1st Trunk Group (Index # 0)
Determines the dial number of the primary trunk group. (See Trunk Group
Definition beginning on page 8-18.)
Alternate Route ROUT [0,5,1,1]
GRP#/LIB# Any valid trunk group or public library dial number

Determines the dial number of the alternate trunk group or public library (speed
call) dial number to process an outgoing call if the primary trunk group has no
available trunks.
FROM TIME 00:00..23:59 (None)

Determines the time the alternate (secondary) route becomes available. Time is
entered in a 24-hour format (00=midnight, 12=noon; 01=1 AM, 13=1 PM; see
Programming and Entering Time Units on page 2-6) as HH:MM.
8-34
TILL TIME 00:00..23:59 (None)

Determines the end of the time period the alternate (secondary) route becomes
available. Time is entered in 24-hour format (00=midnight, 12=noon; 01=1 AM,
13=1 PM; see Programming and Entering Time Units on page 2-6) as HH:MM. For
example, for 1:13PM, enter 13:13.
Alternate Route ROUT [0,5,1,1]
8-35
DID/E&M Groups ç DIDG [0,5,6]
DID/E&M Groups establish from one to four unique Direct Inward Dial (DID) and
E&M trunk groups. Each group has an individual digit filter, allowing incoming
digits from the trunks within a specific group to be modified thus matching the
system numbering plan. A DID/E&M trunk may be a member of a DID/E&M
group consisting of one or more DID/E&M trunks, however a trunk can be a
member of only one DID/E&M group.
If a DID/E&M line belongs to a DID/E&M group, the number of digits received
by the Coral is defined when the group was assigned its identifying numbers. The
number assigned to a group can consist of between one and ten (1 - 10) digits. Once
the number is assigned it is fixed unless changed through the filter. By using the
filter the DID/E&M number can be changed to suit various system requirements by
making it compatible to the system numbering plan. The number pattern is verified
and acted on by the system only after all digits are received as defined.
If a DID/E&M line does not belong to a DID/E&M group, then each digit of the
numbering plan is separately verified for acceptance. Only after all the digits have
passed and the numbering plan is correct, communication continues without
filtering.
Legal DID group members may be defined through the following types of cards:
• 4TWL • 8DID • 4GID • 30T/E
• 8GID • 4BID • 30T
• 8BID • 30T/M
DID/E&M Groups DIDG [0,5,6]
8-36
FROM 0..3
TO 0..3
DID/E&M_GRP#
Enter the required range of DID/E&M group index numbers FROM the lowest
DID/E&M group index number TO the highest DID/E&M group index number.
NAME:
SHORT(5) Maximum: 5 ASCII characters, R (Remove for BLANK)
Defines the trunk group’s short name (up to 5 alphanumeric characters) and full
name (up to 16 alphanumeric characters), associated with the trunk group. This
entry is used only for programming purposes. Incoming trunk calls display the
individual trunk name, not this group name. See General Rules for Entering Names
on page 2-10.
FULL (16) Maximum: 16 ASCII characters, R (Remove for BLANK)

Defines the trunk group’s full name (up to 16 alphanumeric characters), associated
with the trunk group. This entry is used only for programming purposes. Incoming
trunk calls display the individual trunk name, not this group name. See General
Rules for Entering Names on page 2-10.
FILTER See Table 8-3 below

The filter modifies digits received from the trunks in the group to match the system
number. A filter can channel an incoming DID/E&M call to an outbound tie line or
CO trunk. Such a filter contains the Public Library dial number to access the

desired trunk or group, not the trunk or trunk group dial number. Digits may appear
in the filter after the Public Library dial number. The table below lists and explains
the various filters.
This filter is relevant only when INCOMING_OFFSET_FILTER (below) is defined as
NONE.
8-37
When more than one group of stations or when the capability to address a
fragmented numbering plan is required, use the INCOMING_OFFSET_FILTER listed
below.
Table 8-3: DID/E&M Group Filters - Range of Operation
Filter Operation Example Explanation
ADD/INSERT Digit string from trunk: 156 Enter the required digits at the position in the
DIGITS Desired digit string: 4156 filter where the insertion is desired. Additional
digits are inserted before any remaining digits
are received from the trunk. Digits cannot be
Filter entry: 4 added to the end of a digit string received
from the trunk.
DELETE Digit string from trunk:123456 Enclose the digit pattern that should be
MATCHING DIGITS Desired digit string: 456 matched and deleted between square
(Conditional brackets ([ ]). Digits will only be deleted if the
Extraction) pattern appears starting with the first digit
Filter entry: [123] received from the trunk. The received pattern
must match the pattern within the brackets,
exactly. Entering D in the digit string matches
any digit received in that position.
DELETE DIGITS Digit string from trunk:396354 A specific number of digits may be deleted
Desired digit string: 354 within the string by entering R followed by
the quantity of digits to delete. Digits are
always deleted from a received string starting
Filter entry: R3 with the first digit received. Digits in the
middle of the received string may not be
deleted.
INSERT DELAY Digit string from trunk: 1234 Incoming calls routed from the system to
Desired digit string: other switching systems in a network may
6000,14 second delay,1234 require delays (pauses) during the digit string
transmission. Delays are entered into the
filter string at any position by entering D
Filter entry: *6000D9D5 followed by a single digit (1-9). If more than 9
digits must be removed using the Rn (where

“n” = any digit from 0 to 9, inclusive), or if a
delay (Dn, where “n” = any digit from 0 to 9,
inclusive), if more than 9 seconds is required,
enter the instruction as often as necessary to
accomplish the task. For example, to delete
12 digits, enter R9R3 (9+3=12); to add a 30
second delay enter: D9D9D9D3
(9+9+9+3=30).
These digits denote seconds (one through
nine seconds). Numbers can be entered one
after another in order to increase the delay
period beyond 9 seconds.
* 6000 is a Public Library num
8-38
INCOMING_OFFSET_ None (previous filter applied)

FILTER 0 to Max as defined in SIZ for OFFSET_FILTER (page 4-15), R (Remove for
None)
Defines which offset filter element is relevant for DID/E&M members when
dialing into the Coral (see Offset Filters beginning on page 8-42).
DID and E&M members dialing into the system are interpreted as the specification
of the extended filter.
In the absence of an extended filter, the previous filter is applied.
The extended filter can be used for installing a fragmented numbering plan with the
capability to dial to several groups of stations with different prefixes. The previous
filter supports only one area.
#_DIGITS_EXPCTD 1..51, R (Remove for None)

Determines the number of digits that are expected to be received from the Central
Office through the incoming trunk. When None (default) is selected, the received
digits are analyzed when the interdigit time-out is over. However, when numbers 1
through 51 are selected, the received digits are immediately analyzed after all the
expected digits are detected.
INCOMING_CLI_ Yes/No
REQUEST
Determines if a request should be made to the CO for Calling Line Identification
(CLI) on an incoming call.
Enables the display of incoming caller identification (CID or CLI) to telephone
with a display unit. During (Loop-Start analog trunk) ringing, the incoming caller
identification display allows the called party to decide whether to answer the call
or not. The CLI number will remain on display for the call duration, both in the
CAP and the SMDR listing.

The incoming CLI can be received via 4/8T-CID trunk cards and via MFC trunks.
Likewise in DTMF signaling, only from E&M continuous with Wink Start trunks.
 Notes:
• This parameter is also defined in the DID/E&M Groups (page 8-36) branch
(DIDG [0,5,6]).
• The CLI feature for analog Loop-Start / Ground-Start trunk requires
Authorization for Caller ID.
8-39
• For display of the incoming call (CLI) in the SMDR listing, the
“On-Line Extended SMDR Information” parameter on the SMDR SMDR
Control (page 14-2) branch (SMDR,0 [3,2,0]) must be defined.
• This parameter is also defined in Trunk Group Definition beginning on
page 8-18.
When a particular trunk is defined in both the above tables during an incoming call,
the CLI parameter in the DID/E&M Groups (page 8-36) branch (DIDG [0,5,6]) is the
determining factor.
PREFIX: FROM/TO 0..9, number of digits defined in #_DIGITS_EXPCTD, R (Remove)

Eu1 only (BID, 30T/E)
This option is relevant when #_DIGITS_EXPCTD, above, equals 1 through 8. The
maximum number of prefixes allowed per DID group is five (5), for each of five
(5) different Numbering Plan ranges. This represents the five prefix ranges
permitted by the Central Office for dialing internal stations.
COLLECT_TONE_ Yes/No
OVERRIDE?
This parameter is relevant only if
COLLECT_CALL_REJECT_TONE [40] (page 9-17) (SLT Definition branch (SLT
[or IST or ROOT,0,2,1,1])) or
COLLECT_CALL_REJECT_TONE [75] (page 9-65) (Keyset Definition branch
(KEY [or EKT or 0,2,1,2,0])) is set to YES.
Defines whether or not an incoming collect call arriving via this trunk group to a
station may override the collect call restriction, if defined for the station.
This is relevant when a Coral user needs permission to accept collect calls from a
specific destination only.
8-40
MEM # Any valid DID or E&M trunk dial number up to 255 members, None
Identifies the dial number of the DID or E&M trunk in the DID/E&M group. The
prompt appears each time an entry is made and [ENTER] is pressed.
If an attempt is made to define a member that is not a DID or E&M trunk number
this error message appears:
NOT DID/E&M TK#.
A trunk can be a member of only a single DID/E&M group. If an attempt is made
to define a trunk that is already defined, the following message appears:
 To insert a DID or E&M trunk dial number into an existing list, press
ALREADY DEFINED IN GRP#?
[CR] at the trunk dial number which is to follow the inserted trunk. Enter
A and the new trunk dial number. In order to remove a trunk from the
group, enter [R]. All trunks must be removed from a group before the
group can be deleted.
8-41
Offset Filters ç ROOT,0,0,7

In addition to the filter provided for each trunk group, the Coral allows defining a
maximum of 250 Offset Filters with a fixed number of elements per offset filter,
(see OFFSET_FILTER on page 4-15).
The Offset Filter can be used for installing a fragmented numbering plan with the
capability to dial several groups of stations with different prefixes.
The Offset Filter is used for mapping the Numbering Plan ranges of the Coral
System to that of the Network. The offset filter works in conjunction with any filter
previously defined for a trunk or trunk group.
For an incoming DID call, the regular filter (defined in the trunk group) is applied
first and then the offset filter.
An outgoing call can also use the offset filter. In this instance, the offset filter is
applied before the regular filter, but for ANI only.
It is possible to choose only an offset filter, or a regular filter, or both, or no filter
at all.
Each element is programmed to filter a specific range of received dial numbers to
match the system numbering plan. The number of elements allowed, system-wide,
is defined in N_FILTER_ELEMENTS PER OFFSET FILTER (page 4-16) in the Sizes
Definition branch (SIZ).
The following examples demonstrate a few ways in which the Offset filters
redefine numbers received in the Coral.
Offset Filter #1
Element # Received Number Number in Coral
Element #1 FROM: 356-6000 2000

Offset Filters ROOT,0,0,7
TO: 356-6199 2199
Element #2 FROM: 326-4500 4500
TO: 326-4599 4599
Element #3 FROM: 8-536-2500 84002500
TO: 8-536-2599 84002599
SELECT OFFSET 0 to Max as defined in SIZ for OFFSET_FILTER (page 4-15)

FILTER#
Enter the number of the required offset filter.
8-42
Once this filter is selected, the following option menu becomes available:
Option Description
0 - UPDATE Allows updating the existing filter element.
1 - DISPLAY Displays the elements for the selected filter.
2 - ADD Adds an element to the selected filter.

Up to N_FILTER_ELEMENTS PER OFFSET
FILTER (page 4-16) (defined in SIZ) elements per
offset filter exist.
3 - REMOVE Removes a specific element from the selected filter.
7 - ERASE Erases all elements in the selected filter.
FROM/TO RECEIVED# Up to eight digits, 0 to 9, *, #

Enter the first and last numbers in a range of dial numbers as received from the CO.
FROM DIAL# Up to eight digits, 0 to 9, *, #

Enter the first number in a range of Coral internal dial numbers that is to be dialed
when the FROM/TO RECEIVED# above is received.
The To Dial # end range is automatically applied.
ERROR MESSAGES The following error messages may be received when programming Offset Filters:
Error Message Cause
OFFSET FILTER NOT DEFINED Received when attempting to display

elements in a filter that has no
previous elements defined.
WRONG OFFSET FILTER UPDATE Received when attempting to update

elements of a filter that has no
Offset Filters ROOT,0,0,7

previous elements defined, or the
wrong range of numbers has been
entered.
WRONG OFFSET FILTER REMOVE Received when attempting to remove

elements from a filter that has no
entered.
WRONG OFFSET FILTER ADD Received when attempting to add

elements to a filter that has no
entered.
8-43
Power Fail Trunk Definition ç TRK,4 [0,2,1,0,0,4]
Power Fail Trunk Definition establishes the database for power fail (PF) trunks.
Power fail programming applies only to LS/GS (Loop Start or Ground Start) analog
trunks. Power fail trunks are standard Ground Start or Loop Start trunks connected
to a Power Fail trunk card, along with any one of the following cards:
• 4T cards with four (4) PF ports (CKT# 0, 1, 2, and 3):
4TPF, 4T/S-PF-ES, 4TMR/S-12PF-ES, 4T/S PF-G, 4TMR/S-12/16PF,
4TMR/S-12/16PF/S, 4TMR-PF-G, 4TMR/S-50/16-PF-G
4TMR-PFipx, 4TMR/S-12/16-PF-Gipx, 4ALS
4T-C, 4T-Cipx, 4T Office, 4T-CID, 4T-CIDipx and 4T-CID Office
• 8T cards with four (4) PF ports (CKT# 2, 3, 4, and 5):
8T-C, 8T-CID, 8T/S PF-G, 8TPF, 8ALS,
8T-Cipx, 8T-CIDipx, 8T Office, 8T-CID Office
Each LS/GS trunk port may have one station dial number assigned to it, along with
any one of the following cards:
• 2/4/8SK (Cards Discontinued)
• CDRS/CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
• station card circuit, plus a SLT
• station card circuit, plus a power fail EKT301-PF or EKT321-PF. (Discontinued)
Power Fail Trunk Definition TRK,4 [0,2,1,0,0,4]
• Power fail EKT301-PF or EKT321-PF (Discontinued) provide voice only

communication when in power fail mode, (the display is blank and
programmed buttons do not function).
Should power return to normal while a station is in conversation, the call is not
disconnected since the station is defined as busy to the system.
Install a power fail station near the Attendant position when possible.
 In European systems 4ALS and 8ALS trunks have the Power Fail option
when defined as Loop Start or NonDID type trunks. Incoming trunk seize
must be accompanied with a ring current, see CHECK_RING for the
relevant Port Database.
! Only SLTs or EKT301/321-PF sets can be power failure stations.

FlexSets, DKTs and DSTs cannot be power failure stations.
8-44
FROM/TO DIAL# Any valid LS/GS analog trunk dial numbers/All LS/GS analog trunks
 Digital trunks cannot be used.

Enter the required range of Loop Start/Ground Start analog trunks; FROM the
lowest LS/GS analog trunk number TO the highest LS/GS analog trunk number.
DEST Any valid station SLT or EKT301/321-PF dial number/None

Determines the power fail station system dial number that is connected during
power failure to the trunk.
Power Fail Trunk Definition TRK,4 [0,2,1,0,0,4]
8-45
LS/GS (Loop/Ground Start) Trunks ç TRK,2 [0,2,1,0,0,2]
LOOP START/GROUND START/ALS70-LS/NON-DID/DDO/NON-DDI TRUNKS

The following information applies to ground start, loop start, ALS70-LS, non-DID,
DDO and non-DDI trunks only (including 4TWL cards). The following parameters
are used in addition to the General Trunk Definitions, as described in this chapter.
Field Numbers appear in square brackets ([ ]).
FROM/TO DIAL # Any valid LS/GS trunk number // All defined LS/GS trunks
Enter the required range of trunk numbers, FROM the lowest TO the highest.
LS/GS [0] 0 (Loop Start)/1(Ground Start)

4T/8T Trunks only CC0: 1
Determines whether the trunk loop signaling is loop start (LS) or ground start (GS).
This entry must match the entry in the Card Database in this chapter, and option
strapping on the card (see Peripheral and Service cards Installation Manual).
• 4T, 4TMR, 4TMR-PF, 4TPF, 8TPF
• 4T-C, 8T-C, 4T-CID, 8T-CID
• 4T-Cipx, 8T-Cipx, 4T-CIDipx, 8T-CIDipx
• 4T Office, 8T Office, 4T-CID Office, 8T-CID Office (LS only)
ANSWER [1] Yes/No

LS/GS (Loop/Ground Start) Trunks TRK,2 [0,2,1,0,0,2]
Digital Trunks only

Determines whether an outgoing call should expect an answer from the Central
Office. If Yes is selected the system waits for a CO answer for the duration of the
wait time defined in ANSWER_DELAY [9] (page 8-5). When the time expires before
answer is detected, the system automatically disconnects the trunk. A user
connected to the trunk cannot transfer calls before answer is accepted.
DISC_SUPER [2] Yes/No

Loop Start and Eu0 nonDID: Yes
Eu0 (NonDDI) only
This option is the same as DISC SUPER in General Trunk Definitions (see page
8-15). Programming one Disconnect Supervision will directly affect the other. It is
recommended to program this option through General Trunk Definitions beginning
on page 8-11.
Determines whether the system call processing logic can expect disconnect
supervision from the Central Office. If N is entered, the trunk is considered a Port
Without Disconnect Supervision (PWDS), and when connected to another PWDS,
will recall to the incomplete calls destination periodically to determine if a
conversation is still in progress between the 2 ports. Enter N if disconnect
supervision is not provided, or not consistently provided on incoming calls to the
8-46
trunk. Should disconnect supervision appear on the trunk, an N in this entry will
inhibit its recognition by the system.
Entering Y requires Central Office supervision.
DISC_SUPER_I/C [3] Yes/No

Ground Start only
Incoming Disconnect Supervision determines whether the system call processing
logic can expect disconnect supervision from the Central Office. If N is entered, the
trunk is considered a Port Without Disconnect Supervision (PWDS). When
connected to another PWDS, the connection periodically recalls the incomplete
calls destination to determine if a conversation is still in progress between the 2
ports. N should be entered if disconnect supervision is not provided, or is not
consistently provided on incoming calls to the trunk. Should disconnect
supervision appear on the trunk, an N in this entry does not inhibit its recognition
by the system. If Y is entered, supervision must be provided by the Central Office.
This entry is independent of the DISC SUPER O/G entry.
DISC_SUPER_O/G [4] Yes/No

Ground Start only
Outgoing Disconnect Supervision is similar to, but independent of DISC SUPER I/C,
above. This parameter determines whether the system call processing logic can
expect disconnect supervision from the CO during outgoing calls. If N is entered,
the trunk is considered a Port Without Disconnect Supervision (PWDS) when the
trunk is seized to make an outgoing call. Should disconnect supervision appear on
the trunk, a N in this entry will not inhibit its recognition by the system. If Y is
entered, supervision must be provided by the CO.

POLAR RVRS
UPON:
ANSWER [5] Yes/No
Polarity Reverse Upon Answer determines whether the first polarity reverse after
outgoing seizure is interpreted as answer supervision. If Y is entered, ANSWER_
DELAY [9] on page 8-5 (General Trunk Timers) is active, and battery reverse must
occur before the trunk can be held or transferred.
ONHK [6] Yes/No

Polarity Reverse Upon Onhook determines whether a polarity reverse is interpreted
as disconnect supervision. If Y is entered and POLAR RVRS UPON ANSWER is
Y, the first polarity reverse outgoing seizure is interpreted as an answer, and the
following reverse is interpreted as a disconnect. If POLAR RVRS UPON
ANSWER is N, the first polarity reverse after seizure is interpreted as a disconnect.
Regardless of this entry, an open circuit from the Central Office is interpreted as a
disconnect.
8-47
ACTIVE_CALL_ C (Camp)/B (Busy)

CAMP_BUSY [7]
Determines how the system relates to incoming trunk calls (trunk-to-station) to a
busy station not defined as Multi-Appearance (see M.A. definition for SLTs on
page 9-14, for Keysets on page 9-42).
Enter B (Busy) so that the calling party hears a busy tone when the destination
station is busy.
Enter C (Camp-on offhook/Call Waiting/Call Offer) to treat the line as a regular
LS/GS trunk and to have the Coral relate to the call as an incoming call from the
CO. In this case, if the internal called station is busy, the call automatically
camps-on to the busy station or enters as a second call in the multi-appearance. In
this case (camp-on offhook or multi appearance), the calling party hears a second
ringback tone.
CALLER_ID [8] Yes/No

SAU Requirement
Defines whether this analog line can provide the Caller’s ID. When this
information is available, the Caller’s Name/Number can be displayed on the station
user set with a display unit.
Define this parameter to Yes when the trunk card is 4/8T-CID, 4/8T-CIDipx,
4/8T-CID Office, (or when the external trunk CID hardware used to implement this
feature is installed in parallel to the analog line).
CALLER_ID_BOX_ 1..64/N (None)

LINE# [9]

For 4/8T-CID, 4/8T-CIDipx and 4/8T-CID Office cards as well as for

Coral Teleport FXO units, define this parameter as None.
The CID module is an offspring board that can be mounted on 4/8T-CID,
4/8T-CIDipx and 4/8T-CID Office cards to support the Caller ID on
analog trunks, eliminating the external Caller ID box and the RMI,
8DRCM-2, 8DRCM approach.
This parameter is relevant only when external trunk hardware is used to implement
Caller ID.
Defines the physical hardware external box number to which this analog trunk line
is connected. The hardware, an external box, is physically connected in parallel to
the analog trunk, and to the 8DRCM-2, 8DRCM or RMI card (not KB0 and not
8DRCF) via a RS-232 serial interface port (like the PI Terminal Device). The
hardware runs an application to read the Caller ID information thus enabling Caller
ID functions on the station connected via analog trunks.
Each “box” contains 8 ports and a maximum of 8 boxes can be connected to one
system. If this number is already defined for another trunk, then the following
message is displayed:
ALREADY_DEFINED_BY_DIAL#; CONFIRM Y/N?
8-48
The Caller ID information is sent to a Coral Caller ID (CID) box port on a RS-232
serial interface port terminal. The terminal should be defined in TERM as CID (see
page 17-22).
For more information refer to Engineering Note -120EN9700, Caller ID On
Analog Trunks.
8-49
4T/8T LGS Port Database ç TRUNK,1 [0,2,1,0,1]
The Trunk Port Database allows programming the trunk port database tables for
Loop Start and Ground Start trunk ports connected to 4T or 8T card types.
There are 6 Trunk Port Databases (0-5), one of which is assigned to each Loop Start
and Ground Start trunk port (see Port List - Chapter 6). Field numbers appear in
square brackets ([ ]).
FROM: 0..5
TO: 0..5
PORT_DB#
Enter the required range of 4T/8T Port Database tables, FROM the lowest 4T/8T
Port Database table number TO the highest 4T/8T Port Database table number.
CO_DISC [0] 250..1000..2500 ms(in 50 ms increments)

Central Office Disconnect determines the minimum period that a disconnect signal
from a trunk must remain before the system recognizes the signal as a valid call
disconnect, thereby releasing the trunk.
SUSP_SZE [1] 50..80..500 ms(in 10 ms increments);

Eu0: 200 ms
Eu3: 300 ms
4T/8T LGS Port Database TRUNK,1 [0,2,1,0,1]
Suspect Seize determines the period that an incoming call signal must continuously
remain at a trunk port before the signal is recognized as a possible seize from an
outside party. SUSP_SZE results in prohibiting outgoing calls thus preventing a
glare condition, or double seizure (see Figure 8-3 on page 8-51).
CO_BLOCK [2] 50..110..300 ms (in 10 ms increments)

Ground Start Trunks
Determines the timing of a blocking signal received from the Central Office
only
(ground or ring), which is the minimum silent duration until the system interprets
the signal as a block signal. The timer applies only to trunks defined as Ground
Start with Ring (see 4T/8T Card Database beginning on page 8-52). In a CO block
state, the trunk is considered busy, thus prohibiting an outgoing trunk seizure. The
system awaits ringing indicating an incoming call.
8-50
MIN_SZE [3] 50..300..500 ms (in 10 ms increments);

Eu0: 330
Eu3: 320
Minimum Seize time determines the additional period that an incoming call signal
must continuously remain at a trunk port before the signal is recognized as an
incoming call. In other words, incoming recognition time is measured as SUSP_
SZE + MIN_SZE (see Figure 8-3 on page 8-51).
 MIN_SZE time must be less than SUSP_OFFHK [7] (page 6-3).

SEND_TO_CARD? [4] Yes/No

Transfers the updated database immediately to the trunk cards. Regardless of entry,
routine diagnostics periodically resend the port database to the cards, including any
update made. This parameter is used only in the Update Mode.
Figure 8-3.
INCOMING CALL
Incoming Trunk Call
Seize Timers
MINIMUM SEIZE
IDLE
time
4T/8T LGS Port Database TRUNK,1 [0,2,1,0,1]

SUSPECT SEIZE OFFHOOK
8-51
4T/8T Card Database ç TKDB

4T/8T Card Database establishes the card database for the following Loop
Start/Ground Start (LGS) trunk cards:
• 4TWL
The system allows for a maximum total of four 4T/8T card database combinations
(0-3). The Coral system makes no logical distinction among a 4T, 4TMR and a
4TPF card, and likewise 8T and 8TPF cards are considered equivalent. Where a
parameter (option) is available for only the 4T/4TPF/4T-C or 8T/8TPF/8T-C card,
this is noted. Field numbers appear in square brackets ([ ]).
FROM: 0..3
TO: 0..3
CARD_DB#
Enter the required range of Card Database tables; FROM the lowest Card Database
table number TO the highest Card Database table number.
4T/8T? [0] 4T/8T

Determines the database card type. If 4T is defined, after a power failure the system
returns to 8T. Card type 4T should be used only when the system is using 4T cards
exclusively. When 4T is defined the system skips the last four circuits (CKT 4-7).
Enter 4T for 4T, 4TMR, 4TPF, 4TPF, 4T-C, 4T-CID and 4TMR-PF cards.
Enter 8T for 8T, 8TPF, 8T-C and 8T-CID cards.
4T/8T Card Database TKDB
LS_RING_PAUS [1] 1..5..12 seconds

7: Eu8
Loop Start Ring Pause determines the minimum period that ring generator must
remain absent during an incoming call before the system terminates an incoming
call indication. This timer applies only to trunks which are defined as Loop Start
(LS) in the Trunk LS/GS Port Definition and LS/GS Trunk Card database. The
entry should be at least one second greater than the normal interval between ring
bursts from the Central Office.
8-52
GS_RING_PAUS [2] 1..12 seconds

Ground Start Ring Pause determines the minimum period that earth ground must
remain absent from the tip conductor during an incoming call before the system
terminates an incoming call indication. This timer applies only to trunks defined as
Ground Start (GS) in the Trunk LS/GS Port Definition and LS/GS Trunk Card
database.
O/G BREAK_TIME [3] 18..60..90 ms (in 3 ms increments);

67: CC2, Eu3, Eu6, Eu8;
65: Eu1
Outgoing Break Time determines the period that the loop current is interrupted
during a rotary (pulse) dial cycle from a rotary dialing trunk port during an
outgoing call.
O/G MAKE_TIME [4] 18..40..90 ms (in 3 ms increments);

Eu3 and CC2: 33
Outgoing Make Time determines the period that loop current is restored during a
rotary (pulse) dial cycle from a rotary dialing trunk port during an outgoing call.
O/G INTERDGT_T [5] 200..800..2250 ms (in 10 ms increments)

Eu: 2100 ms
CC2: 320 ms
Outgoing Rotary Interdigit Time-Out determines the minimum period that loop
current will be restored between digits being rotary (pulse) dialed from a rotary
dialing trunk port during an outgoing call (for DTMF trunk tones see DTMF_
TONE beginning on page 6-5 in Feature Timers).
GS_DISCONNECT [6] NO RANGE

800 ms: Set by manufacturer
DO NOT CHANGE THE DEFAULT.
This is the period of time after a ground start trunk is disconnected in which no
outgoing calls may be generated along the trunk. Incoming calls are received
during this period, however.
8-53
METER (4TMR):
f0 [7] 0(16kHz), 1(12kHz), 2(50Hz)
Eu0: 2
Eu8: 0
 Not used for CC0 (USA) systems

Identifies the frequency sent by the CO to define a meter pulse. This option is
relevant for 4TMR and 4TMR-PF cards only. The frequency must match the
frequency type printed under the card name on the front panel.
f0 ACCURACY [8] 1..3..10 inclusive 1 unit = ±1%**
 Not used for CC0 (USA) systems.

Identifies the accuracy of the meter pulse frequency sent by the CO. This option is
relevant for 4TMR and 4TMR-PF cards only. This feature is not used when f0 [7],
above, equals 50Hz (2).
METER_AFTER_ Yes/No;
DISCONNECT [9] Yes: CC2, Eu2, Eu3
 DISC_SUPER [17] on page 8-15, [TRK,0] must be set to YES in order to

activate this feature.
Determines if metering pulses after a trunk call is disconnected are relevant for call
charging (see also METER_BEFORE_CONNECT [11] on page 6-10 in SFE.)
METER_TIME_ 50..12750 ms (in 50 ms increments);

AFTER_DISCONNECT Eu2, Eu3: 3000
[10]

This parameter is relevant only when the previous METER_AFTER_
DISCONNECT parameter is set to Yes.
Defines the system waiting time for more pulses before a disconnect is actually
performed.
8-54
COLLECT CALLS 1..254 (1 unit = 10 ms)

BLOCK [11,12,13]
CC3 only
 The 4T/8T card software version must be 14.36 or higher.
Three parameters are used to implement a blocking protocol for incoming collect
calls.
Parameter Name Default

COLLECT_BLOCK_T1 [11] 15 units (150ms)
In an incoming call, if the person called is restricted by COS to accept collect calls,
the Coral signals the CO accordingly. The signaling is implemented by
disconnecting and connecting the line according to the following time intervals:
• Line closed for T1 interval
• Line opened for T2 interval
• Line permanently closed
If the incoming call is a collect call, the CO will disconnect the line after
identification of the above pulse sequence.
8-55
CKT 0-7 (CIRCUITS 0-7 DEFINITION)

A-type G (Ground Start)/L (Loop Start);
CC0: G
(Table 8-4 describes the circuit defaults.)
! If A-(GS/LS) is changed, all established calls on all 4T/8T trunk cards are
dropped, and all 4T/8T cards re initialize.
Determines whether the CKT (trunk port) on all cards with this database are
Ground Start or Loop Start. The system default is determined by the COUNTRY
field in the Installation entry (see Chapter 3-Installation). If 0 (USA/North
America) is defined as the COUNTRY code, the default for all CKTs is Ground
Start; in other countries the default is Loop Start. Check card to confirm strapping
matches the software entry. This entry must match LS/GS (TRK, 2) (see page 8-46).
B-LS pts Yes/No

Loop Start Proceed to Send determines whether the trunk is muted for 750
milliseconds after outgoing seizure to protect the system from Central Office
trunks which momentarily interrupt battery following seizure.
8-56
C-gs with ring Yes (Loop Start or Ground Start w/Ring)/No (Ground Start w/o Ring);
The table below presents the various circuit defaults
Ground Start with Ring determines whether the trunk recognizes, and waits for,
ringing as an incoming call signal. If N is entered, a Ground Start trunk interprets
a ground on the tip conductor as an incoming call. If Y is entered, a Ground Start
trunk interprets a ground on the tip conductor as a CO Block condition and waits
for ring generator to appear before reporting an incoming call.
Table 8-4: Circuit Default Table
A-type B-type C-type

Loop Start = LS LS PTS (Y/N) GS WITH RING
Ground Start = GS (Y/N)
Country Code
CKT # CC0 All

0 GS [14] LS No [15] Yes [16]
1 GS [17] LS No [18] Yes [19]
2 GS [20] LS No [21] Yes [22]
3 GS [23] LS No [24] Yes [25]
4* GS [26] LS No [27] Yes [28]
5* GS [29] LS No [30] Yes [31]
6* GS [32] LS No [33] Yes [34]
7* GS [35] LS No [36] Yes [37]
* 8T, 8TPF, 8T-C, 8T-CID (ipx, Office) cards only

[38]
Transfers the updated card database immediately to the trunk cards. Regardless of
including any update made. This parameter is used only in the Update Mode.
8-57
4TEM - E&M Continuous
Details for the E&M Continuous are found on the following pages:
E&M Continuous Timers.................................................................... 8-59
4TEM (E&M Continuous) Card Database ......................................... 8-62
4TEM - E&M Continuous TKDB
8-58
E&M Continuous Timers ç TK.T,2 [0,0,1,2,2]
Each E&M Continuous trunk port (4TEM and 4TEMipx card) is assigned one of
two E&M Continuous Timer tables, see E&M_CONTINUOUS_TIMERS # [1] on page
8-87. These timers determine the disconnect and recognition timers for E&M
continuous trunks only. In addition to General Trunk Timers, E&M timers must be
programmed for all E&M Continuous trunks. Field numbers appear in square
brackets ([ ]).
 These timers are not relevant for E&M Pulsed trunks connected to 4TEMP
card.
FROM 0..1
TO 0..1
E&M_CONT_TIMERS#
Enter the required range of E&M Timer table numbers; FROM the lowest E&M
Timer table number TO the highest E&M Timer table number.
MIN_ONHK [0] 20..40..300 (1 unit = 10 ms)

Determines the minimum period that an “E” lead must remain in an idle state
during a call before the trunk recognizes a far-end disconnect. This timer applies
when far-end is released first.
MIN_ONHK_ACK [1] 10..300 (1 unit = 10 ms)

Determines the minimum period that an “E” lead must remain in an idle state,
awaiting on-hook Acknowledgment, before the trunk recognizes a far-end
E&M Continuous Timers TK.T,2 [0,0,1,2,2]

disconnect. This timer applies when the local PABX releases first and the far-end
release is expected.
MIN_FLASH [2] 1..4..255 (1 unit = 10 ms)

Minimum Calibrated Opening determines the minimum period that an “E” lead
must remain in a high state before the trunk recognizes a far-end calibrated opening
signal.
 Calibrated opening is used for transfer and feature activation, when

H.FLASH ACCEPT [6] on page 8-88 parameter is set to Yes.
8-59
MAX_FLASH [3] 10..75..255 (1 unit = 10 ms)

Maximum Calibrated Opening determines the maximum period that an “E” lead
can remain in a high state before the trunk recognizes a far-end calibrated opening
signal. When the flash exceeds this defined time the system either ignores the
action or reports a disconnect condition, if the minimum on-hook time is not met.
ANS/DISC_PULSE_ 1..10..255 (1 unit = 10 ms)

WIDTH [4]

This pulse can only be activated when ANS/DISC_PULSE_ON_XFER (see
page 8-89) is set to Yes.
Defines the duration of an Answer/Disconnect signal. This signal is normally used
for answering services, such as Voicemail systems.
INCOMING: The following options apply only to incoming E&M trunk calls.
WINK/DELAY [5] 1..2..30 (1 unit = 100 ms)

Determines the minimum period that an “E” lead must remain in an active state
before the trunk recognizes an incoming call indication. This timer only applies to
trunks which are defined as Wink Start or Delay Start (Stop/Go) (see E&M Trunk
Definition beginning on page 8-87).
IMMEDIATE [6] 6..30 (1 unit = 10 ms)

before the trunk recognizes an incoming call indication. This timer only applies to
trunks which are defined as Immediate Start (see E&M Trunk Definition beginning
on page 8-87).
DIGIT_RJCT [7] 3..5..6 (1 unit = 10 ms)

Determines the period following incoming seize acknowledge that any change,
whether “E” lead electrical state or audio dialing signal, is ignored. This timer only
applies to E&M trunks which are defined as Wink Start or Delay Start (Stop/Go)
(see E&M Trunk Definition beginning on page 8-87). This timer is initiated when
“E” lead changes from an active state to an idle state at the end of either a Wink or
Go signal. When this timer expires, incoming dialed digit analysis may commence.
OUTGOING: The following options apply only to outgoing E&M trunk calls.
MAX_WINK/SG [8] NO RANGE

4 (1 unit = 100 ms)
Set by the manufacturer.
Not applicable.
8-60
MIN_ANSWER [9] 10..20..300 (1 unit = 10 ms)

before the system recognizes a far-end answer. After answer supervision is
received, a subsequent return of the “E” lead to an idle state is interpreted as a
far-end disconnect.
8-61
4TEM (E&M Continuous) Card Database ç CDB,3

4TEM Card Database programs the Database for 4TEM and 4TEMipx trunk cards.
There are 3 4TEM Card Databases (0-2), any one of which can be assigned to each
4TEM and 4TEMipx trunk card (see Card List - Chapter 6). Programming is in
addition to general trunk programming.
 Installation note: When using 4TEM/S card, layout B (issue 3 and higher),
the jumper on JMP4 must be set to “C” position.
FROM: 0..2
TO: 0..2
CARD_DB#
Enter the required range of Card Database tables; FROM the lowest Card Database
table number TO the highest Card Database table number.
INCOMING: The following parameters are relevant only for incoming E&M calls.
I/C_MAX_BREAK [0] 30..90..250 ms (in 10 ms increments)

Determines the maximum “Break” time, during a rotary (pulse) dial cycle, for the
station card to recognize the rotary dialed digits (“E” lead remains interrupted).
I/C_MAX_MAKE [1] 30..90..250 ms(in 10 ms increments)

Determines the maximum “Make” time between successive Breaks while a digit is
being rotary (pulse) dialed (“E” lead active). If signaling current remains when this
4TEM (E&M Continuous) Card Database CDB,3
timer expires, the trunk card interprets the restoral as a pause between digits or as
end of digits.
OUTGOING: The following parameters are relevant only to outgoing E&M calls.
O/G_BREAK [2] 20..59..192 ms

Determines the “Break” time during a rotary (pulse) dial cycle from a pulse dialing
E&M trunk, during an outgoing call (M lead is idle).
O/G_MAKE [3] 20..39..192 ms

Determines the “Make” time during a rotary (pulse) dial cycle from a pulse dialing
E&M trunk, during an outgoing call (M lead is active).
8-62
O/G_INTERDGT [4] 100..200..2550 ms

Outgoing Rotary Interdigit Time determines the period that the M lead is active
between rotary (pulse) dialed digits from a rotary dialing E&M trunk, during an
outgoing call. (For DTMF trunk tones, see DTMF_TONE beginning on page 6-5 in
Feature Timers).

Update Mode.
4TEM (E&M Continuous) Card Database CDB,3
8-63
4TEMP (E&M Pulsed)
Details for the E&M Pulsed are found on the following pages:
4TEMP (E&M Pulsed) Port Database................................................ 8-65
4TEMP (E&M Pulsed) Card Database............................................... 8-67
4TEMP (E&M Pulsed) CDB,3
8-64
4TEMP (E&M Pulsed) Port Database ç TRUNK,7

4TEMP Port Database establishes the port database for 4TEMP (Pulsed E&M)
trunk cards. The system allows for a maximum of four database tables
combinations (0-3), one of which is assigned to each Pulsed E&M trunk port (see
Port List - Chapter 6). Field numbers appear in square brackets ([ ]).
 Installation Note: 4TEMP protocol is activated by 4TEM/S card, from

Layout B (issue 3 and later), with the jumper JMP4 set to the “P”
position.
FROM/ 0..3
TO 0..3
PORT_DB#-
Enter the required range of 4TEMP card database tables; FROM the lowest table
number TO the highest table number.
SZE_ACK [0] Yes/No

Determines if a Seize Acknowledge signal is relevant for the trunk port. The signal
specifications are defined in 4TEMP card database.
ANSWER [1] Yes/No

Determines if an Answer supervision signal is relevant for the trunk port. The
Answer signal specifications are defined in 4TEMP card database.
CLEAR [2] P (Clear By Pulse)/C (Clear By Continuance – N/A)
4TEMP (E&M Pulsed) Port Database TRUNK,7

Determines the trunk signaling method used for Calls Clearing. Determines which
type of Clearing signals are relevant for the trunk port. The signal specifications are
defined in the 4TEMP card database.
CLEAR_FWD_ACK [3] Yes/No

Determines if a Clear Forward Acknowledge signal is relevant for the trunk port.
The signals specifications are defined in 4TEMP card database.
CLEAR_BCK_ACK [4] Yes/No

Determines if a Clear Backward Acknowledge signal is relevant for the trunk port.
The signals specifications are defined in 4TEMP card database.
8-65
CO_BLOCK [5] P (Block By Pulsed) N/A

C (Block By Continuance) N/A
N (Block By No_Response)
Determines the trunk signaling method used for Blocking by the far-end.
Determines which type of Block is relevant for the trunk port.
The blocking signal specifications are defined in 4TEMP card database.

Transfer the updated card database immediately to the trunk cards. Regardless of
entry, routine diagnostics periodically send the Card Database to the cards,
including any updates made. This parameter is used only in the Update Mode.
4TEMP (E&M Pulsed) Port Database TRUNK,7
8-66
4TEMP (E&M Pulsed) Card Database ç CDB,7

 Installation Note: 4TEMP protocol is activated by 4TEM/S card, from
Layout B and later (issue 3 and later) with the jumper JMP4 set to the
“P” position.
4TEMP Card Database establishes the card database for 4TEMP (Pulsed E&M)
trunk cards.The system allows for a maximum four database table combinations
(0-3), one of which is assigned to each card (see Card List - Chapter 6). Field
numbers appear in square brackets ([ ]).
The fields in 4TEMP table (card database) are organized in groups of related
parameters. In Update mode, the first field in each group is used as a control switch
to show or skip to the next group. Enter No to skip to the next group of fields, or
when the feature is Not Applicable (N/A) for the current version or country.
FROM: 0..3
TO: 0..3
CARD_DB#
Enter the required range of 4TEMP card database tables; FROM the lowest table
 The following two fields are relevant for all Pulsed E&M trunks.
MIN_FLASH [0] 1..10..200 (1 unit = 10 ms)

Minimum Calibrated Opening Recognition time determines the minimum period
that an “E” lead must remain in an active state before the trunk recognizes a far-end
calibrated opening signal.
Calibrated opening is used for transfer and feature activation, when H.FLASH
4TEMP (E&M Pulsed) Card Database CDB,7

ACCEPT [6] (page 8-88) is set to Yes.
The 4TEMP trunk detects a valid pulse FLASH signal only if the pulse is shorter
than MAX_FLASH defined below and longer than MIN_FLASH defined here.
MAX_FLASH [1] 1..30..250 (1 unit = 10 ms)

Maximum Calibrated Opening Recognition time determines the maximum period
that an “E” lead can remain in an active state for the trunk to recognize a far-end
calibrated opening signal. When the pulse exceeds this defined time the Coral
either ignores the action or reports another condition.
The 4TEMP trunk detects a valid pulse FLASH signal only if the pulse is shorter
than MAX_FLASH defined here and longer than MIN_FLASH defined above.
 The duration of a flash pulse sent by the Coral is defined in Trunk Timers
8-67
BLOCKING BY
PULSE:
<N/A>  The following Blocking By Pulse fields are relevant for trunks, only when
CO_BLOCK [5]=P is defined in its 4TEMP Port Database.
BLOCK_BY_PULSE Yes/No
[2]
Enter “No” to skip to (the next prompt) BLOCK_BY_CONTINUANCE.
Press “Enter” to display BLOCK_BY_PULSE fields.
This parameter is used only in the Update mode.
 When BLOCK_BY_PULSE above is set to Yes, the following six fields are
available:
O/G_BLOCK [3] 1..200 (1 unit = 0.1 second)

Tip: Must be longer than SZE or any other pulse duration.
Block By Pulse, Transmission Duration determines the duration of a Block pulse
(the period that the “M” lead must remain in an active state). This pulse is sent by
the Coral to the far-end in order to block the tie-line.
O/G_OUT_OF_BLOCK 1..200 (1 unit = 0.1 second);

[4] Tip: Must be longer than MAX_CLEAR_BCK [37] (page 8-78) duration.
Out of Block by Pulse, Transmission Duration determines the duration of an
Out-of- Block pulse (the period that the M lead must remain in an active state). This
pulse is sent by the Coral to the far-end in order to release the tie-line.
I/C_MIN_BLOCK [5] 1..200 (1 unit = 0.1 second)

Incoming lower limit recognition time of Block pulse. This pulse is sent by the
far-end to the Coral in order to block the tie-line.
This timer determines the minimum period that an “E” lead must remain in an
active state before the Coral 4TEMP trunk recognizes a far-end Blocking signal.
The 4TEMP trunk detects a valid pulse BLOCK signal only if the pulse is shorter
than I/C_MAX_BLOCK defined below and longer than I/C_MIN_BLOCK
defined here.
8-68
I/C_MAX_BLOCK [6] 1..250 (1 unit = 0.1 second)

Incoming upper limit recognition time of Block pulse. This pulse is sent by the
far-end to the Coral in order to block the tie-line.
This timer determines the maximum period that an “E” lead can remain in an active
state for the Coral 4TEMP trunk to recognize a far-end Blocking signal. When the
signal exceeds this defined time the system either ignores the action or reports
another condition.
The 4TEMP trunk detects a valid pulse BLOCK signal only if the pulse is shorter
than I/C_MAX_BLOCK defined here and longer than I/C_MIN_BLOCK defined
above.
I/C_MIN_OUT_OF_ 1..200 (1 unit = 0.1 second);

BLOCK [7] Tip: Must be longer than MIN_SZE [44] (page 8-79) duration.
Incoming lower limit recognition time of Out_of_Block pulse. This pulse is sent
by the far-end to the Coral in order to release the tie-line.
The timer here determines the minimum period that an “E” lead must remain in an
active state before the Coral 4TEMP trunk recognizes a far-end Out_of_Blocking
signal.
The 4TEMP trunk detects a valid pulse OUT_OF_BLOCK signal only if the pulse
is shorter than I/C_MAX_OUT_OF_BLOCK defined below and longer than I/C_
MIN_OUT_OF_BLOCK defined here.
I/C_MAX_OUT_OF_ 1..250 (1 unit = 0.1 second);

BLOCK [8] Tip: Must be longer than MAX_SZE_ACK [56] (page 8-82) duration and longer
than MAX_CLEAR_FWD [35] (page 8-77) duration.

Incoming upper limit recognition time of Out_of_Block pulse. This pulse is sent
by the far-end to the Coral in order to release the tie-line.
The timer here determines the maximum period that an “E” lead can remain in an
signal.
When the signal exceeds this defined time the system either ignores the action or
reports another condition.
is 1er than I/C_MAX_OUT_OF_BLOCK defined here and longer than I/C_MIN_
OUT_OF_BLOCK defined above.
8-69
BLOCK BY
CONTINUANCE:
<N/A>  The following Blocking By Continuance fields are relevant for trunk, only
when CO_BLOCK [5] (page 8-66) = C is defined in its 4TEMP Port
Database.
BLOCK_BY_ Yes/No
CONTINUANCE [9]
Enter “No” to skip to (the next prompt) BLOCK_BY_NO_RESPONSE.
Press “Enter” to display BLOCK_BY_CONTINUANCE fields.
 When BLOCK_BY_CONTINUANCE above is set to Yes, the following three

fields are available:
• O/G_BLOCK
• I/C_MIN_BLOCK (Minimum Block By Continuance Recognition)
• I/C_MIN_OUT_OF_BLOCK (Minimum Out Of Block By Continuance
Recognition)
O/G_BLOCK [10] 1..200 (1 unit = 0.1 second)

Tip: Must be longer than SZE or any other pulse duration.
Block By Continuance, Minimum Transmission duration determines the minimum
period that the “M” lead must remain in an active state, for the far-end trunk to
recognize a BLOCK indication. This pulse is sent by the Coral to the far-end in
order to block the tie-line.
I/C_MIN_BLOCK [11] 1..200 (1 unit = 0.1 second)

The Minimum Block by Continuance recognition duration determines the

minimum period that an “E” lead must remain in an active state, before the trunk
recognizes a far-end BLOCK indication. This pulse is sent by the far-end to the
Coral in order to block the tie-line.
I/C_MIN_OUT_OF_ 1..200 (1 unit = 0.1 second)

BLOCK [12]
The Minimum Out of Block by Continuance Recognition determines the minimum
period that an “E” lead must remain in an active state, during a blocking state,
before the trunk recognizes a far-end OUT OF BLOCK indication. This pulse is
sent by the far-end to the Coral in order to release the tie-line.
8-70
BLOCK BY NO The following Blocking By No Response fields are relevant for a trunk, only when
RESPONSE: CO_BLOCK [5] (page 8-66) is defined as N in its 4TEMP Port Database.
Examples causing a trunk to enter a blocking condition include:
• Sze Ack is not accepted after Seize was sent for outgoing call.
• Answer is not accepted after digits were sent to the far-end station.
• Clear Ack is not accepted after Clear was sent for ending a call.
• Digits are not accepted after incoming Seize.
BLOCK_BY_NO_ Yes/No
RESPONSE [13]
Enter No to skip to (the next prompt) CLEARING: (page 8-74).
Press Enter to display BLOCK_BY_NO_RESPONSE fields.
 When BLOCK_BY_NO_RESPONSE above is set to Yes, the following

eleven fields are available:
O/G_OUT_OF_ 1..10..200 (1 unit = 0.1 second)
BLOCK_WIDTH [14]
The Out of Block By No Response Pulse, Transmission Duration determines the
duration of an Out-of- Block pulse (the period that the “M” lead must remain in an
active state). This pulse is sent by the Coral to the far-end in order to release the
tie-line.
O/G_OUT_OF_ 1..35..200 (1 unit = 10 ms)

BLOCK_ACK [15]
Out Of Block By No Response, Acknowledge Pulse, Transmission Duration
determines the duration of an Out-of- Block-Acknowledge pulse (the period that
the “M” lead must remain in an active state). This pulse is returned by the Coral to

the far-end after receiving Out-of- Block pulse.
I/C_MIN_OUT_OF_ 1..9..200 (1 unit = 0.1 second)

BLOCK [16]
Minimum Out Of Block By No Response Recognition is the incoming lower limit
recognition time of Out_of_Block pulse. This pulse is sent by the far-end to the
Coral in order to release the tie-line from a blocking state.
signal.
is shorter than I/C_MAX_OUT_OF_BLOCK as defined below and longer than
I/C_MIN_OUT_OF_BLOCK as defined here.
8-71
I/C_MAX_OUT_OF_ 1..16..250 (1 unit = 0.1 second)

BLOCK [17]
Maximum Out Of Block By No Response Recognition is the incoming upper limit
recognition time of OUT_OF_BLOCK pulse. This pulse is sent by the far-end to
the Coral in order to release the tie-line from a blocking state.
active state for the Coral 4TEMP trunk to recognize a far-end Out_of_Blocking
signal.
When the signal exceeds this defined time the system either ignores the action or
reports another condition.
is shorter than I/C_MAX_OUT_OF_BLOCK as defined here and longer than I/C_
MIN_OUT_OF_BLOCK as defined above.
I/C_MIN_OUT_OF_ 1..20..200 (1 unit = 10 ms)

BLOCK_ACK [18]
Minimum Out Of Block By No Response Acknowledge Recognition is the
incoming lower limit recognition time of Out_of_Block_Acknowledge pulse,
which is returned from the far-end to the Coral, after receiving Out_Of_Block
pulse.
active state before the Coral 4TEMP trunk recognizes a far-end Out_of_Blocking_
Acknowledge signal.
The 4TEMP trunk detects a valid pulse OUT_OF_BLOCK_ACKNOWLEDGE
signal only if the pulse is shorter than I/C_MAX_OUT_OF_BLOCK_ACK as
defined below and longer than I/C_MIN_OUT_OF_BLOCK_ACK as defined
here.
I/C_MAX_OUT_OF_ 1..60..250 (1 unit = 10 ms)

BLOCK_ACK [19]
Maximum Out Of Block By No Response Acknowledge Recognition is the
incoming upper limit recognition time of OUT_OF_BLOCK_ACKNOWLEDGE
pulse. This pulse is returned from the far-end to the Coral, after receiving OUT_
OF_BLOCK.
active state for the Coral 4TEMP trunk to recognize a far-end OUT_OF_
BLOCKING_ACKNOWLEDGE signal.
The 4TEMP trunk detects a valid pulse OUT_OF_BLOCK_ACK signal only if the
pulse is shorter than I/C_MAX_OUT_OF_BLOCK_ACK as defined here and
longer than I/C_MIN_OUT_OF_BLOCK_ACK as defined above.
8-72
CYCLE_TIME [20] 1..150..250 (1 unit = 0.1 second)

Wait for Out-of-Block-Acknowledge determines the maximum time that the Coral
will wait for the Out-of- Block_ Acknowledge signal, after O/G-Out-of- Block was
sent. When this time is out without receiving the Acknowledge signal, the Coral
will send another O/G_OUT_OF_ BLOCK pulse (i.e.defines the OFF (pause) time
between successive O/G-OUT-OF- BLOCK pulses.
WAIT_FOR_SZE_ACK 0..50..200 (1 unit = 10 ms)

[21] Tip: Must be longer than MIN_TIME_TO_SZE_ACK [54] (page 8-81)
Determines the maximum time that the Coral will wait for the Seize Acknowledge
signal, after Seize was sent for an outgoing call. When this time is out without
receiving the Seize Acknowledge signal, the Coral will block the line for outgoing
calls.
This timer is relevant for the trunk, only when SZE_ACK [0] (page 8-65) defined as
Yes in its 4TEMP Port Database.
WAIT_FOR_ANSWER 0..200 (1 unit = 0.1 second)

[22] Tip: Must be at least 1.0 second less than ANSWER_DELAY defined in route
TK.T,0 (see page 8-5)
Determines the maximum time that the Coral will wait for the called party's off
hook (answer) signal, after origination of an outgoing call. The Wait for Answer
time is initiated at the expiration of the Outgoing INTERDIGIT timer (defined
later). When this timer is expired without receiving the Answer signal, the Coral
will block the tie-line for outgoing calls.
This timer is relevant for the trunk, only when ANSWER [1] (page 8-65) defined as
Yes in its 4TEMP Port Database.

WAIT_FOR_CLEAR_ 0..200 (1 unit = 0.1 second)

FWD_ACK [23]
Determines the maximum time that the Coral will wait for the Clear Forward
Acknowledge signal, after Clear Forward was sent for ending an outgoing call.
When this time is out without receiving the signal, the Coral will block the tie-line
for outgoing calls.
This timer is relevant for trunk, only when CLEAR_FWD_ACK [3] (page 8-65) is
defined as Yes in its 4TEMP Port Database.
8-73
WAIT_FOR_CLEAR_ 0..50..200 (1 unit = 10 ms)

BCK_ACK [24]
Determines the maximum time that the Coral will wait for the Clear Backward
Acknowledge signal, after Clear Backward was sent for ending an incoming call.
When this time is out without receiving the signal, the Coral will block the tie-line
for outgoing calls. This timer is relevant for trunk, only when CLEAR_BCK_ACK
[4] (page 8-65) is defined as Yes in its 4TEMP Port Database.
CLEARING: Two clearing types are available for call disconnect, one of which is selected to
each trunk in its port database. The following fields are relevant only to Clearing
fields.
 The Clearing signals duration should be different from all other pulses
(except Blocking signals) and it is recommended that it should have the
longest duration.
CLEAR_FWD_ACK 1..2000 (1 unit = 10 ms)

[25]
Clear Forward Acknowledge pulse, Transmission Duration determines the
duration of a Clear Forward Acknowledge pulse (the period that the “M” lead must
remain in an active state). Relevant on an incoming call when the far-end caller
initiates clearing. This pulse is returned by the Coral to the far-end caller, after
receiving Clear Forward signal.
This pulse is relevant for trunk, only when CLEAR_FWD_ACK [3] (page 8-65) is
defined as Yes in its 4TEMP Port Database.
CLEAR_BCK_ACK 1..100..2000 (1 unit = 10 ms)

[26]
Clear Backward Acknowledge pulse, Transmission Duration determines the
duration of a Clear Backward Acknowledge pulse (the period that the “M” lead
must remain in an active state). Relevant on an outgoing call when the far-end
called initiates clearing. This pulse is returned by the Coral to the far-end called,
after receiving Clear Backward signal. This pulse is relevant for trunk, only when
CLEAR_BCK_ACK [4] (page 8-65) is defined as Yes in its 4TEMP Port Database.
8-74
MIN_CLEAR_FWD_ 1..2000 (1 unit = 10 ms)

ACK
Minimum Clear Forward Acknowledge Recognition is the incoming lower limit
[27]
recognition time of CLEAR_FORWARD_ACKNOWLEDGE pulse. Relevant on
an outgoing call when the caller initiates clearing. This pulse is returned from the
far-end called to the Coral, after receiving a CLEAR_FORWARD signal.
active state before the Coral 4TEMP trunk recognizes a far-end CLEAR_
FORWARD_ACKNOWLEDGE signal.
The 4TEMP trunk detects a valid pulse CLEAR_FWD_ACK signal only if the
pulse is shorter than MAX_CLEAR_FWD_ACK defined below and longer than
MIN_CLEAR_FWD_ACK defined here.
MAX_CLEAR_FWD_ 1..2500 (1 unit = 10 ms)

ACK
Maximum Clear Forward Acknowledge Recognition is the incoming upper limit
[28]
recognition time of CLEAR_FORWARD_ACKNOWLEDGE pulse. Relevant on
an outgoing call when the caller initiates clearing. This pulse is returned from the
far-end called to the Coral, after receiving a CLEAR_FORWARD signal.
active state for the Coral 4TEMP trunk to recognize a far-end CLEAR_
FORWARD_ACKNOWLEDGE signal.
The 4TEMP trunk detects a valid pulse CLEAR_FWD_ACK signal only if the
pulse is shorter than MAX_CLEAR_FWD_ACK defined here and longer than
MIN_CLEAR_FWD_ACK defined above.
MIN_CLEAR_BCK_ 1..80..2000 (1 unit = 10 ms)

ACK
Minimum Clear Backward Acknowledge Recognition is the incoming lower limit
[29]
recognition time of CLEAR_BACKWARD_ACKNOWLEDGE pulse. Relevant
on an incoming call when the called initiates clearing. This pulse is returned from
the far-end caller to the Coral, after receiving a CLEAR_BACKWARD signal.
active state before the Coral 4TEMP trunk recognizes a far-end CLEAR_
BACKWARD_ACKNOWLEDGE signal.
The 4TEMP trunk detects a valid pulse CLEAR_BCK_ACK signal only if the
pulse is shorter than MAX_CLEAR_BCK_ACK defined below and longer than
MIN_CLEAR_BCK_ACK defined here.
8-75
MAX_CLEAR_BCK_ 1..150..2500 (1 unit = 10 ms)

ACK
Maximum Clear Backward Acknowledge Recognition is the incoming upper limit
[30]
recognition time of CLEAR_BACKWARD_ACKNOWLEDGE pulse. Relevant
on an incoming call when the called initiates clearing. This pulse is returned from
the far-end caller to the Coral, after receiving a CLEAR_BACKWARD signal.
active state for the Coral 4TEMP trunk to recognize a far-end CLEAR_
BACKWARD_ACKNOWLEDGE signal.
The 4TEMP trunk detects a valid pulse CLEAR_BCK_ACK signal only if the
pulse is shorter than MAX_CLEAR_BCK_ACK defined here and longer than
MIN_CLEAR_BCK_ACK defined above.
 The following Clearing_By_Pulse fields are relevant for trunk, only when
CLEAR BY
PULSE: CLEAR [2] (page 8-65) is defined in its 4TEMP Port Database.
CLEAR_BY_PULSE Yes/No
[31]
Enter No to skip to (the next prompt) CLEAR BY CONTINUANCE: <N/A> (page 8-78).
Press Enter to display CLEAR_BY_PULSE fields.
 When CLEAR_BY_PULSE above is set to Yes, the following six fields are
available:
CLEAR_FWD [32] 1..100..2000(1 unit = 10 ms)

Clear Forward pulse, Transmission Duration determines the duration of a Clear
Forward pulse (the period that the “M” lead must remain in an active state). This
pulse is sent by the Coral to the far-end, on an outgoing call when the caller initiates
clearing.
CLEAR_BCK [33] 1..50..2000 (1 unit = 10 ms)

Clear Backward pulse, Transmission Duration determines the duration of a Clear
Backward pulse (the period that the “M” lead must remain in an active state). This
pulse is sent by the Coral to the far-end, on an incoming call when the called
initiates clearing.
8-76
MIN_CLEAR_FWD [34] 1..80..2000 (1 unit = 10 ms)

Minimum Clear Forward Recognition is the incoming lower limit recognition time
of Clear Forward pulse. Relevant on an incoming call when the caller initiates
clearing. This pulse is sent from the far-end caller to the Coral, in order to end the
call.
active state before the Coral 4TEMP trunk recognizes a far-end Clear Forward
signal.
The 4TEMP trunk detects a valid pulse CLEAR_FWD signal only if the pulse is
shorter than MAX_CLEAR_FWD defined below and longer than MIN_CLEAR_
FWD defined here.
MAX_CLEAR_FWD 1..150..2500 (1 unit = 10 ms)

[35]
Maximum Clear Forward Recognition is the incoming upper limit recognition time
of Clear_Forward pulse. Relevant on an incoming call when the caller initiates
clearing. This pulse is sent from the far-end caller to the Coral, in order to end the
call.
active state for the Coral 4TEMP trunk to recognize a far-end Clear_Forward
signal.
The 4TEMP trunk detects a valid pulse CLEAR_FWD signal only if the pulse is
shorter than MAX_CLEAR_FWD as defined here and longer than MIN_CLEAR_
FWD as defined above.
MIN_CLEAR_BCK [36] 1..43..2000 (1 unit = 10 ms)

Minimum Clear Backward Recognition is the incoming lower limit recognition
time of Clear_Backward pulse. Relevant on an outgoing call when the called
initiates clearing. This pulse is sent from the far-end called to the Coral, in order to
end the call.
active state before the Coral 4TEMP trunk recognizes a far-end Clear_Backward
signal.
The 4TEMP trunk detects a valid pulse CLEAR_BCK signal only if the pulse is
shorter than MAX_CLEAR_BCK defined below and longer than MIN_CLEAR_
BCK defined here.
8-77
MAX_CLEAR_BCK 1..80..2500 (1 unit = 10 ms)

[37]
Maximum Clear Backward Recognition is the incoming upper limit recognition
time of Clear_Backward pulse. Relevant on an outgoing call when the called
initiates clearing. This pulse is sent from the far-end called to the Coral, in order to
end the call.
active state for the Coral 4TEMP trunk to recognize a far-end Clear_Backward
signal.
The 4TEMP trunk detects a valid pulse CLEAR_BCK signal only if the pulse is
shorter than MAX_CLEAR_BCK defined here and longer than MIN_CLEAR_
BCK defined above.
CLEAR BY CON-  The following Clearing_By_Continuance fields are relevant for trunk,
TINUANCE: only when CLEAR [2] (page 8-65) is defined as C in its 4TEMP Port
<N/A> Database.
CLEAR_BY_ Yes/No
CONTINUANCE [38]
Enter No to skip to (the next prompt) INCOMING: (page 8-79) fields.
Press Enter to display Clear_By_Continuance fields.
 When CLEAR_BY_CONTINUANCE above is set to Yes, the following four

fields are available:
O/G_CLEAR_FWD [39] 1..200 (1 unit = 0.1 second)

Clear Forward, Transmission Duration determines the minimum period that the
“M” lead must remain in an active state, for the far-end trunk to recognize a Clear
Forward indication. This signal is sent by the Coral to the far-end on an outgoing
call, when the caller initiates clearing in order to end the call.
O/G_CLEAR_BCK [40] 1..200 (1 unit = 0.1 second)

Clear Backward, Transmission Duration determines the minimum period that the
“M” lead must remain in an active state, for the far-end trunk to recognize a Clear
Backward indication. This signal is sent by the Coral to the far-end on an incoming
call, when the called initiates clearing in order to end the call.
8-78
I/C_CLEAR_FWD [41] 1..200 (1 unit = 0.1 second)

Minimum Clear Forward Recognition determines the minimum period that an “E”
lead must remain in an active state, before the trunk recognizes a far-end Clear
Forward indication.
Relevant on an incoming call when the caller initiates clearing. This signal is sent
from the far-end caller to the Coral, in order to end the call.
I/C_CLEAR_BCK [42] 1..200 (1 unit = 0.1 second)

Minimum Clear Backward Recognition determines the minimum period that an
“E” lead must remain in an active state, before the trunk recognizes a far-end Clear
Backward indication.
Relevant on an outgoing call when the called initiates clearing. This signal is sent
from the far-end called to the Coral, in order to end the call.
INCOMING: The following fields are relevant only during incoming calls.
SUSP_SZE [43] 1..2..200 (1 unit = 10 ms)

Minimum Suspect Seize Recognition determines the period that an incoming call
signal must remain at a trunk port (“E” lead active) before the signal is recognized
as a possible seize from the far-end.
MIN_SZE [44] 1..3..200 (1 unit = 10 ms)

Minimum Seize Response Recognition is the incoming lower limit recognition
time of Seizure pulse. This pulse is sent by the far-end to the Coral in order to start
a new call from an idle state.

active state before the Coral 4TEMP trunk recognizes a far-end Seizure signal.
The 4TEMP trunk detects a valid pulse SEIZE signal only if the pulse is shorter
than MAX_SZE defined below and longer than MIN_SZE defined here.
MAX_SZE [45] 1..22..250 (1 unit = 10 ms)

Maximum Seize Response Recognition is the incoming upper limit recognition
time of Seizure pulse. This pulse is sent by the far-end to the Coral in order to start
a new call from an idle state.
active state for the Coral 4TEMP trunk to recognize a far-end Seizure signal.
The 4TEMP trunk detects a valid pulse SEIZE signal only if the pulse is shorter
than MAX_SZE defined here and longer than MIN_SZE defined above.
8-79
DELAY_TO_SZE_ACK 0..200 (1 unit = 10 ms)

[46]
Delay from Seize Receiving to Seize Acknowledge Transmission determines the
delay time between Seize recognition to Seize Acknowledge start. In other words,
the delay period from the detection of an incoming Seize signal to the start of the
outgoing Seize Acknowledge signal. During this time all incoming digits are
ignored.
 In addition to this delay, a Seize Ack does not start until Coral resources
(for example DTMF receiver) are available to process the call.
This timer is relevant for trunk, only when SZE_ACK [0] (page 8-65) is defined as
Yes, in its 4TEMP Port Database.
SZE_ACK [47] 1..50..200 (1 unit = 10 ms)

Seize Acknowledge Pulse, Transmission Duration determines the duration of a
Seize Acknowledge pulse (the period that the “M” lead must remain in an active
state). This pulse is returned by the Coral after a seizure signal from the far-end has
been recognized and resources in the Coral are available.
This pulse is relevant for trunk, only when SZE_ACK [0] (page 8-65) is defined as
MIN_MAKE [48] 1..20..100 ms

Minimum Make Time Recognition determines the minimum Make time between
successive Breaks, during a rotary (pulse) dial cycle, for the trunk card to recognize
the rotary dialed digits (“E” lead idle).
The 4TEMP trunk detects a valid pulse MAKE signal only if the pulse is shorter
than MAX_MAKE defined below and longer than MIN_MAKE defined here.
MAX_MAKE [49] 1..70..250 ms

Maximum Make Time Recognition determines the maximum Make time between
successive Breaks, during a rotary (pulse) dial cycle, for the trunk card to recognize
the rotary dialed digits (“E” lead idle).
If “E” lead remains idle when this timer expires, the trunk card interprets the
restoral as a pause between digits or as end of digits.
The 4TEMP trunk detects a valid pulse MAKE signal only if the pulse is shorter
than MAX_MAKE defined here and longer than MIN_MAKE defined above.
MIN_BREAK [50] 1..40..100 ms

Minimum Break Time Recognition determines the minimum Break time, during a
rotary (pulse) dial cycle, for the trunk card to recognize the rotary dialed digits (“E”
lead active).
8-80
The 4TEMP trunk detects a valid pulse BREAK signal only if the pulse is shorter
than MAX_BREAK defined below and longer than MIN_BREAK defined here.
MAX_BREAK [51] 1..80..250 ms

Maximum Break Time Recognition determines the maximum Break time, during
a rotary (pulse) dial cycle, for the trunk card to recognize the rotary dialed digits
(“E” lead active).
The 4TEMP trunk detects a valid pulse BREAK signal only if the pulse is shorter
than MAX_BREAK defined here and longer than MIN_BREAK defined above.
ANSWER [52] 1..200 (1 unit = 10 ms)

Answer pulse, Transmission Duration determines the duration of an Answer pulse
(the period that the “M” lead must remain in an active state). The answer signal is
returned by the Coral, to the far-end caller, after the called station off-hooks.
This pulse is relevant for trunk, only when ANSWER [1] (page 8-65) is defined as
OUTGOING: The following fields are relevant only during outgoing calls.
SZE [53] 1..4..200 (1 unit = 10 ms)

Seizure pulse, Transmission Duration determines the duration of a Seize pulse (the
period that the “M” lead must remain in an active state). This pulse is sent by the
Coral from an idle state the far-end in order to place a new outgoing call.
MIN_TIME_TO_SZE_ 0..250 (1 unit = 10 ms);

ACK [54] Tip: Must be less than WAIT_FOR_SZE_ACK [21] (page 8-73)

Seize Acknowledge Reject Time determines the time from Seize sent until the
Coral is ready to accept the Seize-Acknowledge from the far-end. This is an
anti-glare protection time. Any pulse detected in this time is interpreted as
suspected incoming call. Incoming call is preferred over outgoing call.
MIN_SZE_ACK [55] 1..40..200 (1 unit = 10 ms)

Minimum Seize Acknowledge Pulse Recognition is the incoming lower limit
recognition time of Seize_Acknowledge pulse. Determines the minimum period
that an “E” lead must remain in an active state before the Coral recognizes a far-end
ready for an incoming call. This pulse is returned by the far-end after the seizure
signal from the Coral has been recognized and resources in the far-end are available
to accept dial digits.
8-81
The 4TEMP trunk detects a valid pulse SZE_ACK signal only if the pulse is shorter
than MAX_SZE_ACK defined below and longer than MIN_SZE_ACK defined
here.
MAX_SZE_ACK [56] 1..60..250 (1 unit = 10 ms)

Maximum Seize Acknowledge Pulse Recognition is the incoming upper limit
recognition time of Seize_Acknowledge pulse. Determines the maximum period
that an “E” lead can remain in an active state for the Coral to recognize a far-end
ready for an incoming call. This pulse is returned by the far-end after the seizure
signal from the Coral has been recognized and resources in the far-end are available
to accept dial digits.
The 4TEMP trunk detects a valid pulse SZE_ACK signal only if the pulse is shorter
than MAX_SZE_ACK defined here and longer than MIN_SZE_ACK defined
above.
MAKE [57] 1..40..250 ms

Outgoing Rotary Dialing Make Time determines the Make time between
successive Breaks, during a rotary (pulse) dial cycle from a pulse dialing trunk
during an outgoing call (“M” lead idle). Dialing the number “five” means 5 Breaks
and 4 Makes.
BREAK [58] 1..60..250 ms

Outgoing Rotary Dialing Break Pulse, Transmission Duration determines the
Break time during a rotary (pulse) dial cycle from a pulse dialing trunk during an
outgoing call (“M” lead active). Dialing the number “two” means 2 Breaks and 1
Make.
INTERDIGIT [59] 1..100..250 (1 unit = 10 ms)

Outgoing Rotary Interdigit Time determines the period that the “M” lead is idle
between rotary (pulse) dialed digits from a rotary dialing trunk, during an outgoing
call.
For DTMF trunk tones, see DTMF_TONE beginning on page 6-5 in Feature
Timers.
MIN_ANSWER [60] 1..200 (1 unit = 10 ms)

Minimum Answer Pulse Recognition is the Incoming lower limit recognition time
of ANSWER pulse. Determines the minimum period that an “E” lead must remain
in an active state before the Coral recognizes a far-end answer.
8-82
The 4TEMP trunk detects a valid pulse ANSWER signal only if the pulse is shorter
than MAX_ANSWER defined below and longer than MIN_ANSWER defined
here.
MAX_ANSWER [61] 1..250 (1 unit = 10 ms)

Maximum Answer Pulse Recognition is the incoming upper limit recognition time
of the ANSWER pulse. Determines the maximum period that an “E” lead can
remain in an active state for the Coral to recognize a far-end answer.
The 4TEMP trunk detects a valid pulse ANSWER signal only if the pulse is shorter
than MAX_ANSWER defined here and longer than MIN_ANSWER defined
above.
[62]
Transfer the updated card database immediately to the trunk cards. Regardless of
entry, routine diagnostics periodically resend the Card Database to the cards,
including any updates made. This parameter is used only in the Update Mode.
8-83
4TWL Trunk Card Database ç CDB,10

Indian (CC8) and New Zealand (Eu7) systems only
The Two Way Loop (TWL) Trunk Card Database programs the trunk card database
tables for DID and DOD trunk ports connected to the 4TWL or 4TWLipx cards.
There are 4 Trunk card Databases (0-3), one of which is assigned to each card (see
Card List - Chapter 6). Field numbers appear in square brackets ([ ]).
The Two Way Loop (TWL) interface operates on a 2 wire basis, A and B, with a
-48V potential or loop. Four analog interfaces with bi-directional TWL protocol
exist. Backward recognition is -48V for wire A and earth for wire B (or visa versa).
Signals in the forward direction are sent via a loop applied across the 2 wires.
The 4TWL card is used to implement DID and DOD functions.
Incoming calls will act exactly as DID incoming calls (see DID/E&M Groups
beginning on page 8-36).
Outgoing calls are Loop Start with answer supervision and disconnect suppression
(DTMF only).
 No calibrated hookflash is available on this trunk card.
FROM/ 0..3
TO 0..3
CARD_DB#
Enter the required range of 4TWL card database tables; FROM the lowest table
SUSP_SZE [0] 20..60..100 ms (in increments of 10)

4TWL Trunk Card Database CDB,10
outside party. SUSP_SZE results in prohibiting outgoing calls thus preventing a
glare condition, or double seizure (see Figure 8-3 on page 8-51).
SEIZE [1] 110..350..500 ms (in increments of 10)

Determines the minimum period that an incoming call signal (loop current) must
remain at a trunk port before the signal is recognized as a seize from the CO.
INTERFACE SIDE [2] 0 (User)/ 1(Network)

Not used in this version. Always set to User.
8-84
CO DISCONNECT [3] 300..600..2500 ms (in 10 ms increments)

Central Office Disconnect determines the minimum waiting period for a trunk
disconnect signal before the system recognizes the signal as a valid call disconnect,
thereby releasing the trunk.
DELAY TO BLOCK [4] 10..65 seconds

Delay Before Trunk Block defines the maximum system waiting time for a
disconnect acknowledgment signal from the Central Office, before the system
blocks the trunk line. When the trunk is blocked the call is either transferred to an
incomplete call destination or calls toward the CO are blocked. This timer is
applied when the Coral releases first and the CO release is pending.
O/G_BREAK [5] 30..60..120 ms
 For card version 1.03 and later.

Outgoing Break Time determines the period that the loop current is interrupted
during a rotary (pulse) dial cycle conducted by the rotary dialing trunk port.
O/G_MAKE [6] 20..40..80 ms

Outgoing Make Time determines the period that the loop current is restored
between successive break pulses of the dialed digit, during a rotary (pulse) dial
cycle conducted by the trunk port.
O/G_INDGT [7] 500..700..1000 ms

Outgoing Rotary Interdigit Time determines the period from completion of the
lasts digit transmission to commencing transmission of the next consecutive digit,
during an outgoing call.
I/C_MIN_BREAK [8] 10..40..60 ms

Incoming Minimum Break Time determines the minimum Break time, during a
rotary (pulse) dial cycle, for the trunk card to recognize the rotary dialed digits.
A break-time greater than or equal to the defined period is not recognized by the
system as a break if it is also shorter than or equal to I/C_MAX_BREAK below.
8-85
I/C_MAX_BREAK [9] 30..90..110 ms

Incoming Maximum Break Time determines the maximum Break time, during a
rotary (pulse) dial cycle, for the trunk card to recognize the rotary dialed digits.
A break-time greater than or equal to the defined period is not recognized by the
system as a break if it is also shorter than or equal to I/C_MIN_BREAK below.
I/C_MIN_MAKE [10] 20..60 ms

Incoming Minimum Make Time determines the minimum Make time between
successive Breaks while a digit is being rotary (pulse) dialed.
If signaling current remains when this timer expires, the trunk card interprets the
I/C_MAX_MAKE [11] 40..60..100

Incoming Maximum Make Time determines the maximum Make time between
successive Breaks while a digit is being rotary (pulse) dialed.
If signaling current remains when this timer expires, the trunk card interprets the
SEND_TO_CARD [12] Yes/No

routine diagnostics periodically resend the card database to the cards, including any
updates made. This parameter is used only in the Update Mode.

8-86
E&M Trunk Definition ç TRK,1 [0,2,1,0,0,1]
E&M Trunk Definition is used to define the trunk signaling parameters for E&M
trunks connected to 4TEM, 4TEMipx, 4TEMP, T1, 30T, 30T/E, 30T/M, 30T/x
cards. These parameters apply only to E&M trunks, and are used in addition to
General Trunk Definitions beginning on page 8-11. Field numbers appear in square
brackets ([ ]).
FROM/TO DIAL# Any valid E&M dial number;

Default: All defined E&M trunks
Enter the required range of E&M trunks; FROM the lowest E&M trunk number TO
the highest E&M trunk number.
DELAYED/IMMEDIATE/ 0 (Delay Start), 1 (Immediate Start), 2 (Wink Start);

WINK [0]

Continuous trunks only
When this trunk is defined as CAMA in General Trunk Definitions (see
TYPE [4] on page 8-12), then this parameter is automatically set to Wink
start and cannot be changed.
Determines whether the signaling/handshaking protocol of the E&M Continuous
trunk is Delay Start, Immediate Start, or Wink Start.
E&M_CONTINUOUS_ 0..1
TIMERS # [1]
Determines which E&M Continuous Timer table, 0 or 1, (see E&M Continuous
Timers beginning on page 8-59) is used to define the trunk operating
characteristics.
2W/4W [2] 2W/4W
E&M Trunk Definition TRK,1 [0,2,1,0,0,1]

4TEM, 4TEMipx,
This option applies only for analog 4TEM, 4TEMipx, 4TEMP cards, providing the
4TEMP cards only
cards with the connection to a CO that works in 4-wire mode. The 2-wire or 4-wire
option is strap selectable. When working in 4-wire mode ETR and ETT are the
transmitting leads and ERR and ERT are receiving leads. In 2-wire mode only ETR
and ETT leads are utilized.
 Notes:
• Selecting 2W or 4W must match the wire strap on the card (See relevant
Coral Installation Manual).
• Wire selection directly influences the Network Balance (see Balancing
Network beginning on page 19-24). The 2-wire mode uses 2 as the
Balancing Network, while 4-wire mode uses 0. After selecting the
appropriate mode, the Coral system automatically selects the proper
balancing network.
8-87
ANSWER_ Yes/No
MANDATORY [3]
Provides answer supervision for E&M Continuous trunks, by either disconnecting
Continuous trunk only
or connecting the trunk when the answer signal is not detected.
Entering Yes doesn’t accept an answer and automatically releases the outgoing
trunk after time-out.
Enter No so that if the answer is not accepted, the outgoing trunk connects after
time-out.
CORAL_MAIL [4] Yes/No

Voicemail System -
Determines whether the trunk is connected to the Voicemail System (Yes).
4TEM and 4TEM/S
CoralMail™ is an integrated proprietary voice messaging system.

cards only
When Y is selected, 2W/4W (see above) must be set to 4W, and
ANS/DISC_PULSE_ON_XFER (see below) must be set to Y.
DATA_SERVICE [5] Not Used
H.FLASH ACCEPT [6] Yes/No
 In noisy areas, set this parameter to No.

Determines whether the E&M trunk can recognize a calibrated opening signal sent
from the far-end. Flash duration is defined through E&M Continuous Timers
beginning on page 8-59 and 4TEMP (E&M Pulsed) Card Database beginning on
page 8-67.
CONNECTED_TO_ Yes/No
PUBLIC_EXCHANGE
This parameter determines how the Coral relates to an incoming call.
[7]
Enter N to define regular E&M line.
When entering Y, the Coral relates to the line as an incoming call from a CO. In
this case, if the internal called station is busy, the call camps-on automatically to
the busy station or enters as a second call in the multi-appearance to avoid sending
a busy tone.
Enter Y to enable an incoming call to a busy station to act as a CO trunk; the call
rings as multi-appearance or camp-on (instead of busy tone).
8-88
ANS/DISC_PULSE_ Yes/No
ON_XFER [8]
Answer/Disconnect Pulse After Transfer determines whether the system sends a
Continuous trunks only
signal when a call is either answered or disconnected by a third party (Yes). This
parameter functions when a transferred call appears on a currently busy E&M
Continuous trunk. This parameter is typically used when a trunk is connected to a
Voicemail system or automatic attendant. Using this parameter allows immediate
Voicemail response to the transferred call. ANS/DISC duration is defined by
ANS/DISC_PULSE_WIDTH [4] on page 8-60, in E&M Continuous Timers. The signal
is sent over the E&M Continuous trunk from the third party to the first party.
MUSIC_ON_ 0..3;
HOLD/TRANSFER [9] Coral IPx 500 and CDRS 200E: 0 (MP-1), 1 (MP-2);
Determines which music source is sounded on the called party’s line after being
placed on hold or transferred by the E&M trunk.
WINK_FOR_BUSY [10] Yes/No
 This parameter is relevant only for E&M Trunks defined as “Wink Start”.
This parameter defines whether or not a wink signal is sent, in addition to the busy
tone, when the called party is busy. This wink signal can be used to activate
applications which run only on E&M lines (such as Voicemail).
The wink signalling is defined in Trunk Timers beginning on page 8-7.
INCOMING_TOLL [11] Yes/No

CC10 only
This parameter defines whether or not an incoming toll call is allowed to break into
an ongoing conversation by the attendant/operator.

The operator is notified whether the called party is busy only if the incoming line
is prompted with an appropriate signal. Therefore, WINK_FOR_BUSY above
must be set to YES and one “wink” is sent.
If the break-in is not allowed, two winks are sent by the Coral (ON, OFF, ON).
Additionally, the Coral checks if the called party is engaged in a conversation in a
“connect” state. i.e., it is not held, dialing, in conference, etc., If state of connect is
detected, the incoming toll call is allowed to break in and is heard by both parties.
The Coral also checks whether break-in is allowed according to other system
parameters (such as DATA_SECURE_LINE).
8-89
DID Trunk Definition ç TRK,3 [0,2,1,0,0,3]
DID Trunk Definition is used to program the trunk signaling parameters for each
Direct Inward Dial (DID) trunk installed in Coral systems. This parameter applies
only to DID trunks connected to 8DID, 30T, 30T/E, 30T/M, 30T/x, ALS, BID,
GID, 4TWL cards and is used in addition to General Trunk Definitions beginning
on page 8-11.
FROM/TO DIAL# Any valid DID trunk dial number; All defined DID trunks
Enter the required range of DID trunks, FROM the lowest DID trunk dial number
TO the highest DID trunk dial number.
IMMEDIATE/WINK, 0 (Immediate Start), 1 (Wink Start or Delay Start)

DELAYED
Determines when the signaling/handshaking protocol of the trunk is Immediate
Start, Wink Start or Delay Start. Entering 1 allows the trunk to be either Wink Start
or Delay Start. The signaling protocol is further defined in 8DID Card Database
 Notes:
• This entry must match CKT 0-7 defined in“8DID Card Database” (see
page 8-91).
• In European systems the equivalent BID trunk ports must be set to zero
(0). The parameter displays:0 = IMM/BID, 1 = WINK/DELAYED.
DID Trunk Definition TRK,3 [0,2,1,0,0,3]
8-90
8DID Card Database ç DIDB

The 8DID Card Database is relevant and assigned to each 8DID, 8DID/S,
8DID/S-Z trunk card (see Card List – Chapter 6).
 This menu is not relevant for 4TWL, ALS70-DID, BID or GID cards.
FROM/ 0..3
TO 0..3
CARD_DB#
Enter the required range of card database tables; FROM the lowest table number
TO the highest table number.
CKT 0-7 0 (Immediate Start),1 (Wink Start), 2(Stop Go [Delay])

(CKT ON DID CARD)

[0,1,2,3,4,5,6 or 7]
This entry must match the IMMEDIATE/WINK, DELAYED entry found in DID
Trunk Definitions (see page 8-90).
Determines when the signaling/handshaking protocol for the CKT (trunk port) on
all trunk cards with this Database is Immediate Start, Wink Start, or Stop/Go
(Delay) Start. This protocol is also defined under DID Trunk Definition beginning
on page 8-90.
8DID Card Database DIDB
8-91
COLLECT CALLS 1..254 ms

BLOCK [8,9,10]
CC3 only
 The 8DID/S-Z card software version must be 17.16 or higher.
Three parameters are used to implement a blocking protocol for incoming collect calls.
Parameter Name Default

In an incoming call, if the person called is restricted by COS to accept collect calls,
the Coral signals the CO accordingly. The signaling is implemented by
disconnecting and connecting the line according to the following time intervals:
• Line permanently closed
If the incoming call is a collect call, the CO will disconnect the line after
identification of the above pulse sequence.
MIN_BREAK [11] 20..32..72 ms

Determines the minimum period that loop current must be interrupted during a
rotary (pulse) dial cycle for the trunk card to recognize rotary dialing.
MAX_BREAK [12] 20..80..72 ms

Determines the maximum period that loop current can remain interrupted during a
rotary (pulse) dial cycle for the trunk card to recognize rotary dialing.
MAX_(BREAK+ 48..200..252 ms
MAKE) [13]
Determines the maximum rotary (pulse) dial cycle (Break + Make) duration, while
a digit is rotary dialed.
8-92
SEIZE [14] 10..60..1020 ms

Determines the minimum period that an incoming call signal (loop current) must
remain at a trunk port before the signal is recognized as a seize from the CO.
DISCONNNECT [15] 80..152..300 ms

Determines the minimum period for a disconnect signal (loop current interrupted)
before the Coral recognizes the signal as a valid call disconnect, thereby releasing
the trunk.
SEIZE.TO-WINK [16] 80..140..300 ms

Determines the minimum delay between the recognition of an incoming seizure
and the application of a Wink signal in response. This timer applies only to DID
trunks which are defined as Wink Start (DID Trunk Definition beginning on page
8-90).
Upon incoming seizure, the system checks resources to determine whether or not
the system is ready to process the call. If resources are available, this timer is
started. When this timer expires, the trunk sends a Wink signal.
WINK WIDTH [17] 40..304..320 ms

Determines the duration of the Wink signaling pulse, sent in response to an
incoming trunk seizure. This timer applies only to DID trunks which are defined as
Wink Start (see DID Trunk Definition beginning on page 8-90).
FILTER AFTER WINK 28..72..120 ms

[18]
Determines the period following the application of a Wink signal where any change

on the trunk, whether electrical state or audio dial signal, is ignored. This timer only
applies to DID trunks which are defined as Wink Start (see DID Trunk Definition
When this timer expires, incoming dialed digit analysis commences.
FILTER AFTER GO 28..72..120 ms

[19]
Determines the period following the application of a Go signal that any change on
the trunk, whether electrical state or audio dial signal, is ignored. This timer only
applies to DID trunks which are defined as Delay Start (Stop/Go) (see DID Trunk
Definition beginning on page 8-90).
When this timer expires, incoming dialed digit analysis commences.
8-93
SG SEIZE.TO START 80..120..300 ms

[20]
Determines the minimum delay between the recognition of an incoming seizure
and the application of a Stop Dial signal in response. This timer applies only to DID
trunks which are defined as Delay Start (Stop/Go) (see DID Trunk Definition
When this timer expires, the trunk sends a Stop Dial signal.
SG PULSE WIDTH 80..140..300 ms

[21]
Determines the minimum duration of a Stop Dial signal, acknowledging an
incoming trunk seizure. This timer applies only to DID trunks which are defined as
Delay Start (Stop/Go) (see DID Trunk Definition beginning on page 8-90.
When the Time From Seize To Stop/Go Start timer described in this form expires,
the trunk sends a Stop Dial signal and the system checks to determine if resources
are available to process the call. When system resources are available, this timer is
started. When this timer expires, the trunk sends a Go signal.
[22]
Update Mode.
8-94
T1 and 30T/x Card Configuration ç DTDB,0

The configuration option is used to determine the protocol type for individual
channels on a digital trunk card.
Access is accomplished by entering the physical location of any current card (shelf
and slot), or before installing the card, by defining the default.
When entering this mode, the PI prompts the user to enter 0 for changing the
default or 1 for access by physical current card location.
0 - DEFAULT This option is used to display or modify the default configuration of the digital
Configuration cards. It determines the protocol type for individual channels on the digital trunk.
This default will be given to the digital card that will be installed in the future. For
cards already installed, the configuration can be modified by using the 1-CURRENT
Configuration option below.
Each trunk can be separately configured according to any of the following ranges:
Card Type Range Default

E&M (0) DDI (1) DDO, LS, GS, B_DI
Continuous NonDID (2) (3)
T1 0 (E&M), 1 (LS), 2 (GS) 0-23 - - N/A
30T 0 (E&M), 1 (DDI), 2 (DDO) - 18-29 0-17 N/A
30T/E 0 (E&M),1 (DDI), 2 (DDO) - 18-29 0-17 N/A

30T/CHI, etc.
30T/M 0 (E&M),1 (DDI), 2 (DDO), - 18-29 0-17 -

3 (BI_D)
30T/E (Eu0) 0 (E&M),1(DDI), 2(NonDID) - 18-29 0-17 N/A
T1 and 30T/x Card Configuration DTDB,0

30T/E (Eu1) 0 (E&M),1 (DDI), 2 (DDO) - 0-14 15-29 N/A
*
2DT (T1) 0 (E&M) 0-23 N/A N/A N/A
2DT (30T) tbd
2DT (30TM) tbd
*Bi-Directional, for 30T/M card version 32.xx and higher.
* 2DT cards do not support LS and GS protocols
8-95
1-CURRENT This option is used to display or modify signaling protocol for each installed digital
Configuration trunk according to card location, by entering the card’s physical location in the
system. The system automatically skips over slots not equipped with digital cards.
Each trunk can be separately configured according to any of the ranges listed in the
0 - DEFAULT Configuration table above.
Before entering Current Config, the system checks for a previous update that is still
pending. If such an update is detected then the following message appears:
** WARNING ** DGTL CARD in config mode
override configuration? (Y/N)
Entering Yes causes the system to ignore all entries made in the previous card
configuration. Entering No causes the system to return to the previous mode level.

0..2: CDRS 200E

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
8-96



UPDATE? Yes/No
! Changing the configuration causes:

1. All established calls on this card to be dropped.
2. The database that belongs to the card and its associated trunks to
be erased.
3. The card to re initialize without the previous definitions.
 All related databases must be programmed again.

Transfers the new card configuration to the trunk card and database. When No is
selected, any entries are ignored. No default is presented, therefore, either Y
(update) or N (cancel operation) must be entered. This parameter is used only in the
Update Mode.
8-97
T1, PRI, TBR, 30T/x, 2DT Synchronization ç DTDB,3

The SYNC option form defines the clock reference source with which the Coral
system switching is synchronized.
Determines which of the digital trunk cards or 2DT cards’ peers are utilized as the
primary (PRM) clock reference source and which digital trunks are utilized as the
secondary (SEC) reference source, if any. The PRM and SEC digital trunk cards
are especially wired in the backplane in order to use a card operating in slave clock
mode.
 When a TBR card is selected, set SYNC_CHANNEL to Yes and

PERMANANT ACTIVE CHANNEL [DTDB,4] to No (see page 26-19).
 The 2DT card can select one of the two clock sources in the board. The
clock source is extracted from peer# 0 or from peer# 1. The selection
between these two clock sources is controlled by the Coral system main
control card.
A 2DT card can NOT support both primary and secondary synchronization
simultaneously.
A card operating in Slave Clock mode has the backplane pre-wired at the factory
and cards must be installed only in the proper slot. For further details, see Table
8-5 below and refer to the relevant Coral Installation Manual.
! Changing the clock reference source through the following parameters,

resets the current digital trunk card.
Attempting to define a location when no ISDN or digital card (2DT, T1, PRI-24,
T1, PRI, TBR, 30T/x, 2DT Synchronization DTDB,3
PRI-30, 4TBR, 8TBR or 30T/x) is installed in the defined card slot, causes the
following error message to appear:
NOT DGTL TRK CARD.
The attempt will be refused.
8-98
Synchronization Card Slots Range

The two card slots, designated PRM SYNC and SEC SYNC vary with each
cabinet. The table below identifies the card slot location range for each cabinet
type.
Table 8-5: External Clock Synchronization Card Slots Range
Cabinet Type Primary Clock Sync. Secondary Clock Sync.

Card Slot Card Slot
PRM SYNC SEC SYNC
Coral IPx Office (1,8) or (1,10) or (1,8) or (1,10) or

(2,4) or (3,4) (2,5) or (3,5)
Coral IPx 500 (0,4) or (1,4) or (2,4) (0,5) or (1,5) or (2,5)
CDRS/CDRX 200E (0,4) or (1,4) or (2,4) (0,5) or (1,5) or (2,5)
Coral IPx 800 (0,4) or (1,4) or (2,4) (0,5) or (1,5) or (2,5)
Coral IPx 3000 (0,4) or (8,4) (0,5) or (8,5)
Coral IPx 4000 (0,4) (2,4) or (4,4) or (8,4)
Coral FlexiCom 400 (0,2) (0,3)
FlexLITE 400 (0,2)* (0,3)*
Coral FlexiCom 5000 (0,4) (1,4)

Main with two peripheral
shelves 1xPB-24
Coral FlexiCom 5000 (0,4) (2,4) 128 T.S.

Main with two peripheral (4,4) 256 T.S.
shelves 2xPB-24 (8,4) 512 T.S.

Main with three peripheral (4,4) 256 T.S.
shelves 2xPB-24 (8,4) 512 T.S.

Main with three peripheral (8,4) 256 T.S.
shelves 3xPB-24
Coral FlexiCom 6000 (0,4) (2,4), (4,4) or (8,4)

* Sync slots in FlexLITE are used to synchronize the system clock only when
the FlexLITE 400 is used as self-contained cabinets with common control
cards.
8-99
ADDR (Shelf,
Slot)
! Changing the clock reference source through the following parameters,
resets the current digital trunk card.
PRM Any (Shelf,Slot) as listed in Table 8-5 under PRM SYNC, or R(Remove “--,--“)
Determines which of the digital trunk cards is utilized as the Primary (PRM) clock
reference source.
Shelf and Slot numbers are entered between parenthesis, separated by a comma.
Entering R removes the card slot location reference.
When Remove is entered or (—,—) is displayed the system selects the clock source
automatically.
PEER_SELECTION 0 (Peer #0), 1 (Peer #1), 2 (Both)

This parameter is displayed beneath the PRM parameter for authorized 2DT cards,
only.
It defines whether the 2DT card functions as the primary synchronization source
according to the following methods:
• 0 - synchronization available only if PRM peer #0 Status is OK
• 1 - synchronization available only if PRM peer #1 Status is OK
• 2 - synchronization available only if at least one of the PRM peers Statuses is
OK
Update PRM? Yes/No

This parameter is displayed for authorized 2DT cards, only.
Enter Yes to accept changes.

It defines whether the 2DT card functions as the pimary synchronization source
according to the selected peer:
When No is selected, any entries are ignored. No default is presented, therefore,
either Y (update) or N (cancel operation) must be entered.
This parameter is used only in the Update Mode.
SEC Any (Shelf,Slot) as listed in Table 8-5 under SEC SYNC, or R(Remove “--,--“)
Determines which of the digital trunk cards is utilized as the Secondary (SEC)
clock reference source.
Shelf and Slot numbers are entered between parenthesis, separated by a comma.
Entering R removes the card slot location reference.
When Remove is entered or (—,—) is displayed the system selects the clock source
automatically.
8-100
PEER_SELECTION 0 (Peer #0), 1 (Peer #1), 2 (Both)

This parameter is displayed beneath the SEC parameter for authorized 2DT cards,
only.
It defines whether the 2DT card functions as the secondary synchronization source
according to the following methods:
• 0 - synchronization available only if SEC peer #0 Status is OK
• 1 - synchronization available only if SEC peer #1 Status is OK
• 2 - synchronization available only if at least one of the SEC peers Statuses is
OK
Update SEC? Yes/No

This parameter is displayed for authorized 2DT cards, only.
Enter Yes to accept changes.
It defines whether the 2DT card functions as the secondary synchronization source
according to the selected peer:
STATUS  Display Only

0 (OK), 1 (Lock Fault), 2 (Communication Fault)
PRM - Shows the diagnostic status for the primary digital trunk card.

• PEER 0 - Shows the diagnostic status for the primary Peer #0 of a 2DT card.
• PEER 1 - Shows the diagnostic status for the primary Peer #1 of a 2DT card.
SEC - Shows the diagnostic status for the secondary digital trunk card.
• PEER 0 - Shows the diagnostic status for the secondary Peer #0 of a 2DT card.
• PEER 1 - Shows the diagnostic status for the secondary Peer #1 of a 2DT card.
CURR_CLK  Display Only

0 (Self (Master)), 1 (Primary (Slave)), 2 (Secondary (Slave))
Shows the current clock reference source with which the Coral system is
synchronized.
8-101
2DT Card Database ç CDB,12

 Due to logistical requirements, the cards are labelled:
"PRI-2DT", PRI-2DTipx" or "PRI-2DT Office”
on the front panel and on attached shipping documentation.
The 2DT digital trunk card supports up to two trunk lines, or “peers”, or circuits.
The 2DT Card Database option is used to determine the protocol type for individual
peers (circuits) on a 2DT card. This option is applicable for 2DT cards with
firmware 60 or higher (any combination of PRI-23 and PRI-30).
Card Configuration
The card is configured and identified by the Coral main software in two ways:
by the strap jumpers on the board and by PI branch, as defined in Table 8-6 in
the Configuration row. In version 60 the Coral ignores the jumpers on board, and
identifies the card type according the PI database configuration.
Table 8-6: 2DT Card Firmware 55,57,60 Configuration Options
RJ-45 2DT Card Version
Network
Interface 55 57 60
#0 PRI-23, PRI-30 PRI-23, PRI-30, PRI-23, PRI-30

T1, 30T, or 30TM
#1 N/A N/A PRI-23, PRI-30*
Configuration Straps Straps PI
* The enabling of the second trunk circuit on the card requires authorization,
see 2DT WITH 2 CKTS on page 3-18.
The PI allows configuring the protocol type for individual peers on the 2DT card,
whether a card is currently physically installed or not yet installed. Access is
2DT Card Database CDB,12
accomplished by entering the physical location of any current 2DT card (shelf and
slot), or before installing the card, by defining the default:
• To define protocol type parameters before physically installing a 2DT card,
enter the 2DT Card Database: DEFAULT Configuration (page 8-103) branch
[CDB,12,0]. The parameter definitions in this branch will apply to all 2DT
cards installed in the future.
• After a 2DT card is physically installed or defined in Card List on page 6-59, its
protocol type definitions may be changed in order to customize the individual
peers. These changes are made in the 2DT Card Database: CURRENT
Configuration (page 8-105)branch [CDB,12,1].
Details for the 2DT cards are found on the following pages:
2DT Card Database: DEFAULT Configuration ............................... 8-103
2DT Card Database: CURRENT Configuration .............................. 8-105
8-102
2DT Card Database: DEFAULT Configuration ç CDB,12,0

This option is used to display or modify the default configuration of the 2DT cards.
It determines the protocol type for individual peers on the 2DT cards.
The parameter definitions given in this branch (default configuration) will be given
to any 2DT card that will be installed in the future.
For cards already installed or defined in Card List on page 6-59, the configuration
can be modified in the next branch: 2DT Card Database: CURRENT
Configuration beginning on page 8-105. To initialize the card, the
technician/installer must update the parameters in the Current Configuration
branch immediately upon installation.
Each peer can be separately configured according to any of the following
parameters:
0_PEER#0: The following three parameters apply to peer #0.
0_PEER_TYPE 0 (PRI-30), 1 (PRI-23), R (Remove for deactivation “- -”),

(Default: PRI-23 for USA)
Defines the trunk protocol applied to all trunks in peer #0,
for all 2DT cards that will be installed in this Coral system.
0_IMPEDANCE 0 (120 ), 1 (75 )
2DT Card Database: DEFAULT Configuration CDB,12,0

• 0 - Twisted pair cable, balanced line impedance, 120 ohms
• 1- Coaxial cable, unbalanced line impedance, 75 ohms
Defines the network interface cables type and impedance that are connected to the
RJ-45 network interface of peer #0, for all 2DT cards that will be installed in this
Coral system.
0_CARD_DB 1 (PRI-23) Do not change default number for: AT&T, 4ESS

0 (PRI-30) Do not change default number for: ETSI
Identifies the card database (CDB) number assigned to peer #0,
Each peer can be allotted with one of the card database tables that are assigned to
the PEER_TYPE defined as PRI-30 or PRI-23.
8-103
1_PEER_TYPE 0 (PRI-30), 1 (PRI-23), R (Remove for deactivation “- -”)

Defines the trunk protocol applied to all trunks in peer #1,
1_IMPEDANCE 0 (120 ), 1 (75 )

RJ-45 network interface of peer #1, for all 2DT cards that will be installed in this
Coral system.

Identifies the card database (CDB) number assigned to peer #1,
UPDATE? Yes/No
Accept the new default card configuration to the 2DT card database,
2DT Card Database: DEFAULT Configuration CDB,12,0

8-104
2DT Card Database: CURRENT Configuration ç CDB,12,1

This option is used to display or modify the protocol type for each installed 2DT
card’s peer according to card location, by entering the card’s physical location in
the system. The system automatically skips over slots not equipped with digital
cards.
Each peer can be separately configured. Upon card initialization, the system checks
its authorization parameters and resource store. If the sizes of any trunk type
required by the 2DT exceeds the maximum defined system sizes or system
authorization, the card is not initialized and an error message is displayed in Card
List on page 6-59. Table 6-3 on page 6-62 includes a complete list of Card List error
messages for 2DT cards that have not initialized properly.

0: Coral FlexiCom 400 (with HDC controller) ;
0..2: CDRS 200E

0..2: Coral IPx 500, 800
0..15: Coral IPx 3000, 4000
2DT Card Database: CURRENT Configuration CDB,12,1



8-105
CURRENT CARD_2DT
CONFIGURATION l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l

(Default: as defined in 0_PEER_TYPE on page 8-103)
Defines the trunk protocol applied to all trunks in peer #0, for the current 2DT card.
0_IMPEDANCE 0 (120 ), 1 (75 )

(Default: as defined in 0_IMPEDANCE on page 8-103)
RJ-45 network interface of peer #0, for the current 2DT card.

(Default: as defined in 0_CARD_DB on page 8-103)
Identifies the card database (CDB) number assigned to peer #0, for the current 2DT
card.

(Default: as defined in 1_PEER_TYPE on page 8-104)
Defines the trunk protocol applied to all trunks in peer #1, for the current 2DT card.
1_IMPEDANCE 0 (120 ), 1 (75 )

(Default: as defined in 1_IMPEDANCE on page 8-104)
RJ-45 network interface of peer #1, for the current 2DT card.
8-106

(Default: as defined in 1_CARD_DB on page 8-104)
Identifies the card database (CDB) number assigned to peer #1, for the current 2DT
card.
SEND TO CARD? Yes/No (Yes or No must be entered)
! Changing the configuration causes:

1. All established calls on this card to be dropped.
2. The database that belongs to the card and its associated trunks to
be erased.
3. The card to re initialize without the previous definitions.
 All related databases must be programmed again.

Transfers the new card configuration to the current 2DT card and database.
8-107
T1 and 30T Card Database ç DTDB,1,0

Establishes the T1 (24 channel American standard) and 30T (CET/E1 30 channel
European standard) card database.
The 30T card database establishes the card database for the E1 30 channel. The
card is represented with different suffixes in various countries such as:
Israel: 30T; Ireland: 30T/M IR, etc.
The /M designation stands for Master or Main.
Note that “30T/M xxx” is the card type designation, whereas the system assigns a
30T identity through the Card List on page 6-59 and Port List on page 6-67.
There are four card databases (0 - 3), one of which is assigned to each T1 and 30T
digital trunk card (see Card List - Chapter 6). By default, Card Database 0 is
dedicated to 30T, and Card Database 1 is dedicated to T1.
FROM/ 0..3
TO 0..3
CARD_DB#
ALL: The following parameters apply to all trunk types.
O/G_BREAK [0] 18..61..90 ms (in 3 ms increments)

Outgoing Break Time determines the Break time during a rotary (pulse) dial cycle
T1 and 30T Card Database DTDB,1,0
from a trunk programmed as a pulse dialing trunk, during an outgoing call.

O/G_MAKE [1] 18..40..90 ms (in 3 ms increments)

Outgoing Make Time determines the period that loop current will be restored
during a rotary (pulse) dial cycle from a trunk programmed as a pulse dialing trunk,
O/G INDGT [2] 200..700..2550 ms (in 10 ms increments)

Outgoing Rotary Interdigit Time determines the period that loop current is restored
between digits being rotary (pulse) dialed from a trunk programmed as a pulse
dialing trunk port, during an outgoing call. (For DTMF trunk tones, see DTMF_
TONE beginning on page 6-5 in Feature Timers).
8-108
E&M: The following parameters apply only to incoming E&M Continuous calls.
I/C_BREAK [3] 30..90..250 ms (in 3 ms increments)

Incoming Break Time determines the maximum Break time, during a rotary
(pulse) dial cycle, for the trunk card to recognize the rotary dialed digits (“E” lead
remains interrupted).
I/C_MAKE [4] 30..90..250 ms (in 3 ms increments)

Incoming Make Time determines the maximum Make time between successive
Breaks while a digit is being rotary (pulse) dialed (“E” lead active). If signaling
current remains when this timer expires, the trunk card interprets the restoral as a
pause between digits or as end of digits.
LOGIC T1 Range: Not Applicable

(CEPT=Y/TDMX=N) [5] 30T Range: Y(CEPT)/N(TDMX)
 Not used in CC0 (USA) systems.

Choose Y for positive signalling over the trunk lines, such as the -CEPT (European
Conference of Postal and Telecommunications Administrations) protocol which
allows defining the system logic according to this general European standard.
Choose N for reverse signalling over the trunk lines when using products such as
the TDMX (TADIMUX- another communication product made by the same Coral
manufacturer).
DDO: The following parameters apply only to DDO calls via 30T card.
 The following parameters are only used for 30T DDO cards and are not used
in CC0 (USA) systems.

FAIL_SEIZE [6] 100..5000..10000 ms (in 100 ms increments)
Fail Seize Time determines the maximum system waiting time between seizure and
the seize acknowledgment signal. If seize acknowledgment is not recognized, after
a defined time-out period, the trunk is released by the system.
MIN_METER [7] 50..200 ms (in 10 ms increments)

Minimum Meter Pulse Recognition determines the minimum meter pulse duration.
The metering pulse interval must be between MIN_METER and MAX_METER in
order to be recognized by the 30T trunk. A metering pulse shorter than MIN_
METER is not recognized.
8-109
MAX_METER [8] 200..500..1000 ms (in 10 ms increments)

Maximum Meter Pulse Recognition determines the maximum meter pulse
duration. The metering pulse interval must be between MIN_METER and MAX_
METER in order to be recognized by the 30T trunk. A metering pulse longer than
MAX_METER is not recognized.
DID: The following parameters apply only to DID calls via 30T card.
 The following parameters are only used for 30T DDI cards and are not used in
CC0 (USA) systems.
MIN_BREAK [9] 20..40..70 ms (in 10 ms increments)

CC1: 20
Minimum Break Time determines the minimum period that loop signal must be
interrupted during a rotary (pulse) dial cycle for the trunk card to recognize rotary
dialing.
MAX_BREAK [10] 70..80..150 ms (in 10 ms increments)

CC1: 120
Maximum Break Time determines the maximum period that loop signal can remain
dialing.
MAX_(BREAK+MAKE) 100..200..250 ms (in 10 ms increments)

[11]
Maximum Break Plus Make time determines the maximum rotary (pulse) dial
cycle (Break + Make) duration, while a digit is rotary dialed.
DISCONNECT [12] 80..150..1000 ms (in 10 ms increments)

Minimum Disconnect Time determines the minimum disconnect signal time
period, during a call, in order for the system to identify disconnect.
SEIZE [13] 50..60..1000 ms(in 10 ms increments)

Minimum Seize Time determines the minimum period in which a trunk card must
detect a seize signal in order to identify an incoming seizure.
[14]
8-110
T1 and 30T Port Database ç DTDB,2,0

The circuit database allows programming the port database tables. There are four
digital trunk port databases (0-3). In default mode, Port Database 0 is dedicated to
30T, Port Database 1 is dedicated to T1. Field numbers appear in square brackets ([ ]).
FROM/ 0..3
TO 0..3
PORT_DB#
Enter the required range of port database tables; FROM the lowest table number
METERING [0] Yes/No
 Not used in CC0 systems.

For CC0 systems (North America), change the T1 default to No.
SUSP_SZE [1] 50..60..300 ms (in 10 ms increments)

PDB #1: 80 ms
Suspect Seize determines the waiting period for an incoming call signal at a trunk
port before the signal is recognized as a possible seize from an outside party, in
order to prevent glare.
MIN_SZE [2] 50..320..500 (in 10 ms increments)

PDB #1: 300 ms
Minimum Seize determines the additional period that an incoming call signal must
T1 and 30T Port Database DTDB,2,0

remain at a trunk port before the signal is recognized as an incoming call. Incoming
recognition time is actually SUSP_SZE + MIN_SZE (see Figure 8-3 on page 8-51).

Ground Start trunks PDB #1: 450 ms)
only
CO Block determines the timing of a blocking signal received from the Central
Office (ground or ring), i.e. the minimum duration without a ring until the system
interprets the signal as a block signal. The timer applies only to trunks defined as
Ground Start with Ring in the 4T/8T Card Database Branch (see C-gs with ring on
page 8-57). In a CO block state, the trunk is considered busy, thus prohibiting
outgoing trunk seizure. The system waits for ringing, before indicating an
incoming call.
8-111

entry, routine diagnostics periodically resend the card Database to the cards,
T1 and 30T Port Database DTDB,2,0
8-112
30T/M Cards ç
Details for the 30T/M trunks are found on the following pages:
30T/M Card Database ....................................................................... 8-114
30T/M DDI/DDO/BI-D Port Database............................................. 8-120
30T/M DDI Port Database................................................................ 8-122
30T/M Timers ................................................................................... 8-123
30T/M Cards
8-113
30T/M Card Database ç DTDB,1,2

The 30T/M card database establishes the card database for the E1 30 channel in
some countries. Some variations of the card (software only) are:
Mexican (30T/M), China (30T/M CHI), Brazil (30T/M BZL),
Argentina (30T/M ARG), Poland (30T M-PL), etc.
30T Office (30T or 30TM jumper selection).
Note that “30T/M xxx” is the card type designation. The system assigns a 30TM
identity through the Card List on page 6-59 and Port List on page 6-67.
There are two card databases (0 - 1), each of them can be assigned to one or more
30TM trunk cards (see Card List - Chapter 6). Field numbers appear in square
brackets ([ ]).
FROM/ 0..1
TO 0..1
CARD_DB#
O/G_BREAK [0] 10..65..120 ms

O/G_MAKE [1] 10..35..120 ms

30T/M Card Database DTDB,1,2
Outgoing Make Time determines the period between two successive “Break”
intervals during a rotary (pulse) dial cycle from a trunk programmed as a pulse
dialing trunk, during an outgoing call.
O/G_INDGT [2] 500..700..2550 ms (in 10 ms increments)

Outgoing Rotary Interdigit Time determines the period between two successive
“Break” intervals between digits being rotary (pulse) dialed from a trunk
programmed as a pulse dialing trunk port, during an outgoing call. (For DTMF
trunk tones, see DTMF_TONE beginning on page 6-5 in Feature Timers).
8-114
DISCONNECT Yes/No
RECALL [3] Mexico (CC2): Yes/No
 Notes:
• Relevant for CC1, CC2, CC3, CC5 and CC6 systems only.
• This feature is only available for 30TM cards with
Issue# 021004812 or higher.
Outgoing Calls Only: This parameter determines whether to ignore the CO_DISC
[2] (page 8-120) time interval and use a longer time interval: DISCONNECT RECALL
TIME [5] defined in the 30T/M DDI/DDO/BI-D Port Database beginning on page
8-120 for this card.
IGNORE SUPP#6 [4] Yes/No

Belgium and China (Eu1 & CC6): Yes/No
 This feature is only available for 30TM cards with

Outgoing Calls Only: This parameter enables using the Q.422 protocol instead of
the Q.422, Supp 6 protocol for outgoing calls, thereby disabling the metering pulse
signals from the far end towards the card during outgoing system calls.
ENABLE CCB? [5] Yes/No;

Brazil (CC3): Yes/No

Set this parameter to Yes to enable Call Collect Block, thereby disabling the
destination from receiving collect calls.
When this parameter is set to Yes, collect calls may be disabled at the destination

(as defined by its COS).
 The following four parameters are presented in order to define the signal
indicating the Call Collect Block.
During an incoming call, if the system destination is restricted by COS to accept
collect calls, the Coral signals the CO accordingly. The signaling pulse is defined
by the CCB_Tx time intervals as described in the sketch (CCB_T3 can be set to 0):
8-115
Figure 8-4.
CCB Pulse Signal
Line Answer CCB_T2 CCB_T2
CCB_T1 CCB_T3 CCB_T4 Line
CCB Pulse
The CO aborts a call if the destination responds with a CCB pulse pattern
CCB_T1 (10ms) [6] 0 (Enable CCB? = No;

1..255 units: Enable CCB? = Yes
Brazil (CC3): 1..15..255 (1 unit=10 ms)

Incoming Calls Only: When ENABLE CCB? [5] above is set to Yes, this parameter
defines the CCB_T1 time period.
CCB_T2 (10ms) [7] 0: Enable CCB? = No;

1..255 units: Enable CCB? = Yes;
Brazil (CC3): 1..30..255 (1 unit=10 ms)
 This feature is only available for 30TM cards,Issue# 021004812 or higher.

CCB_T3 (10ms) [8] 0..255 units (1 unit=10 ms)

CCB_T4 (10ms) [9] 0: Enable CCB? = No;

1..255 units: Enable CCB? = Yes
Brazil (CC3): 1..70..255 units (1 unit=10 ms)

8-116
CCB PULSE IGNORE 0..60 units (1 unit = 100ms)

TIME (100ms) [10] Brazil (CC3): 0..20..255
• Relevant only for DDO.
• This feature is only available for 30TM cards,Issue# 021004812 or
higher.
This parameter enables the card to disregard CCB signals sent towards the card by
defining a CCB Pulse Ignore time period in this parameter. Setting this parameter
to 0, disables the ignore CCB pulses (i.e. enables CCB signals). When no time
period is defined for this parameter some calls may be disconnected.
METER:
MIN_ON [11] 20..130..140 ms (in 10 ms increments)
Minimum Meter Pulse Recognition determines the minimum meter pulse duration.
The metering pulse interval must be between MIN_ON and MAX_ON in order to
be recognized by the 30T/M trunk. A metering pulse shorter than MIN_ON is not
recognized.
MAX_ON [12] 160..190..990 ms (in 10 ms increments)

Maximum Meter Pulse Recognition determines the maximum meter pulse
duration. The metering pulse interval must be between MIN_ON and MAX_ON in
order to be recognized by the 30T/M trunk. A metering pulse longer than MIN_ON
is not recognized.
MIN_OFF [13] 50..100..2500 ms (in 10 ms increments)

Minimum Time Between Meter Pulses defines the minimum period between meter
pulses in order to recognize the next pulse.

METER PULSE Yes/No;
ENABLE [14] CC1, CC2: Yes/No
CC6 (China):Yes/No: only for Bit A

When no R2_Signalling meter pulse information is sent (metering pulses from the
CO destination to the call initiator -DDO side), set this parameter to No to block
the card from recognizing these pulses.
8-117
DID: The following options are relevant only during incoming calls on DID type trunks.
MIN_BREAK [15] 10..40..70 ms

dialing. A break-time less than the defined period is not recognized by the system
as a break.
MAX_BREAK [16] 70..90..255 ms

Maximum Break Time determines the maximum period that a loop signal can
remain interrupted during a rotary (pulse) dial cycle for the trunk card to recognize
rotary dialing. A break-time greater than the defined period is not recognized by
the system as a break.
MIN_MAKE [17] 10..20..60 ms

Minimum Make Time determines the minimum Make (current restoral) period for
a loop signal during a rotary (pulse) dial cycle for the trunk card to recognize rotary
dialing. A make-time less than the defined period is not recognized by the system
as a break.
MAX_MAKE [18] 30..60..255 ms

Maximum Make Time determines the maximum Make (current restoral) period for
dialing. A make-time greater than the defined period is not recognized by the
system as a break.
E&M: The following parameters are relevant only for E&M Continuous type trunks.
I/C_MIN_BREAK [19] 10..30..60 ms

lead remains interrupted). A break-time greater that the defined period is not
recognized by the system as a break.
I/C_MAX_BREAK [20] 60..90..255 ms

lead remains interrupted). A break-time greater that the defined period is not
8-118
I/C_MIN_MAKE [21] 10..30..60 ms

successive Breaks while a digit is being rotary (pulse) dialed (“E” lead active). If
signaling current remains when this timer expires, the trunk card interprets the
I/C_MAX_MAKE [22] 60..90..255 ms

LOGIC (CEPT/TDMX) C(CEPT)/T(TDMX)

[23]
CEPT (European Conference of Postal and Telecommunications Administrations)
TDMX (TADIMUX - another communication product made by the same Coral
manufacturer) that allows defining the system so that 30 calls (analog or digital
channels, 64 Kbps data per channel) can be communicated along a pair of standard
telephone wires for remote subscribers. A choice of analog or digital channels
permits the interconnection of analog or digital PABXs, telephones or terminals.
BIT B VALUE [24] 1 (Bit B value is always 1)

2 (Bit B value takes Bit A’s value)
3 (Bit B value is always 0)

E & M Signalling protocol is based on changes in the bit signalling. For systems

where bit B is analyzed, define it in this parameter towards the far side.
DDO: The following parameters apply only to DDO type trunks.
FAIL_SEIZE [25] 20..50..255 units (1 unit = 100 ms)

the seize acknowledgment signal. If seize acknowledgment is not recognized, after
a defined time-out period, the trunk is released by the system.
[26]
8-119
30T/M DDI/DDO/BI-D Port Database ç DTDB,2,2,0

FROM/ 0..1
TO 0..1
PORT_DB#
SUSP_SZE [0] 20..30..50 ms (in 10 ms increments)

Suspect Seize determines the period that an incoming call signal must remain at a
trunk port before the signal is recognized as a possible seize from an outside party.
MIN_SZE [1] 50..70..1550 ms (in 10 ms increments)

recognition time is calculated as SUSP_SZE + MIN_SZE (see Figure 8-3 on page
8-51).
CO_DISC [2] 200..350..2550 ms (in 10 ms increments)

Central Office Disconnect determines the minimum waiting period for a trunk
disconnect signal before the system recognizes the signal as a valid call disconnect,
thereby releasing the trunk.

30T/M DDI/DDO/BI-D Port Database DTDB,2,2,0
Central Office Block determines the timing of a blocking signal received from the
Central Office.
This parameter defines the minimum period for the system to interpret the signal
as a block signal. In a CO block state the trunk is considered busy, thereby
preventing further use of the trunk.
SZ_ACK [4] Yes (Delay)/No (Immediate)

Seize Acknowledge determines when the signaling/handshaking protocol of the
incoming DID trunk is Delay Start or Immediate Start.
8-120
DISCONNECT 60..90..180 seconds

RECALL TIME [5]

This feature is only available for 30TM cards with
When DISCONNECT RECALL [3] (page 8-115) is set to Yes in the Card database, this
parameter defines the time period for which the CO Disconnect is extended in order
to verify the CO disconnect.

Transfers the updated port database immediately to the trunk cards. Regardless of
30T/M DDI/DDO/BI-D Port Database DTDB,2,2,0
8-121
30T/M DDI Port Database ç DTDB,2,2,1

FROM/ 0..1
TO 0..1
PORT_DB#

Central Office Disconnect determines the minimum period for a disconnect signal
from a trunk that must remain before the system recognizes the signal as a valid
call disconnect, thereby releasing the trunk.

Determines the timing of a blocking signal received from the Central Office. This
parameter allows the minimum period until the system interprets the signal as a
block signal to be defined. In a CO block state the trunk is considered busy, thereby
preventing further use of the trunk.
DISCONNECT N/A
RECALL TIME [4]
Not Relevant for DDI.

including any update made. This parameter is used only in Update Mode.
30T/M DDI Port Database DTDB,2,2,1
8-122
30T/M Timers ç TRUNK,6

The following timers apply when the Coral system releases trunks before the
Central Office, but the CO is also expected to release. Both timers allow the
maximum waiting period, for a disconnect acknowledgment signal from the CO,
before the Coral blocks the trunk line to be defined.
DDO_DELAY_TO_ 1..1800..36000 1 unit=0.1 second

BLOCK
Applies to DDO trunks.
DDI_DELAY_TO_ 1..900..36000 1unit=0.1 second

BLOCK
Applies to DDI trunks.
30T/M Timers TRUNK,6
8-123
30T/E Cards ç
Details for the 30T/E trunks are found on the following pages:
30T/E Card Database ........................................................................ 8-125
30T/E DDI Port Database................................................................. 8-130
30T/E DDO Port Database ............................................................... 8-132
30T/E NonDDI Port Database .......................................................... 8-133
30T/E Cards
8-124
30T/E Card Database ç DTDB,1,1

Utilized only in European Systems
The 30T/E card database establishes the card database for E1 30 channel European
standard systems. There are two card databases (0 - 1), one of which is assigned to
each 30T/E digital trunk card (see Card List - Chapter 6). Field numbers appear in
FROM/ 0..1
TO 0..1
CARD_DB#
O/G_BREAK [0] 10..65..120 ms

O/G_MAKE [1] 10..35..120 ms

Outgoing Make Time determines the period in which loop current is restored
during a rotary (pulse) dial cycle from a trunk programmed as a pulse dialing trunk,
O/G_INDGT [2] 500..700..2550 (in 10 ms increments)

Outgoing Rotary Interdigit Time determines the period in which loop current is
30T/E Card Database DTDB,1,1

restored between digits being rotary (pulse) dialed from a trunk programmed as a
pulse dialing trunk port, during an outgoing call. (For DTMF trunk tones, see
DTMF_TONE beginning on page 6-5 in Feature Timers).
METER:
MIN_ON [3] 20..100..120 (in 10 ms increments)
Minimum Meter Pulse Recognition. The 30T/E trunk detects an active metering
pulse signal only if the pulse is shorter than MAX_ON defined below and longer
than MIN_ON defined here.
8-125
MAX_ON [4] 180..200..990 (in 10 ms increments)

Maximum Meter Pulse Recognition. The 30T/E trunk detects an active metering
pulse signal only if the pulse is shorter than MAX_ON defined here and longer than
MIN_ON defined above.
MIN_OFF [5] 200..2550(in 10 ms increments)

Minimum Time Between Meter Pulses determines the minimum period between
meter pulses so that the next pulse may be identified.
8-126
Eu0 systems only
DID: The following options apply only during incoming calls on DID type trunks.
MIN_BREAK [6] 10..40..70 ms

dialing. A break-time less than the defined period is not recognized by the system
as a break.
MAX_BREAK [7] 70..90..255 ms

Maximum Break Time determines the maximum period that a loop signal can
rotary dialing. A break-time greater than the defined period will not be recognized
by the system as a break.
MIN_MAKE [8] 10..20..60 ms

Minimum Make Time determines the minimum Make (current restoral) period for
a loop signal to exist during a rotary (pulse) dial cycle for the trunk card to
recognize rotary dialing. A Make time less than the defined period is not
MAX_MAKE [9] 30..60..255 ms

Maximum Make Time determines the maximum Make (current restoral) period for
dialing. A Make time greater than the defined period will not be recognized by the
system as a break.
8-127
E&M: The following parameters apply only to E&M Continuous type trunks.
I/C_MIN_BREAK [10] 10..30..60 ms

lead remains interrupted). A Break time greater that the defined period is not
I/C_MAX_BREAK [11] 60..90..255 ms

lead remains interrupted). A Break time greater that the defined period is not
I/C_MIN_MAKE [12] 10..30..60 ms

I/C_MAX_MAKE [13] 60..90..255 ms

LOGIC (CEPT/TDMX) C(CEPT)/T(TDMX)

[14]
CEPT (European Conference of Postal and Telecommunications Administrations)
TDMX (TADIMUX- another communication product made by the same Coral
manufacturer) that allows defining the system so that 30 calls (analog or digital
channels, 64 Kbps data per channel) can be communicated along a pair of standard
telephone wires for remote subscribers. A choice of analog or digital channels
permits the interconnection of analog or digital PABXs, telephones or terminals.
DDO: The following parameter applies only to DDO type trunks.
FAIL_SEIZE [15] 20..50..5000 (1 unit = 100 ms)

the seize acknowledgment signal. If seize acknowledgment is not recognized after
a defined time-out period, the trunk is released.
8-128
[16]
including any update. This parameter is used only in the Update Mode.
8-129
30T/E DDI Port Database ç DTDB,2,1,0

Utilized only in European Systems
FROM/ 0..1
TO 0..1
PORT_DB#
SUSP_SZE [0] 20..30..50 (in 10 ms increments)

outside party.

continuously remain at a trunk port before the signal is recognized as an incoming
call. Incoming recognition time is measured as SUSP_SZE + MIN_SZE (see
Figure 8-3 on page 8-51).
CO_DISC [2] 200..350..2550 (in 10 ms increments)

Central Office Disconnect determines the minimum period for a trunk disconnect
signal before the system recognizes the signal as a valid call disconnect, thereby
releasing the trunk.
30T/E DDI Port Database DTDB,2,1,0
CO_BLOCK [3] 60..350..1000 (in 10 ms increments)

Eu0 only
Central Office Block determines the blocking signal timing received from the
Central Office by defining the minimum period until the system interprets the
signal as a block signal. In a CO block state, the trunk is considered busy
preventing further trunk use.
MIN_EOS [4] 0..2550 (in 10 ms increments)

Eu0 only
The Minimum End-Of-Selection timer determines the minimum period that the
voltage polarity across the TT-TR must be reversed by the Central Office, after dial
outpulsing, for the trunk card to recognize EOS. This option is used for both Pulse
and DTMF dialing. The EOS is sent by the CO to the Coral after the last dialed digit
is accepted by the CO. The Coral responds by a line terminator of 0 - 560.
This signal is also called Number Received Signal.
8-130
SZ_ACK [5] Yes (Delay)/No (Immediate)

Eu0, Eu1 only

entry, routine diagnostics periodically resend the card Database to the cards,
including any update. This parameter is used only in the Update Mode.
30T/E DDI Port Database DTDB,2,1,0
8-131
30T/E DDO Port Database ç DTDB,2,1,1

Utilized only in Eu1, Eu2 and Eu3 systems
FROM/ 0..1
TO 0..1
PORT_DB#


Central Office Block determines the timing for a blocking signal received from the
Central Office, by defining the minimum period until the system interprets the
signal as a block signal. In a CO block state, the trunk is considered busy, thereby
RECONNECT [6] Yes/No

Allows defining whether or not a reconnect takes place after a Central Office
disconnect is carried out. The reconnect wait period is defined below in SEC.
SEC [7] 1..60..255 seconds
 This parameter appears only when RECONNECT [6], above, is set to Yes.
30T/E DDO Port Database DTDB,2,1,1
Defines the system waiting time (in seconds) before a reconnect is actually
performed.

8-132
30T/E NonDDI Port Database ç DTDB,2,1,2

Utilized only in Eu0 systems (Netherlands)
FROM/ 0..1
TO 0..1
PORT_DB#
SUSP_SZE [0] 20..30..50 ms(in 10 ms increments)

Determines the period that an incoming call signal must remain at a trunk port
before the signal is recognized as a possible seize from an outside party.
MIN_SZE [1] 50..70..1500 ms(in 10 ms increments)

Determines the additional period that an incoming call signal must remain at a
trunk port before the signal is recognized as an incoming call. Incoming
recognition time is measured as SUSP_SZE + MIN_SZE (see Figure 8-3 on page
8-51).
CO_DISC [2] 200..350..2550 ms(in 10 ms increments)

Central Office Disconnect determines the minimum time interval for a disconnect
trunk signal before the system recognizes the signal as a valid call disconnect and
releases the trunk.
CO_BLOCK [3] 60..350..1000 ms(in 10 ms increments)
30T/E NonDDI Port Database DTDB,2,1,2

Central Office, by defining the minimum period for the system to interpret the
signal as a block signal. In a CO block state the trunk is considered busy, thereby
MIN_EOS [4] 0, 200..2550 ms(in 10 ms increments)

Minimum End-Of-Selection determines the minimum period that the voltage
polarity across the TT-TR must be reversed by the Central Office, after dial
out-pulsing, for the trunk card to recognize EOS. This option is used for both Pulse
This signal is also called Number Received Signal.
8-133

30T/E NonDDI Port Database DTDB,2,1,2
8-134
ALS70 Cards ç TRUNK,3 [0,2,1,0,3]

Details for the ALS70 trunks are found on the following pages:
ALS70 Card Configuration............................................................... 8-136
ALS70 Card Database ...................................................................... 8-138
ALS70 Port Database........................................................................ 8-141
ALS70 Loop Start Port Database ..................................................... 8-142
ALS70 DID Port Database ............................................................... 8-143
ALS70 NonDID Port Database ........................................................ 8-144
ALS70 Trunk Timers ........................................................................ 8-145
ALS70 (Abonnee Lijn Signalering 1970) trunks can be defined as one of the
following trunk types:
• Loop Start
• DID
• NonDID
Additionally, each of the various types of ALS70 trunks can have the following
attributes:
• Defined as both incoming and outgoing trunks
• Receiving and detecting Meter Pulse (4ALS/M and 8ALS/M cards)
• Trunk group membership, see Trunk Group Definition beginning on page 8-18,
where the default is the first group, (dial #0), including all the ALS70 trunks.
A DID type-defined trunk can belong to a DID/E&M group (see page 8-36), with
incoming signals sent directly to the destination station. However, trunks defined
as either LS or NonDID, connect the line directly to a predefined station.
 The suffix /M added to the card name means: Built-In Metering Hardware,
ALS70 Cards TRUNK,3 [0,2,1,0,3]

for example 4ALS/M or 8ALS/M. This information is printed on the card
front panel. However, the /M feature is neither shown in the Card List nor
Port List menus.
8-135
ALS70 Card Configuration ç TRUNK,3,0 [0,2,1,0,3,0]

Determines the port type for each trunk according to the port location (shelf
number, slot number and circuit). Only a slot initialized as an ALS card can be
accessed through this option. A 4ALS card includes four trunk ports; 8ALS
includes eight trunk ports. A trunk port can be defined as any one of the following
types: LS (Loop Start), DID (Direct Inward Dial) or NonDID.
The card database configuration must match the option strapping on the card (See
the relevant Coral Installation Manual).
FROM/TO SHELF # All available Shelves

2..3: Coral IPx Office expansion cage 800X

1..2: Coral IPx 500 expansion cage 800X
0..2: Coral IPx 800
0..15: Coral IPx 3000, 4000
Enter the required range of shelf location numbers, FROM the lowest shelf number
TO the highest shelf number.
FROM/TO SLOT # All Available Slots;

ALS70 Card Configuration TRUNK,3,0 [0,2,1,0,3,0]

Enter the required range of slot location numbers, FROM the lowest slot number
TO the highest slot number.
CARD 
4ALS, 8ALS
Displays the initialized card name. The prefix digit indicates the total number of
available ports.
8-136
CKT# 0 (LS), 1 (DID), 2 (NonDID)

Displays the card layout for each of the eight (0-7) circuits.
Circuits 0-3 are used by both 4ALS and 8ALS type cards. Circuits 4-7 are restricted
to 8ALS type cards only.
! Changing the DID definition excludes the trunk from the DID/E&M
group.
UPDATE (Y/N)? Yes/No

Transfers the updated card configuration, immediately to the trunk card and
database. When No is selected, all entries are ignored and the card ports remain as
previously defined. Modification occurs when Yes is entered. This parameter is
used only in the Update Mode.
! When ALS is installed, selecting Yes resets the card and disconnects
all established calls.
ALS70 Card Configuration TRUNK,3,0 [0,2,1,0,3,0]
8-137
ALS70 Card Database ç TRUNK 3,1 [0,2,1,0,3,1]

ALS70 Card Database establishes the card database for trunk cards 4ALS
and 8ALS. The system allows for a maximum total of four ALS card database
combinations (0-3), one of which is assigned to each card (see Card List - Chapter
6). The Coral makes no logical distinction between 4ALS and 8ALS cards.
FROM/TO CARD_DB 0..3

0..3
Enter the required range of ALS70 card database tables, FROM the lowest table
INCOMING: The following options apply only during incoming calls on ALS70-DID trunks.
MIN_BREAK [0] 20..30..70 ms

DID Minimum Break Time determines the minimum period in which the loop
current must be interrupted during a rotary (pulse) dial cycle for the trunk card to
recognize rotary dialing. A Break time less than the defined period is not
MAX_BREAK [1] 30..90..100 ms

ALS70 Card Database TRUNK 3,1 [0,2,1,0,3,1]
DID Maximum Break Time determines the maximum period that a loop signal can
rotary dialing. A break-time greater than the defined period is not recognized by
the system as a break.
MIN_MAKE [2] 10..16..60 ms

DID Minimum Make Time determines the minimum Make (current restoral)
period for the loop current to exist during a rotary (pulse) dial cycle for the trunk
card to recognize rotary dialing. A Make time less than the defined period is not
recognized by the system as a make.
MAX_MAKE [3] 30..100 ms

DID Maximum Make Time determines the maximum Make (current restoral)
period for the loop current to exist during a rotary (pulse) dial cycle for the trunk
card to recognize rotary dialing. A Make time greater than the defined period is not
recognized by the system as a make.
8-138
LS_RING_PAUS [4] 1..5..12 seconds

Loop Start Ring Pause determines the minimum period that the ring generator is
off during an incoming call, before the system terminates the call. Disconnect takes
place before the call is answered or interrupted. This timer applies only to trunks
defined as Loop Start (LS) in the ALS70 Configuration Definition and Check Ring
in ALS70-LS Port Database. The entry should be at least one second greater than
the normal interval between ring bursts from the Central Office.
DID_DISC_BEFORE_ 100..320..2550 (in 10 ms increments)

ANS [5]
DID Disconnect Before Answer determines the minimum period that the loop
current must be reversed during an incoming call before the system terminates an
incoming call indication. This timer applies only to trunks defined as DID in the
ALS70 Configuration Definition.
NONDID_RING_PAUS 100..320..2550 (in 10 ms increments)

[6]
NonDID Disconnect Before Answer determines the minimum period that the loop
current must be reversed during an incoming call before the system terminates an
incoming call indication. This timer applies only to trunks defined as NonDID in
the ALS70 Configuration Definition.
OUTGOING: The following options apply only during outgoing calls on ALS70 trunks.
BREAK_TIME [7] 21..59..90 (in 3 ms increments)

Outgoing Break Time determines the period that loop current is interrupted during
a rotary (pulse) dial cycle from a rotary dialing trunk port during an outgoing call.

Signaling method is defined in TYPE [4] (page 8-12).
MAKE_TIME [8] 21..39..90 (in 3 ms increments)

Outgoing Make Time determines the period that loop current is restored during a
Signaling method is defined in TYPE [4] (page 8-12).
INTERDGT_T [9] 200..700..2550 (in 10 ms increments)

Outgoing Rotary Interdigit Time determines the period that loop current is restored
between digits being rotary (pulse) dialed from a rotary dialing trunk port during
an outgoing call.
Signaling method is defined in TYPE [4] (page 8-12). (For DTMF trunk tones, see
DTMF_TONE beginning on page 6-5 in Feature Timers).
8-139
METER: The following parameters define the METER signal (sent by the CO in order to
define a meter pulse). This option applies to 4ALS/M and 8ALS/M cards only.
f0 [10] 0 (16kHz), 1 (12kHz), 2 (50kHz)

Identifies the frequency sent by the CO to define a meter pulse. Although 12 and
16 kHz are displayed, currently only 50Hz is available. Therefore only enter 2 for
this parameter.
f0 Accuracy (1 - 10)% 1..3..10 1 unit = 1%;

12/16kHz only [11]
Identifies the accuracy of the meter pulse frequency sent by the CO.
f0 Accuracy (5, 10)% 5..10 1 unit = 1%

50Hz only [12]
Identifies the accuracy of the meter pulse frequency sent by the CO.
MIN_METER [13] 50..70..200 (in 10 ms increments)

Minimum Meter Pulse. The ALS70 trunk detects an active metering pulse signal,
with the defined frequency, only if the pulse is shorter than MAX_METER defined
below and longer than MIN_METER defined here.
MAX_METER [14] 200..250..1000(in 10 ms increments)

Maximum Meter Pulse. The ALS70 trunk detects an active metering pulse signal,
with the defined frequency, only if the pulse is shorter than MAX_METER defined
here and longer than MIN_METER defined above.
[15]
entry, routine diagnostics periodically resend the database to the cards, including
any updates made. This parameter is used only in the Update Mode.
8-140
ALS70 Port Database ç TRUNK,3,2 [0,2,1,0,3,2]

The ALS70 Trunk Port Database allows programming the trunk port database
tables for Loop Start, DID and NonDID trunk ports connected to 4ALS or 8ALS
cards. There are 4 Trunk Port Databases (0-3) for each trunk type, one of which is
assigned to each trunk port (see Port List - Chapter 6). Field numbers appear in
Access Option Full Name Mnemonic

0 LS Loop Start TRUNK,3,2,O
1 DID Direct Inward Dial TRUNK,3,2,1
2 NonDID Non Direct Inward Dial TRUNK,3,2,2
Each option is discussed below.
FROM/TO PORT_DB# 0..3

0..3
Enter the required range of port database tables; FROM the lowest port database
table number TO the highest port database table number.
ALS70 Port Database TRUNK,3,2 [0,2,1,0,3,2]
8-141
ALS70 Loop Start Port Database ç TRUNK,3,2,0 [0,2,1,0,3,2,0]

Suspect Seize determines the period that an incoming call signal must remain at a
trunk port before the signal is recognized as a seize from an outside party. This is
done in order to prevent glare.


CHECK_RING [5] Yes/No

Check Incoming Seize Ring. An incoming trunk seize may be accompanied with a
ring current. This option allows the system to check the ring cadence. (See ALS70
LS_RING_PAUS [4] on page 8-139).
ALS70 Loop Start Port Database TRUNK,3,2,0

8-142
ALS70 DID Port Database ç TRUNK,3,2,1 [0,2,1,0,3,2,1]

SUSP_SZE [0] 10..30 (in 10 ms increments)
Suspect Seize determines the period that an incoming call signal (polarity reversal)
must remain at a trunk port before the signal is recognized as a seize from an
outside party.



ALS70 DID Port Database TRUNK,3,2,1 [0,2,1,0,3,2,1]

polarity across the TT-TR must be reversed by the Central Office (CO), after dial
outpulsing, for the trunk card to recognize EOS. This option is used for both Pulse
This signal is also called Number Received signal.
SZE_ACK [4] Yes (Delay)/No (Immediate)


8-143
ALS70 NonDID Port Database ç TRUNK,3,2,2 [0,2,1,0,3,2,2]

Suspect Seize determines the period that an incoming call signal (polar reversal)
must remain at a trunk port before the signal is recognized as a possible seize from
an outside party thus preventing glare.

8-51).


polarity across the TT-TR must be reversed by the Central Office (CO), after dial
out-pulsing, for the trunk card to recognize EOS. This option is used for both Pulse
ALS70 NonDID Port Database TRUNK,3,2,2
is accepted by the CO. The Coral responds by a line terminator of 0 - 560. This
signal is also called Number Received signal.
CHECK_RING [5] Yes/No

Check Incoming Seize Ring determines whether an incoming trunk seize may be
accompanied with a ring current. This option allows the system to check the ring
cadence. (see ALS70 NONDID_RING_PAUS [6] on page 8-139).

8-144
ALS70 Trunk Timers ç TRUNK 3,3 [0,2,1,0,3,3]

Only one timer is available for this option.
DELAY_TO_BLOCK 1..100..600 1 unit=0.1 second

Delay Before Trunk Block defines the maximum system waiting time for a
disconnect acknowledgment signal from the Central Office, before the system
blocks the trunk line. When the trunk is blocked the call is either transferred to an
incomplete call destination or calls toward the CO are blocked. This timer is
applied when the Coral releases first and the CO release is pending.
ALS70 Trunk Timers TRUNK 3,3 [0,2,1,0,3,3]
8-145
BID Cards ç TRUNK,4 [0,2,1,0,4]
Utilized only in Eu1 Systems (Belgium)

The BID (Belgium Inward Dialing) card is the incoming call interface between the
Belgium Regie of Telegraphy and Telephony (RTT) and the Coral system. The BID
card has a capacity of four (4BID) or eight (8BID) ports. The BID card provides
the subscriber with the ability to receive calls directly at the station, without first
being routed through an attendant. The BID card acts as a Direct Inward Dialing
device.
The sole function of this card is to identify an incoming seizure, as well as connect
and disconnect signals of the DID channel by reversing polarity (line-signaling).
Dial number detection (register signaling) is carried out by the MFC protocol,
using the 16MFR card.
 The BID card cannot operate without an MFR card installed in the system.
The following BID options are available and are described in the following pages:
BID Trunk Port Database ................................................................. 8-147
BID Trunk Timers............................................................................. 8-149
Option Full Name Access Mnemonic
PORT_DB Port Database 0 TRUNK 4,0
TIMERS Trunk Timers 1 TRUNK 4,1

BID Cards TRUNK,4 [0,2,1,0,4]
8-146
BID Trunk Port Database ç TRUNK 4,0 [0,2,1,0,4,0]

The BID Trunk Port Database allows programming the trunk port database tables
for DID trunk ports connected to 4BID or 8BID cards. There are 4 Trunk Port
Databases (0-3), one of which is assigned to each trunk port (see Port List -
Chapter 6). Field numbers appear in square brackets ([ ]).
FROM/TO PORT_DB# 0..3

0..3
Enter the required range of BID Port database tables; FROM the lowest port
database table number TO the highest port database table number.
SUSP_SZE [0] 20..200 (in 10 ms increments)

Suspect Seize determines the minimum period that an incoming call signal
(polarity reversal) must remain at a trunk port before the signal is recognized as a
possible seize from the CO. During the idle state, the voltage across the tip and ring
is -48V and the DC current is between 5mA and 90mA. During an incoming call
the line polarity is reversed.

Minimum Seize determines the additional period that an incoming call signal
(polarity reversal) must remain at a trunk port before the signal is recognized as an
incoming call. Incoming recognition time is measured as SUSP_SZE + MIN_SZE
BID Trunk Port Database TRUNK 4,0 [0,2,1,0,4,0]

(see Figure 8-3 on page 8-51).
As a response to a seizure, the Coral changes the loop impedance from 500 to
15k.


Central Office Disconnect determines the minimum period for a disconnect signal
(polarity reversal) before the Coral recognizes the signal as a valid call disconnect,
thereby releasing the trunk. Upon CO disconnect the Coral changes the DC
resistance to greater than 1m.
8-147

CO (polarity reversal). It defines the minimum time until the system interprets the
signal as a block signal.
In a CO block state, the trunk is considered busy, resulting in only information,
since the trunk is only available for incoming calls.

BID Trunk Port Database TRUNK 4,0 [0,2,1,0,4,0]
8-148
BID Trunk Timers ç TRUNK 4,1 [0,2,1,0,4,1]

Only one timer is included in this option.
DELAY_TO_BLOCK 1..600..65534 1unit = 0.1 second

Defines the maximum system waiting time for a disconnect acknowledgment
signal from the Central Office before blocking the trunk line. This timer applies
when the Coral releases first and the Central Office release is pending. The call is
disconnected by causing a resistance change from 500 to 15k. Therefore, CO
acknowledgment is accomplished through polarity reversal. Once the polarity
reversal is recognized, the Coral changes the DC resistance to more than 1m.
BID Trunk Timers TRUNK 4,1 [0,2,1,0,4,1]
8-149
GID Cards ç TRUNK,5 [0,2,1,0,5]
Utilized only in Eu2 Systems (Germany)

The GID (German Inward Dialing) card is the interface between the German Post,
Telegraph and Telephone (PTT) and the Coral system.
The GID card is a duplex outgoing/incoming analog device with capacity for four
(4GID) or eight (8GID) ports. GID allows the subscriber to receive calls directly at
the extension within the system, as well as to dial out. The GID cards can function
with any one of the following types of Central Offices: EWSO 1, S55V and DIV0
(called Local EXchange - LEX).
 GID is compatible only with pulse dialing. Do not program with DTMF.
The following GID options are available and are described in the following pages:
GID Card Database ........................................................................... 8-151
GID Port Database ............................................................................ 8-155
GID Timers ....................................................................................... 8-157
Option Full Name Access Mnemonic

CARD_DB Card Database 0 TRUNK 5,0
PORT_DB Port Database 1 TRUNK 5,1
TIMERS Trunk Timers 2 TRUNK 5,2

GID Cards TRUNK,5 [0,2,1,0,5]
8-150
GID Card Database ç TRUNK 5,0 [0,2,1,0,5,0]

GID Card Database establishes the card database for 4GID and 8GID trunk cards.
The system allows for a maximum of four GID card database combinations (0-3),
one of which is assigned to each card (see Card List - Chapter 6). The Coral makes
no logical distinction between 4GID and 8GID cards. Field numbers appear in
FROM/TO CARD_DB 0..3

0..3
Enter the required range of GID card database tables; FROM the lowest table
INCOMING: The following options apply only during incoming calls on GID trunks.
MIN_BREAK [0] 20..35..100 ms

Minimum Break determines the minimum period that a loop signal must be
dialing. A Break time less than the defined period is not recognized by the system
as a Break.
MAX_BREAK [1] 30..85..150 ms

Maximum Break determines the maximum period that a loop signal can remain
GID Card Database TRUNK 5,0 [0,2,1,0,5,0]

dialing. A Break time greater than the defined period is not recognized by the
system as a Break.
MIN_MAKE [2] 20..25..100 ms

Minimum Make determines the minimum make (current restoral) period that loop
signal must exist during a rotary (pulse) dial cycle for the trunk card to recognize
rotary dialing. A Make time less than the defined period is not recognized by the
system as a make.
MAX_MAKE [3] 25..60..100 ms

Maximum Make determines the maximum Make (current restoral) period for a
loop signal to exist during a rotary (pulse) dial cycle for the trunk card to recognize
rotary dialing. A Make time greater than the defined period is not recognized by
the system as a make.
8-151
Clear Down: The following two parameters define the Clear Down pulse duration allowed by the
Coral.
Clear Down is a disconnect pulse sent from the LEX to the Coral. Clear Down is
a 90Vrms/50Hz pulse and can be initiated by the LEX at any stage. When a Clear
Down signal is sensed, the Coral switches to idle.
MIN_CLEAR_DOWN 40..80..1000 in 20 ms increments

[4]
Determines the minimum period for the GID card to detect an active signal in order
to identify the Clear Down from the LEX.
MAX_CLEAR_DOWN 40..200..1000 in 20 ms increments

[5]
Determines the maximum period for the GID card to detect an active signal in order
to identify the Clear Down signal from the LEX.
 The following two parameters define the Flash Clear pulse sent by the Coral.
Flash Clear: Is a Clear Backward signal sent from the Coral. This Clear Backward pulse initiates
a disconnect while Coral is in the connect state. To send this pulse, the GID card
sends a series of on/off pulses on the TR lead, which are created by connecting a
small resistance to the line for a brief period (on), and stopping the pulse for an
additional period (off). The combination of brief on/off pulses causes the Flash
Clear signal. The duration of these pulses is defined through Coral parameters
FLASH_CLEAR_OFF and FLASH_CLEAR_ON, described below.
FLASH_CLEAR_ON 100..150..210 (in 10 ms increments)

[6]
Determines the duration of the FLASH_CLEAR_ON signal, that is, the time that a
small resistance is connected to the TR lead.

FLASH_CLEAR_OFF 200..450..600 (in 10 ms increments)

[7]
Determines the OFF period between the FLASH_CLEAR_ON pulses. The OFF
pulse is created by removing the resistance from the TR lead set up in FLASH_
CLEAR_ON.
8-152
OUTGOING: The following options apply only during outgoing calls on GID trunks. The pulse
signaling method is defined in TYPE [4] (page 8-12).
BREAK_TIME [8] 54..60..66 (in 3 ms increments)

Outgoing Break determines the period that loop current is interrupted during a
MAKE_TIME [9] 36..39..45 (in 3 ms increments)

Outgoing Make determines the period that loop current is restored during a rotary
(pulse) dial cycle from a rotary dialing trunk port during an outgoing call.
INTER_DIGIT_TIME 640..700..2500 (in 10 ms increments)

[10]
Outgoing Interdigit Time determines the period that loop current will be restored
between digits being rotary (pulse) dialed during an outgoing call.
CLEAR_FWD_TIMER 300..1400..2500 (in 10 ms increments)

[11]
Clear Forward Timer defines the duration of the disconnect signal sent by the
Coral. On outgoing calls the Coral can initiate the disconnect by opening the
current loop for the period defined in this parameter.
METER: The following parameters identify METER (the frequency sent by the LEX (CO)
to define a meter pulse). The first metering pulse sent from the LEX is guaranteed
only after the Coral has made the transition to connect state.
F0_ACCURACY [12] 0..2..5 1 unit = 1%

Identifies the accuracy of the meter pulse 16 kHz frequency sent by the LEX.
MIN_METER [13] 48..80..352 (in 8 ms increments)

Minimum Meter Pulse Recognition. The GID trunk detects an active metering
pulse signal only if the pulse is shorter than MAX_METER defined below and
longer than MIN_METER defined here.
MAX_METER [14] 88..368..1000 (in 8 ms increments)

Maximum Meter Pulse Recognition. The GID trunk detects an active metering
pulse signal only if the pulse is shorter than MAX_METER defined here and longer
than MIN_METER defined above.
MIN_OFF [15] 100..400..2500 (in 10 ms increments)

Minimum Time Between Meter Pulses defines the minimum period allowed
between consecutive metering pulses thus identifying the next pulse.
8-153
TRUNK CODE: Used for long distance LEX (CO) incoming DID calls. Applicable only for EWS01
and DIVO Central Offices. Used in Western Germany.
TIME_TO_EOD [16] 200..1000 (in 10 ms increments)

Time to End of Dial defines the minimum delay time between recognizing the last
correct system dial number (digit) sent by the LEX until the End-Of-Dial (EOD)
signal is sent from the Coral.
END_OF_DIAL [17] 100..150..200 (in 10 ms increments)

Determines the duration of the End Of Dial signal, sent from the Coral, after a dial
number is accepted.
TIME_TO_BUSY [18] 200..700..900 (in 10 ms increments)

Determines the delay time between the end of the EOD signal and the start of the
busy signal sent from the Coral.
BUSY_SIGNAL [19] 600..750..900 (in 10 ms increments)

Determines the duration of the busy signal sent from the Coral. The busy signal is
sent with a delay after the EOD signal when the called station is busy. Busy tone is
sounded after transmitting the signal.
START_SIGNAL [20] 100..150..200 (in 10 ms increments)

Determines the duration of the start signal sent from the Coral. The start signal is
sent after the called station answers the call (off-hooks). After the end of the start
signal the Coral goes to a connect state and reverses the voltage polarity across the
TT and TR. This signal is not sent without a trunk code.

MIN_TC [21] 10..66..84

Minimum Trunk Code determines the minimum period in which the GID card must
detect an active TC signal in order to identify the Trunk Code signal. The TC signal
is sent by the LEX at the beginning of each digit to inform the Coral if the call
management is performed according to the incoming Traffic with Trunk Code
protocol.
[22]
8-154
GID Port Database ç TRUNK 5,1 [0,2,1,0,5,1]

The GID Trunk Port Database programs the trunk port database tables for DID
trunk ports connected to 4GID or 8GID cards. There are 4 Trunk Port Databases
(0-3), one of which is assigned to each trunk port (see Port List - Chapter 6).
FROM 0..3
TO 0..3
PORT_DB#
Enter the required range of port database tables; FROM the lowest port database
table number TO the highest port database table number.

Suspect Seize determines the minimum period that an incoming call signal must
remain at a trunk port before the signal is recognized as a seize from the LEX, thus
preventing glare.

8-51).
The Coral responds by reversing the polarity.
GID Port Database TRUNK 5,1 [0,2,1,0,5,1]



LEX, thus defining the minimum period before the system interprets the signal as
a block signal. In a CO block state, the trunk is considered busy, thereby preventing
further trunk use. Central Office Blocking is performed by opening the current
loop.
8-155

GID Port Database TRUNK 5,1 [0,2,1,0,5,1]
8-156
GID Timers ç TRUNK 5,2 [0,2,1,0,5,2]

One timer is included in this option.
GID_TEST_DURATION 1..30..65534 (1 unit = 0.1 second)

Determines the maximum interval that an incoming call from the LEX to the DID
Test Number remains in a connected state before the Coral disconnects the call.
The DID Test Number is a feature code defined in the system numbering plan (see
Table 5-3, DID Test Number, index number 186). This number is used by the LEX
as a test port and is not a physical port.
The LEX initiates an incoming test call to this logical port as required for
diagnostic purposes. The GID card responds to this call as if it were a regular call
with Auto Answer and Auto Disconnect, after the GID_TEST_DURATION.
GID Timers TRUNK 5,2 [0,2,1,0,5,2]
8-157
GID Timers TRUNK 5,2 [0,2,1,0,5,2]
8-158
9 Station Controls
The Station Controls contain the programming instructions for all the different
station types.
Station Timers...............................................................................................9-2
SLT Definition ..............................................................................................9-5
SLT: iDSP Card (Caller ID Type Bellcore/ETSI) Database......................9-19
SLT Card Database.....................................................................................9-20
Keyset Timers .............................................................................................9-27
Keyset Ring Cadence .................................................................................9-29
Keyset Definition........................................................................................9-31
Keyset Button - Programming ...................................................................9-77
Keyset Fixed System Keys - Programming.............................................9-103
Keyset Soft Keys Idle Set ........................................................................9-104
Keyset Preference - Programming ........................................................... 9-118
APA, PEX/APA and APDL RS-232 Setup ..............................................9-120
Wireless Stations - CoralAIR ...................................................................9-123
Magneto 8SM Card Database ..................................................................9-126
9-1
Station Controls PI Reference Manual
Station Timers ç ST.T [0,0,1,1]
Station Timers define the various timers for all station features system wide.
RING [0] 1..450..10000 (1 unit = 0.1 second)

CC1: 600
Defines the ringback tone duration to an internal station before the system
disconnects or forwards the call to a call forward no answer destination.
MULT_APR_RING [1] 1..900..9000 (1 unit = 0.1 second)
 This timer is also utilized for 1Boss Groups, see Note 1 on page 10-21.
Multi-Appearance Ringback defines the ringback tone duration to an internal
multi-appearance station before the system disconnects.
BUSY [2] 1..1200..3000 (1 unit = 0.1 second)

When a user dials to a busy station or trunk this timer determines the duration of
the internal busy tone before the system reverts to reorder tone (disconnect) or
forwards the call to an incomplete destination.
REORDER [3] 1..50..3000 (1 unit = 0.1 second)

Defines the duration of the reorder (error) tone before lockout (disconnect) on a
Single Line Telephone (SLT) and on a keyset before the keyset enters an idle state
(see TONE_TO_IDLE [2] on page 9-27).
Station Timers ST.T [0,0,1,1]
CONFIRM [4] 1..9..10 (1 unit = 0.1 second)

Defines the duration of the tone confirming feature activation or cancellation. To
define the time duration before the keyset can enter an idle state define TONE_TO_
IDLE [2] (page 9-27) as larger than this parameter.
DVMS [5] Not applicable.

HOLD [6] 100..6000..65534 (1 unit = 0.1 second);

CC1, Eu: 1200
Eu9: 450
Defines the duration of the hold interval after which the call returns to the
originating station. An automatic ring indicates that the call has returned.
9-2
PI Reference Manual Station Controls
HARD_HOLD [7] 100..1200..65534 (1 unit = 0.1 second);

Eu9: 450
Defines the hard hold duration after which the call returns to the originating station.
An automatic ring indicates that the call has returned. When HARD_HOLD is
utilized the station is considered busy towards new incoming calls.
PARK [8] 100..1200..65534 (1 unit = 0.1 second)

Defines the time period that a party remains parked (special hold, retrievable from
any station) after which the call returns to the originating station. An automatic ring
indicates that the call has returned.
PAGE_Q [9] 100..600..65534 (1 unit = 0.1 second)

Defines the duration that a call placed in the page queue remains in the queue
before recalling the originator.
1st_DIGIT [10] 10..100..1200 (1 unit = 0.1 second)

Defines the maximum system waiting time for the first digit dialed after offhook.
A disconnect follows time-out.
This is also the time-out period used when defining HOT_ST_DELAY, i.e. the time
the system waits after the station user lifted the handset and received dial tone, but
did not yet dial. After this time period the user is automatically transferred to a
predetermined Hot Station Delay destination.

The interdigit timer defines the maximum system waiting time between any two
digits for an internal call.

FEAT_DIAL [12] 1..600..1200 (1 unit = 0.1 second)

Feature Dial defines the maximum idle time allowed while invoking a feature.
HKFLS FILTER [13] 3..10 (1 unit = 0.1 second);

Eu: 5
Hookflash Filter determines the hookflash filter period following the completion
of a valid offhook (for answer). During this period the system ignores all SLT
electrical circuit changes or load changes. The Hookflash filter provides a flexible
anti-bounce parameter. The anti-bounce filter provides a way of avoiding false
signaling problems when an SLT answers a call. Because of the nature of this
parameter, all intentional dialing and hookflashing during this period are ignored.
9-3
MAGNETO_AUTO_ 10..30..200 (1 unit = 0.1 second)

ANS [14]
Magneto Auto Answer defines the ringback duration to a magneto station before
the magneto station automatically answers (automatically connected).
CF_NO_ANS INT/EXT 10..100..200 (1 unit = 0.1 second)

[15] CC1: 180
 This parameter is only relevant when the station has defined a Call
Forward No Answer destination (default dial #142) or Call Forward No
Answer External destination (default dial #17703).
Defines the ringing duration to a called station before the station’s calls are
forwarded to its Call Forward No Answer destination.
FLEXICALL_CF_NO_ 10..150..200 (1 unit = 0.1 second)

ANS [16]
This parameter defines the ringing duration to a FlexiCall station and its remote
phone, before the stations’s calls are forwarded to its Call Forward No Answer
destination.
Define this parameter as 50% higher than CF_NO_ANS INT/EXT [15] above, to
compensate for the delay to the remote phone.
9-4
SLT Definition ç SLT [or IST or ROOT,0,2,1,1]
SLT - Station definition is used to program each:

• Single Line Telephone (SLT), commonly referred to as 500 or 2500 sets,
connected to peripheral cards as described on page 9-20.
• SLT_IP connected via third-party MGCP gateways
• Magneto telephone set connected to 8SM or 8SMipx cards (see page 9-126).
 For Keyset definition (see page 9-31).

FROM/TO DIAL # Any valid system SLT station number, All
Enter the required range of SLT dial numbers FROM the lowest number TO the
highest number.
PRM_COS [0] 0..249 (or maximum defined in SIZES, see COS on page 4-16)
Sets the station’s primary Class of Service (COS). A COS may be assigned to a
single station, several stations or all stations.
SEC_COS [1] 0..249 (or maximum defined in SIZES, see COS on page 4-16)
Sets the station’s secondary COS. This is typically the COS applied to the station
when the system is in Night 1 or Night 2 mode. COS ranges are the same as for
PRM_COS.
SLT Definition SLT [or IST or ROOT,0,2,1,1]

PRIV_LIBS [2] 0..10..255 (or maximum defined in SIZES, see PRIVATE on page 4-12)
This parameter determines the maximum number of speed call (Private Library)
numbers available to the station.
A Private Library can be used to speed dial long numbers. Also, a Private Library
is used to dial external or network numbers for features that allow only internal
destinations such as Call Forward, Divert and Hunt features.
TERMIN [3] Yes/No

Determines whether a station may only terminate (receive) calls (and not originate
them). (Attendant Modifiable: default feature code #152)
ORIGIN [4] Yes/No

Determines whether a station may only originate calls (and not receive any calls).
Entering Yes prevents the user from receiving calls.
(Attendant modifiable: default feature code #151)
9-5
BLOCK [5] Yes/No

Blocks the station from originating or receiving all (internal and external) calls.

Set this parameter to Yes to prohibit the station from originating outgoing trunk
calls. (Attendant modifiable: default feature code #154)Enter Yes to restrict
outgoing calls.
Enter No for no restrictions.
PRIVACY [7] Yes/No

Boss groups only
Prevents a third party from entering a conversation on a Boss line. (User
modifiable: default feature code #186/#6)

Boss groups only
Boss group member can place a call on hold that can be retrieved from hold only
by the station that originated the hold condition.
(User modifiable: default feature code #187)
HARD_HOLD [9] Yes/No

Defines whether or not a station with an established call on hold is considered busy
for additional incoming calls. The station can still originate (initiate) calls.
No: Idle for incoming calls and for making additional calls.
Yes: Busy for incoming calls and idle for making additional calls.
LAST_NUM [10] Yes/No

Last Number Redial determines whether a station user is able to automatically
redial the last number dialed (by pressing a single programmed station button (with
default dial number #143) or by dialing *).
To enable redialing of internal station numbers, INTERNAL_LAST_NUM_REDIAL
[6] (page 6-20) must be set to Yes.
This parameter also defines whether or not the station user can save the last
external number dialed for future dialing (feature code #196/#9), when defined by
COS (see SAVED [57] on page 7-18).
9-6

Prevents “break-in” and other tones being sent to the station. This parameter is
normally used when data (through a modem, facsimile and other similar devices)
is being transferred.
DND_WP [12] Yes/No

Defines whether this station is blocked from receiving a whisper page (paging only
one party) during an ongoing conversation.
 Enter Yes to inhibit or No to enable Whisper paging to this station. (User

Modifiable: default feature code #1745).To enable this feature, define
DND_WP [26] on page 7-10, in COS, to Yes.
STATUS [13]
When set to Yes, this parameter enables the SLT user to receive an alert tone
indicating that the second party (called or calling party) is in Speaker Mode
(activated for handsfree or group conversation).
This feature is only relevant when the second party is a keyset (FlexSet, FlexSet-IP,
DKT, T207M, T208M, T207M/NP, T208M/BL) station user.
CALL_MODE [14] IRSS/Call_back

Defines the IRSS mode applicable for this SLT station.
• IRSS (Call-through) — from an off-site phone the user calls his/her desk phone
and receives a dial tone after successfully completing the authentication
process. The offsite caller pays for the entire call.
• Callback — from an off-site phone the user calls his/her desk phone. The
system identifies the user, sounds a callback announcement (See CALL_BACK_
ANNOUNCEMENT [11] on page 6-22, disconnects the call, and calls the user
back at a predefined IRSS number. Upon answering the call, the user receives
a dial tone. This option allows employees to make calls at company’s expense
from an external off-site station.
Who pays for the IRSS Request (to the Coral?
• Callback without Announcer - No charge
• Callback with Announcer - The offsite caller pays for the portion of the call
during which the announcement is heard. .
9-7
[15]
Set to Yes only for SIP stations.
Defines whether the MG module should try and detect Fax tones from this IP
station.
Set this parameter to Yes if this SLT station is able to send or receive fax calls.
General
voice calls.
one of the parties is a SIP station or a SIP Trunk. The parameter in irrelevant for
MGCP stations.
[16]

Set to Yes only for IP stations.
Defines whether the MG module should try and detect modem tones from this
station.
Set this parameter to Yes if this SLT is able to send or receive modem calls.
General

voice calls.
ATT [17] Yes/No

Identifies the station as having Attendant station privileges and Class Of Service,
see Attendant Class of Service beginning on page 7-33.
 It is preferable to define a Keyset/FlexSet Station as an Attendant.

Defining an SLT as an Attendant severely limits the Attendant’s
capabilities.
9-8
AUTO_UNATT_TRANS Yes/No
[18]

Applies only to Attendant Stations (ATT [17] above, must be set to Yes).
Allows unanswered calls to an attendant station to be automatically transferred to
another destination, after a system wide defined time-out period.
When AUTO_UNATT_TRANS is set to Yes, the attendant console will enter the
unattended mode automatically, but only after the system defined time-out period
AND:
• The attendant’s calls are then transferred to an Alternate Attendant Destination
(attendant feature code: #146).
• If no alternate attendant destination is defined, then all calls to this attendant
station receive the UNATTENDED message.
• The attendant’s calls automatically return to the attendant station the next time
the attendant offhooks.
When AUTO_UNATT_TRANS is set to No, the attendant console continues
ringing unless it is manually answered.
AUTO_RELEASED_ Yes/No
ALL [19]
ACD&UCD only
Defines whether or not the system will automatically release (i.e. invoke
ACD&UCD Release/Resume, feature code #1975) an agent that does not answer
a call within a predetermined time interval (defined by TIME_TO_NEXT_
MEM (page 10-12) in the HUNT branch).
Once the agent is released, no calls are transferred to the agent, thereby improving
the ACD/UCD group response time.

The released agent is automatically resumed by the system the next time the agent
offhooks at the station.
Set this parameter to Yes to allow the system to automatically release agents when
they are not active.
PASSCODE [20] Any 4 digits (0-9, , #), or None

Identifies the station’s four-digit passcode needed to operate certain Coral features
such as Phone Lock, Executive Privilege, IRSS/Freedom and COS Switchover.
CHECK_OUT [21] Yes/No

SAU Requirement
Determines whether or not the station is in “Check-Out” status. When set to Yes,
the station Class Of Service is changed to a system defined Class Of Service (see
OUT_COS. [2] on page 6-42. (Attendant modifiable: default feature code #1970)
9-9
TYPE [22] 0 (Rotary, pulse dial only), 500-type phones

1 (Rotary and DTMF), 500/2500-type phones
Determines the type of station signaling method used for dialing.
rotary (pulse dial) or DTMF dialing
Type Description
0 Pulse/Rotary dialing, 500-type phones
1 Pulse/Rotary and DTMF touch-tone dialing, 500 or 2500-type phones.
Selecting 1 permits DTMF and pulse dialing on the same line, called
MIXED SLT. When an answering machine or other common carriers
or any DTMF controlled auxiliary equipment is connected, the type
should be set to 1.
To use a DTMF dialing, 2500-type phones one of the following

equipment is required:
• 8DRCF, 8DRCM-2, 8DRCM, 8DTMF, or 8DTR card
• MRC cards
• U-RMI Office or U-MR Office cards
• The Coral IPx 500M main cage contains 24 (max) circuits
• The Coral CDRS 200E main cage contains 24 (max) circuits
 SA cards (8/24SA, 4/8/16/24SA Office, or 8/16/24SAipx) support

Pulse/Rotary dialing from firmware version 6 or higher.
 For SLT-IP connected to the Coral Teleport/FXS for VoIP calls,

set this parameter to 0 (Rotary), for both DTMF and Pulse dial devices.
ANNOUNCER [23] Yes/No

Determines whether a SLT station is used only as an announcer destination for:
• CALL_BACK_ANNOUNCEMENT [11] (on page 6-22)
• ACD/UCD recorded announcements (RECORDED MESSAGES: on page
10-14)
• Wakeup announcer destination (ANN_DEST [0] on page 6-41)
9-10
MULTI_APPEARANCE Yes/No
[24]
Multi-Appearance defines whether a station can receive several internal calls on a
single line, even though the station is active (busy).
When set to Yes, the busy called station receives a call-waiting tone and the calling
station party hears a ringback tone (see ORIGINATOR_CALL_WAITING_TONE [2] on
page 6-50 to define which ringback tone is heard). When set to No, the busy called
party does not receive any indication and the calling party hears a busy tone.
Always set this parameter to No when:
The station is an ACD member, see MEM # (A/R/CR) (page 10-17).
 Notes:
•
• For LS/GS trunks

Incoming calls always appear as multi-appearance regardless of this
parameter definition.
• Although this parameter is not applicable for magneto telephones, it is
still used for displaying magneto information.
ANSWER CALL Yes/No

WAITING WITH HF
When set to Yes, this parameter enables the user to put the original conversing
[25]
party on hold and to answer a waiting call by pressing hookflash. If more than one
call is waiting, the call with the highest priority is answered first. Any following
hookflash changes the call state to Broker/Consultation/3-Way or a combination of
them or Continuous Conference, depending on the station COS definition for
1=BROKER, 2=CONSULT, 4 = 3-WAY, 5=ALL, 6=Continuous Conf [11] (page 7-6).

This feature is also enabled by activating the following related keys:
• Digit 1 operating as hookflash (relevant when DIGIT_ONE_AS_H.F.
[5] (page 6-20) is defined as Yes)
• Flash (R button) on some phones
• FLASH by SLT cradle
9-11
RECEIVE CID [26] Yes/No

SAU Requirement
Determines whether an SLT set may receive Caller ID information.
Set this parameter to YES if this SLT is equipped with a display or an external
Caller ID display box.
SEND_CALLER_ID Yes/No
[27]
This parameter defines whether the calling station’s telephone number is displayed
on the called station’s keyset display panel.
Enter Yes to send the caller ID information for this station.
Enter No to restrict the caller’s ID on external calls. To further restrict the ID on
internal and internal network calls, set CLIR on Internal Calls [7] (page 6-20) in
Station Options (SFE, 2) to Yes.
When this parameter is set to Yes, the user can override this setting (i.e., not send
Caller ID info) on a per-call basis (default feature code #1444) for external calls
and for internal calls only when CLIR on Internal Calls [7] is also set to Yes.
 Regardless of this parameter setting, when CLIR on Internal Calls [7] is set
to No, the Caller ID can be restricted only on external calls.
9-12
ALTERNATE_LINE_ID 0..3200 (or maximum as defined in SIZ, see Chapter 4) or

[28] R (Remove- for no Alternate), None
Defines the index number for the alternate ID number for a caller’s line to be
displayed at the terminating end. The ID number is defined in the ISDN/ALI Table
(see Alternate Line ID beginning on page 26-9). This parameter, however, defines
the index number within the Table.
Use this parameter if the Caller Identification number other than the ISDN Caller
ID is sent to the terminating end.
SEC_ALTERNATE_ 0..3200 (or maximum as defined in SIZ, see Chapter 4) or

LINE_ID [29] R (Remove- for no Alternate); None
 Notes:
• This number is used for information for E911 emergency centers.
• This number is only used when USE SECOND ALI [19] (page 15-16) in
Dial Services is set to Yes (when set to No, this Second Alternate Line
ID is ignored.)
This parameter defines a second alternate Line ID number for a caller’s line to be
displayed at the terminating end. It should be used to provide a phone number that
is recognized by the emergency center in order to physically locate the calling
station user.
 AFTER applying the Auto Set Relocate feature (see page 5-22), enter the
Second ALI number originally assigned to the user’s new location before
the profiles were swapped.
The ID number is defined in the ISDN/ALI Table (see Alternate Line ID beginning

on page 26-9). This parameter, however, defines the index number within the Table
When this parameter is not defined for the station, the system definition for the
DEFAULT_SECOND_ALI [18] (page 6-12) is used instead.
9-13
OPX_STATION [30] Yes/No
 This parameter applies to stations only when the station card

configuration strap (Jumper or via IpProgrammer S/SH) is set to the SH
mode.
Over Public Exchange (OPX) Station defines whether to light the message lamp
indicator on SLT stations.
For SLTs that are directly connected to and operated from the Coral, set this option
to No and the station lamp will light for waiting messages.
For SLTs connected to the Coral by means of another PABX or through the CO,
this option should be set to Yes (disable message lamp) to prevent high voltage
pulses from being sent over long distances.
This parameters only apply to the following cards with their related jumper set to
the “SH” position, or when SA cards are configured to “SH” mode:
• 4/8/16SH/S(-LL), jumper JMP4
• 8/16/24SLS, jumper JP1
• 8/16SLSipx, jumper JU1
• 4/8/20S Office, 4S+8Fx Office, 4S+16Fx Office, 8S+8Fx Office,
8S+16Fx Office, jumper JU
• SA cards programmed to “SH” mode via IpProgramm
Tip: Set this parameter to Yes, to prevent unnecessary damage to electrical circuits,
Voicemail systems, facsimile machines and modems that may be overly sensitive
to the message lamp voltage signal sent. A distinctive tone indicating a waiting
message is still sent over the line and heard.
HOOK_FLASH_ Yes/No
RELEVANT [31]
Determines whether the Hookflash operation (i.e. dialing 1 or pressing flash) by the
SLT can be accepted by the system. Entering No disables the hookflash operation
(i.e. pressing the onhook or 1 button).
 Recommendation: In noisy environments or over very long lines, set this

parameter to N.

Defines whether or not the “Malicious Call Trace” option is active causing the
system to record incoming calls to this SLT. The number of calls to be recorded is
defined in the #_OF_CALLS_TRACED [33] parameter below.
(User Modifiable: default feature code #1740)
(Attendant Modifiable: default feature code #1742)
9-14
#_OF_CALLS_ 0..3..60 (Max: 10,000 telephone #'s per system)

TRACED [33]
Defines the maximum number of incoming “traced” calls to be recorded per
station. The calls are recorded on a “last in, first out” method.
 When CALL_TRACE [32] above is set to N, this parameter cannot be

changed and remains as previously set.
Permanent/Temporary P/T
_AUTO SET
RELOCATE [34]
 Notes:
• When TEMPORARY_AUTO SET RELOCATE [8] on page 6-21 is defined to
NO in the System Features - Station Options branch (SFE,2), then this
parameter is automatically defined as Permanent and cannot be
changed to Temporary.
YES, then this parameter can be defined as Permanent or Temporary.
Define this parameter as:
• Permanent so that the station relocation holds until reverse relocation is
performed.
• Temporary to automatically reverse the relocation at midnight (only when
TEMPORARY_AUTO SET RELOCATE [8] on page 6-21 is set to Yes).
This parameter should be set identically for both source and destination stations. It
allows swapping station profiles between similar sets, either temporarily or
permanently.
See Auto Set Relocate (Portability) List per Device Type on page 18-11.

(User Modifiable: No default feature dial number is automatically assigned for this
feature. The system manager must define a default feature dial number
corresponding to the feature index number (220).)
VIP [35] Yes/No
 Only digital stations can receive a VIP ring.

Defines the station as a VIP station, thereby causing any other internal station to
ring differently (same as Voice Page ring). The called station hears the different
ring and realizes this is a high priority call.
9-15
VOICE_MAIL [36] Yes/No
 This feature does not apply to SLT_IP and Magneto stations.

Defines whether this SLT line acts as an interface for a Voicemail system (Y) or not
(N) or whether CoralMail-2 is connected to this line (Y).
When this station is defined as a member of an IVR ACD group (see IVR_ACD (ACD
only) on page 10-4), the IVR operates as follows:
• If VOICE_MAIL is set to Yes, the IVR is simultaneously enabled with the
ACD waiting queue. The call will not lose its place in the queue while
interacting with the IVR. ANI or DNIS numbers can be sent to this SLT. See
APPEND_TO_DIAL_NUMBER_AS_SUFFIX.
• If VOICE_MAIL is set to No, when the station user answers, the call is
disconnected from the ACD waiting queue and the IVR application takes over.
SLT_VM_CAMP_ON Yes/No
[37]
Enables the SLT line serving as a Voicemail interface to camp on (i.e. set system to
redial when called party is free) to a busy station when defined as Y. The line might
need to camp on to a busy station as an Automated Attendant service requirement.
ANSWER_ None/Answer/Disconnect/Both
DISCONNECT_
Defines whether the station will hear the DTMF signals transmitted.
SIGNAL [38]
Entry Description
Answer DTMF signals will be transmitted when the SLT station

answers
Both DTMF signals will be transmitted when the SLT station both
answers and disconnects
Disconnect DTMF signals will be transmitted when the SLT station

disconnects
None DTMF signals will not be transmitted either when the SLT
station answers or disconnects
MUSIC_ON_ 0..3
HOLD/TRANSFER [39] IPx 500 and CDRS 200E: 0(M1), 1(M2)
Defines which music source is sounded on the held (called party’s) line when the
SLT station places a call on hold or transfers the call.
9-16
COLLECT_CALL_ Yes/No
REJECT_TONE [40]
On an incoming call, this parameter defines whether to send a special tone to the
Central Office (PTT) attendant indicating that the CORAL called party may not
accept a collect call. Set this parameter to Yes to send a collect call reject tone
(defined in Tone Plan, see page 6-97) to the Central Office (PTT) attendant. The
attendant, upon hearing this tone, should deny the request for a collect call
connection and disconnect the call.
9-17
TONE(VM) [41]

Tip: Set this parameter to Yes for ports defined as Voicemail.
Set this parameter to Yes to disable the reorder tone sent to this SLT when it did not
yet onhook after a 2-way call disconnect.
SEND FAILURE Yes/No

REPORT [42]
The Coral Fault Manager (CFM) application detects Locked out SLTs, i.e. SLTs in
an undefined state. In order for an undefined SLT to be reported to the CFM, set
this parameter to Yes.
This parameter is only relevant when FAILURE REPORT (page 17-5) in the Message
Control branch is set to Yes.
3WAY [43]
This parameter is relevant when an SLT port participates in a 3-way call where at
maintained after one of the parties exits the 3-way call. When N (No) is selected
for all of the ports engaged in a 3-way call, RTP is discontinued after one of the
parties exits the 3-way call, and is then re-established for the remaining two parties.
A A
3WAY 2WAY
B C C

 Only when the parameter for all three ports that participate in a 3-way
under which it is defined).
See KEEP_RTP_AFTER_3WAY [25] on page 8-17 for a trunk port
and KEEP_RTP_AFTER_3WAY [85] on page 9-70 for a keyset port.
9-18
SLT: iDSP Card (Caller ID Type Bellcore/ETSI) Database ç CDB,9

The following cards support CLID (Caller ID) for SLT station (500 or 2500 sets)
users in accordance with Bellcore and ETSI standards. DSP technology is
employed to enable the FSK (Frequency Shift Keying) tone generators located on
the cards. This branch applicable for:
• iDSP card
• Coral IPx Office systems with U-RMI Office or U-MR Office cards
• Coral IPx 500 systems with MSBipx hardware issue 0200X1000 or higher
• CDRS 200E systems
The iDSP card allows simultaneous CLID transmission to a maximum of 64 SLT
stations.
SAU Requirement (IPx Office, IPx 500, and CDRS 200E)
Separate Software Authorization is required to allocate the CLID resources. URC
CLID on page 3-16 defines the maximum number of URC CLID resources
authorized for this Coral system. See URC-Card (IPx Office, IPx 500 and
CDRS 200E) beginning on page 4-33.
CLID TYPE 0 (Bellcore)

1 (ETSI)
Defines the type of standard supported by the SLT for the Caller ID feature.
SLT: iDSP Card (Caller ID Type Bellcore/ETSI) Database

Choose 0 if the system supports Bellcore GR-30 protocol.
Choose 1 if the system supports ETSI 300-659-1 para. 6.1.1 protocol.
Transfers the updated card database immediately to the cards. Regardless of entry,
update made. This parameter is accessible only through the Update Mode.
9-19
SLT Card Database ç STDB

The SLT card database is used to establish the card database for the following
station cards:
• CDRS/CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
There are four Station card databases (Card_DB#: 0-3), one of which is assigned
to each station card (see Card List - Chapter 6). These cards provide station circuits
for Single Line Telephone (SLT) sets, commonly referred to as 500 or 2500 sets or
for other non-proprietary telephones that interface the Coral system. Card database
programming is identical for each card.
FROM 0..3
TO 0..3
CARD_DB#
Enter the required range of card database tables FROM the lowest card number TO
the highest card number.
SLT Card Database STDB
9-20
INT_RING (S): The following two entries (Fields 0 and 1) control the ring cadence for internal
(station-to-station) calls.
These parameters only apply to the following cards with their related jumper set to
the S position:
8S+16Fx Office, jumper JU1
• SA cards programmed to “S” mode via the IpProgrammer application
Figure 9-2. Internal

Ring Cadences ON
Ringing Silence
OFF
ON [0] 50..500..12750 ms (in 50 ms increments)

Eu1: 900 ms
Eu8: 500 ms
Eu9: 1000 ms
CC1: 1000 ms
Sets the on ringing duration. See Figure 9-2.

OFF [1] 50..2000..12750 ms (in 50 ms increments)

Eu1: 2700 ms

Sets the silent period between ring cycles. See Figure 9-2.
9-21
EXT_RING (S): The following six parameters (Fields 2 - 7) set the ring cadences for incoming
trunk calls.
the S position:
• 4/8/20S Office, 4S+8Fx Office, 4S+8Fx Office, 4S+16F Office,
8S+8Fx Office, 8S+16Fx Office, jumper JU1
• SA cards programmed to “S” position via IpProgrammer
Figure 9-3. External

Ring Cadences ON 1 ON 2 ON 3
Ringing Silent Ringing Silent Ringing Silent

Period #1 Period #1 Period #2 Period #2 Period #3 Period #3
OFF 1 OFF 2 OFF 3
ON_1 [2] 50..500..12750 ms (in 50 ms increments)

CC1: 1500 ms
Eu1: 250 ms
Eu6, CC8: 400 ms
Eu9: 1000 ms
Sets the ringing duration of the first ring in a three-ring cycle. See Figure 9-3.
OFF1 [3] 50..500..12750 ms (in 50 ms increments)

CC1: 3000 ms
Eu1: 350 ms
Eu6, CC8: 200 ms
Eu9: 4000 ms
Sets silent period between ON_1 and ON_2. See Figure 9-3.
ON_2 [4] 0..500..12750 ms

CC1, Eu9: 0 ms
Eu1: 250 ms
CC8: 400 ms
Same as ON_1 but for the second (of three) ringing periods.
9-22
OFF2 [5] 0..2000..12750 ms

CC1, Eu9: 0 ms
Eu1: 2700 ms
Same as OFF1, but for the silent period between ON_2 and ON_3.
ON_3 [6] 0..12750 ms

Same as ON_1, but for the third (of three) ringing periods.
OFF3 [7] 0..12750 ms

MSG_LAMP_&_RING See table below for range options

(SH) [8] Defaults: 0 (Most systems),
Eu1: 2
Eu8: 4
Eu: 3
Message Waiting Lamp & Ring determines the internal/external ring cadence and
Message Waiting lamp flash rate when a station card is installed for SLT stations,
equipped with message lamps, in hotel rooms.
the “SH” position, or when SA cards are configured to “SH” mode:
8S+16Fx Office, jumper JU
• SA cards programmed to “SH” mode via IpProgrammer

External/Internal Ring Cadence (ms) Ring
Frequency Typically
Range External Ring Internal Ring SA Cards Used
In:
ON_1 OFF1 ON_2 OFF2 ON OFF
0 670 1800 670 2520 1600 4050 20Hz USA & Mexico
1 850 1300 850 1500 750 3750 25Hz Rest of World
2 300 300 300 3100 1000 3000 25Hz Belgium
3 500 500 500 2500 1000 3000 25Hz Europe
4 TBD TBD TBD TBD TBD TBD 25Hz Czech Republic
9-23
MIN_OFFHK [9] 70..200..500 ms (in 10 ms increments)

Eu3, Eu6: 70 ms
 MIN_OFFHK must be less than SUSP_OFFHK [7] (page 6-3).

Minimum Offhook determines the minimum offhook recognition time for Single
Line Telephones (SLT).
MIN_ONHK [10] 100..790..1200 ms (in 10 ms increments)

CC1, CC2, Eu9: 200 ms
Eu1: 240 ms
Eu3: 1120 ms
Minimum Onhook determines the minimum onhook recognition time for single
line telephones (SLT).
MIN_HKFLS [11] 10..200..2550 ms (in 10 ms increments)

CC1, Eu9: 50 ms
CC2, Eu3: 10 ms
Eu1: 90 ms
Eu8: 40 ms
Minimum Hookflash determines the minimum hookflash recognition time for

Single Line Telephones (SLTs). (Hookflash is used for transfer and feature
activation on SLTs.)
MAX_HKFLS [12] 10..780..2550 ms (in 10 ms increments)

CC1: 400 ms
CC2, Eu3: 150 ms
Eu1: 230 ms
Eu8: 160 ms
Eu9: 200 ms
Maximum Hookflash determines the maximum hookflash recognition time for

Single Line Telephones (SLTs). When hookflash duration exceeds this defined
time, the system either ignores the action or reports an onhook condition when the
minimum onhook time is met. (Hookflash is used for transfer and feature activation
on SLTs.)
9-24
MIN_BREAK [13] 10..50 ms (in 10 ms increments)

CC1, Eu8, Eu9: 20 ms
Eu1: 50 ms
Determines the minimum “Break” (current interruption) recognition time for

pulse/rotary dialing on SLTs (500 type).
 SA cards (8/24SA, 4/8/16/24SA Office, or 8/16/24SAipx)

support Pulse/Rotary dialing from firmware version 6 or higher.
MAX_BREAK [14] 50..90 ms (in 10 ms increments);

Eu8: 100 ms
Determines the maximum “Break” (current interruption) recognition time for


MIN_MAKE [15] 10..30 ms (in 10 ms increments)

CC1, Eu9: 20 ms
Eu3: 80 ms
Determines the minimum “Make” (current restoral) recognition time for



MAX_MAKE [16] 30..70 ms (in 10 ms increments)
Eu3: 80 ms
Eu8: 100 ms
Determines the max “Make” (current restoral) recognition time for pulse/rotary
dialing on SLTs (500 type).

9-25
H.F. FILTER [17] 200..500..800 ms (in 10 ms increments)
 All intentional dialing during this period is also ignored.

Filter After Hookflash determines the period following the completion of a valid
hookswitch flash during which any electrical change of the SLT circuit is ignored.
During this period, any changes in loop current or audio energy are ignored. This
timer is intended to provide a flexible hookswitch anti-bounce parameter, in order
to avoid false signaling problems on single line stations when attempting to
transfer, park, hold, or conference an existing call.
FIXED_RING [18] Yes/No
 This parameter is relevant only for FlexiCom 200 and CDRS 200 systems.
FIXED_RING_ON [19] 600..720..2000 ms
 This parameter is relevant only for FlexiCom 200 and CDRS 200 systems,
when FIXED_RING [18] is set to Yes.
FIXED_LAMP_ON [20] 80..120..600 ms
 This parameter is relevant only for FlexiCom 200 and CDRS 200 systems,
when FIXED_RING [18] is set to Yes.
.
[21]
Transfers the updated card database immediately to the cards. Regardless of entry,
update made. This parameter is accessible only through the Update Mode.
9-26
Keyset Timers ç EK.T,0 [0,0,1,3,0]
Keyset Timers are used to set the timing parameters for all the following keysets,
system wide:
• FlexSet 280, 280D, 280D-Z, 120, 120D, 120L
• FlexSet 281S, 121S, 280S, 120S
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
• CPA
• GKT
• DKT
• DST
• VM keyset ports
• EKT
• VDK
 These timers do not apply to SLT, Magneto, P-Series, T207S, T208S,

• FKT
T207S/NP, T208S/BL, T322, T328, SeaBeam, and all third-party SIP

terminals.
AUTO_ANSWER [0] 1..10..100 (1 unit = 0.1 second)

Defines the ring duration (the ring duration at the called station and the ringback
tone duration at the calling station) after which the auto answer feature is invoked.
Keyset Timers EK.T,0 [0,0,1,3,0]

AUTO_ANS_V_PAGE 1..10..100 (1 unit = 0.1 second)

[1]
Auto Answer Voice Page defines the “warbling” tone duration after which the
voice page auto answer feature is invoked.
TONE_TO_IDLE [2] 10..300 (1 unit = 0.1 second)

CCO, CC1: 15
 If this timer is increased, it is recommended to also increase the REORDER

[3] and CONFIRM [4] timers defined in Station Timers, (see page 9-2).
Tone Before Idle defines the reorder or confirmation tone duration after which the
station idles.
AOC-E_DISPLAY [3] 1..300..65534 (1 unit = 0.1 second)
 AOC-E_DISPLAY [68] on page 9-62 must first be set to Yes.
9-27
Defines the duration of the Advice of Charge display which appears after a call has
ended and before the display goes into the idle state.
MUTE_RING [4] 1..50..65534 (1 unit = 0.1 second)

Defines the duration of a mute-ring tone towards the keyset user when the first
multi-appearance call arrives. Applies only to “one burst” keysets, (see OPTION
[24] on page 9-38).
NAME/NUMBER 1..30..100 (1 unit = 0.1 second)

DISPLAY [5]
Define the time interval for the Number of the calling party to be displayed on the
user’s keyset when using the Name/Number feature (default feature code: #128;
Index: 8).
The calling name is restored on the keyset display after this time period elapses.
Keyset Timers EK.T,0 [0,0,1,3,0]
9-28
Keyset Ring Cadence ç EK.T,1 [0,0,1,3,1]
Keyset Ring Cadence is used to determine the three pairs of ON/OFF ring/silent
periods for each of the 8 ring cadences (0 - 7) defined for all the following keysets,
system wide:
• FlexSet 280, 280D, 280D-Z, 120, 120D, 120L
• FlexSet 281S, 121S, 280S, 120S
• FlexSet-IP 280S
• GKT
• DKT, DST
• EKT, VDK
Ring cadence, ring level (volume) and ring type (pitch) are selected at individual
stations according to user requirements. The user selects the different cadences by
the keyset ring adjustment feature code at his/her keyset. The default cadence is 4,
the default level is 8 (from 0 to 15), and the default type (pitch) is 0 (from 0 to 7).
Each station can select only one cadence, type, and level at any given time.
Cadence time entries apply to internal (station to station) calls. Incoming calls from
a trunk ring at twice the cadence rate (half each time entry). Voice page, reminder,
and wakeup calls ring at three times the cadence rate (one third each time entry).
 The ring type and cadence level for T207M, T208M, T207M/NP,
T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Series, T322, T328,
SeaBeam, and all third-party SIP terminals, Wireless handsets
(CoralAIR/FlexAir) are local handset features, not controlled by the PI.
Figure 9-4. External ON 1 ON 2 ON 3

Ring Cadences
Keyset Ring Cadence EK.T,1 [0,0,1,3,1]

OFF 1 OFF 2 OFF 3
Table 9-1: Keyset Default Ring Cadence Patterns
Pair Cadence #
0 1 2 3 4 5 6 7
ON_1 600 1,000 1,000 500 500 500 500 500
OFF1 300 2,500 1,000 500 500 500 500 500
ON_2 600 0 0 500 500 500 1,000 1,000
OFF2 300 0 0 2,000 500 500 2,000 500
ON_3 900 0 0 0 500 1,500 0 1,000
OFF3 1,800 0 0 0 2,000 2,000 0 2,000
* ON/OFF time periods given in milliseconds
9-29
 Keysets equipped with a headset should adjust the Ring Type feature at
their keyset station to 7, MAX (default access code #136, then enter 2 for
Ring Type and press UP Volume button until RING TYPE MAX appears).
See also CORD_DISCONNECT_ACTIVATION_BUTTON [97]
and CORD_DISCONNECT_AS_WIRELESS_HEADSET [98] on page 9-76).
This helps eliminate the short annoying burst inherent in the other Ring Types when
disconnecting a call while another call is queued at the same station.
ON-1 Defaults: see Table 9-1

ON-1: 150..12750 ms (in 50 ms increments)
Defines the duration of each of the first ring period.
OFF-1 Defaults: see Table 9-1

OFF-1: 150..12750 ms (in 50 ms increments)
Defines the duration of the silent period between the ON-1 and ON-2 periods.

0,150..12750 ms (in 50 ms increments)
Defines the duration of the second ring period.

0, 150..12750 ms (in 50 ms increments)

Keyset Ring Cadence EK.T,1 [0,0,1,3,1]
0,150..12750 ms (in 50 ms increments)

Defines the duration of the third ring periods.

0, 150..12750 ms (in 50 ms increments)
9-30
Keyset Definition ç KEY [or EKT or 0,2,1,2,0]
Keyset Definition allows programming all system keysets and Wireless stations.
Programming is identical for all the following sets.
• FlexSet 280, 280D, 280D-Z, 120, 120D, 120L
• FlexSet 281S, 121S, 280S, 120S
• FlexSet-IP 280S
• P-Seies (such as: P-335, P-450)
• T207M, T208M, T207M/NP, T208M/BL
• T207S, T208S, T207S/NP, T208S/BL
• T322, T328
• FlexIP SoftPhone (FLIPS)
• Third-party SIP terminals
• CPA
• GKT
• DKT
• DST
• VM keyset ports
• SeaMail (voice and MWI) SIP ports
• LxCMC (voice and MWI) SIP ports
• EKT
• VDK
• FKT
• AA
Keyset Definition KEY [or EKT or 0,2,1,2,0]

 For SLT and Magneto station definition (see page 9-5).
• APDL
FROM/TO DIAL # Any valid system keyset station #; All

Enter the required range of keyset dial numbers FROM the lowest dial number, TO
the highest dial number.
9-31
PRM_COS [0] 0..249 (or maximum as defined in SIZ, see Chapter 4)
1: First keyset
0: All other keysets
 COS #1 default is initialized for stations defined as attendant (ATT [17]

below, must be set to Yes).
Determines the station’s primary or normal Class of Service (COS). A COS may
be assigned to a single station, several stations or all stations.
SEC_COS [1] 0..249 (or maximum as defined in SIZ, see Chapter 4)
1: First keyset
 COS #1 default is initialized for stations defined as attendant (ATT [17]

below, must be set to Yes).
Determines the station’s secondary COS. This is the COS which may be applied
during specified Day/Night modes (see Night Service Definition - Chapter 12), or
by invoking the Class of Service Changeover feature.
PRIV_LIBS [2] 0..10..255 (limited by numbering plan)

Determines the maximum number of speed call (Private Library) numbers
available.
A Private Library can be used to speed dial long numbers. Also, a Private Library
is used to dial external or network numbers for features that allow only internal
destinations such as Call Forward, Divert and Hunt features.
TERMIN [3] Yes/No

Determines whether a station may only terminate (receive) calls, and not originate
any calls. (Attendant Modifiable: default feature code #152)
ORIGIN [4] Yes/No

Determines whether a station may only originate calls and not receive any calls.
Entering Yes bars the user from receiving calls. (Attendant modifiable: default
feature code #151)
BLOCK [5] Yes/No

Blocks the station from making or receiving all (internal and external) calls.
9-32

Outgoing Trunk Restriction determines whether a station cannot originate any
outgoing trunk calls. (Attendant modifiable: default feature code #154)
Yes -restricts outgoing calls
No - no restriction
PRIVACY [7] Yes/No

Boss Groups only
Prevents a third party from entering a conversation on a Boss line or a trunk
reserved for the Boss group. (User modifiable: default feature code #186 or #6)

Exclusive Hold enables a Boss/secretary group member to place a call on hold
which can later be retrieved from hold only by the station that originated the hold
condition. (User modifiable: default feature code #187)
HARD_HOLD [9] Yes/No

Defines whether or not a station with an established call on hold is considered busy
towards additional incoming calls. However, the station can still originate (initiate)
calls when HARD_HOLD is set either to Yes or No.
No: Idle for incoming calls and for making additional calls
Yes: Busy for incoming calls and idle for making additional calls.
LAST_NUM [10] Yes/No

Last Number Redial determines whether a station user is able to automatically
redial the last number dialed (by pressing a button programmed for this feature
(default dial number #143) or by dialing *).
To enable redialing of internal station numbers, INTERNAL_LAST_NUM_REDIAL
[6] (page 6-20) must be set to Yes.
This parameter also defines whether or not the station user can save the last
external number dialed for future dialing (feature code #196 or #9), when defined
by COS (see SAVED [57] on page 7-18).

Prevents “break-in” and other tones being sent to the station. This parameter is
normally used when data (through a modem, facsimile and other such devices) is
being transferred. (User modifiable: default feature code #17700)
9-33
DND_WP [12] Yes/No

Defines whether this station is blocked from receiving a whisper page (paging only
one party) during an ongoing conversation.
Enter Yes to inhibit or No to enable whisper paging to this station. (User
Modifiable: default feature code #1745).
• Set this parameter to Yes, for: FlexAir handsets (T-402, T-404, T-408,
T-304) and IP stations (T207M, T208M, T207M/NP, T208M/BL, T207S,
T208S, T207S/NP, T208S/BL, P-Series, T322, T328, SeaBeam, FlexIP
SoftPhone, third-party SIP phone, and FlexSet-IP 280S).
• To enable this feature, define DND_WP [26] (page 7-10), in COS, to Yes.
STATUS [13]
For SIP phones, this feature is for display only and will appear as N (No).
When set to Yes, this parameter enables the station user to receive a message on the
display as well as an alert tone indicating that the second party (called or calling
party) is in Speaker Mode (activated for handsfree or group conversation).
This feature is only relevant when the second party is a keyset (T207M, T208M,
T207M/NP, T208M/BL, FlexSet, FlexSet-IP, and DKT) station user.
 For P-Series, T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam,

and third-party SIP phone, this feature is not applicable. For SIP phones
this parameter is for display only and will appear as N (No).
CALL_MODE [14] IRSS/Call_back

Defines the IRSS mode applicable for this keyset station.
• IRSS (Call-through) — from an off-site phone the user calls his/her desk
phone and receives a dial tone after successfully completing the authentication
process. The offsite caller pays for the entire call.
• Callback — from an off-site phone the user calls his/her desk phone. The
system identifies the user, sounds a callback announcement (See CALL_BACK_
ANNOUNCEMENT [11] on page 6-22, disconnects the call, and calls the user
back at a predefined IRSS number. Upon answering the call, the user receives
a dial tone. This option allows employees to make calls at company’s expense
from an external off-site station.
Who pays for the IRSS Request (call to the Coral?
• Callback without Announcer - No charge
• Callback with Announcer - The offsite caller pays for the portion of the call
during which the announcement is heard.
9-34
[15]

This parameter is relevant only for IP endpoints.
Defines whether the MG module should try and detect Fax tones from this IP
station.
Set this parameter to Yes if this Keyset is able to send or receive fax calls.
General
voice calls.
[16]

This parameter is relevant only for IP endpoints.
Defines whether the MG module should try and detect modem tones from this
station.
Set this parameter to Yes if this Keyset is able to send or receive modem calls.
General

voice calls.
ATT [17] Yes/No

Yes: First keyset (Attendant)
No: All other keysets
 When an APDL is connected, set this parameter to Yes.

Identifies the station as having Attendant station privileges and COS (see Attendant
Class of Service beginning on page 7-33).
9-35
AUTO_UNATT_TRANS Yes/No
[18]

This parameter applies only to Attendant Stations (when ATT [17]=Yes).
Allows unanswered calls to an attendant station to be automatically transferred to
another destination, after a system wide defined time-out period.
When AUTO_UNATT_TRANS [18] is set to Yes, the attendant console will enter the
unattended mode automatically, but only after the system defined time-out period
AND:
• The attendant’s calls are then transferred to an Alternate Attendant Destination
(attendant feature code: #146).
• If no alternate attendant destination is defined, then all calls to this attendant
station receive the UNATTENDED message.
• The attendant’s calls automatically return to the attendant station the next time
the attendant offhooks or presses any other station key/button.
When AUTO_UNATT_TRANS [18] is set to No, the attendant console continues
ringing unless it is manually answered.
AUTO_RELEASED_ Yes/No
ALL [19]
ACD&UCD only
Defines whether or not the system automatically releases (i.e. invokes ACD&UCD
Release/Resume, feature code #1975) an agent that does not answer a call within
a predetermined time interval (defined by TIME_TO_NEXT_MEM (page 10-12) in the
HUNT branch).
Once the agent is released, no calls are transferred to the agent, thereby improving
the ACD/UCD group response time.
The released agent is automatically resumed by the system as soon as the agent
activates any key at the station.
Set this parameter to Yes to allow the system to automatically release agents when
they are not answering.
PASSCODE [20] Any 4 digits, 0-9,, # or None

Identifies the station’s four-digit passcode needed to operate certain Coral features
such as Phone Lock, Executive Privilege, IRSS/Freedom and COS Switchover.
CHECK_OUT [21] Yes/No

SAU Requirement
Determines whether or not the station is in “Check-Out” status. When set to Yes,
the station’s Class Of Service is changed to a system defined Class Of Service (see
OUT_COS. [2] on page 6-42). (Attendant modifiable: default feature code #1970)
9-36
MULTI_APPEARANCE Yes/No
[22] Yes: First keyset
Multi Appearance defines whether a station can receive several calls on a single
line while the station is active (busy).
When this parameter is set to Yes, the busy called station receives a call-waiting
tone and sees the calling party number on the keyset display. The calling station
party hears a ringback tone (see ORIGINATOR_CALL_WAITING_TONE [2] on page
6-50 to define which ringback tone is heard) and waits for the call to be answered.
When set to No, the busy called party does not receive any indication and the
calling party hears a busy tone.
For LS/GS trunks:
Incoming calls always appear as Multi Appearance regardless of this parameter
definition.
Always set this parameter to No when:
• The keyset is an ACD member, see MEM # (A/R/CR) (page 10-17).
Always set this parameter to Yes when:
• When an APDL terminal is connected.
• For CKT # 18 of the iCMC cards when initialized as a 24SFT card (the Pilot #
is the internal APA port for iCMC card).
For SIP entities (P-Series, T200S series, T300 series, SeaBeam and
all third-party SIP terminals):
SIP entities must be defined with Late Media Negotiation. SIP entity that is defined
with an Early Media Negotiation cannot be defined as a Multi-Appearance station.

If defining this parameter differently, an error message appears:
Conflict with SIP Early Media negotiation definition, TRY
AGAIN !
Alternatively, station defined with Multi-Appearance cannot be defined with an
Early Media setup, see Media Negotiation [6] (page 29-46).
9-37
M.A MUTED_RING Yes/No

[23]
This parameter is relevant only when MULTI_APPEARANCE [22] above is
set to Yes and is required for Reminder, Wakeup, Camp-on, Call back, etc.
First Multi Appearance Call determines whether a second call indication ring is
active (Yes) or not active (No). When set to Yes, the first Multi Appearance call is
received both with a muted-ring tone and a display message on keysets equipped
with a display panel.
 FlexSet-IP 280S Version 3.26 or higher, when this parameter is set to Yes,
receives a muted-ring tone ONLY via the handset. The tone is not sounded
via the loudspeaker in handsfree mode, but the user sees the calling party
number on the keyset display.
OPTION [24] No (Continuous), Yes (One burst)
 Notes:
• This parameter is relevant only when M.A MUTED_RING [23] above is set
to Yes.
• For FlexAir/CoralAIR wireless handsets, P-Series, T207S, T208S,
T207S/NP, T208S/BL, T322, T328, SeaBeam and third-party SIP
phones, this feature is controlled by the phone.
This parameter determines the ring type for the first Multi Appearance’s Waiting
Call. The muted ring tone at the station can be sounded continuously or in one
burst. When set to Yes (one burst), the duration is defined by a system-wide
parameter, MUTE_RING [4] (page 9-28).
9-38
ANSWER CALL Yes/No

WAITING WITH HF
[25]

This feature does not apply to P-Series, T207S, T208S, T207S/NP,
T208S/BL, T322, T328, SeaBeam and all third-party SIP terminals.
When set to Yes, this parameter enables the user to put the original conversing
party on hold and to answer a waiting call by pressing the transfer key. If more than
one call is waiting, the call with the highest priority is answered first. Any
following transfer changes the call state to Broker/Consultation/3-Way or a
combination of them or Continuous Conference, depending on the station COS
definition for 1=BROKER, 2=CONSULT, 4 = 3-WAY, 5=ALL, 6=Continuous Conf
[11] (page 7-6).
This feature is also enabled by activating the following related keys:
• Digit 1 operating as transfer (relevant when DIGIT_ONE_AS_H.F. [5] (page 6-20)
is set to Yes)
• XFER
• Flash (R button) on wireless handsets
AUTO_ANS [26] Yes/No

Auto Answer determines whether incoming calls are automatically answered in
speaker mode, after a predetermined number of rings.
This feature is not recommended for use on models without microphones
(FlexSet 120L, DST). When this option is defined as Yes, headsets are
recommended.

• For CPA units define AUTO_ANS as YES.
• For FlexAir/CoralAIR wireless handsets, P-Series, T207S, T208S,
T207S/NP, T208S/BL, T322, T328, SeaBeam and all third-party SIP
terminals, this feature is controlled by the phone.
IDLE_DISPLAY [27] Yes/No
 For FlexAir/CoralAIR wireless handsets, P-Series, T207S, T208S,

T207S/NP, T208S/BL, T322, T328, SeaBeam and all third-party SIP
terminals, this feature is controlled by the phone.
Determines whether or not an idle keyset, equipped with a display, shows the time,
date and site name (site name appears only when defined in SITE NAME for PI on
page 17-2 in Root,0,0,3). In addition, to the current time and date, the second line
of the display shows the assigned name and station number if defined system-wide,
see EXT.ID. [17] on page 6-24. (User modifiable: default feature code #137)
9-39
VOICE_MAIL Yes/No

(DTMF receive) [28]
This feature does not apply to:
FlexAir/CoralAIR wireless handsets, FlexSet-IP 280S,
T207M, T208M, T207M/NP, T208M/BL, T207S, T208S, T207S/NP,
T208S/BL, P-Series, T322, T328, SeaBeam.
 NOTE: Applicable for SIP terminals (such as SeaMail or LxCMC).

SAU Requirement
Determines whether this keyset can be used as an interface for a Voicemail
application or any other application that requires DTMF digits to be sent.
Announcer can be provided by SeaMail, IPC/uCMC, IPC/SFC and iVMFipx.
This parameter must be set to No for SeMail, IPC/uCMC, IPC/SFC and iVMFipx
ports when ANNOUNCER [34] on page 9-42 is defined Yes.
This parameter must be set to Yes for IPC/uCMC, IPC/SFC and iVMFipx card
ports. These cards automatically update this parameter to Yes for its keyset ports.
• This keyset station should be defined in an ACD Voicemail group.
When the station is an IVR destination, the IVR definition of the keyset affects the
IVR operation as follows:
• If set to Yes, the IVR is simultaneously enabled with the ACD waiting queue.
The call will not lose its place in the queue while interacting with the IVR. The
call will not lose its place in the queue while interacting with the IVR. ANI or
DNIS numbers can be sent to this keyset. See APPEND_TO_DIAL_NUMBER_
AS_SUFFIX.
• If set to No, when the station user answers, the call is disconnected from the
ACD waiting queue.
The user calling this Voicemail station must program a pre programmed keyset
button with the station number followed by the DTMF digits to be sent. The Coral
system waits for the Voicemail to send an answer signal to the calling station and
then the calling station continues to send the DTMF digits.
VM_CAMP_ON [29] Yes/No

Determines whether a keyset defined as an interface for Voicemail will camp-on
(i.e. set system to redial when called party is free) to a busy destination.
9-40
ANSWER_ None/Answer/Disconnect/Both
DISCONNECT_
Defines whether the station will hear the answer / disconnect sequence. See
SIGNAL [30]
DISCONNECT_SEQ [20] and ANSWER_SEQ [21] under SFE,7 [0,0,4,1,7] on page
6-43.
 Irrelevant only for IP keysets.

Entry Description
Answer DTMF signals will be transmitted when the call is established
Both DTMF signals will be transmitted when the keyset station

both answers and disconnects
Disconnect DTMF signals will be transmitted when the call is

disconnected (by any party)
None DTMF signals will not be transmitted either when the keyset
station answers or disconnects
SECOND_CALL_ Yes/No
DISPLAY [31]

Relevant only for keysets defined with Multi-Appearance.
Controls the second line display for the keyset.
When the keyset is engaged in a conversation that involves both display lines, such
as Name Retention or Call Forward, this parameter defines whether or not the
information on an incoming call can be displayed on the second line, instead of the
current call information, i.e. the caller name or the forwarded destination.

When set to Yes, when an additional call arrives at the keyset, its details are
displayed on the second line, overwriting current information.
When set to No, when an additional call arrives at the keyset, the user is prompted
only with a call-waiting tone. The display remains unchanged, thus, first call
information is still displayed.
AUDIO_PATH [32] Normal/Headset_Only
 Notes:
• This parameter does not apply to P-Seies (such as: P-335, P-450),
T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and all
third-party SIP terminals.
• For DKT2320Z and FlexSet 280D-Z (and
FlexSet 280S/281S/120S/121S when defined for zip tone), this parameter
must be set to Headset_Only.
• SPKR_ON/OFF [43] below must be set to Yes to enable this feature.
9-41
When set to Headset_Only, this parameter enables all calls to be conducted via the
headset and disables the keyset microphone and loudspeaker when pressing the
programmed feature button or by dialing the feature code (default: #1302).
The audio path can only be transferred when the telephone is in an idle state,
regardless of the handset state.(User Modifiable: default feature code #1302)
The FlexSet-IP 280S and T207M, T208M, T207M/NP, T208M/BL users may
activate this feature from any telephony state, not only idle by either dialing its
feature code or using a pre programmed button.
TONE(VM) [33]
Set this parameter to Yes to disable the reorder tone sent to this Keyset when it did
not yet onhook after a 2-way call disconnect.
 Tip: Set this parameter to Yes for Keysets defined as Voicemail.

ANNOUNCER [34] Yes/No

Announcer can be provided by SIP port on SeaMail, IPC/uCMC, IPC/SFC and
iVMFipx ports.
Define this parameter to Yes for ports used as announcer destinations for:
• ACD/UCD recorded announcements (RECORDED MESSAGES: on page
10-14)
• CALL_BACK_ANNOUNCEMENT [11] (on page 6-22)
• Wakeup announcer destination (ANN_DEST [0] on page 6-41)
MLPP Special Announcements on page 6-47
•
Define this parameter to No when VOICE_MAIL (DTMF receive) [28] on page 9-40
is defined “Yes” for ports serving as Voicemail stations, in order to enable using the
Voicemail application to record announcements.
KEYCLICK [35] Yes/No

Determines whether or not keyclick is heard when a key on the dial pad is pressed.
 Notes:
• For FlexAir/CoralAIR wireless handsets, this feature is controlled at the
handset.
• For T207M, T208M, T207M/NP, T208M/BL phones, this feature is
controlled at the station and it’s web portal.
• This feature is not displayed for FlexSet-IP 280S, T207M, T208M,
T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Seies
(such as: P-335, P-450), T322, T328, SeaBeam, and all third-party SIP
terminals.
9-42
MUSIC [36] Yes/No
 Define MUSIC as NO for:

FlexAir/CoralAIR wireless handsets, Flexset-IP 280S,
T208S/BL, P-Seies (such as: P-335, P-450), T322, T328, SeaBeam and all
Determines whether or not background music is heard when the keyset is idle. This
feature requires an ASU, RMI, 8DRCF, 8DRCM-2, 8DRCM or
U-RMI/U-MR/RMI/MR Office card to be present in the system. For Coral IPx 500
and CDRS 200E systems, no extraneous hardware is required.
Music must be programmed (see Music Sources in Chapter 4) and connected to the
system. (User modifiable: default feature code #135)
9-43
MUSIC_NUM [37] 0..3

IPx 500 and CDRS 200E: 0 (Music 1), 1 (Music 2)
 This feature does not apply to:

FlexAir/CoralAIR wireless handsets, Flexset-IP 280S,
T208S/BL, P-Seies (such as: P-335, P-450), T322, T328, SeaBeam, and all
Determines the background music source to be sounded from multiple music
sources. This parameter is relevant when MUSIC, above, is set to Yes. The range is
limited by # OF MUSIC SOURCES (1-4) (page 4-45). (User modifiable: default
feature code #1329)
V_PAGE_IN [38] Yes/No
 This feature is not available for FlexAir/CoralAIR wireless handsets,

P-Seies (such as: P-335, P-450), T207S, T208S, T207S/NP, T208S/BL,
T322, T328, SeaBeam, and all third-party SIP terminals.
Voice Page In determines whether or not a keyset can be voice paged (through the
station speaker). Also serves as the Voice Page Do Not Disturb feature when set to
N). (User modifiable: default feature code #134)
AUTO_ANS_V_P [39] Yes/No
 This feature is not available for FlexSet 120L, DSTs, FlexAir/CoralAIR

wireless handsets, P-Seies (such as: P-335, P-450), T207S, T208S,
T207S/NP, T208S/BL, T322, T328, SeaBeam, and all third-party SIP
terminals.
Auto Answer to Voice Page determines whether or not voice page to station is
automatically answered.
Y: enables two-way conversation
N: disables the keyset microphone (effecting one-way communication) until
manually answered. (User modifiable: default feature code #133)
ELAPSE_TIME [40] Yes/No
 This feature is not available for P-Seies (such as: P-335, P-450), T207S,
T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and all third-party
SIP terminals.
Determines whether or not the call duration is displayed on the keyset during an
external call. (User Modifiable: default feature code #129)
9-44
AUTO_JOIN=3/ 0..3 (see Table 9-2 below)

AUTO_HOLD=2/
1: First Keyset
AUTO_TRANSFER=1/

OFF=0 [41]
Notes:
• This parameter is irrelevant for P-Seies (such as: P-335, P-450),
• Keysets defined as Attendant (ATT [17] above) should define this
parameter to 1 (Auto Transfer).
• Auto Hold, Auto Transfer, and Auto Join are mutually exclusive; only one
can be used.
When a station user is engaged in a regular call (2-way), this parameter may be
used to define what to do with the ongoing call when trying to handle incoming or
outgoing call.
Table 9-2: Auto_Join / Auto_Hold / Auto_Transfer / Off
0 Off Use for none of these type options.
1 Auto Transfer Use to automatically place an in-progress call in

transfer mode when any keyset button is pressed
including dial pad keys. The user can now continue
to dial another number which will automatically
 Set this option for Keysets defined as

transfer the call to that number.
Attendant (ATT [17] above).

2 Auto Hold Use to automatically place the in-progress call on
hold when any keyset DSS, LINE, TRUNK or
LOOP button is pressed. The user can now
continue to dial another number while the original
call is held.
3 Auto Join Use to automatically have a new incoming call join

the call in progress when the user presses any
keyset DSS, LINE, TRUNK or LOOP button, or to
have a call placed on hold join the call in progress
by pressing the blinking HOLD button.
9-45
AUTO_DTMF_IN_ Yes/No
3WAY_&_CONF [42]
This parameter is relevant for FlexSet 121S/281S, FlexSet-IP 280S,
T207M, T208M, T207M/NP, T208M/BL phones.
Determines whether or not the Touch-Tone Dialing (DTMF) from a phone engaged
in a 3-way conference or multiparty calls, can be activated without the need of
pressing the OCC key (Other Common Carrier, #127).
When set to Y (Yes), the keyset is capable of transmitting DTMF signals during a
3-way, conference, and multiparty call, enabling it to send commands to Voicemail
and other applications without using a soft key or a pre-programmed OCC button.
When set to N (No), DTMF signals will be transmitted from the keyset only after
pressing an OCC button.
SPKR_ON/OFF [43] Yes (ON/OFF) / No (SPKR)
Yes: First keyset

 This feature is not available for FlexAir/CoralAIR wireless handsets,

T322, T328, SeaBeam and all third-party SIP terminals.
Determines whether the SPKR (speaker) key is used as a speakerphone key or as
an ON/OFF (connect/release) key generally used with an Headset or stations
defined as Attendant (ATT [17] above).
This parameter must be set to Y (Yes):
• When a wireless headset is connected (see CORD_DISCONNECT_
ACTIVATION_BUTTON [97] and CORD_DISCONNECT_AS_WIRELESS_

HEADSET [98] on page 9-76).
• For a CDRS 200E built in keyset.
• For keysets using Headset Only (i.e. when AUDIO_PATH [32], above, is set
to Headset Only).
BLIND_ATT [44] Yes/No
 The VSM can be connected only to an EKT.

Blind Attendant (Vision-Impaired Console or VIC) identifies the EKT321 as being
connected to a proprietary console for the visually impaired (Voice Synthesizer
Module or VSM). To transmit aural messages, the EKT321 should be equipped
with a display unit because the voice messages are linked to the visual messages.
When this parameter is set to Yes, LANGUAGE [56] (page 9-57) must be set to
English.
9-46
PROTOCOL Only one of the following three parameters may be defined as Yes.
TYPES: • 3RD_PARTY_EVENTS [45]
• PCC [46]
• ACD_PC [47]
3RD_PARTY_EVENTS Yes/No
[45]

When this parameter is set to Yes, the next two parameters PCC [46] and
ACD_PC [47]) are not displayed.
Set this parameter to Yes to define this Keyset with iAPA or FlexSet with APA,
PEX/APA, (or APDL) as the communicator between the CSTS application (such
as the Coral Navigator) and the Coral.
For the Coral Navigator, set this parameter to Yes for the 24th port (APDL) on the
IPC2 card.
This parameter should only be set to Yes for the following type station devices:
• FlexSet that includes an APA or PEX/APA unit with Version 3.15 or higher
• APDL unit
• Keyset with iAPA
PCC [46] No/PCC/CSTS_PCC
 Notes:
• This setting is irrelevant for FlexAir/CoralAIR wireless handsets,
T322, T328, SeaBeam and all third-party SIP terminals. Therefore, it

must be set to No for these phone types.
• This parameter is automatically set to No by the iVMFipx, IPC/uCMC
and IPC/SFC cards for ports defined as Announcer.
Defines the protocol type for connecting a keyset (APDL, FlexSet 280S or DKT
w/APA, GKT or FlexSet 80) to a PCC or CAP application. PCC [46] also identifies
the port as being used for Automated Attendant (AA) via 4IAA card.
For applications using the CSTS (Coral Supported Telephony Services) protocol,
set this parameter to CSTS_PCC. For applications using any other protocol set this
parameter to PCC. If the keyset is not connected to any PCC or CAP application,
enter No.
Different keysets associated with PCC and CSTS_PCC applications connected to
the same Coral PABX must be defined on separate line cards (8/16/24SFT,
8/16SFTipx, 8/16/24SFT Office, 4S+8Fx Office, 8S+8Fx Office, 4S+16Fx Office,
8S+16Fx Office, 8/16/24SDT, 8/16SKD and 8SVD). One line card is needed to run
the non-CSTS applications and another line card to run the CSTS based
9-47
applications. If defining this parameter differently for another keyset defined on the
same card, an error message appears:
Conflict with previous definition of KEYSET wxyz.
PCC [46] and ACD_PC [47] are mutually exclusive for the same keyset. Therefore,
when PCC [46] is set PCC or CSTS_PCC, then ACD_PC [47] (below) is
automatically set to No and vice versa.
 Notes:
• The PCC must be version 10.080 or later.
• A PCC connected to APA cannot be used as a Multi_PCC station but
rather as a singular PCC station only.
• To employ a PCC station via APA (not iAPA), the APA setup is needed
(see APA, PEX/APA and APDL RS-232 Setup on page 9-120).
• The keyset (FlexSet, DKT, GKT,...) must be connected to one of the first
8 card ports (CKT # 0 - 7).
9-48
ACD_PC [47] No/ACD/CSTS_ACD
 This setting is irrelevant for FlexAir/CoralAIR wireless handsets, P-Seies

(such as: P-335, P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328,
SeaBeam and all third-party SIP terminals. Therefore, it must be set to No
for these phone types.
Defines the protocol type for connecting a keyset with APA or iAPA to a
proprietary ACD-PC station via a CSTS protocol or to another ACD system using
any other protocol.
• ACD is used for applications using any other non-CSTS protocol.
Applicable for CCM version 2 or lower.
• CSTS_ACD is used for applications using the CSTS (Coral Supported
Telephony Services) protocol. Applicable for CCM version 3 or higher.
• No is used if the keyset is not connected to any ACD or ACD-PC
application.
Different keysets associated with ACD and CSTS_PCC applications connected to
the same Coral system must be defined on separate line cards (8/16/24SFT,
8/16SFTipx, 8/16/24SFT Office, 4S+8Fx Office, 8S+8Fx Office, 4S+16Fx Office,
8S+16Fx Office, 8/16/24SDT, 8/16SKD and 8SVD). One line card is needed to run
the non-CSTS applications and another line card to run the CSTS based
applications. If defining this parameter differently for another keyset defined on the
same card, an error message appears:
Conflict with previous definition of KEYSET wxyz.
PCC [46] and ACD_PC [47] are mutually exclusive. If one is defined, the other must
be set to No.
 Notes:

• For the 4IAA, the 2/8SD card should be upgraded to software version
14.60 or higher.
• The keyset (Flexset, DKT, GKT,...) must be connected to one of the first
8 card ports (CKT # 0 - 7).
9-49
iAPA The following two parameters are used to establish the logical connection between
the CTI application computer and its associated Coral Keyset.
• APPLICATION_IP_SOCKET(#/R) [48]
• UGW_CARD_LOCATION (Shelf,Slot) [49]
iAPA (Figure 9-5) is applicable for CTI application computers communicate with
the Coral system, via the organization’s network rather than via the APA devices.
It may be defined for these keyset units:
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
• DKT 1000 series
• DKT 2000 series
• FlexSet 120, 120D, 120L, 120S, 121S
• FlexSet 280, 280D, 280D-Z, 280S, 281S
The following parameters must also be defined for iAPA:
• Authorization for APA on page 3-15
• RTP PORT BASE [2], KEEP ALIVE INTERVAL [3], iAPA_TCP_PORT [4] on page
29-69
APPLICATION_IP_ Any valid IP address, R (remove the IP address _ _ _._ _ _ _._ _ _ )

SOCKET(#/R) [48]
 This parameter is displayed only if one of the previous three parameters
(3RD_PARTY_EVENTS [45], PCC [46] and ACD_PC [47]) is defined as Yes.
Defines the IP address of the CTI application computer. The IP socket defined is
used to transfer data to and from the PUGW.
• The computer must be connected to the organization’s LAN
• The computer must be equipped with a “Serial Port to TCP/IP

Redirector”, which is a third-party software
• The associated keyset must be active at all times
• Only one CTI application computer will work behind any NAT
This parameter is used by the PUGW card to communicate with the CTI
application computer.
UGW_CARD_ Any (Shelf,Slot) of PUGW card. Shelf and Slot numbers are entered
LOCATION (Shelf,Slot) between parenthesis, separated by a comma.
[49]
This parameter is displayed only if the previous parameter APPLICATION_
IP_SOCKET(#/R) [48] is set.
Defines the physical location of the PUGW card (Version 10.60 or higher) from
which the CTI application computer relays data to and from the application.
This parameter is used by the CTI application computer to communicate with the
PUGW card.
9-50
PI Reference Manual
9-51
Station Controls

Figure 9-5.
iAPA Architecture
Incoming Calls
TAPIdriver
FlexCT Contact Launcher
Application using FlexCT Contact Launcher
Serial Port RS-232 to
TCP/IP Redirector
Line
LAN
FlexSet 121S
Coral IPx Any wired
PUGW CTI application
keyset computer
LAN
PC
FlexSet-IP 280S
LAN
LAN
T200M series PC
LAN LAN
FlexSet-IP 280S PC
LAN LAN
IP (MGCP) terminals CTI application computers
9-52
BLOCK BUSY/IDLE Yes/No

events for all ports on
When this parameter is set to:
card? [50]
No: All Applications running from this card receive Busy/Idle events.
Yes: None of the Applications running from this card will not receive Busy/Idle
events. All other events are received normally (i.e. Busy/Idle blocked for all card
ports).
9-53
SMS [51] Yes/No
 This parameter is relevant for applications that receive SMS messages

from FlexAir handsets.
Set this parameter to Yes to use the FlexAir protocol type when sending SMS
messages to/from their related applications.
Additionally, set this parameter to Yes for the Alarm Application (IP station)
destination to which the FlexAir handsets send their SMS messages.
 The Alarm Application destination must be programmed in the handset

(T-402, T-404 or T408) station/s Program Button Index #7 via the Keyset
Button - Programming branch (PROG).
SOFTKEY [52] Yes/No
 Define SOFTKEY as No for FlexAir/CoralAIR wireless handsets, P-Seies

(such as: P-335, P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328,
SeaBeam, third-party SIP terminals and all other keysets not listed below.
Set this parameter to Yes to define the keyset as one that supports Soft Keys.
Define SOFTKEY as YES for the following keysets:
• T207M, T208M, T207M/NP, T208M/BL
• FlexSet-IP 280S
• FlexSet 80S, 80P
• GKT
MIC [53] Yes/No
 This feature is not available for FlexSet 120L, DSTs, CPAs,

FlexAir/CoralAIR wireless handsets, P-Seies (such as: P-335, P-450),
Identifies the station as equipped with a microphone.
9-54
COMBINED_AUDIO Yes/No
[54]

Notes:
• This feature is denied when a station is defined as SPKR_ON/OFF
[43] (page 9-46).
• This feature is applicable for FlexSet 120/121/280/281series, T207M,
T208M, T207M/NP, T208M/BL, FlexSet 80, EKT, GKT, and DKTs.
The speaker key on the keyset can be programmed for Combined Audio to activate
the group listening feature. This feature allows keyset users on a call using the
handset to press the speaker key and have the other party's voice broadcast over the
speaker. The keyset user continues to converse on the handset.
This feature allows simultaneous use of the speaker and the handset. The speaker
can be activated by pressing the speaker key while conversing. Conversation is
carried on as usual through the handset, while the conversation is also broadcast
through the speaker. Pressing the speaker key while in group listening reverts the
keyset back to private conversation. (Also known as Group Listening and Call
Monitoring.)
9-55
DISPLAY_SIZE [55] 0..7
Entry DSP Type Description

0 No display DST, ADPL, CPA
FlexSet 120, 120L
P-Seies (such as: P-335, P-450), T207S, T208S,
T207S/NP, T208S/BL, T322, T328,
SeaBeam and all third-party SIP terminals
1 32 DKT with APA for PCC or CAP
EKT, VDK (2 rows x 16 characters)
FlexAIR, CoralAIR (wireless handsets - WST)
2 48 DKT1110 (2 rows x 24 characters)
FlexSet 120D (2 rows x 24 characters)
FlexSet 120S, 121S (3 rows x 24 characters) when
bottom line is controlled by FlexSet software,
i.e. SOFT_KEYS_MENU (page 4-29) is defined as Fixed
3 80 DKT2X1X (2 rows x 40 characters)
FlexSet 280D, 280D-Z (2 rows x 40 characters)
FlexSet-IP 280S, FlexSet 280S, 281S
(3 rows x 40 characters) when bottom line is controlled
by FlexSet software,
i.e. SOFT_KEYS_MENU (page 4-29) is defined as Fixed
GKT, FlexSet 80 (Graphic Display)
4 160 Not Used
5 NA Not Used
6 72 T207M, T207M/NP (128 x 32 pixels)
bottom line is controlled by Coral, i.e. SOFT_KEYS_
MENU (page 4-29) in Sizes Tab is defined as Selectable
7 120 T208M, T208M/BL (128 x 64 pixels)
bottom line is controlled by Coral, i.e. SOFT_KEYS_
MENU (page 4-29) in Sizes Tab is defined as Selectable
 This parameter cannot be updated for FlexSet-IP 280S,

T208S/BL, P-Seies (such as: P-335, P-450), T322, T328, SeaBeam, and all
Identifies the display type and whether it is equipped with a display module.
9-56
LANGUAGE [56] First/Second/Third/Fourth(See table below)

SAU Requirement: 2nd LANGUAGE, 3rd LANGUAGE, 4th LANGUAGE (see
page 3-20).
A maximum of 4 different languages can be loaded per one Coral system. This
option determines which language is used by the keyset.
 For WSTs only English is available.

This parameter is relevant when DISPLAY_SIZE, above, is not set to 0.
The correlation between 1st, 2nd, 3rd, 4th and set of messages is fixed by the
manufacturer for each system. When the selected language in PI-LANGUAGE
[26] (page 6-26) System Features is written from right to left, then all keysets
automatically display that language and this multilingual display option is blocked.
(User modifiable)
 The number of languages is limited by the current Authorization (SAU).

Country First 2nd 3rd 4th
Code* Language Language Language Language
(Default)
CC0 Portuguese French Spanish
CC1 Portuguese Hebrew†
CC2,CC3,CC4 Portuguese Spanish

,CC5,CC6,
CC8
CC7 Polish Spanish

CC9 Polish Hungarian
CC10 English Russian Spanish

German
Eu0,Eu1,Eu2 Dutch French
Eu3,Eu5,Eu6, Dutch Spanish

Eu7
Eu4 Dutch Hungarian
Eu8 Czech Russian
Eu9 Italian French
Eu10 Spanish Italian

* See Table 1-4 on page 1-19 for a list of Country Codes.
† Hebrew language is not availalbe for T207S, T208S, T207S/NP, T208S/BL, P-Seies
(such as: P-335, P-450), SeaBeam, and all third-party SIP terminals.
9-57
EXTERNAL RING Yes/No

ONLY [57] Wireless Handsets only
When this parameter is set to Yes, the Coral sends only the External ring type to
this wireless station.
 Set this parameter to Yes for wireless handsets that do not support more
than one ring type (such as the Siemens Micro 4000L), otherwise, the
handsets will not ring.
When this parameter is set to No, the Coral system can send either an internal or
external ring to the station.
DISPLAY_ANI_FOR_ F (First line)/ S (Second Line)

DSP32/48/72_IN_
Defines whether the Automatic Number Identification (ANI) is displayed on the
(First/Second)_LINE
1st line (F) or 2nd line (S).

[58]
This parameter is only relevant for Keysets with a display size of 16 or 24
characters per row. See DISPLAY_SIZE [55] on page 9-56.
When F is chosen, the ANI is displayed on the first line of the keyset in shortened
form because important characters from the first line display cannot be overridden.
Choose S (Second Line) to enable the display of the entire ANI on the second line.
This is done when there is not enough space on the first line to display both the ANI
and the name.
When S is chosen, the next two parameters 2ND_LINE_PREFERENCE_FOR_
DSP32/48/72 [59] and 2ND_LINE_DISPLAY_ORDER [60] are also relevant.
2ND_LINE_ N (Normal)/ A (ANI)

PREFERENCE_FOR_
DSP32/48/72 [59]

This parameter is only relevant for Keysets with a display size of 16 or 24
characters per row, when DISPLAY_ANI_FOR_DSP32/48/72_IN_
(First/Second)_LINE [58] above is set to S.
When the ANI is defined to be displayed on the second line of the keyset display
(in DISPLAY_ANI_FOR_DSP32/48/72_IN_(First/Second)_LINE [58]), this parameter
defines a preference for either the ANI or the normal Called ID presentation.
Additionally, the Name/Number programmed key (default feature dial number:
#128) can be used to scroll between different Called and Caller information (names
and numbers).
When this parameter is set to Normal:
The normal display is presented including the Name Retention and Forward Cause
on the second line (e.g. “CALLED ID JOSEPH” or “‘Joseph FWD Don”).
The Name/Number key can be pressed up to 3 times. Each time the key is pressed,
the display toggles between the following 3 modes in the following order:
1. Normal display on the second line with the dial numbers (e.g. “CALLED
9-58
ID 2783” or “2783 FWD 4005”).

2. The Caller ID name on the second line (e.g. “Dan Smith”).
3. The Caller ID (i.e. the ANI) number on the second line (e.g.
“2125551234”).
When this parameter is set to ANI:
The Caller ID/ANI name is displayed on the second line (e.g. “Dan Smith”).
The Name/Number key can be pressed up to 3 times. Each time the key is pressed,
the display toggles between the following 3 modes in the following order:
1. Caller ID (ANI) number display on the second line (e.g. “2125551234”).
2. The Called ID name on the second line (e.g. “CALLED ID Joseph”).
3. The Called ID number on the second line (e.g. “CALLED ID 2784”).
2ND_LINE_DISPLAY_ N (Name and ANI), A (ANI and Name)

ORDER [60]
This parameter is only relevant for Keysets with a display size of 16 or 24
characters per row, when DISPLAY_ANI_FOR_DSP32/48/72_IN_
(First/Second)_LINE [58] above, is set to Second Line.
Keysets with a Display size of 16 or 24 characters per row, as follows:
• FlexSet 120D (2 rows x 24 characters)
• FlexSet 120S, 121S (3 rows x 24 characters) when bottom line is controlled
by FlexSet software
• DKT1110 (2 rows x 24 characters)
• DKT with APA for PCC or CAP
• EKT, VDK (2 rows x 16 characters)
• FlexAir handset, CoralAIR handset (wireless handsets)

Defines the default presentation on the second line of the display panel, as follows:
• When N (NAME_FIRST) is defined, the caller’s name is displayed first.
•
 This will cause the second parameter to be truncated.

When A (ANI_FIRST) is defined, the caller’s ANI is displayed first.
9-59
BUT_NUM [61] 0 (Eight Keys), 1 (Sixteen Keys), 2 (Twenty-Four Keys)
 This parameter is not available for P-Seies (such as: P-335, P-450),
Displays the number of programmable keys.
KSI [62]  Yes/No

 The KSI can only be connected to an EKT.
Defines whether a KSI is installed and connected to the 2SK/4SK/8SK port. The
information is automatically updated by the system.
Identifies the EKT has having a KSI interface. The KSI Interface provides the
capability to connect SLT units in parallel with EKT units. When a system is
defined as KSI, the SLTs and EKTs are completely synchronized. The KSI
interface provides ringing signals, hookswitch control and signaling, as well as
Message Waiting indications for the SLT. Examples of SLT devices and their
usages include:
• Standard Cordless Home telephones
• Facsimile machines
• Answering machines
• Modems
• Additional telephone in hotel suite
KSI TYPE [63] 1 (Rotary and DTMF), 0 (KSI not installed) or (Rotary, pulse dial only)
EKT To SLT Interface. Identifies the parallel SLT as having rotary (pulse dial) or
DTMF dialing. To use a DTMF telephone, an 8DRCF, 8DRCM-2, or 8DRCM card
must be installed in the system (See the relevant Coral Installation Manual).
Selecting 1 permits DTMF and pulse dialing on the same line, called MIXED SLT.
This parameter is relevant only when KSI is installed, see KSI [62] above. When the
KSI is not connected, set KSI TYPE to 0.
9-60
EIS [64] Yes/No

KSI Special Mode. When set to Yes, the SLT becomes the communication device,
but the EKT keypad is used for dialing. EKT Voice operation is turned off. The SLT
Onhook is regarded as a disconnect signal so that the call can be cleared. In this
configuration, the SLT is the master and the EKT is the slave.
When set to No, both the EKT and SLT operate in parallel as regular telephones.
This feature is typically used when the EKT is used for its keys and the SLT is used
as the audio connection.
SEND_CALLER_ID Yes/No
[65]
This parameter defines whether the calling station’s telephone number is displayed
on the called station’s keyset display panel.
Enter Yes to send the caller ID information for this station.
Enter No to restrict the caller’s ID on external calls. To further restrict the ID on
internal and internal network calls, set CLIR on Internal Calls [7] (page 6-20) in
Station Options (SFE, 2) to Yes.
When this parameter is set to Yes, the user can override this setting (i.e., not send
Caller ID info) on a per-call basis (default feature code #1444) for external calls
and for internal calls only when CLIR on Internal Calls [7] is also set to Yes.
 Regardless of this parameter setting, when CLIR on Internal Calls [7] is set
to No, the Caller ID may be restricted only on external calls.

ALTERNATE_LINE_ID 0..3200 (maximum is defined in SIZ-Chapter 4) or R (Remove- for no
[66] Alternate); None
Defines the index number for the alternate ID number for a caller’s line to be
displayed at the terminating end. The ID number is defined in the ISDN/ALI Table
(see Alternate Line ID beginning on page 26-9). This parameter, however, defines
the index number within the Table.
Use this parameter if the Caller Identification number other than the ISDN Caller
ID is sent to the terminating end.
9-61
SEC_ALTERNATE_ 0..3200 (maximum is defined in SIZ-Chapter 4) or R (Remove- for no

LINE_ID [67] Alternate); None
 Notes:
• This number is used for information for E911 emergency centers.
• This number is only used when USE SECOND ALI [19] (page 15-16) in
Dial Services is set to Yes (when set to No, this Second Alternate Line
ID is ignored.)
This parameter defines a second alternate Line ID number for a caller’s line to be
displayed at the terminating end. It should be used to provide a phone number that
is recognized by the emergency center in order to physically locate the calling
station user.
 AFTER applying the Auto Set Relocate feature (see page 5-22), enter the
Second ALI number originally assigned to the user’s new location before
the profiles were swapped.
The ID number is defined in the ISDN/ALI Table (see Alternate Line ID beginning
on page 26-9). This parameter, however, defines the index number within the
Table.
When this parameter is not defined for the station, the system definition for the
DEFAULT_SECOND_ALI [18] (page 6-12) is used instead.
AOC-E_DISPLAY [68] Yes/No

FlexSet 120L, DST Range: No
 This parameter is relevant to keysets equipped with a display module.

Defines whether or not the keyset display shows the call cost at the end of the call.
The call cost may be detailed in either the number of metering pulses or the cost in
dollars (or any other currency defined in your system) when and only if CHARGE_
TYPE [10] (page 6-10) in SFE is set to Meter and METERING_UNIT_
CHARGE (page 8-31) in Trunk Group is not defined as N.
 This parameter does not affect the SMDR printing.

Tip: In Hotel/Motel installations, in order to charge telephone rates that differ from
local telephone costs, enter N.
9-62
ALERTING_ Yes/No
MAKECALL [69]
Defines whether to alert the calling station user that the CoraLINK MAKE_CALL
feature is being employed.
When the Coral system has been instructed to connect two ports (stations), this
feature determines whether the called station rings as follows:
Entering Y causes only the calling station to ring. Only after the calling keyset is
answered does the call go through causing the called station to ring.
 Set this parameter to Yes for SIP stations (P-Seies (such as: P-335,
P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and
all third-party SIP terminals) serviced by CoraLINK applications (via CLA
or MAP cards). (SLTs are automatically defined for Alerting Makecall as
Yes.)
Entering N causes both stations to ring simultaneously. When the calling station
answers the call, then it hears a ring back tone until the called station answers.

Defines whether or not the “Malicious Call Trace” option is active. A list of all
incoming calls to the particular keyset is recorded. The number of calls to be
recorded is defined in the parameter below, #_OF_CALLS_TRACED.
(User Modifiable: default feature code #1740)
(Attendant Modifiable: default feature code #1742)
#_OF_CALLS_ 0..3..60 (Max: 10,000 telephone #'s per system)

TRACED [71]
Defines the maximum number of incoming “traced” calls to be recorded. The calls

are recorded on a “last in, first out” method.
When CALL_TRACE [70] is set to N, this parameter cannot be changed and remains
as previously set. (User Modifiable)
9-63
Permanent/Temporary P/T
_AUTO SET
RELOCATE [72]
 Notes:
NO in the System Features - Station Options branch (SFE, 2), then this
parameter is automatically defined as Permanent and cannot be
changed to Temporary.
YES, then this parameter can be defined as Permanent or Temporary.
Define this parameter as:
• Permanent so that the station relocation holds until reverse relocation is
performed.
• Temporary to automatically reverse the relocation at midnight (only when
TEMPORARY_AUTO SET RELOCATE [8] on page 6-21 is set to Yes).
This parameter should be set identically for both source and destination stations. It
allows swapping station profiles between similar sets, either temporarily or
permanently.
See Auto Set Relocate (Portability) List per Device Type on page 18-11.
(User Modifiable: No default feature dial number is automatically assigned for this
feature. The system manager must define a default feature dial number
corresponding to the feature index number (220).)
VIP [73] Yes/No
 Only digital stations can receive a VIP ring.

Defines the station as a VIP station, thereby causing any other internal station to
ring differently (same as Voice Page ring). The called station hears the different
ring and realizes this is a high priority call.
MUSIC_ON_ 0..3
HOLD/TRANSFER [74] IPx 500 and CDRS 200E: 0 (MP-1), 1 (MP-2)
Defines which music source is sounded on the held line (i.e., the second party)
when the station places a call on hold or transfers the call.
9-64
COLLECT_CALL_ Yes/No
REJECT_TONE [75]
On an incoming call, defines whether to send a special tone to the Central Office
(PTT) attendant indicating that the CORAL called party may not accept a collect
call. Set this parameter to Yes to send the collect call reject tone (defined in Tone
Plan, see page 6-97) to the Central Office (PTT) attendant. The attendant, upon
hearing this tone, should deny the request for a collect call connection and
disconnect the call.
ENHANCED_DIAL_ Yes/No
MODE [76]

This parameter is not relevant for P-Seies (such as: P-335, P-450), T207S,
T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, and all third-party
SIP terminals.
Enables this station user to dial numbers from the keypad and then continue the
dialing procedure by pressing any pre-programmed DSS key.
REPORT_3RD_ Yes/No
PARTY_EVENTS [77]
Set this parameter to Yes for keyset stations that are managed by the CSTS
application. When this parameter is set to Yes, the stations data is sent to the CSTS
Server via the Coral.
For Coral Navigator:
• Set this parameter to Yes for all Coral Navigator Client ports:
• In the relevant COS for the station ports, set SILENT_MON_DENY [14] (page 7-8)
to No

9-65
EKT/VDK only: The following two parameters: PEM_EXIST [78] and PEM_INSTALLED [79] apply
only to EKTs and/or VDKs.
PEM_EXIST [78]  Display Only

0 (No),
1 (PEM 40 Keys);
2 (One Multi-PEM: 40 Keys);
3 (Two Multi-PEMs: 80 Keys);
4 (Three Multi-PEMs: 120 Keys)
For Display Only: Defines which PEM/MPEM the system recognizes as being
connected to an EKT/VDK. The information displays the type of configuration
installed. This information is automatically updated by the system.
PEM_INSTALLED [79] 0 (None);

1 (PEM 40 Keys);
2 (One Multi-PEM: 40 Keys),
3 (Two Multi-PEMs: 80 Keys),
4 (Three Multi-PEMs: 120 Keys)
1: First EKT/VDK
0 All other EKTs/VDKs
Determines the database memory that is allocated for the PEM by defining the
amount of PEM keys that can be used (including no PEM at all). Five different
PEM configurations are available. When allocating the number of PEM keys, the
amount must be equal to or greater than the PEM_EXIST [78] definition, otherwise
the following message appears and the PEM installation is denied:
CONFIGURATION ERR
When PEM_EXIST [78] = 0, entering 0 for PEM_INSTALLED [79] clears memory
space for other users.
9-66
FlexSet/ DKT/ The following two parameters: ACTIVE DPEM ID'S [80] and INSTALLED DPEMS [81]
GKT only: apply only to FlexSet 280/281/80, DKT, or GKT.
ACTIVE DPEM ID'S  Display Only

[80]
None,
1 (One DPEM/FlexSet 40B: 40 Keys);
2 (Two DPEMs/FlexSet 40B: 80 Keys);
3 (Three DPEMs/FlexSet 40B: 120 Keys)
Determines whether the system recognizes the presence of an expansion module:
• FlexSet 40B connected to a FlexSet 280/281 series
• DPEM connected to a DKT/GKT
The information displays the type of configuration installed and is automatically
updated by the system.
INSTALLED DPEMS 0 (No),

[81] 1 (One DPEM/FlexSet 40B: 40 Keys);
2 (Two DPEMs/FlexSet 40B: 80 Keys);
3 (Three DPEMs/FlexSet 40B: 120 Keys);
1: First keyset
Determines the database memory that is allocated for the DPEM or (FlexSet 40B)
by defining the amount of DPEM/FlexSet 40B keys that can be used. When
allocating the number of DPEM/FlexSet 40B keys, the amount must be equal to or
greater than ACTIVE DPEM ID'S [80] defined above, otherwise the following error

message appears and the DPEM/FlexSet 40B installation is denied:
CONFIGURATION ERR
When ACTIVE DPEM ID'S [80] = None, entering 0 as this parameter value clears
memory space for other users.
9-67
T200 and T300 The following two parameters: ACTIVE TEM ID’S [82] and TEM INSTALLED [83]
series only: apply only to:T207M, T208M, T207M/NP, T208M/BL, T207S, T208S, T207S/NP,
T208S/BL, P-Seies (such as: P-335, P-450), T322, T328.
ACTIVE TEM ID’S [82]  0: (no TEM installed)

1: TEM installed with phone (Display Only)
 This parameter is relevant only for: T207M, T208M, T207M/NP,

T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Seies (such as: P-335,
P-450), T322, T328 phones
Determines whether the system recognizes the presence of a Terminal Expansion
Module connected to the phone.
• The TEM (for T200 series) adds another 44 programmable keys to the phone.
• The X338 (for T328) adds another 38 programmable keys to the phone. Up to
three X338 expansion modules can be connected to the T328 in a daisy chain,
rendering a maximum of 130 buttons (including the phone’s 16 built-in
programmable buttons).
TEM INSTALLED [83] 0 (No), 1 (One TEM: 44 Keys and one X338: 38 Keys)
1: First keyset
 This parameter is relevant only for: T207M, T208M, T207M/NP,

T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Seies (such as: P-335,
P-450), T322, T328 phones
Determines the database memory that is allocated for the Terminal Expansion
Module by defining the amount of expansion modules that can be used. When
allocating the number of expansion module keys, the amount must be equal to or
greater than ACTIVE TEM ID’S [82], above, otherwise, the following error message
appears and the expansion module installation is denied:
CONFIGURATION ERR
When ACTIVE TEM ID’S [82] = None, entering 0 as this parameter value clears
memory space for other users and all programmed buttons will be deleted (for
T207M, T208M, T207M/NP, T208M/BL phones).
9-68
TURRET Console Any valid system Keyset station number, N (None), R (Remove)
extended DPEM [84]
This parameter defines a secondary (partner) keyset to be attached an existing
keyset station, thus creating a turret console. The two keysets are physically
connected. A suffix is added to each keyset dial number of a turret console:
P defines the primary keyset and S defines the secondary keyset.
This feature is normally used to augment a keyset with the maximum of 3 DPEMs
to create a turret console with an additional keyset and one, two or three DPEMs,
allowing a maximum of 288 programmable buttons for the console.
Attempting to define a secondary keyset that has already been defined as a
secondary keyset results in the following error message:
Conflict with Primary
Only Flexsets/keysets may be connected as turret consoles. Attempting to connect
SLTs or other types of telephones result in the following error message:
Illegal Port Type
Primary
1
2
1 2 3 3
1 2 3 1
1 2 3 2
1 2 3 3
1 2 3
1 2 3

Partner
9-69
3WAY [85]
This parameter is relevant when a keyset port participates in a 3-way call where at
maintained after one of the parties exits the 3-way call. When N (No) is selected
for all of the ports engaged in a 3-way call, RTP is discontinued after one of the
parties exits the 3-way call, and is then re-established for the remaining two parties.
A A
3WAY 2WAY
B C C

 Only when the parameter for all three ports that participate in a 3-way
under which it is defined).
See KEEP_RTP_AFTER_3WAY [25] on page 8-17 for a trunk port
and KEEP_RTP_AFTER_3WAY [43] on page 9-18 for an SLT port.
9-70
DKT: The following parameter is only relevant when this keyset station is a DKT.
SPECIAL_SPEAKER_ 1 (Normal Environment Noise), 2 (Special Environment Noise)

ENVIRONMENT [86]
The Speaker Phone installed in the DKT is designed to cope with two states of
environmental noise. Any DKT can be adapted to Environment Noise 1 or
Environment Noise 2. Two Speaker Phone acoustical environment selection
choices exist:
• Normal Acoustical Environment Noise
• Special Acoustical Environment Noise
SEND FAILURE Yes/No

REPORT [87]
Set this parameter to Yes in order to send data to the Coral Fault Manager (CFM)
application indicating when the Keyset/FlexSet is undefined or not working.
This parameter is only relevant when FAILURE REPORT (page 17-5) in the Message
Control branch (MSG, 2, 0) is set to Yes.
9-71
SOFTKEY: The followingparameters are displayed only when SOFTKEY [52] on page 9-54 is
Display Features set to Yes:
HUNT [88] Yes/No

Defines whether or not the idle display of the T207M, T208M, T207M/NP,
T208M/BL, FlexSet-IP 280S, FlexSet 280S, 281S, 120S, 121S, 80S, 80P and GKT
shows the telephony features relevant to a hunt group, allowing activation via the
Soft Keys.
Set this parameter to Yes if the station user is a member of a Hunt group.
BOSS [89] Yes/No

shows the telephony features relevant to a Boss group, allowing activation via the
Soft Keys.
Set this parameter to Yes if the station user is a member of a Boss group.
PICKUP [90] Yes/No

shows the telephony features relevant to a pickup group, allowing activation via the
Soft Keys.
Set the this parameter to Yes if the station user is a member of a Pickup group.
ZONE_PAGE [91] Yes/No

shows the telephony features relevant to a zone page group, allowing activation via
the Soft Keys.
Set the this parameter to Yes if the station user is a member of a Zone page group.
BELL_UNA [92] Yes/No

shows the telephony features relevant to a Bell UNA group, allowing activation via
the Soft Keys.
Set the this parameter to Yes if the station user is a member of a Bell UNA group.
9-72
GRP_CALL [93] Yes/No

shows the telephony features relevant to a group call, allowing activation via the
Soft Keys.
Set the this parameter to Yes if the station user is a member of a group call.
9-73
SOFTKEY:
IDLE_SET [94] 0..15
 This parameter is relevant only for:

• FlexSet 120S,280S (possessing phone versions 3.50 or higher)
• T207M, T208M, T207M/NP, T208M/BL
Choose a Set number to control the bottom line display (Soft Keys display menu
options) for idle keysets.
The Sets are defined in the Keyset Soft Keys Idle Set (page 9-104) branch.
3RD_LINE_CONTROL Not_Relevant/MCP/Phone/Both (type the whole word or the first letter)

[95]

Relevant only for FlexSets 280S, 281S, 120S, 121S;
and T207M, T208M, T207M/NP, T208M/BL.
This parameter indicates which entity controls the bottom line display on the
FlexSets.
Select Description
Not_Relevant Indicates that this phone is not equipped with a third line
display or that the FlexSet phone is installed with software
version lower than 3.5x.
MCP Indicates that the phone’s third line display is controlled by
the Coral Main Software (i.e. one of 16 sets may be chosen
for the bottom line display)
FlexSet 121S, FlexSet 281S, T207M, T208M, T207M/NP,

T208M/BL sets must be defined as MCP.
Phone Indicates that the phone’s third line display is controlled by
the phone’s internal software version (3.5x or higher).
Both This option (means MCP and Phone) is currently not used.
9-74
Phone Type 3RD_LINE_CONTROL [95]

possible values
FlexSet-IP 280S Phone
FlexSet 120S/280S (Version 3.50 or higher) Phone or MCP
FlexSet 120S/280S (Version 3.49 or lower) Not Relevant
FlexSet 80 (GKT) Not Relevant
FlexSet 121S/281S MCP
T207M, T208M, T207M/NP, T208M/BL MCP
T207S, T208S, T207S/NP, T208S/BL, T322, T328, Not Relevant

P-Seies (such as: P-335, P-450)
SeaBeam softphone Not Relevant
FlexAir/CoralAIR Wireless handset Not Relevant
N_CALL_LOGS [96] 0..20..100;

Note: Default value derived from value for N_CALL_LOG_PER_
USER (page 4-30) in Sizes Tab
 This parameter is only available when 3RD_LINE_CONTROL [95], above, is

set to MCP for the following keysets:
• FlexSet 120S,280S (possessing phone versions 3.50 or higher)
• T207M, T208M, T207M/NP, T208M/BL

This parameter defines the maximum call logs that may be reserved for this keyset.
Note that a maximum number of call logs is defined for all the system keysets
together in Sizes Tab.
9-75
FLEXSET:
CORD_DISCONNECT_ 0..143/R
ACTIVATION_BUTTON
[97]

This parameter is only relevant for:
• FlexSets 280S, 281S, 120S, 121S
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
Designates the programmable button index number that is automatically toggled
(turned on or off) each time the headset cord is disconnected or connected.
The corresponding button should be programmed to perform the required feature,
for example: DND, Login/Logout, Attended/Unattended, Call Forward, etc.
See Figures 9-8, 9-10 and 9-12 for button number locations.
Note: If AUDIO_PATH [32] (page 9-41) is set to Normal, the keyset must be in the
On-Hook mode for this feature to be activated.
CORD_DISCONNECT_ Yes/No
AS_WIRELESS_
HEADSET [98]

This parameter is only relevant when wireless headset is installed for:
• FlexSets 280S, 281S, 120S, 121S
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
When set to Y (Yes), a call can be answered and disconnected by pressing the
built-in activation button on the wireless headset.
When set to N (No), calls can only be answered and disconnected by pressing the
SPKR_ON/OFF [43] on page 9-46 Key on the phone.

Note: This parameter must be set to Y (Yes) when a wireless headset is connected
(see CORD_DISCONNECT_ACTIVATION_BUTTON [97] and SPKR_ON/OFF [43] on
page 9-46).
REFRESH KEYSET Yes/No

[99]
Transfers the updated keyset definitions immediately to the keyset. Regardless of
entry, routine diagnostics periodically resend the keyset definitions to the keyset,
including any update made. This parameter is accessible only through the Update
Mode.
Set this parameter to Yes to immediately apply the most recent changes.
9-76
Keyset Button - Programming ç PROG [0,2,1,2,2]
Keyset Button Programming is used to adapt the keysets to the user’s personal and
professional needs.
Table 9-3 on page 9-79 shows some typical functions that can be programmed into
a keyset button.
Table 9-4 on page 9-81 lists all available keysets and their figures.
Features can then be activated or deactivated at the press of a “programmed button”
thus immediately activating the feature. There are certain features that require
using programmed buttons because they require feature destinations, such as
Divert Call and Help-Requesting.
Key (or Button) programming defines the operation of each keyset button. When
the Class of Service permits, keys may be programmed individually by the user at
each station.
 All Keyset type phones (exclude: EKT, FlexAir/CoralAIR Wireless

handsets, T207M, T208M, T207M/NP, T208M/BL, T207S, T208S,
T207S/NP, T208S/BL, P-Seies (such as: P-335, P-450), T322, T328,
SeaBeam, AA and all third-party SIP terminals.) include four Fixed System
Keys (page 9-103), Button Index #: F1-F4 (programmable keys on the
lower left hand side of the keyset) that are defined identically system-wide.
Changing the button contents for one of these keys at any one station will
automatically update them at all the other stations.
FROM/TO DIAL # Any valid system Keyset station number;

All
Keyset Button - Programming PROG [0,2,1,2,2]

Enter the range of keyset station dial numbers required for programming FROM
the lowest number, TO the highest number.
FROM/TO BUTT # 0..143 (see following figures)

0..7 (Wireless telephones);
All
FROM BUTT #: Enter the first button number for the required range of keys.
TO BUTT #: Enter the last button number for the required range of keys.
KEYSET BUTTON Identifies the feature number or port dial number or sequence of feature/port dial
CONTENT # numbers.
The button numbers in the range above will now present themselves each on a new
line. The button number is followed by the feature/port dial numbers.
Update the requested button’s number accordingly. Remove a button entry by
entering R while the cursor/pointer is on the appropriate button line.
9-77
Enter the programmed string followed by N (“non-programmable”) in order to lock

the key for additional station programming.
 Notes: (1-5) Keyset Notes:

1) When the system is initialized, only a single attendant is allocated by
the system. When additional attendants are required, the individual
Keyset must be specially programmed with attendant features. Such
programming can be performed either as an update key-by-key process,
or by using the more efficient duplicating functions.
2) To use the Alarm button on the FlexAir Handsets (T-402,404,408 only)
(see Figure 9-26), define handset button — (Button Index#7) with the
SMS Alarm Server destination. Enter N following the destination
number to prevent users from changing the destination..
3) CoralAIR Wireless handsets (see Figure 9-25) Key (Button) #7 on a
Wireless unit must be programmed through the PI system to receive
Voicemail messages.
Lock the key (i.e. disable further station programming on that key) by
suffixing the programming string for Voicemail (XXXX) with N, for all
wireless telephones at button #7.
4) Key 7 (shown shaded in Figure 9-14, Figure 9-15 and Figure 9-16) on
model EKT321-PF telephones is reserved for ground start functions
when there is a power failure. Under normal conditions the key has no
effect when pressed. The function of this key cannot be modified on an
EKT321-PF set. However, the LED key does function during normal
operation and can be PI programmed to utilize the LED for busy
indications or other LED requirements.
5) Key 23 of Automated Attendant (4IAA card) must be programmed to

Night-1/Day Transfer (default dial no. #185).
Table 9-3 shows some typical functions that can be programmed into a keyset
button.
9-78
Table 9-3: Key Contents and Descriptions
Key Contents Key Description Procedure Example
DSS (Direct Permits making or transferring a call to

Station Selection) an extension or trunk by using a
with Busy Lamp defined key. Also lights a busy lamp
indication for stations or trunks
programmed under a DSS key.
DSS (Direct Permits making or transferring a call to There are two ways to program a key for
Station Selection) an extension or boss/hunt group by DSS so that the LED Indicator remains unlit:
o Program a speaker button which is
without Busy Lamp using a defined key without lighting the
immediately followed by the station number
busy lamp. (e.g. enter #1201234 to reach station 1234).
This feature is typically used in hotel o Enter the library code 7000.
situations for telephones in the guest In the OUT TK? field in Public Library or
rooms. Large Library (see Chapter 11), enter the
When this feature is used, the station or hunt or boss group dial number
programmed button lamps (hotel desk, for the programmed button.
EXAMPLE:
barber shop, restaurant, etc.) on the
LIB: 7000
telephone in the guest room do not light NAME: Barber
when their line is engaged. Therefore, TOLL_OVERRIDE: Y
for example, when the restaurant line is TNNT_GROUP: 0 (Enter same COS
busy, the direct line (programmed as COS programmed for the
button) to the restaurant on the guest’s guest telephone.)
telephone (in his/her room) does not DIAL NUM: 1 (This field is irrelevant
in this case, enter any #.)
light.
OUT TK: 1234 (Enter the Dial
Number for the Barber.)
Network Number Permits programming a key to dial any This procedure is performed
(without busy lamp) Network extension number without exactly as it is done within a
having the LED indicator light every singular Coral system.
time the extension is busy.

Single Feature Permits activating or canceling a single To program a key to turn the music
Coral feature. The button is used as a feature on and off: Enter the
toggle switch. feature code #135.
Series of Features Permits programming a series of To program a key to simultaneously

features under a single key; useful for turn off the music and transfer all
one-button speed dialing, voice calls to a library number
response and Voicemail system access, programmed for Voicemail: Enter
and other complex dialing procedures. the feature code #135 followed by
The SPKR code #120 must be the SPKR code #120 and then
programmed between each successive feature code #141 7000 (i.e. 7000
feature sequence. or any other library number).
Feature Key Permits activating or canceling a Follow the directions above and
without feature or series of features without add the SPKR code #120 after
confirmation tone or hearing a confirmation tone or seeing a library code 7000.
display display. The SPKR code #120 must be
programmed after each successive
feature sequence.
9-79
Table 9-3: Key Contents and Descriptions
Key Contents Key Description Procedure Example
Series of Features Permits activating or canceling a To program a key, for

with feature or series of features with the simultaneously turning on both the
LED indication LED controlled by the key pressing music and idle display features:
order. When the key is pressed the first Enter the LED On/Off feature code
time, the LED lights and the features #1301 and feature code #135
are activated. When the key is pressed followed by the SPKR code #120
again, the LED is extinguished and then feature code #137.
regardless of the current state of the
features.
NOTE: The LED On/Off feature code
#1301 must be programmed before the
first feature code is entered in order to
function properly.
Outside Permits programming a key to dial an To program a key to dial 914

Telephone outside telephone number. 555-8132 over trunk group 9:
Number Enter the trunk group number, 9,
(Speed Key) followed by the area code 914 and
then the number 5558132. Dial
codes can be added by using DIAL
NUM (page 11-7) options.
LINE (Boss Group) Programs a Line key in Boss Group for To program a key:

identical displays and signals. Enter LINE code #126 followed by
a Line Number (00 to 05) and then
Not applicable for SLT, Magneto, enter the Boss Group number.
 For T300 series Stations refer

FlexAIR handset, T200S series,
P-Series, and 3rd-party SIP
Stations. to the Application Note
AN1202-001. Requires Coral
Version 16.02.03 or higher.

ELA Line Key Programs a ELA Line key for members To program an ELA line key:
of an ELA group. Enter LINE code #17718 followed
The line key flashes at all ELA member by a Line Number (00 to 31) and
 For T300 series Stations refer

stations for incoming ELA group calls. then enter the ELA Group number.
Any ELA member may pick up the call
or place the call on hold for other ELA
to the Application Note
 Not applicable for SLT, Magneto,

members to pick up.
AN1202-001. Requires Coral
Version 16.02.03 or higher.
FlexAIR handset, T200S series,
P-Series, and 3rd-party SIP
Stations.
XDA External Destination Appearance. This To Program an XDA Line Key:
Line key is lit only for member’s of a See RSRVD_TO_BOSS_
Boss Group sharing the same reserved GROUP (page 11-3).
Public Library defined for the external
destination.
9-80
Table 9-4: Keyset Default Button Programming and Serial Number locations
Keyset Type See Figure
CoralAIR Wireless Handsets on page 9-100

DKT1110 - Default Button Programming on page 9-95
DKT1110 - Serial Number locations on page 9-96
DKT21xx and optional DPEMs Serial Number locations on page 9-97
DKT21xx Default Button Programming on page 9-95
DKT23xx (All other keysets) Default Button Programming on page 9-95
DKT23xx (All other keysets) Default Button Programming on page 9-93
(EU and ROW)
DKT23xx (First keyset, Attendant, all EU) Default Button on page 9-93
Programming
DKT23xx (First keyset, Attendant, CC0) Default Button on page 9-93

Programming
DKT23xx (First keyset, Attendant, CC1) Default Button on page 9-94

Programming
DKT23xx and optional DPEMs - Serial Number locations on page 9-98

DST - Default Button Programming on page 9-95
DST - Serial Number locations on page 9-96
EKT/VDK (All other keysets) Default Button Programming on page 9-91

EKT/VDK (First keyset, Attendant) Default Button on page 9-89
Programming (CC0 and all EU)
EKT/VDK (First keyset, Attendant) Default Button on page 9-90

Programming (CC1 and CC2 systems)
EKT/VDK and optional PEMs on page 9-92

FlexAir Wireless Handsets on page 9-101
FlexSet 120, 120D, 120L on page 9-83
FlexSet 120S, 121S on page 9-83
FlexSet 280, 280D, 280D-Z on page 9-84
FlexSet 280, 280D, 280D-Z with optional FlexSet 40B units on page 9-85
FlexSet 280S, 281S on page 9-84
FlexSet 280S, 281S with optional FlexSet 40B units on page 9-86
FlexSet 80 (GKT43xx) with optional DPEMs on page 9-99
9-81
Keyset Type See Figure
T207M, T208M, T207M/NP, T208M/BLL and TEM unit on page 9-87

on page 9-88
Turret Console PARTNER FlexSet 40B units on page 9-102
 Keyset Button Programming is not applicable for SLT, Magneto, T207S,

T208S, T207S/NP, T208S/BL, P-Seies (such as: P-335, P-450), T322,
T328, SeaBeam, and third-party SIP terminals.
9-82
Figure 9-7.
FlexSet 120, 120D
&120L
Button (Key) FlexSet 120, 120D, 120L
Number Locations
7
F4
6
F3 5
F2 4
3
F1
2
1
0
Figure 9-8.
FlexSet 120S &
121S
Button (Key)
Number Locations FlexSet 120S, 121S

5
F4
4
F3 3
F2 2
1
F1
0
9-83
Figure 9-9.
FlexSet 280, 280D
& 280D-Z
Button (Key)
Number Locations FlexSet 280, 280D, 280D-Z
23 15 7
F4
22 14 6
F3 21 13 5
F2 20 12 4
19 11 3
F1
18 10 2
17 9 1
16 8 0
Figure 9-10.
FlexSet 280S &
281S
Button (Key)
Number Locations FlexSet 280S, 281S
21 15 7
F4
20 14 6
F3 19 13 5
F2 18 12 4
17 11 3
F1
16 10 2
9 1
8 0
9-84
PI Reference Manual
40B units
for FlexSet 280,
Number Locations
Figure 9-11.
optional FlexSet
280D & 280D-Z with
Button (Key)
1st FlexSet 40B 2nd FlexSet 40B 3rd FlexSet 40B
FlexSet 280D
63 53 43 33 103 93 83 73 143 133 123 113
62 52 42 32 102 92 82 72 142 132 122 112

23 15 7 61 51 41 31 101 91 81 71 141 131 121 111
F4
22 14 6 60 50 40 30 100 90 80 70 140 130 120 110
F3 21 13 5 59 49 39 29 99 89 79 69 139 129 119 109
F2 20 12 4 58 48 38 28 98 88 78 68 138 128 118 108
19 11 3 57 47 37 27 97 87 77 67 137 127 117 107

F1
18 10 2 56 46 36 26 96 86 76 66 136 126 116 106
17 9 1 55 45 35 25 95 85 75 65 135 125 115 105
16 8 0 54 44 34 24 94 84 74 64 134 124 114 104
9-85
Station Controls

9-86
Station Controls
40B units
Number Locations
Figure 9-12.
optional FlexSet
280S/281S with
for FlexSet
Button (Key)
1st FlexSet 40B 2nd FlexSet 40B 3rd FlexSet 40B
FlexSet 280S, 281S

63 53 43 33 103 93 83 73 143 133 123 113
62 52 42 32 102 92 82 72 142 132 122 112

21 15 7 61 51 41 31 101 91 81 71 141 131 121 111
F4
20 14 6 60 50 40 30 100 90 80 70 140 130 120 110
F3 19 13 5 59 49 39 29 99 89 79 69 139 129 119 109
F2 18 12 4 58 48 38 28 98 88 78 68 138 128 118 108

17 11 3 57 47 37 27 97 87 77 67 137 127 117 107
F1
16 10 2 56 46 36 26 96 86 76 66 136 126 116 106
9 1 55 45 35 25 95 85 75 65 135 125 115 105
8 0 54 44 34 24 94 84 74 64 134 124 114 104
1 2 3
1 2 3 1 2 3 1 2 3
PI Reference Manual
PI Reference Manual
T208M/BL with an
Number Locations
Figure 9-13.
T207M/NP,
for T207M, T208M,
Button (Key)
optional TEM unit
TEM TEM
T207M, T208M
34 56
23 45
33 55
22 44
32 54
21 43
31 53
20 42
30 52
19 41
12 29 51
18 40
MSG XFER 28 50
03 07 11
17 39
27 49
CONF REDIAL
16 38
02 06 10
26 48
DIR HOLD 15 37
01 05 09 25 47
14 36
HEADSET MUTE SPKR 24 46
00 04 08 35
13
BUTT# 00 - 08 are phone fixed keys SHIFT

BUTT# 09 - 12 are phone programmable keys
9-87
Station Controls

T207M, T208M, Programmable Keys

T207M/NP,
T208M/BL Fixed The T207M, T208M, T207M/NP, T208M/BL phones include four programmable
Function Keys keys (Serial No. 09-12). These keys can be programmed and changed by the end
user and by the technician.
The TEM expansion units include 22 x 2 programmable keys (Serial No. 13-48).
These keys can be programmed and changed by the end user and by the technician.
Fixed Function Keys
The T207M, T208M, T207M/NP, T208M/BL phones include nine fixed function
keys (Serial No. 00-08). Do not change these keys. These keys are programmed by
default, by the system, as described in the table below.
 NOTE: The nine fixed key contents cannot be changed by the end user (i.e.
feature code is followed by an N).
Although the technician can change the fixed key contents on a per phone
basis, the keys revert back to the default programming when the telephone
is reset. Therefore, technicians should not attempt to change these keys.
Table 9-5: T207M, T208M, T207M/NP, T208M/BL Default and Key Serial No.
T207M, T208M, T207M/NP, T208M/BL

Default and Key Serial No.:
Left Middle Right

12
03 MSG. 07 XFER 11
(#175N) (#122N)
02 CONF 06 REDIAL 10
(#122N) (#143N)
01 DIRectory 05 HOLD 09
(#1994N) (#171N)
00 HEADSET 04 MIC. MUTE 08 SPKR

(#1302N) (#1320N) (#120N)
9-88
Figure 9-14.
First EKT/VDK 23 15 7
(Attendant)– CO.
Default Button (Key)
MSG. NIGHT LINE-8
Programming
#5 #185 7107
CC0 and all
European systems 22 14 6
UNATT. CALL CO.
ATTND. PARK LINE-7
#145 79 7106
21 13 5
DIRECT CO.
CAMP-ON PICKUP LINE-6
#176 77 7105
20 12 4
VOICE ALL CO.
PAGE PAGE LINE-5
#3 7300 7104
19 11 3
MIC. BRK CO.
MUTE IN LINE-4
#1320 #124 7103

18 10 2
XFER/ FORCE CO.
CONF. RLS. LINE-3
#122N #123 7102
17 9 1
SPKR./ EXCL. CO.
INTCM. SOURCE LINE-2
#120N #1321 7101
16 8 0
EXCL. CO.
HOLD DEST. LINE-1
#4, #11N #1322 7100
9-89
Figure 9-15.
First EKT/VDK 23 15 7
(Attendant)- UNATT.
Default Button (Key) ATTND. NIGHT-1 NIGHT-2
Programming
CC1,CC2 systems
#145 #185 #184
22 14 6
HNDSET/
SPKR ALARM
#1323 #1997
21 13 5
VOICE AUTO
PAGE REDIAL SERIES
#3 #178 #195
20 12 4
CALL NAME/
PARK OCC NUM.
79 #127 #128
19 11 3
BRK
CAMP-ON IN MSG.
#176 #124 #175

18 10 2
EXCL. MIC.
LOOP DEST. MUTE
#121N #1322 #1320
17 9 1
EXCL. FORCE
LOOP SOURCE RLS.
#121N #1321 #123
16 8 0
LOOP HOLD SPKR
#121N #4N #120N
9-90
Figure 9-16.
Standard EKT/VDK 23 15 7
- Default Button CO
(Key) Programming LINE-8 MSG
CCO 7107 #5
22 14 6
CO
LINE-7 DND
7106 #145
21 13 5
CO FWD
LINE-6 BSY/BA
7105 #147
20 12 4
CO MIC.
LINE-5 MUTE.
7104 #1320
19 11 3
CO
LINE-4 CAMP-ON
7103 #176N
18 10 2
CO XFER/
Note: LINE-3 CONF.
In all other systems,
only the following 7102 #122N

buttons (keys) are
programmed by 17 9 1
default:
CO SPKR/
LINE-2 INTCM
3: HOLD (#4N)
2: XFER (#122N) 7101 #120N
1: LOOP (#121N) 0
16 8
0: SPKR (#120N) CO
LINE-1 HOLD
7100 #4N
9-91
9-92
Station Controls
optional PEMs
Number Locations
Figure 9-17.
for EKT/VDK and

Button (Key)
EKT/VDK 1st PEM 2nd PEM 3rd PEM
23 15 7 63 55 47 39 31 103 95 87 79 71 143 135 127 119 111
22 14 6 62 54 46 38 30 102 94 86 78 70 142 134 126 118 110
21 13 5 61 53 45 37 29 101 93 85 77 69 141 133 125 117 109
20 12 4 60 52 44 36 28 100 92 84 76 68 140 132 124 116 108
19 11 3 59 51 43 35 27 99 91 83 75 67 139 131 123 115 107
18 10 2 58 50 42 34 26 98 90 82 74 66 138 130 122 114 106
17 9 1 57 49 41 33 25 97 89 81 73 65 137 129 121 113 105
16 8 0 56 48 40 32 24 96 88 80 72 64 136 128 120 112 104

PI Reference Manual
PI Reference Manual
Programming
Button (Key)
DKT23XX Default
Figure 9-18.
1st Attendant - Eu 1st Attendant (CC0 - USA) Standard DKT (EU and ROW)
DIRECT UNATT. DIRECT CO.

MSG. ALARM MSG. PAGE-Q1
PICKUP ATTND PICKUP LINE 7
ALL ALL CO.

LOOP PAGE-Q NIGHT-1 LOOP PAGE-Q2
PAGE PAGE LINE 6
VOICE CO.
LOOP BRK-IN NIGHT-2 LOOP PAGE-Q3 ALARM
PAGE LINE 5
FORCE AUTO XFER CO.

HOLD CAMP-ON BRK-IN HOLD
RLS. REDIAL LINE 4
EXCL. VOICE FORCE CO.

XFER CAMP-ON LOOP XFER
DEST. PAGE RLS. LINE3
EXCL. CALL MIC. EXCL. CO.

LOOP SPKR LOOP
SOURCE PARK MUTE SOURCE LINE 2
HNDSET/ MIC. CALL EXCL. CO.

SPKR HOLD SPKR
SPKR MUTE PARK DEST. LINE 1
9-93
Station Controls

Figure 9-19.
DKT23XX Default
Button (Key)
Programming-
CC1 Attendant
DIRECT UNATT. CO.

MSG. ATTND
PICKUP LINE 1
LOOP ALL CO.

PAGE-Q
PAGE LINE 2
VOICE CO.
LOOP BRK-IN PAGE LINE 3
FORCE AUTO CO.

PICKUP
RLS. REDIAL LINE 4
EXCL CO.
HOLD CAMP-ON
DEST. LINE 5
EXCL CALL CO.

XFER
SOURCE PARK LINE 6
HNDSET MIC. CO.

SPKR
MUTE LINE 7
SPKR
9-94
PI Reference Manual
Programming
DKT23xx/21xx/1110
Figure 9-20.
Button (Key)
& DST - Default
Standard DKTs:
DKT 23XX DKT 21XX DKT 1110 / DST
CO.
MSG.
LINE 7 CO.
DND
LINE 1
CO.
DND
LINE 6
MSG. CAMP-ON
CO.
CAMP-ON
LINE 5
CO. MIC. CO. MIC. MIC.

XFER XFER XFER
LINE 4 MUTE LINE 1 MUTE MUTE
CO. FWD. FWD. FWD.

LOOP LOOP MSG. LOOP
LINE3 BSY/HA BSY/HA BSY/HA
CO.
SPKR PAGE-Q SPKR DND PAGE-Q SPKR PAGE-Q
LINE 2
CO. PICKUP PICKUP PICKUP

HOLD HOLD CAMP-ON HOLD
LINE 1 GROUP GROUP GROUP
9-95
Station Controls

Figure 9-21.
Button (Key) Serial
Number locations
for DKT1110/DST
DKT 1110 / DST
7 5
6 4
F4 3
F3 2
F2 1
F1 0
4 FIXED
SYSTEM KEYS
9-96
PI Reference Manual
optional DPEMs
Number locations
Figure 9-22.
for DKT21XX and

Button (Key) Serial
1ST DPEM 2nd DPEM 3rd DPEM
47 37 27 17 87 77 67 57 127 117 107 97
DKT 21XX 46 36 26 16 86 76 66 56 126 116 106 96
45 35 25 15 85 75 65 55 125 115 105 95
44 34 24 14 84 74 64 54 124 114 104 94
43 33 23 13 83 73 63 53 123 113 103 93
42 32 22 12 82 72 62 52 122 112 102 92
F4 7 3 41 31 21 11 81 71 61 51 121 111 101 91
F3 6 2 40 30 20 10 80 70 60 50 120 110 100 90
F2 5 1 39 29 19 9 79 69 59 49 119 109 99 89
F1 4 0 38 28 18 8 78 68 58
4 FIXED
SYSTEM KEYS
9-97
Station Controls

9-98
Station Controls
Figure 9-23.
optional DPEMs
Number locations
for DKT23XX and
Button (Key) Serial
63 53 43 33 103 93 83 73 143 133 123 113
DKT 23XX 62 52 42 32 102 92 82 72 142 132 122 112
61 51 41 31 101 91 81 71 141 131 121 111
23 20 13 6 60 50 40 30 100 90 80 70 140 130 120 1110
22 19 12 5 59 49 39 29 99 89 79 69 139 129 119 109
21 18 11 4 58 48 38 28 98 88 78 68 138 128 118 108
F4 17 10 3 57 47 37 27 97 87 77 67 137 127 117 107
F3 16 9 2 56 46 36 26 96 86 76 66 136 126 116 106
F2 15 8 1 55 45 35 25 95 85 75 65 135 125 115 105
F1 14 7 0 54 44 34 24 94 84 74 64 134 124 114 104
4 FIXED
SYSTEM KEYS
PI Reference Manual
PI Reference Manual
Figure 9-24.
optional DPEMs
Number locations
(GKT43xx) and
for FlexSet 80
Button (Key) Serial
63 53 43 33 103 93 83 73 143 133 123 113
GKT 43XX 62 52 42 32 102 92 82 72 142 132 122 112
61 51 41 31 101 91 81 71 141 131 121 111
60 50 40 30 100 90 80 70 140 130 120 1110
59 49 39 29 99 89 79 69 139 129 119 109
58 48 38 28 98 88 78 68 138 128 118 108
F4 3 57 47 37 27 97 87 77 67 137 127 117 107
F3 2 56 46 36 26 96 86 76 66 136 126 116 106
F2 1 55 45 35 25 95 85 75 65 135 125 115 105
F1 0 54 44 34 24 94 84 74 64 134 124 114 104
4 FIXED
SYSTEM KEYS
9-99
Station Controls

Figure 9-25.
Button (key)
Number locations
for CoralAIR
Wireless Handsets
CoralAIR
wireless handset
1 2 3
4 5 6
Programmable Keys:
Only Buttons 0-7 are Coral programmable.
Button # 7 is reserved for Voicemail and is not station
programmable.
9-100
Figure 9-26. Button

(Key) Number
locations for FlexAir
Wireless Handsets
FlexAIR
Note: The handset < < OK
/C
buttons Ê to Ñ
correspond to button
ALT R
index #: 0 to 7,
1 2 3
respectively, when ABC DEF
programming from
the PI database. 4 5 6
GHI JKL MNO
7 8 9
8 9WXYZ

PQRS TUV
T-402, T-404, T-408 units T-304 unit
9-101
Figure 9-27.
Button (Key) Serial
Number locations for
Turret Console
PARTNER
FlexSet 40B units
1 2 3
3
FlexSet 40B Buttons

Partner
1 2 3
2
Partner 3rd
1 2 3
1
1 2 3
3
FlexSet 40B Buttons

Partner 2nd
1 2 3
2
Primary
1 2 3
1
FlexSet 40B Buttons

Partner 1st
Note:
When the Primary FlexSet has only one, two or no 40B units
attached, the Partner FlexSet 40B button numbers continue
from the last button number for the Primary FlexSet.
9-102
Keyset Fixed System Keys - Programming ç SYS

Fixed System This option allows programming the four Fixed System Keys (FSK) for all the
Keys following sets in the system identically. Programming is identical for all the
following sets.
• FlexSet 280, 280D, 280D-Z, 120, 120D, 120L
• FlexSet 281S, 121S, 280S, 120S
• FlexSet-IP 280S
• DKT
• DST
 Fixed System Keys cannot be programmed for EKT, VDK,

• FKT/Fonetasy
FlexAir/CoralAIR Wireless handsets, CPA, P-Series, T200 series, T300

series, P-series, SeaBeam, and all third-party SIP terminals.
See T207M, T208M, T207M/NP, T208M/BL Fixed Function Keys on page 9-88.
• Four Fixed System Keys are defined identically for all the system keysets.
• Change the FSKs only via the PI.
• The FSKs operate in the same manner as the other programmable keys, except
for updating LEDs, when Ports and Groups are programmed.
Fixed System Keys are programmed according to the identification serial number
(index #) associated with each key. The FSK defaults for the various systems are
shown below. Enter the appropriate code for each button, while the cursor/pointer
is on the appropriate button’s line.
Default for:
System Button
Keyset Fixed System Keys - Programming SYS

Serial No. CC0 CC1 All other
USA Israel systems
F1 HOLD (#171) SPKR (#120) SPKR (#120)
F2 SPKR (#120) XFER (#122) LOOP (#121)
F3 LOOP (#121) HOLD (#171) XFER (#122)
F4 XFER (#122) Group Pickup (76) HOLD (#171)
This table defines the feature or port dial number, or sequence of feature/port dial
numbers and additional digits stored for the button.
Table 9-3 on page 9-79 shows some typical types of functions that can be
programmed into a key/button.
! Station and trunk numbers may not be programmed in Fixed System

Keys.
9-103
Keyset Soft Keys Idle Set ç SKEY [0,2,1,2,4]
This branch enable the bottom line display control via the Coral main software,
when SOFT_KEYS_MENU (page 4-29) in Sizes Tab is set to Selectable, for the
following keysets:
• FlexSet 120S, 280S (installed with software versions 3.50 or higher)
 For FlexSet 120S/280S installed with software version 3.50 or higher and
• T207M, T208M, T207M/NP, T208M/BL
the Coral Main Software Version is 15.5 or higher, the third line display
may be controlled by either of the following two options:
• The FlexSet software — the third line display is fixed and cannot be
changed.
• The Coral Main Software — the features displayed on the third line may
be presented in a different order and/or some features may not be
 For FlexSet 121S, 281S, T207M, T208M, T207M/NP, T208M/BL; the

displayed at all, depending on the customer request.
bottom line display may be controlled only by the Coral Main Software.
SOFT_KEYS_MENU (page 4-29) in SIZ TAB must be set to Selectable
otherwise no bottom line display is shown.
This branch is used to enable the technician to define up to 15 Soft Key sets, as well
as, allow the technician to assign a particular set to a soft key station or a range of
stations. Each set includes a list of features in the order entered by the technician.
The first set, Set# 0 includes the feature defaults (names and order of display)
originally programmed into the phone. This set is embedded in the Coral Main
Keyset Soft Keys Idle Set SKEY [0,2,1,2,4]
Software Version and cannot be changed.

Sets# 1-15 may be created and/or updated by the technician as required.
 Notes:
• Once the Sets are defined in this branch, the technician may assign the
Set to a station via SOFTKEY: IDLE_SET [94] (page 9-74) in Keyset
Definition branch (KEY).
• The SOFTKEY: 3RD_LINE_CONTROL [95] (page 9-74) KEY parameter can
be used to view which entity controls the bottom line display.
9-104
Once this route is selected the following option menu is available.
Option Description
0 - UPDATE Allows updating Sets 1 to 15.
1 - DISPLAY Displays the bottom line options for the phones per
requested Set. Sets 0 to 15 are available.
6 - DUPLICATE Duplicates a range of phones based on an previously

defined Set.
FROM/TO SET# 0..15 for Display Option

1..15 for Update Option
Default: All Sets
 Set#0 cannot be updated.

Enter the Set# range to be updated or displayed from the lowest Set# to the highest.
Each set can be updated or duplicated and can be customized by the technician.
SOFTKEY IDLE SET Range: Any of the options 01 to 39 in any order between parenthesis
OPTIONS Table 9-7 lists the feature options by name, number and contents;
Default: Set 0 - predefined by phone’s software version (contains features
01 to 39 in same order)
Default: Sets 1..15 (empty sets)
This parameter allows the technician to create a list of features that is to be
displayed on the bottom line for the idle FlexSet 120S/280S (versions 3.50 or

higher), T207M, T208M, T207M/NP, T208M/BL, and the idle FlexSet 121S/281S
phones.
The feature options are shown on the phones in the same order as shown in this
parameter.
This is the feature list currently offered by the Coral and the soft key phones:
01-Msg 02-CALLog 03-Dir 04-FWD 05-Music
06-DND 07-FlexiC 08-Redial 09-Page_Q 10-Hold
11-Remind 12-Pickup 13-CampOn 14-Park 15-V-Page
16-WhspPg 17-SltMon 18-AcctCd 19-IdCtrl 20-WakeUp
21-aWake 22-CnfIns 23-GpCall 24-AcdUcd 25-Lock
26-Exec 27-COS-Sw 28-Setup 29-Trace 30-aTrace
31-RoomSt 32-aRmSts 33-BG:Fwd 34-aFwd 35-Charge
36-St.Set 37-Tk.Set 38-System 39-ELA 40-
41- 42-
replace (...)/add after N (a,N,...)/remove (r,...)/end <CR>:
The following list includes the feature option numbers and their corresponding
9-105
names that are displayed when Italian is selected with the Multilingual Displays
feature (#1328). Table 9-6 displays the SKEY feature options when English is
the selected language and the corresponding Italian SKEY feature options.
01-Msg 02-RegCmt 03-_Dir 04-_Dev 05-Music 06-DND
07-FlexiC 08-Reselz 09-ParchS 10-Atts 11-Promem
12-Pickup 13-Richmt 14-Parc
15-Annunc 16-WhspPg 17-SltMon 18-AcctCd 19-IdCtrl
20-Svegl 21-aSveg 22-CnfIns 23-ChmtGr 24-AcdUcd
25-Bloc 26-_Exec 27-COS-Sw 28-Setup
29-Trace 30-aTrace 31-StCame 32-aStCam 33-GB:Dev
34-aDev 35-Costo
36-St.Set 37-Ln.Set 38-Sistem 39-ELA 40- 41-42-
replace (...) / add after N (a,N,...) / remove (r,...) /
end <CR>:
Table 9-6: SKEY Feature Options (when Italian is the Displayed Language)
Feature Feature Feature Name Sub Menus and/or

Option # Acronym Feature Codes
FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
01 Msg Msg Message Includes Message sub

menu:
• Message Leave
(#175),
• Message Cancel
(#1440)
02 RegCmt Log Call Log No feature dial

number.
Call Log cannot be used
if it is not included in the
user’s feature set.
03 Dir Dir Directory Includes Directory

(#1994) sub menu:
• New: Add new
entry to Private
Directory
• Next: Search by
scrolling
9-106

FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
04 Dev Dev Call Forward Includes the sub menu

for all the different types
of Call Forward options
(not including Attendant
and Boss).
Note! See FlexSet
User guide for complete
list.
05 Music N/A Music Includes Music sub

menu:
• Music On/Off
(#135)
• Music Tuner
(#1329)
06 DND DND Do Not Disturb #145
07 FlexiC FlxC FlexiCall Includes FlexiCall sub

menu:
• All (#17710)
• External (#17711)
• Internal (#17712)
08 Reselz Rslz Redial Options Includes Redial sub

menu:
• Last Number
Redial (#143)

• Saved Number
(#196)
• Auto-Redial
(#178)
09 ParchS Prc Page Que 7060Ü
10 Atts Atts Call Hold #171
11 Promem Prmr Reminder #172

Request
12 Pickup PkUp Pickup Includes Pickup sub

menu:
• Direct Pickup
(#180)
• Group Pickup
(#181)
• Night Answer
(#192)
9-107

FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
13 Richmt Camp Camp-On - Call #176

Back
14 Parc Parc Call Park #183
15 Annunc VPg Voice Page to #191

Single Keyset
16 WhspPg WPg Whisper Page #1744
17 SltMon SM Silent Monitor Includes Silent Monitor

sub menu:
• 2-way (#1981)
• Split (#1448)
18 AcctCd ActC Account Code #1990
19 IdCtrl CID Caller ID Control #1444
20 Svegl Sveg Wakeup Request #173
21 aSveg aSV Attendant #1980

Wakeup
22 CnfIns cIns Conference #1983

Inspect
23 ChmtGr GpCl Group Call Includes Group Call sub

menu:
• Partner Release
(#1446)
• Group Release
(#1447)
• Add-On (#1449)
24 AcdUcd ACD ACD/UCD Includes ACD/UCD

features Hunt group sub menu
• See FlexSet user
guide for complete
list
25 Bloc Bloc Phone Dial Lock #148
26 Exec Exec Executive #170

Privilege
27 COS-Sw COS COS Switchover #149
9-108

FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
28 Setup fSet Phone Setup Includes all the phone

features setup features:
• Ring
• Auto Answer
• VP-AA
• VP-Rcv
• Elapsed Time
• Headset
• Idle Display
• Language
• Passcode
• Program Key
• Preference
• Private Library
• Secure
• DND-WP
• Privacy
• Ex Hold
• Move St (Auto Set
Relocate)
29 Trace Trc Malicious Call Includes Call Trace sub

Trace menu:
• On/Off (#1740)
• Print (#1741)
30 aTrace aTrc Attendant Includes Attendant Call

Malicious Call Trace sub menu:
Trace • On/Off #(1742)
• Print (#1743)
31 StCame Room Room Status 7026Ü

or
Canned
Messages
These features
are mutually
exclusive,
therefore
activating this soft
key will only
activate the
relevant feature
for your system.
32 aStCam aRS Attendant Room 7010Ü

Status
9-109

FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
33 GB:dev bDev Boss Group: Call Includes the sub Menu

Forward for Boss Group Call
Forward Options
• See the FlexSet
User guide
34 aDev aDev Attendant Call Includes the sub Menu

Forward for Attendant Call
Forward Options
• See the FlexSet
User guide
35 Costo Cost Call Charge Print Includes Call Charge

sub menu:
• Report (#1972)
• Reset (#1978)
36 St.Set sSet Attendant Station Includes Attendant

Features: Setup Station Features sub
menu:
• Check-In/Out
• Attendant DND
• Hot Station Delay
• Hot Station
Immediate
• Originating Only
• Station Restriction
• Block Station
• Terminating Only
37 Ln.Set tSet Attendant Trunk Includes Attendant

Features: Setup Trunk Features sub
menu:
• Auto Guard
• CO Block
• Busy Out
• Direct In Line
• Nite1/Nite2
• Drop on No Dial
• Hot Trunk
Immediate
• Hot Trunk Delay
• Incoming Only
• Outgoing Only
• Reserved By
Attendant
9-110

FlexSet T207M,
120S, T208M,
280S, T207M/NP,
121S, T208M/BL
281S
38 Sistem Sis System Features: Includes Attendant

Setup System Features sub
menu:
• Alarm
• Attendant to...
• Day/Nite1/2
• Public Library
• Set Time
39 ELA ELA Extension Line Enter ELA group

Appearance number and proceed to
define Line Keys ring
state (Yes ring, No Ring
or Delay ring) for phone
40-42 For Future Use
Create or edit the feature list by entering the feature option numbers within
parenthesis as follows:
To Create a New List or Replace an Old List:
Enter: (feature number1, feature number 2, ...)
To Insert Features:
Enter (a, N, feature number1, feature number 2, ...)

where:
- N is the sequential number of the feature position (and not the feature
number) after which you want to enter a new feature.
- feature number1 is the number of the first feature to be inserted
- feature number2 is the number of the second feature to be inserted
- etc.
To Insert a Feature at the beginning of a List:
Enter (a, 0, feature number)
To Remove numbers:
Enter: (r, N1, N2,...)
where:
- N1 is the sequential number of the feature position (and not the feature
number) of the first number you want to remove
- N2 is the sequential number of the feature position (and not the feature
number) of the second number you want to remove
9-111
To remove all numbers,

Enter: ( )
Examples:
• To create a SET that offers the Message, Call Log, Call Forward, DND, and
Silent Monitor features, in that order, enter the following in this parameter:
(01 02 04 06 17)
• To insert 29-Call Trace to this SET after 02-Call Log, the second item in the
list, enter: (a 2 29)
• The resulting SET is displayed as:
(01 02 29 04 06 17)
• To remove 17-Silent Monitor, the sixth item in the SET, enter: (r 6)
• To add 8-Redial at the beginning of the list, enter: (a 0 8)
Feature Names and Sub Menus
See the T207M, T208M, T207M/NP, T208M/BL, FlexSet 120S/121S or
FlexSet 280S/281S User Guides for a complete description of feature option menus
and sub menus. The feature display may be limited by the user’s COS definition
Table 9-7: SKEY Feature Options
Feature Feature Feature Name Sub Menus and/or Feature Codes

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
01 Msg Msg Message Includes Message sub menu:

• Message Leave (#175)
• Message Cancel (#1440)
02 CALLog Log Call Log No feature dial number.

Call Log cannot be used if it is not
included in the user’s feature set.
03 Dir Dir Directory #1994 or ##

Sub menu includes:
• New: Add new entry to Private
Directory
• Next: Search by scrolling
04 Fwd Fwd Call Forward Includes the sub menu for all the
different types of Call Forward
options (not including Attendant and
Boss Group).
• See User guide for complete list.
9-112

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
 Note: Not available for

05 Music N/A Music Includes Music sub menu:
• Music On/Off (#135)
T207M, T208M, • Music Tuner (#1329)

T207M/NP, T208M/BL
06 DND DND Do Not Disturb #145
07 FlexiC FlxC FlexiCall Includes FlexiCall sub menu:

• All (#17710)
• External (#17711)
• Internal (#17712)
08 Redial Redl Redial Options Includes Redial sub menu:

• Last Number Redial (#143)
• Saved Number (#196)
• Auto-Redial (#178)
09 Page_Q PgQ Page Que Includes Page Que sub menu:

• PageQ1/PgQ1 (7060)

• PagQ10/PQ10 (7069)
10 Hold Hold Call Hold #171
11 Remind Remd Reminder Request #172
12 Pickup PkUp Pickup Includes Pickup sub menu:

• Direct Pickup (#180)
• Group Pickup (#181)
• Night Answer (#192)
13 CampOn Camp Camp-On - Call Back #176
14 Park Park Call Park #183
9-113

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
15 V-Page VPg Voice Page to Single Keyset #191
16 WhspPg WPg Whisper Page #1744
17 SltMon SM Silent Monitor Includes Silent Monitor sub menu:

• Both (2-way) SM2 (#1981)
• Split (1-way) SM1 (#1448)
18 AcctCd ActC Account Code #1990
19 IdCtrl CID Caller ID Control #1444
20 WakeUp Wake Wakeup Request #173
21 aWake aWk Attendant Wakeup #1980
22 CnfIns cIns Conference Inspect #1983
23 GpCall GpCl Group Call Includes Group Call sub menu:

• Partner Release (#1446)
• Group Release (#1447)
• Add-On (#1449)
24 AcdUcd ACD ACD/UCD features Includes ACD/UCD Hunt group sub

menu
• See User Guide for complete list
25 Lock Lock Phone Dial Lock #148
26 Exec Exec Executive Privilege #170
27 COS-Sw COS COS Switchover #149
9-114

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
28 Setup fSet Phone Setup features Includes all the phone setup features:
• Ring
• Auto Answer
• VP-AA
• VP-Rcv
• Elapsed Time
• Headset Only
• Idle Display
• Language
• Passcode
• Program Key
• Preference
• Private Library
• Secure
• DND-WP
• Privacy
• Ex Hold
• Move St (Auto Set Relocate)

29 Trace Trc Malicious Call Trace Includes Call Trace sub menu:
• On/Off (#1740)
• Print (#1741)
30 aTrace aTrc Attendant Malicious Call Includes Attendant Call Trace sub
Trace menu:
• On/Off (#1742)
• Print (#1743)
31 RoomSt Room Room Status 7026Ü
32 aRmSts aRS Attendant Room Status 7010Ü
33 BG:Fwd bFwd Boss Group: Call Forward Includes the sub Menu for Boss
Group Call Forward Options
• See the User guide
34 aFwd aFwd Attendant Call Forward Includes the sub Menu for Attendant
Call Forward Options
• See the User guide
9-115

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
35 Charge Chrg Call Charge Print Includes Call Charge sub menu:
• Report (#1972)
• Reset (#1978)
36 St.Set sSet Attendant Station Features: Includes Attendant Station Features

Setup sub menu:
• Check-In/Out
• Do Not Disturb
• Hot Station Delay
• Hot Station Immediate
• Originating Only
• Station Restriction
• Block Station
• Terminating Only
37 Tk.Set tSet Attendant Trunk Features: Includes Attendant Trunk Features

Setup sub menu:
• Auto Guard
• CO Block
• Busy Out
• Direct In Line
• Nite1/Nite2
• Drop on No Dial
• Hot Trunk Immediate
• Hot Trunk Delay
• Incoming Only
• Outgoing Only
• Reserved By Attendant
38 System Sys System Features: Setup Includes Attendant System Features

sub menu:
• Alarm
• Attendant to...
• Day/Nite1/2
• Public Library
• Set Time
39 ELA ELA Extension Line Appearance #17718
9-116

Option Acronym
#
FlexSet T207M,
120S T208M,
280S T207M/NP,
T208M/BL
121S
281S
40 N/A N/A For Future Use For Future Use
9-117
Keyset Preference - Programming ç PREF [0,2,1,2,1]
Preference Programming allows defining each of the following Keysets with its
preference destinations (up to 12):
• FlexSet 280, 280D, 280D-Z, 120, 120D, 120L
• FlexSet 281S, 121S, 280S, 120S
• FlexSet-IP 280S
• T207M, T208M, T207M/NP, T208M/BL
• GKT
• DKT
• DST
• EKT
• VDK
 Preference Programming is irrelevant for P-Seies (such as: P-335, P-450),

• FKT
T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam, third-party

SIP terminals, Wireless handsets (FlexAir/CoralAIR), CPA, SLT and
Magneto station.
Definitions can be made either from the PI or from the keyset when the Class of
Service permits. A preference priority level can be assigned to each keyset. This
priority level informs the system which line, loop or trunk is selected when:
• the station handset is lifted
• the SPKR key is pressed
• a number is dialed on the keypad
Keyset Preference - Programming PREF [0,2,1,2,1]
If an outside line is selected as first priority, a Loop or Line key should also be
programmed in order to use features and permit internal dialing. Failure to do so
blocks feature access.
Enter the keyset dial number for which you would like to choose the preference:
For example: For a FlexSet dial no. 400, the preferences can be set as such:
>400
PREF # 0 - 7100
PREF # 1 - 7101
PREF # 2 - #121
PREF # 3 - 7102
PREF # 4 - 7103
PREF # 5 - 7104
PREF # 6 - 7105
PREF # 7 - 7106
PREF # 8 - 7107
PREF # 9 - 7108
PREF # 10 - 7109
PREF # 11 - 7110
9-118
FROM/TO DIAL # Any valid system Keyset station number, All

Enter required range of keyset dial numbers FROM the lowest dial number TO the
highest dial number.
ENTER PREF # (n) 0..11

This parameter is used to enter the various priority levels destinations when
off-hook, and determine the priority destinations. “n” is a number from 0-11.
 When ELA lines are selected, the maximum number of priority destinations
is reduced. Each ELA line requires three PREF # entries. Therefore, the
maximum number of priority destinations available is proportionately
reduced by the number of ELA lines programmed below. Up to four ELA
line numbers can be entered.
PREF # (n) A, R, CR (no default)

Once a preference number is selected, this option appears for updating the
preference destinations. “n” is a number from 0-11.
A: Add (insert) new number at current location
R: Remove number
CR: Skip number and keep its current content.
PREF# (n) Any system trunk number, trunk group number, Routing Access number, Dial
service number, phone loop, loop originating only, ELA line number or boss
group line number.
None (no preferences are defined as the default)
Keyset Preference - Programming PREF [0,2,1,2,1]

This option is used when display mode is selected. “n” is a number from 0-11.
9-119
APA, PEX/APA and APDL RS-232 Setup ç CDB,8

SAU Requirement: APA on page 3-15.
The Application Processing Adapter (APA) allows defining all RS-232 serial ports
connected to the APA ports. The parameters listed here are used to setup a
Coral FlexSet 280D,280S,281S,80S,80P, APDL, GKT, or DKT with APA or any
other API circuitry requiring an RS-232 interface to the Coral system.
An APA port enables accessing system information onto a PC for a single CAP,
Coral Navigator, FlexCT CallMaster, FlexCT TAPIdriver, FlexCT Contact
Launcher and other applications compliant with the FlexCT proprietary API
products.
APA provides a programmable serial RS-232E applications interface and is
available on the following proprietary units:
• FlexAPDL (Issue 9 or lower) with APA-F
• FlexAPDL (Issue 10 or higher) with APDL-FS
• FlexSet 280D with PEX/APA-FS
• FlexSet 280S with APA-F
• FlexSet 280S with PEX/APA-F
• FlexSet 80S
• FlexSet 80P
• GKT 4320
• GKT 4321
• DKT 2322
APA, PEX/APA and APDL RS-232 Setup CDB,8
 The number of APA ports is limited by Feature Authorization (SAU

• DKT APDL
requirement), see 17-APA (page 3-15).

FlexSet APA-F unit - attaches to the underside of the Coral FlexSet 280S or APDL
(Issue 9 or lower).
FlexSet PEX/APA-F unit - PEX-F and APA-F in one module, attaches to the
underside of the Coral FlexSet 280S or APDL (Issue 9 or lower). The PEX
provides external power supply input for extended loop operation, Coral FlexSet
40B interface, recorder coupler interface, listen-only handset and ISDN peripheral
bus extension interface.
FlexSet PEX/APA-FS unit - PEX-FS and APA-FS in one module, attaches to the
underside of the Coral FlexSet 280D,280S,281S. The PEX-FS provides external
power supply input for extended loop operation, Coral FlexSet 40B interface,
recorder coupler interface, listen-only handset and ISDN peripheral bus extension
interface.
9-120
FlexSet APDL (Application Process Data Link) module - same as the

combination of Coral FlexSet 280S with APA but has no voice/audible/keypad
circuitry. The APDL can provide an RS-232E link when no voice circuitry is
needed. It supports external applications needing digital links to the Coral such as:
Coral SMDI Converter (CSC), OEM Voicemail and the Proctor E911 interface
among others.
 Notes:
• Do not install CAP and CCM on the same APA.
! Each of the following parameters must be identically defined in the

FlexCT, CCM, CAP,..., Server databases.
Otherwise, accessing the external equipment results in errors or the
system malfunctions.
PROTOCOL 0 (Manufacturer), 1 (Transparent)

Enter the required protocol element. Entering 0 defines the Coral Manufacturer’s
Protocol and is generally used for all APA applications. Entering 1 defines a
transparent D-channel protocol used for system upkeep and as a preparation for
future applications.
BAUD RATE 0 (4,800 bps), 1 (9,600 bps), 2 (19,200 bps)

Determines the interface baud rate. Enter the number corresponding to the desired
rate.
N_BITS 7, 8

Determines the number of data bits used.
PARITY N (No parity), E (Even), O (Odd)

Determines the parity check method.
STOP_BITS 1, 2
Determines the number of stop bits used.
ECHO Yes (local echo)/ No

Enables the control of a local echo from the APA to the PC causing every character
transmitted by the PC to automatically appear on screen.
9-121
Transfers the updated APA/RS-232 database immediately to all FlexSet/Keyset
peripheral cards (8/16/24SFT, 8/16SFTipx, 8/16/24SFT Office, 4S8F Office,
8S8F Office, 4S16F Office, 8S16F Office, 8/16SFTsl, 8F8Ssl, 8/16/24SDT,
8/16SKD and 8SVD) for all APA, PEX/APA and APDL units. Regardless of entry,
update which has been made. This parameter is used only in the Update Mode.
9-122
Wireless Stations - CoralAIR ç WST,0 [0,2,1,8]
Coral systems equipped with SKW peripheral cards provide for wireless station
ports enabling service for portable handsets (wireless telephones) that can be used
within the system facilities. A unique Electronic Serial Number (ESN) is
programmed into each handset during the manufacturing process. This ESN must
then be registered into the Coral PI database in order to identify the particular
handset with the specific Coral system and enable wireless activity.
 The System ID number, defined in System Features - SFE,12, (see page

6-56) and dial numbers (defined in the NPL [40]) are not sufficient for
defining the portable handsets in the system database.
The ESN numbers can be entered by designating the index numbers or dial
numbers, allocated to the wireless units.
Option Description
0 - INDEX_ACCESS The ESN numbers can be entered by

designating the index numbers, as
described on page 9-124.
1 - DIAL NUMBERS_ACCESS The ESN numbers can be entered by
designating dial numbers, as described
on page 9-125.
Wireless Stations - CoralAIR WST,0 [0,2,1,8]
9-123
0-INDEX_
ACCESS
FROM/TO INDEX# 0 to Maximum defined in Sizes, see WIRELESS in Chapter 4
All
Enter the range of wireless station index numbers FROM the lowest index number.
TO the highest index number. Use the NPL,0,5,40 route to identify the index
numbers associated with the wireless units.
DIAL# 
Displays the dial number (up to 8 digits) for the portable handset associated with
the index number above.
ESN CODE See the portable handset

Enter the ESN code of the portable handset defined with the above dial number.
For PCS, 1.9GHz models
To find the ESN code, perform the following operations on the handset unit:
1. Press the FCN key to place the idle handset in menu operation.
2. Use the scroll s t keys to search for SYSTEM CONFING. Fn 10
3. Press FCN again to display SID#0.
4. Press the END button to display the ESN number. The ESN number is
displayed for about five seconds.
See the CoralAIR Wireless Systems Installation Manual, Chapter 6 for details.
For DECT models:
The ESN is found on the back of the handset unit, see the original manufacturer’s
handset User Guide.

9-124
1-DIAL
NUMBERS_
ACCESS
FROM/TO DIAL# Any valid system WIRELESS dial number (see Route: NPL, 0,5,40), All
Enter the range of wireless station dial numbers. FROM the lowest dial number TO
the highest dial number. Use the NPL,0,5,40 route to identify the wireless dial
numbers.
INDEX# 
0..1536
Displays the index number for the portable handset associated with the dial number
above.
ESN CODE See the portable handset

Enter the ESN code of the portable handset defined with the above index number.
For PCS, 1.9GHz models
To find the ESN code, perform the following operations on the handset unit:
1. Press the FCN key to place the idle handset in menu operation.
2. Use the scroll s t keys to search for SYSTEM CONFIG. Fn 10
3. Press FCN again to display SID#0.
4. Press the END button to display the ESN number. The ESN number
disappears after about five seconds.
See the CoralAIR Wireless Systems Installation Manual, Chapter 6 for details.
For DECT models:

The ESN is found on the back of the handset unit, see the original manufacturer’s
handset User Guide.
9-125
Magneto 8SM Card Database ç CDB,5

The Magneto 8SM and 8SMipx cards (herein referred to as the “8SM”) database
allows defining the Magneto 8SM Card ringing parameters. The system contains
three Magneto card databases (0-2). One Magneto card database is assigned to each
Magneto 8SM station card (see Card List - Chapter 6). These cards provide ring
down station circuits for magneto sets. Field numbers appear in square brackets ([
]).
FROM 0..2
TO 0..2
CARD_DB #
Enter the required range of card database tables FROM the lowest card number TO
the highest card number.
INTERNAL RING The following two parameters ON and OFF, control the ring cadence for internal
CADENCES: (station-to-magneto station) calls.
ON [0] 50..500..12750 ms (in 50 ms increments)

Sets the internal ring cadence. See figure below.
OFF [1] 50..2000..12750 ms (in 50 ms increments)

Sets the duration of the silent period between ring cycles. See figure below.
EXTERNAL The following six parameters set the ring cadences for incoming trunk calls.
RING
CADENCES:
ON_1 [2] 50..500..12750 ms (in 50 ms increments)

Magneto 8SM Card Database CDB,5
CC1: 1000
Sets the duration of the first ring in a three-ring cycle. See figure below.
OFF1 [3] 50..500..12750 ms (in 50 ms increments)

CC1: 3000
Sets the silent period between the ON_1 and ON_2 intervals. See figure below.
Figure 9-28.
Internal Ring ON
Cadence
Ringing Silence
OFF
9-126
ON_2 [4] 0..500..12750 ms

CC1: 0
Same as ON_1, but for the second (of three) ringing periods.
OFF2 [5] 0..2000..12750 ms

CC1: 0
ON_3 [6] 0..12750 ms

Same as ON_1, except for the third (of three) ringing periods.
OFF3 [7] 0..12750 ms

Same as OFF2, except for the silent period between ON_3 and ON_1.
Figure 9-29.
External Ring ON 1 ON 2 ON 3
Cadence
OFF 1 OFF 2 OFF 3
MIN_RING_IN [8] 10..500..1200 ms

Minimum Incoming Ring Recognition determines the minimum period that a
magneto station user should generate a ring voltage before the system identifies the
following signals:
• Offhook signal during idle state

• Disconnect signal during conversation
RING_SIG_RJCT [9] 0..5..254 seconds

Ring Signal Reject determines the period following the completion of a valid
offhook (MIN RING IN) during which any electrical ring voltage generated by the
magneto station user is ignored. This timer is intended to avoid a false disconnect
signal, (see System Features Magneto Disc Ring - Chapter 6).
[10]
Transfers the updated card database immediately to the station cards. Regardless of
including any update made. This parameter is used only in the Update mode.
9-127
9-128
10 Groups
This chapter describes the various feature groups used in the system. The various
groups and page numbers are listed below:
Hunt Group .................................................................................................10-2
Boss Group ...............................................................................................10-18
Pickup Group............................................................................................10-23
Zoned Voice Page Group..........................................................................10-24
Bell/UNA Group.......................................................................................10-25
Group Calls...............................................................................................10-26
ELA Group ...............................................................................................10-38
 Generally, after typing the From and To range of group numbers, updating
or viewing groups can be carried out either on all groups defined by
From/To or on specific group members.
The choice is available in response to the question:
Any specific member (CR/NUM) -

[Enter] Pressing [Enter] displays or updates all currently
All Groups: defined groups.
[NUM] Typing in a single dial number allows displaying or
Group updating a specific group, i.e. groups which include the
Member: typed member.
For example: While in the Boss Group node entering
4526 displays all boss group sets defined with 4526 as
one of the members.
10-1
Groups PI Reference Manual
Hunt Group ç HUNT [0,5,0]
Hunt groups are composed of a list of members at various destinations (stations,

public libraries, ports, etc.). These telephone members are externally accessed by
dialing the Hunt group number. The conversation is routed to the various Hunt
group members by one of the following user determined methods:
• Terminal (each call directed to first member available in numerical order),
• Circular (call directed to first member available following the last member to
receive a call)
• Statistical (each ACD call directed to the member who has been verified in
idle for the longest time).
Additionally, a Supervisor entry permits routing overflow calls (not answered) to a
station, public library, trunk or trunk group, boss group, or another hunt group. A
hunt group may also function as a Uniform Call Distribution (UCD) group or
Automatic Call Distribution group (ACD), with announcement devices permitting
calls arriving at a busy group to be answered by a recorded announcement. A
station may be a member of several Hunt groups.
COS: The Hunt Group COS is determined by the COS authorized for the first
member of the Group.
! For Coral systems including PC_ACD and CCM systems, define all the
ACD parameters in the PC_ACD or CCM database. All changes and
additions to dialing numbers for accessing ACD groups in the General
NPL, require immediate changes as well in the PC_ACD/CCM database
(and then reset the server computer). Otherwise, accessing the ACD
groups results in error messages.
Hunt Group HUNT [0,5,0]
10-2
PI Reference Manual Groups
FROM/TO HUNT# Any valid system hunt group dial number; All
Enter the required range of hunt group dial numbers, FROM the lowest dial number
TO the highest dial number.
NAME:
SHORT(5) Maximum of 5 printable ASCII characters, R (Remove for BLANK)
Defines the short name (up to 5 alphanumeric characters) of the Hunt group, which
appears on a member’s keyset equipped with a display when a call is directed to the
group. When BLANK is entered, a group name does not appear on the keyset
display and the Hunt group dial number is displayed.
FULL(16) Maximum of 16 printable ASCII characters, R (Remove for BLANK)

Defines the full name (up to 16 alphanumeric characters) of the Hunt group, which
display and the Hunt group dial number is displayed.
This name is used for the Hunt Group entries of the system’s Shared Directory. Full
Names defined as Blank are not copied to the Shared Directory.
GROUP TYPE U(UCD)/A(ACD)
 Software Authorization is needed for ACD group type definition.

Determines whether the hunt group is either a UCD or ACD type.
Set this parameter to A (ACD) for PC-ACD, CCM or iVMFipx or IPC/SFC ports.

Set this parameter to A (ACD) for Announcer ports from an SeaMail, IPC/SFC,
IPC/uCMC and iVMFipx. When ANNOUNCER [34] on page 9-42 is defined Yes.
IPC/SFC: If the live record feature is to be used, the last port on this card
should not be defined as a Hunt Group member.
Changing the group type from ACD to UCD or vice versa is not permitted when
members already exist in the group.
10-3
IVR_ACD Yes/No
(ACD only)
When a caller is waiting for his call to be answered by an ACD group, set this
parameter to Yes to have the call simultaneously camp-on to the ACD group and
also be answered by an IVR (which administers a related application).
The caller continues waiting to be answered by the ACD group while he/she is
connected to the IVR and does not lose his/her “place in line”. When the ACD
group is free to answer the call (i.e. an agent is freed) the IVR is disconnected and
the call goes through to the agent immediately.
 If the IVR destination is a station number not defined as a Voicemail port,

then, once the IVR connection is made, the caller does not continue
camping-on to the ACD group. The caller is now directly connected to the
IVR.
When this parameter is set to Yes, the following parameters are not relevant and
therefore not displayed:
• VM_GROUP (ACD only)
• TIME_TO_2ND_ANN
• ENTER 1ST ANNOUNCER
• ENTER 2ND ANNOUNCER
VM_GROUP Yes/No
(ACD only)

This parameter does not appear if IVR_ACD (ACD only), above, is set to
Yes.
Defines all members of this group as SLT or Keyset ports defined for Voicemail
systems.
When updating this parameter:
1. Check that the MEM # (A/R/CR) group is empty.
2. Define the GROUP TYPE as an ACD group.

3. Ensure that each group member (i.e. the defined port) is defined only in one
 All members of this group should be defined with Voicemail

group (a port cannot be defined in more than one VM group).
(see VOICE_MAIL [36] (page 9-16) for SLTs and

VOICE_MAIL (DTMF receive) [28] (page 9-40) for Keysets/FlexSets.
Set this parameter to Yes for a Hunt Group whose members originate from ports on
an iVMFipx card
Set this parameter to Yes for Announcer ports from an IPC/SFC, seaMail.
When a station is defined as a group member, the LOGIN is automatically assigned
by the system. When the station is removed from the group, it automatically logs
out.
10-4
LOAD ID Yes/No
(ACD only)
Determines whether an ACD member is required to enter an ID number. When an
ID number is not required the port dial number is used for identifying the ACD
agent.
CAP_ Yes/No
REINTRODUCTION_
Defines whether or not a CAP application is prompted with a PRESENT message
OF_QUEUED_CALL
when a call waiting (multi-appearance) for an available agent is removed from the
waiting queue and starts ringing at the available agent’s station.
A message to CAP is always sent when the multi-appearance call enters the ACD
waiting queue.
SEARCH TYPE 0 (circular) / 1 (terminal) / 2 (statistical ACD group)

Determines the call distribution method:
• Terminal: Always start with MEM #1
• Circular: Start with the MEM following the last member who received a Hunt
group call
• Statistical (ACD only): The next MEM to be called is the one who has been
verified in idle for the longest time.
Statistical Call Distribution
Idle time in Statistical Search is an ongoing current measurement for each group
member. It is not a cumulative measurement.
The start and stop time for the “idle time count” begins or ends when:
• An ACD call is answered
• The member logs in or out
• Release or Resume is activated on the member station
• Call Forward is activated or cancelled on the member station
 Notes:
• The DND feature is activated or cancelled on the member station
• Statistical Search types are recommended for low traffic ACD groups.
• In order to select a statistical search type, ACD_STATISTICAL_SEARCH
must be set to “Y” (see page 4-26). Attempting to define SEARCH TYPE
in a non-initialized system generates an error message.
10-5
OVERFLOW Any valid system dial number of a station, boss group, hunt group,
public library, Routing Access, Dial Service, trunk or
trunk group (for dictation equipment, etc.) or
R (Remove current number for None)
Enter the dial number to which all unanswered or non serviceable calls are routed.
EXTENDED Yes/No
OVERFLOW
• This parameter appears only when GROUP TYPE (page 10-3) is set to
(ACD only) ACD.
• The INACTIVE GROUP SETTINGS, UNAVAILABLE GROUP SETTINGS and
the RING-NO ANSWER CALLS SETTINGS are available only when this
parameter is set to Yes.
ACD evenly distributes incoming calls, stacks the calls in a waiting queue if no one
is available, and sends overflow calls to an alternate destination.This set of
extended Overflow parameters provides enhanced ACD routing capabilities, such
as conditional routing to multiple destinations and an option to either queue a call
to the ACD group or immediately divert the call to a predefined destination.
INACTIVE  An Inactive Group is comprised of an empty group with no agents defined or

GROUP a group with the last defined agents logged out.
SETTINGS
The following 4 parameters provide an alternative destination for calls camped on
an inactive ACD group.
Q NEW CALLS Yes/No

Set this parameter to No to immediately reroute new calls to the Inactive Group to
an alternate destination (see DESTINATION below).
Setting this parameter to Yes allows incoming ACD calls to camp onto the Inactive
ACD group. The call remains in the queue until answered or until the queuing time
expires. When the timer for camping onto the group (TIME_TO_
OVERFLOW (page 10-12)) expires, the calls are rerouted to the
OVERFLOW (page 10-6) destination.
DESTINATION Overflow (OVERFLOW on page 10-6 Destination);

NUM (Any valid system station, boss group, hunt group, public library,
Routing Access, Dial Service, trunk or trunk group dial number)
Defines the destination (station number) for new calls to the Inactive ACD group.
10-6
QUEUED CALLS STAY Yes/No

IN QUEUE
Set this parameter to No to immediately reroute the calls in queue of the Inactive
ACD group to an alternate DESTINATION defined below.
Setting this parameter to Yes allows the calls already camped on an ACD group to
continue camping on this ACD group that became Inactive while the call was
waiting.

Defines the destination (station number) for ACD calls camped on the ACD group
that became Inactive while the calls were already waiting in the queue.
UNAVAILABLE Unavailable Group - all the active agents in the group became unavailable by
GROUP activating one or more of the following features at their stations: Don’t Disturb,
SETTINGS Call Forward ALL, Release All.
Q NEW CALLS Yes/No

Set this parameter to No to immediately reroute new calls to the Unavailable ACD
group to an alternate DESTINATION defined below.
Setting this parameter to Yes allows new incoming ACD calls to camp onto the
Unavailable ACD group. The call remains in the queue until answered or until the
queuing time expires. When the timer for camping onto the group (TIME_TO_
OVERFLOW (page 10-12)) expires, the calls are rerouted to the
OVERFLOW (page 10-6) destination.


Defines the destination (station number) for new ACD calls camped on an
Unavailable ACD group.
QUEUED CALLS STAY Yes/No

IN QUEUE
Set this parameter to No to immediately reroute the calls in queue of the
Unavailable ACD group to an alternate DESTINATION defined below.
Setting this parameter to Yes allows the calls already camped on an ACD group to
continue camping on this ACD group that became unavailable while the call was
waiting.
10-7

Defines the destination (station number) for ACD calls camped on the ACD group
that became Unavailable while the calls were already waiting in the queue.
RING-NO Ring No Answer (RNA) calls are defined as ACD calls ringing at the location of
ANSWER an active and available agent but not answered within a predefined time.
CALLS
SETTINGS
Q NEW CALLS Yes/No

Set this parameter to No to immediately reroute calls to a Ring-No Answer ACD
group to an alternate DESTINATION defined below and avoid applying the Auto
Release feature (see AUTO_RELEASED_ALL [19] on page 9-36) at this agent’s
station.
Setting this parameter to Yes, allows incoming ACD calls to camp on to an RNA
ACD group (a group with at least one active and available agent that did not answer
the call within a predefined time period).
The following warning is displayed when this parameter is set to Yes.
! NOTE: All agents are set to Auto-Release when RNA Q CALLS is set to
Y. This will override any Auto-Release setting for the agent's station.
Caution should be used so as to prevent agent confusion when they do
not answer ACD calls ringing their set.
The call remains in the queue to the ACD group until answered or until the queuing
time is over (and the call is rerouted to the overflow destination).
If an ACD group is defined as ONE STEP GROUP, then any RNA calls immediately
overflow to the RNA destination for queued calls, even if this parameter is defined
as Yes. The RNA destination in this case is the most recent destination that was
recorded in the PI database before this parameter was defined as Yes.

Defines the destination (station number) for new RNA calls to the ACD group.
10-8
ONE STEP GROUP Yes/No

Determines whether calls directed to the group ring at only one station in the Hunt
Group before going to the group overflow destination (above). If N is entered, a
call directed to one member steps to the next available member, after the TIME_TO_
NEXT_MEM (page 10-12) timer expires.
USER_CANNED_ Range: 0..15, R (Remove for None)

MESSAGE# Default: None
Defines the number of the Canned Message (0 to 15) that is displayed to users
calling this not yet answered group. The text for Canned messages 0 to 15 is
defined in NAME - (page 16-3) in Room Status/User Canned Messages (Root,0,3,0).
MUSIC_SOURCE 0..3
IPx 500 and CDRS 200E: 0 (Music 1), 1 (Music 2)
Determines the music-on-hold source from multiple music sources. This music is
heard by callers that queue on the group for the duration of the TIME_TO_2ND_ANN
timer, between the 1st & 2nd announcements. The range is limited by # OF MUSIC
SOURCES (1-4) (page 4-45).
RETAIN_HUNT_ Yes/No
MUSIC_SOURCE
Defines whether the Music Source that is sounded when a call entering the Hunt
group is answered, accompanies the call throughout the system (i.e. until
disconnect or transfer to another Hunt Group or Wait Que where this feature is also
set to Y).
When this parameter is set to Yes, the call retains the same Music Source (for the
duration of the call within the system) even when the call is transferred to another
agent or placed on Hold.

MUSIC_WITH_ Yes/No
ANSWER
When this parameter is set to Y (Yes), one of the following will occur:
• If there is no announcer in the system, when a new call is sent to a Hunt group
and all of the group members are busy, music will be heard.
• If there is an announcer in the system and it is not busy, it is immediately
reached, and this parameter is irrelevant.
• If the announcer is busy and the caller is camped-on to it, music is heard.
If this parameter is set to N (No), and there is no announcer in the system, the caller
will hear a ringback tone.
 When the caller is connected to music, an answer signal is sent to the

central office and the caller is charged for the call.
10-9
WRAP-UP TIME 0..76..6500 seconds

Defines the time period, immediately following the completion of an ACD/UCD
call, during which an ACD/UCD member will not receive the next hunt call.
Wrap-Up time is defined in seconds. Wrap-Up time may be used by ACD/UCD
members in order to complete previous call handling or for any other purpose that
requires restricting incoming calls. In addition, this parameter allows ACD agents
to utilize the Wrap-Up code without interfering with incoming calls.
This feature can only be activated from the agent’s station (see relevant User’s
Guide). By activating this feature the agent can utilize idle (time-out) periods
between consecutive group calls. The Wrap-Up time is defined on a
group-by-group basis.
#_OF_Q_CALLS_ 0..254 or None

FOR_DELAY(Number
of Calls Wait)
 This parameter should be less than or equal to #_OF_Q_CALLS_FOR_BUSY
(ACD only/ Not LS trunks) below.
(ACD only)
This feature is used for programming the maximum number of waiting calls
allowed before additional incoming calls are delayed. When the number of
incoming calls is greater than the defined amount for this parameter, then call delay
is activated and all further incoming calls ring for a programmable time period.
(The ring delay period is defined in the following CALL_DELAY_TIME (ACD only)
Timer). When activated, incoming delayed calls continue ringing for the duration
of the defined time period. Only after this period expires or when the number of
waiting calls is less than this number, will the system put the call in a waiting state
and route it to the group for processing.
By not immediately answering calls during peak periods (by using this feature), the
Coral can give the impression that the call was not answered, thereby shortening
the wait period before the call is actually transferred to a destination. Charges are
therefore not accrued until a recorded announcement is heard.
The benefits to users of this feature include:

• Reduced telephone cost to customers.
• Significant savings for toll-free subscribers and long distance calls.
• Call queuing time is reduced.
Defining 0 for this parameter causes an immediate ringback tone to be sent to the
caller when all agents are busy.
CALL_DELAY_TIME 5..30..500 seconds

(ACD only)
Determines the time period that an incoming ACD call can be delayed when the
number of waiting calls is more than the defined value of #_OF_Q_CALLS_FOR_
DELAY(Number of Calls Wait) (ACD only), above.
10-10
#_OF_Q_CALLS_ 0..254, None

FOR_BUSY
(ACD only/
 Define this parameter as greater or equal to #_OF_Q_CALLS_FOR_
DELAY(Number of Calls Wait) (ACD only), above.
Not LS trunks)
Defines the maximum number of waiting (listening to the mandatory
announcement, other announcements, delayed calls) ACD calls. Once the limit
defined here is reached, the next caller receives a busy tone.
Enter None to define no limit for waiting calls.
This feature is Attendant Modifiable (feature code #1746) only when ACD_CALLS_
FOR_BUSY [43] (page 7-43) is defined as Y.
The following calls will enter the ACD group queue regardless of the maximum
defined here:
• Call Forward No Answer calls
• Overflows from other groups
• Calls Diverted to an ACD group (for diverted calls to receive a busy tone
instead of waiting to be answered, set the next parameter to No)
• Calls Forwarded to an ACD group.
CHECK_#_OF_Q_ Yes/No
CALLS_FOR_BUSY_
ON_DIVERT

From versions 15.85.11 and higher, this parameter name replaces
DIVERT_IGNORES_#_OF_Q_CALLS_FOR_BUSY.
No other changes have been made.
 This parameter is displayed only when #_OF_Q_CALLS_FOR_BUSY (ACD

only/ Not LS trunks), above, is defined (i.e. not None).
This parameter is relevant only for diverted calls to an ACD group when #_OF_Q_
CALLS_FOR_BUSY (ACD only/ Not LS trunks), above, parameter is defined and

exhausted or has been fully utilized (i.e., the limit for waiting calls to this ACD
group was met).
Set this parameter to:
• No - so that additional calls diverted to this ACD group hear a busy tone (useful
for applications diverting calls to the ACD group).
• Yes - so that additional calls diverted to this ACD group can camp onto the
ACD group and wait to be answered.
10-11
TIME_TO_OVERFLOW 1..120..6553 seconds
 Notes:
• During this time period, a caller may hear a First and/or Second
Announcer, when defined as a MUSIC_SOURCE.
• Define this time period as greater than TIME_TO_NEXT_
MEM (page 10-12).
Determines the time period that a call remains in queue before going to the
overflow or the Incomplete Call Destination (if no overflow is identified).
TIME_TO_2ND_ANN 1..20..6553 seconds
 This parameter does not appear if IVR_ACD (ACD only), above, is set to
Yes.
Determines the time period between the end of the first announcement and the
beginning of the second announcement. This timer also determines the periodic
cycle within the second announcer phase.
During this time, one of the following facilities can be defined through MUSIC_
SOURCE (page 10-9): music, reorder tone, busy tone or no sound at all, which is
heard by the caller. The second announcement and defined interval sounds are
repeated periodically until the hunt recall timer has expired.
TIME_TO_NEXT_MEM 1..20..6553 seconds

Determines the time period that a call rings at a member station in a hunt group
before hunting to the next group member.
 To have the system automatically release an agent who’s station has not been
answering, set AUTO_RELEASED_ALL [19] (page 9-9) (SLT Definition branch)
or AUTO_RELEASED_ALL [19] (page 9-36) (Keyset Definition branch) to Yes.
10-12
IVR CR (Enter for None);

Num (any legal station/trunk or Public Library number);
Defines the IVR destination. Legal destinations include:
• E&M trunk defined as Hot Immediate, with Immediate or Wink (according to
the external IVR) protocol and ANSWER_MANDATORY set to No (see E&M
Trunk Definition beginning on page 8-87).
• Trunk Groups that include E&M Hot Immediate trunks as defined above.
• Any ACD group (also ACDs defined as Voicemail) not defined as an IVR
connection: the ACD group is automatically be defined as Terminal.
• Any SLT port (also SLTs defined as Voicemail) not defined as ANNOUNCER
[23] (page 9-10).
• Magneto station
• Any Keyset port (except for Wireless stations): also keysets defined as
Voicemail, PCC or 4IAA.
• A Public Library Destination with one of the above destination options as its
contents.
TIME_TO_IVR 1..20..6553
When a caller is routed to an ACD Hunt group defined with an IVR connection, the
caller is immediately routed to the IVR. After this initial connection, the caller
continues camping on the ACD group.
This parameter defines the time interval for continually re-offering a connection to
the IVR while the caller is camped-on to an ACD group waiting to be answered
(see IVR_ACD (ACD only), above). If the caller chooses to re-connect to the IVR,
s/he remains queued on the ACD group.
 To disconnect from the IVR, set this parameter with a value equal to or

larger than TIME_TO_OVERFLOW.
CALL_WAITING_ Yes/No
TONE Y: CC1
Defines whether a caller will be prompted with a call-wait tone if all active group
members are busy. The definition is valid for the specific group only and not
system wide.
10-13
RECORDED The Coral system includes three different types of message transmission:
MESSAGES: • Mandatory Announcer
• First Announcer
• Second Announcer
The announcer is a device with a prerecorded message. This device can be
connected either to a SLT port, SeaMail SIP port, DVMS port, iVMFipx keyset
port, IPC/uCMC or IPC/SFC keyset port.
• In order to install an ANNOUNCER device in an SLT port, the SLT definition
must be defined as ANNOUNCER [23]=YES, (see page 9-10).
• In order to use a DVMS port, DVMS MSG must be programmed (see page 23-2).
iVMFipx as Announcer:
When using iVMFipx keyset ports as announcers (Coral IPx 500 and CDRS 200E
systems), update the following parameters in the Keyset Definition branch:
• VOICE_MAIL (DTMF receive) [28] (page 9-40) = Yes (automatically updated)
• ANNOUNCER [34] (page 9-42) = Yes
• PCC [46] (page 9-47) = No (automatically updated)
Hunt Group branch (HUNT):
• GROUP TYPE (page 10-3) = ACD
• VM_GROUP (ACD only) (page 10-4) = Yes
IPC/SFC as Announcer:
When using IPC/SFC keyset ports (Simplicity) as announcers, the following
parameters must be updated per keyset port:
Keyset Definition branch (KEY):
• VOICE_MAIL (DTMF receive) [28] (page 9-40) = Yes (automatically updated)
• ANNOUNCER [34] (page 9-42) = Yes
• PCC [46] (page 9-47) = CSTS (automatically updated)
Hunt Group branch (HUNT):
• GROUP TYPE (page 10-3) = ACD
• VM_GROUP (ACD only) (page 10-4) = Yes
MANDATORY Keyset port # (SeaMail, iVMFipx, IPC/uCMC or IPC/SFC port) defined as

ANNOUNCER,
SLT port # defined as ANNOUNCER,
DVMS port # defined with special message,
Identifies the announcer that is heard before calls are directed to either an
ACD/UCD group or to the first announcer. After the mandatory message is
completed, the caller is directed to either an idle agent or to the first announcement
if all agents are busy. Such mandatory messages can provide general information
to the caller or advertisements, as required.
10-14
ENTER 1ST Keyset port # (SeaMail, iVMFipx, IPC/uCMC or IPC/SFC port) defined as
ANNOUNCER ANNOUNCER,
Yes.
Identifies the announcer dial number to incoming calls whenever all of the
ACD/UCD members are busy. When first announcer is heard, the system
automatically camps the call onto the group and then one of the following facilities,
as defined through MUSIC_SOURCE (page 10-9): music, busy tone or no sound at
all, is heard.
When the first announcer is defined as NONE the incoming caller will hear the
TONE TYPE (page 4-45) that is defined for the Music Source: Music, Busy or
Ringback tone or Silence.
 1ST ANNOUNCER appears in Display Mode only if an entry has been made
(i.e. a port number was defined for this parameter).
10-15
ENTER 2ND Keyset port # (SeaMail, iVMFipx, IPC/uCMC or IPC/SFC port) defined as
ANNOUNCER ANNOUNCER,
Yes.
Identifies the announcer dial number for calls waiting to be answered by a group
member, for more than the defined time period. The second announcer is heard if
the call is camped on the group for at least the time period defined for the start of
second announcer (see TIME_TO_2ND_ANN on page 10-12).
 2nd ANNOUNCER appears in:

• Update Mode only if 1ST ANNOUNCER has been previously defined.
• Display Mode only if an entry has been made.
The following error messages may appear while recorded announcements are
defined:
Error Message Explanation Corrective Action
NOT ANNOUNCER An attempt was made to Enter a SLT, Keyset or

(SLT/KEYSET/DVMS) enter a non SLT, Keyset DVMS port number. If you
PORT or DVMS port number. do not know the number,
ask the telephone system
manager.
NOT DEFINED An SLT or Keyset Define the required port as

ANNOUNCER number was entered, an ANNOUNCER in the
but was not defined as appropriate branch (KEY):
an ANNOUNCER port. • SLT Definition:
ANNOUNCER
[23] (page 9-10)
• Keyset Definition:
ANNOUNCER
[34] (page 9-42).
DVMS NOT DEF IN A DVMS port number Define the required DVMS
(PDB) was entered, but the port for a specific message
PORT was not defined using DVMS MSG
for a special MSG. [0] (page 23-2).
10-16
MEM # Any number (see Notes below), Station, None;

(A/R/CR) up to 255 members per group.
A: Add new number at current location;
R: Remove number
CR: Skip number.
Identifies the Hunt group members by either member dial number or library dial
number. Enter the dial number of each member of the Hunt Group.
 Notes:
• Any valid number can be used for member number, such as: system
station, central Bell/UNA or Modem dial numbers (a public library
number and/or a Boss group number can only be members of UCD
groups).
• Remove (R) is denied when a member is active (not idle). If an attempt
is made to remove an active station the error message
PORT-IS-ACTIVE is displayed.
• An SLT station defined as ANNOUNCER cannot be a member of a hunt
group.
• If an attempt is made to define a non valid (illegal) system number the
error message: ILL PORT TYPE appears.
• A station can only be defined once for a particular group. If an attempt
is made to define a station number that is already a member of the
current hunt group the error message: ALREADY DEFINED appears.
• IPC/SFC: If the live record feature is to be used, the last port on this
card should not be defined as a Hunt Group member.
• Never define ACD members with Multi-appearnce option.
For an SLT see MULTI_APPEARANCE [24] (page 9-11)=No.
For a keyset see MULTI_APPEARANCE [22] (page 9-37)=No.
Application Note:
Using the Public Library as a UCD Group member allows the option of providing

agents with the ability to operate at home or from distant localities. This option is
particularly appropriate when call volume reaches the capacity of in-house staff.
When this happens, calls can be automatically re-routed to agents homes or other
distant sites.
10-17
Boss Group ç BOSS [0,5,2]
Boss groups are a versatile and unique feature of the Coral Communication system.
Boss groups may be used to direct a call to several stations simultaneously. Calls
directed to a Boss group ring at all members assigned to ring within the group, then
may be directed to members which are assigned to ring after a delay (ring delay
after time-out).
Additionally, Boss Groups offer key system emulation features. Member stations
of a Boss group may share a Boss line key which functions very much like a
common line among keysets. Trunks reserved to a Boss group act on member
stations in a manner similar to the common lines of a key telephone system; this
includes group-wide HOLD, incoming call, and busy indications; and automatic
conference (break-in); as well as exclusive use by member stations.
The XDA application allows for a common line appearance of external
destinations at the Boss Group members’ stations when the external destination is
defined as a reserved Public Library number see RSRVD_TO_BOSS_
GROUP (page 11-3) in the Private Library branch (LIB, 0).
A station may be a member of several Boss groups.
 Notes:
• Busy indication lamps are not available on SLT, Magneto,
CoralAir/FlexAir wireless telephones and most SIP telephones.
• SIP entities defined with an Early Media Negotiation cannot be defined
as members in a Boss Group (the phones will not ring), see Media
Negotiation [6] (page 29-46).
Boss Group Class of Service
The Boss Group COS is defined by the first Boss Group member’s COS. This is
relevant for Call Forwarding Boss Groups.
Boss Group BOSS [0,5,2]
10-18
FROM/TO BOSS# Any valid system boss group dial number; All
Enter the required range of boss group dial numbers. FROM the lowest dial
number, TO the highest dial number.
NAME:
Defines the short name (up to 5 alphanumeric characters) of the Boss group, which
display and the Boss group dial number is displayed. See General Rules for Entering
Names (page 2-10).
FULL (16) Maximum of 16 printable ASCII characters, R (Remove for BLANK)

Defines the full name (up to 16 alphanumeric characters) of the Boss group, which
display and the Boss group dial number is displayed.
This name is used for the Boss Group entries of the system’s Shared Directory. Full
Names defined as Blank are not copied to the Shared Directory.
See General Rules for Entering Names (page 2-10).
10-19
# LINES 1..6 (when number of groups is between 1 to 512)

1..3 (when number of total groups is between 513 and 1024)
 After defining a member in any group, the # of lines will automatically be

changed to 3 if the number of lines was not previously defined.
Determines the number of incoming calls to the group that may be in-progress
simultaneously. When this number of calls is in-progress, the group is busy towards
additional calls directed to the group.
RING_DELAY 1..200..600 (1 unit = 0.1 second)

Boss Group Ringback defines the time period that all Boss Group stations that are
assigned to ring, will ring. This parameter also defines the time period after which
all Boss Group stations defined with delayed ring will ring.

MESSAGE# Default: None
calling this not yet answered group. The text for Canned messages 0 to 15 is
defined in NAME - (page 16-3) in Room Status/User Canned Messages (Root,0,3,0).
MEMBER_FWD_ Yes/No
BUSY_OVERRIDE?
Determines whether an activated Forward Busy feature of one of the members in
the group can be ignored for calls directed to the boss group, thus giving priority to
the group calls over private calls.
Busy members receive notification of the incoming call on the second line of their
display.
 The Call Forward Busy feature for private calls is not affected.
CALL_WAITING_ Yes/No
TONE CC1: Y
Defines whether a caller hears (and sends) a call waiting tone to a boss group. The
definition is valid only when there is an available boss group line. If all lines in the
boss group are busy, then the caller will hear a busy tone and not the call waiting
tone.
The definition is valid for the specific boss group only and not system wide.
This call waiting tone duration is defined as a second ringback tone (see Second
Ringback (2nd R.back) in Table 6-12).
10-20
MEM # Any valid system station number or R (Remove);

R: Remove number;
CR: Skip number.
 SIP entities defined with an Early Media Negotiation cannot be defined as

members in a Boss Group (the phones will not ring), see Media Negotiation
[6] (page 29-46).
Identifies the Boss group members by member station dial numbers. Enter the
station’s dial number followed by ring control either Y (ring assigned) or N (no ring
assigned) or D (delayed ring assigned), for example 201Y, 202N. If Y or N or D is
not entered following the dial number, ring assigned (Y) becomes the default.
APP RING CONTROL Y (Immediate Ring), N (No Ring Assigned), D (Delayed Ring)
(Y/N/D)
N (No ring assigned) cannot be defined for SLT and WST stations.
Defines station ringing for group members. Do not enter spaces or tabs between the
station dial number and the ring control definition.
Notes:
1) If APP RING CONTROL is set to Y or D, and the last ringing station is
defined as multi-appearance, then the ring time is determined by the
MULT_APR_RING timer (Station Timers); otherwise, RING DELAY
determines the ring duration.
2) An active member's station cannot be removed. If an attempt is made to
remove an active station the message: PORT-IS-ACTIVE is
displayed. A member can only be removed when the station is idle.
3) Any station defined as ANNOUNCER cannot be a member of a boss
group.

4) If an attempt is made to define a non valid (illegal) system number the
error message: ILL PORT TYPE appears.
5) A station can only be defined once for a particular group. If an attempt
is made to define a station number that is already a member of the
current boss group the error message: ALREADY DEFINED appears.
6) SLT, Magneto, T200S series, P-Series, 3rd-party SIP phones, and
FlexAir/ CoralAIR wireless Stations that are members of a Boss Group
do not have flashing Line Keys to alert them of a Boss Group call in
progress. Therefore, their Ring Control State should be defined as Yes
or Delay.
7) T300 series Stations may be members of a Boss Group. Refer to the
Application Note AN1202-001, which describes the basic programming
required for Boss Line key #126. Requires Coral Version 16.02.03 or
10-21
higher.
10-22
Pickup Group ç PICK [0,5,3]
A Pickup group enables a member of a Pickup to answer a call arriving at another

member station defined in the group. Entering station dial numbers into Pickup
groups allows members of a group to answer a call ringing on another member's
station by dialing a feature dial number. The feature dial number remains the same
regardless of the Pickup group. A call can only be picked up by another member of
the Pickup group which contains the ringing station. A station may be a member of
only one Pickup group.
FROM/TO PICKUP# 0 to maximum defined in Sizes, see PICKUP (page 4-14); All
Enter the required range of Pickup group index numbers.
MEM # Any valid system station dial number;

R: Remove number;
CR: Skip number.
Identifies the Pickup group members by member station dial number. Enter the dial
number of each member of the Pickup group.
 Notes:
• Only a station can be a member of a pickup group. If an attempt is
made to define a non valid station number the error message appears:
NOT A ST #.
A station can be a member of only a single group. If an attempt is made to define a
station number that is already a member of a group this error message appears:
ALREADY DEFINED IN GRP #?
Pickup Group PICK [0,5,3]

10-23
Zoned Voice Page Group ç VPZ [0,5,4]
Zoned Voice Page Group allows programmers to define Keyset Zoned Voice Page
groups. Entering Keyset station dial numbers into a Zoned Voice Page group allows
a caller to establish a one-way call to the speaker of all idle members of the group.
Each Zoned Voice Page group is assigned a unique dial number. Any keyset or
FlexSet station may be a member of several Zoned Voice Page groups.
 SLT, Magneto, FlexAir/CoralAIR wireless handsets, P-Seies (such as:

P-335, P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam
softphone, and third-party SIP terminals may not be members of a Zoned
Voice Page group.
They may, however, initiate a Zoned Voice Page.
 For Coral IPx Office systems: when the Zoned Voice Page Group includes
IP keysets (FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL), the
group must be defined as Group Calls on page 10-26, otherwise it will not
function.
FROM/TO ZONE# Any valid system zone group dial number; All
Enter the required range of Zone group dial numbers.
TNNT_GRP 0..63
Defines the tenant group number (see Tenant Class of Service on page 7-44)
required for accessing or paging a defined group of Keysets.
MEM # Any valid system Keyset (FlexSets, CPAs, FlexSet-IP 280S, T200M series,
(A/R/CR) GKT, DKT, EKT included) station dial number;
Zoned Voice Page Group VPZ [0,5,4]
up to 255 members per group.

NOTE: All keysets must be equipped with a loud speaker.
 Coral FlexiCom 200 and CDRS 200: All keysets are members of the first
Zone Group.
R: Remove number;
CR: Skip number.
Identifies the Zoned Voice Page group members by member station dial number.
Only Keysets may be a member of a Zoned Voice Page group. Enter the dial
number of the group member’s station.
 Remove (R) is denied when a member is active (listening to a page call or

during paging). If an attempt is made to remove an active station the error
message PORT-IS-ACTIVE is displayed. A member can only be removed
when the station is idle.
10-24
Bell/UNA Group ç BELL [0,5,5]
The Bell/UNA group is used to establish Universal Night Answer (UNA) Bell
groups. Bell groups allow members to answer calls directed to the Bell port. A
UNA/Bell Relay dial number and a station dial number may be a member of only
one Bell group.
An incoming call may be automatically directed to a central bell. When the bell
rings anyone within that group may dial the feature code to pickup the call.
FROM/TO BELL/UNA# All or 0 to maximum defined in Sizes, see BELL/UNA (page 4-14)
Enter the required range of Bell group index numbers.
BELL Any valid system ASU, RMI, 8DRCF, 8DRCM-2, 8DRCM or

U-RMI/U-MR/RMI/MR Office Bell/UNA dial number
First Bell group (index 0): 7050,
All other groups: None
Identifies the Bell/UNA Relay port dial number assigned to the group. Only calls
directed to this Bell/UNA relay port may be answered by member stations.
Similarly, only member stations of this group may answer calls directed to this
Bell/UNA relay port. Enter the dial number of the ASU, RMI, 8DRCF, 8DRCM-2,
8DRCM or U-RMI/U-MR/RMI/MR Office card Bell/UNA Relay port.
MEM# Any valid system station dial number;

(A/R/CR) up to 254 members per group (see note below).
First Bell group (index 0): All defined station dial #'s;
All other groups: Empty
R: Remove number;
Bell/UNA Group BELL [0,5,5]

CR: Skip number.
Identifies the Bell group members by member station dial number. Enter the dial
number of each member of the Bell group.
 Maximum number of members allowed per group is 254 (and not 255
because the BELL number is also a member).
10-25
Group Calls ç CALL [0,5,7]
A Group Call can be defined as a preset conference call where all the participants
have been pre-defined as members in this branch. Thus, the conference initiator
rings all the members by dialing the Group Call number.
 Alternatively, the Group Call can be defined as a temporary Group Call

(define ADD_ON as Y) where no members are defined on a permanent
basis, but where the participants are added (joined) via the initiator’s
telephone as the call is being established.
 In Coral IPx Office systems, the Group Call can also be used to create a
Zone Page by Group Call when the group includes IP keysets
(FlexSet-IP 280S, T200M series).
Set the following parameters as defined below:
BREAK_IN/OUT_TONE on page 10-31
JOIN MEMBERS IN MUTE on page 10-32
AUTO_ANSWER (KEYSET) on page 10-33
AUTO_ANSWER (OPERATOR) on page 10-33
AUTO_DISCONNECT BY on page 10-33
LOCK ACTIVE GROUP CALL on page 10-34
NEXT GROUP on page 10-36
MEM # (A/R/CR) on page 10-37.
Group Call A Group Call is initiated when an authorized user, usually the Group Operator,
Definitions dials the assigned Group Call dial number, thus causing all the registered members
(defined in MEM # (A/R/CR)) to ring.
To initiate a temporary Group Call conference, the Group Call initiator must
1. Dial the temporary Group Call feature number (default #1449)
2. Dial the Group Call dial number.
3. Dial the required members, one after the other.
Group Calls CALL [0,5,7]
4. Dial the activation code.

Group Call members can be internal stations or external numbers dialed through
public library numbers. Typical usages of this feature include preprogramming a
conference for regular conference users, staff conferences, or creating a message
group for general information or emergency warnings.
When a Group Call is placed, all stations defined for that group ring. As a member
joins the conference (i.e. answers the incoming group call), all actively
participating members can be alerted by a warning tone (when BREAK_IN/OUT_
TONE is set to Yes). Stations that go unanswered can be defined to continue (or
discontinue) ringing (see STOP_RING_AFTER_1ST_ANSWER) without disturbing
the conference, until the defined time-out period is completed. At this point, the
conference is locked to members that have not yet joined (when JOIN_AFTER_
STOP_RING is defined as No).
10-26
Group Call participants may also be admitted in mute mode (if JOIN MEMBERS IN
MUTE is defined). Participants must request permission to speak from the GROUP
OPERATOR defined for that Group Call.
The Group Call can be locked against new participants (non registered members)
by defining LOCK ACTIVE GROUP CALL to Yes in this branch.
Group Call - Different COS definitions allow the authorized user to:
COS Definitions • Establish a temporary Group Call containing no predefined members. The
members are added by the call initiator while initiating the call (default feature
code: #1449)
• Release a group call participant (default feature code: #1446)
• Terminate the group call (default feature code: #1447)
Group Call Size Group Calls are based on the availability of conference circuits. Therefore, the
maximum number of Group Calls and the Group Call size is limited by the number
of conference cards and how the card is defined in the database.
Conference Card Type max. number of members
CNF card (defined as CONF in Each card allows two group calls.
Card List menu) Each group with a maximum of 15
participants (14 members plus the group call
initiator) per call.
8DRCF, 8DRCM-2, or 8DRCM Each card allows a maximum number of 6

card participants (5 members plus the conference
initiator)
IPx Office U-RMI/U-MR Each card allows a maximum number of 14
(URC2) participants (13 members plus the conference
initiator)

IPx 500 (MSBipx Each system allows a maximum number of 14
Issue-0200X1000 or higher, participants (13 members plus the conference
RMI-F/URC2) initiator)
CDRS 200E (RMI-F/URC2) Each system allows a maximum number of 14
participants (13 members plus the conference
initiator)
A large Group Call A large Group Call with a maximum of 100
participants can be established when single
group calls are chained via public library
numbers.
10-27
Creating a Large Group Call

Single Group Calls can be linked to create a large Group Call of up to 100
members. Any combination of external numbers and stations can participate. The
number of single Group Calls that can be combined into one Group Call depends
on the available number of conference cards. Each single Group Call consists of a
Conference Port and up to 5, 13, or 14 members (see Group Call Size above).
To create a large Group Call, one Group Call is connected to the next Group Call
in back-to-back mode via E&M, TBR or PRI trunks. To achieve this, a Public
Library number is defined as one of the members. This Public Library includes a
trunk or trunk group number that dials the next group call in the chain.
Another Public Library number can be defined as a member of the second Group
Call which contains a link to the third Group Call in the chain, etc.
The Public Library used for establishing the connection should use an outgoing
trunk defined with JOIN GROUP CALL IN MUTE (page 8-32) in TGDEF as No (see
trunks A and C in the Example below).
The incoming trunks used for establishing the back-to-back connection between
the single Group Calls should never be defined as Outgoing Only (see trunks B and
D in the Example below).
Lastly, ensure that each Group Call defines the NEXT GROUP parameter so that the
system knows where to route new non registered participants when the first group
is full. This also ensures that the system knows which Group Calls to disconnect
when the conference is terminated.
10-28
Example
To create a large Group Call with 18 registered members, one operator, and an
option to add 4 non-registered members, define the following parameters:
Group Call 5600 Group Call 5601 Group Call 5602

CONF card 8DRCM-2, 8DRCM-2,
Members Trunk B 8DRCM, or Trunk D 8DRCM, or
8DRCF 8DRCF
Members Members
1: User-1 1: User-10 1: User-14
Trunk A Trunk C
2: User-2 2: User-11 2: User-15
3: Pub Lib 1 3: Pub Lib 2 3: User-16
4: User-3 4: User-12 4: User-17
5: User-4 5: User-13 5: User-18
6: User-5
7: User-6
8: User-7
9: User-8
10: User-9
11: NULL
12: NULL
13: NULL
14: NULL
Add On = No Add On = No Add On = No
Next Group: 5601 Next Group: 5602 Next Group: None
Group Operator: Group Operator: Group Operator:
User 1 User 1 User 1
Trunks A&B are connected back-to-back.

Trunks C&D are connected back-to-back.
Trunks A and C (i.e. the defined OUT TK?s for Public Library) are used for
Outgoing and must define JOIN GROUP CALL IN MUTE (page 8-32) (TGDEF) as No.

Trunks B and D are Incoming and are used for the initiation of the next group call.
Define all the Group Calls as not temporary, i.e. ADD_ON (page 10-32) as No.
Define the same Group Operator for all the Group Calls. If the Group Call initiator
is not the Group Operator, define one of the other members as the Group Operator.
Define the Public Libraries with the following definitions:
Public Library 1:
• OUT Tk?: Trunk A
• Dial NUM: Group Call 5601 dial number
Public Library 2:
• OUT Tk?: Trunk C
• Dial NUM: Group Call 5602 dial number
10-29
FROM/TO Any valid system Group Call dial number

GRP_CALL# (Defined in Chapter 5 - General Numbering Plan, Group Call [35]);
All
Enter the range of required Group Call dial numbers FROM the lowest TO the
highest Group Call dial number. The maximum number of groups is defined in
SIZES, see GRP_CALL (page 4-14).
NAME:
Defines the short name (up to 5 alphanumeric characters) of the Group Call. This
name appears on the member’s keyset display when:
• calling the Group
• being called by the Group
• being transferred to a Group Call.
When BLANK is entered, a group name does not appear on the keyset display and
the Group Call dial number is displayed.

Defines the full name (up to 16 alphanumeric characters) of the Group Call. This
name appears on the member’s keyset display when:
• calling the Group
• being called by the Group
• being transferred to a Group Call.
When BLANK is entered, a group name does not appear on the keyset display and
the Group Call dial number is displayed.
10-30
CONF # All or any valid system conference dial# as defined in CONF [30] on page 5-43
Allows defining whether the Group Call is activated over a specific conference port
or over any idle (free) system conference port (All). A specific conference port
number is selected by entering the conference port dial number associated with a
particular port. Each CNF card has two conference ports. The 8DRCF, 8DRCM-2,
and 8DRCM card have one conference port. Each URC2 unit has up six conference
ports.
When All is selected, any of the idle conference ports can be used when Group Call
is activated. In this case the system selects any free conference port, as required.
 When CONF # is defined as ALL and the number of group calls is greater
than the number of available conference ports, then, in order to use the
group call, at least one conference port should be reserved and not
assigned to any group.
TNNT_GRP 0..63
Allows defining the tenant group number required for accessing the Group Call.
STOP_RING_AFTER_ Yes/No
1ST_ANSWER
When a Group Call is activated, all stations (members) defined for that particular
group ring. Members join the conference call by answering the phone or pressing
the lit GRP CALL # programmed key. Stations that go unanswered continue
ringing, without disturbing the conference, until the defined time-out period GRP_
CALL_RING [21] (page 6-5) expires.
To cancel the ringing at the other members’ phones after the call was answered by
any one group member (before the ringing time-out), enter Y for this parameter.
BREAK_IN/OUT_ Yes/No

TONE
Defines whether or not a warning tone, (see BRK_In/Out on page 6-97) is sounded
when a member joins or leaves a group call. All participating group members hear
the tone. When Y is selected a tone will be heard; When N is selected no tone will
be heard.
 It is recommended that this parameter be set to N when the group is to be

used for Zone Page.
10-31
JOIN_AFTER_STOP_ Yes/No
RING
Enter Y to enable a Group Call member (i.e. registered member station defined in
the PI Group Call Member database) to join an ongoing conference call although
the phone has stopped ringing, because the call was answered and/or the ringing
time-out period expired.
ADD_ON Yes/No
Enter Y to define this Group Call as temporary.
 Do not define members for this Group Call dial number when this
parameter is set to Yes.
A temporary Group Call should contain no predefined members. The Group Call
initiator adds members from his/her station. After the Group Call is terminated, all
the members are dropped and the same Group Call can be used again with other
members.
The temporary Group Call initiator requires COS authorization, see ADD_ON_
CONFERENCE [55] (page 7-18), default feature code #1449.
JOIN MEMBERS IN Yes/No

MUTE
When set to Yes, this parameter causes Group Call members to join the call in mute
mode. The members can hear the ongoing conference but are not able to speak to
the conversing parties.
The joining group members request permission to speak from the GROUP
OPERATOR (defined below), by using a programmed button with the
REQUESTING HELP feature code, followed by the Group Operator’s station
number (or by the XFER button). SLT stations must hookflash the Group Operator
to request to speak.
Set this parameter to No in order to enable the joining Group Call members to
speak during the Group Call.
 This parameter must be set to Y when the group is to be used for Zone
Page.
10-32
AUTO_ANSWER Yes/No
(KEYSET)
When set to Yes, Group Call keyset members, including the group call operator
(FlexSet, FlexSet-IP, T207M, T208M, T207M/NP, T208M/BL, CPA, GKT, DKT,
EKT) that do not answer until the AUTO_ANS_V_PAGE [1] timer expires,
automatically join the conference.
(The timer is defined in Keyset Timers on page 9-27).
 This parameter does not apply to SLT, Magneto, FlexAir/CoralAIR

wireless handsets, P-Seies (such as: P-335, P-450), T207S, T208S,
T207S/NP, T208S/BL, T322, T328, SeaBeam, and all third-party
SIP terminals.
 This parameter must be set to Y when the group is to be used for Zone
Page.
AUTO_ANSWER Yes/No
(OPERATOR)
When set to Yes, a Group Call operator that does not answer before the AUTO_ANS_
V_PAGE [1] timer expires, automatically joins the conference (regardless of the
AUTO_ANSWER (KEYSETS) definition.
(The timer is defined in Keyset Timers on page 9-27).
AUTO_DISCONNECT Operator/Initiator/None
BY
Defines which party Operator or Initiator can force release all participants upon
hanging-up. When set to Operator or Initiator, all conference participants
(whether members of the main group or chained groups) will be released from the
conference when the Group Call Operator or Initiator (as defined) disconnects.
 This parameter must be set to Initiator when the group is to be used for
Zone Page.

DISCONNECT_ Yes/No
FLEXSETS_
The group call can be configured to disconnect all keysets within the group call
IMMEDIATELY
immediately, without producing a tone. This parameter defines whether or not a
tone is heard on all keysets after the group call is finished. When N (No) is selected
the tone to idle is heard. When Y (Yes) is selected, all keysets in the group
disconnect immediately without producing a tone.
10-33
LOCK ACTIVE Yes/No

GROUP CALL
Defines whether an ongoing Group Call is locked against new participants who are
not defined as members of that Group Call.
When set to Yes, this parameter prevents non-registered Group Call members from
joining an ongoing Group Call.
When set to No, any station can join the group call - by dialing the Group Call
number or by being transferred to the conference by a Group Call member.
This parameter has no relevance for Group Call registered members, who are
blocked from joining an ongoing group call only when JOIN_AFTER_STOP_RING,
above, is set to No.
 It is recommended that this parameter be set to N when the group is to be

used for Zone Page.
DISPATCH_GROUP_ No, P(pre-defined), T(temporary)

CALL
Defines the type of group call that can be made by the user: predefined, temporary,
or none.
• Predefined group calls can activate several predefined libraries with one
programmable button. Each library contains the number of a party to be
included and the specific trunk to be used. By pressing the button, the user
automatically initializes a group call with all of the predefined members of the
group. All phones within the group begin ringing. The programmable button
LED of the group member’s phone flashes until the group call is answered by
the group member. When the group member answers, the programmable
button LED remains continuously on. A group member is released from the
group call by the operator by pressing the group member’s programmable
button.
• Temporary group calls activate one library at the touch of a programmable
button. The library contains the number of a party to be included and the
specific trunk to be used. New group members are added and removed from
the group by pressing the programmable button of each member. The
programmable button LED flashes until the group call is answered by the
group member and remains continuously on until the group member is
removed from the group by the operator or removes himself from the group by
hanging up. Any party can add himself to the group by pressing the
programmable button of the group call operator.
10-34
DISPATCH_SUB_ No/Yes
GROUP
When defined as y (yes), the group operator has eight group calls and
programmable buttons for each group. Each one of the group calls is comprised of
two chained group calls and defined with three members (defined in the end of the
chain). The user can press each of the programmable buttons and talk with the
group. While in the group call, when the user presses the programmable buttons,
the phones defined in that group will start ringing and be added to the existing
group when answered.
GROUP OPERATOR Any valid system Keyset (with display) Station number;
None: (--) (R-Remove for None: --)
 Keysets only (FlexSet, FlexSet-IP, T207M, T208M, T207M/NP, T208M/BL,

GKT, DKT, or EKT)
Defines this Keyset Station as the Group Operator for this Group Call.
Only the Group Operator is authorized to grant participants permission to speak,
(relevant when JOIN MEMBERS IN MUTE, above, is set to Yes).
It is preferable to define the same group operator for all group calls within a large
(chained) group call.
When Group Calls are not initiated by the Group Operator one member of the
Group Call should be defined as the Group Operator by using the define Group Call
Operator feature (default feature code: #17716 - COS definition, See GROUP_
CALL_OPERATOR [54] (page 7-17)).
Chained Groups
Changing this parameter (via the keyset station - default feature code: #17716 or
here), automatically updates the group operator for this group and all groups
further on in the chain.
For Example:

Groups were chained in the following order:
First: 5600 ==> 5601==> 5604 ==> 5603 ==> 5605-Last.

The Group Operator was changed for group 5601.
• Groups 5604, 5603 and 5605 are defined with the new group operator
• Group 5600 retains the previous group operator.
10-35
NEXT GROUP Any valid system Group Call Dial number, R (Remove for --)
Enter R for the last group call in the chain or when the group is not chained.
 This parameter is relevant for adding new participants to an ongoing

Group Call or for terminating the large Group Call (default feature code
#1447).
Defines the sequence of the large (chained) Group Call (or Zone Page for IPx
Office systems).
This parameter also defines how the new participant is routed. A new participant
joining the conference is routed to the first group that has a free member. If the first
group is full, the new participant is routed to the group call defined as NEXT GROUP.
10-36
MEM # Any valid system SLT, Keyset, FlexSet, FlexSet-IP, P-Series, T200M series,
(A/R/CR) T200S series, third-party SIP Terminal, FlexAir/CoralAIR wireless handset,
Magneto, Public Library number, or, Private Library number of Group Call
Initiator1
 When the group is to be used for Zone Page in IPx Office systems:
Any valid system Keyset member as permitted for Zoned Voice Page Group
members (see Zoned Voice Page Group on page 10-24).
R: Remove number;
CR: Skip number.
Enter the member dial number. The Group Call members can be identified either
by station number or by Public Speed Call number.
 Restrict the maximum number of members according to the conference

card defined in CONF # parameter (see page 10-31), as follows::Notes:
Conference Card Type max. number

of members
CNF card (defined as CONF in Card List menu) 14
8DRCF, 8DRCM-2, or 8DRCM card 5
IPx Office U-RMI/U-MR (URC2) 13
IPx 500 (MSBipx Issue-0200X1000 or higher, RMI-F/URC2) 13
CDRS 200E (RMI-F/URC2) 13
• SLT defined as ANNOUNCER [23] cannot be included in Group Calls.

• An active Group Call cannot be updated.
• When Public Library is defined as a group member, do not use Loop
Start Trunks Without Disconnect Supervision, (see page 11-8).

• When a Private Library is programmed as a member in the Group Call,
then the Group Call can only be initiated by a Station user. It cannot be
defined as a Call Forward destination for any other station.
Alternatively, no incoming call can dial this private library.
1. Private Lib cannot contain a Public Lib#.

When a Private Library number is entered as a member of the Group Call, the private library of
the current Group Call Initiator is dialed. This is useful for Emergency (911) dialing, for IP sta-
tions that may be located in a different state or locality than their primary Coral.
For Example:
Define a Group Call destination, such as 911, with the following members:
Mem#1: a Private Library Number that includes a Trunk Group to an emergency destination
within the station’s geographic location (e.g. private lib 7001 = 81 + 911).
Mem#2: another local Emergency destination: either a Coral Station or another Private Library
(e.g. Coral station 5400:House Guard).
10-37
ELA Group ç ELA

The Extension Line Appearance (ELA) feature enables sharing station extension
appearances between stations by creating a group of ELA Coral station users
(members).
Every ELA group can be defined as one of three working modes, as follows:
 Regular - An incoming call to the ELA group (i.e., to the ELA main station
dial number) rings and/or lights a programmed line key at the members’
stations so that any ELA group member can answer the call by lifting the
handset or pressing the flashing programmed line key. The call appears as a lit
line at the other members’ stations. The other keyset members may break-in to
the call or pickup a held ELA call by using their programmed line keys.
 Personal - In this mode only one member can be active (logged-in).

An incoming call to the Personal ELA group rings and/or lights a programmed
line key only at the active member’s station so that all other ELA group
members can not answer the call. The other keyset members may not break-in
to the call or pickup a held ELA call.
While on a call, the active member is identified to the second party as the ELA
group main station.
 Department - In this mode the number of active members is unlimited.

An incoming call to the Departmental ELA group rings and/or lights a
programmed line key at all the active members’ stations. The call appears as a
lit line only at the active members’ stations. The other non-active keyset
members may not break-in to the call or pickup a held ELA call.
A maximum of 32 different line keys may be defined for each ELA group station
member.
An ELA group includes one or more Coral station members defined for a single
ELA main station. The ELA group number is the ELA main station dial number.
Therefore, there are no ELA group NPL type numbers reserved in the system.
ELA Group ELA
This branch allow you to create or remove an ELA group as well as to configure
the group parameters.
To create an ELA group:
A station number becomes an ELA group number only when members are defined
for the station. Therefore, an ELA group is created only after defining at least one
member station number in MEM # (A/R/CR) (page 10-40) for the requested From/To
ELA# (page 10-39).
To remove an ELA group:
Removing all members from an ELA group (ELA#) deletes the ELA group. The
station reverts to a regular station with no support for ELA lines.
10-38
 Notes:
• Members cannot be removed when any of the ELA group members are
active.
• In addition to defining the ELA group members in this branch, make
sure that you define the main ELA station, as well as all ELA members,
each as Multi-Appearance in their station definition branch.
From/To ELA# Range: All Station numbers

Default:in Display Mode:Only ELA Main stations
in Update Mode:FROM First TO Last Available station number
 Notes for ELA Main Station:

• for Initial definitions: Although the system defaults with the first station
number defined in the Coral, if no members are defined for the station,
no ELA group is formed.
• ELA Main Station must be defined as Multi-Appearance to enable the
line calls. See:
SLT Definition, MULTI_APPEARANCE [24] on page 9-11.
Keyset Definition, MULTI_APPEARANCE [22] on page 9-37.
Enter a range of ELA group numbers from the lowest to the highest group number.
NAME: Short Display Only

Displays the Port List Short name for this ELA group (i.e. the name for the ELA
Main station).
NAME: Full Display Only

Displays the Port List Full name for this ELA group (i.e. the name for the ELA
Main station).
This name is displayed on keysets calling the group, as well as on all keyset
ELA Group ELA

members receiving ELA calls. If no name is defined, then the ELA group dial
number is displayed on the keyset.
#LINES 1..2..32
Defines the maximum number of ELA Line keys that can be programmed for this
ELA group.
This parameter, therefore, determines the number of incoming calls to the group
that can be in-progress simultaneously. When this number of calls is in-progress,
the group is busy towards additional calls directed to the group.
10-39
RING DELAY 0..200..1000 (1 unit = 0.1 second)

Defines the time period that all ELA Group members that are assigned to ring, will
ring.
This parameter also defines the time period after which all ELA Group members
defined with delayed ring (D) will begin to ring.
MODE Regular/Personal/Department
Determines whether the ELA group is either a Regular or a Personal or a
Department type.
MEM # (A/R/CR) Any valid system station number or R (Remove);

up to 255 members per group.
A: Add new number at current location
R: Remove number (the group must be in Idle when removing a station member)
CR: Skip number
Use this parameter to add or remove members. Enter the Member’s station number
followed by the APP Ring Control state for the member.
ELA Station Ring Control - APP Ring Control (Y/N/D) defines the user’s ELA
lines ringing state, as follows:
• Yes - ELA calls ring immediately
• No - ELA calls don’t ring at the station
 APP Ring Control (Y/N/D) is automatically defined as No for keyset

• Delay - ELA calls ring after a system-wide pre-defined timeout period
members (not SLT, T200S series, SeaBeam, third-party SIP terminals or

FlexAir/CoralAIR wireless handset) who do not have any ELA Line Keys
already defined at their stations.
 For Regular and Department ELA Groups the APP Ring Control (Y/N/D)
is set during system configuration, as follows:
ELA Group ELA
• Y for the active member

• N for non-active members
 For Personal ELA Group this item is automatically set by the system, as
• D for active member and delayed ring
follows:
• Y for the active member
• N for non-active members
The member can program one or more ELA Line keys at his/her station.
When programming a line key from the station set, the member must also define a
ring control type.
10-40
Although a member can be defined with a ring state of Y via this parameter, it can
initialize with a ring state of N depending on how the last line key was programmed
at the station. In this manner, all the line keys at one station will have the same ring
control type.
Therefore, the member’s ring type for the station may be updated via this parameter
or directly from the member’s station set.
APP Ring Control States (for Regular and Department ELA Groups):
Y. Rings immediately when the group is called.
D. Rings only after the Ring Delay period expires.
N. Does not ring when the group is called.
 Notes for ELA Members:

• ELA Main Stationn, as well as all the member stations, must be defined
as Multi-Appearance to enable the line calls.
For SLT see MULTI_APPEARANCE [24] on page 9-11.
For keyset see MULTI_APPEARANCE [22] on page 9-37.
• ELA Main Station cannot be defined as a member of its own ELA
group.
• A member may belong to one or more ELA groups simultaneously.
• If APP RING CONTROL is set to Y or D, and the last ringing station is
defined as Multi-Appearance, the ring time is determined by the
MULT_APR_RING timer (Station Timers); otherwise, RING DELAY
determines the ring duration.
• A member can only be removed when the ELA group is idle, otherwise
the following message appears:
“ELA GROUP IS ACTIVE, TRY AGAIN”.
• Any station defined as ANNOUNCER (in KEY or SLT) cannot be a
member of an ELA group.
• SLT, Magneto, T200S series, P-Series, 3rd-party SIP phones, and
FlexAir/CoralAIR wireless Stations that are members of an ELA Group
do not have flashing Line Keys to alert them of an ELA Group call in
ELA Group ELA

progress. Therefore, their Ring Control State should be defined as Yes
or Delay.
• T300 series Stations may be members of an ELA Group. Refer to the
Application Note AN1202-001, which describes the basic programming
required for ELA Line key #17718. Requires Coral Version 16.02.03 or
higher.
10-41
ELA Group ELA
10-42
11 Libraries
The Libraries Branch contains the Public, Private and Serial Libraries. This chapter
gives the necessary instructions for programming all libraries.
The Library type and its related page number is listed below:
Public Library .............................................................................................11-2

Private Library............................................................................................ 11-9
Serial Library............................................................................................ 11-12
Large Public Library - Overview ............................................................. 11-18
Large Public Library Numbering Plan ............................................. 11-20
Large Public Library Contents.......................................................... 11-22
Directory ................................................................................................... 11-25
Directory - Systems (Shared) Directory Entries .............................. 11-26
Directory - Personal Directory ......................................................... 11-29
11-1
Libraries PI Reference Manual
Public Library ç LIB,0 [0,6,0]
The Public Library is used to establish an abbreviated common access to frequently

dialed numbers. The Public Library is also known as the system-wide speed call.
The DIAL_NUM and SPECIFIC_TK options can be changed at the Attendant
console, when the console has the appropriate COS definition.
FROM/TO PUB_LIB# Any valid system access code number;

All codes
Enter the required range of Public Library (Speed Call) access code numbers.
FROM the lowest number TO the highest number.
NAME: SHORT(5) Maximum of 5 printable ASCII characters, R (Remove for BLANK)

Defines the short name (up to 5 alphanumeric characters) of the Public Library
entry. The name appears on keysets equipped with a display when the entry is
accessed. When BLANK is defined, an entry name does not appear on the keyset
display and the library entry dial number is displayed.
This library name is also displayed on the destination screen.
 Tip: Use a library name to send text messages to other station users or
legal destination. See Application Note below.
NAME: FULL (16) Maximum of 16 printable ASCII characters, R (Remove for BLANK)
Defines the full name (up to 16 alphanumeric characters) of the Public Library
entry. The name appears on keysets equipped with a display when the entry is
Public Library LIB,0 [0,6,0]
accessed. When BLANK is defined, an entry name does not appear on the keyset
display and the library entry dial number is displayed.
This library name is also displayed on the destination screen as well as in the
Shared Directory. Full Names defined as Blank are not copied to the Shared
Directory.
 Tip: Use a library name to send text messages to other station users or
legal destination. See Application Note.
11-2
PI Reference Manual Libraries
TOLL_OVERRIDE Yes/No
Determines if access to the library entry overrides Toll Barrier restrictions applying
to the calling station Class of Service. Setting this parameter to No invokes Toll
Barrier restrictions.
NAME_RETENTION_ Yes/No
OVERRIDE
Set this parameter to Yes in order to override SYSTEM_WIDE_NAME_RETENTION
[23] and ACD/LIB_NAME_RETENTION [24] (page 6-26) (defined in SFE,2). This
enables the user to change the Called Party Name on the station display of
forwarded stations. The user changes the Called Party Name by first defining and
then dialing a new Public Library # destination from his/her keyset.
PROTECTED? Yes/No
Set this feature to Yes in order to deny the user the ability to change the content of
the Public Library from his/her station.
TNNT_GRP 0..63
Defines the tenant group number required for accessing this Public Library entry.
This option can be used to block certain users from dialing this external number.

MESSAGE#
calling this not yet answered Public Library number. The text for Canned messages
0 to 15 is defined in NAME - (page 16-3) in Room Status/User Canned Messages
(Root,0,3,0).
RSRVD_TO_BOSS_ Any valid Boss Group number, or N for None

GROUP

General Info
A Public Library can be reserved to a particular Boss Group to enable an External
Destination Appearance (XDA).
XDA enables an external destination to appear and act as a line key at the Boss
Group member’s station sets, by using a reserved Public Library for the external
destination. XDA is similar to the RSRVD_TO [13] on page 8-14 for a trunk port in
the General Trunk Definitions branch (TRK, 0) except that XDA is implemented for
external stations as opposed to Trunks.
Parameter Definitions
Define the Boss Group number for which this Public Library must be reserved, in
this parameter.
When this parameter is defined with a Boss Group number, only the Boss Group
members may access this Public Library. All other station users trying to dial into
the Public Library receive the ATT_RSRVD message on their keyset displays.
11-3
 Notes:
• Define a FULL Name for Public Libraries reserved to a Boss Group
(i.e. when this parameter is defined).
• Define the External Destination number in this Public Library DIAL
NUM field.
• If the External Destination does not possess ANI representation, then an
additional Public Library must be defined with the external destination
number defined in its DIAL NUM field and the Boss Group # defined
in its OUT TK field but without a FULL Name definition and without a
RSRVD_TO_BOSS_GROUP definition.
Refer to the New Developments Summary, Coral MSW Version 15 for a detailed
explanation on programming XDA.
PRIORITY_ Yes/No
PREEMPTION_CALL?
When set to Yes, this parameter prioritizes calls made via this Public Library.
Public Libraries used for emergency calls can be enabled to allow the emergency
call to immediately connect to the emergency station by disconnecting (or breaking
into, see PREEMPTION TYPE [9] on page 6-21) a previously established
non-emergency call by defining the appropriate public libraries with this parameter
set to Yes.
NOTE! Previously established emergency calls are not disconnected. The new
emergency call camps on the busy trunk and waits until the trunk is freed.
 When the emergency destination is located in the same Coral system

(non-network), then its Public Library definitions must define DIAL_NUM
as None and OUT_TRK must include the emergency destination dial
number.
For Coral Networks:
The definitions for the different Public Libraries leading to the emergency
destination in a Coral Network or in the Public Network are described below. An
example is provided for clarification.
11-4
Figure 11-1. Coral

Network Coral Network
Configuration
Example Node C: Public
Gateway Network
Node A Node D
Node B
For Coral Networks: The emergency destination may be located in any one of the
network nodes or in the Public Network. If the emergency destination is located in
the Public Network, then the Emergency Destination Public Library must be
located in the gateway node leading to the Public Network.
For this example, we assume the emergency destination is in Node C or the Public
Network.
Table 11-1:
Public Library Definitions per Node for Call Path: D to B to A to Emergency Destination
Public Emergency Destination Private Network Nodes:

Library Location
Contents
Node C Public Network A B D
Emergency 6000 6000 defined 6001 6002 6003

Pub Lib # in Node C (i.e.,
gateway to
Public Network)

DIAL_NUM None External Dial 6000: 6001: 6002:
Number of Emergency Emergency Emergency
Emergency Pub Lib # of Pub Lib # of Pub Lib # of
Destination Next Node Next Node Next Node
OUT_TRK 5000: 4580: 80: 80: 80:

Internal Dial Routing Access Routing Routing Routing
Number of to Public Network Access to Access to Access to
Emergency Node with Node A Node B
Destination Emergency
Destination
PRIORITY_ Yes Yes Yes Yes Yes

PREEMPTION_
CALL
11-5
APPEND_TO_DIAL_ (0 (None), 1 (ANI*DNIS*), 2 (DNIS*ANI*)

NUMBER_AS_SUFFIX
This parameter allows you to send ANI and DNIS numbers to an SLT or keyset that
is defined as a Voicemail interface. If the call is routed via a trunk that supports
ANI, Coral will send both the ANI and the DNIS over the DTMF. If the call is
being routed over a trunk that does not support ANI, Coral will send the number
defined as ANI along with the DNIS over the DTMF. The caller’s number is the
same as the trunk number. If the caller has no number, only the DNIS will be sent.
This feature is applicable for ordinary calls, transferred calls, calls with a held
party, all types of forwarded calls, and diverted calls.
In order for this feature to work:
• The VOICE_MAIL [36] parameter under SLT [or IST or ROOT,0,2,1,1] must be
defined as Y (Yes) for SLT phones.
• The VOICE_MAIL (DTMF receive) [28] parameter under KEY [or EKT or 0,2,1,2,0]
 ANI and DNIS numbers are sent with DIAL NUM.

must be defined as Y (Yes) for keyset phones.
11-6
DIAL NUM 1 to Maximum digits (including the codes listed below) defined in SFE (see
MAX_DGTS_ON_TK [5] (page 6-8)). It is possible to send ANI and DNIS
numbers. See APPEND_TO_DIAL_NUMBER_AS_SUFFIX.
Enter the required external dial digits.
 DO NOT enter the Trunk Group, Routing Access or Dial Service number
(for example 81, 82, etc.); enter all other numbers. The Trunk Group,
Routing Access or Dial Service number is entered in the OUT TK?
parameter defined below.
When defining a public library to dial an ISDN application, enter the 7

digit DID dial number of the ISDN application in this field.
When using the Public Library, various dialing instruction codes can also be
utilized. The following table lists these codes.
Code Instruction
Dx Used to delay dialing by x seconds (x = 1 to 9)
E0 Stop dial (Keyset display shows: “.”)
E1 Outpulsing wait period during which user is able to dial any

number of digits
E2 Send following digits as Pulse
E3 Send following digits as DTMF
E4 Inhibits display (Keyset display shows: “_” for each digit
E5 Enables display
E6 Wait for second Dial Tone
E71 Caller ID Restriction Implementation.

Restrict the presentation of the caller phone number from

appearing on the display of the called external party (as well as
 Enter the feature code E71 and then the dial number.
internal party, depending on system-wide settings).
E72 Enables displaying Caller ID number
E8 Display “-” on Keyset display
E9 Calibrated opening (flash) on trunk (Keyset display shows “hf”)
11-7
OUT TK? (N/TK_NO/GRP/LIB) Any valid trunk, trunk group, dial service, Routing
Access, Wait-Que, Network number, or another Public Library dial number,
or None (N) or for special purposes: Station/Boss Group/Hunt Group;
Note: Another Large Public Library is not allowed
Enter the dial number of the outside line access code, Public Library or station if a
specific facility (group) is selected, otherwise enter N. If N is entered a station
attempting to dial this library number must also add the outside line access code.
 When defining a public library to dial an ISDN application, define this

parameter with the trunk group number which contains the BRI trunk.
Stations equipped with a display receive the display message:
ENTER TK/GROUP#.
A Public Library dial number may be entered to gain dial access to a common
carrier, or route over a private network, before the contents of the current library is
dialed.
 When Public Library is used as a member of a Group Call, do not use

Loop Start Trunks Without Disconnect Supervision.
Application Note
To use a Public Library Number as a Text Message:
1. Define SYSTEM_WIDE_NAME_RETENTION [23] (page 6-26) to Yes.
2. Create a Public Library with the following entries:
• Enter the desired message in the NAME field. The field may contain a
message like “WIFE_ON_LINE_2”.
• Set NAME_RETENTION_OVERRIDE to Yes.
• Enter any code for DIAL NUM.
• Set OUT_TK to No.
3. To send the message: dial the library number or press a pre-programmed
key with the library number.

4. When the message ENTER DEST NUM appears on your keyset display,
enter the destination dial number. Possible destination numbers include:
keyset stations, boss groups and hunt groups.
11-8
Private Library ç LIB,1 [0,6,1]
The Private Library is used to establish an abbreviated personal (station-specific)

access to frequently dialed numbers. The Private Library also is known as
“personal speed call”. Library dial numbers and trunk numbers can be changed by
the user, when the station has the appropriate COS definition.
FROM/TO STATION Any valid system station dial number;

All dial numbers
Enter the required range of station numbers FROM the lowest station number, TO
the highest station number.
FROM/TO PRIV_LIB# Any valid system access code number;

All code numbers
Enter the required range of Speed Call Private Library access code numbers FROM
the lowest Private Library number TO the highest Private Library number.
Private Library LIB,1 [0,6,1]
11-9
ENTER DIAL NUM 1 to Maximum digits (including the codes listed below) defined in SFE (see
MAX_DGTS_ON_TK [5] (page 6-8))
 DO NOT enter the Trunk Group, Routing Access or Dial Number (for
example 81, 82, etc.); enter all other numbers. The Trunk Group, Routing
Access or Dial Number is entered in SPECIFIC TK? (defined below).
When using the Private Library various dialing instruction codes can also be
utilized. The following table lists these codes:
Code Instruction
E1 Outpulsing wait period during which user is able to dial any number of digits
E5 Enables display

Restrict the presentation of the caller phone number from appearing on the
display of the called external party (as well as internal party, depending on
system-wide settings).
SPECIFIC TK? (N/TK_NO/GRP/LIB) Any valid trunk, trunk group, dial service, Routing
Access, another Public or Private Library dial number, or None (N), Station
numbers or Network numbers for special purposes
 Another Large Public Library is not allowed in the range.

Enter the dial number of the outside line access code (or Routing Access or Dial
Service or Trunk number) Public or Private Library, or station if a specific facility
(group) is selected, otherwise enter N. If N is entered, a station attempting to dial
11-10
this library number must also add the outside line access code. Stations equipped
with a display receive the display message:
ENTER TK/GROUP#.
carrier, or route over a private network, before the current library number is dialed.
11-11
Serial Library ç LIB,2 [0,6,2]
The Serial Library is used when the addition of a prefix digit or number is required
in the Public Library Numbering Plan. Serial libraries are useful when, for
example, several Coral systems are linked into a private network or in order to
reserve dial numbers for use as extensions or other features in the system
Numbering Plan.
The Serial Library number which the user dials from the telephone is composed of
a prefix and a suffix. The prefix is essentially a serial library access code. It must
be defined in the NPL and may be from 1 to 8 digits long. The suffix is the specific
library number entry and is 4 digits long (0000 - 4095). Thus, the serial library
access number may be up to 12 digits long.
Use of the prefix enables use of the suffix number by itself to be used as an
extension (or other Coral number or feature).
For example, dialing 6-1234 reaches library 1234, while dialing 1234 reaches
telephone extension 1234. The number 6 must be defined as the library prefix as
shown in the example below.
Note that the prefix is used to inform the system that the number following it (the
suffix) is a library number and not another Coral feature. The use of a different
prefix is immaterial as far as the system is concerned; 6-WXYZ and 7-WXYZ (for
example) reach the same library number, i.e., WXYZ, if both 6 and 7 are defined
as Serial Library numbers.
The Serial and Public Libraries use the same Coral memory resources. The only
difference between the two is only the way in which the particular library numbers
are accessed. The total number of Public and Serial libraries together is 4096.
 Notes:
• The Public Library size must be increased to the total required amount
Serial Library LIB,2 [0,6,2]
of both public and serial libraries.

• The extra prefix must be defined in the system Numbering Plan under
FEATURE, Index number 161. The prefix number may be composed of
1 to 8 digits.
Once the prefix number has been defined, the Serial Library operates similarly to
the Public Library, except for the additional access number.
For Example: The following example shows how to define a 5 digit library number,
64000, where the total amount of public and serial library numbers is 4096:
1. Go to SIZizes Def. (see Chapter 4), and define the Public library size
definition to 4096. The following screen message will appear:
Max Libraries (8192)
PRIVATE (4096) 2000
PUBLIC (4096) 4096
LARGE PUB (64000) 0
11-12
LARGE NPL (1000) 0

LARGE PUB DIGITS (32) 0
GROUPS:
BELL/UNA (6) 2
2. Go to the Numbering Plan and enter right click to choose the REMOVE
option or (NPL, 0, 3)
3. Remove all existing dial numbers beginning with 6 (6xxx)
4. Go to the Numbering Plan and enter right click to choose the ADD option
or (NPL, 0, 2).
5. Add the new dial number 6
6. After entering 6, the following screen appears
FROM NEW DIAL# - 6

TO NEW DIAL# -
NUMS ALREADY DEF? (Y/N) N
0- TRUNK
1- SLT
2- KEYSET
3- KEYSET_V_PAGE
4- TRUNK_GRP
5- HUNT_GRP
6- BOSS_GRP
7- PUBLIC_LIB
9- FEATURE
10- EDIT
11- BELL
12- PAGE
13- MODEM

14- DID_NUMS
16- DATA_PORT
19- PRIVATE_LIB
20- KEYSET_Z_PAGE
21- RELAY
22- DATA_USER
23- DATA_GRP
30- CONF
31- DVMS_MSG
32- DVMS_PORTS
33- PAGE_Q
35- GROUP_CALL
36- DIAL_SERV
37- ROUTING_ACC
11-13
38- WAIT_QUE
39- NETWORK
40- WIRELESS
41- IP_Keyset
42- IP_SLT
43- IP_LGS
44- IP_KEY_VPG
Choose Type
* : 9,
ENTER INDEX# - 161
7. Select 9- FEATURE and define INDEX # as 161.
8. The Serial Library #4000 is then defined in Libraries at (LIB, 2).

LIB: 4000
NAME:
SHORT(5) SMITH
FULL (16) SMITH J.
TOLL_OVERRIDE- N
TNNT_GRP - 0
DIAL_NUM = 5461234
OUT TK = 9
The entries listed above are defined on the following pages.
The Serial Library is used to establish a big public (system-wide) library of
frequently dialed numbers.
FROM/TO (LIB#) SER# Range: 0..4095

Default: 0..999
Enter the required range of Serial Library Index numbers FROM the lowest index,
TO the highest Index.
NAME:
Defines the short name (up to 5 alphanumeric characters) of the Serial Library
entry which appears on keysets equipped with a display when the entry is accessed.
When BLANK is defined, an entry name does not appear on the keyset display and
the serial library entry dial number is displayed. See General Rules for Entering
Names on page 2-10.
11-14

Defines the full name (up to 16 alphanumeric characters) of the Serial Library entry
which appears on keysets equipped with a display when the entry is accessed.
When BLANK is defined, an entry name does not appear on the keyset display and
the serial library entry dial number is displayed. See General Rules for Entering
Names on page 2-10.
TNNT_GRP 0..63
Determines the access capabilities of various tenant groups into the Serial Library.
Tenant groups with access levels that include Tenant Group access will be able to
use the library entry.
11-15
DIAL NUM 1 to Maximum digits (including the codes listed below) defined in SFE
System Features, see MAX_DGTS_ON_TK [5] (page 6-8)
 DO NOT enter the trunk group dial number, Routing Access or Dial
Service (for example 81, 82, etc.); enter all other numbers. The trunk
group dial number, Routing Access or Dial Service is entered in SPECIFIC_
TK? (defined below).
When using the Serial Library, various dialing instruction codes can also be
utilized. The following table lists these codes.:
Code Instruction

number of digits
E5 Enables display

11-16
SPECIFIC TK? N/TK_NO/GRP/LIB (Any valid trunk, trunk group, dial service, Routing
Access, Wait-Due, another Public Library dial number, or None (N),
Station/Boss Group/Hunt Group or Network number for special purposes
 Another Large Public Library is not allowed.

specific facility (group) is selected, otherwise enter N. If N is entered, a station
attempting to dial this Serial library number must also add the outside line access
code. Stations equipped with a display receive the display message
ENTER TK/GROUP#.
carrier or route over a private network before the contents of the current library is
dialed.
11-17
Large Public Library - Overview ç LIB,3

General The Coral supports two types of public libraries:
• Pub Library - up to 4,096 entries (also accessed by Serial library feature code).
• Large Pub Library - up to 65,000 entries.
There is no interaction between the two library types. Each type is a different entity
and uses different Coral memory resources. Details for the Large Pub Library are
found on the following pages.
Large Public Library Numbering Plan ............................................. 11-20
Large Public Library Contents.......................................................... 11-22
The Large Pub Library is used when more than 4,096 numbers are required for the
Public Library, or when a prefix number (1 to 8 digits) is required in the Public
Library numbering plan. The Large Pub Library is also useful when, for example,
several Coral systems are linked into a private network or when one wants to
reserve dial numbers for other features in the system Numbering Plan.
The Large Pub Library number which the user dials from the telephone is
composed of a prefix number followed by a suffix number. The prefix number is
essentially an access number to the Large Pub Library. It serves to notify the Coral
system that the suffix number following refers to a specific library number and not
to other Coral features such as an internal telephone extension, etc. The suffix dial
number may be up to 8 digits long. Thus, the Large Pub Library dial number may
be up to 16 digits long.
Each entry in the Large Pub Lib has a unique suffix index number, from 0 up to
64,999 (limited by Sizes). Every suffix index is assigned by a dial number(s), up to
8 digits length (defined by “Large Pub NPL”, Route: LIB,3,0).
The prefix dial number must be added to the General system NPL. This is a general
Large Public Library - Overview LIB,3
Feature Code for the Large Pub Library Prefix. The number(s) assigned by index #
“199”. (Will be called Prefix for explanation).
Thus, in order to use the Large Public Library, the user has to dial the Prefix (1 to
8 digits), followed by the required Suffix Large Pub Lib Dial# (1 to 8 digits).
However, the user must have a correct Access Tenant Group in its COS.
For example, use the general Feature code “index #199” to tell the system that the
number 6161 is a Large Pub Library prefix. From this point on, dialing 6161
accesses the Large Pub Library database. The user continues and dials up to 8 more
digits (the suffix).
For example: dialing 6161-10001234 accesses Large Pub Library number
10001234. The Large Pub Library number 10001234 is itself assigned to a selected
number (out of the 65,000 available) in the Large Pub Library numbering plan.
The Large Pub Lib can be programmed into a keyset key for fast key dialing.
11-18
Limitations The Large Pub Lib cannot be defined as a system feature destination (such as Call
Forward, DIL, etc.....)
The Large Pub Libraries can be programmed or updated via CoralVIEW Designer
(CVD) only.
Procedure For Defining Large Public Library
1. Make sure that PUBLIC, LARGE_PUB, LARGE_NPL, LARGE_PUB_DIGITS are
defined according to your system size requirements (see Sizes Def.-Chapter
4). The Large Pub Library uses significant amount of Coral resources. It is,
therefore, recommended to define the LARGE_PUB size to be close to your
actual requirements plus a reasonable amount of “spare”. It should not
otherwise be set to the maximum allowed.
2. Make sure that the dial # to be used as the Large Public Library Prefix, is
assigned to the general Feature code index# 199 in NPL,0 (see page 5-38).
The extra prefix must be defined in the system Numbering Plan as a
FEATURE, Index number 199. The prefix number may be composed of 1
to 8 digits.
Use the following steps (in a system after first initialization):
a) Go to the General NPL (Route: NPL,0).
b) Remove all existing dial# starting with the required PREFIX number.
c) Add the new PREFIX dial#, by entering the following data listed in ( ):
FROM NEW DIAL# (Enter the required PREFIX number)
TO NEW DIAL# (Enter [CR])
NUMBERS ALREADY DEF? (Enter N)
Choose type *: (Enter 9)
ENTER INDEX#- (Enter 199)
3. Wait for the prompt message NUMBERS ADDED
Large Public Library - Overview LIB,3

Repeat the above procedure when more PREFIX numbers are required.
(In this case enter Y for NUMBERS ALREADY DEF?)
4. Once these procedures are completed, Large Public Library can be setup for
the operating system. Follow the procedures listed in the following pages.
First assign a Suffix dial# to all required entries (Route: LIB,3,0), then enter
the required information to each suffix (Route: LIB,3,1).
11-19
Large Public Library Numbering Plan ç LIB,3,0 [0,6,3,0]
The Large Lib Numbering Plan is used to determine and establish the system-wide
pattern scheme for the second part (Suffix) of the Large library dial#.
Dialing digits via the keypad or programmed buttons on the keypad is the user's
method of instructing the Coral system to access a library and dial out. The dial#
includes two parts, the PREFIX and a secondary numbering plan (the SUFFIX) for
each entry.
The Prefix defines access to all Large Library entries in the system. A Suffix is
assigned to each entry. These numbers must be ADDED to the system after first
initialization. The system programmer has a reference tool to refer a Suffix dial
number to a specific entry. That reference tool is an internal index number in the
system which refers to dial numbers.
The Large Public Library Numbering Plan is used to assign system suffix dial
numbers to the index numbers in the flexible numbering scheme.
INDEX #: An index number is a software identification number which identifies a speed dial
library number. Each entry is identified by a specific index number regardless of
the suffix dial number assigned to it by the Numbering Plan. The first entry is
identified by index 0.
In general, the number of large public libraries established in the System Sizes
determines the quantity of index numbers allocated. The first 1,000 large public
speed dial library numbers for instance, require index numbers 0 through 999
(inclusive), the second 1,000 would require index numbers 1000 through 1999
Large Public Library Numbering Plan LIB,3,0 [0,6,3,0]
(inclusive).
DIAL #: The suffix dial number is used (after dialing the Prefix) to access the related large
public library entry. The suffix dial number range is determined by the
programmer. FROM and TO DIAL # numbers must have the same number of digits
(for example, 000-999, 0000-9999, ..., 00000000-99999999)
1 to 8 digits for the suffix may be used, however, using less than 4 digits
severely restricts the flexibility of the Numbering Plan.
Option Description
0 - UPDATE Allows updating of the existing suffix numbering plan
1 - DISPLAY Displays the entire suffix numbering plan
2 - ADD Adds a suffix number to the numbering plan
3 - REMOVE Removes selected suffix numbers from the numbering plan
7 - ERASE Erases all suffix numbers in the numbering plan
11-20
Table 11-2: Numbering Plan Options - Full Explanation
Function Prompts & Captions Description
0 - UPDATE FROM OLD DIAL#: Enter the first existing suffix dial number of the range that requires
updating.
TO OLD DIAL#: Enter the last existing suffix dial number that requires updating. If
only a single number is required, enter the same number as FROM
OLD DIAL#.
FROM NEW DIAL#: Enter the first new suffix dial number in the range that was defined
under the old dial number. (Once the first number is entered, the rest
of the defined range is automatically calculated.)
1 - DISPLAY FROM DIAL#: Displays the first suffix dial number defined in the display range.
TO DIAL#: Displays the last suffix dial number defined in the display range.
INDEX#: Displays the index number of first library entry in the range.
2 - ADD FROM NEW DIAL#: Enter the first new suffix dial number of the range that is to be
added.
TO NEW DIAL#: Enter the last new suffix dial number to be added. If only a single
number is required, enter the same number as FROM NEW DIAL#.
FROM INDEX#: Enter the index of the first new suffix dial number
3 - REMOVE FROM OLD DIAL#: Enter the first existing suffix dial number of the range that requires
removal.
TO OLD DIAL#: Enter the last existing suffix dial number that requires removal. If
only a single number is required, enter [CR]. After the number is
typed and [CR] pressed, if the number was successfully removed the
following message appears:
LARGE_PUBLIC NPL NUMBERS REMOVED.
The requested suffix dial numbers are immediately removed from the
numbering plan.
Large Public Library Numbering Plan LIB,3,0 [0,6,3,0]

7 - ERASE When ERASE is selected the following message appears:
**WARNING**: all dial numbers will be
lost! ARE YOU SURE (Y/N)? N
Use this option cautiously! Entering Yes immediately and
permanently removes all currently defined suffix numbers from the
Numbering Plan. The default is No; Press [CR] to return to the main
Numbering Plan menu.
11-21
Large Public Library Contents ç LIB,3,1 [0,6,3,1]
This menu is used to establish a large public (system-wide) library of frequently

dialed numbers.
FROM/TO LIB# Any number up to 8 digits long

Enter the required range of large library suffix dial numbers FROM the lowest
suffix number TO the highest suffix number.
TNNT_GRP 0..63
Determines the access capabilities of various tenant groups into the Large Public
Library. Tenant groups with access levels that include Tenant Group access will be
able to use the library entry.
Large Public Library Contents LIB,3,1 [0,6,3,1]
11-22
DIAL_NUM 1 to Maximum digits (including the codes listed below) defined in SIZizes
Def., see LARGE_PUB_DIGITS (page 4-13)
 Do not enter the trunk group dial number, Routing Access or Dial Service
(for example 81, 82, etc.); enter all other numbers. The trunk group,
Routing Access or Dial Service number is entered in the OUT_TK
parameter defined below.
When using the Large Pub Library, various dialing instruction codes can also be
utilized. The following table lists these codes.
Code Instruction

number of digits
E5 Enables display


OUT_TK Any valid trunk, trunk group, dial service, Routing Access, Wait-Que, another
Public Library dial number, or None (N), Station/Boss_Group/Hunt_Group
number for special purposes;
Note: Another Large Library is not allowed.
specific facility (group) is selected, otherwise enter N. If N is entered a station
11-23
attempting to dial this Large Public Library number must also add the outside line
access code. Stations equipped with a display receive the display message:
“ENTER TK/GROUP#”.
A Public Library dial number may be entered to access a common carrier, or
private network, before the current library is dialed.
11-24
Directory ç LIB,4 [0,6,4]
The Directory feature provides keyset users a searchable directory listing. Both
Shared and Personal records are combined and organized alphabetically, for easy
retrieval. A search result can be dialed at the touch of a key.
Shared Directory is composed of the following internal and external numbers:
• Public Speed Call Library
• Hunt Group
• Boss Group
• All stations defined in the system
Personal Directory is a self-built database of external telephone numbers. It is
accessible only from the station keyset at which it was entered.
Details for the Directory are found on the following pages.
Directory - Systems (Shared) Directory Entries .............................. 11-26
̀Directory - Personal Directory............................................................11-29
Directory LIB,4 [0,6,4]
11-25
Directory - Systems (Shared) Directory Entries ç LIB,4,0 [0,6,4,0]
Systems (Shared) Directory entries may be hidden or displayed. The technician

may choose to access the entries either by their name or number:
• For NAME ACCESS choose 0
• For NUMBER ACCESS choose 1
After the access method is chosen, the technician is asked to select whether to
Update (0) or Display (1) the list. A range of entries based on whether they are
listed or unlisted (hidden) may be displayed. The Update parameter options allow
the technician to define the entries as listed or unlisted (hidden).
0-NAME Access
Enter Name Initial Any alphanumeric string of characters (max:16)
Characters
Define the range of shared directory entry names to be accessed in this parameter.
The names must already be defined as FULL Names in Port List.
Enter any one letter or combination of letters to display all names beginning with
the same letter(s) as well as all names that follow in alphabetical order after the
requested string of letters.
For Example:
Entering SM returns all names beginning with SM as well as any names in the
alphabet after SM such as SMith, SMithsonian, Sonny, Tufts, Umbridge, etc., until
the end of the directory.
Directory - Systems (Shared) Directory Entries LIB,4,0
1-NUMBER Ac-
cess
FROM/TO DIAL# Any valid system dial number
Enter the range of dial numbers for the requested directory entries to be accessed.
 The following parameters are displayed regardless of branch used to access

them: NAME ACCESS (LIB, 4, 0, 0) or NUMBER ACCESS (LIB, 4, 0, 1).
Select Entry A - All Entries (Default)

H - Hidden Entries only
D - Displayed Entries only
Request a list of system (shared) directory entries either by entries that are listed or
unlisted. Alternatively, all system (shared) entries may be displayed/updated.
11-26
The following screen is shown when the technician requests to Display - All the
entries (i.e., not in Update mode):
SYSTEMS DIRECTORY ENTRIES

NUMBER NAME TYPE DISPLAY
============================================================
2058 Mess Hall PUBLIC_LIB N
7528 Mr. President BOSS N
9311 Payroll HUNT Y
2023 Dr. Dolittle KEYSET Y
The Display column values are taken from DISPLAY_ENTRY_IN_

DIRECTORY (page 11-27) below.
Y = indicates displayed entries
N = indicates hidden entries.
0-Update
NAME Max of 16 ASCII characters as defined in Port List (Display Only)
Displays the FULL (long) name defined in Port List, for this shared directory entry.
 Shared Directory entries require a FULL:NAME to be defined for the port.

Entries with the BLANK Full Name cannot be displayed in the directory

list.
NUMBER Any NPL dial number, max 8 digit; (Display Only)

Displays the defined NPL dial number for this shared directory entry.
TYPE Public Library, Hunt Groups, Boss Groups, and System Ports (i.e. SLT,
Keysets, etc.) (Display Only)
Displays the system port type: SLT, Keyset, Public Library, Hunt Group and Boss
Group, for this shared directory entry.
DISPLAY_ENTRY_IN_ Yes/No
DIRECTORY
Define the shared directory entry as unlisted (hidden) or listed.
Enter Yes to have the directory entry displayed for all keyset users.
11-27
Enter No to unlist the directory entry and hide if from all searching and browsing
keyset users.
11-28
Directory - Personal Directory ç LIB,4,1 [0,6,4,1]
The Personal Directory menu allows adding or updating the Personal Directory
entries for a specific keyset. Update, Display and Add options are available for the
requested keyset, by entering 0, 1, or 2 after selecting the station dial number.
SELECT STATION Any valid system keyset station

DIAL#
Enter the number of the keyset station.
Enter Name Initial Any alphanumeric character(s)

Characters
Enter the initial characters of the Personal Directory entry. The list scrolls to the
first entry that is a match. All entries alphabetically subsequent to the matching
entry are available for 0-Update and 1-Display.
Once a station is selected, the following option menu is available.
Option Description
0 - UPDATE This option allows updating the directory entries for the
selected station.
1 - DISPLAY Displays all the listed entries for the selected station. The
entries are displayed from the first entry name that matches
the characters entered in Enter Name Initial Characters.
2 - ADD Adds a new entry to the personal Directory for the requested
station.
Directory - Personal Directory LIB,4,1 [0,6,4,1]

NAME Max of 16 ASCII characters
Defines the name (up to 16 alphanumeric characters), which appears on keysets
equipped with a display. A name defined as BLANK is not added to the directory.
11-29
NUMBER Any number, max 16 digit;

R (Remove the current entry from the Directory)
Add or edit the entry’s external telephone number. The number must be entered
without spaces or dashes. Do not enter the outside line access code.
Attempting to enter a number already assigned to an existing entry record causes
the following message to appear:
ALREADY DEFINED IN NAME (entry name)
Attempting to assign a number to a new entry added in excess of the maximum Size
Definition defined in ENTRIES PER USER (page 4-13), causes the following
message to appear:
ILL NUM, TRY AGAIN!
Directory - Personal Directory LIB,4,1 [0,6,4,1]
11-30
12 Night Service
Night Service contains programming instructions for Night/Weekend/Holiday

Service Timers and their Service Definitions.
Night Service - Timers ...............................................................................12-2

Night Service- Definition ...........................................................................12-5
Weekend Timers .........................................................................................12-6
Holiday Timers ...........................................................................................12-7
12-1
Night Service PI Reference Manual
Night Service - Timers ç NIGHT,0 [0,0,4,0,0]
Night Service defines the various type of timer services that are performed during
and after regular working hours including weekends and holidays. The night
service mode is used in conjunction with Night Service Definition in order to
specify all night-time telecommunication services. The system is grouped into
three service periods, each of which contains one of the three time blocks or types,
called Day, Night1 and Night2. The times at which each block becomes effective
is defined by under TIME for each of the three service and holiday groups. TYPE
allows defining one of the three time blocks for each service period (i.e. either Day,
Night1 or Night2).
ON TIME Yes (System-controlled)/No (Manual control)

Defines whether the transfer between DAY and NIGHT services is performed
automatically (controlled by the system clock) or manually (for example, by the
attendant using feature codes: #184, #185). Manual override can still be used when
automatic (Yes) is selected. This option can be changed by the attendant with
feature code #1993, see AUTO_NIGHT SERV [36] (page 7-42).
1st SERV:
TIME - 00:00..08:00..23:59
First Service Period sets the START time for the first of three time periods. The
hour entered in TIME signals both the END time for leaving the 3rd Service time
period, as well as the START time for the 1st Service time period. See Programming
and Entering Time Units (page 2-6) for defining time units.
Night Service - Timers NIGHT,0 [0,0,4,0,0]
TYPE - 0 (Day), 1 (Night1), 2 (Night2)

Defines the service mode for the 1st time period as Day, Night1 or Night2.
2nd SERV:
TIME - 00:00..17:00..23:59
Second Service Period sets the second of three time periods. The hour entered in
TIME signals both the END time for leaving the 1st Service Time period, as well as
the START time for the 2nd Service Time period. See Programming and Entering
Time Units (page 2-6) for defining time units.
TYPE - 0 (Day), 1 (Night1), 2 (Night2)

Defines the service mode for the 2nd time period as Day, Night1 or Night2. If the
2nd Service period is not defined, set this parameter to NONE.
12-2
PI Reference Manual Night Service
3rd SERV:
TIME - 00:00..22:00..23:59
Third Service Period sets the third of three time periods. The hour entered in TIME
signals both the END time for leaving the 2nd Service Time period, as well as the
START time for the 3rd Service Time period. See Programming and Entering Time
Units (page 2-6) for defining time units.
TYPE 0 (Day), 1 (Night1), 2 (Night2)

Defines the service mode for the 3rd time period as Day, Night1 or Night2. If the
3rd Service period is not defined, set this parameter to NONE.
WEEKEND/HOLIDAY 0 (Day) / 1 (Night1) / 2 (Night2)

SERV(ICE) N: No special Weekend or Holiday Service time, i.e. same as during regular
working hours. (Holidays and Weekend do not invoke any special service)
Defines which service mode (Day, Night1 or Night2) is to be used for the weekend
and holiday time periods.
Note: When making (“ROUTING ACCESS”) external calls, the system overrides
the definition here and uses NIGHT PRIORITY and NIGHT COST as defined in
Chapter 15.
HOLIDAY_-STR_TIME 00:00..08:00..23:59, or None

Start Of Holiday Time determines the time of day that holiday routing operation
begins on days which are designated as holidays. When NONE is entered, holiday
routing is not invoked.

HOLIDAY_-END_TIME 00:00..22:00..23:59, or None
End Of Holiday Time determines the time of day that holiday routing operation
ends on days which are designated as holidays. When None is entered, holiday
routing is not invoked.
CURRENT_TYPE 0, 1, 2 or NONE
Determines the current Service Mode.
 If Attendant Console Class of Service NIGHT 1 TRANSF, NIGHT 2

TRANSF, and DAY/NIGHT ON TIME are set to Yes, the Attendant Console
may be used to override the time parameters listed above.
12-3
UPDATE? Yes, No
When set to Yes, all permissible changes are entered.
When set to No, only ON_TIME is executed.
12-4
Night Service- Definition ç NIGHT,1 [0,0,4,0,1]
Night Service Definition is used to set the primary and secondary Class of Service
for each service mode (defined by Night Service - Timers on page 12-2). In addition,
Night Service - Definition allows defining the destination for incomplete calls and
intercepted calls for the defined Time Service Mode (Day, Night 1 or Night2).
FROM/ 0..2
TO 0..2
TYPE
Enter the required service modes: 0 (Day); 1 (Night1); 2 (Night2) FROM the
lowest number, TO the highest number.
COS 0 (Primary), 1 (Secondary);

Day mode: 0 (Primary), Night1/2 mode: 1 (Secondary)
Defines each service mode when primary or secondary COS is utilized for stations.
The setting is defined system-wide and is based on the Classes Of Service
programmed under SLT and KEY definitions
(see PRM_COS [0] and SEC_COS [1] on page 9-5 for COS for SLT Definition
and PRM_COS [0] and SEC_COS [1] on page 9-32 for COS of Keyset Definition).
The primary and the secondary COS can be the same.
INCOMPLETE_ Any valid system station, Hunt group, Boss group, Public Library, Bell/UNA,
CALLS_DEST Modem, DVMS MSG/Port, Group Call dial number or None
First Keyset (Attendant)
Sets the destination for unanswered calls for each service mode (set in the Night
Night Service- Definition NIGHT,1 [0,0,4,0,1]

Service Timers). An unanswered call is defined as: busy, no answer, illegal
destination, undefined, etc. This feature must be activated in System Features -
Intercept/Incomplete (page 6-33) branch (SFE, 3).
 If a Boss or Hunt group is selected for the destination of incomplete calls,

then the returning PWDS call will arrive at the first group member.
INTERCEPT_CALLS_ Any valid system station, Hunt group, Boss group, Public Library, Bell/UNA,
DEST(INATION) Modem, DVMS MSG/Port, Group Call dial number or None
None
Sets the destination for intercept routed calls for each service mode. Intercept
relevant - Toll bar, COS fail, Dial fail and/or undefined. This feature must be
activated inSystem Features - Intercept/Incomplete (page 6-33) branch (SFE, 3).
12-5
Weekend Timers ç NIGHT,2

Defines the times for Weekend Service operation. Weekend Service causes the
system to route calls according to Night Service- Definition described previously in
this chapter.
FROM_DAY 1..7 or N (No weekend)

Enter the digit representing the day of the week on which the weekend begins.
Day Digit Day Digit
Sunday 1 Thursday 5
Monday 2 Friday 6
Tuesday 3 Saturday 7
Wednesday 4 No Weekend N
FROM_TIME 00:00..23:59 or None

Enter the hour and minutes the weekend operation begins. See Programming and
Entering Time Units (page 2-6) for defining time units.
TO_DAY 1..7 or N (weekend)

Enter the digit representing the day of the week on which the weekend ends. See
the above table for digit information.
TO_TIME 00:00..23:59 or None

Enter the hour and minutes the weekend operation ends. See Programming and
Entering Time Units (page 2-6) for defining time units.
Weekend Timers NIGHT,2
12-6
Holiday Timers ç NIGHT,3

Allows the programming of Holiday operation. Holiday operation causes the
system to route calls according to the Night Service-Definition as described earlier
in this chapter. The Holiday start and end times are defined in HOLIDAY_-STR_TIME
and HOLIDAY_-END_TIME on page 12-3.
When ADD (1) is selected, time span of the holiday is defined, by defining the
holiday begin and end time. When REMOVE (3) is selected, the holiday is deleted
from the program.
The maximum number of holidays that can be entered is 15: HOLIDAY # = 1-15.
MODE 0 (Month/Day), 1 (Month/Week/Day)

Determines how the holiday period is defined, according to:
• Month and day of month (month=1-12; day=1-31)
• Month, week of month, and day of week (month=1-12; week=1-5; day=1-7)
Depending upon which mode is selected, the following parameters can be defined:
Mode Possible Parameters
0-m/d FROM MONTH FROM M DAY

TO MONTH TO M DAY
1-m/w/d FROM MONTH FROM WEEK FROM W DAY

TO MONTH TO WEEK TO W DAY
FROM_MONTH 1..12
Sets the month in which the holiday occurs. Enter the digit representing the month.
Holiday Timers NIGHT,3

Month Digit Month Digit
January 1 July 7
February 2 August 8
March 3 September 9
April 4 October 10
May 5 November 11
June 6 December 12
12-7
FROM_WEEK 1..5
Defines the week of the month from which the holiday begins.
 This parameter is not used when the Holiday Timers - MODE is set to M/D.
Enter the number (1 to 5) representing the week of the month in which the holiday
occurs.
FROM_W_DAY 1..7
Defines the day of the week (1 to 7) on which the holiday occurs.
DAY DIGIT DAY DIGIT
Sunday 1 Thursday 5
Monday 2 Friday 6
Tuesday 3 Saturday 7
Wednesday 4
FROM_M_DAY 1..31
Defines on which day of the month (1-31) the holiday begins.
TO_MONTH 1..12
Default: Same as FROM_MONTH value (above)
Enter the month in which the holiday ends - if this is different from the month in
which it begins. Enter the digits according to the table listed in FROM_MONTH.
TO_WEEK 1..5
Default: Same as FROM_WEEK (above)

Defines the week of the month from which the holiday ends. You need to define
this parameter only if it differs from the month on which the holiday begins.
 This parameter is not used when the Holiday Timers - MODE is set to M/D.
Enter the number (1 to 5) representing the week of the month in which the holiday
ends (if this is different from the week it begins).
12-8
TO_W_DAY 1..7
Default: Same as FROM_W_DAY (above)
Defines the day of the week on which the holiday ends. You need to define this
parameter only if it differs from the day on which the holiday begins.
Enter the day of the week (1-7) on which the holiday ends (if this is different from
the day it begins).
TO_M_DAY 1..31
Default: Same as FROM_M_DAY (above)
Defines the day of the month (1-31) on which the holiday ends.You need to define
this parameter only if it differs from the day on which the holiday begins.
Enter the day of the month (1-31) on which the holiday ends (if this is different
from the day it begins).
12-9
12-10
13 Toll Barriers
Toll Barriers contains the programming instructions for defining Toll Barriers
elements.
Toll Barrier .................................................................................................13-2
13-1
Toll Barriers PI Reference Manual
Toll Barrier ç TOLL [0,0,6]
 After First Initialization, Toll Barriers are not present by default in the
system. All numbers are classified as PASS. However, once ADD is
selected in the Toll Barrier option, the Toll Barrier database can be
utilized and updated.
Toll Barriers can be displayed, added or removed. Choose one of the following
options to proceed.
The following option menu is available for this Route:.
Option Description
1 - DISPLAY Displays the current Toll Barrier list of elements. When the
list is empty, the message NO ELEMENTS! appears.
2 - ADD Adds a new Toll Barrier element. This option must be

selected in order to initialize the Toll Barrier feature, (see
note above). When all ADD parameters are entered, the
system automatically increments the element number; the
element list will read:
ELEMENT# 1, ELEMENT# 2, ELEMENT# 3, etc.,
including the last element defined.
3 - REMOVE Deletes a Toll Element (Toll Elements are automatically

renumbered when an element is removed).
SELECT PTRNS 0..7

Default: All COS patterns 0..7
Select the COS pattern. Each COS can be assigned one toll barrier pattern (0
through 7, inclusive). The pattern can be defined by a single number or by several
numbers. When several numbers are entered, separate each number with a comma
Toll Barrier TOLL [0,0,6]
for example: 3,5,6. If no specific pattern is selected and [CR] is entered, all patterns
are defined.
SELECT TK_ Any Trunk Group(s) and Routing Access code(s)

GRPS/ROUTING_ACC Default: All Trunk Groups and Routing Access
Use this parameter to select the Trunk Group(s) and Routing Access codes. When
this parameter is applied, toll restrictions are placed only on the trunk group(s) and
Routing Access code(s) listed by access code (for example: 80, 81, 82, etc.). The
Trunk Group and Routing Access dial numbers must already have been defined in
the Numbering Plan. One number, several or all numbers may be selected. If
several numbers are selected, separate each number with a comma for example: 80,
83, 84. If no specific Group or Routing is selected and [CR] is entered, all Trunk
Groups and Routing Access codes are defined.
13-2
PI Reference Manual Toll Barriers
TYPE 0 (Block) Blocks the call if digits match the barrier (From/To Dial #)
1 (Pass) Passes the call if digits match the barrier (From/To Dial#)
2 (Absorb) Disregards the digits if the digits match barrier (From/To Dial #)
Defines one of three toll barrier types, once the Trunk Group or Routing Access has
been selected.
FROM/TO DIAL # Up to 32 characters (1-9, 0, *, #) and (N, P, X)

X (any digit)
Define the range of barrier digits.
N = any digit except 0 and 1
P = only digits 0 and 1
X = any digit including * and #
The TO DIAL # entry must be greater than, or equal to, the FROM DIAL # entry.
If N, P, or X is entered as part of the FROM DIAL #, the TO DIAL # is irrelevant
and does not appear as a programming option.
Toll Barrier TOLL [0,0,6]
13-3
Toll Barriers PI Reference Manual
13-4
14 SMDR
This chapter describes the programming for Station Message Detail Recording
(SMDR) parameters and Coral Internal Traffic.
Station Message Detail Recording provides on-line storage and printing of station
call information.
The Coral system offers flexibility in on-line report control, with which data is
reported, and the report’s output format.
The Coral SMDR creates a record for each trunk call. System programming defines
whether the system reports incoming calls, outgoing calls or both.
The SMDR also creates a record of internal calls between stations in the same
manner as external calls. System calls, such as Reminder, Wakeup or Camp On, are
not supported.
SMDR data can be transmitted to an external device (such as a printer) via RS-232
serial port interface or via an IP port connectivity using the MAP application as
described below:
• "In Coral systems that include the MAP application, the SMDR data can be
transmitted via an IP port using the MAP application. For hardware
requirements, refer to the relevant Control Card Installation Manual or the
Coral IPx Office Installation Manual.
• "The SMDR data is transmitted through a predetermined RS-232 port on the
peripheral RMI, 8DRCM-2, 8DRCM, 8DRCF, or MSBipx card. For interface
PIN functions and other hardware requirements, refer to the relevant Coral
Installation Manual.
Format Parameters define which SMDR parameters should be listed in the actual
report.
For further details, refer to the SMDR Specifications Manual.
SMDR Control............................................................................................14-2
Report Control ..........................................................................................14-10
Format Params.......................................................................................... 14-11
Auto On-Line............................................................................................14-13
Charge Table .............................................................................................14-16
14-1
SMDR PI Reference Manual
SMDR Control ç SMDR,0 [3,2,0]
SMDR Control is used to set the SMDR report display, storage, and call data
requirements to generate a record. Field numbers appear in square brackets ([ ]).
TK_GRPS [0] Any valid trunk group(s) or ( ) for None;

• To add one or more numbers, enter: (A, number 1, number 2,...).
• To remove one or more numbers, enter: (R, number1, number2,...).
• To remove all numbers, enter: ( ).
Identifies the Trunk Groups which may be reported for SMDR calls. Group
numbers are entered between parentheses, with each group separated by commas
or spaces.
DISPLAY_IN [1] Yes (Display Incoming Calls)/No
 Used for on-line reports.

Determines whether SMDR records are generated for incoming trunk calls.
DISPLAY_OUT [2] Yes (Display Outgoing Calls)/No
 Used only for on-line reports.

Determines whether SMDR records are generated for outgoing trunk calls.
SMDR records can be generated for selected time periods when set to No, (see Auto
On-Line beginning on page 14-13).
DISPLAY_START_ Yes/No
SMDR Control SMDR,0 [3,2,0]
CALL [3]
Used only for outgoing calls, in addition to the report generated at the end
of the call, with the final elapsed time.
.Determines whether to generate an SMDR report as soon as an outgoing call is
started indicating only that an outgoing call has been established.
This report is used for call cost limit applications. External applications allotting a
call “budget” per user ID forewarn the user of the approaching time limit. The
application can also prevent the user from overusing the budget.
14-2
PI Reference Manual SMDR
BACKUP [4] Yes/No

SAU Requirement
This parameter is irrelevant when SMDR_DEST [14] (below) is set to “99”
(configured for IP port connectivity via MAP-CNCM).
In that case the SMDR backup memory is automatically provided by the
MAP even when the BACKUP [4] feature is set to NO.
When the SMDR interfaces with the MAP application, the Coral SMDR
backup memory is not utilized and the maximum number of records used
by the SMDR_BACKUP (page 4-16) parameter can be defined as 0.
Therefore the Coral system memory allocated for this feature can be
released for other resources.
 This parameter is relevant when SMDR_DEST [14], below, is set to 1-24

and SMDR data is transmitted through a predetermined RS-232 port on
the peripheral RMI, 8DRCM-2, 8DRCM, 8DRCF, or MSBipx card.
SMDR Backup provides the capability to automatically store and save SMDR
On-Line call records whenever a printer or SMDR equipment malfunctions
(RS-232 DTR signal is lost). When this feature is enabled, the system can store the
maximum number of records in a temporary buffer, as defined in SIZES, see
SMDR_BACKUP (page 4-16). However, if the SMDR processor is out of order for a
prolonged period, the buffer may fill up and new incoming calls will be lost.
Once the malfunctioning device operates properly (the DTR signal returns) the
stored data is automatically printed.
Two types of attendant alarms concerning the state of the SMDR Backup are
available:
• DTR Alarm (Alarm Code: 60):
This alarm is activated whenever the RS-232 DTR signal is lost. The system
begins sending SMDR records to the buffer when this happens.
• Buffer 75% Records (Alarm Code: 61):

This alarm is activated whenever the SMDR buffer occupies 75% of the
records. However, up to an additional 25% of the records can still enter the
buffer. The number of records is defined in SIZES, (see page 4-16).
14-3
ON_LINE_SERIAL_ Yes/No
NO. [5]
Determines whether a serial number is shown at the beginning of each record.
ON_LINE 8_DIGIT_ Yes/No

NPL [6]
Determines whether the full eight numbers of the TK-G, TK-N, and ST number
appear in the SMDR report.
When set to Yes, the full TK-G, TK#, and ST# number parameters appear on their own
line at the end of each record.
When set to No, only the last four digits of the trunk or station number (as listed in
the Numbering Plan, Route: NPL) of the above parameters are shown.
ON_LINE EXTENDED_ Yes/No

SMDR_INFORMATION
Determines whether additional ISDN/Network parameters such as C_T (Call
[7]
Type), CPN, and AOC (Advice of Charge) appear at the end of each record.
CPN (Calling Party Name), Call Source
The prefix N or E displayed in the CPN field defines the calling number
(i.e. the call source) as follows:
• N indicates a Network calling number.
 The Network number appears in the SMDR of all the related PINXs of the
• E indicates an External calling number.
call (originating, transit, terminating/outgoing gateway).

C_T (Call Type), Call Destination
The prefix P, I or N displayed in the C_T field identifies the call destination as
follows:
• P (Private) indicates an internal call destination.
• I (International) indicates an external call destination.
• N (National) indicates a national call destination.

In order to display CLI, INCOMING_CLI_REQUEST (page 8-31) must be defined in
Trunk Group, or in DID/E&M (see page 8-39).
DISPLAY_INTERNAL_ Yes/No
NETWORK_CALL [8]
Defines whether internal network calls should be displayed on the SMDR report.
Internal network calls include calls where the calling party and the called party
originate from the same Coral network, but not necessarily from the same Coral
system.
14-4
DISPLAY_INTERNAL_ Yes/No
CALL [9]
Defines whether internal calls should be displayed on the SMDR report.
 INTERNAL_SMDR_IN_SYSTEM (page 4-27) in Sizes Tab must be set to Yes in

order to set this parameter to Yes.
Internal calls include calls where the calling party and the called party originate
from the same Coral system.
DISPLAY_ABANDON_ Yes/No
CALL [10]
(Coral version 15.85.30
 This parameter is only relevant when DISPLAY_IN [1], above, is set to Yes.
or higher) Determines whether or not SMDR records are generated for abandoned incoming
calls, including.
• Any incoming call from a station or a trunk (including QSIG and IP-Net) that
was not answered by a Coral subscriber, such that a call was never established.
• An incoming call from a trunk that was automatically re-routed to another PBX
in the network (regardless of whether or not it was answered by the dialed
party).
See 9-IN in Table 14-1 on page 14-11.
DISPLAY_DNIS [11] Yes/No
 This parameter is only relevant when DISPLAY_IN [1], above, is set to Yes.
Define this parameter to Yes to display the DNIS number of the incoming call
which is listed under DIAL# in the SMDR Report.
OUTBOUND_ Yes/No
NUMBER_AS_SENT_
ON_TRUNK [12]
 This parameter is only relevant when DISPLAY_OUT [2], above, is set to

Yes.
(Coral version 16.01
or higher) Determines whether SMDR records are generated for outgoing trunk calls (under
DIAL_TO field) with the number manually dialed by user or with the modified
number sent by Coral on trunk.
• Yes - as sent on trunk
The displayed number is the modified number “real digits” sent by Coral on
trunk.
• No - as dialed by user.
The displayed number is what the user dialed.
14-5
SMDR/CHARGE_ Any single printable keyboard character with the exception of “@”.
CURRENCY_UNIT [13] Any lower case letter entered will be displayed as a capital letter.
(Coral version 15.85.30 For space/blank, enter underscore: “_”
or higher) Default: “$”
Defines the character used to represent the unit of currency to be displayed on
SMDR and CHARGE records, along with the outgoing calls price.
Caution!
Do not define this parameter as “@” (commercial “at” sign).
This symbol is not recognized by the system and could corrupt
information in the SMDR reports.
 The currency unit for caller’s keyset display is defined by CURRENCY_UNIT

[12] parameter (Route: SFE,0) on page 6-11and is in no way relevant to
this parameter.
SMDR_DEST [14] 1..24 for RS-232 Serial or Modem port (see Table 17-2 on page 17-11)
99 for IP port via MAP
Determines the output terminal destination to which generated SMDR records are
sent for on-line reports.
 KB0 is not available for SMDR purposes.

Coral IPx Office must utilize the built-in MAP application for SMDR
purposes.
 The MAP is not available in Coral IPx 4000 and FlexiCom 6000 systems.
Enter “99” for IP port connectivity via MAP-CNCM software, if available and
active in your system (see CNCM (page 27-5) in the MAP branch (ROOT,3,10)).
The system returns the last IP port number not yet used.
If the SMDR via MAP-CNCM application is configured to Server mode, the

SMDR records are sent to the default TCP/IP socket defined by the CNCM
application. If the SMDR via MAP-CNCM application is configured to Client
mode, the SMDR records can be sent to up to two destinations (redundancy) that
are defined in the CNCM application. For further information, refer to Chapter 7
of the Station Message Detail Recording (SMDR) Specifications.
14-6
CHARGE_DEST [15] 1..24 for RS-232 Serial or Modem port (see Table 17-1 on page 17-11),
Identifies the terminal port to which selected SMDR charge printouts are sent,
when requested by attendant (using feature codes #1972, #1978).
 KB0 is not available for CHARGE purposes.

Coral IPx Office must utilize the built-in MAP application for CHARGE
purposes.
active in your system (see CNCM (page 27-5) in the MAP branch (ROOT,3,10)).
The system returns the last port number not yet used.
RESET_CHARGE_ Yes/No
TABLE? [16]
Appears in UPDATE mode, only.
Clears cost calculation and pulse metering charges (see Charge Table beginning on
page 14-16). When set to Yes, this parameter resets the charges for all stations in
the system. Resetting the Charge Table can also be performed by the Attendant
Console, by using the Reset with Printout feature code #1978, (see the Attendant
Console Guide for details).
Upon resetting, this parameter is automatically returned to No..
CHK. IN/OUT_ Yes/No

CHARGE_RESET [17]
Allows resetting the station Charge Table during Check-In/Out procedure. The
amount is cleared when Check In/Out is activated.
RESET_SERIAL_No.? Yes/No

[18]
Appears in UPDATE mode, only.
Resets the SMDR serial ticket number that is printed on the on-line report.
Upon resetting, this parameter is automatically returned to No..
SINGLE_LINE_ Yes/No
OUTPUT [19]
This parameter creates SMDR reports without Carriage Returns (CR) or Line
Feeds. Therefore, the report continues to print on the same line when this parameter
is set to Yes. This parameter is generally used for external systems using
computerized forms and replaces the definitions in Terminal Setup beginning on
page 17-11.
14-7
NUMBER_OF_CALLS_ 1..80..65534 or 0 (Header not printed)

PER_PAGE [20]

Setting this parameter to Zero (0) turns the header off.
Sets the number of call records sent to a printer before a form feed “FF” command
causes the paper to advance to a new sheet (page) and a new header to be printed.
An 11 inch page includes 66 lines.
 An 11" page contains 66 lines. However, it is good practice to define the

page as slightly less than 11" so that the text does not run off the page.
SMDR_START_ 0..10..255 seconds

CHARGE [21]
Determines the time lapse between the end of dial signal and the time a call is
considered valid to generate a call record. Calls which are shorter than this period
are not reported. This timer has no effect on, and is not affected by the SMDR_
FREE_CHARGE [22] timer.
When a meter pulse is detected, SMDR_START_CHARGE [21] and SMDR_FREE_
CHARGE [22] start immediately, without regard to the timers.
SMDR_FREE_ 0..255 seconds

CHARGE [22]
Determines the time lapse between the end of dial signal and the time the system
begins tracking elapsed time for the call. Records generated for a call shorter than
this period indicate an elapsed time (duration of call) of zero seconds. This timer
has no effect on, and is not affected by the SMDR_START_CHARGE [21] timer.
14-8
LONG_DIST 1-5 Up to 4 characters combined of: 0-9, *, #, N, P or X

[23-28] R (Remove for None: No selection - all numbers) See Entering Range for
Long Distance below
N = any digit except 0 and 1

P = only digits 0 and 1
X = any digit on the telephone keypad, including * and #
When outgoing calls are printed, it is possible to print all calls or only certain Long
Distance calls on the basis of the first four digits of the dialed number.
The call record is transmitted to the pre-determined SMDR destination,
immediately upon termination of the call.
These entries permit limiting the SMDR record, charging and on-line printing to
certain prefix digits. These prefix digits can only include the prefix codes shown
above, with a maximum of five field entries. If an entry is made, only those start
digits listed cause the system to generate a call record.
Record Output Charge (C), On-line (O) or both (CO);

Default: CO
Entering Range for Long Distance
Enter the Long Distance digits and the Record Output:
• Charge - to add the call cost to the station’s charge accumulator (See Charge
Table on page 14-16)
• On-line - to print the record as it is generated
• CO - Does both: Charge and On-Line
The delimiter “-” must be entered after the digits and character codes, but before
the record output in order to define the printing or charging method.

For Example
1NPX-CO
• Records all 1NPX calls
• Adds the call cost to the station’s charge accumulator and
• Prints the record as it is generated.
14-9
Report Control ç SMDR,1 [3,2,1]
SMDR Report Control allows defining the SMDR Report parameters according to
installation needs. The following SMDR Report options are available:
• Format Parameters
• Auto On-Line
Each SMDR Report Control option can be reached through the numeric node
number or mnemonic method. The following table presents the access options for
Report Control.
SMDR Report Mnemonic Numeric Node

Control Options Route Route
0 - FORMAT SMDR,1,0 3,2,1,0

PARAMETERS
1 - AUTO ON-LINE SMDR,1,1 3,2,1,1

Report Control SMDR,1 [3,2,1]
14-10
Format Params ç SMDR,1,0 [3,2,1,0]
ON_LINE PARMS See Table 14-1 below;

Default: the first ten codes 1 to 10
Within a call record, each discrete item of information, such as the port (Station)
that originated the call, the date the call was made, and the external number dialed,
etc., is referred to as a data field. The different data fields are listed below.
Use this option to select the parameters (see table below) that are included in the
custom SMDR on-line report. Enter the codes representing the parameters. The
entry code must be typed within parentheses. The codes may be entered in any
order. However, two or more codes must be separated by a comma, for example
(7,2,6,5,10).
 Note, three data fields may be included on the SMDR report which are not
controlled in this branch but rather in the SMDR SMDR Control branch
(SMDR, 0). When these parameters (ON_LINE_SERIAL_NO. [5], ON_LINE
8_DIGIT_NPL [6], ON_LINE EXTENDED_SMDR_INFORMATION [7]) are set to
Yes, they appear on the report regardless of the parameters chosen in this
branch (see the Notes below).
Table 14-1: SMDR Report: Format Parameter Options
Code Parameters Explanation
1 DATE Lists the date on which the call record began.
2 TIME Lists the time the call record began.
3 ELAP Lists the call duration.
4 TK-G Identifies the trunk group on which the call was made (see
Format Params SMDR,1,0 [3,2,1,0]

note •).
5 TK# Identifies the trunk number used for the call (see note •).
6 MTR Call charge
7 ST# Identifies the station originating the call (see note •).
8 ACCT. Lists the account code, if any (see note •)
9 IN Identifies either of the following as an incoming call:

• Y - Established incoming calls,
see DISPLAY_IN [1] on page 14-2.
• A - Abandoned incoming calls,
see DISPLAY_ABANDON_CALL [10] (Coral version 15.85.30
or higher) on page 14-5.
Empty “IN” fields identify outgoing calls.
14-11
Table 14-1: SMDR Report: Format Parameter Options
Code Parameters Explanation
10 DIAL# Lists the incoming or outgoing dialed number.

For an outgoing number (9-IN above is not indicated
as Y nor A), the external dialed number is listed.
For an incoming number (9-IN above is indicated as Y or A)
the DNIS number is listed.
11 XFER Identifies the call as a transferred call.

CALL It identifies when Station and Trunk COS, SMDR_SPLIT [68] on
page 7-20 is defined as either Destination or Both.
{Note: Both definition is relevant from Coral version
15.85.37 or higher}.
12 EXE PRIV. Marks a call made using the Executive Privilege feature.
13 IP_ For incoming calls, displays the IP address of the originator

ADDRESS of an IP call. (Irrelevant for outgoing calls.)
 Notes:
• When 8-ACCT. is selected and #ACCT_DGTS [7] on page 6-9, is between
5 & 16 digits, and 10-DIAL# is selected, the dial number is printed on
its own line (second line).
• When VFAC. [9] (SFE) is activated, the code is printed according to how
SMDR is defined in the VFAC branch (see page 24-8).
• When selected, TK-G, TK# and ST# are printed (each at a max of 4
digits) when an 8 digit numbering plan is required.
• When ON_LINE 8_DIGIT_NPL [6] on page 14-4 is set to Yes, then TK-G,
TK# and ST# are printed on separate lines, each eight digits long, even
if not selected here.
• When ON_LINE EXTENDED_SMDR_INFORMATION [7] on page 14-4 is set
Format Params SMDR,1,0 [3,2,1,0]
to Yes, then the C-T (Incoming Call Type), CPN (Calling Party Number)
and AOC fields are automatically printed.
14-12
Auto On-Line ç SMDR,1,1 [3,2,1,1]
This option is relevant only when DISPLAY_OUT [2] (page 14-2) is set to No.
The following parameters define the time periods at which SMDR Auto On-Line
reports for outgoing calls are generated.
HOURS Yes/No
Defines whether the SMDR auto on-line reports should be generated only between
the hours specified between the following FROM TIME and TO TIME prompts when
set to Yes.
When No is selected, SMDR auto on-line reports are not printed on an hourly basis.
The system displays the WEEKEND (Y/N) prompt next.
 When HOURS is set to Yes, the following two options are available:
FROM TIME 00:00..17:45..23:59

Enter the time the auto on-line reports are to begin. Time is entered in 24 hour
format (24:00 = midnight; 12:00 = noon; 13:00 = 1 p.m.).
For an explanation of programming and entering the time units,
see Programming and Entering Time Units on page 2-6.
For midnight hours, Auto On-Line requires:
00:00 to 00:59, to be defined as 24:00 to 24:59.
TO TIME 00:00..07:00..23:59
Enter the end time for the auto on-line reports. Time is entered in 24 hour format.
For an explanation of programming and entering the time units,
Auto On-Line SMDR,1,1 [3,2,1,1]

see Programming and Entering Time Units on page 2-6.
14-13
WEEKEND Yes/No
Determines whether auto on-line reports are to be generated on the weekend.
If WEEKEND = N (No), the next prompt is HOLIDAY (Y/N).
 When WEEKEND is set to Yes, the following four options are available:
FROM DAY 1,2,3,4,5(Thursday),6,7

Enter the number of the day (1 through 7) the weekend begins;
Sunday = 1, Saturday = 7.
FROM TIME 00:00..18:30..23:59

Enter the time, in 24 hour format on which the weekend begins. (For an explanation
of programming and entering the time units, see Programming and Entering Time
Units on page 2-6).
TO DAY 1 (Sunday),2,3,4,5,6,7
Enter the number of the day (1 through 7) the weekend ends;
Sunday = 1, Saturday = 7.
TO TIME 00:00..07:45..23:59
Enter the time, in 24 hour format on which the weekend ends. (For an explanation
of programming and entering the time units, see Programming and Entering Time
Units on page 2-6).

14-14
HOLIDAY Yes/No
Determines whether auto on-line reports are to be generated on holidays.
When HOLIDAY = Y, the prompts appear to set the holiday date and time limiters.
 When HOLIDAY is set to Yes, the following six options are available:
FROM MONTH 1..4..12

Enter the month (1 through 12) in which the holiday commences.
FROM DAY 1..21..31

Enter the day (1 through 31) on which the holiday commences.
FROM TIME 00:00..12:00..23:59

Enter the time, in 24 hour format at which the holiday commences. (For an
explanation of programming and entering the time units, see Programming and
Entering Time Units on page 2-6).
 For midnight hours, Auto On-Line requires:

TO MONTH 1..4..12
Enter the month (1 through 12) in which the holiday ends.
TO DAY 1..23..31

Enter the day (1 through 31) on which the holiday ends.
TO TIME 00:00..09:30..23:59
Enter the time the holiday ends, in 24 hour format. (For an explanation of
programming and entering the time units, see Programming and Entering Time Units
on page 2-6).
 For midnight hours, Auto On-Line requires:

14-15
Charge Table ç SMDR,2 [3,2,2]
The SMDR Call Charge Table is used to display or reset the charges or charge
individual stations. Calculating cost is programmed in Cost Calculation (see
Chapter 15).
To reset the charges for all stations, use RESET_CHARGE_TABLE? [16] (page 14-7).
Both Call Charge Printout and Call Reset With Printout can also be performed
through the Attendant Console by using the appropriate feature codes (default
codes): #1972 for Printout and #1978 for Reset With Printout.
Charges per station are automatically calculated after an outgoing call is
completed. Should a charge overflow situation develop, the printout and reset
occur automatically. Overflow is currently defined at 65,000 records.
FROM/TO STATION # Any valid station dial number

Enter the range of the required station dial numbers FROM the lowest dial number
TO the highest in order to see the cost calculation changes for that range of
telephone numbers.
CHARGE Zero (0) only for reset (only in Update mode)

This option allows resetting all accumulated pulse metering or call cost. The type
of charge is defined in System Features (Route: SFE,0) CHARGE_TYPE [10] on
page 6-10, as either Meter pulses: 0 - 65,000, or Cost: $0.00 - $6,500.00.
When selecting the Update mode, reset is accomplished by entering zero. In the
Display mode, after TO STATION # is entered, the system is instructed to begin
compiling and printing the charge table. The following messages are displayed at
the terminal from which the print request was made:
*** CHARGE REPORT START ***
Charge Table SMDR,2 [3,2,2]
This message is displayed when the system accepts the TO STATION # entry.
*** CHARGE REPORT END ***
This message indicates that the report has finished printing.
Reports are printed at the terminal defined in CHARGE_DEST [15] on page 14-7.
14-16
15 Routing & Cost Calculation
Software Authorization Limit

This chapter contains programming instructions for Routing and Cost Calculation.
Routing Block Diagram..............................................................................15-2
Routing System Parameters........................................................................15-3
Routing Access General Definitions ..........................................................15-5
Routing Class of Service ............................................................................15-9
Dial Services............................................................................................. 15-11
Route Elements.........................................................................................15-25
Routing Numbering Plan..........................................................................15-28
Routing Translators ..................................................................................15-31
Look Ahead Routing Triggers..................................................................15-32
Cost Calculation Elements .......................................................................15-38
Cost Calculation Numbering Plan............................................................15-40
Cost Calculation Parameters ....................................................................15-41
Routing Access is the Coral’s feature that represents a network’s configuration.
Different Routing Accesses (up to four) group together common parameters that
relate to a network. The Routing Access allows users to choose the specific
network in which to route their calls. A call made through Routing Access uses the
LCR (Least Cost Routing) logic. Different Routing Accesses have different
Routing numbering plans.
• Up to 4 Routing Accesses’ can be defined in System Sizes. Each of the
Routing Accesses can function as a separate Routing and have its own
Routing numbering plan, as well as other parameters.
• Routing Access numbers are assigned specifically in the system’s
General Numbering Plan.
• Before accessing the Routing Access Numbering Plan, the user is
prompted to enter the dial number of the relevant Routing Access (as
defined in the General Numbering Plan).
To Program Routing Access, begin with programming the Routing Numbering
Plan, then Routing Elements and lastly Dial Services.
Disclaimer:
The manufacturer makes no warranties of any kind with respect to the route
selection. Furthermore, the manufacturer specifically disclaims any expressed or
inferred warranties concerning the results of using Routing for any purpose.
Routing is performed according to the programmed database.
15-1
15-2
Diagram
Figure 15-1
Routing Block
Routing & Cost Calculation
ROUTING ROUTING NUMBERING CURRENT TIME ROUTE ELEMENTS DIAL SERVICES TRUNK GROUP
ACCESS PLAN
Ins 1
0) Day (4850,4851) available 4850 TK- GRPS TO CO
........... nn trunks
ELEMENT # Eve ( " " ) 4851 9 Digits outpulsed
80 xxx-xxxx Night ( " " ) on trunk,
4851 TK- GRP nn
........... 9 modified
1) Day (4850,4851)
according
81 xxx-xxxx Eve ( " " ) to filter
Night ( " " )
82 xxx-xxxx
39) Day (4850,4851)

83 xxx-xxxx 48nn TK- GRP nn
Eve ( " " )
........... nn
80 xxx-xxxx Night ( " " )
DIALED XXX...
CHECKED AND
ROUTED ON
ELEMENT #
PI Reference Manual
PI Reference Manual Routing & Cost Calculation
Routing System Parameters ç LCR,0 [ROOT,4,0,0]
Routing System Parameters apply to all Routing Access’ and are used to:
• Inform the user that Routing is being used.
• Indicate when the selected route is shown in a call record and on a keyset
display.
• Determine when system-wide offhook queuing is allowed;
when allowed, sets the offhook queuing duration.
A station user, by dialing a Route Access code before dialing the destination
number causes the system to automatically route a call over the most economical
route.
 To prohibit direct trunk access, and force station users to use Routing
Access, program the station/trunk Class of Service (see Class of Service -
Chapter 7) to access ROUTING_ACC only.
QUEUEING [0] Yes/No

Determines, system-wide, when stations are allowed to have the Queue Offhook
and Onhook features activated through a station’s Routing Class of Service.
This entry overrides the Routing Class of Service entries.
Q_OFFHK_TIME [1] 1..150..65534 (1 unit = 0.1 second)

Defines the duration that a call may queue onto (camp onto) a Routing trunk group.
This timer operates only when the Q_OFFHK parameter in Routing COS is defined
Routing System Parameters LCR,0 [ROOT,4,0,0]

as Yes.
ACCESS_TONE [2] 0 (Dial Tone), 1 (Distinctive Dial Tone), 2 (Confirmation Tone)

1: CC1
Determines what type of tone informs a caller that external number dialing can take
place. The tone is activated after dialing the Routing Access Code or after choosing
an Enblock destination (Trunk, Trunk Group or Dial Service).
15-3
Routing & Cost Calculation PI Reference Manual
ROUTING
DISPLAYED ON:
SMDR [3] Y (Show name), N (Show trunk group)
Determines whether the Dial Service name or trunk group name appears in the
Station Message Detail Recording (SMDR) record.
 SMDR must be separately programmed; see SMDR on page 14-1.

KEYSET [4] Y (Show name), N (Show trunk group)

Determines whether the Dial Service name (NAME [0] (page 15-11) in the Dial
Services branch (LCR, 3)) appears on the caller’s keyset display.
The name appearing on the keyset display is defined the Routing Access General
Definitions name (NAME [1] (page 15-5) in the Routing Access General Definitions
branch (LCR, 3)).
Routing System Parameters LCR,0 [ROOT,4,0,0]
15-4
Routing Access General Definitions ç LCR,1

Routing Access is the Coral’s feature that represents a network’s configuration.
Different Routing Accesses (up to four) group together common parameters that
relate to a network. The Routing Access allows users to choose the specific
network in which to route their calls. A call made through Routing Access uses the
LCR (Least Cost Routing) logic.
Different Routing Accesses have different Routing numbering plans.
There are 4 Routing Access defined by default. This branch defines the general
parameters for each Routing Access Dial number such as the Name, Elements and
Automatic Number IDs.
FROM/TO ROUTING_ Any valid system Routing Access dial number defined in General Numbering
ACCESS DIAL# Plan, see ROUTING_ACC [37] (page 5-44);
All
Enter the range of required Routing Access numbers FROM the lowest Routing
Access number TO the highest Routing Access number.
NAME [1] 1 to 5 printable ASCII characters, R (Remove for BLANK)

Identifies the 5 character alphanumeric name of the Routing Access. The Routing
Access names may appear on the caller’s Keyset display (see page 15-4) and/or in
the Trunk Group field of an SMDR record in place of the trunk group dial number,
when a call is routed via Routing Access. When no name is entered, the name of
Routing Access General Definitions LCR,1

the trunk group is displayed and the Dial number of the trunk group the call was
placed over is shown in the SMDR record. See General Rules for Entering Names
on page 2-10.
To erase a name, the group must be removed using the REMOVE option in the
previous menu.
DEFAULT ELEMENT# 0..49

[2]
When a dialed number is not found in the Routing Numbering Plan, the call is routed
to a default route (see Route Elements beginning on page 15-25). Typically, the
default route is the local trunk group.
NPID [3] I (ISDN telephony), P (Private), U (Unknown)
 Outgoing PRI and BRI only

Numbering Plan IDentification defines the characteristics of the NPID digits that
are sent from the Coral to the Called Network. This is one of the ISDN messages
15-5
sent to the network that informs the network in which mode the Coral is sending
the digits.
I: Coral to Public Network
P: Coral to Private Network (PABX)
U: The Public Network determines the incoming digit mode
15-6
OUTGOING ANI The following three Outgoing Calls Automatic Number Identification options
apply only during outgoing calls and define the ANI options.
• PREFIX
• SITE LDN
• SITE LDN ALL CALLS
PREFIX [4] Up to 16 digits, R (Remove for None --)
 Applies only during outgoing calls.

Enter up to 16 digits as the prefix to the Calling Party Number (CPN).
SITE LDN [5] Up to 16 digits, R (Remove for None --)

Site Listed Directory Number determines what number is sent to the network as the
calling party number. This number is also used while dialing outgoing calls through
the Routing Access code or Trunk Group or Dial Service number associated with
the current ROUTING_ACCESS.
Enter up to 16 digits as a general user identification number for all calling parties.
SITE LDN All Calls [6] Yes/No

This parameter is used to override the above SITE LDN parameter when defined.
Activating SITE LDN overrides the default option of sending Calling Party
Numbers based on the originating extension number.
15-7
TYPE OF  The following two options apply only to ISDN.

NUMBER:
CALLED [7] See Table 15-1
 ISDN only
Defines the information sent by the Coral to the Network, defining the type of
destination external number called.
CALLING [8] See Table below
 ISDN only
Defines the format of the ANI (Automatic Number Identification also known as
CPN, Calling Party Number) that the Coral sends to the Network, on outgoing
calls.:
Table 15-1: Range and Defaults for Called and Calling Type Numbers
NPID [3] (page 15-5) CALLED [7] (page 15-8) and

CALLING [8] (page 15-8)
Range Default
P (Private • R1 (Regional-1) R1 (Regional-1)

• R2 (Regional-2)
• P (PISN)
• Local
• U (Unknown,
digit format decided by the
Central Office)
U (Unknown) or • I (International - 13 digits) N (National)

I (ISDN)
• N (National - 10 digits)
• S (Subscriber - 7 digits)
• U (Unknown,
Central Office)
MLPP METHOD [9] Yes/No

Enables this Routing Access number to be used as access to the MLPP feature
instead of its feature code.
15-8
Routing Class of Service ç LCR,2 [ROOT,4,0,2]
Routing Class of Service links the Route priorities to Station Classes of Service.
Routing Class of Service also determines when the caller hears a “Warning Tone
For Expensive Groups”. In addition, Class of Service can also define when a station
is able to queue to a selected trunk group and determines the queue period.
FROM/TO COS# 0 to maximum defined in Sizes (see COS on page 4-16)

All
Enter the required COS numbers.
CALLS”.
N_EXPENSIVE_ 0 (no access to Routing), 1..30, All

LEVELS
Determines the number of levels within a Route Element priority list (up to 30
services), a station is able to access in any Route Element. The Route Priority levels
start with the first listed Dial Service. When all Dial Services in the priority list
which are available to the caller’s Class of Service (COS) are busy, the caller
receives busy tone and, COS dependent, may activate the queue on-hook feature.
Entering 0 prohibits Routing Access use by a caller with COS.
Routing Class of Service LCR,2 [ROOT,4,0,2]

Entering 1 allows only the first Dial Service listed in each route priority to be used
to process a call.
Enter ALL to allow the system to use any Dial Service listed in the route priority
to process a call.
WARNING_TONE_ Yes/No
FOR_EXPENSIVE_
Determines whether a warning tone for an expensive route is heard by a caller
SERVICES
routed to a Routing Service that has Expensive tone activated.
 EXPENSIVE_TONE in Dial Services [LCR,3] must be set to Yes to send a

tone to the station. The tone duration is defined in EXPENSIVE_ROUTE_
TONE [11] (page 6-3).
15-9
Q_OFFHK Yes/No
Allows an offhook station to automatically camp-on and access the system-wide
Routing Queue feature (Routing System Parameters), when QUEUEING
[0] (page 15-3) is defined as Yes.
Q_OFFHK_NEXT_ 1..3..255 (seconds)

SERVICE
Queue Offhook Time Out Next Service defines the time interval allowed for an
offhook station that has QUEUEING [0] on page 15-3 (Routing System Parameters)
to remain queued on a trunk group before the call is routed to the next defined
service.
Q_ONHK Yes/No
Allows a station to camp-on a busy ROUTING and then on-hook while waiting
for a free trunk.
Q_ONHK_NEXT_ 1..10..255 (seconds)

SERVICE
Queue Onhook Time-Out Next Service defines the time interval allowed for an
onhook station with Q_ONHK set to Yes to remain queued on a trunk group before
the call is routed to the next defined service.
Routing Class of Service LCR,2 [ROOT,4,0,2]
15-10
Dial Services ç LCR,3 [ROOT,4,0,3]
For routed calls, Dial Services provide filtering, line parameters, routing and
expensive tone functions. For ISDN calls (Incoming or Outgoing, Routing or
non-Routing) the Dial Service associates a network service with a call.
When an incoming call is directed via the NET-IP from another Coral system, it is
routed to the Dial Service. The Dial Service associates an IP address with each
number dialed.
FROM/TO SERVICE Any valid system Dial Service number (defined in General NPL, DIAL_SERV
DIAL# [36] on page 5-44);
All
Enter the range of required Dial Services numbers. FROM indicates the lowest dial
service number required. TO indicates the highest dial service number required.
NAME [0] 1 to 5 printable ASCII characters, R (Remove for Blank)

Identifies the 5 character alphanumeric Dial Service name. Whether the name is
displayed, depends on how KEYSET [4] (page 15-4) in Routing System Parameters
is defined. The Dial Service name may appear on telephone sets equipped with a
display. Dial Service names may also appear in the Trunk Group field of an SMDR
record. This is in place of the trunk group dial number, when a call is routed
through the Dial Service and depends upon how SMDR [3] on page 15-4 is defined
in Routing System parameters. When no name is entered, the name of trunk group
is displayed and the dial number of the trunk group the call was placed over is
shown in the SMDR record.
See General Rules for Entering Names on page 2-10, for general naming rules.
Dial Services LCR,3 [ROOT,4,0,3]

NSF [1] 0..to max defined in SIZ (see NETWORK_FACILITIES on page 4-20);
PRI only (Remove for “-”)
Network Specific Facility indicates which network facility is required when
communicating with the Network (see NSF beginning on page 26-6).
Two Dial Services cannot access the same NSF when defined for incoming only or
both incoming and outgoing. This parameter must be defined if Call by Call is
provided by the network.
ROUTING ACCESS [2] Any valid Routing Access dial number (see ROUTING_ACC [37] (page 5-44)
First Routing Access in Numbering Plan
The Routing Access number is related to the specific Dial Service. The maximum
number of Routing Access Dial Services is 4 (see page 4-21).
This destination is relevant for non-ISDN calls.
15-11
(DIAL IN/CALLER 0 to maximum defined in SIZ (see OFFSET_FILTER (page 4-15);

OUT) OFFSET [3] R (Remove for “-”)
Defines which offset filter (see page 8-42) is relevant to the trunk accessed by this
Dial Service.
Applies to trunks dialing into the Coral and also to outgoing ANI calls (reverse
conversion). When the offset filter is defined, the incoming digits are modified to
match the system numbering plan.
CALLER # OUT See DIAL_FILTER [10] below or R (Remove)

FILTER [4]
For outgoing calls only.
Defines the filter used to define the outgoing ANI (Automatic Number
Identification). This is the number that is displayed to the network.
If (DIAL IN/CALLER OUT) OFFSET [3] above is defined, then the outgoing number
(ANI) is first filtered by that offset filter and then by this Caller # Out Filter.
SERVICE TYPE [5] O (Outgoing), I (Incoming), B (Both)

Dial Services are invoked also for incoming calls.
O: Outgoing parameters are displayed.
I: Incoming parameters are displayed.
B: All parameters are displayed.
LAR ON Call Yes/No

Independent Signaling
Enables LAR on CISC.
Connections [6]
When set to Yes, LAR reroutes CISC over other channels when the current Dial
Service is faulty (see Look Ahead Routing Triggers beginning on page 15-32 for
LAR definitions) and does not block a trunk or Dial Service.
LAR TRIGGERS SET 0..3

[7]
Define the LAR triggers Set to be used with this Dial Service (see NAME (16) [1] on
page 15-34).
15-12
EXTENDED Yes/No
INTERNAL DIAL_
SERVICE [8]

When this parameter is set to Yes, ROUTING DEST NUM [9], below, is
irrelevant.
Allows the system to reroute internal calls routed externally.
Procedure:
The user-dialed external number is retained within the system and rerouted (by
modifying the outgoing number) using the DIAL_FILTER [10] and (DIAL IN/CALLER
OUT) OFFSET [3] filters in this branch.
The call is then dialed through the ROUTING_ACC code or Trunk Group or Dial
Service number associated with the current Routing Access.
 To apply the above parameter to a trunk group, set the ALLOW_TRUNK_

GROUP_IN_EXTENDED_INTERNAL_DIAL_SERVICE parameter
(Route: SYSGEN,3,2) to Yes (on page 4-42), requires level 2 password.
This feature is useful when part of a dialed number needs to be relayed
over an analog trunk with the Overlap method.
• Tip: To reroute an originating internal call routed via a trunk, set DIAL_
FILTER [10] to identify the DOD prefix, truncate it, and send the
remaining digits to the NPL. The NPL identifies the remaining digits as
an internal station number and routes the call to the requested station.
When this parameter is set to Yes, a user dialing directly to this dial service receives
an ILLEGAL message.
ROUTING DEST NUM Any station number (Keyset, SLT or WST), ACD/UCD group, Boss Group,
[9] Group Call or Trunk Group number
First Dial Service: First trunk group in Numbering Plan
All other Dial Services: (--)
 When EXTENDED INTERNAL DIAL_SERVICE [8], above, is set to Yes, this

parameter is not displayed.
Enter the dial number to be used by the Dial Service to process outgoing calls.
• For Network configurations:
When a local node requires a CO line through a remote node, the trunk
group(s) between the two nodes should also be defined to route external
network calls.
In order to route external network calls, another Dial Service should be defined for
the same QSIG ROUTING_DEST_NUM. The existing Dial Service supports routing
calls within the network (NPID of the related Routing Access = private) and the
other supports routing calls out of the network (NPID of the related Routing
Access= ISDN telephony).
For NET-IP this parameter defines the relevant trunk group to be configured.
15-13
DIAL_FILTER [10] See information below or R (Remove)
 For outgoing calls only.

Determines which digits are deleted, added, removed or unchanged to the
user-dialed digits. Some long distance carriers cannot accept a leading digit “1”;
some calls may be routed along a tieline (network) and digits added (the tieline
code) and deleted (the leading “1” and area code).
The various dial filters and their operational instructions are:
• [n n] = remove specified digit(s) or characters (0-9, #, * represented here by n
n) from the user-dialed digit string; the square brackets must be keyed;
[n n] is a conditional deletion and is used only from the first digit in the
user-dialed digit string.
• Rn = remove “n” (n = 0-9) number of digits to the right of the Rn instruction.
• nn = add the specified digits (0-9, #, *) to the user-dialed digit string; a Public
Library (speed call) editing number may be inserted (see page 11-7).
• Dn = delay for “n” seconds (0-9); several Dn entries may be placed together if
the required pause is greater than 9 seconds.
• %n = send the following “n” (n = 0-9) digits as they were dialed by the caller.
• R = Removes a defined filter, used in order to clean a filter and return the filter
 Notes:
to the default filter.
• A “conditional extraction” ([nn]), if used, must be for the first digit(s)

in the user-dialed digit string; “conditional extraction” cannot be used
elsewhere within the user-dialed digit string. Use Rn (where “n”=0-9)
to remove digits other than the first digit(s) in the user-dialed digit
string.
• If more than 9 digits must be removed using the Rn (where “n” = any
digit from 0 to 9, inclusive), or if a delay (Dn, where “n” = any digit
from 0 to 9, inclusive), if more than 9 seconds is required, enter the

instruction as often as necessary to accomplish the task. For example,
to delete 12 digits, enter R9R3 (9+3=12); to add a 30 second delay
enter: D9D9D9D3 (9+9+9+3=30).
EXPENSIVE TONE Yes/No for each (day/even/night) period (N/N/N)

(day/even/night) [11]

Outgoing Calls only
Determines when an Expensive Route warning tone is sent to the caller (as defined
in Routing Class of Service) when the call is routed through the defined Dial
Service. Each of the three time periods can be independently set.
15-14
TNNT_GRP [12] 0..63

Defines the tenant group number required for accessing the Dial Service for
outgoing calls. This option can be used to block certain users from dialing directly
via the Dial Services.
Tenant restrictions are defined through COS.
BCCOS [13] 0..63

ISDN Only
Defines which Bearer Capability COS is relevant for trunks defined as ISDN when
dialing in or out of the Coral System (see BCCOS Control beginning on page 26-5).
COS [14] 0..to maximum defined in SIZ (see COS (page 4-16))
 Applicable only when Call by Call is available from the Network.

Determines the Class of Service in effect when receiving an incoming call through
a Dial Service. The COS assigned to a call received through a Dial Service
overrides the COS assigned to the specific trunk.
D.I.L. DESTINATION None;

[15] Any valid station, Boss/Hunt group, Public Library, Bell/UNA, RMI Modem,
DVMS MSG/Port, Group Call
Direct In Line at Day Service determines the destination of an incoming call with
service (e.g. with NSF) during the Day Time. This definition overrides any
destination in the Trunk general definitions or DID destination indicated by the
Network.
NIGHT1 DESTINATION None;


service (e.g. with NSF) during the Night1 Time. This definition overrides any
Network.
NIGHT2 DESTINATION None

service (e.g. with NSF) during the Night2 Time. This definition overrides any
Network.
15-15
DIAL IN FILTER [18] See DIAL_FILTER [10] on page 15-14

Incoming Calls only
This filter modifies digits received from the trunks in the group to match the system
number. A filter can channel an incoming call to an outbound line or service. Such
a filter contains a Public Library dial number.
USE SECOND ALI [19] Yes/No
 Set this parameter to Yes for the Dial Service that routes calls to the local
Emergency center.
When an alternate ANI is provided for the caller (e.g., for the PSTN for emergency
calls, see SEC_ALTERNATE_LINE_ID [29] on page 9-13 for SLTs and SEC_
ALTERNATE_LINE_ID [67] on page 9-62 for Keysets), this parameter decides
whether the Alternate Line ID should be sent to the called network instead of the
primary ALI.
Set this parameter to Yes for the Dial Service that routes calls to the local
Emergency (E911) Center.
This prevents calls routed via the Dial Service from sending the primary ALI to the
called network. The Second ALI containing information intended for the
Emergency center is sent instead.
In cases where it is impossible to form the outgoing ANI (e.g. an originating caller
that does not have a number in the NPL, then the DEFAULT_SECOND_ALI [18] on
page 6-12 is used, when defined. The ISDN type of number (when applicable) is
set to Unknown. If there is no definition for the Default Second ALI then the
information is sent to the network including an indication that the number is

unknown.
15-16
COMPRESSION_ Only available codes are displayed

CAPABILITY [20] 0=G.711 with 10ms; 7=G.729 with 40ms;
2=G.711 with 40ms; 9=G.723 with 60ms;
4=G.729 with 10ms; 11=G.711 with 80ms
5=G.729 with 20ms; 12=G.723 with 90ms;
6=G.729 with 30ms; 13=G.729 with 80ms;

G.723 defines compression ratio between 5 and 6 (Not Available)
VAD makes use of silence to gain even better call compression (Not
Available)
Define the call compression values for calls using this Dial Service.
When a call is established, the system checks which compression capabilities are
available for both sides in the following order:
1. The compression capability for this Dial Service must match the COS
compression capability defined for the calling station (see USER_
COMPRESSION_LIST [105] (page 7-31)).
If the calling station is an IP Keyset, then one of the COS compression
capabilities must match a compression capability of the IP Keyset.
If the calling station is an IP_SLT or IP_LGS, then one of the COS
compression capabilities must match a compression capability of the media
module.
This defines the compression capabilities of the originating side, now this must
be matched against the capabilities of the destination side.

2. The compression capability now must match the COS compression
capability defined for the called station (see USER_COMPRESSION_LIST
[105] (page 7-31)).
If the called station is an IP Keyset, then one of the called station’s COS
compression capabilities must match a compression capability of the IP
Keyset.
If the calling station is an IP_SLT or IP_LGS, then one of the called station’s
COS compression capability must match a compression capability of the
media module.
3. The highest priority compression capability defined for all sides is used.
If no match is found, then the call cannot be completed and the message
CODEC MISMATCH appears on the keyset display.
The keyset COS is defined in PRM_COS [0] on page 9-32.
15-17
NET_IP: The following options are applicable for IP_NET and are irrelevant when this Dial
Service is used for SIP trunk.
IP_ADDRESS [21] Range: Any valid IP Socket address or R (Remove for Blank)
See the IT Manager for legal IP Address
Default: 255.255.255.255:_ _ _ _
Enter the UGW Global IP Signalling Socket address for the remote destination
UGW used with this Dial Service.
This is used to connect IP devices between Network nodes because the Sentinel
does not support IP NET trunks.
This Dial Service is also used for defining Unregistered SIP trunks, see SIP Trunk
The IP_ADDRESS [21] is irrelevant when SIP_TRUNK [23] is set to Yes.
SIGNALING_LOCAL_ Yes/No
IP_ADDRESS [22]

This parameter is only relevant when this Dial Service’s Zone is defined to
use Global IP addresses (i.e. IP_ADDR (page 29-85) in IP_Zone (IP,6)
branch is set to Global).
Set this parameter to Yes in order to create a Looped IP NET circuit, when IP_
ADDR (page 29-85) in IP ZONE, (IP,6) for the Zone used by this Dial Service is set
to Global.
In this manner, the IP NET circuit uses the Local IP Address for its Signalling
transmission, even though the Zone is defined to use Global Address for the call’s
parties.
The SIGNALING_LOCAL_IP_ADDRESS [22] is irrelevant when SIP_TRUNK [23] is set
to Yes.
SIP_TRUNK [23] Yes/No

Determines whether this Dial Service is used for SIP trunk (Yes) or not (No).
The following options apply only to SIP trunk calls.
The maximum number of Dial Services that may be defined for SIP trunks cannot
exceed Sizes Definition - FOREIGN_PROXY on page 4-19.
15-18
SIP_GENERAL: The following options are relevant for all SIP trunk calls. These parameters are
displayed only when SIP_TRUNK is defined as Y (Yes).
PROXY_ Range: R (remove), IP address, or

NAME/ADDRESS [24] any legal domain name, maximum 50 characters, case sensitive:
A-Z, a-z, 0-9 “*” (asterisk), “&” (ampersand), “+” (plus), “$” (dollar sign),
“-” (hyphen), “_” (underscore), “.” (period), “!” (exclamation point), “~” (tilde),
“/” (slash mark), “%” (percent)
Default:_ _ _._ _ _._ _ _._ _ _

Defines the proxy name or IP address of the ITSP (Internet Telephony Service
Provider).
 When using a DNS, the IP address of the DNS server must be defined (see
PRIMARY_DNS_ADDRESS(#/R) [21] on page 29-77).
PROXY_PORT [25] Range: 0...5060...65535
Default:5060
Defines the port of the ITSP (Internet Telephony Service Provider). This parameter
is relevant when the DNS does not supply the port.
TRANSPORT [26] 0-TCP, 1-UDP, 2-TLS

The transport protocol used by the ITSP (Internet Telephony Service Provider).
This parameter is relevant when the DNS does not supply the port.
TRANSFER_METHOD R (Refer), I (re-Invite)

[27]
When a Coral station tries to transfer a SIP trunk or SIP station, its matching
definition is checked and the transfer proceeds accordingly. For unregistered
trunks, the Dial Service definition always overrides the port definition. If the
transfer is performed via re-INVITE, and user B or user C are SIP stations, the
transfer data will not appear on the display panels.
 The REFER message does not work with SIP trunks. For SIP trunks,
re-INVITE must be defined.
SUPPORT_SESSION_ Yes/No
PROGRESS_183 [28]
Coral supports Session Progress 183 and therefore, can be configured to relay the
media from a remote phone that responds to an INVITE request of a SIP phone.
The caller from the SIP phone will hear the media of the remote station instead of
the standard SIP ringback tone.
15-19
The media of the remote device are packetized according to the Session
Description Protocol (SDP). Session progress response 183 relays the SDP data
from the remote device to the SIP phone. When the SUPPORT_SESSION_
PROGRESS_(183) parameter is set to Y (Yes) for the Coral SIP device, the session
progress response of the remote device will be relayed to the Coral SIP device. The
SDP information including the tone of the remote device will be heard instead of
the ringback tone generated by the Coral SIP device.
 This feature will work only if the remote device is configured to transmit
information in EARLY MEDIA (i.e. before the SIP session begins).
When set to Y (Yes) for a Coral SIP trunk, Coral relays the session progress
response from a remote device to that trunk. If the Coral SIP device does not
support the session progress response, set this parameter to N (No). If this
parameter is defined differently under DIAL SERVICES and SIP TRUNK, the
definition under DIAL SERVICES overrides the definition under SIP TRUNK for
that trunk.
INTERNAL_HOLD [29] Yes/No

Enables Music on Hold (MOH) to be heard by another party by using SENDRCV
instead of SENDONLY. When this parameter is set to Y (Yes), MOH is sent via
SENDRCV. When this parameter is sent to N (No), MOH is sent via SENDONLY.
This parameter also appears under the SIP Trunk branch. The parameter definition
under Dial Services overrides the parameter definition under SIP Trunks.
DIVERSION_ No/Sip/Tel
HEADER_URI_TYPE
Coral supports diversion headers URI (Uniform Resource Identifier).
[30] When a call is forwarded to a SIP terminal or trunk, a diversion header can be sent.
This means that if party A calls party B and is forwarded to the SIP Voicemail of
party B, party A reaches the Voicemail of party B.

This parameter defines whether or not diversion headers are sent to SIP terminals
or trunks. When Sip or Tel is defined, diversion headers are sent to SIP terminals
and trunks. When No is selected, diversion headers are not sent to SIP terminals
and trunks.
When Sip/Tel is selected, the diversion is sent according to the following formats:
• <sip:xxx.xx.xx.xx>
• <tel:xxx.xx.xx.xx>
This convention is selected according to requirements of the local technology.
The definition for a given trunk under DIAL SERVICES overrides the definition
under SIP Trunk: DIVERSION_HEADER_URI_TYPE [10] on page 29-59.
15-20
SIP_OUTGOING: The following options are relevant for outgoing calls only.
USER_NAME [31] R (remove), maximum 50 characters, case sensitive:

Defines the authentication password of registration and outgoing INVITE request
when an authentication request is sent by the far proxy. This parameter is provided
by the ITSP (Internet Telephony Service Provider).
AUTHENTICATION_ R (remove), maximum 50 characters, case sensitive:

USER_NAME [32] A-Z, a-z, 0-9 “*” (asterisk), “&” (ampersand), “+” (plus), “$” (dollar sign),
(Coral version 16.01.15 “-” (hyphen), “_” (underscore), “.” (period), “!” (exclamation point), “~” (tilde),
or higher) “/” (slash mark), “%” (percent)
When required by the ITSP (Internet Telephony Service Provider), defines the
authentication user name of registration and outgoing INVITE request when an
authentication request is sent by the far proxy. Otherwise, the USER_NAME [31]
parameter may be used instead.
PASSWORD [33] R(remove), maximum 20 characters, case sensitive:

“/” (slash mark).
Defines the authentication password of registration and outgoing INVITE request
when an authentication request is sent by the far proxy. This parameter is provided
by the ITSP (Internet Telephony Service Provider).
FROM_HOST [34] Caller/Account_username

Defines which of the following is sent to the ITSP (Internet Telephony Service
Provider) proxy server with outgoing calls:
• Caller - the caller ID (i.e. the dial number) is sent to the ITSP proxy server
• Account_username - the user name provided by the ITSP
FROM_DOMAIN [35] Client/Server

Defines the Domain name that will be sent with each outgoing call. If “C” is
selected, the domain name will be taken from the SELF DOMAIN parameter under
the IP General branch, when defined, or the card local/global IP address (according
to zone setting). If “S” is selected, the domain name will be taken from the PROXY_
NAME/ADDRESS [24] on page 15-19.
15-21
OUTBOUND_PROXY_ Range: Any legal domain name or IP address.

NAME/ADDRESS [36] Default:_ _ _._ _ _._ _ _._ _ _
Defines the name or IP address of the ITSP (Internet Telephony Service Provider).
OUTBOUND_PROXY_ 0...5060...65535
PORT [37]
Defines the port of the server that connects to the proxy.
REGISTRATION [38] Yes/No

This parameter enables the Coral to register with a foreign proxy.
When set to No, enables connecting with Unregistered SIP trunks, which means
name/password is not required.
 Note: In some cases, at night service time, Unregistered SIP trunks are put
in sleep mode by the ITSP, so that incoming calls cannot enter the system.
To overcome this situation, define the REGISTRATION parameter as Yes,
and reduce the BACK_OFF_TIMER [15] on page 29-74 to 1 minute. The Coral
will send messages to the ITSP every 1 minute. These messages will
constantly sent, which will cause the ITSP and the Unregistered SIP trunks
to never be put into sleep mode.
REGISTRAR_ Range: Any legal name or IP address

NAME/ADDRESS [39] Default:_ _ _._ _ _._ _ _._ _ _
Defines the IP address of the registrar server. This parameter is relevant only if the
address is different from the PROXY_NAME/ADDRESS [24] on page 15-19.
REGISTRAR_PORT 0...5060...65535
[40]
Defines the port of the registrar server. This parameter is relevant only if the
registrar port is different from the proxy port. This parameter is relevant only when
working with IP addresses.
15-22
CURRENT_ Range Any legal domain name or IP address.

REGISTRAR_ Default:_ _ _._ _ _._ _ _._ _ _
NAME/ADDRESS [41]
Displays the destination (name or IP address of the server) to which the Coral will
refer when registering the SIP trunk. Even if the PROXY_NAME or
REGISTRAR_NAME parameters have been defined, the ITSP (Internet
Telephony Service Provider) can accommodate a 3xx request and redirect the
registration request to another destination. This parameter displays the destination
to which the Coral will refer to register the SIP trunk.
STATUS [42] Range: Active, Reg Fail, IN PROCESS (Display only)

Default: [Display only]
Displays the current registration status of the server. When the field is blank, the
SIP trunk is not registered. When “Active” is displayed, the SIP trunk is registered.
When “Register_Fail” is displayed, registration was attempted but not successful.
REGISTER_NOW [43] Yes/No

Causes the Coral SIP trunk to register via the destination defined in the CURRENT_
REGISTRAR_NAME/ADDRESS [41] parameter (above).
When Y (Yes) is selected, the SIP trunk will automatically register. Entering Y is
similar to any common reset function.
15-23
SIP_INCOMING: The following options are relevant for incoming calls only.
PROVIDER_IP_LIST: Range: Any valid IP address or R (Remove for Blank)

#1 [44] See the IT Manager for legal IP Address
#2 [45] Default:_ _ _._ _ _._ _ _._ _ _:_ _ _ _
#3 [46]
#4 [47]
#5 [48] Up to five IP addresses provided by the ITSP (Internet Telephony Service
Provider) can be entered in the fields below this parameter (#1, #2, #3, #4, and #5).
Incoming SIP calls from that ITSP can be routed through any of these IP addresses.
Enter R adjacent to the value to be deleted.
DESTINATION_ To/Uri
NUMBER [49]
Configures the Coral system to recognize incoming SIP trunk numbers from the
(Coral V. 15.85.37 or Internet Telephone Service Provider (ITSP) according to its “URI” format (default)
higher) or according to its “To” format. This parameter is relevant:
• When the PROXY_NAME/ADDRESS [24] parameter (SEE PAGE 15-19) is
defined by a name, or
• For incoming calls from IP addresses that are different from that defined by the
PROXY_NAME/ADDRESS [24] parameter.
AUTHENTICATION Yes/No
[50]
This parameter defines whether authentication is required by incoming SIP trunks.
PASSWORD [51] R (remove), maximum 20 characters, case sensitive:

“/” (slash mark).
Defines the authentication password of calls received with an INVITE request
when an authentication request is sent by the local proxy. This parameter is
displayed only when SIP_TRUNK Yes/No is set to Yes.
15-24
Route Elements ç LCR,4 [ROOT,4,0,4]
Route Elements define the priorities for each of the three time periods
(day/evening/night). These time divisions generally correspond to the long
distance carrier’s rate periods, which usually start at 8AM, 5PM and 11PM.
 During weekends or holidays, as defined in Night Services, the priorities

for outgoing calls will be according to Night PRIO.
FROM ELEMENT # 0..49

TO ELEMENT # 0..49
Enter the required Route element numbers to be updated or displayed FROM the
lowest element number TO the highest element number.
 This option applies only to the REMOVE mode.

SELECT ELEMENT #
0..49
Enter the required Route element number to be removed.
LAR MAX 0..2..10

ASYNCHRONOUS
Defines the maximum number of LAR attempts to reroute the call to the next Dial
FAILS
Service (see Look Ahead Routing Triggers beginning on page 15-32 for
ISDN/QSIG cause numbers that trigger LAR). After the maximum is reached, the
connection fails and the system returns a cause failure to the originating (or transit
originating) Coral.
LAR SYSTEM Cost/Performance

PREFERENCE
Route Elements LCR,4 [ROOT,4,0,4]

Define the LAR system preference, whether lower system costs are more important
or system performance is more important.
Selecting Performance causes the LAR mechanism to block the failed Dial Service
for a longer period. This reduces the number of attempts to reroute the call to that
trunk or Dial Service, thus providing a faster response for the user.
Selecting Cost causes the LAR mechanism to block the faulty Dial Service more
frequently, thus increasing the probability of establishing a connection over the
most economical route.
15-25
DAY: FROM None or 00:00..23:59

Enter the hour and minute, in 24-hour format, when the DAY routing is to begin.
The DAY:FROM time entry is the end time for the NIGHT:FROM entry. If
NIGHT:FROM, below, is not defined, then DAY:FROM defines the end of the
EVEN:FROM period. If EVEN:FROM is not entered, then DAY:FROM has no
meaning and the Route Element is defined over the entire day (see Figure 15-2
below).
For an explanation of programming and entering the time units, see Programming
and Entering Time Units on page 2-6.
Figure 15-2.
DAY:FROM EVEN:FROM
24-Hour Day Chart
End of NIGHT End of DAY period
period or or End of NIGHT
End of EVENing if if DAY:FROM not
NIGHT:FROM not DAY defined
defined
NIGHT:FROM
End of EVENing
If NIGHT:FROM and NIGHT EVENing
period or
EVEN:FROM are not End of DAY if
defined, then DAY is EVENing:FROM not
defined for an entire 24 defined
hours.
DAY: PRIO Any valid combination of Dial Services or ( ) None;

Route Element #0: 1st Dial Service 4850, Route Elements #1-49: ( )
Defines the priority order of the Dial Service to be used during the DAY time
period. Enter the most economical Dial Service first and the most expensive Dial
Service last. Normally, the Dial Service which routes calls directly over local
trunks is entered last. A Dial Service may be entered more than once to fill out the
priority list so that the number of levels in the list satisfies Route COS
requirements. Enter Dial Services within parentheses, separated by commas, e.g.
(4850,4851,4855). The number of Dial Services available is determined by SIZES
upon system configuration. The Dial service number value is determined by the
General NPL.
EVEN: FROM None or 00:00..23:59

Enter the hour and minutes in 24-hour format for the evening time period to begin.
The EVEN:FROM entry is the end time for the DAY:FROM entry. If no
EVEN:FROM time is entered, then NIGHT:FROM defines the end period for the
day time Route Element (see Figure 15-2 on previous page). For an explanation of
on page 2-6.
15-26
EVEN: PRIO Any valid combination of Dial Services or ( ) None

Same as above, but for the Evening period.
NIGHT: FROM None or 00:00..23:59

Enter the hour and minutes in 24-hour format for the night time period to begin.
The NIGHT:FROM entry is the end time for the EVEN:FROM entry. If no
NIGHT:FROM time is entered, then DAY:FROM defines the end period for the
day time Route Element (see figure on previous page). For an explanation of
on page 2-6.
NIGHT: PRIO Any valid combination of Dial Services or ( ) None

Same as above, but for the NIGHT, WEEKEND and HOLIDAY periods.
15-27
Routing Numbering Plan ç LCR,5 [ROOT,4,0,5]
The Routing Numbering Plan is used to list dialed number patterns and their
appropriate routing. Each range of number patterns is listed from least specific to
most specific, with the appropriate Route Element to process the number pattern,
and the total number of digits to be received before routing begins. Numbers not
defined in the Routing Numbering Plan follow the defaults defined by the Routing
System Parameters beginning on page 15-3.
! The Routing Numbering Plan has NO connection to the General

Numbering Plan described in Chapter 5.
SELECT ROUTING_ Any valid system Routing Access dial number (defined in General
ACCESS DIAL # Numbering Plan [37], see Chapter 5)
Enter the Routing Access dial number, no default is available.
FROM 0-9, *, #, N (2-9), P (0,1), X (0-9)
 If N, P, or X appears in the FROM entry, the TO prompt does not appear.

Enter the lowest number (one or more digits up to a maximum of 32) to set the
range of numbers for the Routing function to check. See entry EXAMPLES below.
TO 0-9, *, #, N (2-9), P (0,1), X (0-9)

Same as entered in FROM above
Routing Numbering Plan LCR,5 [ROOT,4,0,5]
Enter the highest number (one or more digits up to a maximum of 32) to set the
range for numbers for the Routing function to check. The TO dial number entry
must be greater than, or equal to the FROM dial number entry.
If FROM above is defined with N, P or X, this parameter does not appear.
EXAMPLES
FROM 1-301 TO 1-401:
All numbers from 1-301 to 1-401 (inclusive) are routed.

FROM 1-NNX TO (no entry):
All area codes (NNXs) are routed. An area code’s first two digits (N) may be any
digit except 0 and 1; and its final digit (X) is any digit.
Program the Routing Numbering Plan entries from the general to the specific, for
example, first enter NNX, then enter 1NNX, then 1812 to avoid overlapping (see
Overlapping Note on page 15-30).
15-28
ELEMENT 0..49
As defined in default route (“-”)
 The selection of the Default element is displayed as a dash ( - ).

Determines the Route Element to process a call matching the FROM and TO dialed
digit information entered above. If the Route Element is not selected through this
option, but default is selected by pressing [CR], then the call is routed according to
DEFAULT ELEMENT# [2] (page 15-5) defined in Routing Access General Definitions.
N_DGTS “-” or N: None

0 to max digits defined in SFE (see MAX_DGTS_ON_TK [5] (page 6-8))
 Applicable if ENBLOCK Dialing is used outside Routing Access.

Not all Routing Access parameters must be defined for ENBLOCK to
function when the call is made outside Routing Access.
Determines the total number of digits the system must receive at this specific route.
When the required number of digits are reached by dialing, the call is immediately
out-dialed by the Routing process. If the number is not reached, the digits are dialed
at the end of the trunk interdigit time.
TYPE_OF_NUM :
ISDN only
Table 15-2: Range and Defaults for Called and Calling Type Numbers
NPID [3] (page 15-5) CALLED [7] (page 15-8) and

CALLING [8] (page 15-8)
Range Default

P (Private • R1 (Regional-1) R1 (Regional-1)
• R2 (Regional-2)
• P (PISN)
• Local
• U (Unknown,
Central Office)
U (Unknown) or • I (International - 13 digits) N (National)
I (ISDN)
• N (National - 10 digits)
• S (Subscriber - 7 digits)
• U (Unknown,
Central Office)
Defines the type of number to be indicated to the network on outgoing calls

matching the corresponding dial range. If not specified, the default is taken from
TYPE OF NUMBER: CALLED [7] (page 15-8).
15-29
Overlapping When assigning ranges to different elements, any number entered in the range may
Note be a maximum of 32 digits. Therefore, when two ranges of differing length are
entered and both incorporate identical first digits, overlapping may occur.
To avoid overlapping, always enter ranges in the most general terms possible (i.e.
using the N, P, and X terms). The N, P and X digit terms are all inclusive until a
specific digit range is encountered. If this is not possible, then the larger range must
be broken up to exclude the specific digit range.
Example 1:
Assigning the ranges:
100 Ô 119 to Element 3 and
1134 to Element 7
causes overlapping at the 1134 number since 113 and 1134 (as well as any other
number beginning with 113) are routed similarly.
 To avoid overlapping:
Define the 100 Ô 119 range as 1PX.
Example 2:
Assigning the ranges:
1234 to Element 7
causes overlapping at the 1234 number since 123 and 1234 (as well as any other
number beginning with 123) are routed similarly and therefore cause an ambiguity
with regard to which routing element should be selected.

To avoid overlapping:
Define the 100Ô 189 range as two ranges (the digit terms do not apply in
this case):
1234 to Element 7.
15-30
Routing Translators ç LCR,6 [ROOT,4,0,6]
Routing Translators allow for the addition, subtraction or change of digits in a

number to make the number dialed appear as if it was dialed from the alternate
routing destination. In the following four fields a default is not available and a
variable must be entered in the field.
SOURCE Any valid system Routing Access Dial Number (defined in General
Routing_Access DIAL Numbering Plan, see NPL, 0,5,37)
#
The Routing Access number chosen/accessed by the user.
DESTINATION Any valid system Routing Access Dial Number other than the one entered
Routing_Access DIAL above for SOURCE
#
The Routing Access number to which the dialed number is routed.
FILTER See DIAL_FILTER [10] on page 15-14

The filter modifies digits received to match the CO or outgoing service's
requirements. Digits may be added, removed (i.e. ignored) or conditionally
A filter can channel an outgoing call to any outgoing trunk or service as well as
public library number.
OFFSET 0 to Maximum defined in OFFSET_FILTER in SIZ, or R (Remove)

Defines which offset filter is applied for trunks accessed by the Destination
Routing Translators LCR,6 [ROOT,4,0,6]

Routing (see page 8-42).
15-31
Look Ahead Routing Triggers ç LCR,7 [ROOT,4,0,7]
The Look Ahead Routing (LAR) mechanism helps prevent telephone network
failures by rerouting calls. Network failures causes are identified in this branch and
the faulty component (trunk or dial service) is temporarily blocked. The call
continues to be rerouted until it can be completed. The call rerouting is transparent
to the network user.
LAR handles only asynchronous network failures (i.e., a call attempt failure after
a trunk is seized but before the call is answered by the terminating end) for Public,
Private, IP or analog networks.
When the LAR mechanism blocks a trunk or Dial Service because of an
asynchronous failure, an alarm message that contains the failure “cause” is
automatically displayed on the PI screen and an alarm message is stored in the
Diagnostics Alarms branch (see 23- LAR ALARMS on page 22-9).
The technician can use the LAR attendant feature (default feature dial number:
#1979) to manually block or unblock the Trunk or Dial Service blocked by the
LAR mechanism. This feature enables the technician to test faulty trunks or Dial
Services and then return them to service.
A list of failure causes and their meaning is presented here:
Table 15-3: Cause Numbers and Descriptions
# Cause Description # Cause Description # Cause Description

1 unassigned number 2 no route 3 no route to destination
(dest=UGW)
Look Ahead Routing Triggers LCR,7 [ROOT,4,0,7]
4 send special information 5 misdialed trunk prefix 6 channel unacceptable

tone
7 call delivered in established 8 prefix 0 dialed but not 9 prefix 1 dialed but not
channel allowed allowed
10 prefix 1 dialed but not 11 more digits received than 16 normal clearing
required allowed
17 user busy 18 no user responding 19 no answer from user
21 call rejected 22 number changed 23 reverse charging

rejected
24 call suspended 25 call resumed 26 non-selecting user

clearing
27 destination out of order 28 invalid number format 29 facility rejected
30 response to status enquiry 31 unspecified cause 33 circuit out of order
34 no channel available 35 destination unattainable 37 degraded service
38 network out of order 39 transit delay range can't be 40 throughput range can't
achieved be achieved
* Do not define these Causes as “Block Override” in a Coral Network
15-32
Table 15-3: Cause Numbers and Descriptions
# Cause Description # Cause Description # Cause Description

41 temporary failure or 42 network congestion 43 access information
IP Signaling failure discarded
44 request channel not 45 preempted 46 precedence call blocked

available
47 resources unavailable 49 quality of service available 50 requested facility not

subscribed
51 reverse charging not allowed 52* outgoing calls barred 53 outgoing calls barred
within CUG
54* incoming calls barred 55 incoming calls barred within 56 call waiting not
CUG (Closed User Group) subscribed
57 BCCOS not authorized 58 BCCOS not available 63 service or option not

available
65 BCCOS not implemented 66 channel not implemented 67 transit network selection

not implemented
68 message not implemented 69 facility not implemented 70 restricted digital

information
79 service/option not 81 invalid call reference 82 channel does not exist

implemented
83 suspect call exist already 84 call identity in use 85 no call suspended
86 call having required identity 87 called user not member 88 incompatible destination
cleared CUG (Closed User Group) or CODEC Match Failure
89 non existent abbreviated 90 destination address missing 91 invalid transit

address
92 invalid facility parameter 93 mandatory information 95 invalid message

element is missing unspecified
96 mandatory IE (Information 97 nonexistent message 98 wrong message

Element) missing
99 bad information element 100 invalid element contents 101 wrong message for state
102 timer expiry 103 mandatory IE (Information 111 protocol error

Element) len error
112 type of protocol not available 113 ISUP (ISDN User Part) not 127 interworking unspecified
available
181 Fail on E911 calls 182 Fail in Wait for Ready State 183 Fail in Dial
(fail to receive
acknowledgment for trunk
seizure)
184 Glare Fail (collision of two 250 setup_on_line_down 252 setup on existing call id
simultaneous calls in reverse
directions)
253 setup in unexpected state 254 restart error disconnect
* Do not define these Causes as “Block Override” in a Coral Network
15-33
The causes should be sorted into one of the parameters listed in this branch as
needed. Each cause can be associated with either the DIAL SERVICE [2] or TRUNK
[3] parameter in this branch, but not to both. Adding a cause to the Trunk or Dial
Service parameter automatically removes it from the previous parameter. However,
a cause number can simultaneously reside in either the Trunk or Dial Service
parameter as well as in the Block Override [4] parameter so that the LAR
mechanism can avoid a faulty route, yet not block it completely.
General Recommendations when sorting Cause numbers in parameter fields:
• Any cause that is Route related or related to a specific channel should be placed
in the DIAL SERVICE [2] parameter list.
• Any cause that is related to trunks should be placed in the TRUNK [3] parameter
list.
• Causes that are related to the end user or end device should not be placed in
any parameter list.
• If the cause text is unclear or ambiguous it should not be placed in any
parameter list.
• Whenever there is a doubt regarding the behavior of one of the causes put in
the Trunk or Dial Service list, it is recommended to also put the particular cause
number in the Block Override [4] parameter list in order to avoid undesired
blocking.
FROM SET # 0..3

TO SET # 0..3
Enter the required LAR Trigger Set number to be updated or displayed FROM the
lowest set number TO the highest.
Defaults per LAR SET:

SET 0: public_network
SET1: private_qsig_net
SET 2: ip_net
SET 3: analog_trunks
Define the name (up to 16 alphanumeric characters) for this set of IDSN/QSIG
causes that trigger LAR routing and blocking mechanisms on the failed call
attempt. Each set is associated with a specific network. The name should refer to
the type of Network it is to be implemented upon, i.e. Public, Private, IP or Analog
Network.
By default, Set # 0 relates to the Public Network, Set # 1 to Private QSIG networks,
Set # 2 to IP networks and Set # 3 to analog networks.
A name defined as BLANK displays only the cause number/s.
Use “_” (underscore) for space. See General Rules for Entering Names on page
2-10.
15-34
DIAL SERVICE [2] Any ISDN/QSIG cause number (see Table 15-3) or
None (enter R to remove numbers)

SET 0:
(41,47,49,50,57,58,63,81,82,99,102,250,252,253,254)
SET1: (3,27,49,50,52,54,63,65,69,70,99)
SET 2: (28,42,49)
SET 3: ()
 LAR blocking cannot be activated on a Dial Service dialed directly by the

user.
Enter cause numbers in this field that are clearly associated with a failed route or
faulty D-channel.
For P-335, P-450, T207M, T208M, T207M/NP, T208M/BL and FlexSet-IP 280S
Survivability, add the cause “1” (telephone in undefined state) in the LAR Set used
for IP stations.
If a call attempt fails with a “cause” defined in this field, the LAR reroutes the call
to the next available Dial Service.
Enter cause numbers under the display line:
• within parentheses
• in ascending order
• separated by a space or comma.
To Add Number(s):
Enter “A,” followed by the cause numbers: (A, number1, number 2,...)

To Remove Number(s):
Enter “R,” followed by the cause numbers: (R, number1, number 2,...)
To Remove All Numbers:
Enter empty parentheses: ()
15-35
TRUNK [3] Any ISDN/QSIG cause number (see Table 15-3) or


SET 0: (6,44,98)
SET1: (6,42,44,98)
SET 2: (98)
SET 3: (181,182,183,184)
 LAR blocking cannot be activated on a trunk dialed directly by the user.

Enter cause numbers in this parameter that are clearly associated with a failed
trunk.
If a call attempt fails with a “cause” defined in this field, the LAR reroutes the call
to the next available trunk.
To Add Number(s):
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l ]
15-36
Block Override [4] Any ISDN/QSIG cause number (see Table 15-3) or

SET 0: (47,49,50,57,58,63,81,82,98,99,250,252,253,254)
SET1: (2,42,49,50,52,54,63,65,69,70,98,99)
SET 2: (28,42,49,98)
SET 3: (184)
Enter cause numbers in this parameter that should not cause any LAR blocking on
the trunks and Dial Services.
If the call attempt fails with a cause entered in this parameter, the LAR mechanism
is not triggered. Causes that clearly indicate that the failure is final (e.g. User Busy)
should be entered into this parameter.
Also, enter the cause numbers that are not clearly Dial Service or Trunk related
problems in this parameter in order to avoid unnecessary blocking.
To Add Number(s):

l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l ]
15-37
Cost Calculation Elements ç COST,0 [ROOT,4,1,0]
Cost Calculation Elements are used for call billing purposes based on the Routing
services and the time that the call is initiated. There are some Cost Calculation
Elements, one of which is assigned to each entry in the Cost Calculation
Numbering Plan (see Cost Calculation Numbering Plan, in this chapter). Within
each Cost Calculation Element, a distinct set of costs: Day initial and additional,
Evening initial and additional and Night initial and additional price; can be
assigned for each of the Dial Services (defined in Routing - Dial Services, in this
chapter) which can be used to operate the call.
 During Weekend or Holidays, as defined in Chapter 12, the charge is

determined by “Night” INITIAL_PRICE & ADDITIONAL_PRICE [COST,0].
FROM/TO COST# 0 to maximum defined in Sizes - Chapter 4

All
Enter the required COST ELEMENT numbers FROM the lowest number TO the
highest number.
FROM/TO DIAL_ Any valid system Dial Service number (defined in General Numbering Plan,
SERVICE# DIAL_SERV [36] (page 5-44))
All
Enter the required Routing DIAL_SERVICE numbers FROM the lowest number
TO the highest number.
DAY:
Cost Calculation Elements COST,0 [ROOT,4,1,0]
FROM 00:00..23:59
This is start time for the DAY calling period (e.g., 8 AM). This option is also the
ending time for the NIGHT calling period. The time is denoted in a 24-hour format.
INITIAL_PRICE 0..65534 (1 unit = $0.01, i.e. 1 U.S. cent)

Enter the charge for the initial call period (e.g., the first 3 minutes) of the call. Call
charges are made in 10 cent increments ($0.10). Entries are made without decimals
or commas: for $1.50, the entry is 150. The INITIAL PERIOD is defined in Cost
Calculation Parameters (COST,2).
15-38
ADDITIONAL_PRICE 0..65534 (1 unit = $0.01/minute)

This is the charge accrued for each additional call minute after the end of INITIAL_
PRICE (above). Calls are charged in 10 cent increments ($0.10). Entries are made
without a decimal; i.e.: for $1.50, the entry is 150.
EVEN:
FROM 00:00..23:59
This is the start time for the EVENING calling period (for example, 5PM). It also
serves as the DAY calling period end time. The time is denoted in a 24 hour format.

Same as INITIAL_PRICE for DAY, but for the evening period.

Same as ADDITIONAL_ PRICE for DAY, but for the evening period.
NIGHT:
FROM 00:00..23:59
This is the start time for the NIGHT calling period (for example, 11PM). It also
serves as the EVENING end time. The time is denoted in a 24 hour format. For an
explanation of programming and entering the time units, see Programming and
Cost Calculation Elements COST,0 [ROOT,4,1,0]

Entering Time Units on page 2-6.

Same as INITIAL_PRICE for DAY, but for the NIGHT, WEEKEND and HOLIDAY
periods.

Same as ADDITIONAL_PRICE for DAY, but for the NIGHT, WEEKEND and
HOLIDAY periods.
15-39
Cost Calculation Numbering Plan ç COST,1 [ROOT,4,1,1]
Cost Calculation Numbering Plan assigns number pattern entries to one of 50 Cost
Calculation Elements (see Cost Calculation Elements, in this chapter). Numbers not
defined in the Cost Calculation Numbering Plan are charged according to the
Default Cost defined in the Cost Calculation Parameters, in this chapter. Number
pattern entries for Cost Calculation must always be entered from most specific to
least specific.
 Program Cost Calculation Numbering Plan entries from the specific to

the general; for example, first enter 1804555, then enter 1804, then 1NPX,
etc.
 Successful addition of a new Numbering Plan entry always results in the

message: ** NUMBERS ADDED**.
FROM Any sequence of up to 32 digits: 0-9, N (2-9), P (0,1), X (0-9)

Enter the LOWER number pattern of a range to be assigned to a Cost Element. As
many as 32 digits may be entered.
TO Any sequence of up to 32 digits: 0-9, N (2-9), P (0,1), X (0-9)

According to FROM, above
Enter the HIGHER number pattern of a range to be assigned to a Cost Element. If
N, P, or X was entered in FROM, this prompt does not appear. As many as 32 digits
Cost Calculation Numbering Plan COST,1 [ROOT,4,1,1]
may be entered.
COST# 0..49
Enter the Cost Element number (see Cost Calculation Elements beginning on page
15-38) required to calculate charges for calls matching the number pattern defined
above.
15-40
Cost Calculation Parameters ç COST,2 [ROOT,4,1,2]
Cost Calculation defines the initial Cost Calculation charge period and the default
cost of calls that do not match an entry in the Cost Calculation Numbering Plan, in
this chapter.
Elapsed time for cost calculation purposes is determined by the SMDR_FREE_
CHARGE parameter as defined in SMDR Control, Chapter 14.
INITIAL PERIOD 0..3..255 minutes

Determines the length of the initial period (generally the first minute) for which the
INITIAL COST entry in the appropriate Cost Element is charged.
DEFAULT COST 0..49

When a dialed number is not found in Cost Calculation Numbering Plan beginning
on page 15-40, then the call is charged according to the Default Cost Calculation
elements. Typically, the default cost is used for local calls which are neither time
nor distance sensitive.
Cost Calculation Parameters COST,2 [ROOT,4,1,2]
15-41
Cost Calculation Parameters COST,2 [ROOT,4,1,2]
15-42
16 Room Status/
User Canned Messages
This chapter contains programming instructions for operating the Room Status and
User Canned Messages features, and instructions for displaying the Room Status
port status.
The Room Status features are mainly applicable for Hotel and Motel use and allow
assigning various operational states to room telephones. The status definition
(name) can be assigned as required. Room status may be set and viewed either
through the PI system’s service terminal or through the attendant station
(depending on its Class Of Service). Room Status allows naming, selecting and
using the status of rooms assigned to each definable Room Status.
The Room Status branch presents five options and routes, as follows:
Room Status Option Route Root Page Number

Names — 0,3,0 16-3
Status/Message Select — 0,3,1 16-5
Status/Message Display — 0,3,2 16-6
Busy Display BUSY 0,3,3 16-7
Terminal MSG, 1 0,8,1 16-8
Because User Canned messages is based on the Room Status feature, the Room
Status Name remains the canned text message. These names/messages are assigned
system-wide. Therefore, the Room Status feature and the Canned Messages feature
are mutually exclusive, and cannot be activated simultaneously in the same Coral
system. See the Feature Authorization branch (FEAT,1,HOTEL/MOTEL (page 3-20)
and CANNED MESSAGE (page 3-25)) to determine which feature is available in your
system.
While the Room Status feature enables activating up to 16 different Room Status
messages/names concurrently, the User Canned Messages feature enables
activating only one message per station at any time.
The Canned Messages feature enables defining text messages of up to 16
alphanumeric characters in the Coral, as opposed to Room Status messages that are
limited to only 10 characters. The station user can choose to display any one of
these 16 pre-programmed system canned text messages, on the internal calling
party’s keyset, until the call is answered.
 Although more than one Canned message can be “turned-on” for any
single station, the canned message with the lowest index number is shown
to the internal caller.
16-1
Room Status/ User Canned Messages PI Reference Manual
Relevant parameters for the Room Status feature:

• Feature Authorization HOTEL/MOTEL (page 3-20)
• System Features USER_CANNED_MESSAGES [21] (page 6-25)
• User COS ROOM_STATUS [8] (page 7-5)
• Attendant COS ROOM_STATUS [18] (page 7-37)
• Feature Access Codes (NPL) Room Status / Canned Messages (page 5-33)
Relevant parameters for the User Canned messages feature:

• Feature Authorization CANNED MESSAGE (page 3-25)
• System Features USER_CANNED_MESSAGES [21] (page 6-25)
• System Features USER_CANNED_MESSAGES_OVERRIDE_2nd_LINE
[22] (page 6-25)
• User COS ROOM_STATUS [8] (page 7-5)
• Attendant COS ROOM_STATUS [18] (page 7-37)
• ACD/UCD Hunt Group USER_CANNED_MESSAGE# (page 10-9)
• Boss Group USER_CANNED_MESSAGE# (page 10-20)
• Public Library USER_CANNED_MESSAGE# (page 11-3)
• Wait Que USER_CANNED_MESSAGE# [9] (page 27-18)
• Feature Access Codes (NPL) Room Status / Canned Messages (page 5-33)
16-2
PI Reference Manual Room Status/ User Canned Messages
Names ç 0,3,0
Names is used to define the text of each Room Status (or Canned Messages)
selection, from Status 0 to Status 15 (16 names or text messages). Rules for
entering names are as follows:
FROM STATUS # 0..15

TO STATUS # 0..15
Enter the Room Status number(s) required for update/display name FROM the
lowest number to the highest.
NAME - Up to 10 alphanumeric characters - Room Status feature

Up to 16 alphanumeric characters - User Canned Messages feature
R (Remove for Blank);
Status ## (## = 00-15)
Define the name or canned text message for this Status number.
The name length may be:
• 10 characters long for the Room Status feature (USER_CANNED_MESSAGES
[21] (page 6-25) set to No)
• 16 characters long when Room Status# is used for the Canned Messages
feature (USER_CANNED_MESSAGES [21] (page 6-25) set to Yes).
 Changing USER_CANNED_MESSAGES [21] (page 6-25) from Y to N
truncates this name to 10 characters. The extra characters are lost if and
when returning the User Canned Message definition to Y at a later time.
See General Rules for Entering Names on page 2-10, for general naming rules. A
Room Status Name defined as BLANK displays only the dial number on the
keyset.
Use Table 16-1 on page 16-4 to list the room status names or the canned messages
Names 0,3,0
texts for reference.
16-3
Table 16-1: Room Status / Canned Message - Names and Access Codes
STATUS User * Attendant † NAME

# Access Codes Access Code Up to 10 characters long for the Room Status feature
Up to 16 characters long for the Canned Messages feature
Index Default Index Default
0 126 7026 110 7010
71 127 7027 111 7011
72 128 7028 112 7012
73 129 7029 113 7013
74 130 7030 114 7014
75 131 7031 115 7015
76 132 7032 116 7016
77 133 7033 117 7017
78 134 7034 118 7018
79 135 7035 119 7019
80 136 7036 120 7020
81 137 7037 121 7021
82 138 7038 122 7022
83 139 7039 123 7023
84 140 7040 124 7024
85 141 7041 125 7025
* See Feature Access Codes (NPL) Room Status / Canned Messages: SLT (page 5-33)
† See Feature Access Codes (NPL) Room Status / Canned Messages: ATT (page 5-33)
Names 0,3,0
16-4
Status/Message Select ç 0,3,1

Select a Room Status to be viewed (by station numbers) in the next branch (next
entry on menu: Root 0,3,2).
STATUS/MESSAGE # - 0..15
Select the Room Status # (or the canned message) to be viewed. Room Status and
Canned messages are mutually exclusive and cannot be used concurrently.
The name for this option # is given in Names (page 16-3).
Canned Messages selection for non stations:

Refer to the following parameters to define the number of the Canned Message
(0 to 15) that is displayed to users calling ACD/UCD groups, Boss Groups, Public
library and Wait Ques not yet answered.
• ACD/UCD Hunt Group USER_CANNED_MESSAGE# (page 10-9)
• Boss Group USER_CANNED_MESSAGE# (page 10-20)
• Public Library USER_CANNED_MESSAGE# (page 11-3)
• Wait Que USER_CANNED_MESSAGE# [9] (page 27-18)
Status/Message Select 0,3,1
16-5
Status_Display/Message ç 0,3,2
FROM/TO DIAL # Any station dial number;

All system stations
Enter the range of station dial numbers for status display purposes.
 Press [CTRL-C] to exit from the status display screen.

STATUS DISP Assign (Yes), Deassigned (Blank), Undefined (U);

None
Displays the requested range of stations listed by dial number as: Assigned (Y),
Deassigned (blank), or Undefined (U), only for the Room Status# chosen in
STATUS/MESSAGE # - (page 16-5).
Yes: ASSIGNED: Station is defined with this STATUS/MESSAGE # - message.
Blank: DEASSIGNED: STATUS/MESSAGE # - message has been removed (i.e.
Room Status# LED is turned off) for the station.
U: UNDEFINED: Keyset is disconnected.
Status_Display/Message 0,3,2
16-6
Busy Display ç BUSY [0,3,3]
FROM/TO DIAL # - Any system port;

All system ports
Enter the range of dial numbers (typically Keyset, SLT, WST, trunk dial #) for
“Busy” status display purposes.
 Press [CTRL-C] to exit from the status display screen.

BUSY DISPLAY Busy (Yes), Idle (Blank), Undefined (U);

None
Displays a designated range of ports by dial number as: Busy (Y), Idle (Blank), or
Undefined (U). Generally used for maintenance purposes.
Busy Display BUSY [0,3,3]
16-7
Terminal ç MSG,0 [0,8,0]
Room Status Terminal is used to determine which RS-232 data port (on RMI,
8DRCM-2, 8DRCM or 8DRCF card) is defined as a Room Status Terminal. Once
defined, only the Room Status/User Canned Messages feature is displayed through
this port and other PI system functions are not possible.
The defined port can be returned to a regular PI system port only when defined
from another terminal or KB0.
TERM # None, 1..24 (see Table 17-1 on page 17-11)

Enter the port number which should be defined as Room Status/User Canned
Messages Terminal.
active in your system (see CNCM (page 27-5)) in MAP branch).
The system returns the last port number not yet used.
Terminal MSG,0 [0,8,0]
16-8
17 Service Terminals
This chapter contains programming instructions for Program Interface (PI)

passwords, PI Data Terminal Port and Data Modem definition.
Password and Site Name ............................................................................17-2
Message Control .........................................................................................17-4
Message Select ...........................................................................................17-6
Terminal Destination ..................................................................................17-8
CoralVIEW Traffic (CVT) Terminal Destination ......................................17-9
Call Trace..................................................................................................17-10
Terminal Setup.......................................................................................... 17-11
KB0 Setup Through Attendant Console - Feature...................................17-29
Terminal Reset ..........................................................................................17-30
Terminal Clear ..........................................................................................17-31
iVMF Remote Maintenance .....................................................................17-32
17-1
Service Terminals PI Reference Manual
Password and Site Name ç 0,0,3

The Password menu is used to define the site name and password entries to various
privilege levels. Password provides restrictions for system servicing and customer
naming. Four levels of service passwords are available, with each level having its
own menu access privileges.
When viewing these parameters, the current system Password Level is displayed
as 16 asterisks in place of Password Level of the user that accessed the system.
Only Password Levels lower than the current one are displayed.
SITE NAME for 1 to 20 printable ASCII characters,

KEYSET for SPACE insert underscore: “_”,
for No Display: enter one underscore: “_”;
Identifies the 20 character, alphanumeric, site or installation message. This
message may appear on all the keysets (equipped with display type of 40 characters
per each line, e.g. FlexSet 280D, 280D-Z, 280S, 281S, 80S, 80P, and
FlexSet-IP 280S), when the Idle Display feature is activated. The defined message
is displayed on the first display line to the right of the date display.
 This option is not available for Wireless telephones.

SITE NAME for PI 1 to 9 printable ASCII characters,

for SPACE insert underscore: “_”,
for No Display: enter one underscore: “_”;
TADIRAN
Identifies the 9 character, alphanumeric, site or installation name. This name
appears on the PI terminal device each time the system is accessed at the Root
menu of the PI or when [CTRL-T] is pressed.
Password and Site Name 0,0,3
LEVEL 0 1 to 16 printable ASCII characters

OPERATOR (Coral IPx/FlexiCom systems)
M20ICH02L (Coral Wave Gateway systems)
This is the Lowest Level Password, typically the Operator level password. The
Level 0 password user can change the Level 0 password. In addition, a user with a
Level 0 password may view all system parameters accessible to Level 2 password
users. However, access and changes are allowed for a restricted number of options
such as: Room Status, Features, Libraries and Time/Date (ADMIN).
17-2
PI Reference Manual Service Terminals

SUPER (Coral IPx/FlexiCom systems)
Y11AE05L (Coral Wave Gateway systems)
Password Level 1 is typically assigned to the supervisor. The Level 1 password
user can change Level 0 and Level 1 passwords. Allows access to all the Level 0
lists, plus the Administration features: Groups, PROG.

Confidential (for manufacturer’s personnel only)
Password Level 2 is typically assigned to the maintenance center. The password
Level 2 user can change passwords for Levels 0, 1 and 2. Password level 2 allows
access to all Level 1 lists plus: PI system messages, system configuration, system
sizing, first initialization and system backup.
LEVEL 3 Confidential: For manufacturer’s internal use only.

Password and Site Name 0,0,3
17-3
Message Control ç MSG,2,0 [0,8,2,0]
For Manufacturer’s Use Only. Do not change.

Message Control determines which messages are displayed by the Coral system at
the Program Interface service terminal unit. Contact the manufacturer for
parameter information.
STIMUL Yes/No
 Set this parameter to No, from anywhere within the PI system by entering
[CTRL] - V.
STIMULUS displays or hides control messages between the
MCP-IPx2/MEX-IP2/MCP-ATS and the HDC/4GC/16GC/32GC and peripheral
cards. This option is a master control for the following four EXTENDED PROTOCOL
options and the Message Select options beginning on page 17-6.
EXTENDED  The following 4 fields are relevant only when STIMUL above is set to Yes.
PROTOCOL
SIMPLE_FORM Yes/No
Displays or hides the logical message. A logical message can be one of three types:
a single HDLC message, HDLC message with additional messages, or a number of
HDLC messages used in order to give the technician clearer information.
EXTENDED_FORM Yes/No
Displays or hides the HDLC control messages. The extended form is known as the
physical layer.
Message Control MSG,2,0 [0,8,2,0]
TWN_FORM Yes/No
Displays or hides the TELENETWORK message.
Q931_TAIL_FORM Yes/No
Displays or hides the tail of the Q931 protocol. An ISDN message is composed of
the TWN_FORM and the original part of the Q931 message as the tail end. This
parameter determines how the tail part of the ISDN message is displayed.
ALARMS Yes/No
Displays (Yes) or hides (N) alarm information provided by the system's on-line
diagnostic procedures.
17-4
DEBUG Yes/No
Displays the current internal hardware diagnostics test status, that is, the number of
tests in-progress and the hardware being tested (shelf, slot, circuit).
DI.COR Yes/No
Corrective Diagnostics displays or hides corrective diagnostic messages as they
occur.
EXCEPT Yes/No
Exceptions displays or hides exception diagnostic messages as they occur. These
messages indicate an unusual but temporary situation and do not designate any
system malfunction.
FAILURE REPORT Yes/No

Set this parameter to Yes to enable error message to be sent to the Coral Fault
Manager (CFM) application via the designated KBn port or MAP card.
When this parameter is set to Yes, only binary diagnostic information can be sent
via the KBn defined in DIAG (page 17-8) from the Terminal Destination branch.
 Coral ASCII information for alarms and diagnostics cannot be sent via the
same KBn. Therefore, no alarm messages will be printed to the terminal
when this parameter is set to Yes, even if ALARMS, in this branch, is set to
Yes.
Message Control MSG,2,0 [0,8,2,0]
17-5
Message Select ç MSG,2,1 [0,8,2,1]

Message Select is used to determine which Coral system Stimulus messages are
displayed. STIMUL must be set to Y (Yes) in Message Control, (see page 17-4).
Contact the manufacturer for parameter information.
Rules for Entering Ranges in this Branch
One of the following Logical Include Codes must be entered at the beginning of
the string, otherwise, the first number is interpreted as a logical statement.
Code Description
0 Include all items, except the ones listed in

parentheses.
1 Include only the items listed in parentheses.
2 Include all items available in the system.

Slot number(s) not required when “2” is selected.
a Add the following items to the list.
r remove the following items from the list.
... Delete all the items from the list.
Examples:
The system has 8 slots installed.
Enter (0, 2,3,4) to add all slots except 2, 3, and 4
The list now includes slots: (0, 1, 5, 6, 7)
To add slot 3, enter (a 3)
The list now includes slots: (0, 1, 3, 5, 6, 7)
Message Select MSG,2,1 [0,8,2,1]
To list all the slots enter (2)

To remove all the slots from the list, enter (...).
The list is now empty.
SHELF - (0,0,..,15)/(1,0,..,15)/All shelves (2)

Enter the logical code required and then enter the shelf numbers to be checked (in
parentheses, with each number separated by a comma) on the same line.
Example: When the first 3 shelves are required, enter (1,0,1,2)
SLOTS (0,1,..,18)/(1,1..,18)/All slots (2)

Define card slot number/s on the shelf required for monitoring.
Enter the logical code required and then enter the slot numbers to be checked (in
17-6
 The group control card (SVC, 32GC) for STIMULUS MESSAGES must be
defined as Slot 0.
CKTS (0,0,..,31)/ (1,0,..,31)/All circuits (2)

Define the CKT (circuit) numbers required for monitoring.
Enter the logical code required and then enter the circuit numbers to be checked (in
PORTS (0,0,..,# of ports installed)/ (1,0,..,# of ports installed)/All ports (2)

Enter the Port numbers required for monitoring.
Enter the logical code required and then enter the port numbers to be checked (in
Alternatively, the port dial number can be used with the “e” suffix (e.g. port number
23 may have dial number 1234. Enter 1234e as the port number to monitor this
port).
When a Port number is defined, then a Shelf, Slot and Circuit number need not be
defined.
CODES UP see COM.DOC files;

All messages except D4H and 80H (0H, D4H, 80H)
Define the set of codes required for checking HDLC messages from the peripheral
cards to the Main Switch. Only messages with OPCODE from the CODES UP set
are output.
CODES DOWN see COM.DOC files;

All messages except 1H (0H, 1H)
Message Select MSG,2,1 [0,8,2,1]

Define the set of codes required for checking HDLC messages from the peripheral
cards to the Main Switch. Only messages with OPCODE from the CODES DOWN
set are output.
SW_UP Yes (Show Switch Up Messages)/No (No Messages)

Show HDLC messages from the peripheral cards to the Main Switch.
SW_DN Yes (Show Switch Down Messages) /No (No Messages)

Show HDLC message from the Main Switch to the peripheral cards.
TIME Yes/No
Allows printing the time and date of control messages. Time is printed according
to the format defined in SFE, DATE_MODE (Eu/USA) [16] on page 6-24.
17-7
Terminal Destination ç MSG,2,2 [0,8,2,2]

Terminal Destination is used to set the system destination (IP port, Serial RS-232
or Modem port) for Program Interface (PI) Stimulus and Diagnostics messages.
Contact the manufacturer for parameter information.
STIMU 0(KB0),
1..24 for Serial RS-232 or Modem port (see Table 17-2 on page 17-11),
 This parameter is only relevant when STIMUL on page 17-4, is requested

and set to Yes.
It determines the output terminal number to which the selected stimuli messages
(see Message Select beginning on page 17-6) are sent.
active in your system (see CNCM (page 27-5) in MAP branch).
DIAG 0(KB0),
1..24 for Serial RS-232 or Modem port (see Table 17-2 on page 17-11),
 This parameter is only relevant when one or more of the following

parameters (starting on page 17-4) is requested and set to Yes:
Terminal Destination MSG,2,2 [0,8,2,2]
ALARMS, DEBUG, DI.COR, EXCEPT, or FAILURE REPORT.

Diagnostics determines the output terminal number to which the requested
ALARMS, DEBUG, DI.COR, EXCEPT, and FAILURE REPORT (see Message Control
beginning on page 17-4) are sent.
17-8
CoralVIEW Traffic (CVT) Terminal Destination ç ROOT,3,5

Authorization Limit
 This branch is irrelevant for the Internal Traffic feature.
This branch is used to determine which RS-232 data terminal of the 8DRCF,
8DRCM-2, 8DRCM or RMI card is defined as a CoralVIEW Traffic (CVT) Report
terminal.
The CVT system provides the Coral system with the ability to accumulate and
report on the system’s port traffic. The information may be used for periodic checks
on system load and for trunking decisions. The traffic report presents data for the
following connection types:
• Stations to External line
• Station to Station
• Trunk Calls: Incoming/Outgoing
TRAFFIC_TERM# None,
1..24 for Serial or Modem port (see Table 17-2 on page 17-11)
Determines the output terminal destination for the Traffic report.
CoralVIEW Traffic (CVT) Terminal Destination ROOT,3,5

17-9
Call Trace ç ROOT,3,6

Authorization Limit
This branch defines the terminal destination for the Malicious Call Trace Option.
CALL TRACE None,

TERMINAL 1..24 for Serial or Modem port (see Table 17-2 on page 17-11)
Determines the output terminal destination for printing the Malicious Call Trace
reports. Station/Attendant reports are sent by dialing the appropriate print code
(#1741- Station reports, #1743-Attendant reports), see Chapter 5. An example of a
typical Call Trace Report is shown below.
MALICIOUS CALL TRACE: PRINT FORMAT
CALLER CALLED DATE TIME
039231204 1114 29/12/07 08:20:12
7100 1114 29/12/07 09:15:32
1115 1114 29/12/07 08:37:03
8135230279 1114 29/12/07 08:59:45
Call Trace ROOT,3,6
17-10
Terminal Setup ç TERM,0 [0,8,0,0]
Terminal Setup is used to define the RS-232 data interface ports, as well as the
Modem used for remote maintenance and MAP (via TELNET). In addition, KB0
can be setup directly from the Attendant Console (see KB0 Setup Through Attendant
Console - Feature on page 17-29 for terminal setup procedure from the Attendant
Console).
The Terminal Setup for different systems is shown below.
Table 17-1: KB0 Terminal # 0
*
Coral System Type Terminal #
Serial RS-232 Modem
0 (KB0) 1 2 3 4
(Figure 17-1)
IPx Office (Figure 17-2) l Front panel — — —
l MCP-IPx2 l l l ‡
IPx 500 and CDRS 200E (Figure 17-3)
 LIU (TELNET)
IPx 800, 3000 (Figure 17-5) l MEX-IP2    

FlexiCom 400 (with HDC controller) (Figure 17-7)  LIU (TELNET)
FlexiCom 5000 (Figure 17-8)
IPx 4000 (Figure 17-6) l MCP-ATS    

FlexiCom 6000 (Figure 17-9),
* l Standard,  Optional (field upgrade). Requires: 8DRCF, 8DRCM-2, 8DRCM or RMI card
 Optional (field upgrade). Requires: 8DRCF, 8DRCM or RMI card (check availability)
† IPx Office modem requires U-RMI Office or RMI Office card (check availability)
‡ IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not include a MODEM. The modem was standard in
MSBipx Hardware Issue-0220X1003 or lower.
Table 17-2: RMI Terminal # 1-24
Terminal Setup TERM,0 [0,8,0,0]

8DRCF, 8DRCM-2, 8DRCM or RMI card order Terminal #
IPx 500, IPx 800, 3000, 4000, Office Serial Modem*

CDRS 200E FlexiCom 400 (with HDC controller), RS-232
5000, 6000
Built-in (Auxiliary Connector) First card 1 2 3 4
First card Second card 5 6 7 8
Second card Third card 9 10 11 12
Third card Fourth card 13 14 15 16
Fourth card Fifth card 17 18 19 20
Fifth card Sixth card 21 22 23 24
17-11
* 8DRCM-2 and CDRS 200E do not include a MODEM.

IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not include a MODEM. The modem was standard in
MSBipx Hardware Issue-0220X1003 or lower.
Table 17-3: MAP1 Terminal # 1-28
Number of cards defined in SIZ Terminal #

definition (on page 4-15) in
8DRCF/8DRCM/RMI/ ASU parameter
0 1 2 3 4
1 5 6 7 8
2 9 10 11 12
3 13 14 15 16
4 17 18 19 20
5 21 22 23 24
6 25 26 27 28
Terminal # for the MAP (CNCM) PI application is dependant on the sizes capacity
of U-RMI/U-MR/RMI/MR Office, 8DRCF, 8DRCM-2, 8DRCM, RMI and ASU
cards (and MSBipx in the Coral IPx 500 and CDRS 200E). The terminal numbers#
for the MAP is calculated as:
4 times the number defined in 8DRCF/8DRCM/RMI/ ASU parameter +1, +2, +3, +4.
[(4 X 8DRCF/8DRCM/RMI/ ASU) +1, +2, +3, +4] = see Table 17-3
 The MAP card is not available in Coral IPx 4000 and FlexiCom 6000
systems.
1. MAP is not applicable for IPx 4000 and FlexiCom 6000 systems
17-12
Figure 17-1. Control

Cards- MEX-IP2
MEX-IP2
Front Panel M
C
P
-
I
P
x
2
Option
Option Switches
Switches
Set DIP Switch# 1
KB0 to the Right for
KB0
KB0 Connections
Reset
Reset
RESET
IMC-4/8
FMsl IMC-8 /16
Release
Button
IMC-4/8
Release Button IMC-8/16
KB0
RS-232 E
Set DIP Switch# 1

to the Right for LAN LAN
KB0 Connections
KB0
SAU SAU
Reset
Indicator
Lights
HS
MCP-IPx2 MEX-IP2 MCP-ATS
Coral IPx 500 Coral IPx 800, 3000 Coral IPx 4000
FlexiCom 200 FlexiCom 300, 400V, 400, 5000 FlexiCom 6000
CDRS 200, 200E
Coral IPx Office

CPU
UGW
GC
FAN
MAINT.
MRC
GC ACT.
POWER
COM RESET
SYS.
MEMORY DISK RESET
1 3 5 7
IMC-x IMC-x KB0 RESET

Release
Button
17-13
Figure 17-2.
Coral IPx Office IPx 800X Expansion Cage
Terminal # 4th 5th
8DRCM-2, 8DRCM-2,
8DRCM, 8DRCM,
8DRCF, 8DRCF,
or RMI or RMI
17 = PORT 1 21 = PORT 1
18 = PORT 2 22 = PORT 2
19 = PORT 3 23 = PORT 3
20 = MODEM 24 = MODEM
IPx 800X Expansion Cage

1th
8DRCM-2,
8DRCM,
8DRCF,
or RMI
5 = PORT 1
6 = PORT 2
7 = PORT 3
8 = MODEM
Coral IPx Office Main Unit

CPU
UGW
GC
FAN
MAINT.
MRC
GC ACT.
POWER
COM RESET
SYS.
MEMORY DISK RESET
1 3 5 7
0 = KB0
4 = MODEM (U-RMI Office or RMI Office)
Coral IPx 800X

2nd Expansion
Coral IPx 800X

1st Expansion
Coral IPx Office Main Unit
17-14
Figure 17-3.
Coral IPx 500 and IPx 800X Expansion Cage
CDRS 200E 4th 5th
8DRCM-2, 8DRCM-2,
Terminal # 8DRCM,
8DRCM,
8DRCF, 8DRCF,
or RMI or RMI
17 = PORT 1 21 = PORT 1
18 = PORT 2 22 = PORT 2
19 = PORT 3 23 = PORT 3
IPx 800X Expansion Cage

1th
8DRCM-2,
8DRCM,
8DRCF,
or RMI
5 = PORT 1
6 = PORT 2
7 = PORT 3
8 = MODEM
M
C
P
-
IP
x
Coral IPx 500M Main Unit
4 = Built-in Modem
(only on MSBipx
issue ??? And lower)
Auxiliary
Connector
1 = KB1 0 = KB0
2 = KB2
3 = KB3 MCP-IPx2

Coral IPx 800X
2nd expansion
Coral IPx 800X

1st expansion
Coral IPx 500M

Main Cage
17-15
Figure 17-4.
Coral
IPx 800 (with HDC 4th 5th
controller) 8DRCM-2, 8DRCM-2,
Terminal # 8DRCM, 8DRCM,
8DRCF, 8DRCF,
or RMI or RMI
13 = PORT 1 17 = PORT 1
14 = PORT 2 18 = PORT 2
15 = PORT 3 19 = PORT 3
6th
8DRCM-2,
8DRCM,
8DRCF,
or RMI
21 = PORT 1
22 = PORT 2
23 = PORT 3
24 = MODEM
MEX-IP
1st
8DRCM-2,
8DRCM, Coral
8DRCF, IPx 800M
or RMI Main Cage
SAU
1 = PORT 1 MEX-IP2
INT
RST
2 = PORT 2
0 = KB0
RS-232E
3 = PORT 3
4 = MODEM
IPx 800
system
3 cages
in rack
17-16
Figure 17-5.
Coral
IPx 3000 (with 4GC 4th 5th
controller) 8DRCM-2, 8DRCM-2,
8DRCF, 8DRCF,
or RMI or RMI
13 = PORT 1 17 = PORT 1
14 = PORT 2 18 = PORT 2
15 = PORT 3 19 = PORT 3
6th
8DRCM-2,
8DRCM,
8DRCF,
or RMI
21 = PORT 1
22 = PORT 2
23 = PORT 3
24 = MODEM
MEX-IP
1st
8DRCM-2,
8DRCM, Coral IPx 3000M
8DRCF, Main Cage
or RMI
MEX-IP2 SAU
1 = PORT 1 INT
RST
2 = PORT 2
0 = KB0
RS-232E
3 = PORT 3
4 = MODEM
IPx 3000
system
8 cages
in racks
17-17
Figure 17-6.
Coral
IPx 4000 4th 5th
Terminal # 8DRCM-2, 8DRCM-2,
8DRCM, 8DRCM,
8DRCF, 8DRCF,
or RMI or RMI
13 = PORT 1 17 = PORT 1
14 = PORT 2 18 = PORT 2
15 = PORT 3 19 = PORT 3
1st
8DRCM-2, 6th
8DRCM, 8DRCM-2,
8DRCF, 8DRCM,
or RMI 8DRCF,
or RMI
1 = PORT 1
2 = PORT 2 21 = PORT 1
22 = PORT 2
3 = PORT 3 23 = PORT 3
0 = KB0
Coral IPx 4000C

Control Cage
MCP-ATS RESET
ALRM SPKR
HDD PWR
CPV5350
FlexiCom 4000
Cabinet
17-18
Figure 17-7.
Coral FlexiCom 400 B C D 1 2 3 4 5 6 7 8 9 10
(with HDC
controller)
MEX-IP2
Terminal #
1st 2nd
8DRCM-2, 8DRCM-2,
8DRCM, 8DRCM,
8DRCF, 8DRCF,
or RMI or RMI
1 = PORT 1 5 = PORT 1
2 = PORT 2 6 = PORT 2
3 = PORT 3 7 = PORT 3
4 = MODEM 8 = MODEM
0 = KB0
RS-232E
Coral FlexiCom 400

17-19
Figure 17-8.
Coral
FlexiCom 5000 4th 5th
(with 4GC controller) 8DRCM-2, 8DRCM-2,
8DRCF, 8DRCF,
or RMI or RMI
13 = PORT 1 17 = PORT 1
14 = PORT 2 18 = PORT 2
15 = PORT 3 19 = PORT 3
1st
8DRCM-2, 6th
8DRCM, 8DRCM-2,
8DRCF, 8DRCM,
or RMI 8DRCF,
or RMI
1 = PORT 1
2 = PORT 2 21 = PORT 1
22 = PORT 2
3 = PORT 3 23 = PORT 3
MEX-IP2
FlexiCom 5000
SAU Control Shelf
INT
RST
MEX-IP2
0 = KB0
RS-232E
FlexiCom 5000 FlexiCom 5000

3-shelf 4-shelf
17-20
Figure 17-9.
Coral
FlexiCom 6000 4th 5th
(with 32GC 8DRCM-2, 8DRCM-2,
controller) 8DRCM, 8DRCM,
Terminal # 8DRCF, 8DRCF,
or RMI or RMI
13 = PORT 1 17 = PORT 1
14 = PORT 2 18 = PORT 2
15 = PORT 3 19 = PORT 3
1st
8DRCM-2, 6th
8DRCM, 8DRCM-2,
8DRCF, 8DRCM,
or RMI 8DRCF,
or RMI
1 = PORT 1
2 = PORT 2 21 = PORT 1
22 = PORT 2
3 = PORT 3 23 = PORT 3
0 = KB0
Coral FlexiCom 6000

Control Cage

MCP-ATS RESET
ALRM SPKR
HDD PWR
CPV5350
FlexiCom 6000 FlexiCom 6000

3-shelf 4-shelf
17-21
FROM/TO 0 for KB0 (see Table 17-1 on page 17-11),

TERM # 1..24 for Serial or Modem port (see Table 17-2 on page 17-11),
1..28 for PI via MAP port (see Table 17-3 on page 17-12)
Enter the terminal number, or numbers, required to setup.
 For MAP ports, only the following parameters are rellevant:

TERMINAL TYPE, CONNECTION_TYPE, ENHANCED_DISPLAY_FORMAT KB0
only, AUTO_LOGOUT, AUTO_LOGOUT_TIME and PROGRAM (Y/N)?.
TERMINAL TYPE 0-4, see Table 17-4

Determines the escape sequences used by the PI for character attribute and cursor
positioning functions. The following devices are defined by the range number:
Enter the digit corresponding to the terminal type emulated by the PI terminal
device connected to the port. To determine emulation, refer to manufacturer
information supplied with the terminal device.
Table 17-4: Terminal Type
Digit Terminal Type Description
0 VT100 DEC VT-100 (Default)
1 Qume Qume QVT-101 (or ADM-3A/5, TV1900)
2 Printer Standard KSR Data Printer
3 Computer Standard PC, also for CVD and CVA
 For Coral Versions 11 or lower

4 CID Caller ID terminal (not KB0 and not 8DRCF)
When defining this parameter as 4-CID (for Caller

ID applications on analog LS trunks lines see

CALLER_ID_BOX_LINE# [9] on page 8-48) define the
following Setup with a Baud Rate of 9,600 and No
Parity and N_Bits as 8.
 For Coral Versions 14 or higher

Caller ID for Analog LS trunks is supported via
4T-CID and 8T-CID cards and no Caller ID box is
needed.
 For Coral Versions 14.66 or higher

Caller ID for Analog LS/GS IP trunks is supported
via its FXO Coral Teleport unit and no Caller ID
box is needed
.
17-22
CONNECTION_TYPE  Display mode Only (KB0, RMI, MODEM, or TELNET)

Displays the type of connection used to access the program interface terminal.
Connection Type Optional Hardware
KB0 • IPx Office

• MCP-IPx2
• MEX-IP2
• MCP-ATS
• LIU
RMI • 8DRCM-2 (1,2,3) RS-232

• 8DRCF (1,2,3) RS-232
• 8DRCM (1,2,3) RS-232
• RMI (1,2,3) RS-232
• IPx 500 (1,2,3) RS-232
MODEM • 8DRCF (4) modem

• 8DRCM* (4) modem
• RMI (4) modem
• U-RMI Office (4)
• RMI Office (4)
• IPx 500 (4)†
TELNET • IPx Office (MAP-CNCM)

• MAP card (CNCM)
* The MODEM is not available on 8DRCM-2 cards.
† IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not include a
MODEM. The modem was standard in MSBipx Hardware Issue-0220X1003 or
lower.

17-23
ENHANCED_ Yes/No
DISPLAY_FORMAT
This parameter is relevant for KB0 only, when the terminal type (above) is VT100
KB0 only
or a PC with VT emulator and determines whether KB0 has an enhanced display
(Yes), or resembles the terminals connected to the
8DRCF/8DRCM-2/8DRCM/RMI (No).
When set to Y, the top line on the screen displays the title bar with the following
information:
• Date and time: dd/mm/yy hh:mm
(when defined in the following parameter)
System type:
G. HDC (FlexiCom 400, IPx 500, 800, and CDRS 200E),
4GC (FlexiCom 5000, IPx 3000),
iGC (IPx Office),
32GC (FlexiCom 6000, IPx 4000)
M. Master (Coral FlexiCom 5000, IPx 3000)
S. Slave (Coral FlexiCom 5000, IPx 3000)
Standby (Coral FlexiCom 6000, IPx 4000)
A. Active (Coral FlexiCom 6000, IPx 4000)
Faulty. Inactive faulty system- performs activities such as diagnostics, alarm
activation for service calls and communication with the Active system for fault
reporting and verifying the proper operation of the active system.
In this mode, the system still performs tests and might automatically return to
proper operation when normal results are observed.
(Coral FlexiCom 6000, IPx 4000)
Maintenance. Inactive system in Maintenance mode-performs diagnostics, alarm
activation for service calls and communication with the Active system for fault
reporting and verifying the proper operation of the active system.

The system enters this mode and returns to Active mode only manually by the
technician. (Coral FlexiCom 6000 or IPx 4000)
• Node title: the current PI system node such as Card List, Port List, NPL etc.
• Active controls: such as ^w, ^e etc.
The bottom line displays ERROR messages, e.g. ILLEGAL NUMBER, TRY
AGAIN, etc.
While entering a password, a beep is heard and * is displayed for each character.
Directly entering a new PI system node like Port List or Card List clears the
previous screen.
^U acts as a scroll.
The display of the last changes in SNAP mode are emphasized for better
readability.
17-24
TIME_AND_DATE_ Yes/No
DISPLAY_AT_TITLE_
This parameter is prompted only when a previous parameter is set to Yes. It
BAR
determines whether or not the time and date are displayed in the top line (title bar).
KB0 only
• Recommendation: Set this parameter to No, if the terminal is used for
logging information.
AUTO_LOGOUT Yes/No
AUTO_LOGOUT cancels (after the time-out period) the current process and places
the PI into the Enter Password menu upon inactive terminal (operates as if
[CTRL]-P were entered at the keyboard), see [CTRL] P on page 1-15.
AUTO_LOGOUT_TIME 2..30..1440 (minutes)
 Appears only when AUTO_LOGOUT, above, is set to Yes.

This parameter determines the time interval, before the system cuts out
automatically following the last operation. One minute before automatic log-out a
warning message is displayed:
WARNING! IDLE TERMINAL WILL BE LOGGED-OUT WITHIN A MINUTE!
17-25
BAUD RATE See Table 17-5 and Table 17-6 below;

Default: 0..1..11
Determines the data send/receive rate in bits per second (bps) for RS-232 data
interface ports, as well as the Modem used for the remote maintenance. Enter the
digit corresponding to the desired selection shown below.
Table 17-5: RS-232 Interface Baud Rate
KB0 KB1-3 KB 1-3, 5-7, 9-11,

13-15, 17-19, 21-23
Baud
Entry
Rate MEX-IP2 IPx IPx 500M 8DRCF RMI
MCP-ATS Office CDRS 200E 8DRCM-2
MCP-IPx2 8DRCM
0 AUTO* N/A N/A 4 4 4

1 9,600 4 4 4 4 4
2 4,800 4 4 4 4 4
3 2,400 4 4 4 4 4
4 1,800 N/A N/A N/A N/A N/A
5 1,200 4 4 4 4 4
6 600 4 4 4 4 4
7 300 4 4 4 4 4
8 19,200 4 4 4 4 N/A
9 38,400 4 N/A 4 4 N/A

10 57,600 4 N/A 4 4 N/A
11 115,200 4 N/A 4 4 N/A
* Setting the BAUD_RATE to AUTO enables the Coral to automatically synchronize the
baud rate between the PI Terminal Device and the RS-232 Interface. Once the PI Terminal
Device is working, press ENTER continuously until the Coral successfully synchronizes
with the RS-232 Interface.
NOTE: If the card (RMI, 8DRCF, 8DRCM-2, 8DRCM, MEX-IP2, MCP-IPx2, MCP-ATS) is
reinitialized or removed and replaced, BAUD_RATE automatically reverts to its default
definition of 1 (9600 bps). The technician must redefine the KBx settings to 0 (AUTO).
17-26
Table 17-6: Modem Baud Rate KB4,8,14,16,20,24
Entry Modem Type - 8DRCM*, RMI

Bell 103/212A or ITU V.21/V.22, 300/1200bps
0 BO N/A
1 BA Bell answer Type 103/212A
2-3 --- N/A
4 CO N/A
5 CA CCITT Answer V.21/V.22
6 - 11 ---- N/A
* The MODEM is not available on 8DRCM-2 cards.
Entry Modem Type-

8DRCF, IPx 500M*, U-RMI Office, RMI Office
56 Kbps (V.90)
0, 1 - 11 The modem tries to synchronize from a maximum of
56 Kbps down to the highest possible baud rate.
* IPx 500M with MSBipx Hardware Issue-0230X1003 or higher does not
include a MODEM. The modem was standard in MSBipx Hardware
Issue-0220X1003 or lower.
.
PARITY See table below;0

Determines the parity check method used by the PI. Enter the digit corresponding
to the desired selection.
Entry Parity Entry Parity

0 None 2 Mark
1 Odd 4 Space
3 Even
N_BITS 7/8
Determines the number of data bits used by the PI to identify an ASCII character.
PROGRAM (Y/N)? Yes/No

Transfers the updated information immediately to the RS-232 data interface port,
when Yes is entered.
17-27
Regardless of entry, routine diagnostics periodically resend the Terminal Setup to

the RS-232 data interface port, including any update made.
17-28
KB0 Setup Through Attendant Console - Feature
Setting KB0 Through KB0 terminal setup can also be performed at the Attendant Console. This
Attendant Console procedure should only be carried out by a qualified technician. All changes take
effect immediately.
1. Dial KB0 Setup Feature Code #1996. The following message appears on
the keyset display:
BAUD RATE ####
2. Scroll between options by pressing the VOL UP button or NEXT softkey.
3. The following table presents the options and ranges available when setting
up KB0 through the Attendant Console.
Option Range and Default Attendant

Console Message*
Baud Rate See Table 17-5 on page 17-26 BAUD RATE # # # # # #
Default for all systems: 9600
Parity 0 (No), 1 (Odd), 3 (Even) PARITY #

NO= 0 ODD= 1 EVN= 3
No. of Bits 7, 8 # BIT

BIT = (7/8)
* # (number sign) = current KB0 setup on attendant’s keyset display.
4. Enter the required change for each option or scroll to the next option.
5. When finished, press the SPKR key or hang up.
6. The KB0 terminal is setup as required.
KB0 Setup Through Attendant Console - Feature TERM,0
17-29
Terminal Reset ç TERM,1 [0,8,0,1]
Terminal Reset is used to reset one of the RS-232 terminal ports. Reset cancels the
current process and places the PI into the previously used menu (operates as if
[CTRL]C were entered at the terminal).
TERM # 0(KB0), 1..24 (see Table 17-1 on page 17-11)

Enter the terminal number required to be reset.
The message
*** PROCESS ABORTED AT TERM # ***
is displayed at the terminal originating the request.
 The # sign is replaced by the terminal number at which the current process
is being aborted.
Terminal Reset TERM,1 [0,8,0,1]
17-30
Terminal Clear ç TERM,2 [0,8,0,2]
Terminal Clear is used to clear communication on one of the RS-232 terminal

ports. Clear cancels the current process and places the PI system into the Enter
Password menu (operates as if [CTRL] P were entered at the terminal).
TERM # 0(KB0), 1..24 (see Table 17-1 on page 17-11)

Enter the terminal number to be cleared.
The message:
*** PROCESS ABORTED AT TERM # ***
is displayed at the terminal originating the request.
 The # sign is replaced by the terminal number at which the current process
is being aborted and then the current session ends.
Terminal Clear TERM,2 [0,8,0,2]
17-31
iVMF Remote Maintenance ç ROOT,3,8

This branch allows programming the iVMFipx card remotely via a Coral modem.
The iVMFipx card provides integrated Voicemail functionality for Coral IPx 500,
CDRS 200E systems. iVMF ports can also be configured to be used as an
announcer ports:
• defined as ANNOUNCER [34] (page 9-42) =Yes, (KEY branch- 8SDT)
• iVMF ports configured as announcer ports within the card, see relevant iVMF
Manual
This branch defines the remote modem connection process for Voicemail
integration from the iVMFipx card.
SHELF 0..2: Coral IPx 500 and CDRS 200E

Define the shelf in which the iVMFipx is located.
SLOT 1..8: Coral IPx 500M and CDRS 200Emain cages (Shelf #: 0)
1..10: Coral IPx 500X and CDRX 200E expansion cages (Shelf #: 1, 2)
Define the slot in which the iVMFipx card is located.
The iVMFipx card provides 8 Voicemail ports and may be installed in any
peripheral I/O slot of the Coral IPx 500 and CDRS/CDRX 200E.
CONNECTION? Yes/No
 The PI terminal must be connected via a Coral modem (i.e., via KB4, or
KB8 of an 8DRCF and NOT directly via the RS-232 KB0) to enable
remote connection to the Voicemail Interface.
iVMF Remote Maintenance ROOT,3,8
To Establish a Connection to the Card:

1. Enter Yes to begin to establish a connection with the iVMFipx card.
2. The Coral Administration screen is displayed:
ADMINISTRATION
0-TIME/DATE
1-TIME_ADJ
2-SMDR
3-WAKEUP
4-ACCOUNT
5-TRAFFIC
6-CALL TRACE
7-SOFTWARE UPGRADE
8-iVMF REMOTE MAINTENANCE
9-Internal Traffic
10-MAP
17-32
: *
3. Press ESC>ESC to complete the connection process.
The Voicemail Main Administration screen is displayed on the PI terminal
enabling access to its password controlled programming menus. Refer to the
iVMFipx Integrated Voicemail with Flash Technology Installation and
Maintenance Manual for details.
To Return to the Coral PI Menus:
Press CTRL-C four times from anywhere within the Voicemail menus to re-access
the Coral and return to the Program Interface Root Menu.
17-33
17-34
18 Features
This chapter contains the programming instructions for port features that can be
activated from either the PI terminal, CVD terminal or from the Attendant Console.
These features can be activated on either stations or trunks. This chapter does not
display the Authorization Parameters listed in Chapter 3.
Trunk Features allow to define the operation of system trunks for special use, such
as for incoming or outgoing calls only or for designating a trunk as reserved for a
particular group or specific station.
Station Features allow to define stations for specific feature activation. Some of
these features operate permanently, or until redefined, such as Call Forward All.
Some features can also be operated directly from a user station or attendant station,
when defined by COS.
Feature Control ...........................................................................................18-2
18-1
Features PI Reference Manual
Feature Control ç FEAT,0 [0,4,0]
The following station, group or trunk features can be either updated (0-UPDATE)
or displayed (1-DISPLAY) as required.
The dial numbers needed for update or display are then entered (range of dial
numbers is defined Table 18-1 under Operates On) after which the following menu
appears:
CHOOSE FEATURE:
1 ATTEND_MSG 16 HOT_TK_DELAY 31 CF_EXT_BUSY
2 CF_ALL 17 DROP_NO_DIAL 32 CF_NO_ANS_EXT
3 CF_BUSY 18 HOT_TK_IMM 33 TIMED_FWD_EXT
4 DONT_DIST 19 I/C_ONLY_TK 34 AUTO SET RELOCATE
5 HOT_ST_IMM 20 TK_RSRVD 35 FlexiCall_ALL
6 DIAL_LOCK 21 NIGHT-1 36 FlexiCall_INT
7 HOT_ST_DELAY 22 NIGHT-2 37 FlexiCall_EXT
8 DIR_IN_LINE 23 EXC_HOLD 38 IRSS (Freedom)
9 TERMIN_ONLY 24 PRIVACY 39 CF_UNDEF
10 ORIGIN_ONLY 25 O/G_ONLY_TK 40 LOAD_ID
11 ST_BLOCKING 26 CHECK_OUT 41 LOGIN_LOGOUT
12 O/G_TK_RESTR 27 TIMED_FWD 42 RELEASED_RESUMED_ALL
13 CF_NO_ANS 28 CLR_ID_RESTR 43 WRAP_UP_TIME
14 BUSY_OUT 29 LAR_BLOCKED 44 PRIMARY_LOGIN

Feature Control FEAT,0 [0,4,0]
15 CO_BLOCKED 30 CF_EXT_ALL 45 MESSAGE
18-2
PI Reference Manual Features
Update the various features by:

• Selecting any of the required feature numbers listed above,
• and then entering any one of the following responses.
Response Action Result
A Assign feature FE.ADDED is displayed.
R Remove (cancel) feature FE.RMVD is displayed.
DEST Feature Port # (see Destination FE.ADDED is displayed.

Range in Table 18-1).
A/R (Add/Remove) Acts as an on/off switch.
A feature that is merely activated, but has no destination selected
can either be added or removed. Removing can take place only
after the feature has been added.
When the feature is not assigned the following message appears:
NOT ASSIG (A/CR)
When the feature is assigned, this following message appears:
ASSIG (R/CR)
Display the various features by typing in the relevant feature number and pressing
[ENTER]. To display all activated features, type ALL or press [CR].
Legend for Table 18-1:
Modified By Description
AM Attendant Modifiable
BM Boss Group Modifiable
UM User Modifiable

COM Central Office Modifiable
Operates On Description
B Operates on Boss Group
S Operates on Stations
H Operates on Hunt Group
T Operates on Trunks
T*** Operates on Trunks but

Excluding PRI and TBR Trunks (ISDN)
18-3
Table 18-1: Table of Modifiable Features
Mnemonic Modified Explanation Destination Oper-

Full Feature By Range ates On
Name
1 - ATTEND MSG AM Allows an attendant to leave a message at a Attendant station defined as S/B
Attendant Message To station. When the message is delivered, ATT [17]=Yes in Keyset
Station and Boss message indication is automatically canceled. Definitions (see page 9-35).
Group
2 - CF ALL AM/UM/BM Allows re-routing a call to another destination. Station, Boss/Hunt Group, S/B/H
Call Forward All When activated, all calls are re-routed. Private/Public Libraries,
Bell/UNA, DVMS MSG/Port,
Group Call, Wait Que, Net #
3 - CF BUSY AM/UM/BM Allows re-routing a call to another destination Station, Boss/Hunt Group, S/B
Call Forward Busy when the user's station is busy or when the Private/Public Libraries,
Boss Group's lines are all occupied. Bell/UNA, DVMS MSG/Port,
4 - DONT DISTURB AM/UM Inhibits incoming call signaling (ringing is A/R S/B
Do Not Disturb turned off). Station can make calls. A caller to
this station hears a reorder tone. Only a caller
with DND Override can call the station.
5 - HOT ST IMM AM Causes a station that offhooks to immediately Trunk number, station, Keyset S
Hot Station Immediate route to a predefined destination. As opposed Voice Page, Trunk Group,
to Hot Station Delay, where the programmed Boss/Hunt Group,
destination is dialed only after a defined Public/Private Libraries,
time-out period. Bell/UNA, Page Public
Address, Zone Group Page,
DVMS MSG/Port, Group Call,
Dial Service, Routing Access,
Net #
6 - DIAL LOCK UM Locks the telephone against unauthorized A/R S

usage.
7 - HOT ST DELAY AM When activated, a station rings another Trunk number, station, Keyset S
Hot Station Delay station, or automatically connects to a paging Voice Page, Trunk Group,
device or automatically dials out when the Boss/Hunt Group,
handset is taken off-hook and no digits are Public/Private Libraries,

dialed within the programmed first digit Bell/UNA, Page Public
time-out. Address, Zone Group Page,
As opposed to Hot Station Immediate, where DVMS MSG/Port, Group Call,
the programmed destination is dialed Dial Service, Routing Access,
 Not applicable for P-Seies (such

immediately after an off-hook condition. Net #
as: P-335, P-450), T207S,

T208S, T207S/NP, T208S/BL,
T322, T328, and all third-party
SIP terminals.
8 - DIR IN LINE AM Determines the destination of direct in-line Station, Boss/Hunt Group, T
Direct-In-Line calling, when DAY Service Period is activated. Public Library, Bell/UNA, RMI
Destination This feature can link a trunk to a specific mode, DVMS MSG/Port,
destination in such a way that incoming CO Group Call, Wait Que, Net #
(including DID) calls are connected directly to
the destination, without attendant intervention.
18-4

Name
9 - TERMIN ONLY AM Prevents the station from originating any calls. A/R S
Station Terminating Calls can only be received at this station.
Only
10 - ORIGIN ONLY AM Blocks all incoming calls. This station can only A/R S
Station Originating originate calls. A caller to this station hears a
Only reorder tone.
11 - ST BLOCKING AM Prevents the station from making or receiving A/R S

Station Blocking calls. A caller to this station hears a reorder
tone.
12 - O/G TK RESTR AM Prevents the station from making outgoing A/R S

Outgoing Trunk trunk calls.
Restriction
13 - CF NO ANS AM/UM/BM Allows re-routing a call to another destination. Station, Boss/Hunt Group, S/B
Call Forward No When activated, calls are re-routed only when Private/Public Libraries,
Answer the station is not answered, after a defined Bell/UNA, DVMS MSG/Port,
time-out period. Group Call, Wait Que, Net #
14 - BUSY OUT AM Blocks a trunk from originating or terminating A/R T

Trunk Busy Out calls. This feature is typically used when trunk
repair is required.
15 - CO BLOCKED AM/COM An out-of-service signal sent by the CO that A/R T

Trunk CO Blocked blocks the trunk card from receiving incoming
and/or making outgoing calls. This option
allows the technician to view trunks blocked by
the Central Office.
16 - HOT TK DELAY AM The outgoing trunk connects after an outgoing A/R T***
Hot Trunk Delayed time-out delay, if no dialing has taken place.
17 - DROP NO DIAL AM When a trunk has been accessed, but no A/R T

Trunk Drops When No dialing (no first digit) has taken place, the trunk
Dialing is Detected will be dropped after a predefined time-out
period.

18 - HOT TK IMM AM An outgoing trunk call immediately connects A/R T***
Immediate Hot Trunk when accessed.
19 - I/C ONLY TK AM Trunk is blocked for outgoing calls. Only A/R T

Incoming Trunk Only incoming calls are allowed.
20 - TK RSRVD AM Allows reserving a trunk or trunk group for a Station, Boss Group T
Trunk Reserved to specific station or Boss Group. When
Specific Station specifically allocated only those stations or
groups can dial out along the trunk.
21- NIGHT-1 AM Same as 8-DIR IN LINE, but for NIGHT-1 Station, Boss/Hunt Group, T
Night1 Destination service period. Public Library, Bell/UNA, RMI
modem, DVMS MSG/Port,
22 - NIGHT-2 AM Same as 8-DIR IN LINE, but for NIGHT-2 Station, Boss/Hunt Group,
Night2 Destination service period. Public Library, Bell/UNA, RMI
mode, DVMS MSG/Port,
18-5

Name
23 - EXC HOLD UM Ensures that a call placed on hold can be A/R S
Exclusive Hold in Boss retrieved only at the station where Exclusive
Group Hold was originally placed. If Exclusive Hold is
not utilized, the call that was placed on hold
can be retrieved by any other Keyset member
of your Boss Group. This feature can be
utilized for a specific call or for all calls.
24 - PRIVACY UM Prevents a third Boss Group party from joining A/R S

Privacy in Boss Group the conversation.
25 - O/G ONLY TK AM Blocks a trunk towards all incoming calls. Only A/R T
Out-Going Only Trunk outgoing calls can exist along such a trunk.
26 - CHECK OUT AM Places the station in Check-Out status. When A/R S

deactivated, the station is in Check-In status.
27 - TIMED FWD AM/UM/BM Allows re-routing a call to another destination Station, Boss/Hunt Group, S/B/H
Timed Call Forward according to the time period defined in Private/Public Libraries,
TIMED_ FORWARD INT/EXT on page Bell/UNA, DVMS MSG/Port,
6-38. This feature is the same as Call Forward Group Call, Wait Que, Net #
All, except that it operates at specifically
designated hours.
28 - CLR_ID_RESTR UM Restricts the presentation of the User's A/R S

Caller Identification telephone/ID number at the calling party's
Restriction destination. This feature is activated on a per
call basis, before dialing the external
destination number.
29 - LAR_BLOCKED AM Allows blocking trunks or Dial Service which A/R T or

reported failure cause back to the originator. Dial
Only causes indicated in the Trunk Group or Service
Dial Service fields (Look Ahead Routing
 This feature is irrelevant for

Triggers branch) trigger the LAR Block feature.
trunks defined as I/C ONLY TK.
 LAR feature requires setting

LOOK AHEAD ROUTING [21] on
page 6-13 to YES.
30 - CF_EXT_ALL AM/UM/BM Allows re-routing external calls to another Station, Boss/Hunt Group, S/B/H
Call Forward All- destination. When activated, all calls are Private/Public Libraries,
External re-routed. Bell/UNA, DVMS MSG/Port,
31 - CF_EXT_BUSY AM/UM/BM Allows re-routing external calls to another Station, Boss/Hunt Group, S/B
Call Forward Busy- destination when the user's station is busy or Private/Public Libraries,
External when the Boss Group's lines are all occupied. Bell/UNA, DVMS MSG/Port,
32 - CF_NO_ANS_ AM/UM/BM Allows re-routing external calls to another Station, Boss/Hunt Group, S/B
EXT destination. When activated, calls are Private/Public Libraries,
Call Forward No re-routed only when the station is not Bell/UNA, DVMS MSG/Port,
Answer - External answered, after a defined time-out period. Group Call, Wait Que, Net #
18-6

Name
33 - TIMED_FWD_ AM/UM/BM Allows re-routing external calls to another Station, Boss/Hunt Group, S/B/H
EXT destination according to the time period Private/Public Libraries,
Call Forward Timed - defined in TIMED_ FORWARD INT/EXT Bell/UNA, DVMS MSG/Port,
External on page 6-38. This feature is the same as Call Group Call, Wait Que, Net #
Forward All, except that it operates at
specifically designated hours.
34- PERM/TMP_ UM Allows swapping station profiles. Station S

PORT
(Auto Set Relocate) See Auto Set Relocate (Portability) List
per Device Type on page 18-11 below.
35- FLEX_ALL UM Allows a user to set an on/off-site phone as a Station, Private/Public S
remote destination supplementing the Coral Libraries, Bell/UNA, DVMS
station. Both internal and external incoming MSG/Port, Group Call, Net #
calls ring simultaneously at the station and the
remote destination. During the call, the remote
destination is considered a Coral station and is
thus enabled with Coral features.
36- FLEX_INT UM Allows a user to set an on/off-site phone as a Station, Private/Public S

remote destination supplementing the Coral Libraries, Bell/UNA, DVMS
station. Only internal incoming calls ring MSG/Port, Group Call, Net #
simultaneously at the station and the remote
destination. External calls ring only at the
Coral station. During the call, the remote
destination is considered a Coral station and is
thus enabled with Coral features.
37- FLEX_EXT UM Allows a user to set an on/off-site phone as a Station, Private/Public S

remote destination supplementing the Coral Libraries, Group Call
station. Only external incoming calls ring
simultaneously at the station and the remote
destination. Internal calls ring only at the Coral
station. During the call, the remote destination
is considered a Coral station and is thus
enabled with Coral features.

38- IRSS UM Allows defining an IRSS off-site destination Private/Public Libraries S
that can access certain Coral features by containing the off-site
receiving dial tone from the Coral. The telephone number.
features include: New Call Request, Transfer,
3-way call, Call Divert, access Voicemail,
Activate/Cancel the FlexiCall All feature as
well as change the FlexiCall destination.
18-7

Name
39-CF-UNDEF UM/BM Defines a Call Forward destination for calls to Station, Boss/Hunt Group, S/B
(Call Forward an undefined station. Private/Public Libraries,
Undefined) Bell/UNA, DVMS MSG/Port,
IP User When this feature is used to avoid Undefined Private Library containing the
Coral IP Stations, assign a CF_Undefined IP station number and
Private Library number to this IP station to Routing Access to the
search for the same IP station number in the different network nodes.
different Coral systems where the IP station’s NOTE!
call agent (primary or secondary) may reside. The same IP station number
For IP terminals, program a non-IP must already be defined in
destination, like Voicemail, as the forwarding each Coral system of a Coral
destination. If the IP link goes down or the Network.
bandwidth limit is exceeded a call routed to
the IP terminal will get rerouted to the CF_
UNDEF destination instead of being
disconnected.
40-LOAD_ID UM This feature enables the system to identify the ID number (4 digits) S
ACD group agent when the agent joins the
system for the first time during a session.
Once the agent’s ID number is registered in
the system for the first time, he/she can join
as many ACD groups as required. As long as
he/she is logged into at least one ACD group,
his/her ID number will remain in the system.
However, once he/she has logged out of the
last group, his/her ID number will be erased
from the system. Entering an ACD group
 Only one ID number is allowed

requires reloading the agent’s ID.
per station, any additional Load

ID replaces the current one.
The ID number can be changed

as many times as needed.
18-8

Name
41-LOGIN_LOGOUT UM This feature is used when an ACD group ACD group number, A/R S/H
agent joins or leaves an ACD group. An agent
can simultaneously be a member of numerous
 Notes:
ACD groups.
• In some systems ID number

must be loaded before Login.
• Logging-out from all the
ACD groups the agent’s ID
number is erased from the
system.
• Logging-out from an agent’s
primary group, also causes
log-out as primary, so the
group is no longer marked as
primary.
42-RELEASED_ UM This feature is used to temporarily release an A/R S/H
RESUMED_ALL ACD/UCD group agent from all of the
ACD/UCD groups of which he/she is a
member. This feature also allows to resume
connections with the ACD/UCD groups from
which the agent released him/herself..
#1975 - Released Resumed All Features
43-WRAP_UP_TIME UM This feature allows you to provide an idle ACD group number, A/R S/H
ACD/UCD group member with a time-out
period between consecutive group calls. The
time-out period is determined for each group
on a system-wide basis (WRAP-UP TIME on
page 10-10). This feature allows an agent to

utilize the Wrap-Up code without interfering
with outside calls.
18-9

Name
44-PRIMARY_LOGIN UM This feature allows defining an ACD group ACD group number, A/R S/H
agent as having priority in specific ACD group
over other groups of which he/she is a
member. Once the agent has logged in to
his/her primary group, waiting calls are always
routed to him/her from this group first. Only
when no more calls are waiting on the primary
group queue, the agent will receive calls from
 Notes:
other groups.
• Some ACD/UCD groups may

require entering an ID
number before logging in to
the group (see 40-LOAD_ID
on page 18-8).
• Only one group can be
marked as primary group for
an agent. When logging in
again on a different group as
primary, the previous
primary log-in is overridden.
45-MESSAGE This feature allows you to leave a callback Keyset, FlexSet or SLT
message at a station for another station. stations with a message
waiting lamp, station groups,
or network numbers
18-10
Table 18-2: Auto Set Relocate (Portability) List per Device Type
l = Swappable Device Types
T207M, T208M, T207M/NP, T208M/BL

FlexSet 280, 280D, 280D-Z, 280D-HS
FlexSet 120, FlexSet 120D
FlexIP Softphone (FLIPS)
SLT, Type 500, Type 2500

FlexSet 80S, FlexSet 80P
Device Types
FlexSet 280S, 281S

FlexSet 120S, 121S
FlexSet-IP 280S
FlexSet 120L
EKT, VDK
DKT 2xxx
DKT 1xxx
Magneto
DST
EKT, VDK l l l l l l l l
DKT 2xxx l l l l l l l l
DKT 1xxx l l l l l l l l
DST l l
FlexSet 80S, 80P (GKT 4320, 4321) l l l l l l l l
FlexSet 280, 280D, 280D-Z, 280D-HS l l l l l l l l
FlexSet 120, 120D l l l l l l l l
FlexSet 120L l l
FlexSet 280S, 281S l l l l l l
FlexSet 120S, 121S l l l l l l l l
FlexIP Softphone (FLIPS) l l l
FlexSet-IP 280S l l l
T207M, T208M, T207M/NP, T208M/BL l l l
Magneto l l

SLT, Type 500/2500 l l
 The Auto Set Relocate feature is not applicable for the following stations:
FlexAir Wireless handsets (T-304, T-402, T-404, T-408), CoralAIR Wireless handsets, Coral SIP
terminals (P-Seies (such as: P-335, P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328,
SeaBeam softphone), third-party SIP terminals, SLT-IP stations (behind Coral Teleport/FXS, SIP
gateway, MGCP gateway).
CAUTION!
Larger keyset units swapped with smaller units of the same type lose their extra button/key functions.
18-11
WARNING!
Swapped phones lose their physical location definition towards the E911 center.
To ensure that the E911 center location definition remains intact, manually swap the Second ALI
phone profiles in SLT or Keyset Definition (see SEC_ALTERNATE_LINE_ID [29] (page 9-13) or SEC_
ALTERNATE_LINE_ID [67] (page 9-62)) after the users swap phone profiles.
Also ensure that USE SECOND ALI [19] (page 15-16) is set to Yes in Dial Services.
18-12
19 Voice Transmission Controls
This chapter contains information about the setup levels for controlling voice
transmission across ports and cards. In addition, special network balancing features
for trunks and other types of ports is presented.
Gains - General Description.......................................................................19-2

Gains Tables ...............................................................................................19-3
Feature Control .........................................................................................19-17
Personal Port Gain, Compensation: Ports ................................................19-22
Personal Port Gain, Compensation: Comp ..............................................19-23
Balancing Network ...................................................................................19-24
19-1
Voice Transmission Controls PI Reference Manual
Gains - General Description

Voice transmission levels from port to port through the Coral switching system can
be adjusted through the system database, provided at least one of the ports has an
analog interface. When all ports in a connection are digital, such as, DID station to
T1/E1/PRI trunk channel, the transmission levels of the ports cannot be adjusted.
Adjust the voice transmission levels between any type of port by using either the
General Port Gains, Personal Port Gains, Feature Control or Balancing Network
tables. The tables also provide individual adjustment for any port. The following
tables (menus) are provided for making these adjustments.
Table 19-1: List of Gain Controls
Name of Table Route Description

(Menu)
General Port Gains 0,1,3 Determines the basic setup levels for ports and
paths in the system, during voice connections.
Personal Port Gains- 0,2,3 Determines the personal (per port)

Compensation compensation for transmission levels in the
system.
Feature Control 0,1,4 Determines the basic setup levels for ports
when not connected to other ports.
Balancing Network 0,2,2 Determines the type of termination for ports,

while providing optimal impedance matching for
both trunk lines and station lines.
The transmission levels entered through the PI do not necessarily indicate the
actual transmission levels from port to port. The levels entered through the PI
represent only the adjustments made as the analog audio signal is converted to a
digital Pulse Code Modulation (PCM) signal, and the conversion from PCM back
to an analog audio signal. Therefore, the true transmission levels are the sum of the
gain produced in the PCM conversion and the effect of the port circuitry on the
analog signal.
Entries made through the PI are referred to as Software Gain, while the effect of
the port circuitry is referred to as Hardware Gain. The combination of these two
gain factors determines the port-to-port or (end-to-end) transmission level of the
system.
 It is not recommended to change any gain values in the system, unless a

severe gain level problem or trunk imbalance exists.
However, when values must be changed, it is good practice to make the changes in
small and carefully planned steps. The effect of these changes should be closely and
continuously checked for their influence on the entire system.
19-2
PI Reference Manual Voice Transmission Controls
Gains Tables ç ROOT,0,1,3

Defines Gain Values for the different system paths (all types of ports) for
completed calls, but only after the call has been established during voice
connection. After this option is chosen, the following information appears on the
PI terminal for source and destination data.
Table 19-2: Gains-Source or Destination Types
Port Type Description Applied to Card Family
0 SLT POTs (Single Line Telephones) • Full size: 8/24SA, 8/16/24SLS, or 4/8/16SH card
• IPx 500 and CDRS/CDRX 200E: 8/16/24SAipx or 8/16SLSipx
card
•
1 MAGNETO Military magneto station 8SM, 8SMipx
2 EKT EKT keysets 2SK, 4SK, 8SK
3 VDK VDK keysets 2SD, 8SD, 4IAA
4 LS/GS Loop Start (LS) or • Full size: 4T-C, 8T-C, 4T-CID, 8T-CID, 4/8TPF, 4TMR-PF card
Ground Start (GS) analog trunks • IPx 500 and CDRS/CDRX 200E: 4/8T-Cipx, 4/8T-CIDipx,
4TMR-PFipx, 4TMR-PF-Gipx
• IPx Office: 4T Office, 8T Office, 4T-CID Office, 8T-CID Office
•
5 E&M E&M analog trunk cards 4TEM, 4TEMsl, 4TEMipx, 4TEM/S, 4TEMP/S
6 DID DID analog trunk cards 8DID, 8DID/S, 8DID/S-Z, 4BID, 8BID, 4GID, 8GID
7 ALS70 ALS70 analog trunk cards 4ALS, 8ALS

(Netherlands only)
8 DGTL Digital E1/T1 trunk cards T1, T1sl, T1ipx, 30T, 30Tsl, 30Tipx, 30T/E, 30T/M, 30T/x, 30Tsl,
30Tipx, 30T Office (30T or 30TM jumper selection),
UDT Office(T1), 2DT(T1/30T/30TM), 2DTipx(T1/30T/30TM),
Gains Tables ROOT,0,1,3

2DT Office(T1/30T/30TM)
9 NA Not Available (Not Available)
10 MODEM MODEM • Full size: 8DRCF, 8DRCM, RMI card

• IPx 500M: Embedded on motherboard (MSBipx Hardware
Issue-0220X1003 or lower)
• IPx Office: RMI Office or U-RMI Office card (check availability)
11 MUSIC MUSIC SOURCE • Full size: 8DRCF, 8DRCM-2, 8DRCM, RMI, ASU card
• IPx 500M and CDRS 200E: Embedded on motherboard
• IPx Office: U-MR Office, MR Office, RMI Office or U-RMI Office
19-3
Table 19-2: Gains-Source or Destination Types
Port Type Description Applied to Card Family
12 CONF Conference card ports • Full size: 8DRCF, 8DRCM-2, 8DRCM, CNF (defined as CONF)
• IPx 500M: 8DRCF on MSBipx issue 0100X1000 and lower
This parameter is irrelevant for conference ports provided by:

• CDRS 200E
• IPx 500M: URC2 on MSBipx issue 0200X1000 and higher
13 DVMS Digitized Voice Message System 4VS, 4VSN
14 3-WAY 3-WAY ports Any card using three way calls
15 PRI PRI trunks PRI-23, PRI-30, PRI-23sl, PRI-30sl, UDTipx (PRI-23), PRI-30ipx,
PRI-30 Office, UDT Office (PRI-23), 2DT(PRI-23/30),
2DTipx(PRI-23/30), 2DT Office (PRI-23/30)
16 DKT/DST FlexSet, DKT, DST and GKT 8/16SKD, 8SVD, 8/16/24SDT, 8/16/24SFT,
keysets 8/16/24SFT Office, 4S8F Office, 8S8F Office, 4S16F Office,
8S16F Office,
8/16SFTipx, 8/16SFTsl, 8F8Ssl
17 TBR BRI trunks 4TBR, 8TBR, 8TBRP, 4TBRsl, 8TBRsl, 8TBRPsl, 4TBRipx,
8TBRipx, 8TBRPipx, 4TBR Office
18 TWL TWL trunks 4TWL, 4TWLsl, 4TWLipx
19 iDSP iDSP card This parameter is irrelevant for Caller ID ports provided by:
• CDRS 200E
• IPx 500M: URC2 on MSBipx issue 0200X1000 and higher
20 IP IP endpoints UGW, UGWipx, UGW-E, UGW-Eipx, PUGW, PUGWipx,

Coral IPx Office (embedded CUGW on MCB Office)
 ALS70, BID, GID, and 30T/E cards are used only in European systems.
FROM 0..20
TO 0..20
SOURCE
Enter the required source port type range (originating side of transmission path);
FROM the start range TO the end range.
FROM 0..20
TO 0..20
DEST
Enter the required destination port type range (terminating side of transmission
path) FROM the start range TO the end range.
After entering this information, the current Gain Table default values are displayed
for the various system paths.
1) Every path can be controlled either by Source or by Destination.
For example: The SLT--> LS/GS_TRK path, which represents the
19-4
keyset to trunk levels, can also be programmed for its inverse path of
LS/GS_TRK --> SLT.
2) Receive (RX) and Transmit (TX) gains refer to Source.
RCV [2] -18dB..+12dB (in increments of 0.5dB)

Default: see Table 19-3 and Table 19-4 below
Receive is the amplification (gain) from the PCM channel to the Source Port.
TRX [3] -18dB..+12dB (in increments of 0.5dB)

Default: see Table 19-3 and Table 19-4 below
Transmit is the amplification (gain) from the Source Port to the PCM Channel.
Ports having the maximum value of gain can not have additional gain through
personal gain control, since the circuitry is already set for the maximum value.
 The full range is used by cards equipped with SICOFI components. Other
cards with C1 automatically cut the gain to a range of +6dB to -6dB.
For example: When an SLT is connected to a Loop Start/Ground Start trunk, the
gain equation would be:
1. Total gain from SLT to LS/GS_TRK:
• TRX[SOURCE = SLT-->DEST = LS/GS_TRK] + RCV[SOURCE =
LS/GS_TRK-->DEST = SLT]
2. Total gain from LS/GS_TRK to SLT:
• RCV[SOURCE = SLT-->DEST = LS/GS_TRK] + TRX[SOURCE =
LS/GS_TRK-->DEST = SLT]
Figure 19-1
Originating and
SOURCE DESTINATION
Terminating Sides- TRX TM
RCV
PORT CORAL PORT
Sketch
PCM

RCV TRX
ORIGINATING SIDE TERMINAL SIDE
19-5
Table 19-3: Default Gain Table* :continued

  
Source To Destination Source Receive Source Transmit
xmit/rcv card Gain Gain
rcv_gain
 xmit_gain

SLT ––> SLT +1 +5.5
SLT ––> MAGNETO +1 +5.5
SLT ––> EKT +1 +5.5
SLT ––> VDK +1 +5.5
SLT ––> LS/GS +6 +5.5
SLT ––> E&M +3 +5.5
SLT ––> DID +6 +5.5
SLT ––> ALS70 +6 +5.5
SLT ––> DGTL_TRK +3 +3
SLT ––> MODEM +6 +5.5
SLT ––> MUSIC +1 +5.5
SLT ––> CONF +1 +5.5
SLT ––> DVMS +6 +5.5
SLT ––> 3-WAY +0 +6
SLT ––> PRI +3 +3
SLT ––> DKT/DST/FlexSet +1 +5.5

/IP
SLT ––> TWL +6 +5.5
SLT ––> iDSP +1 +5.5
MAGNETO ––> SLT -1.5 +0
MAGNETO ––> MAGNETO -1.5 +0
MAGNETO ––> EKT -1.5 +0

MAGNETO ––> VDK -1.5 +0
MAGNETO ––> LS/GS +3.5 +0
MAGNETO ––> E&M +0.5 +0
MAGNETO ––> DID +3.5 +0
MAGNETO ––> ALS70 +3.5 +0
MAGNETO ––> DGTL_TRK +0.5 -2.5
These column titles do not appear on the PI terminal screen but are given as an aid to
understanding this table.

“--” indicates that connections cannot be made between the relevant type of ports.
The port gain definition remains as defined in Feature Control.
* Special Gains for different countries are given in Table 19-4.
19-6

  
 
rcv_gain xmit_gain
MAGNETO ––> MODEM +3.5 +0
MAGNETO ––> MUSIC -1.5 +0
MAGNETO ––> CONF -1.5 +0
MAGNETO ––> DVMS +3.5 +0
MAGNETO ––> 3-WAY -2.5 +0.5
MAGNETO ––> PRI +0.5 -2.5
MAGNETO ––> DKT/DST/FlexSet -1.5 +0

/IP
MAGNETO ––> TWL +3.5 +0
MAGNETO ––> iDSP +0 +0
EKT ––> SLT -6 +0
EKT ––> MAGNETO -6 +0
EKT ––> EKT -6 +0
EKT ––> VDK -6 +0
EKT ––> LS/GS +4 +0
EKT ––> E&M +1 +0
EKT ––> DID +4 +0
EKT ––> ALS70 +4 +0
EKT ––> DGTL_TRK -4 -2.5
EKT ––> MODEM +4 +0
EKT ––> MUSIC -2 +0
EKT ––> CONF -6 +0

EKT ––> DVMS -2 +0
EKT ––> 3-WAY -6 +0.5
EKT ––> PRI -4 -2.5
EKT ––> DKT/DST/FlexSet -6 +0

/IP
EKT ––> TWL +4 +0

These column titles do not appear on the PI terminal screen but are given as an aid to
19-7

  
 
rcv_gain xmit_gain
EKT ––> iDSP +0 +0
VDK ––> SLT -6 +0
VDK ––> MAGNETO -6 +0
VDK ––> EKT -6 +0
VDK ––> VDK -6 +0
VDK ––> LS/GS +4 +0
VDK ––> E&M +1 +0
VDK ––> DID +4 +0
VDK ––> ALS70 +4 +0
VDK ––> DGTL_TRK -4 -2.5
VDK ––> MODEM +4 +0
VDK ––> MUSIC -2 +0
VDK ––> CONF -6 +0
VDK ––> DVMS -2 +0
VDK ––> 3-WAY -6 +0.5
VDK ––> PRI -4 -2.5
VDK ––> DKT/DST/FlexSet -6 +0

/IP
VDK ––> TWL +4 +0
VDK ––> iDSP +0 +0
LS/GS ––> SLT +0.5 +0
LS/GS ––> MAGNETO +0.5 +0

LS/GS ––> EKT +0.5 +0
LS/GS ––> VDK +0.5 +0
LS/GS ––> LS/GS +0.5 +0
LS/GS ––> E&M +0.5 +0
LS/GS ––> DID +0.5 +0
LS/GS ––> ALS70 +0.5 +0

19-8

  
 
rcv_gain xmit_gain
LS/GS ––> DGTL_TRK +0.5 +0.5
LS/GS ––> MODEM +0.5 +0
LS/GS ––> MUSIC +0.5 +0
LS/GS ––> CONF +0.5 +6
LS/GS ––> DVMS +0.5 +0
LS/GS ––> 3-WAY -2.5 +3.5
LS/GS ––> PRI +0.5 +0.5
LS/GS ––> DKT/DST/FlexSet +0.5 +0

/IP
LS/GS ––> TWL +0.5 +0
LS/GS ––> iDSP +0 +0
E&M ––> SLT -2.5 +0
E&M ––> MAGNETO -2.5 +0
E&M ––> EKT -2.5 +0
E&M ––> VDK -2.5 +0
E&M ––> LS/GS +0.5 +0
E&M ––> E&M +0.5 +0
E&M ––> DID +0.5 +0
E&M ––> ALS70 +0.5 +0
E&M ––> DGTL_TRK +0.5 +0.5
E&M ––> MODEM +0.5 +0
E&M ––> MUSIC -2.5 +0

E&M ––> CONF -2.5 +2
E&M ––> DVMS +0.5 +0
E&M ––> 3-WAY -5.5 +0.5
E&M ––> PRI +0.5 +0.5
E&M ––> DKT/DST/FlexSet -2.5 +0

/IP

19-9

  
 
rcv_gain xmit_gain
E&M ––> TWL +0.5 +0
E&M ––> iDSP +0 +0
DID ––> SLT +0.5 +0
DID ––> MAGNETO +0.5 +0
DID ––> EKT +0.5 +0
DID ––> VDK +0.5 +0
DID ––> LS/GS +0.5 +0
DID ––> E&M +0.5 +0
DID ––> DID +0.5 +0
DID ––> ALS70 +0.5 +0
DID ––> DGTL_TRK +0.5 +0.5
DID ––> MODEM +0.5 +0
DID ––> MUSIC +0.5 +0
DID ––> CONF +0.5 +0
DID ––> DVMS +0.5 +0
DID ––> 3-WAY -2.5 +3.5
DID ––> PRI +0.5 +0.5
DID ––> DKT/DST/FlexSet +0.5 +0

/IP
DID ––> TWL +0.5 +0
DID ––> iDSP +0 +0
ALS70 ––> SLT +0.5 +0

ALS70 ––> MAGNETO +0.5 +0
ALS70 ––> EKT +0.5 +0
ALS70 ––> VDK +0.5 +0
ALS70 ––> LS/GS +0.5 +0
ALS70 ––> E&M +0.5 +0
ALS70 ––> DID +0.5 +0

19-10

  
 
rcv_gain xmit_gain
ALS70 ––> ALS70 +0.5 +0
ALS70 ––> DGTL_TRK +0.5 +0.5
ALS70 ––> MODEM +0.5 +0
ALS70 ––> MUSIC +0.5 +0
ALS70 ––> CONF +0.5 +6
ALS70 ––> DVMS +0.5 +0
ALS70 ––> 3-WAY -2.5 +3.5
ALS70 ––> PRI +0.5 +0.5
ALS70 ––> DKT/DST/FlexSet +0.5 +0

/IP
ALS70 ––> TWL +0.5 +0
ALS70 ––> iDSP +0 +0
DKT/DST/FlexSet ––> SLT -5 +0
DKT/DST/FlexSet ––> MAGNETO -5 +0
DKT/DST/FlexSet ––> EKT -5 +0
DKT/DST/FlexSet ––> VDK -5 +0
DKT/DST/FlexSet ––> LG/GS +0 +0
DKT/DST/FlexSet ––> E&M -3 +0
DKT/DST/FlexSet ––> DID +0 +0
DKT/DST/FlexSet ––> ALS70 +0 +0
DKT/DST/FlexSet ––> DGTL_TRK -3 -2.5
DKT/DST/FlexSet ––> MODEM_POOL +0 +0

DKT/DST/FlexSet ––> MODEM +0 +0
DKT/DST/FlexSet ––> MUSIC +0 +0
DKT/DST/FlexSet ––> CONF -5 +0
DKT/DST/FlexSet ––> DVMS +0 +0
DKT/DST/FlexSet ––> 3-WAY -6 +0.5
DKT/DST/FlexSet ––> PRI -3 -2.5

19-11
Table 19-3: Default Gain Table*

  
 
rcv_gain xmit_gain
DKT/DST/FlexSet ––> DKT/DST/FlexSet -5 +0
/IP
DKT/DST/FlexSet ––> TWL +0 +0
DKT/DST/FlexSet ––> iDSP -7 +0
TWL ––> SLT +0.5 +0
TWL ––> MAGNETO +0.5 +0
TWL ––> EKT +0.5 +0
TWL ––> VDK +0.5 +0
TWL ––> LS/GS +0.5 +0
TWL ––> E&M +0.5 +0
TWL ––> DID +0.5 +0
TWL ––> ALS70 +0.5 +0
TWL ––> DGTL_TRK +0.5 +0
TWL ––> MODEM +0.5 +0
TWL ––> MUSIC +0.5 +0
TWL ––> CONF +0.5 +6
TWL ––> DVMS +0.5 +0
TWL ––> 3-WAY -2.5 +3.5
TWL ––> PRI +0.5 +0.5
TWL ––> DKT/DST/FlexSet +0 +0

/IP
TWL ––> TWL +0.5 +0

TWL ––> iDSP +0.5 +0

 
DGTL_TRK ––> ANY PORT —— ——
 
CONF ––> ANY PORT TYPE —— ——
DVMS ––> ANY PORT TYPE -6 +6
MODEM ––> ANY PORT TYPE +0 +0

 
3-WAY ––> ANY PORT TYPE —— ——

19-12
Table 19-3: Default Gain Table* continued
  
 
rcv_gain xmit_gain
MUSIC ––> ANY PORT TYPE +0 +0
 
ANY PORT ––> MODEM POOL —— ——
PRI ––> ANY PORT TYPE +0 +0

 
TBR ––> ANY PORT TYPE —— ——
ANY PORT ––> TBR ——

 ——

iDSP ––> ANY PORT TYPE +0 +0
IP endpoints ––> ANY PORT TYPE -7 +0

19-13
Table 19-4: Default Gain Table - Special Gains by Country continued

Source* To* Destination* Source Receive Source Trans-
xmit/rcv card Gain mit Gain
rcv_gain* xmit_gain*
CC0 - USA
SLT ––> DGTL_TRK -3
SLT ––> PRI -3
MAGNETO ––> DGTL_TRK -5.5
MAGNETO ––> PRI -5.5
EKT ––> DGTL_TRK -6
EKT ––> PRI -6
VDK ––> DGTL_TRK -6
VDK ––> PRI -6
LS/GS ––> DGTL_TRK -2.5 +3.5
LS/GS ––> PRI -2.5 +3.5
E&M ––> DGTL_TRK -5.5
E&M ––> PRI -5.5
DID ––> DGTL_TRK -2.5 +3.5
DID ––> PRI -2.5 +3.5
MODEM ––> DGTL_TRK -6 -3
MODEM ––> PRI
DID ––> CONF +6
DID ––> PRI
DID ––> 3-WAY -2.5 +3.5
DID ––> DKT/DST/FlexSet 0
ALS70 ––> DGTL_TRK -2.5 +3.5
ALS70 ––> DKT 0
DKT/DST/FlexSet ––> SLT -7
DKT/DST/FlexSet ––> MODEM -7
DKT/DST/FlexSet ––> MUSIC -7
Eu0 - Netherlands
SLT ––> E&M +3.5

EKT ––> LS/GS -3
EKT ––> E&M -3
EKT ––> DID -3
EKT ––> ALS70 -3
EKT ––> MODEM -3
VDK ––> LS/GS -3
VDK ––> E&M -3
VDK ––> DID -3
VDK ––> ALS70 -3
VDK ––> MODEM -3
DID ––> CONF +6
Eu1 - Belgium
*These column titles do not appear on the PI terminal screen but are given as an aid to
19-14
Table 19-4: Default Gain Table - Special Gains by Country

SLT ––> ANY PORT -1 +6
MAGNETO ––> ANY PORT 3.5 +0.5
EKT ––> ANY PORT -6 +0.5
VDK ––> ANY PORT -6 +0.5
LS/GS ––> ANY PORT -2.5 +4
E&M ––> ANY PORT -4 +3
DID ––> ANY PORT -2.5 +4
ALS70 ––> ANY PORT -2.5 +4
TWL ––> ANY PORT -2.5
Eu2 - Germany
SLT ––> ANY PORT +0 +0
MAGNETO ––> ANY PORT -3.5 +0.5
EKT ––> ANY PORT -4.5 +0.5
VDK ––> ANY PORT -4.5 +0.5
LS/GS ––> ANY PORT +0 +0
DID ––> ANY PORT +0 +0
ALS70 ––> ANY PORT +0 +0
Eu3 - Spain or Eu8 - Czech Republic
SLT ––> ANY PORT +0 +0
MAGNETO ––> ANY PORT -3.5 +0.5
EKT ––> ANY PORT -4.5 +0.5
VDK ––> ANY PORT -4.5 +0.5
LS/GS ––> ANY PORT -1 -1
DID ––> ANY PORT -1 -1
ALS70 ––> ANY PORT -1 -1

TWL ––> ANY PORT
19-15
Table 19-4: Default Gain Table - Special Gains by Country

19-16
Feature Control ç ROOT,0,1,4

Feature Control (FEAT CTRL) allows defining transmission value levels for port
types (cards) not engaged in conversation, for example, dial tones, system tones,
DTMF tones, music, 4VS messages, etc. The list of Port Types and a description
of the related cards are listed below. When Feature Control is selected, the
following menu appears:
Table 19-5: Feature Control Gains
PORT_TYPE: Applied to Card Family:
0-SLT • Full size: 8/24SA, 8/16/24SLS, or 4/8/16SH card

• IPx 500 and CDRS/CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
1-MAGNETO 8SM, 8SMipx
2-EKT 2SK, 4SK, 8SK
3-VDK 2SD, 8SD, 4IAA
4-LS/GS_TRK • Full size: 4T-C, 8T-C, 4T-CID, 8T-CID, 4/8TPF, 4TMR-PF card
• IPx 500 and CDRS/CDRX 200E: 4/8T-Cipx, 4/8T-CIDipx, 4TMR-PFipx,
4TMR-PF-Gipx
• IPx Office: 4T Office, 8T Office, 4T-CID Office, 8T-CID Office
•
5-E&M_TRK 4TEM, 4TEMsl, 4TEMipx, 4TEM/S, 4TEMP/S
6-8DID_TRK 8DID, 8DID/S, 8DID/S-Z
7-ALS70_TRK 4ALS, 8ALS (Netherlands only)
8-MFR MFC tone Receiver and decoder ports:

• 16MFR card
Feature Control ROOT,0,1,4

9-DTMF DTMF Receiver and decoder ports:
8DTMF, 8DRCF, 8DRCM-2, 8DRCM, 4/8DTR,
Coral IPx 500 (8DRCF on MSBipx issue 0100X1000 and before).
• The DTMF ports provided by:
CDRS 200E,
Coral IPx 500 (URC2 on MSBipx issue 0200X1000 and later)
and Coral IPx Office (U-RMI Office and U-MR Office cards)
may be adjusted in the URC Card Database branch (CDB,11,2) and not in the
Feature Control. See DTMF GAIN on page 4-40.
19-17
Table 19-5: Feature Control Gains
10-DTD Dial tone Detector and call progress tone analyzer ports:
8DTD,
8DRCM-2,
8DRCM,
8DRCF,
Coral IPx 500M (8DRCF on MSBipx issue 0100X1000 and before).
• The DTD ports provided by:
CDRS 200E,
Coral IPx 500 (URC2 on MSBipx issue 0200X1000 and later)
and Coral IPx Office (U-RMI Office and U-MR Office cards)
may be adjusted in the URC Card Database branch (CDB,11,2) and not in the
Feature Control. See DTD GAIN on page 4-40.
11-RMI/ASU Music ports:

8DRCF, 8DRCM-2, 8DRCM, RMI, ASU,
CDRS 200E Main Cage,
Coral IPx 500M Main Cage,
Coral IPx Office (U-MR Office, MR Office, RMI Office or U-RMI
Office).
12-DVMS 4VS, 4VSN
13-N/A Not Available
14-BID_TRK 4BID, 8BID (Belgium only)
15-GID_TRK 4GID, 8GID (Germany only)
16-DKT/DST/GK 8/16SKD, 8SVD, 8/16/24SDT, 8/16/24SFT, 8/16/24SFT Office,

T/ 4S8F Office, 8S8F Office, 4S16F Office, 8S16F Office, 8/16SFTipx,
FlexSet 8/16SFTsl, 8F8Ssl
17-PRI PRI-23, PRI-30, PRI-23sl, PRI-30sl, UDTipx (PRI-23), PRI-30ipx,

PRI-30 Office, UDT Office (PRI-23), 2DT(PRI-23/30),
2DTipx(PRI-23/30), 2DT Office (PRI-23/30)
18-TWL 4TWL, 4TWLsl, 4TWLipx

At the asterisk (*), enter the number of the required port type and press [CR] to
display the following programmable options:
RCV. GAIN -6dB..+6dB(in increments of 0.5dB);

Default: See Table 19-6 and Table 19-7
Programs the receiving side gain for the selected port.
TX. GAIN -6dB..+6dB(in increments of 0.5dB);

Default: See Table 19-6 and Table 19-7
Programs the transmit side gain for the selected port.
The following fields are additional attributes available for cards with C1 only:
19-18
BYTE1  The system automatically skips this parameter
BALANCE_NETWORK  The system automatically skips this parameter
SIGNALLING  The system automatically skips this parameter
19-19
Table 19-6: Port Type - Default Transmission Codes

Port_Type Transmission Relevant for Cards with C1
Gains (dB)

RCV.GAIN TX.GAIN BYTE1 BALANCE SIGNALLING
NETWORK
0- SLT +6 +6 80H 1 AFH
1- MAGNETO +3.5 +0 80H 2 AFH
2- EKT -2 +0 80H 2 B9H
3- VDK -2 +0 80H 2 B9H
4- LS/GS_TRK +0.5 +0 80H 4 BFH
5- E&M_TRK +0.5 +0 80H 0 AOH
6- 8DID_TRK +0.5 +0 80H 4 AFH
7- ALS70_TRK +0.5 +0 80H 4 BFH
8- MFR -6 -6 FFH -- FFH
9- DTMF +0 -6 80H 0 AOH
10- DTD +3 -6 80H 0 AOH
11-RMI/8DRCM/ +0 +0 80H 0 BBH
8DRCF
12- DVMS -6 +6 80H 0 AFH
13- N/A
14- BID_TRK -2.5 +0 80H 4 BFH
15- GID_TRK +0.5 +0 80H 4 BFH
16- DKT/DST/ -6 +0 FFH -- FFH
GKT/FlexSet
17- PRI +0 +0 FFH -- FFH
18- TWL +0.5 +0 80H 4 AFH
19-20
Table 19-7: Transmission Codes for European System
Port_Type Transmission Gains (dB)
Rcv.Gain Tx.Gain
Eu1 - Belgium
0 - SLT +3
4 - LS/GS_TRK -2.5
15 - GID_TRK +0
Eu2 - Germany
0 - SLT +0 -3
1 - MAGNETO -3.5
2 - EKT -4.5 +0.5
3 - VDK -4.5 +0.5
4 - LS/GS_TRK +0
5 - E&M_TRK -4 +3
6 - GID_TRK +0
Eu3 - Spain
0 - SLT +0 -3
1 - MAGNETO -3.5
2 - EKT -4.5 +0.5
3 - VDK -4.5 +0.5
4 - LS/GS_TRK -1 -1
5 - E&M_TRK -4 +3

6 - 8DID_TRK -1 -1
7 - ALS70_TRK -1 -1
14 - BID_TRK -1 -1
15 - GID_TRK -1 -1
19-21
Personal Port Gain, Compensation: Ports ç ROOT,0,2,3,0

This option enables fine tuning the gain control for each individual port. Gain
compensation can be above or below the value entered into the general Port Gain
Table, see Tables 19-3 and 19-4. Each port can be assigned with one of the
thirty-two GAIN_COMP elements defined in Personal Port Gain, Compensation:
Comp. Each element has a separate receive (RCV) and transmit (TRX) gain
compensation.
 In the Gain Comp. element table, the default for all ports is 0.
After this route is selected the following options appear:
FROM/TO DIAL Any system port dial number

All system ports
Enter the range of required port dial numbers for updating the Personal Port Gain.
GAIN_COMP# 0..31
Enter the new gain compensation element number.
Personal Port Gain, Compensation: Ports ROOT,0,2,3,0
19-22
Personal Port Gain, Compensation: Comp ç ROOT,0,2,3,1

This option defines a set of thirty-two GAIN_COMP elements. These elements apply
to all system ports. When adjusted by the proper values, these compensating
elements can either increase or decrease the port’s personal gain as required.
 GAIN_COMP Element #0, the default element is constantly rated at 0dB

and cannot be changed. When a port requires modification, first check to
see whether existing elements may be used instead. If an existing element
can not be used, then program the next non-zero element.
FROM 0..31
TO 0..31
GAIN_COMP#
Enter the range of elements by entering the first and last element required for
programming.
A notice appears stating that gain compensation values are denoted in decibels.
RCV -18dB..+12dB (in increments of 0.5dB)

Comp #0, 3-31 = 0dB
Comp #1 = -0.5dB
Comp #2 = +1dB
Enter the receiving gain compensation value for fine adjustment.
Personal Port Gain, Compensation: Comp ROOT,0,2,3,1

TRX -18dB..+12dB (in increments of 0.5dB)
Comp #0, 3-31 = 0dB
Comp #1 = -0.5dB
Comp #2 = +1dB
Enter the transmitting gain compensation value for fine adjustment.
 The full range is used by cards equipped with SICOFI components. Other
cards with C1 automatically cut the gain to a range of +6dB to -6dB.
19-23
Balancing Network ç ROOT,0,2,2

The Balancing Network menu provides control of the side tone (returned signal)
for all system ports except for digital ports. Balancing Network values should be
changed only when users are experiencing trunk volume problems, oscillations,
high side tones or DTMF dialing problems. Generally the first balance value to
change is the destination side (trunk or far extension).
 Some trunk interfaces may also be controlled by a jumper (600/900on

the Coral trunk. When a jumper is used, the default 600 strap should be
selected for some loaded lines. 900 can be used with the default Balance
Network values. (See Installation Manual).
FROM/TO DIAL Any system port dial number;

All system ports
Enter the range of required port dial numbers for updating the Balancing Network.
VALUE 0..2..7 (See Tables 19-8, 19-9 and 19-10)

4/8/16SH: Eu2, Eu3, CC1, ROW = 1
Enter the required Balancing Network values.
SEND_TO_PORT? Yes/No
Enables sending new values while conversing in order to check in real time
whether the new values are acceptable. If Y is not entered, the new values are added
when a new call is attempted.
Balancing Network ROOT,0,2,2
19-24
Table 19-8: Balancing Network Values: Cards with CI

Card Type Value Description
16SH,8SH,4SH,16S,8S,4S 1 Default value only
8SK,4SK,2SK 2 Default value only
8SM,8DID,4T,8T,4TEM(2W) 1 For loaded lines with
card strapped to 900
2 0 to 0.4 km
3 0.4 to 0.8 km
4 0.8 to 1.2 km
5 1.2 to 2 km
6 2 to 3 km
7 Above 3 km
4TEM(4W),RMI,4VS,4VSN,8SD 0 Disable Balance Network
 Notes (1-5):
1) Normally, these values are used according to length of the
communication lines, as shown on the right side of the table.
2) All values refer to 24 gauge wire (0.5mm), for other wire gauges use
the next value.
3) Four wire 4TEM (4W) E&M trunks require Balancing Network code 0.
4) Digital cards (2SD,8SD, 4IAA, 8SVD, 8/16SKK, 2/4SKW, 8/16/24SFT,
8/16/24SFT Office, 4S8F Office, 8S8F Office, 4S16F Office,
8S16F Office, 8/16SFTipx, 8/16SFTsl, 8F8Ssl, PRI-23, PRI-30,
PRI-23ipx, PRI-30ipx, PRI-23sl, PRI-30sl, PRI-30 Office,
UDT(PRI-23), 4TBR, 8TBR, 8TBRP, 4TBRipx, 8TBRipx, 8TBRPipx,
4TBRsl, 8TBRsl, 8TBRPsl, 4TBR Office, T1, T1ipx, T1ipx, UDT(T1),
30T, 30Tipx, 30Tsl, 30T/E, 30T/M, 30T/x, 30T Office (30T or 30TM
jumper selection,

2DT(T1/30T/30TM/PRI23/PRI30),
2DTipx(T1/30T/30TM/PRI23/PRI30),
2DT Office(T1/30T/30TM/PRI23/PRI30)),
4VS, 4VSN, 8DRCM-2, 8DRCM, 8DRCF, URC and CNF) do not have
any balancing networks.
Do NOT change the network values for these ports.
5) 600/900W jumper placed only on 4T, 8T, 4TPF, 4TMR and 4TEM
cards.
19-25
Table 19-9: Balancing Network Values: Cards with SICOFI
Value
Card
1 2 3/4 5/6 7 Ø*
USA (CC0), ISRAEL & ROW (CC1), Mexico (CC2), Netherlands (Eu0)
4,8,16SH/S 0 - 0.4 km 0.4 - 1.2 km 1.2 - 2.8 km >2.8 km >2.8 km 0.5
4,8SK/S 0 km + 600† 0 - 0.4 km 0.4 - 1.6 km 1.6 - 4 km 1.6 - 4 km 0.5
8SM/S, 8SMipx 0.4 - 1.2 km 0 - 0.4 km 1.2 - 2.8 km 2.8 - 4 km >4 km 0.5
4,8T/S Loaded Line 0 - 0.4 km 0.8 - 1.6 km 1.6 - 3.6 km >3.6 km 0.5
ALS70 Loaded Line 0 - 0.4 km 0.8 - 1.6 km 1.6 - 3.6 km >3.6 km 0.5
4TEM/S 0.4 - 1.2 km 0 - 0.4 km 1.2 - 2.8 km 2.8 - 4 km >4 km 0.5
8DID/S 0.4 - 1.2 km 0 - 0.4 km 1.2 - 2.8 km 2.8 - 4 km >4 km 0.5
Belgium (Eu1)
4,8,16SH/S 0 - 0.4 km + 0 km 0.4 - 1.2 km 1.2 - 2.4 km >2.4 km 0.5
600
4,8T/S Loaded Line 0 - 0.4 km 0.8 - 1.6 km 1.6 - 4 km >3.6 km 0.5
4TEM/S 1.5 km, 0.6mm 0 km 1.5km, 3.5 km, 3.5 km, 0.5
0.4mm 0.6mm 0.4mm
8SM/S, 8SMipx 1.5 km, 0.6mm 0 km 1.5km, 3.5 km, 3.5 km, 0.5
0.4mm 0.6mm 0.4mm
Germany (Eu2), Spain (Eu3), Australia (Eu6)

4,8,16SH/S 0 km - COMP‡ 0 km + 3 km + 3 km - 3 km - 0.4
600 600W COMP COMP
4,8SK/S 0 km +600
† 0 - 0.4 km 0.4 - 1.6 km 1.6 - 4 km 1.6 - 4 km 0.5
8SM/S, 8SMipx 1.5 km, 0.6mm 0 km 1.5km, 3.5 km, 3.5 km,
0.4mm 0.6mm 0.4mm
4,8T/S 1.5 km, 0.6mm 0 km 1.5km, 3 km, 3.5 km,

0.4mm 0.6mm 0.4mm
4GID, 8DID/S 1.5 km, 0.6mm 0 km 1.5km, 3.5 km, 3.5 km,
0.4mm 0.6mm 0.4mm
4TEM/S 1.5 km, 0.6mm 0 km 1.5km, 3.5 km, 3.5 km,

0.4mm 0.6mm 0.4mm
* Wire diameter in millimeters

† These items are used only in the laboratory.
Do NOT enter or use these values.
‡ COMP: Complex impedance.
19-26
Table 19-10: Balancing Network Values: Cards With SICOFI-4
Card* VALUE
0 1 2 3/4 5/6 7 Ø
USA (CC0)
* see below Disable 0-0.4 km 0.4-1.2 km 1.2 -2.8 km >2.8 km >2.8 km 0.5
Balance
Network‡
Belgium (Eu1)
* see below Disable 0-0.4 km 0-0.4 km 0.4-1.2 km 1.2 -2.8 km >2.8 km 0.5
Balance
‡
Network
Germany (Eu2), Spain (Eu3), Australia (Eu6)
* see below Disable 0-0.4 km 0.4-1.2 km 1.2 -2.8 km >2.8km >2.8 km 0.4
Balance
‡
Network
Israel & ROW (CC1), Netherlands (Eu0), Mexico (CC2)
* see below Disable 0-0.4 km 0.4-1.2 km 1.2 -2.8 km >2.8 km >2.8 km 0.5
Balance
‡
Network
* Full size: 8/24SA, 8/16/24SLS, or 4/8/16SH card

IPx 500 and CDRS/CDRX 200E: 8/16/24SAipx or 8/16SLSipx card
IPx Office: 4/8/16/24SA Office, 4/8/20S Office, 4SA+8Fx Office, 4SA+16Fx Office, 8SA+8Fx Office or
8SA+16Fx Office card
† Wire diameter in millimeters

‡ These items are used only in the laboratory.
Do NOT enter or use these values.
19-27
19-28
20 Wakeup
This chapter describes the programming options available for the Wakeup feature.
See also, System Features - Hotel beginning on page 6-41.
Wakeup Control ..........................................................................................20-2

Wakeup Report ...........................................................................................20-4
20-1
Wakeup PI Reference Manual
Wakeup Control ç WAKEUP,0 [3,3,0]
When Wakeup Control is selected, the following report switches can be utilized
whether or not an actual report is printed out. Samples of various wakeup reports
are shown further on in this chapter.
SORT_BY [0] S (Station)/T (Time)

When set to T, enables printing Wakeup reports sorted by the requested wakeup
hour. When set to S, the Wakeup reports remain sorted by station numbers.
 Sample on-line reports are shown on page 20-4 and on page 20-5.
DISPLAY:
NEW/CANC [1] Yes/No

Determines whether or not a new wakeup request or canceled request is printed.
FAIL [2] Yes/No

Determines whether or not a failed wakeup attempt is printed.
SUCCESS [3] Yes/No

Determines whether or not a successful wakeup attempt is printed.
Wakeup Control WAKEUP,0 [3,3,0]
20-2
PI Reference Manual Wakeup
DEST [4] 1..24 for Serial or Modem port (see Table 17-2 on page 17-11)
Determines the output terminal destination for the wakeup report.
The Announcer destination ANN_DEST [0] is defined in SFE - Hotel (see page
6-41).
.
NUMBER_OF_ 1..80..65534 or 0 (Header not printed)

RECORDS_PER_
Sets the number of wakeup records sent to a printer before a form feed (FF)
PAGE [5]
command causes the paper to advance to a new sheet (page) and a new header to
be printed.
 Zero (0) turns the header off.

Hint: An 11” page typically contains 66 lines. However, it is good practice to
choose a page that is somewhat less than 11” (10.5”) so that the text does not run
off the page.
Wakeup Control WAKEUP,0 [3,3,0]
20-3
Wakeup PI Reference Manual
Wakeup Report ç WAKEUP,1 [3,3,1]
Wakeup reports are used to select stations that are required for display or printing
on demand. The following material is not presented as a programming option, but
is provided for tutorial and system maintenance purposes only.
When the Wakeup Report is selected the option is available for selecting a range of
stations:
FROM/TO STATION # All defined station numbers

Enter station numbers FROM the lowest required station number TO the highest.
Choose all station numbers by pressing [CR].
When printing is carried out at a terminal other than from where the request
originated, the following two messages appear:
*** WAKEUP REPORT START ***The Wakeup report is starting to
print.
*** WAKEUP REPORT END *** The Wakeup report has completed
printing.
Printing is carried out at the terminal defined in DEST [4] (page 20-3) in the Wakeup
Control branch.
The Wakeup Report can be sorted by either Station number or the requested
Wakeup hour by selecting S (Station) or T (Time) in SORT_BY [0] (page 20-2) in the
Wakeup Control branch.
A sample Wakeup report sorted by station number is given below:
WAKE-UP REPORT
DATE 12/31/02
Wakeup Report WAKEUP,1 [3,3,1]
ST# W_U_TIME ST# W_U_TIME
Eli 08:05 PM Eli 12:15 AM
202 12:00 PM 203 05:00 AM
Pearl 06:00 AM Pearl 12:02 PM
401 12:00 PM 404 10:00 PM
Orly 11:50 AM 406 12:00 PM
On-Line Reports
Several different types of on-line reports are available: New/Canceled, Fail,
Success. The type of report depends upon how DISPLAY is defined in Wakeup
Control (see page 20-2). When a wakeup request is unfulfilled, the report includes
the reason for the failure, for example: busy, no answer, lock-out, undefined. A
sample on-line report is presented below:
20-4
PI Reference Manual Wakeup
DATE TIME INFORMATION ST W U TIME
09/18/01 03:42 PM NEW ENTRY ELI 11:05 PM
12/27/01 03:30 PM CONFIRM 5303 06:30 AM
03/23/02 07:32 PM FAIL PEARL 06:31 AM NO ANSWER
01/27/02 08:33 PM FAIL 80009876 07:32 AM BUSY
 The reports shown in this chapter are not actual printouts, but are replicas
of the types of reports available and are presented in the interest of clarity.
20-5
PI Reference Manual
Wakeup
20-6
21 Special System Options-
Database Control
& Duplication Systems
This chapter describes the software devices that are used to control the type of
information that is stored on the system memory.
Additionally, this chapter also explains the operation of the Coral duplication
system.
Database Control ........................................................................................21-2
First Initialization .......................................................................................21-3
Backup ........................................................................................................21-4
Database Control: Disk (FlexiCom 6000, IPx 4000) ................................21-5
Database Control: FLASH (IPx Office, FlexiCom 200,300,400,5000, IPx
500,800,3000, CDRS 200E).....................................................................21-12
Duplication (FlexiCom 5000 and IPx 3000 dual control).......................21-19
HSB (FlexiCom 6000/R and IPx 4000/R redundant control) .................21-24
21-1
Special System Options- Database Control & Duplication Systems PI Reference Manual
Database Control ç ROOT,0,10

Database Control provides the means for controlling and monitoring the activities
and state of the different types of system-wide databases. Through Database
Control the system can be returned to either the default Database or to the latest
versions of database backup as required. This option also serves as a backup to
flash memory, thereby providing the ultimate in system protection.
Coral System Type Control Flash Mem- Storage

Card Type ory Card Capacity
Type
IPx 500 MCP-IPx2 IMC8 8 MB

CDRS 200E
FlexiCom 400 (with HDC controller), 5000 MEX-IP2 IMC8/IMC16* 8/16 MB

IPx 800, 3000
FlexiCom 6000, IPx 4000 MCP-ATS CFD 64 MB
IPx Office MCB Office IMC8 8 MB

* An IMC16 card is required (Coral Software Version 15 and higher)
when the database exceeds 1.5MB
The basic options in Database Control for controlling backup and restore
operations on flash memories of the FMsl, CFD and IMC8/16 and are presented
below. First Initialization and Backup are discussed in greater detail on the
following pages.
Branch Option Description Page
0 - First Initialization Returns the database and Size Tables to default. 21-3
1- Last Power Fail Displays the time and date of last system power
Database Control ROOT,0,10
initialization. Display is according to the

format defined in SFE, DATE_MODE (Eu/USA)
[16] (page 6-24).
2- Backup Allows entry to the backup and restore 21-4
facilities.
21-2
PI Reference Manual Special System Options- Database Control & Duplication Systems
First Initialization ç ROOT,0,10,0

When First Initialization is performed, the system database returns to the default
values, excluding Installation and Feature Authorization, see Chapter 3.
Sizes/URC/Music/Units Definition values (Chapter 4) can be saved or returned to
default sizes.
RETURN TO DEFAULT Yes/No

SIZES? To exit this node, type [CTRL]-U, [ESC] or any direct access abbreviation
Executes system initialization by either returning to default sizes or saving the last
update sizes. This option is only displayed when system sizes have been modified.
N: Installation, Sizes definition, Size Table and the MAX_DVMS_MSG [9] fields in
SFE will be saved.
Y: All system databases, excluding Installation, will return to default sizes.
ARE YOU SURE? Yes/No

** WARNING **: first initialization will be performed
(Y/N)?
ARE YOU SURE? is a prompt to help protect against accidentally initializing the
system. This allows backing out of the initialization procedure at the last moment.
! Entering Y initializes the system causing:

1. The system database (including or excluding Installation and Sizes
as defined in the parameter above) to return to their default values.
3. All calls to be dropped.
4. All keyset (FlexSet 120S, 280S, 121S, 281S;
First Initialization ROOT,0,10,0

21-3
I
Backup ç ROOT,0,10,2
During normal operation, the system configuration database is saved to a file on the
Flash memory permanent storage. A saved database file may be loaded (restored)
at any time.
The system database is located on a protected RAM and is saved on the flash
memory of the control card. The two database files DB0.DEF and DB1.DEF are
saved on a flash memory. DB0.DEF is used for the daily backup performed
automatically at a preset time (usually every day), while DB1.DEF is used for
manual backups performed by the technician.
File Name Code Description
DB0.DEF 0 Daily backup automatically at a preset time.
DB1.DEF 1 Technician copy for manual backup.
The options in Database Control for controlling backup and restore operations for
Coral FlexiCom systems are presented below. They are discussed in on the
following pages.
Branch Option Relevant for Coral systems: Page
0- DISK FlexiCom 6000 21-5

IPx 4000
1- TAPE Not Used NA

(DX SYSTEMS ONLY)
2- FLASH FlexiCom400, 5000 21-12

(SL/MEX/IPx Office ONLY) IPx 500, 800, 3000
IPx Office
Backup ROOT,0,10,2
CDRS 200E
21-4
C
Database Control: Disk (FlexiCom 6000, IPx 4000) ç ROOT,0,10,2,0
The following table presents the options in Database Control for controlling Coral
FlexiCom 6000 or Coral IPx 4000 operations. A more detailed explanation is given
on the following pages.
0- SAVE Copies the system database to the CFD. 21-6

DATABASE
1- EXCHANGE Not Used NA

DB0/DB1
2- LOAD Loads the system database DB0.DEF (or 21-7

DBS DB1.DEF) from the CFD card.
3- COPY Copies a file(s) on the CFD to a new file 21-8

FILES on the same CFD.
4- SHOW Displays all current CFD files with 21-10

DIR information about each file.
5- UPDATE Not Used NA

VERSION
6- AUTO Activates or deactivates the Auto Backup 21-11

BACKUP feature. Also sets auto backup time and
frequency.
In the Coral FlexiCom 6000 and Coral IPx 4000 system, the database is located on
Database Control: Disk (FlexiCom 6000, IPx 4000)

a battery backed up RAM on the 32GC card.
The CFD holds the nonvolatile copy of the database. Therefore when a database
system restore is needed, it is restored from the CFD to the system RAM on the
32GC card.
21-5
Save Database (FlexiCom 6000 and IPx 4000) ç ROOT,0,10,2,0,0

This option copies the current system database to the flash memory-CFD (Compact
Flash memory Disk) on the MCP-ATS card for Coral FlexiCom 6000 and Coral
IPx 4000 systems. For Coral FlexiCom 6000/R and Coral IPx 4000/R dual
controls, the system database is copied to both flash memories simultaneously
when Save is performed from the Active side.
DEST FILE # 0 (DB0.DEF), 1 (DB1.DEF)

Enter the destination file code. DB0.DEF is the file that is updated during the
Automatic Backup each day. DB1.DEF is an alternate destination file for manual
backups.
EXECUTE Yes/No
Enter Y to execute the Save Database command.
In a Hot Standby system, messages for both system sides appear on the Active
side. The Standby side also displays an appropriate message:
• Messages on Active side: DBS stored to DB1.DEF.
• Message on Standby side: DBS stored to DB1.DEF.
Executing a Save Command may take from a few seconds to a few minutes.
Therefore, changes to the system configuration (such as changing the system to
Night Service, setting a Call Forward or Do Not Disturb instruction at a station, or
even turning on or off the Background Music at a Keyset) cannot be completed
Save Database (FlexiCom 6000 and IPx 4000)
during the save operation, until the database save process is completed.
Attempting to activate such features are refused and invoke the following message
at the keyset display: DBS TEMPORARILY LOCKED!!!
21-6
Load DBS (FlexiCom 6000 and IPx 4000) ç ROOT,0,10,2,0,2

This option loads (restores) the backup database(s) from the CFD (flash memory)
to the system memory by loading the stored backup databases DB0.DEF(0) or
DB1.DEF(1) with a system restart.
When uploading from the technician’s backup file (DB1), the periodical backup
file (DB0) is transferred to the technician’s backup file.
In case of failure, the system is declared Faulty and tries to resume operation using
the most recent, available file.
FILE # 0, 1
Enter the source file code number.
0 (DB0.DEF) is the file from the last automatic Backup. 1 (DB1.DEF) is the file
from the last manual Save Database command performed by the technician.
EXECUTE Yes/No
Enter Y to execute the load database command.
Warning!:
During the loading process, the Coral system is off-line. Calls in progress are
interrupted and new call processing temporarily ceases, for a few seconds
to a few minutes depending on the size of the system. During this process,
the Coral system is non-operational. After the database is successfully
loaded into the database memory, the system executes a Partial Initialization
Load DBS (FlexiCom 6000 and IPx 4000) ROOT,0,10,2,0,2

and begins processing calls.
21-7
Copy Files (FlexiCom 6000 and IPx 4000) ç ROOT,0,10,2,0,3

This option allows copying a file(s) on the CFD (flash memory) to a new file on
the same CFD by copying one database CFD source over another destination file.
This may be necessary after making substantial changes to the system
configuration so that the technician copy and the daily backup copy of the database
are identical.
Copying the file from one source to the other destination is preferable to saving the
database twice, since making changes to the system database are not prohibited
during the copy process. Note that the copy process cannot be used to copy a
database file from one Flash card to another - only from one file to another on the
same Flash card.
The copying procedure is only possible from the Active side of a Hot Standby
system. However, messages indicating a successful copy appear on both system
sides.
0 - DATABASE The Database option allows copying a database file. When this option is selected,
a database SRC FILE # can be copied over a database DST FILE #.
1 - SELECT FILE The Select File option allows copying any file on the Flash memory card to another
file of the same type by using the entire name and extension of the file.
SOURCE FILE 0,1

Enter the code (for database) or full name with extension (for select file) of the
source file.
DEST FILE 0,1

Copy Files (FlexiCom 6000 and IPx 4000)
Enter the code (for database) or full name with extension (for select file) of the
destination file.
Codes:
0: DB0.DEF 1: DB1.DEF
21-8
EXECUTE Yes/No
Enter Y to execute Copy Files.
Copying files to a CFD generally takes a few seconds. When the copy is completed,
a confirmation message: DB0.DEF copied to DB1.DEF appears on the
active system side or on both sides of a Coral FlexiCom 6000/R or Coral IPx
4000/R redundant system:
WARNING!
Executing the copy command replaces the destination data with the source
data, thereby destroying the information currently in the destination file.
Make sure that the actual copying is performed over the required file.
Copy Files (FlexiCom 6000 and IPx 4000)
21-9
Show Dir (FlexiCom 6000 and IPx 4000) ç ROOT,0,10,2,0,4

This option displays all current CFD files with information about each file.
EXECUTE Yes/No
Enter Y to display the directory.
The directory display lists each file on the CFD (flash memory). The FILE_NAME
field identifies each file. The VERSION field indicates the age relative to other
files with the same data. For instance, in the example listed below, DB0.DEF is
version 2, so it is the most current database file. The LAST_DATE and LAST_
TIME fields indicate the last data (in US format: mm/dd/yy) and time the file was
written on the CFD. The FILE_STATUS field is only relevant for database files,
and indicates whether or not the file was written successfully.
Show Directory is possible on both sides of a duplication system.
disk directory
FILE_NAME VERSION LAST_DATE LAST_TIME FILE_STATUS
1: DB0.DEF 2 mm/dd/yy 1: 30: 4 OK
2: DB1.DEF 1 mm/dd/yy 14:00:10 OK
3: DUMP 8224 0/ 0/ 0 0: 0: 0 INVALID
4: PATCH 8224 0/ 0/ 0 0: 0: 0 INVALID
Show Dir (FlexiCom 6000 and IPx 4000) ROOT,0,10,2,0,4
21-10
Auto-Backup (FlexiCom 6000 and IPx 4000) ç ROOT,0,10,2,0,6

This option sets auto backup time and frequency.
The system database can be automatically saved to the CFD file at a preset time
each day. During automatic daily backup, the database is saved to the DB0.DEF
file.
NUMBER OF DAYS 1..7..255, N (for manual backup)

BETWEEN BACKUPS
Set the number of days between automatic backups. If no automatic backups are
needed, enter N for creating manual backups.
SET AUTO BACKUP 00:00 (Midnight)..1:30..23:59

TIME:
This parameter sets the time that the system performs its daily database
backup.Enter the time in a 24-Hour format, see Programming and Entering Time
Units (page 2-6).
Auto-Backup (FlexiCom 6000 and IPx 4000)
21-11
Database Control: FLASH (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS 200E) ç 0,10,2,2
The following pages present the options in Database Control for controlling Coral
400 (with HDC controller), 5000; Coral IPx Office, CDRS 200E, and Coral IPx
500, 800 and 3000 operations. A more detailed explanation is given on the
following pages.
Coral System Type Control Flash Storage

Card Type Memory Capacity
Card Type
IPx 500 MCP-IPx2 IMC8 8 MB

CDRS 200E
FlexiCom 400 (with HDC controller), 5000 MEX-IP2 IMC8/IMC16* 8/16 MB

IPx 800, 3000
FlexiCom 6000, IPx 4000 MCP-ATS CFD 64 MB
IPx Office MCB Office IMC8 8 MB

* An IMC16 card is required (Coral Software Version 15 and higher)
when the database exceeds 1.5MB
 Notes:
• IPx Office; IPx 500, 800, 3000; FlexiCom 300, 400, 5000; CDRS 200E:
The IMC8 has a total storage capacity of 8MB; 4MB are used for the software version
leaving 4MB for Database Control. However, the maximum recommended storage
capacity for the IMC8 is 3.8MB.
• FlexiCom 200; CDRS 200 systems: The FMsl has sufficient capacity to store two
copies of the system database for most systems. However, some larger systems
(database larger than 384K) may have a system configuration that is so large and
Database Control: FLASH (IPx Office, FlexiCom
complex, that only a single copy of the database can be stored. If the database is larger
than 384K, then only (DB0.DEF) is used and the Automatic daily backup cannot be
used (this prevents overwriting the only FMsl copy of the database).
0- SAVE Copies the system database to the IMC8/IMC16 21-13

card
1- LOAD DBS Loads the system database DB0.DEF (or 21-14

DB1.DEF) from the IMC8/IMC16 card.
2- SHOW FILE INFO Displays all files currently stored on the 21-15
IMC8/IMC16 card.
3- AUTO BACKUP Activates or Deactivates the Auto Backup feature. 21-16

Also sets auto backup time and frequency.
4- ERASE Erases the database files from the flash memory 21-17
on the IMC8/IMC16.
5- INIT DUMP FOR QUALIFIED PERSONNEL ONLY! 21-18
21-12
FLASH: Save (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS 200E) ç ROOT,0,10,2,2,0
This option copies the current system database to the flash memory of the
IMC8/IMC16/IMC4(FMsl) card.
DEST FILE 0 (DB0.DEF), 1 (DB1.DEF)

Enter the destination file code:
0: DB0.DEF, the file updated during the Automatic Backup each day.
1: DB1.DEF, the alternate file for manual backups, updated by the technician.
FlexiCom 200 systems:
If the database is larger than 384K, then only 0 (DB0.DEF) is used and the
Automatic daily backup cannot be used (this prevents overwriting the only FMsl
copy of the database).
EXECUTE Yes/No
Enter Y to execute the Save Database command.
Saving the database to the Flash memory generally takes several minutes. While
the database is being saved, it is important to note that changes to the system
configuration are prohibited, such as changing the system to Night Service, setting
a Call Forward or Do Not Disturb instruction at a station, or even turning on or off
the Background Music at a Keyset, until the database save process is completed.
An attempt to change such a feature results in the following keyset message
display: DBS TEMPORARILY LOCKED!!!
FLASH: Save (IPx Office, FlexiCom 200,300,400,5000, IPx

Other possible error messages while attempting to save:
Error Message Explanation
NO SPACE FOR SAVING DATABASE The Flash memory space is

insufficient.
CORRUPTED DBS Unrecognizable file number entry.
When the backup is ready to be saved, the following message appears:

Caution: Previous backup will be lost:
Proceed with backup (Y/N)? [N]
After selecting Y, the system tells you that it is SAVING... .
SAVE OK... The backup completed successfully.
SAVE FAILED!! The backup failed.
21-13
FLASH: LOAD DBS (IPx Office, FlexiCom 400, 5000, IPx 500, 800, 3000, CDRS 200E) ç ROOT,0,10,2,2,1
This option loads (restores) the backup database from the

IMC8/IMC16/IMC4(FMsl) card to the MEX-IP2/MCP-IPx2/Coral IPx Office to
the MCP-IPsl. Upon entering this option, the following message appears:
CAUTION: Database contents will be lost & system will
restart!!!
PROCEED WITH RESTORE (Y/N)? N...
Note that the original database stored in the system memory will now be
overwritten. Answer Y to proceed.
FILE # 0,1
Enter the source file code number.
0: DB0.DEF is the file from the last automatic Backup.
1: DB1.DEF is the file from the last manual Save Database command performed
by the technician.
EXECUTE Yes/No
After entering Y the system notifies you that it is Restoring and after a few
seconds gives one of the following messages:
Message Explanation
FLASH: LOAD DBS (IPx Office, FlexiCom 400, 5000, IPx 500,
Restore Successful. The database was loaded successfully.
Operation Denied; Load The technician tried loading DB1.DEF,

Available only from but DB0.DEF too large and there is no
DB0.DEF. memory space left for DB1.DEF.
Operation Denied; DB0.DEF The DB0.DEF database is corrupted.

is not OK.
Operation Denied; DB1.DEF The DB1.DEF database is corrupted.

is not OK.
WARNING!:
Loading the database takes a few minutes. During this process, the Coral
system is non-operational.
Calls in progress are interrupted and new call processing temporarily
ceases. After the database is successfully loaded into the database memory,
the system executes a Partial Initialization and begins processing calls.
21-14
FLASH: SHOW FILE INFO (IPx Office, FlexiCom 200,300,400,5000, IPx 500,800,3000, CDRS 200E)ROOT,0,10,2,2,2
This option displays the list of all files currently stored on the IMC8/IMC16 or
IMC4(FMsl) card.
Reading the directory from the Flash memory generally takes only a few seconds,
provided no other priority tasks are required of the Main Processor.
EXECUTE Yes/No
Enter Y to display the current list.
The display lists each file stored in the card. The FILE_NAME field identifies each
file. The VERSION field indicates the age relative to other files with the same data.
For instance, in the example listed below, DB0.DEF is version 2, so it is the most
current database file. The LAST_DATE and LAST_TIME fields indicate the last
date (in US format: mm/dd/yy) and time the file was written to the card. The FILE_
STATUS field is valid only for database files, and indicates whether or not the file
was written successfully.
disk directory
FILE_NAME VERSION LAST_DATE LAST_TIME FILE_STATUS
1: DB0.DEF 2 mm/dd/yy 1: 30: 4 OK
2: DB1.DEF 1 mm/dd/yy 14:00:10 OK
3: DUMP 8224 0/ 0/ 0 0: 0: 0 INVALID
FLASH: SHOW FILE INFO (IPx Office, FlexiCom
21-15
FLASH: AUTO BACKUP (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) ç ROOT,0,10,2,2,3
The system database can be automatically saved to the IMC8/IMC16 card at a
preset time each day. During automatic daily backup, the database is saved to the
DB0.DEF file.
NUMBER OF DAYS 1..7..255, N (for manual backup)

BETWEEN BACKUPS
Set the number of days between automatic backups. The default is set to 7 days
between backups, so that an automatic backup file is created every week. If no
automatic backups are needed, enter N for creating manual backups.
SET AUTO BACKUP 00:00 (Midnight)..1:30.. 23:59

TIME:
This parameter sets the time that the system performs its daily database
backup.Enter the time in military format, see Programming and Entering Time
Units (page 2-6).
FLASH: AUTO BACKUP (IPx Office, FlexiCom 400,5000, IPx
21-16
FLASH: ERASE (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) ç ROOT,0,10,2,2,4
This function enables the technician to erase either one or both of the backup
database files stored on the ICM8 card. Upon entering this option, the following
message appears:
CAUTION: Flash dbs backup will be lost!!!
PROCEED WITH ERASE (0/1/A/N)?
0 erases the DB0.DEF database.
1 erases the DB1.DEF database.
A erases both DB0.DEF and DB1.DEF.
N cancels the operation.
Upon entering 0, 1, or A, the system displays:
Erasing...
After a few seconds one of the following messages appear:
Erase Completed... An unsuccessful ERASE operation results in

the following message:
Erase Failed!! The procedure should be repeated if needed.
FLASH: ERASE (IPx Office, FlexiCom 400,5000, IPx
21-17
FLASH: INIT DUMP (IPx Office, FlexiCom 400,5000, IPx 500,800,3000, CDRS 200E) ç ROOT,0,10,2,2,5
QUALAFIED PERSONNEL ONLY!
This parameter should only be used by experienced technicians to erase the dump
file used for diagnostics. Activating this branch results in the following message:
Dump file will be erased!!!
PROCEED(Y/N)?
Enter Y to dump the file and N to retract.
If no dump was made, the following message is received upon activation:
No dump in system!
FLASH: INIT DUMP (IPx Office, FlexiCom 400,5000, IPx
21-18
Duplication (FlexiCom 5000 and IPx 3000 dual control) ç DUPLICATION [ROOT,0,11]
Duplication is operative only for Coral FlexiCom 5000 and Coral IPx 3000 systems
with dual control. In the fully duplicated configuration two 4GC cards are
interconnected through a special data link called “Super-Link” (see Figure 21-1 on
page 21-20). This link enables the two MEX-IP2 cards to communicate and operate
in a “load-sharing” mode.
The duplication configuration has three major conditions from the Master side,
plus the reverse (tag states) from the Slave side.
 Changes can only be made from the Master side.

The duplication system is comprised of two pairs of MEX-IP2 and 4GC cards, plus
a KB0 port installed in each MEX-IP2. One of each pair is designated Master, the
other pair as Slave. All 8DRCM-2 (RS-232 ports); and all RMI, 8DRCF and
8DRCM (RS-232 ports and modems) functions relate to the Master side. Each
condition is briefly described in the following table:
Master Side Slave Side Condition

Config. Explanation Config. Explanation
U Full duplication; Right Master U' Full duplication; Right OK
unit controls left slave unit; Slave unit controls left
MEX-IP2 and 4GC cards (U Tag) master unit; MEX-IP2 and
duplicated 4GC cards duplicated
L Left MEX-IP2 card functional L' Right MEX-IP2 card Abnormal
only in master unit; Slave unit functional only in slave condition.
not operative; 4GC card (L Tag) unit; Master unit not Adjust using
duplicated operative; 4GC card Diagnostic
duplicated Alarms
information,
I No duplication. I' No duplication. option 10-
Duplication (FlexiCom 5000 and IPx 3000 dual control)

Left Master unit operative RIght Slave unit operative DUPLICATION (pa
Slave side malfunctioning (I Tag) Master side ge 22-7).
malfunctioning
* “Master” refers to the logical (acting) master side. While the Physical Master is the system
control side jumpered as a master by default (usually the left side).
 Note:
The Coral FlexiCom 6000/R and Coral IPx 4000/R also offer a completely
redundant system (Hot Standby), with duplicate control sides and is
described at the end of this chapter, see HSB (FlexiCom 6000/R and IPx
4000/R redundant control) beginning on page 21-24.
21-19
DUPL  Yes/No (Read Only)

Shows whether or not the system is installed with duplication.
WT FOR TECH Yes/No (No = system is OK)

Wait for Technician option. Selecting Yes renders the Master MEX-IP2 inoperable
(the MEX-IP2 card is considered Faulty when not connected to the PI). Thus, the
system is “L” configured, with the secondary MEX-IP2 card controlling the full
system.
 An MEX-IP2 in the WT FOR TECH state, can be released by briefly

moving switch #2 (the second switch from the top), on the MEX-IP2 Slave
front panel, to the left and then instantly returning it to the original
position. This action causes the MEX-IP2 Slave unit to reset to Stand
Alone mode.
MASTER Yes/No
Yes indicates that the side addressed is acting as the Master side.
Selecting No on the Master side causes the system to go from U to U' or from U' to
U, depending upon which state the system is in at the time the change is made. This
option must be Yes while displaying through the Master KB0, or any other RMI,
8DRCM-2, 8DRCM, 8DRCF or other modem port.
Figure 21-1. IPx 3000 IPx 3000M IPx 3000M
Master Slave with Physical Slave Physical Master
Super Link- M M
J41 J41
U’ Configuration S S
Sketch
MEX-IP2 MEX-IP2
Duplication Cable
H219
4GC 4GC
FlexiCom 5000 MPG card JMP 1 MPG card JMP 1
Physical Slave Physical Master

M M
S S
MEX-IP2 MEX-IP2
Flat Cable
"Super-Link"
via MPG cards
4GC 4GC
21-20
STD ALONE SLAVE  Yes/No (Read-Only)

Identifies an out of service MEX-IP2 card that can be returned back to service. In
Stand Alone State, the system remains in either “L” or “I” configuration while the
MEX-IP2 slave is not functioning. In order to return to “U” configuration the
system must be initialized by changing the 2ND MEX-IP2 parameter on the Master
side.
2ND 4GC Yes/No
 If the second MEX-IP2 is active it will also be removed from the active
system.
Determines whether or not the 4GC card on the opposite control section is active.
Changing from No to Yes results in joining the second 4GC card to the active
system. Changing from Yes to No results in removing the second 4GC and
MEX-IP2 card from the active system. The system may itself change from Yes to
No when the Slave side is malfunctioning. This option must be Yes while making
a change though the Slave KB0.
2ND MCP Yes/No

Determines whether or not the MEX-IP2 card on the opposite control section is
active. Changing from No to Yes results in joining the second MEX-IP2 card to the
active system. Changing from Yes to No results in removing the second MEX-IP2
card from the active system.
This option must be Yes while displaying through the Slave KB0.

MASTER STRAP  Yes/No (Read-Only)
Default: Left side: Yes; Right side: No.
Indicates whether or not the side addressed is strapped as physical (actual) master.
The information contained in this option is automatically updated by the system.
There are two straps located on the backplane, one strap per pair of MEX-IP2/4GC
cards. The strap JP1 can be set to one of two positions: M or S. However, one pair
(MEX-IP2/4GC) of straps must be set to the “M” position and the second strap
must be set to the “S” position. The strap setup is used by the system software
program while first initialization is taking place.
CONTROL OF OTHER  Yes/No (Read-Only)

SHELVES
Shows whether or not the addressed control section controls the peripheral shelves
of the other side. The information contained in this option is automatically updated
by the system.
21-21
FLAT CABLE  Yes/No (Read-Only)

(Super Link)
Shows whether or not the two control sections of the system are properly connected
through the flat-cable.
Super Link is a special data link interconnected between two 4GC cards. This link
provides the communication route and operation of the two MEX-IP2 cards in a
“Load Sharing” mode. The Super Link allows fully updating all necessary controls
and status information between the two sides of the 4GC duplicated system (see
Figure 21-1).

Executes all permissible changes when set to Yes. Additionally, the following
message appears: DUPLICATION SYSTEM RESTART
Select No to withdraw from the duplication process.
WARNING!:
Changing the duplication parameters
1) Resets the system.
2) Disrupts all calls.
3) All keyset (FlexSet 120S, 280S, 121S, 281S;
EXCEPTION:
Disabling the second MEX-IP2 will NOT cause System Initialization
i.e. switching from a U to an L type system or from a U’ to an L’ system.
21-22
The following messages appear during initialization of a duplication system. These

messages include general information messages as well as error messages.
Message Explanation Corrective

Procedure
This is a The system includes (Not Applicable)

DUPLICATION Duplication.
system:
This is the This is the Master side of the (Not Applicable)

MASTER side: Duplicated System.
This is the This is the Slave side of the (Not Applicable)

SLAVE side: Duplicated system.
Flat Cable The system does not identify • Check that a flat-cable is present.
Failure the presence of the • Check that the flat-cable is properly
“Super-Link” flat cable.
connected.
• Check that the flat-cable is not bent
or kinked.
Second 4GC The system was loaded under • The second 4GC is not present or
Failure an I/I'-type configuration there is no communication
between the two 4GC systems.
• The SPV automatically initialized
the system as I'/I configured.
Second MCP The system was loaded under • The second MEX-IP2 is not
Failure an L/L’-type configuration. present or is faulty.
• The SPV automatically initialized

the system as L’/L configured.
Duplication Because of a communication

Decision error during initialization, the
Error MEX-IP2 could not decide how
to define the Master/Slave
sides.
STAND ALONE The MEX-IP2 is operating

SLAVE properly and is set up as an
independent slave unit.
21-23
HSB (FlexiCom 6000/R and IPx 4000/R redundant control) ç HSB or [ROOT,0,11]
SAU Requirement
The Hot Standby (HSB) Coral FlexiCom 6000/R and Coral IPx 4000/R system is
a dual control system. One control is Active while the second remains in Standby
mode. If the first system fails for any reason, the second, Standby system, becomes
Active.
There is no interruption of calls with this redundant system.
Both the Active and Standby controls are connected to the peripheral shelves while
only one connection is active (supplying all signals,e.g.: PCM, HDLC, Clock, and
Sync). This mechanism is driven by dual 32GC cards with mirrored memory
connected to an ATS-BUS providing communication between the two MCP-ATS
cards.
As a dual control system, if the Active control fails, it is automatically rendered
FAULTY (or Inactive) and the Standby system takes over operation of all calls. The
faulty system continues automatic diagnostics and will automatically recover if
possible.
Inactive Control System
A control system becomes Inactive when the Active or Standby system either fails
or is manually transferred to the Maintenance mode. In Maintenance mode, the
system continues diagnostics tests, alarm activation for service calls, and reports
faults to the Active system.
An Active Control system is automatically transferred to Fault mode when
diagnostics determines the control system to be faulty (see Diagnostic Alarms
HSB (FlexiCom 6000/R and IPx 4000/R redundant control)
beginning on page 22-5). In this mode, the system continues performing tests and
might automatically return to proper operation when normal results are observed.
The control system in Inactive Mode does not participate in the system operations
and is not in Standby mode if the Active system fails.
 Notes on PI Changes:
• Any PI Update can be made from the Active side.
• All HSB parameters on the Standby side can be viewed but not updated.
• All HSB parameters except STATUS (page 21-27) can be updated on the
Maintenance or Faulty side.
See HSB Configurations Table on the next page.
21-24
HSB Configurations
Condition Config Description Config Description
Normal H The Active control system is H’ The Active control system is

on the right and the Standby on the left and the Standby
system is on the left. system is on the right.
Abnormal I The Active system is on the I’ The Active system is on the

right side of the control shelf left side of the control shelf
while the Inactive system while the Inactive
(Maintenance or Faulty) is (Maintenance or Faulty)
on the left. system is on the right.
Single I An Active system Control N/A Single Control systems are

Control system is on the right side of not permissible from the left
the control shelf. No system side.
(Non-HSB)
is installed on the left side.
The HSB parameters are presented below. Note that most parameters are for
display purposes only and are marked Read-Only. The others may be updated as
needed.
HSB Yes/No (Read-Only)

 If this parameter is defined as No, the following parameters are not
displayed.
Displays whether this is an HSB (Hot-Standby dual control system) or not.
Yes: Coral FlexiCom 6000/R / Coral IPx 4000/R (dual control)
No: Coral FlexiCom 6000 / Coral IPx 4000 (single control)

OTHER MCP EXISTS Yes/No (Read-Only)
Displays whether a second MCP-ATS card exists.
A redundant system (Coral FlexiCom 6000/R or Coral IPx 4000/R) must have two
MCP-ATS cards installed.
OTHER 32GC EXISTS Yes/No (Read-Only)

Displays whether a second 32 Group Controller card exists.
A redundant system (Coral FlexiCom 6000/R or Coral IPx 4000/R) must have two
32GC cards installed.
CONTROL SIDE 0 (Right) / 1 (Left) (Read-Only)

Defines the Control side, i.e. the currently Active side of the redundant system.
21-25
MAIN PERIPHERAL Yes/No (Read-Only)

SWITCH CONNECTED
Defines whether the peripheral cards are connected to this side of the redundant
system.
LAST SWAP Date and Time

Displays the last time the systems were swapped (i.e. the active side became the
standby side and vice versa). Display is according to the format defined in SFE,
DATE_MODE (Eu/USA) [16] (page 6-24).
AUTO HOT SWAP Yes/No

Defines whether or not the systems (right and left side) should be automatically
swapped by the system. The next two parameters define when this procedure
should occur.
NUMBER OF DAYS 1..255 days

BETWEEN HOT
SWAPS
This parameter is not relevant if AUTO HOT SWAP is set to No.
Set the number of days between automatic hot swaps.
SET AUTO SWAP 00:00 (Midnight)..1:00..23:59

TIME

This parameter is not relevant if AUTO HOT SWAP is set to No.
Defines a time for the automatic hot swaps. Enter the time in 24-Hour format, see
Programming and Entering Time Units (page 2-6).
AUTO MAINTENANCE Yes/No

TERMINATION
If the Standby side was manually switched to Maintenance mode, setting this
parameter to Yes safeguards the system by automatically reverting the system back
to Standby mode after a predetermined number of hours.
The next parameter defines when exactly the reverse procedure should be applied.
AUTO MAINTENANCE 1..24..255 hours

TERMINATION TIME

This parameter is not relevant if AUTO MAINTENANCE TERMINATION is set
to No.
If AUTO MAINTENANCE TERMINATION, above, was set to Yes, this parameter
defines at which point (after how many hours) the system should automatically be
returned to Standby mode.
21-26
STATUS 0: Active
1: Standby
3: Maintenance
Choose the control status of this side of the system.
If Standby (1) or Maintenance (3) is chosen, the other side must be in Active mode.
OTHER CONTROL 0: Active

STATUS 1: Standby
3: Maintenance
NO_COMM
Choose the control status for the other side. If Standby (1) or Maintenance (3) is
chosen, the other side must be in Active mode.
NO_COMM indicates that this is currently not a redundant system.
UPDATE STATUS: Yes/No

Choose Yes to change the system status as chosen in the previous parameters.
Choose No to retract.
21-27
21-28
22 Diagnostics
This chapter describes the programming requirements for the system diagnostic
tests.
Diagnostic Tests..........................................................................................22-2
Diagnostic Alarms ......................................................................................22-5
22-1
Diagnostics PI Reference Manual
Diagnostic Tests ç ROOT,1,0

The Coral system provides two types of diagnostic tests:
• Auto Background Tests
• Manually Initiated Tests
The Automatic Background Test cycles are predefined by the manufacturer and can
be manually redefined only by authorized technicians. They are only for the
manufacturer’s internal use.
Manually initiated tests can be performed at the local site, by the manufacturer’s
trained and authorized personnel.
Results of both the Automatic and Manual tests can:
• be displayed at the Attendant console alarm key.
• send appropriate messages to the maintenance terminal or printer, see Terminal
Destination, DIAG (page 17-8).
• activate an alarm relay contact.
To activate a test, the required test number (see table below) must be entered
followed by Yes when asked GO Y/N -
For example: If test number 11-All DTDs is required, enter 11 then Y. The test will
run displaying each element that is tested and concluding with the following
message:
TEST COMPLETED
Test Name Function
0-ABORT Instructs any diagnostic system test already in-progress to stop.
1-KEYSET LPB All EKT and VDK Keyset micro controllers are systematically
Diagnostic Tests ROOT,1,0
(EKT, and VDK instructed to repeat a test message to the MCP, thus checking
the HDLC communication link.
Loop-Back)
2-DI B.I.T Checks the diagnostic test procedure database for corruptions.
(Diagnostic
Built-In-Test)
3-CARD POLL Conducts a bidirectional communication test between each

peripheral card and the MEX-IP2/MCP-IPx2/MCP-ATS, thus
checking the HDLC bus.
4-SPEECH RFS Refreshes the 4GC Time Switch.

(Speech Refresh)
5-KEYSETs DB RFS Downloads a message that is sent from the MEX-IP2/MCP-IPx2

(EKT, VDK, DST, DKT, to each Keyset, thereby refreshing a copy of the appropriate
Keyset database to each keyset.
GKT & FlexSets
Database Refresh)
22-2
PI Reference Manual Diagnostics
Test Name Function
6-CARD DB RFS Downloads a message that is sent from the MEX-IP2/MCP-IPx2

(Card Database to each card, thus refreshing a copy of the appropriate
peripheral card database to each peripheral card.
Refresh)
7- Not Used
8-PORT RFS Downloads (refreshes) the appropriate C1 program to each

(Port Refresh) feature control COMBO circuit (C1) on each analog port, VDK
set and time slot defined in the PBC.
9- GC QS Instructs the HDC/4GC/MSBsl/MSBipx card to repeat a test

(Group Controller message to the MCP for communication tests.
Queues)
10- ALL DTMFs Establishes a link between the DTMF generator circuitry on the
HDC/4GC/32GC/MSBsl/MSBipx card and each DTMF receiver
(DTR) circuit. Once the link is setup, the test then verifies if
tones sent by the 4GC/MSBsl/MSBipx are correctly identified by
the DTMF receiver.
11- ALL DTDs Establishes a link between the tone generator circuitry on the
(All Dial Tone HDC/4GC/32GC/MSBsl/MSBipx card and each dial tone detector
card (DTD) circuit. Once the link is setup, the test then verifies if
Detectors)
tones sent by the 4GC/MSBsl/MSBipx are correctly identified by
the DTD.
12- LINKS Checks each unoccupied link by verifying that the tone patterns
sent by the HDC/4GC/MSBsl/MSBipx card on each unoccupied
PCM time-slot is correctly received.
Also checks for the 32GC card, but only for the transmit side.
13- MEMORY Confirms the checksum value to each Read Only Memory
(ROM) device.
This information can be particularly useful whenever the
diagnostic procedures discover errors. When such an error is
discovered, an error prompt appears on the PI terminal screen
and gives the location of the faulty chip.
14- ALL PORTs Establishes a link between the test tone generator circuitry on
the HDC/4GC/MSBsl/MSBipx card and each port. Instructs the
port to enter loopback mode and verify that a tone pattern sent
to the port is successfully and correctly returned.

15- TK Detects the CO trunk dial tone when present. After three failed
AUTOGUARD tests the tested trunk is automatically blocked for outgoing calls.
The trunk is automatically unblocked only after a completely
(Trunk Autoguard)
successful cycle of diagnostic tests. This test is systematically
performed on all E&M, LS/GS & 30T trunk ports. AUTO_GUARD
[2] (page 6-52) must be enabled in SFE to perform this test.
16- DIGITAL TK Not used.

(Digital Trunk)
17- VDK CHK Not used.

(VDK Check)
18- DATA RFS Not Used.

(Data Refresh)
19- TONE RFS Downloads a copy of the tone Table database to the
(Tone Refresh) HDC/4GC/32GC/MSBsl/MSBipx service card.
22-3
Test Name Function
20- DVMS CHK Instructs the 4VS, 4VSN card to send a test tone to the
(DVMS Check) HDC/4GC/MSBsl/MSBipx card.
21- ALL MFCs Establishes a link between the tone generator circuit on the
(16 MFR Detectors) HDC/4GC/32GC/MSBsl/MSBipx and each multi frequency
receiver. Once the link is setup the test then verifies if tones sent
from the HDC/4GC/32GC/MSBsl/MSBipx are correctly identified
by the MFR.
22- E2 Performs a Checksum Test for E2 components. If the test failed,

a warning note will be printed on the screen. E. is displayed on
the seven segment of the MEX/MCP-IPx2 card.
23- CONTROLS Performs the following two tests:

Wait State Test: Displays “S.” on the MEX card if the test failed.
DBX Protection Level Test: Displays “P.” on the MEX card if
the test failed.
For FlexiCom 6000 (ATS) and IPx 4000 systems:
Performs Fan Test and PS-ATS test.
24- DKT SUBUNIT All keyset subunits (FlexSet, DKT, DST, DPEM, APA, APDL) are
systematically instructed to repeat a test message to the
MEX-IP2/MCP-IPx2, thus checking the HDLC communication
link and IOM bus.
25- ALL iDSPs Establishes a link between the test tone generator circuitry on
the 4GC/HDC/32GC card and each resource on the iDSP card.
Instructs the iDSP card to enter loopback mode and verify that a
tone pattern sent to the iDSP card is successfully returned.
22-4
Diagnostic Alarms ç ROOT,1,1

When ALARMS is selected the Alarm menu allows checking the alarm status of
essential system units and subunits. When the alarm status site is equipped with a
terminal (terminal destination, KB0 or other, is defined in Terminal Destination
beginning on page 17-8), the alarm message appears on-line. If no terminal is
provided for the technician, alarms may be detected on an attendant station by
programming an “alarm” button, default feature code, #1997. When an alarm
condition occurs, the alarm button (LED) is lit and the “Alarm Code Parameter”
(below) defines the alarm type on the station display.
• Select any one of the items below to list the appropriate faulty part.
• Enter 27-CLEAR- ALARMS to clear all alarms.
• Enter 0- ACTIVE ALARMS to permit the display of all the currently defined
system alarms.
Table 22-1: Diagnostic Alarms and Messages
PI Faulty KB0 Message Attendant Station Faulty Part Alarm

Objects Display: Alarm Code Relay
Alarms Parameters
0- ACTIVE
ALARMS
1- SEL @H ADDR @H [location] 10/ 1 Flash Memory Major

CHECKSUM
2-RAM Not Relevant
3-CARD [card type] SHELF # SLOT # 40/Shelf #/Slot# Card Error Minor
error type: NO HDLC RESPONSE
error type: INTERNAL
DIAGNOSTIC [type]
error type: RINGER PROBLEM
Diagnostic Alarms ROOT,1,1

error type: RS485
COMMUNICATION
type: {0/1-RAM, 2-PROM CS, 4-INT VECTOR,
5-POOLS}
4-CARD [card type] SHELF# SLOT# CKT# 41/Shelf #/Slot#/CKT# Specific Port Minor
SUBUNIT DIAL NUM#
error type: PORT LOOPBACK
error type: COMMUNICATION
TEST
error type: INTERNAL
DIAGNOSTIC [type]
type:{0-RAM, 2-PROM CS, 4 - Incompatible
Subunit}
22-5

Alarms Parameters
5-HDLC HIGHWAY# 30/Highway # Major

error type: HDLC HDLC Channel
Communication Faulty Periph. Card
error type: Card Force
6-PCM HIGHWAY# FAILURE 31/Highway # PCM Highway Major
 NOTE:
6-PCM HW HIGHWAY# FAILURE DATE/TIME 31/Highway # PCM Highway Major
IPx 4000 and

FlexiCom 6000
7-PCM TIME HIGHWAY# TIME SLOT# T/R (4GC) 32/Highway#/TS# 4GC/HDC Card Minor
SLOT T=Transmit/R=Receive PCM wiring
Faulty Peripheral Card
7-PCM HIGHWAY# TIME SLOT# T PCM Minor
 NOTE:
LINKS (32GC)
T=Transmit
IPx 4000 and

FlexiCom 6000
8-POWER 50/Shelf #/ Major

SUPPLY SHELF# PPS Failure Type 1------------> PPS
Failure Type 2------------> RPS
SHELF# RPS Failure Type 3------------> PS/PB
SHELF# PS/PB
8-PB & 50/Shelf #/ Major

POWER PB#FAULT SHELF# PB
PB
SUPPLY
PB#REMOVED SHELF#
IPx 4000 and Failure Type 1------------> PB
FlexiCom 6000 SHELF# PPS (FlexiCom 6000) Failure Type 2------------> PPS
SHELF# RPS (FlexiCom 6000) Failure Type 3------------> RPS
FAN FAULT A2 Fan Minor
Power Supplies: A4 Minor

PS-ATS #1 FAULT 0------------> PS_ATS#1
1------------> PS_ATS#2
PS-ATS #2 FAULT 2-----------> PS_ATS#3
PS-ATS #3 FAULT
DISK FAULT A5 Disk Major
CNT1 FAULT A3 CNT1 Minor
9-SMDR NO DTR 60 Printer/Printer Cable Minor

61
 These alarms are only applicable for systems connected via Serial RS-232 connectors.
PORT BUFFER IS FULL
They are irrelevant for IPx Office and other Coral systems connected via the MAP card.
22-6

Alarms Parameters
10- 90/Failure Type # Major

DUPLICATIO SECOND MCP 0- MCP Slave Duplication System
1- 4GC Slave 4GC Card
N SECOND 4GC 2- Superlink Cable Superlink Cable
SUPERLINK CABLE
 NOTE:
10-HSB Other MCP and XGC Failure 90/5 MCP and XGC Minor
Other XGC Failure 90/4 XGC
IPx 4000 and Other MCP Failure 90/3 MCP

FlexiCom 6000
No Communica with other side 90/6 no communication to
the standby side.
Other MCP Faulty 90/7 second side is in faulty

mode
Other MCP Maintenance 90/8 second side is in

maintenance mode
11- SYNC FAILURE 80 Primary and/or N/A

DIGITAL secondary
synchronization card
TRUNK
problem
SYNC
12- [card type] SHELF# SLOT# 81/Shelf #, Slot # Faulty Signal Major
DIGITAL [card type] SHELF# SLOT#
TRUNK CHANNEL #
CARD error type: NO SIGNAL
error type: RAI
error type: AIS
error type: CRC
error type: CLOCK FAULT
13-SLAVE 91/Fault Type # Faulty Slave MCP Major

MCP MEMORY 0- Memory
3- SAU
SAU 4- Protection Level
PROTECTION LEVEL 5- Wait State
WAIT_STATE
13-Other Real Time Clock Alarm Not

Applicable
 NOTE:
Side Memory Alarm
Lock Device Alarm Display
Only
IPx 4000 and ATS Disk Alarm
FlexiCom 6000
CNTL Alarm
Batteries Alarm
14- Wrong Expansion Type Expansion Unit N/A

EXPANSION
TYPE
22-7

Alarms Parameters
15- LOW BATTERY ON MCPsl 11/Battery Location # DBX Card Battery Minor
CONTROLS LOW BATTERY ON J1,J2,J3 Minor
Minor
UP/DOWN
15/Protection Level #* Minor

PROTECTION LEVEL# Minor
17/ Wait State Minor

WAIT STATE REGISTERS SAU
16/SAU Type# SAU Major
SAU* PHYSICAL CHECK SAU Major
SAU* SOFTWARE CHECK Major
SAU* MISMATCH
Batteries: 11/ Minor
LOW BATTERY ON 16/32 GC 0------------> 0- 32GC
1------------> 1- XMM Down
LOW BATTERY ON XMM DOWN 2------------> 2- XMM UP
LOW BATTERY ON XMM UP
16-REAL REAL TIME CLOCK FAULT 13 Real Time Clock N/A

TIME CLOCK
17-DKT [card type] SHELF# SLOT# CKT# 42/Shelf #/Slot #/Ckt # FlexSet, DKT, DST, Minor
SUBUNIT DKT SUBUNIT: [type] DIAL NUM# DPEM, APA
type:{DKT2, DKT1, DST2, DST4, DPEM, APA}
18- SEGMENT#, CHECKSUM ERROR 70/Segment # CLA Memory Minor

CLA-ROM
CHECKSUM
19- REAL TIME CLOCK 71 CLA RTC Minor

CLA-REAL
TIME CLOCK
20-CLA- APPLICATION#, ERROR# 72 CLA Application Minor

APPLICATIO error type: MISMATCH RESPONSE
N error type: NO RESPONSE
21-CLA- COMMUNICATION ERROR 73 N/A Minor

DUMMY
MESSAGE
22- E911 GC Incompatible E911 4GC (No DKT message is Non-Compatible E911 N/A
COMPATIBILI Incompatible E911 4GC(other displayed) (4GC) Control Card
TY
4GC)
22-8

Alarms Parameters
23- LAR LAR BLOCKING: Trunk [trk#] A trunk is blocked. Minor

ALARMS DEST [dest#] Cause [#] [Date] A Dial Service is
blocked.
[Time]
ROUTING FAILURES: Dial
Service [D.S.#] DEST [dest#]
Cause [#] [Date] [Time]
24-NODE NODE ID MISSING [date] [time] 00A1 This alarm is activated Minor
ID# when there is no node
ID# defined for the
current node and the
system tries to
activate the Path
Replacement feature
(or a remote node
invites Path
Replacement from the
current node).
25- Telephony GW Fault 0A6H The Keep Alive Minor

TELEHONY Gateway# x Unregistered mechanism did not
detect any Telephony
GATEWAY
Gateway (FXO/FSX
Teleport) unit activity
in the last 24 hours.
The system therefore
deletes the IP address
for the inactive unit
thereby unregistering it
in the Coral.
Clear the alarm by
re-inserting the
Gateway unit, or
changing the unit or
the type of unit as
necessary.

26-SKK SKK Master Fault A8H SKK Master Card Major
Master Card [DATE] [TIME]
CLUSTER# Shelf/Slot location
27-CLEAR-
ALARMS
28-CFM NA NA Sends Coral fault and NA

Update diagnostic messages
immediately to the
Coral Fault Manager
(CFM) application.
FAILURE
REPORT (page 17-5)
must be set to Yes.
22-9
* If lock device (SAU) is faulty for two weeks, the following message is displayed:
“SYSTEM IS DOWN DUE TO: FAULTY LOCK_DEVICE CALL TECHNICIAN”.
and the system shuts down. If the system is powered up again without correcting the lock device problem, the system will shut down
again in 15 minutes.
22-10
23 Special Port Facilities
This chapter describes the special port facilities that are available for tenant
members.
DVMS Port .................................................................................................23-2
Conference ..................................................................................................23-4
Public Address/Page ...................................................................................23-7
Modem ........................................................................................................23-9
Bell/UNA ..................................................................................................23-10
Page_Q/Music...........................................................................................23-11
23-1
Special Port Facilities PI Reference Manual
DVMS Port ç PDB,4 [0,2,1,4]
Four DVMS ports are located on each 4VS or 4VSN card. This option allows
defining one or all of the four DVMS ports to announce a particular message
programmed into the card.
FROM/TO DIAL # Any valid system DVMS port dial number (defined in
General Numbering Plan, DVMS_PORTS [32] (page 5-44);
All
Enter the range of required DVMS Port dial numbers FROM the lowest dial
number required TO the highest dial number required.
MSG [0] N (all messages can be heard) or 2..99(4VS) or 2..27,28,30(4VSN) (limited

by MAX_DVMS_MSG [9] on page 6-46 defined in SFE);
The MSG field is used to dedicate a particular DVMS message to any one of the
four defined DVMS ports.
A dedicated message is typically required for ACD/UCD RECORDED MESSAGES:
on page 10-14, CALL_BACK_ANNOUNCEMENT [11] on page 6-22, or when a
particular announcement must be announced to an unlimited amount of users.
Up to 98 different messages can be stored on a single 4VS card (the maximum is
30 for the 4VSN card). Each port can announce any one message of the 98 (or 30)
messages, allowing a total of four different dedicated messages that can be
announced simultaneously per card.
Users devote the particular message to be announced on one of the 4 DVMS ports
by entering the DVMS MSG index number related to that particular message (2-99
for the 4VS and 2-27,28,30 for the 4VSN). Each DVMS MSG has a 4-digit NPL
dial number and a related 2 digit index number, 02 - 99 (or 02-27,28,30), defined
for use in this parameter. Thus, a user dialing this port number always hears the
DVMS Port PDB,4 [0,2,1,4]
same message.
In this parameter, use the 2-digit DVMS MSG index number instead of the four
digit dial number defined by DVMS_MSG [31] (page 5-43) in the General Numbering
Plan.
Each DVMS card has four ports. A port defined as N enables users to access any
one of the messages stored on the card by dialing its 4-digit DVMS_MSG number.
On the other hand, a port defined with a specific index number enables the user to
hear only the message related to that index number.
 Manufacturer’s Recommendation:
At least one port should be defined as N so that more than four different
messages may be accessed by the users.
23-2
PI Reference Manual Special Port Facilities
TNNT_GRP [1] 0..63

Defines the tenant group number required for accessing the DVMS port. This
option can be used to block certain users from connecting to the current DVMS
port. Tenant restrictions are defined through COS.
WITH_ANSWER [2] Yes/No

SAU Requirement
External incoming calls are sometimes answered with an announcement. This
parameter decides whether to send an answer signal to the calling party's exchange.
The sent answer signal will cause the calling party's exchange to charge the calling
party for the call.
If an answer signal is not sent to the calling party's exchange because this parameter
is set to No, no charge is incurred for the call.
WITH_ANSWER is typically used for systems used as a basis for a public wireless
exchange. Certain situations require not charging for the call, such as notifications
that the wireless telephone is currently turned off or a line is unavailable, or for
notifications of new (changed) numbers.
Enter Yes to send an answer signal and consequently charge for the call.
 Feature Authorization (page 3-5) is required in order not to toll the call
(i.e. To set WITH_ANSWER to No).
DVMS Port PDB,4 [0,2,1,4]
23-3
Conference ç PDB,3 [0,2,1,3]
The following cards support multi-party conference bridges simultaneously:

• CNF (defined as CONF in Card List on page 6-59) – two 15-party bridges
• 8DRCF, 8DRCM-2, 8DRCM – one 6-party bridge
• The Coral IPx 500M main cage (MSBipx Issue-0200X1000 and above) –
two (max: six*) 14-party bridges. Enables a conference of a maximum of 84
participants.
• The CDRS 200E main cage 14-party bridges. Enables a conference of a
maximum of 84 participants.
• U-RMI Office and U-MR Office – two (max: six*) 14-party bridges. Enables
a conference of a maximum of 84 participants.
The U-MR Office and U-RMI Office cards can be installed in the:
• Coral IPx Office main unit slot 6-7 (single card only)
The CNF, 8DRCF, 8DRCM-2, or 8DRCM cards can be installed in the following
systems:
• Coral IPx 500 with 800X expansion cage
• Coral FlexiCom 400 (with HDC controller), 5000, 6000
• Coral IPx 800, 3000, 4000
• Coral IPx Office with IPx 800X expansion cage
 Separate authorization is required to allocate the CONF circuits supported

• Coral IPx Office with FlexiCom 200 expansion unit
by the Coral IPx Office (U-RMI Office / U-MR Office) and IPx 500.
(max: *) The max number, modifiable via the PI, see URC-Current
Configuration - Meet Me on page 4-38.
Conference PDB,3 [0,2,1,3]
23-4
FROM/TO DIAL # Any valid system Conference dial number (defined in General Numbering
Plan, CONF [30] (page 5-43));
All
Enter the range of required Conference dial numbers FROM the lowest Conference
number TO the highest Conference number.
BREAK_IN/OUT_ Yes/No
TONE [0]
This option defines whether or not to inform parties engaged in a conference call
when an additional user joins (break-in) or leaves (break-out) the call.
TNNT_GRP [1] 0..63

Defines the tenant group number required for accessing the conference and Group
Call features. This option can be used to block certain users from connecting to the
current Conference definitions.
CIRCUIT_RESERVED Yes/No
[2]
Set this parameter to Yes to reserve this conference dial number for regular
conferences so that it cannot be used for the Continuous Conference feature.
Setting this parameter to Yes ensures that when a maximum number of Continuous
Conferences are created, thereby exhausting many conference circuits, this
Conference circuit is still reserved for regular conferences.
CONTINUES_CONF B (Blocked), N (Not blocked)

[3]
Adding an additional participant to an ongoing Continuous Conference call.
When set to B (Blocked), only the party initiating the 4-way conference call can

add new participants to the conference call.
When set to N (Not blocked), all members participating in the continuous
conference call can add new participants.
23-5
LINKED TO CONF Any valid URC Conference dial# on the SAME card
DIAL# [4] Default: R (Remove for None)
• Requires URC Software Versions 1.29 or higher.
• URC units available on:
• Coral IPx Office (U-RMI Office, U-MR Office cards)
• Coral IPx 500M (MSBipx Hardware Issue-0200X1000 and above)
• CDRS 200E.
This parameter enables linking Conference circuits on the URC unit only, in order
to create a larger conference. A single URC Conference may contain a maximum
of 84 conference participants.
 Keyset Display for Conference Participants:

The conference number is displayed on the user’s keyset. However,
different members in the same chained conference may see different
conference numbers on their display.
Enter the Conference dial number to be linked to this conference number.
23-6
Public Address/Page ç PDB,5 [0,2,1,5]
Public Address provides the interface for external paging and public address
systems. The audio output of the public address may be used to directly drive
amplified speakers. However, the number of speakers that can be driven varies
according to manufacturer. For more details on external paging devices see the
relevant Coral Installation Manual.
Paging or Public Address, is accomplished through using relay RLY1 located on
the following cards that support one paging interface each:
• The CDRS 200E main cage
• The Coral IPx 500M main cage
• RMI Office, MR Office, U-RMI Office and U-MR Office card
• 8DRCF card
• ASU and RMI cards
CDRS 200E and IPx 500.
The 8DRCF, 8DRCM-2, 8DRCM, RMI and ASU card can be installed in the
following Coral systems:
• Coral FlexiCom 300, 400, 5000, 6000
• Coral IPx 800, 3000, 4000
The RMI Office, MR Office, U-RMI Office or U-MR Office cards can be installed
in the:
Public Address/Page PDB,5 [0,2,1,5]

 When the public address interface of the RMI Office, MR Office, U-RMI
• Coral IPx Office unit (single card only)
Office, U-MR Office or RMI/ASU cards is used the second music interface
is not available.
FROM/TO DIAL # Any valid system Page dial number (defined in General Numbering Plan,
PAGE [12] (page 5-40));
All
Enter the range of required Page dial numbers FROM the lowest Page number
required TO the highest Page number required.
23-7
TNNT_GRP 0..63
Defines the tenant group number required for accessing the Page for public address
systems. This option can be used to block certain users from connecting to the
current Page.
 Each RMI/ASU card includes only one port for PAGING called MP-2.
This port may be used for either PAGING or 2nd MUSIC SOURCE.
When # OF MUSIC SOURCES (1-4) (page 4-45) is employed, the PAGE
feature is blocked. In order to have both features available simultaneously,
an 8DRCM-2, 8DRCM, 8DRCF or additional RMI/ASU card must be
installed.
Each Coral IPx 500, CDRS 200E or 8DRCM-2, 8DRCM, 8DRCF card
includes one port for Paging and two ports for Music Sources.
Public Address/Page PDB,5 [0,2,1,5]
23-8
Modem ç PDB,6 [0,2,1,6]
A modem port is located on the following cards and systems. Each card can be
equipped with a single, auto-answer data modem for accessing the PI from a
remote. This option is normally utilized for programming and maintenance
purposes. The modem can be assigned a dial number for user access. Assigning
tenant numbers to the modem allows or denies tenant access to the modem.
• The Coral IPx 500M main cage (MSBipx Hardware Issue-0220X1003 or
lower) – V.90 ITU-T up to 56Kbps
• 8DRCF card – V.90 ITU-T up to 56Kbps
• U-RMI Office or RMI Office card – V.90 ITU-T up to 56Kbps
• 8DRCM and RMI/ASU cards - 300/1200 bps
CKT 26 on the 8DRCM/8DRCF, U-RMI/RMI Office, and IPx 500.
The modem is not available on the following cards and systems:
• 8DRCM-2 card
• Coral IPx 500M (with MSBipx Hardware Issue-0230X1003 or higher)
• CDRS 200E
The 8DRCF, 8DRCM and RMI/ASU cards can be installed in the following
systems:
• Coral FlexiCom 300, 400, 5000, 6000
• Coral IPx 800, 3000, 4000
The U-RMI Office or U-MR Office cards can be installed in the:
Modem PDB,6 [0,2,1,6]

FROM/TO DIAL # Any valid system Modem dial number (defined in General Numbering Plan,
MODEM [13] (page 5-41));
All
Enter the range of required Modem dial numbers FROM the lowest Modem
number required TO the highest Modem number required.
TNNT_GRP 0..63
Defines the tenant group number required for accessing the Modem. This option
can be used to block certain users from connecting to the modem. Tenant
restrictions are defined through COS.
23-9
Bell/UNA ç PDB,7 [0,2,1,7]
Central Bell is activated by relay RLY2 located on the following cards:

• The Coral IPx 500M main cage
• The CDRS 200E main cage
• RMI Office, MR Office, U-RMI Office and U-MR Office card
• 8DRCF, 8DRCM-2, and 8DRCM card
• ASU and RMI cards
Every bell located on a single card is assigned a unique dial number.
CKT 24 on the 8DRCM-2, 8DRCM, 8DRCF, U-RMI/U-MR/RMI/MR Office, and
IPx 500.
RLY2 relay is used to activate an external ringing bell or lamp, whose activation
time is defined in FE.T, (see page 6-3). Typically, the feature is defined for after
normal working hours, or for noisy work areas where a normally ringing telephone
would not be heard.
The 8DRCF, 8DRCM-2, 8DRCM, RMI and ASU card can be installed in the
following Coral systems:
• Coral FlexiCom 300, 400, 5000, 6000
• Coral IPx 800, 3000, 4000
The RMI Office, MR Office, U-RMI Office or U-MR Office cards can be installed
in the:
FROM/TO DIAL # Any valid system Bell dial number(defined in General Numbering Plan, BELL
Bell/UNA PDB,7 [0,2,1,7]
[11] (page 5-40));

All
Enter the range of required Bell dial numbers FROM the lowest Bell number
required TO the highest Bell number required.
TNNT_GRP 0..63
Defines the tenant group number required for accessing the Bell number on various
special features. This option can be used to block certain users from connecting to
the current Bell.
23-10
Page_Q/Music ç ROOT,0,7
The Page_Q feature enables a station user to place a call in a special hold queue.
The call can then be answered at another station by dialing the specific queue
number.
Each queue number can be assigned a different music source that the holding party
hears. The call may be picked-up by any station member. Additionally, the user
who queued the calling party may page another station user to answer the call.
FROM/TO DIAL # Any valid system Page_Q dial number (defined in General Numbering Plan,
PAGE [12] (page 5-40));
All
Enter the range of required Page_Q dial numbers FROM the lowest Page_Q
number required TO the highest Page_Q number required.
ENTER MUSIC 0..3;

SOURCES IPx 500 and CDRS 200E: 0 (Music 1), 1 (Music 2)
Determines the MUSIC-ON-HOLD source from a multiple music source. This
music is sounded to callers placed in a Page queue until the call is answered. The
range is limited by # OF MUSIC SOURCES (1-4) (page 4-45).
Page_Q/Music ROOT,0,7
23-11
23-12
24 VFAC
Software Authorization Limit

This chapter describes the Verified Forced Account Code (VFAC) options
available.
Verified Forced Account Code...................................................................24-2

0 - INIT CODES ........................................................................................24-5
1 - CODES..................................................................................................24-7
2 - SMDR ...................................................................................................24-9
3 - PASSWORD .........................................................................................24-9
24-1
VFAC PI Reference Manual
Verified Forced Account Code ç VFAC [3,4]
Verified Account Code (VAC) checks the code dialed, when required, by a user.
The Verified Forced Account Code (VFAC) supplements the regular Forced
Account Code (FAC) feature. Both the Forced Account code and the Verified
Forced Account Code require an account code when attempting to make an outside
call. VFAC, however, verifies the accuracy of the account code against the internal
database. If the account code is correct, the caller is allowed to continue dialing the
external number. If the account code is incorrect, a reorder tone is sounded and the
keyset displays the following message: Passcode Fail. Three fail attempts are
allowed by the system. The third failure generates an intercept call with a message
specifying the COS number. Dialing the correct account code number assigns the
caller a matching COS designation for the duration of the call.
Account codes can be between 4 and 16 digits (defined system-wide). When the
system is first initialized, a special random “Init Type Number” is generated. These
account numbers can then be assigned by the PI system programmer to individual
telephones. An additional security measure is provided by making the VFAC
branch of the PI password protected. Account codes are related through their index
numbers. Only authorized system programmers can delete or open account codes.
VFAC is typically used in semi-public places such as: dormitories, hospitals or
professional law firms; VFAC can also be used to keep track of client telephone
billing in places such as professional consulting firms. Additionally, “public
telephones” whose COS designation accepts any code, can be defined in the
database. When a legal VFAC code is entered, the caller can then place calls
through the phone. Multiple VFACs can be assigned to individual telephones. This
prevents a person who has secured another person’s code from using the code from
a different phone.
Verified Forced Account Code VFAC [3,4]
PROCEDURE FOR DEFINING VERIFIED FORCED ACCOUNT CODE

1. Make sure that VFAC_ACCT (page 4-17) size is defined according to your
system requirements.
2. Follow the procedures listed below before defining VFAC: Make sure that
#ACCT_DGTS [7] (page 6-9) in SFE is defined according to your system
requirements. The code length is normally related to the required level of
security; the longer the code, the greater the security.
3. Make sure that VFAC is defined to operate by entering Yes in VFAC.
[9] (page 6-10) in SFE.
4. Make sure that ACCT [58] (page 7-18) in COS is defined as required for all
relevant COS numbers.
5. When Forced Account Code is required make sure that F.A.C_TK_
GRPS/ROUTING ACCESS [6] (page 7-4) in COS is defined as required for all
applicable COS numbers.
6. Make sure that VFAC_PUBLIC [59] (page 7-18) in COS is defined as required
for all relevant COS numbers.
Once these procedures are completed, VFAC can be setup for the system.
24-2
PI Reference Manual VFAC
Generating The total number of Account Codes used depends on how #ACCT_DGTS
VFAC Codes [7] (page 6-9) in the SFE branch is defined. This definition is related to the actual
number of digits that are available for each account code and the parameters as
defined in SIZ - ACCOUNTS. See Chapter 6 -System Features - Outgoing Trunks for
the table of Account Digits and Maximum Number of Codes.
Account codes are automatically generated by the internal secret function. There
are 32 sets of codes for each #ACCT_DGTS [7] (4-16) for a total of 416 different
code set possibilities. This total is established as follows: 32 x (16-3) = 416 (that
is: 32 fixed sets of codes, times the possible number of code strings [a minimum of
4, maximum of 16, {16-3}] equals a total of 416 possible strings). Each code set
contains a fixed number of possibilities, depending on the length of the code string
that is selected (between 4 and 16 digits). This code set is defined system-wide.
Select the code set through INIT TYPE. However, every code set has its own
unique codes, which are constant (cannot be individually changed) and are related
to the index number. A user’s code cannot be changed, only reassigned within the
limits of the currently defined code set.
There are 704 possible strings (32x22=704). This is for a large number of codes -
up to 65,000.
Each Coral system can have only a single code set. Once the number of digits in a
code has been determined, the entire system operates according to the same code
structure.
 External dialing features when VFAC is required:

• Redial features (Last # Redial, Auto Redial, Saved # Redial, etc.) cannot
be activated for telephone numbers that require VFAC.
• A keyset button or library number cannot be programmed with the
VFAC number.

24-3
ENTER ACCOUNT The defined password must be typed before entering the VFAC branch. If the
PASSWORD... password is incorrect then the following message appears:
***ILL PASSWORD***
Unless the proper password is entered the VFAC options cannot be reached. Once
the password is accepted the following menu appears:
0 - INIT CODES
1 - CODES
2 - SMDR
3 - PASSWORD
 See PROCEDURE FOR DEFINING VERIFIED FORCED ACCOUNT CODE on

page 24-2. Make sure that the conditions described in steps 1 through 6
are fulfilled.
Once the menu appears, select the number associated with the required option.
Press [CR] and the option steps then become available. These options will be
discussed according to the order presented in the above menu.
24-4
0 - INIT CODES This option allows you to select one of the thirty-two sets of account codes in place
of the codes that are defined by the VFAC randomly generated code table. The Init
Type can be any number between 0 and 31 thus allowing for one of the thirty-two
account code sets. However, this set of numbers can be changed either by letting
the system randomly select a new set of numbers or by manually changing a
specific INIT TYPE. The code digits are computer generated, therefore, personal
code numbers may not be defined.
The following procedures describe the ways in which the ACCOUNT CODES can
be changed. The various options automatically appear in order once the request has
been fulfilled. However, the system allows backing out of certain options at various
points during the programming procedure.
CHANGE CODES Yes/No

This question permits changing the set of Account CODES. Entering No returns
you to the previous PI node. Entering Yes displays the current INIT TYPE (any
number from 0 through 31) thereby allowing the procedure to continue.
CURRENT INIT. TYPE  0..31

This parameter displays the current INIT TYPE number. The displayed number
assigns the current set of codes.
ANY_SPECIFIC INIT Y (Change by Programmer)/N (Automatic Change by System)

TYPE
This parameter allows defining the preferred method for changing the INIT TYPE.
Select Y to allow the system programmer to manually change the INIT TYPE.
Select N to have the system automatically choose and change the INIT TYPE.
If Y (Change by Programmer) is selected, then a new INIT TYPE number may be

entered (i.e. the next parameter, Enter_New_Init._Type becomes available).
24-5
ENTER_NEW_INIT._ 0..31
TYPE CURRENT INIT TYPE (listed above)
This parameter appears only when ANY_SPECIFIC INIT TYPE above, is set to Y.
Enter any number between 0 and 31. This parameter should be changed with
caution, since all existing Account Codes will be replaced as soon as the new INIT
TYPE is accepted.
 Hint: In order to keep the VFAC Codes secret, we recommend using a

different INIT TYPE for each Coral system that has Account Codes
installed.
Note: The Codes (i.e. the digits) are computer generated. The user cannot
define a personal code number.
Once the new INIT TYPE number is entered, the following warning message
appears:
Warning: All existing Account Codes will be changed.
ARE YOU SURE? (Y/[N]) -
Enter Y to change the Account Codes.
Enter N to retract.
ARE YOU SURE? Yes/No

Answering No causes the current INIT TYPE number to remain intact, thereby
allowing the final chance to back out of the procedure. Answering Yes replaces the
current number with the newly defined number. At this point all existing Account
Codes are replaced by a new set of codes.
24-6
1 - CODES The attributes associated with each code are defined as follows:. The codes can be:
• Cancelled for further use
• Assigned to all system stations
• Assigned to a specific station
• Assigned with a COS number
Selecting CODES from the VFAC main menu allows changing and modifying the
use of the Account Code numbers. Change and Update by either choosing a system
Index number (choose 0) or Code (choose 1) method:
0-Index: through a range of index numbers (each code is associated with an Index
number)
1-Code: for a specific code number
Once the specific manner for making the change is decided, the following modes
of operation are available:
Option Description
0 - UPDATE Allows changing or modifying the attributes.
1 - DISPLAY Displays all attributes for any specific account code.
2 - ADD Instructs the system to select an unused or canceled

Account code in order to assign one of the codes in
the code set to a new user.
The procedure for changing the codes is described below. You can update account
code information by either entering a VFAC code number or VFAC index number
and thereby update the related information (ASSIGN TO and COS parameters).

FROM/TO INDEX  This option is displayed when 0 - Index is selected.
0..to the maximum as defined in Sizes;
All current index numbers
Select the range of index numbers required for updating or displaying. FROM
INDEX: select lowest index number; TO INDEX: select highest index number.
After entering the index number the message: ACCOUNT CODE appears and
lists the Account Code associated with the requested index number.
Index is the serial number that defines the specific Account Code that the system
can identify. The total amount of index numbers that can be used is defined in
SIZES (see Chapter 4). 0 - Index allows selecting a range of Account Codes.
24-7
ENTER CODE 4 to 16 digits: defined in #ACCT_DGTS [7] (page 6-9)
 This option is displayed when 1 - Code is selected.

A specific secret Account Code number must be entered. This number must be
between 4 and 16 digits, as defined in #ACCT_DGTS [7] in the SFE,0 branch. After
entering the number, the message: INDEX appears and lists the Index Number
associated with the requested Account Code.
Once either 0-Index or 1-Code is selected, the following parameter appears:
ASSIGN TO U (Unused: i.e., currently unassigned), C (Cancelled), A (All), S (Station #)
 By default, all Account Code numbers defined as unused.

This parameter allows the programmer to define each VFAC number as any of the
following types:
• Canceled: Temporarily takes the current account code out of use. However, the
account code is not actually deleted from the system memory.
• All: Allows assigning all stations the current Account Code. Typically defined
for public access.
• Station #: Defines the specific station number from which the current Account
Code can be used.
COS None or 0..maximum COS defined in SIZES

This parameter allows defining the station class of service when using the current
Account Code. This parameter can also be left blank for no COS.
When the user dials the correct Account Code the system will then assign a
matching COS for the duration of a single call only. Account Code operates in a
manner similar to Executive Privilege, in that:
• Certain features available at one station can also be utilized at another station.
• Some stations may be denied Account Codes.
• COS must be assigned to stations that use Account Code, thus, Account Code
can act as a passcode to the station operations.
• COS remains in effect for a single call only. After the one call is placed, the
station returns to its original Class Of Service.
24-8
2 - SMDR Use this tab to define the account code on the SMDR report.
ON-LINE N (None)/ I (Index)/ C (Codes)

SMDR-ACCOUNT_
This is a system-wide parameter that allows printing the Account Code information
DISPLAY:
in the SMDR ON-LINE report. Account Code can be represented on the SMDR
report in one of two ways:
• By Index number (5 digits with leading zeros)
• By Code number
See 0 - INIT CODES beginning on page 24-5 for definitions of the Index
and Code number.
Choose None so that the account code is not included in the SMDR report.
For the Account Code to appear in the SMDR report, ACCT. must be defined in
the SMDR Format ON_LINE PARMS (page 14-11).
3 - PASSWORD A special account password is required in order to access the Verified Forced
Account Code node (see ENTER ACCOUNT PASSWORD... on page 24-4). This
password can be changed when required. The changing procedure is described
below.
ENTER OLD 1 to 9 printable ASCII characters;

PASSWORD: Confidential: For Trained and Certified Manufacturer Personnel
To change the password, the system must first identify the old password.
ENTER NEW 1 to 9 printable ASCII characters

PASSWORD:
Enter the new password.

RE-ENTER NEW 1 to 9 printable ASCII characters

PASSWORD:
This is required in order for the system to verify that the password is correct.
When entering a new password one of the following messages appears:
**Password ACCEPTED**
The new password is correct and is accepted by the system.
**Password DENIED**
Password verification was faulty. The previous PI node is displayed.
24-9
24-10
25 Time/Date Set and Adjust
This chapter describes the way in which the system time and date is set, as well as
adjustments that can be made when the system is installed or as required.
Time Set......................................................................................................25-2
Time Adjust ................................................................................................25-5
25-1
Time/Date Set and Adjust PI Reference Manual
Time Set ç TIME [ROOT,3,0]
Time Set allows setting the current system time and date. Changing these values
resets the displays on the Keysets and SMDR reports. The time and date are
displayed according to the format defined in Chapter 6 - System Features- Station
Options, DATE_MODE (Eu/USA) [16] (page 6-24). (Attendant Modifiable)
Press [CTRL-T] to display the time and date at any point on the PI system.
 The Coral real time clock is powered by its own internal battery, retaining
the correct time even after a power failure. Relevant systems: MEX-IP2,
MCP-IPx2, MCP-ATS and IPx Office.
TIME HH:MM (HH = 00..24, MM = 00..59)

12:59
Sets the system time. Time must be entered as hours and minutes
[(HH:MM) HH = hours, MM = minutes]. Not entering a new time causes this
option to display the current time.
AM/PM AM/PM (not available for European clock)

Sets for AM or PM.
AM = 00:00 until 11:59; PM = 12:00 until 23:59 (00:00 = midnight, 12:00 = noon).
YEAR 1987..1992..2084 or 00..99

Defines the current year. The year is entered with four digits or the last two digits
of the required year.
MONTH 1..12
Defines the current month. The month is entered by the actual number of the month
in one or two digits; January = 1, December = 12.
DAY 1..31
Defines the current day of the month. The day of the month is entered in one or two
digits.
25-2
PI Reference Manual Time/Date Set and Adjust
DELTA_TIME_FROM_ +/- HH:MM (HH = 00..12, MM = 00, 15, 30, 45) or R (Remove for None);
GMT None
Defines the time zone of the Coral system by defining a time offset (in hours and
minutes) from GMT time.
• Time must be entered as +/- Hours:Minutes, i.e, with a colon, and minute
definition (00 for no minutes).
• Minute values are entered in increments of 15 minute (00, 15, 30, 45).
! Define this parameter as 0:00 only when this Coral system is physically
located at London GMT time. Otherwise, the time zone offsets defined
for the IP endpoints are meaningless.
What are time zones?

The earth is split into several different time zones. Each zone has a local time that
corresponds to the local sunset. The time zone's base time is GMT (Greenwich
Mean Time). The base time is equal to 0 (based at Greenwich, England) and all
time zones have an offset to GMT between -12 to +12 hours.
Example:
If you live in Germany and the Coral system is located in Berlin, you are in a time
zone defined as “+1” (time difference in hours compared to GMT). Define this
parameter as +1:00. If it is 11:00 o'clock in Berlin it is 10:00 o'clock in GMT “at
the same moment”.
Table 25-1: Time zone examples (Attention for day light or summer time!!!)
Los New Madrid London Berlin Tokyo

Angeles York (GMT)
Delta Time from -8:00 -5:00 -1:00 0 +1:00 +9:00
GMT (Local Offset to
GMT)
Displayed Time 02:00 05:00 09:00 10:00 11:00 19:00

(Local Time)
Time Set TIME [ROOT,3,0]

The IP Ports: Keyset DELTA_TIME_FROM_GMT [16] on page 29-35
and IP: Telephony GW DELTA_TIME_FROM_GMT [10] on page 29-66
define the time zone offset for each individual IP endpoint, if it is different from
the time zone defined for the Coral system. Additionally, each endpoint may be
individually defined a time zone offset at the endpoint terminal.
An override feature, allowing the Coral system to cancel any time zone definition
set by an IP Keyset station is included in the IP Ports: Keyset PHONE_TIME_ZONE_
OVERRIDE_BY_SYSTEM [15] on page 29-34.
System features such as the SMDR and Night Service are handled according to the
Coral system time. However, the Keyset Idle Display Clock, Wake-up,
Reminder, and Call Log features are automatically adjusted to follow the
localized time definitions as per their IP endpoints.
25-3
UPDATE? Yes/No
Executes all permissible changes when set to Yes.
25-4
PI Reference Manual Time/Date Set and Adjust
Time Adjust ç ROOT,3,1

CLK.ADJUSTMENT -32767..+32767 (1 unit = 0.1 seconds per 24 hours)
The system clock can be retarded or advanced for accurate system timing. This
adjustment can be performed by a minimum increment of 0.1 second steps per day.
When the clock is slow, a positive number will speed up the timing; when the clock
is fast, a negative number will slow down the timing. Typically (either +n or -n)
time is corrected in ten second intervals per 24 hours. Time corrections are not
shown at the PI terminal.
Time Adjust ROOT,3,1
25-5
25-6
26 ISDN
This chapter is used to program the system-wide ISDN parameters that connect the
Coral with the Network. The following options are available:
System Features - ISDN.............................................................................26-2
BCCOS Templates......................................................................................26-3
BCCOS Control..........................................................................................26-5
NSF .............................................................................................................26-6
Call by Call.................................................................................................26-8
Alternate Line ID........................................................................................26-9
ISDN Card Signaling................................................................................ 26-11
ISDN Card Signaling: Signaling Channel........................................ 26-12
ISDN Card Signaling: Card location................................................ 26-13
The System Features parameters establish the system default ISDN parameters for
all ISDN trunks that do not belong to any trunk group.
BCCOS (Bearer Capability Class of Service) establishes the communications
characteristics of incoming and outgoing ISDN trunks.
NSF (Network Specific Facility) parameters define services (e.g. INWATS,
ACCUNET, MEGACOM) provided by various carriers. (Applicable only in North
America.)
The Call By Call parameter is not used in this Coral version of the PI.
The Alternate Line ID parameter allows an ANI (Automatic Number
Identification) to be sent to the Network.
The PRI (Primary Rate Interface) and BRI (aka TBR: Trunk Basic Rate Interface)
card signaling parameters identify individual D-Channel characteristics.
26-1
ISDN PI Reference Manual
System Features - ISDN ç SFE,10 [0,0,4,1,10]
The following parameters are applied as default to all ISDN trunks which do not
belong to any trunk group. You must enter a value for Routing Access # before
continuing to update the other related parameters in this branch.
For further details, see Trunk Group Definition beginning on page 8-18.
ROUTING ACCESS # Any valid system Routing Access dial number (see ROUTING_ACC [37] on
[0] page 5-44, NPL,0,5,37)
or None
80
Defines the Routing Access Number to be applied for each outgoing trunk that is
not a member of any trunk group. Such a trunk is treated with the features defined
for the Routing Access selected here (see Chapter 15).
DIALING METHOD [1] E (Enblock), O (Overlap)

Defines the system default dialing method. When Enblock is chosen, the Coral
sends all digits in a packet, as used when dialing over ISDN trunks. When Overlap
is chosen, the trunk is seized first and then the digits are sent.
For CAMA trunks that have not been defined as members of a trunk group, set this
parameter to Enblock.
CALLER # OUT See DIAL_FILTER [10] on page 15-14 or R (Remove)

FILTER [2]
System Features - ISDN SFE,10 [0,0,4,1,10]
Defines the filter applied on an outgoing ANI (Automatic Number Identification).

This filter is used to convert the calling Coral number to the Network number as
listed in the local telephone directory.
DIAL IN/CALLER OUT 0 to 3, R (Remove)

OFFSET [3]
Defines which offset filter is applied for trunks dialing in and out of the system.
In the absence of an offset filter (the default), each digit is separately verified
according to the numbering plan without filtering.
When an offset filter is defined, the incoming digits are modified to match the
system numbering plan. See Offset Filters beginning on page 8-42.
26-2
PI Reference Manual ISDN
BCCOS Templates ç ROOT,5,0,0

BCCOS defines the communications characteristics of incoming and outgoing
ISDN trunks (e.g., Bandwidth). An ISDN call made from a Coral system that is not
BCCOS compatible with the Network, cannot be processed. This also applies to
ISDN calls made from the Network to the Coral.
TEMPLATES Defines the values that are sent/received to/from the network to indicate the
requested BCCOS. There are 32 templates available. The first two templates are
pre-programmed and cannot be modified. The remaining 30 templates are
pre-programmed but can be modified.
FROM/TO TEMPLATE 0..31

0 and 1 are pre-programmed and may not be modified.
The remaining templates are programmable
Enter the range of required TEMPLATES numbers FROM the lowest number
required and TO the highest TEMPLATES number required.
NAME 1 to 16 printable ASCII characters, R (Remove for BLANK);

See Table 26-1 below for defaults
Defines up to a sixteen character name for the template. The name is provided for
reference only and is not displayed anywhere else in the Coral system. See General
PARAMETERS 1 to 5 hexadecimal codes required;

The numbers are entered between parentheses, and must be
separated by commas or spaces;
See Table 26-1 below
BCCOS Templates ROOT,5,0,0

Each template is composed of at least three parameters. The parameters are
displayed in hexadecimal code (1st, 2nd, 3rd). The parameters are listed in a three
to five byte sequence and correspond to the following:
1st: Information byte: Transfer Capability
2nd: Information byte: Transfer Mode
3rd: Information byte: Transfer Rate
4th: Information byte: Transfer Mode (optional)
5th: Information byte: Transfer Rate (optional)
The possible values are defined in CCITT protocol Q-931 and are compatible with
ISDN standards. Commonly used BCs are defined as the default values. Additional
combinations are supplied by the Network carrier.
26-3
DEFAULT
TEMPLATE # NAME PARAMETERS

(in Hexadecimal
Code)
0 SPEECH (0H, 0H,10H)
1 3.1 kHz_AUDIO (10H, 0H,10H)
2 RESTR._DIG._INFO (9H, 0H,10H)
3 UNRES._DIG._INFO (8H, 0H,10H)
4 56k_Unrestricted (8H,0H,10H,1H, FH)
5 to 31 SPEECH (0H, 0H,10H)
BCCOS Templates ROOT,5,0,0
26-4
BCCOS Control ç ROOT,5,0,1

Defines the communications characteristics of incoming and outgoing ISDN
trunks (e.g., Bandwidth). An ISDN call made from a Coral system that is not
BCCOS compatible with the Network cannot be processed. This also applies to
ISDN calls made from the Network to the Coral.
CONTROL Selects the template or various templates to be included in each BCCOS. One of
the templates should be matched by the Bearer Capability values sent by the
network. The first number in the list is the Bearer Capability request sent by the
Coral to the network on outgoing calls.
Modify and define Templates in BCCOS Templates beginning on page 26-3. This
branch only defines which templates are used for the selected BCCOS number.
FROM/TO BCCOS 0..63;

0 is system programmed and cannot be modified.
The remaining BCCOSs are programmable
Enter the range of required BCCOS numbers FROM the lowest TO the highest
number.
TEMPLATES Up to 32 different template numbers can be entered.

A valid template number is a number between 0 and 31.
The numbers are entered between parentheses, with each number
separated by commas or spaces.
To remove all numbers, enter ‘( )’ (empty parentheses);
See Table below for defaults
Enter the list of template numbers to be included in the current BCCOS.
BCCOS Control ROOT,5,0,1

Table 26-1: Default Values for BCCOS #’s
BCCOS # TEMPLATES
0 (0,1)
1 (1,0)
2 (3,0,1,2)
3 (3,2)
4 to 63 ()
26-5
NSF ç ROOT,5,1
Network Specific Facility (NSF) defines the services provided by various carriers
(e.g. INWATS, ACCUNET, MEGACOM). The NSF is required to implement Dial
Services (see Dial Services beginning on page 15-11).
FROM/TO NSF 0 to the maximum defined in SIZ, see NETWORK_FACILITIES (page 4-20);
All
Enter the range of required NSF numbers FROM the lowest NSF number required
TO the highest NSF number required.
NAME 1 to 16 printable ASCII characters, R (Remove for BLANK);

See Table 26-2 below for defaults
Defines up to a sixteen character name for the NSF. The name is provided for
reference only and is not displayed anywhere else in the Coral system. See General
PARAMETERS See Table below for defaults

Defines the NSF parameters. The parameters are displayed in hexadecimal code,
separated by a comma and enclosed in parentheses (e.g. (1H,7H)). The sequence
of numbers in parentheses should correspond to the values Sent/Received To/From
the network indicating the requested service.
Enter two numbers between parentheses, with each number separated by a comma
or space.
The first value corresponds to either a Feature (enter: 0) or a Service (enter: 1).
The second value corresponds to the code for the requested network feature or
service (supplied by the carrier).
NSF ROOT,5,1
26-6
Table 26-2: Default Values for NSF #’s
NSF # NAME PARAMETERS

(in Hexadecimal
Codes)
0 INWATS (1H,4H)
1 WATS_MAXBAND (1H,5H)
2 ACCUNET (1H,6H)
3 LONG_DIST. (1H,7H)
4 MEGACOM_800 (1H,2H)
5 MEGACOM (1H,3H)
6 INTERNAT.800 (1H,8H)
7 MULTIQUEST (1H,10H)
8 OPERATOR (0H,5H)
9 DEF.IEC_OPER (0H,6H)
10 to 255 BLANK ()
NSF ROOT,5,1
26-7
Call by Call ç ROOT,5,2

Not Used in this version.
To exit this node, type [CTRL]-U, [ESC] or any Direct Access Abbreviation.
Call by Call ROOT,5,2
26-8
Alternate Line ID ç ROOT,5,3

This branch allows defining an alternate Automatic Number Identification (ANI,
also known as Calling Party Number (CPN)) to be sent to the second party. This
feature is applied when a user requests that the ANI sent to the network for
outgoing calls should differ from the default ANI based on the extension number.
The number of different Line ID #'s that can be programmed in the Coral is defined
in SIZ, see NUMBER OF ALTERNATE ID (page 4-20).
The ALI index number is defined for each station, when required, in the relevant
station branch.
For SLTs, see: ALTERNATE_LINE_ID [28] (page 9-13) and SEC_ALTERNATE_LINE_
ID [29] (page 9-13).
For FlexSets, Keysets and WSTs, see: ALTERNATE_LINE_ID [66] (page 9-61) and
SEC_ALTERNATE_LINE_ID [67] (page 9-62).
For Trunk Groups, see: TRANSIT ALI (page 8-24).
FROM/TO ENTRY # 0 to the maximum defined in SIZES, Chapter 4;

All
Enter the range of required Alternate Line ID index entries. FROM indicates the
lowest ALI index entry number required. TO indicates the highest ALI index entry
number required.
COMPLETE NUMBER Yes/No

(Y/N)?
Defines whether or not the entire NUMBER (below) must be entered.
When COMPLETE NUMBER? is set to Y, the TYPE_OF_NUMBER and its
NPID (Numbering Plan ID) must be selected, otherwise the default is used. In this
Alternate Line ID ROOT,5,3

case, there is no filtering executed on the number.
When COMPLETE NUMBER? is set to N, only the alternate extension must be
entered. The TYPE_OF_NUMBER and NPID are accessed by the default values
and filtering is applied when defined.
 When COMPLETE NUMBER? is set to No, then only the NUMBER

parameter listed below appears. Otherwise, all the following parameters
appear.
26-9
NPID I (ISDN_telephony), U (Unknown)

Numbering Plan IDentification defines the characteristics of the NPID digits that
are sent from the Coral to the Called Network. This is one of the ISDN messages
sent to the network that informs it in which mode the Coral is sending the digits.
I: Coral to Public Network
U: The Public Network determines the incoming digit mode
TYPE_OF_NUMBER I (International),
N (National),
S (Subscriber),
U (Unknown, The digit format is decided by the CO)
This parameter is sent by the Coral to the public network on outgoing calls. It
indicates the format of the dialed number to the public network.
NUMBER Up to 16 digits (0 to 9, * and #) or R (Remove for None);

Default: (--) None
Defines the dial number that is used as the alternate ANI.
If COMPLETE NUMBER? (above) is set to Y, use this parameter to enter the
entire external public number including any required prefixes. If COMPLETE
NUMBER? is set to N, enter an alternate extension number only.
 When NUMBER is defined, the following parameters are available.

NPID Private:
TYPE_OF_NUMBER U (Unknown)
R1 (Regional-1)
L (Local)
Alternate Line ID ROOT,5,3
P (PISN)
R2 (Regional-2)
Defines the information sent by the Coral to the private Network, defining the
format of the dialed number for the private Network.
NUMBER Up to 16 digits (0 to 9, * and #) or R (Remove for None);

Default: (--) None
Defines the complete dial number that is used as the alternate ANI which the Coral
sends to the private Network.
26-10
ISDN Card Signaling ç DTDB,4

The PRI, BRI, and PRI-2DT card signaling parameters identify individual
D-Channels on an ISDN card. Access is accomplished by entering the physical
location of the card or the peer (Shelf, Slot and DSL) or the index number called
Signaling Channel assigned to the card or to the peer. In both cases, the displayed
information is identical except for the order of appearance.
The signaling index number is defined automatically by the system upon card first
initialization. Every card has specific number of D-signalling channels, as follows:
Table 26-3: Signaling Channels for ISDN Cards
Number of D-Signaling DSL# Card Name

Channels per Card
1 0 PRI-2DT (firmware Version 57 or lower)
2* 0-1 PRI-2DT (firmware Version 60 or higher)
1 0 PRI-23
1 0 PRI-30
4 0-3 4TBR
8 0-7 8TBR
* The enabling of the second trunk circuit (DSL#1) on the 2DT card requires authorization,
see 2DT WITH 2 CKTS on page 3-18.
When entering this mode, the PI prompts the user to enter “0” for access by
signaling channel or “1” for access by physical card location.
In both Physical Card Location and Signaling Channel, direct access is possible by
entering either the option name or the field number enclosed in brackets ([ ]).
Details for the ISDN Card Signaling are found on the following pages:
ISDN Card Signaling DTDB,4

ISDN Card Signaling: Signaling Channel........................................ 26-12
ISDN Card Signaling: Card location................................................ 26-13
26-11
ISDN Card Signaling: Signaling Channel ç DTDB,4,0

This option is used to display or modify signaling information by entering the
channel index number. This number is defined automatically by the system.
Every card has specific number of D-signalling channels, see Table 26-3
FROM/TO 0 to a maximum of 254;

SIGNALING CHANNEL All
Enter the required index number of the D-Channel. FROM the lowest channel
index number TO the highest channel index number.
This index number is defined automatically by the system. Every card has its own
number of D-signalling channels, as listed in Table 26-3. Therefore, the maximum
number of D-signalling channels is defined as: 1 for each PRI23 card, plus 1 for
each PRI30 card, plus 4 for each 4TBR card and 8 for each 8TBR card,
plus 1 or 2 for each PRI-2DT.
 When selecting 0-Signaling Channel, skip to NAME [0] on page 26-14.

ISDN Card Signaling: Signaling Channel DTDB,4,0
26-12
ISDN Card Signaling: Card location ç DTDB,4,1

This option is used to display or modify signaling information by entering the
card’s physical location in the system.
FROM/TO SHELF# All Shelves;

0: Coral FlexiCom400 (Coral II);
0..15: Coral FlexiCom 5000, 6000 (Coral III/4GC)
0..2: Coral IPx 500, 800
0..2: CDRS 200E
0..15: Coral IPx 3000, 4000
Enter the required range of shelf numbers FROM the lowest shelf number TO the

8..10: Coral IPx Office main unit (Shelf #: 1)
ISDN Card Signaling: Card location DTDB,4,1

Enter the required range of slot numbers FROM the lowest slot number TO the
FROM/TO DSL# 0 (Peer #0 of 2DT card functioning as PRI-23/30)

1 (Peer #1 of 2DT card functioning as PRI-23/30, see Table 26-3 page 9-11)
0..3 (4TBR card)
0..7 (8TBR card)
0 (PRI23 card)
0 (PRI30 card)
All
Enter the required range of Digital Subscriber Line (DSL).
26-13
NAME [0] 1..16 printable ASCII characters, R (Remove for BLANK);

BLANK
Defines the name of the card. This name is for reference only and is not displayed
anywhere else in the Coral system.
SIGNALING_  (Display Only)

CHANNEL [1]
Displays the index number of the D-channel. This number is automatically applied
by the system after card first initialization.
Every card has its own number of D-signalling channels, as listed in Table 26-3.
Therefore, the maximum number of D-signalling channels is defined as: 1 for each
PRI23 card, plus 1 for each PRI30 card, plus 4 for each 4TBR card and 8 for each
8TBR card, plus 1 or 2 for each PRI-2DT.
MAIN_
CHANNEL:
SHELF [2]  (Display Only)
Displays the physical shelf location of the card.
SLOT [3]  (Display Only)

Displays the physical slot location of the card.
CHANNEL  24(PRI23), 16(PRI30) or “--” for None

PRI only [4]
Displays the channel number in the PRI card which is used as D-channel signaling.
B_CHANNEL_ E (Exclusive), P (Preferred)

NEGOTIATION [5]
Outgoing Calls only
 Incoming calls are automatically Exclusive.
Determines procedure for network failure to accept a requested channel.
If Exclusive is chosen, failure to accept the requested channel by the network
causes the call to be disconnected by the Coral System.
If Preferred is chosen, failure to accept the requested channel causes the network
to suggest an alternative channel. As a result, the Coral switches the call over to the
suggested channel.
The procedure is transparent to the end-user.
26-14
PROTOCOL_ID [6] A: AT&T, ETSI (TBR {V8.60});

E: ETSI (European);
U: Australia;
Q: QSIG (Internal Network Trunks: ECMA 143/ETSI 300172/ISO DIS11572
Standard)
! WARNING:
Upon update, the BRI or PRI card is restarted and all calls are lost!
Determines standard network protocol: ISDN (public) or QSIG (private networks).

Do not define this parameter as QSIG for the PRI card accommodating trunk
groups with DIALING METHOD (page 8-25) set to Overlap in the Trunk Group
Definition (TGDEF) branch.
For BRI cards: PROTOCOL_ID is defined per card and not per (“slave”) exchange.
Therefore, BRI channel 0 must be defined for the required protocol. All the other
channels should then be defined with the same protocol.
The following message appears after defining the parameter:
Warning!! Use SEND_TO_CARD!
All calls will be disconnected upon update!
Use the SEND_TO_CARD option directly after defining the option for an immediate
update, otherwise, the update is performed 3 minutes later.
PROTOCOL_SIDE [8] [8]:QSIG and BRI: U (User or Slave), N (Network or Master);

(PRI[9]) [9]:Non-QSIG PRI: U (User or Slave), S (Symmetric)
 When QSIG is defined for PROTOCOL_ID above, S (Symmetric) is not

available.
Defines the DSL side at the particular exchange as the User (slave) or Network
(master) side. (A DSL must always have one exchange side defined as User while
the other side is defined as Network.) The Network side resumes call control in
restart (protocol failure) situations. In glare situations, Network side calls take
priority over User side calls.
The PSTN (i.e. any public network) is always defined as the Network side, leaving
the Coral system to be defined as the User side.
All ISDN applications (such as Video Conferences) are always defined as User,
thus enabling the Coral system to take charge as the Network side.
 Symmetric cannot be used if QSIG is defined as the PROTOCOL_ID or

with BRI trunks. (Therefore, define one side as User and the other as
Network.)
26-15
EXTENSION [10] Yes/No

BRI only
 This option appears only when N (Network) is defined for PROTOCOL SIDE
and PROTOCOL ID is not defined as QSIG.
Defines the Network extension as a port or trunk. Enter Y to connect the BRI line
to an external application or terminal equipment such as Video, Router, ISDN
telephone, etc. Enter No to connect the BRI line to another Coral or another PBX.
thus defining the BRI line as a trunk.
LOCAL_RINGBACK Yes/No
[11] PRI only
 This option appears only when N (Network) is defined for PROTOCOL SIDE
and PROTOCOL ID is not defined as QSIG.
Defines the source of ringback tone sent to the caller making a call over a PRI
trunk.
When set to Yes, the local Coral system sends the ringback tone to the calling party.
Otherwise, when set to No, the “far” PABX sends the ringback tone.
This parameter should be set to Yes when the “far” PABX does not support the
same ringback tone as wanted.
END_OF_DIAL_DIGIT Any ASCII character; REM (Remove for None)

[12]

Not relevant for most European systems.
Defines and adds a character to the end of the destination number (Called Party
Number) sent over the trunk to signal the end of dialing.
SENDING_COMPLETE Yes/No
for Outgoing Calls (No:CC0)
[13]
 Not relevant for CC0 systems (North America).
Defines whether or not a “sending complete” information element should be added
to the Called Party number, indicating that the entire number was transmitted.
SENDING_COMPLETE Yes/No
for Enblock Incoming
calls [14]
 Not relevant for CC0 systems (North America).
Enter Y if all incoming Network calls are known to be enblock calls. Enter N if
overlap as well as enblock Network calls are expected.
26-16
 The following parameter does not appear if PROTOCOL_ID above is set to

QSIG.
Send Connected Yes/No

Number to Public
For incoming network calls: The Coral sends a Connect message which includes
Network [15]
the Connected Number to the Public Network when this parameter is set to Yes.
If, however, the Public Network does not support the Connected Number feature
according to ETSI or National ISDN standards, set this parameter to No.
CONNECT_WHEN_ Yes/No
DEST_IS_NOT_ISDN
[16]
 Overlap Only, for Italian Market
This parameter is used in situations when an overlap call is sent to a system
(e.g., Interactive Voice Response - IVR) that sends back an ISDN progress
message: Dest_is_not_ISDN.
When set to Yes, this parameter enables the Coral to switch to a connect state and
start sending DTMF tones to the terminating device or terminating non-ISDN
switch after receiving the Dest_is_not_ISDN message.
Set this parameter to Yes in order to send DTMF tones before connect (after
incoming digits have been received) when a PRI Progress message dest_is_
not_ISDN is received from the far side (CO or PBX).
DTMF_WHEN_CALL_ Yes/No
PROC (OVERLAP
ONLY) [17]
 Overlap Only, for Italian Market

This parameter is used in situations when an overlap call is sent on a PRI trunk to
an application (e.g., Interactive Voice Response - IVR) that sends back an ISDN
Call Proceeding message (88H) before a Connect message is received.
When set to Yes, this parameter enables the Coral to start sending DTMF tones to
the terminating device after receiving the ISDN Call Proceeding message and
before a Connect message is sent (effectively not charging for the call).
Set this parameter to Yes in order to send DTMF tones before connect (after
incoming digits have been received) when a PRI Progress message call_
proceeding is received from the far side (CO or PBX).
MLPP_SUPPORT [18] Yes/No
 MLPP can only be activated over BRI, PRI (AT&T protocol only) or UGW
trunks.
Defines this D_Channel as one that supports MLPP when set to Yes.
26-17
TBCT_FEATURE_ Yes/No
ENABLED [19]
TBCT requires the following ISDN Card Signalling (DTDB, 4) settings:
• PROTOCOL_ID [6] (page 26-15) is set to AT&T
• PROTOCOL_SIDE [8] (PRI[9]) (page 26-15) is set to User
Define this PRI channel as TBCT feature enabled (Yes).
TBCT_SERVICE_ 0..255
PROVIDER_GROUP
Define the SERVICE PROVIDER GROUP number for this PRI channel.
[20]
The TBCT feature can only be activated among PRI channels sharing the same
TBCT Service Provider Group number.
TBCT transfers are allowed only between callers of the same TBCT groups.
Adjacent Entity Range: Any number

Number [21] Default: The index number defined by the system for this SIGNALING_
CHANNEL [1]
Define the same unique Adjacent Entity Number for all channels connected to the
same entity (Coral, public network, other vendor, etc.).
For Example: Define all the D Signalling Channels from the same or different
cards, connected to the same Coral with the same Adjacent Entity number.
Filter_out IN_BAND_ Yes/No

PROGRESS [22]
Set this parameter to Yes to filter out the IN_BAND Progress indicator (ISDN
progress #8 message) for incoming calls.
Set this parameter to Yes in order to block the IN_BAND Progress indicator from
being sent to the CO when it is not compatible with the CO’s call progress.
Initiate IN_BAND_ Yes/No

PROGRESS on alert
[23]
 Not relevant and not displayed for QSIG trunks
When this parameter is set to Yes, the Coral sends the IN_BAND Progress ISDN
message (progress #8) to an incoming ISDN trunk that reaches a ringing (alerting)
station.
If this parameter is set to No, then the Coral does not initiate an IN_BAND
Progress indicator for the call.
If an IN_BAND Progress indicator is received on an ISDN/QSIG trunk that is the
partner of the call, the Coral delivers the indicator to the ISDN trunk depending on
what is defined above for Filter_out IN_BAND_PROGRESS [22].
26-18
Send Redirecting Yes/No

Number [24]
For PRI/BRI trunks that are configured to ETSI or ATT&T, but not to QSIG (see
PROTOCOL_ID [6]), this parameter defines whether or not the re-directing number
(i.e. the number that performed Call Forward) is sent to the forwarded destination.
When set to N (No), Coral sends the number of the call initiator to the forwarded
destination. When set to Y (Yes), Coral sends the redirecting number to the
forwarded destination. This ensures the following:
• The call will be recognized by all service providers, thereby allowing the call
to be forwarded to the intended destination.
• The caller will be able to access the Voicemail of the forwarded destination.
Send Name [25] Yes/No

or higher)
 This parameter is only displayed for AT&T or QSIG channels.
Defines whether or not to send the caller’s name in setup messages for outgoing
calls.
SYNC_CHANNEL Yes/No
[27] BRI only

Enter Yes only when PERMANENT_ACTIVE_CHANNEL [28] BRI only below
is set to Yes.
This parameter is relevant when the BRI card is selected as the PRM or SEC clock
reference source (see T1, PRI, TBR, 30T/x, 2DT Synchronization beginning on
page 8-98). In such a case, one of the 4 or 8 channels (4TBR or 8TBR) is
automatically selected by the system for synchronization source.

This parameter determines whether or not the current channel may be one of the
synchronization sources.
PERMANENT_ Yes/No
ACTIVE_CHANNEL
This parameter is determined according to an agreement or a request of the CO at
[28]
the far side.
BRI only
N: The line is silent and inactive (data does not flow through the line and it can not
operate as a synchronization clock source) when no conversation is taking place.
Y: The line is permanently active even if there is no conversation taking place.
POWER SUPPLY [29] Yes/No

TBR-P Card Only
Defines whether the 4/8TBR-P cards, when installed, supplies power (-48V: US
systems or -42V: European Systems) for the BRI lines to the ISDN terminal
equipment.
26-19

TEI ASSIGNMENT [31] Fixed/Auto (for Network or Master)

BRI only
Defines the Terminal EndPoint Identifier for layer 2 of the protocol
communications. A fixed TEI assignment is a preassigned value defined as 0.
An automatic TEI assignment is defined automatically by the Network or User side
(see PROTOCOL_SIDE [8] (PRI[9]) above).
Generally, a Fixed TEI assignment (enter F) is used when the Coral is connected
to another Coral or to a Public Network (the CO).
The Automatic assignment (enter A) is used when the Coral BRI line is defined as
Network (see PROTOCOL_SIDE [8] (PRI[9]) above) and is connected to an ISDN
application such as Video Conference or Router, etc. or when being used for a
multipoint BRI support.
EXTERNAL_LINE_IS_ Yes/No
PHYSICALLY_
Identifies the BRI port as active and connected to a physical line (Y). When the port
CONNECTED [33]
is not connected to a line, enter N to enable a reset option for the BRI line. When
BRI only N is defined, the BRI line is disabled and the channel LED is lit.
 It is advisable to have this parameter defined as Y for each signalling

channel unless there are particular problems with the specific channel.
26-20
QSIG The following five parameters appear only if PROTOCOL_ID [6] above is set to
Definitions: QSIG. The following requirements must be met when defining these parameters:
• PRI/BRI card version 6.0 or higher is required between all nodes.
• The next five parameters must be defined identically in all the network nodes.
• Network PABXs with Coral software versions lower than 10 (and PRI/BRI
card versions lower than 6.0) do not support CISC (Call Independent
Signalling Connection). Therefore, Network Camp-On, Follow-Me and Divert
features cannot work between the nodes or via a node with a PRI/BRI card
version lower than 6.0.
Support Call Yes/No

Independent When upgrading from Version 9, the default is set to N.
Signalling Connection
Set this parameter to Y in order to support CISC calls (D-channel signalling with
(CISC) [34]
no B-channel (voice)) thus enabling using QSIG Network features between nodes
such as Camp-On and Follow-Me. Once a connection is made between the two
parties, signalling continues between both sides as required by the application.
Set to N if any one of the network nodes does not support CISC.
Transit Counters in Yes/No

CISC calls [35] When upgrading from Version 9, the default is set to N.
Defines whether to set Transit Counters for the CISC calls. The Transit Counters
help avoid an endless loop scenario of forwarded calls. See TRANSIT COUNTER [0]
on page 28-3 for more information.
NET DIVERSION [36] Yes/No

When upgrading from Version 9, the default is set to N.
Defines whether or not the Coral attempts to re-route calls to forwarded
destinations (as opposed to direct switching) in other PABXs by using QSIG
protocol.
This parameter affects the features Call Forward and Call Divert Network features.
Set this parameter to No if one of the PABXs in the network does not support QSIG
Call Forward by re-routing (otherwise a delay in the Call Connect Process may be
incurred).
26-21
TRANSIT_COUNTER_ ECMA/ISO
CODING [37]
A Transit PBX sends the call information in code form. This parameter defines
which QSIG code form is implemented. Enter ISO when an international standard
is needed. Enter ECMA for older European standards. ECMA standards have been
altered to conform to ISO standards and is thereby used in most cases.
The technician should match the QSIG code form to the code form used in the
system that the Coral is connected to.
PROTOCOL PROFILE ECMA/ISO

[38]
Defines the Protocol Profile field in QSIG Facilities used for Coral Features used
in this network node. The Protocol Profile is defined as 11H for ECMA or as 1FX
for ISO. All the network node PABXs should have the same Protocol Profile
defined so that they may communicate.
! WARNING:
Upon update, the BRI or PRI card is restarted and all calls are lost!
Path Replacement Yes/No

re-use of connection
If this D-Signalling Channel is connected to voice-over-data equipment (frame

element [39]
relay or IP), then define this parameter as No.
26-22
SPID/DN 0-7  CCO only

The following 16 parameters appear only if PROTOCOL_ID is defined as ATT
and PROTOCOL_SIDE is defined as Network. They are used to support a
multipoint TEI assignment (AUTO) thus emulating a Coral BRI interface.
• Also requires TBR card version 5.22 or higher.
• Define N_SPID_DN_PER_DSL (Sizes Branch) not equal to zero.
SPID 0 [41] Any valid SPID #
SPID 1 [43]
fSPID 2 [45]
SPID 3 [47]
SPID 4 [49]
SPID 5 [51]
SPID 6 [53]
SPID 7 [55]  BRI trunks only

Enter the CO defined Service Profile ID needed to establish a multipoint BRI
device. SPID 0 is the ID for the first device, SPID 7 is the ID for the 8th device. Up
to 8 ISDN devices can be setup up on one BRI DSL line.
If this Coral system is the User side, then the CO is the BRI provider and supplies
the SPID number.
If this Coral system is the Network side, then Coral is BRI provider. Enter the SPID

number assigned to the ISDN application. Use the DN with a prefix.
Use a public library dial number to dial the ISDN application. Define the Public
Library Number as a network number when calling the ISDN application within a
QSIG network. See Public Library (page 11-2) for instructions on programming
public libraries.
Define the maximum number of SPID per DSL in SIZES (see page 4-20).
26-23
DN0 [42] Any valid Device #
DN1 [44]
DN2 [46]
DN3 [48]
DN4 [50]
DN5 [52]
DN6 [54]
DN7 [56]  BRI trunks only

Enter the corresponding Device Number for the SPID defined above. This is a
public dial number used to activate the device.
NUMBER OF Not Used

TERMINALS [57]
This parameter is not used.
[58]
Transfers the updated card database immediately to the PRI or BRI card.
Regardless of entry, routine diagnostics periodically resend the card database to the
cards, including all the updates made. This parameter is used only in the Update
mode.
! SEND_TO_CARD causes:
1. The card to reset.

26-24
27 MAP, CLA and CoraLINK™
This chapter describes the Management Application Platform (MAP) and the
various CoraLINK database options as relates to the MAP, CLA or CLA-ATS card
on the following pages:
MAP............................................................................................................27-2
CoraLINK ...................................................................................................27-8
CoraLINK: CLA_STATUS ...................................................................... 27-11
CoraLINK: CLA_SIZES ..........................................................................27-15
CoraLINK: WAIT_QUE...........................................................................27-16
27-1
MAP, CLA and CoraLINK™ PI Reference Manual
MAP ç ROOT,3,10
The Management Applications Platform (MAP) serves as a hardware/software
platform for application management and IP connectivity. It allows managing the
different external software applications that interact with the Coral, as well as some
of its internal card software, via a single platform. It, thereby, serves as a hardware
platform for application management as well as IP connectivity. The allotted
managed software differs based on the Coral system.
MAP Card Provides Coral Version
15 or lower 15.5 or higher

CoraLINK Adapter (CLA) for COMPOSIT and Yes Yes
FlexCT CTI (Computer Telephone Interface)
applications.
CNCM direct IP access to a variety of system No Yes

management applications, such as:
Wakeup, PI, CVD, Traffic, CFM, Charge,
SMDR online/backup, MCT, etc.
MAP Platforms per System:
IPx Office systems:

In the Coral IPx Office system, the PUGW, MAP and CoraLINK Adapter
(CLA) software are embedded on the MCB Office card and share the same
IP address.
FlexiCom 400, 5000; IPx 500, 800, 3000; and CDRS 200E systems:
For these Coral systems, the MAP software is stored on a daughter board on
the Coral Main Control Processor cards (MEX-IP2, MCP-IPx2, MEX-IP and
MCP-IPx) called the MAP. This is an optional system card that may be
purchased separately from the Coral system.
Only one (single card) of the following: MAP card or CLA cards may be
MAP ROOT,3,10
installed on:
MEX-IP2 card for Coral FlexiCom 400 (with HDC controller), 5000 and
IPx 800, 3000.
 Coral IPx 3000 and FlexiCom 5000 systems with Duplicated Common
MCP-IPx2 card for Coral IPx 500; and CDRS 200E
Control require duplicated MAP cards. The CLA and MAP card can be
mixed in a Duplicated Common Control system.
FlexiCom 6000 and IPx 4000 systems:

For these Coral systems, the MAP is not available, in the current version.
27-2
PI Reference Manual MAP, CLA and CoraLINK™
MAP IP Address Definition

The IP Address for the MAP is defined in the PI database in the following
locations:
Coral System MAP Address updated in branch:
IPx 500, 800, 3000 IP: General branch, see MAP: (page 29-78)
FlexiCom 400 (with HDC controller), 5000 parameters.
CDRS 200E • The CLA adopts its IP address from
the MAP address as well.
IPx Office UGW: Current Configuration (page 29-13)

• MAP address is the UGW address
• The CLA adopts its IP address from
the MAP address as well.
Coral FlexiCom 6000 ATS systems do not support MAP platform.

Coral IPx 4000
The following table describes which software applications are managed by the
MAP software per different Coral system.
Table 1: MAP application per Coral System

Application IPx 500, 800, 3000 IPx Office IPx 4000
FlexiCom 400, 5000 FlexiCom 6000
CDRS 200E
CNCM   
(Coral software
version
15.5 or higher)
CoraLINK (CLA)   
UGW   
MAP ROOT,3,10
For more information about the MAP, refer to the following manuals:
• Chapter 6 in the “Coral Control Cards (for FlexiCom 200, 300, 400, 5000;
IPx 500, 800, 3000; and CDRS 200E systems) Installation Manual”
MAP Software Upgrades:

• FlexiCom 400,5000; IPx 500,800,3000; and CDRS 200E systems:
The MAP card applications are upgraded with a file downloaded from the
TFTP server. All applications are upgraded using a local web portal.
• IPx Office systems:

The embedded MAP applications are upgraded with a file downloaded from
the TFTP server. Most applications are upgraded using a local web portal. The
UGW software is upgraded via the PI.
27-3
MAP branch:
The MAP serves as a software platform for application management and IP
connectivity.
This branch is used to view the Management Application Platform (MAP) and
CNCM software status, as well as allows the technician to reset the MAP software.
 If the MAP software is reset, all applications running from this platform
are also reset.
The MAP supports software applications as defined in Table 1 on page 27-3.
The MAP serves as a software platform for the CNCM, CLA and CUGW. These
items share the same IP addresses.
 When a MAP card is not installed (or an old CLA or FCLA card is
installed), than the following two parametrs (MAP Card and CNCM) will
show Inactive.
IP connectivity for the following PI port definitions is available when the CNCM
value is Active:
MAP Card Active/Inactive (Display Only)

Displays the status of the MAP card and its software operating system.
MAP ROOT,3,10
27-4
CNCM Active/Inactive (Display Only)

The CNCM application offers integrated Coral system IP connectivity to replace
the Coral KBn serial RS-232 connections.
The CNCM parameter displays the status of the CNCM application that runs on the
IPx Office or on the MAP card. It offers terminal IP connectivity between external
applications and the Coral system when Active.
Table 27-1 lists Coral RS-232 destinations that may be defined as TCP/IP clients
via the CNCM application. The serial KBn destination is redefined via the PI as an
IP port destination and the RMI, DRCM, or DRCF serial ports are not used.
RS-232 serial port destinations in the following branches can be assigned IP
connectivity, by entering the “99” string as the destination port number, and
are assigned the following default TCP/IP ports by the CNCM.
 The Default TCP Port numbers can be changed in the MAP application
software.:
Table 27-1: MAP Application Default Port assignment for IP Socket
Parameter PI Branch Name Default Description

Name TCP
Port
DEST Wakeup Control 11001 Determines the output terminal destination for the wakeup
report.
[4] (page 20-3) (Route: Wakeup,0)
The ANN_DEST [0] is defined in SFE - Hotel (see page 6-41).
CHARGE_DEST SMDR Control 11002 Identifies the terminal port to which selected SMDR charge
printouts are sent, when requested by attendant (using feature
[15] (page 14-7) (Route: SMDR,0) codes #1972, #1978).
CALL TRACE Call Trace 11003 Determines the output terminal destination for printing the
Malicious Call Trace (MCT) reports. Station/Attendant reports
TERMINAL (page 1 Terminal (Route: are sent by dialing the appropriate print code (#1741- Station
7-10) Root,3,6) reports, #1743-Attendant reports). An example of a typical
Call Trace Report is shown on page 17-10.
CVD NA 11004 CVD IP Port
CFM NA 11005 CFM IP Port - used to link between CFM and Coral.
CFM (Coral Fault Manager) redundancy is enabled by
MAP ROOT,3,10
allowing alarm messages to be sent to two different TCP/IP IP
socket destinations.
TRAFFIC_ CVT Terminal Dest 11006 Traffic IP Port - determines the output terminal destination for
the Traffic report. CoralVIEW Traffic (CVT) Terminal
TERM# (page 17-9)
 NOTE: This destination is irrelevant for the

(Route: Root,3,5) Destination
CTR Internal Traffic feature.

The CVT system provides the Coral system with the ability to
accumulate and report on the system’s port traffic. The
information may be used for periodic checks on system load
and for trunking decisions. The traffic report presents data for
the following connection types:
• Stations to External line
• Station to Station
• Trunk Calls: Incoming/Outgoing
27-5
Table 27-1: MAP Application Default Port assignment for IP Socket
Parameter PI Branch Name Default Description

Name TCP
Port
SMDR_DEST SMDR Control 11007 Determines the output terminal destination to which generated
SMDR records are sent for on-line reports.
[14] (page 14-6) (Route: SMDR,0)
If the SMDR application is configured to Server mode, the
SMDR records are sent to the default TCP/IP socket defined
by the CNCM application. If the SMDR application is
configured to Client mode, the SMDR records can be sent to
up to two destinations (redundancy) that are defined in the
CNCM application. For further information, refer to Chapter 7
of the Station Message Detail Recording (SMDR)
 NOTE: This parameter is displayed in

Specifications
SMDR_DEST [14] parameter on page 14-6, in

SMDR Control menu.
SMDR buffering enables the SMDR records to be saved,
even if the connection is lost. Also enables SMDR
redundancy by allowing records to be sent to two different
TCP/IP IP socket destinations. The SMDR application may be
defined as a TCP/IP Client or Server, as required. For further
 This IP port is only relevant when one or

information, refer to Chapter 7 of the SMDR Specifications.
DIAG (page 17-8) Terminal 11008

Destination more of the following parameters (starting
(Route: MSG,2,2)
on page 17-4) is requested and set to Yes:
ALARMS, DEBUG, DI.COR, EXCEPT, or
FAILURE REPORT.
Determines the output terminal number to which the
requested Diagnostics messages (ALARMS, DEBUG,
 This parameter is only relevant when STIMUL

DI.COR, EXCEPT, and FAILURE REPORT) are sent.
STIMU (page 17-8) Terminal 11009

Destination on page 17-4, is requested and set to Yes.
9Route: MSG,2,2)
Determines the output terminal number to which the selected
stimuli messages (starting on page 17-6) are sent.
FROM/TO TERM Terminal Setup 11010 Determines the Program Interface (PI) terminal number.
# (page 17-22) (Route: TERM,0) Coral Database Binary Backup and ASCII are NOT supported
via MAP card.
PI, Room Status (Canned Messages) and CVD IP
MAP ROOT,3,10
connectivity, up to four concurrent users may connect via the

same TCP/IP socket
CFM KA IP 11012 Used for keep alive between CFM and Coral.
Port
 The MAP card does not support Initialization messages, GP messages and
other online Alarm messages, when used to communicate with the PI
(Program Interface) over IP.
27-6
MAP Card Reset? Yes/No

Allows to initialize and updating the MAP card software. When resetting the MAP,
all applications connected via the MAP, are affected and might not operate
properly. The following message is displayed:
Warning: Update will cause CARD INIT!
Any application hosted on this card will be affected
MAP card reset Y/N:
! Initializes the card causing the following:

1. The MAP software resets.
2. CNCM and CoraLINK applications are disrupted (calls are
unaffected).
3. In Coral IPx Office systems, the UGW circuit resets, causing
the disruption of service to all IP terminal equipment, and the
clearing of all IP call logs.
Enter Y to initialize the MAP software.

Enter N to escape this branch without updating the MAP software.
MAP ROOT,3,10
27-7
CoraLINK ç ROOT,7
The CoraLINK is a computer link to the Coral system used to connect and manage
a Coral system from the CoraLINK computer.
CoraLINK is implemented by installing an Adapter Card MAP, CLA, or
CLA-ATS. The CoraLINK Adapter is used for COMPOSIT and FlexCT CTI
(Computer Telephone Interface) applications.
In the Coral IPx systems the CoraLINK is implemented by software embedded
on the MCB Office card.
The CoraLINK Adapter appears in various configurations:
• MAP
• CoraLINK in IPx Office via embedded MAP
• CLA 386 (10Base-2 via Coax) [this type has been discontinued]
• CLA 486 (10Base-T via RJ-45) [this type has been discontinued]
• CLA 686 (100Base-T via RJ-45) with a Compact Flash memory card [this type
has been discontinued]
• CLA-ATS (10/100Base-T via RJ-45) with a Compact Flash memory card
The CLA/CLA-ATS card incorporates the application processor and Ethernet
10/100Base-T interface circuitry for the CoraLINK computer-telephony
integration (CTI) link. CoraLINK uses TCP/IP protocol, complies with the ECMA
179 and 180 standards. CoraLINK also supports the Novell TSAPI protocol, the
Intel Dialogic CT-connect, and IBM’s Callpath.
The CLA is installed in “piggy-back” fashion as a baby card on the MEX-IP2,
MCP-IPx2, MEX-IP, MCP-IPx, MCP-IPsl.
The CLA-ATS card is used in Coral FlexiCom 6000 and Coral IPx 4000 systems.
Dual Systems: In Coral FlexiCom 6000 and IPx 4000 redundancy control systems,
two identical CLA-ATS cards are provided, one for each of the control system sets.
Each CLA-ATS card is capable of providing full CTI link functions operating as
CoraLINK ROOT,7
part of the “Active” control card set.
 Although the Coral FlexiCom 6000/R and IPx 4000 are Hot Standby
systems, the twin CLA-ATS cards operate in a Standby/Duplicated mode,
not offering a Hot Standby option. Therefore, during a common control
swap, the CTI application restarts (thereby possibly disconnecting active
calls and functions).
Also, during the control swap, if a CLA-ATS card fails, the CTI application
fails and does not invoke a control changeover.
Coral FlexiCom 6000/R and IPx 4000 systems equipped with CLA-ATS require a
4XMM or 8XMM card installed on the 32GC cards.
27-8
CoraLINK Platforms per System:
FlexiCom 200, 300, 400, 5000; IPx 500, 800, 3000; and CDRS 200E systems:
For these Coral systems, the CoraLINK software is stored on a daughter board
on the Coral Main Control Processor cards (MEX-IP2 and MCP-IPx2) called
the CLA. This is an optional system card that may be purchased separately
from the Coral system.
Only one (single card) of the following: MAP card or CLA cards may be
installed on:
MEX-IP2 card for Coral FlexiCom 300,400,5000 and IPx 800, 3000.
MCP-IPx2 card for Coral FlexiCom 200, IPx 500, CDRS 200 and
 Coral IPx 3000 and FlexiCom 5000 systems with Duplicated Common
CDRS 200E
Control require duplicated CoraLINK platforms. The CLA and MAP card
can be mixed in a Duplicated Common Control system.
IPx Office systems:

In the Coral IPx Office system, the MAP and CLA (CoraLINK) software are
embedded on the MCB Office card and share the same IP address. The
CUGW also shares the same IP addresses.
FlexiCom 6000 and IPx 4000 systems:

For these Coral systems, the CoraLINK software is stored on the CLA-ATS
card. This is an optional system card that may be purchased separately from the
Coral system.
The CoraLINK is a Computer-Telephony Integration (CTI) Link for the Coral
system, which provides an Open Architecture Interface (OAI) to the call
processing and management circuitry. CoraLINK provides a means for external
computer applications to monitor call activity and establish and manipulate calls
through the Coral system. With CoraLINK, the Coral system functions as a
universal communications switching platform for use in custom and specialized
CoraLINK ROOT,7
communication applications.
The Coral system with CoraLINK can use caller number identification to tailor
greeting and instruction announcements played by the Coral system to each caller.
The computer can then establish connections for, or release the caller as determined
from the caller’s dialed responses.
The CoraLINK can operate in any computer environment including the Novell
NetWare LAN with Novell’s NetWare Telephony Services.
For more information about the CLA, CLA-ATS and CoraLINK, refer to the
following manuals:
 CoraLINK Reference Manual
27-9
 Chapter 2 in the “Coral FlexiCom and IPx Product Description”
 CLA: Chapter 6 in the “Coral Control Cards Installation Manual”
 CLA-ATS: Chapter 8 in the “Coral FlexiCom 6000 and IPx 4000 Installation
Manual”
Minimum requirements for defining CoraLINK:
1. Define a maximum for WAIT_QUE and CALL_SERVICES in SIZ (see page
4-18).
2. Define dial numbers in the General NPL and choose type 38-WAIT_QUE.
This chapter describes the various CoraLINK database options as relates to the
CLA or CLA-ATS card and to the IPx Office on the following pages:
CoraLINK: CLA_STATUS ...................................................................... 27-11
CoraLINK: CLA_SIZES ..........................................................................27-15
CoraLINK: WAIT_QUE...........................................................................27-16
CoraLINK ROOT,7
27-10
CoraLINK: CLA_STATUS ç ROOT,7,0

SAU Requirement
CLA_STATUS allows displaying the status of the CLA card and CoraLINK
software within the Coral installation or updating the internet address. Field
numbers are given in square brackets.
 Recommendation: After updating one or more parameters in CLA_

STATUS, perform a manual reset in CLA_MAINTENANCE [7,2,0].
CARD_EXIST [0]  Yes/No

Informs whether or not a CLA or CLA-ATS card, or CLA application in IPx Office
systems, is installed in the system.
For Coral FlexiCom 6000R and IPx 4000/R systems with CLA-ATS card, the
following messages may appear:
Message on Message on Description Recommenda-

Active Side Standby Side tion
Y (No XMM Card) Y (No XMM Card) There is a CLA card but Install a 4XMM or
no XMM is installed on the 8XMM card on the
32GC card. The CLA card 32GC.
cannot function without an
XMM card installed in the
system.
Yes Not Allowed in The CLA card is installed The system must
Standby on the Standby side, but return to proper Hot
cannot function in this Standby functioning
mode. Only the CLA on before the CLA on the
the Active side is non Active side can
functioning. function properly.
Yes Not Allowed in The CLA card is installed
CoraLINK: CLA_STATUS ROOT,7,0

Maintenance on the Maintenance side,
but cannot function in this
mode. Only the CLA on
the Active side is
functioning.
Yes Not Allowed in The CLA card is installed

Faulty on the Faulty side, but
cannot function in this
mode. Only the CLA on
the Active side is
functioning.
CARD_VERSION [1]  CLA Card Version Numbers

Defines which CLA software version is installed in the system. This parameter is
displayed only when CARD_EXIST above is set to Yes (i.e. the card is installed).
27-11
WORK_STATUS [2]  See table below;

Defines whether the CLA software is active. If the card is inactive, a status message
is displayed (see table below). Recommendations to correct the problem are listed
in the table below.
This parameter is displayed only when CARD_EXIST above is set to Yes (i.e. the
CLA software is Active).
Status Definition Recommendations

Message
CLA IS The CLA software is N/A

ACTIVE installed and
functioning properly.
NO CLA The CLA software Perform a CLA software

VERSION version is not installation.
programmed. See the relevant Coral
Installation Procedure Manual or
CoraLINK Reference Manual.
CHECKSUM The CLA software 1. Install a new software

FAILURE version is faulty. version.
2. Replace the CLA card.
SHARED RAM Communication Replace the CLA card.
FAILURE between the Coral and
the CLA Card by
means of a SHARED
RAM is faulty.
RAM FAILURE The RAM in the CLA Replace the CLA card.
is faulty.
There is no Call your dealer.

NO
AUTHORIZATION authorization to (see page 3-21) 40-CoraLINK
activate the CLA
software, but the card
is installed.
INIT FAILURE The card or software 1. Perform a Reset Operation.

was not initialized. 2. Check that the CLA
software version matches
the Coral software version.
3. Perform a software
installation.
4. Replace the CLA card.
27-12
INTERNET_ADDRESS See Network Administrator;

[3] 192.114.94.165
 The IP address is not relevant for IPx Office systems because the MAP address
(and the CLA address) for IPx Office systems is the CUGW address. The MAP
software status information can be viewed in the CNCM (page 27-5) branch
(Root, 3, 10).
Beware that updating the CLA IP addresses in Coral IPx Office systems based on
MAP software causes an update to the CUGW IP addresses. The following
warning is issued:
This is a CLA Application on IPx Office system.
Update IP parameters via UGW branch.
Defines the IP address for this Coral in the network. The address can be acquired
only from the network administrator.
SUBNET_MASK [4] See Network Administrator;

255.255.255.255
Defines the Internet address for this Coral. Alternatively, use this parameter to
create an address that enables distinguishing the network ID portion of the IP
address from the host ID. Subnet Masks are also used to further segment an
assigned network ID among several local networks.
! All computers on a physical network should use the same subnet mask
and network ID, otherwise, addressing and routing problems can occur.
ROUTER_ADDRESS See Network Administrator;

[5] 255.255.255.255

Defines the router address for this Coral in the network. The address can be
acquired only from the network administrator.
LAST_CLA_INIT [6] 
Military or US time and date, see DATE_MODE (Eu/USA) [16] (page 6-24)
Default: ------
Displays the hour and date of the last CLA Initialization process.
27-13
LAST_INIT_CAUSE [7]  See Table below

Displays the cause for the last CLA Initialization process. A table listing the
different status messages for this parameter is given below:
CLA Message Explanation

CLA_NO_INIT No Initialization has been performed on the CLA card.
CLA_HB_FAIL CLA Hard Bit (Shared Memory) Test Fail
CLA_DUMMY_MSG_FAIL Not Used.
CLA_READY_FOR_CORAL_FAIL Initialization Phase Error
CLA_SELF_INIT_FAIL CLA Self Initialization Detection.
ADD_CLA There is insufficient memory. Add CLA Retries.
CLA_INIT_TIMEOUT CLA Initialization was not completed within the specified

time limit.
CLA_PI_FULL_REQUEST PI CLA Reset Request
CLA_PI_WARM_REQUEST Not Used.
INIT_STATUS_ERROR An error occurred after the beginning or during the

initialization of the CLA card.
CLA_SIDE_SWAP Coral FlexiCom 6000/R (ATS) and Coral IPx 4000/R

systems only:
CLA initialized because the system swapped sides.
 Recommendation: After updating one or more parameters in CARD_

STATUS, perform a manual reset in CLA_MAINTENANCE [7,2,0].
UPDATE? Yes/No
*WARNING: UPDATE WILL CAUSE A CARD INIT!*
UPDATE (Y/N)?
! Updating the above parameters initializes the card causing:

1. The CLA software to reset.
Enter Y to load the modified CLA information.

Enter N to ignore all changes and return the CLA to previously assigned values.
27-14
CoraLINK: CLA_SIZES ç ROOT,7,1

SAU Requirement
This option is used to set the CoraLINK size parameters.
! Changing the CLA SIZES parameters causes:

1. The CLA software to reset.
Size parameters allocate the CoraLINK memory resources efficiently for a

particular installation. Modifying the size table utilizes unused memory space for
active features.
When making changes in the parameters listed in the table below, the changes are
temporary. The changes are only made permanent after entering Y for the Update
field at the end of the table. If Y was not entered for the Update field, the changes
are erased and the current system parameter values are displayed.
The table below describes examples of the maximum and default sizes for the
database memory that can be allocated for each type of Coral system.
The range maximum appears in parentheses on the PI screen.
! The sizes listed in this database are established by program default and
can be changed.
system.
MONITORED CALLS 0..1000

Defines the maximum number of calls that can simultaneously be monitored by the
CoraLINK application.
CoraLINK: CLA_SIZES ROOT,7,1

MONITORED 0..2000;
DEVICES 0..1000..2000: FlexiCom 200
Defines the maximum number of devices that can simultaneously be monitored by
the CoraLINK application.
UPDATE? Yes/No (*Warning*: Update causes a Card Initialization!)

Loads the modified SIZE information and resets the CLA software. When No is
entered, all previous entries are ignored and the system remains at the previously
programmed sizes.
 Before updating, ensure that WAIT_QUE and CALL_SERVICES in SIZ are

defined (see page 4-18).
27-15
CoraLINK: WAIT_QUE ç ROOT,7,3

SAU Requirement
Wait Queue is a special virtual destination used in the Coral system to support the
CoraLINK applications. Calls waiting to be routed to their final destination by
means of an external network application are temporarily placed in WAIT_QUE.
WAIT QUEUE can be a destination of the following features: Call Forward, DIL,
NIGHT_1, NIGHT_2, Incomplete Calls, Intercepted Calls, Public Library Outside
Line.
FROM/TO WAIT_QUE Any valid system Wait_Que dial number as defined in the General
# Numbering Plan, WAIT_QUE [38] (page 5-45);
All
Enter the range of required WAIT_QUE dial numbers. FROM the lowest dial number
TO the highest dial number required.
NAME:
SHORT [0] 1..5 printable ASCII characters; R (Remove for BLANK)
Defines the WAIT_QUE short name (up to 5 alphanumeric characters) which
appears on keysets equipped with a display. A WAIT_QUE name defined as BLANK
does not appear on the keyset display; the dial number is shown instead. See
General Rules for Entering Names on page 2-10.
FULL [1] 1..16 printable ASCII characters; R (Remove for BLANK);

Defines the WAIT_QUE full name (up to 16 alphanumeric characters), which
appears on keysets equipped with a display. A WAIT_QUE name defined as BLANK
CoraLINK: WAIT_QUE ROOT,7,3
does not appear on the keyset display; the dial number is shown instead. See
General Rules for Entering Names on page 2-10.
OVERFLOW_DEST [2] N (for None, to remove the current number) or

Any valid system dial number of a trunk, trunk group, station,
hunt group, boss group, Bell/UNA, Page Public Address, DVMS port, Dial
Service, Routing Access, another Wait_Que destination
Identifies the destination dial number to which all calls that were not handled by
the application during the allotted time interval (defined below) are routed.
27-16
TIME_TO_OVERFLOW 1..1200..65500 (1 unit= 0.1 second)

[3]

During this time period, a caller may hear a tone or a Music Source when
defined, see Music/Tone below.
Determines the time period that a call remains in queue before going to the
overflow destination.
TENANT GROUP [4] 0..63

Defines the tenant group number required for accessing the WAIT_QUE
destination. This can be used to block certain users from connecting to the current
WAIT_QUE.
MUSIC/TONE [5] M (Music)/T (Tone)

Defines the type of sound to be heard by the caller while in WAIT_QUE.
Enter M for a music source or T for a tone source.
MUSIC_SOURCE# [6] 0..3;

IPx 500 and CDRS 200E: 0 (MP-1), 1 (MP-2)
If Music was selected above, enter the number of the music source to be heard by
the caller while in off-hook. The range is limited by # OF MUSIC SOURCES
(1-4) (page 4-45).
RETAIN_WAIT_Q_ Yes/No
MUSIC_SOURCE [7]

This parameter is only relevant when MUSIC/TONE [5] above, is set to
Music.
Defines whether the Music Source that is sounded when a call entering the Wait
CoraLINK: WAIT_QUE ROOT,7,3

Que is answered, accompanies the call throughout the system (i.e. until disconnect
or transfer to another Hunt Group or Wait Que where this feature is also set to Y).
When this parameter is set to Yes, the call retains the same Music Source (for the
duration of the call within the system) even when the call is transferred to another
Wait Que or placed on Hold.
TONE# [8] 1..23 (excluding 8, 11, 14, 15)

If Tone was selected above, this parameter defines which Tone type is heard by the
caller while in WAIT_QUE. See Table 6-10 on page 6-97 and Table 6-11 on page
6-98 for more information about tones.
27-17

MESSAGE# [9] Default: None
SAU Requirement: CANNED MESSAGE on page 3-25
calling this not yet answered Wait_Que number. The text for Canned messages
0 to 15 is defined in NAME - (page 16-3) in Room Status/User Canned Messages
(Root,0,3,0).
WITH_ANSWER [10] Yes/No

Defines whether or not a trunk in WAIT_QUE should send a signal to the CO to
provide an answer signal towards the trunk waiting in a WAIT_QUE to be routed
to the final destination. This parameter is generally used to charge for the call.
WITHOUT_ALERT_ Yes/No
ON_ISDN [11]

ISDN Trunks only
Defines whether or not the Coral sends an Alert signal to the PSTN for incoming
calls. The Alert signal indicates a change in the call status (from incoming to
ringing).
This parameter is relevant only if WITH_ANSWER [10] (page 27-18) above is set to
No. (When set to Yes, the Coral sends both Alert and Answer signaling to the
PSTN.)
27-18
28 ISDNet™
This chapter is used to manage Coral Private Networks and includes the following
branches:
System Features - Network ........................................................................28-3
Node NPL .................................................................................................28-10
Node Content............................................................................................28-12
Special Numbering Plan Functions ..........................................................28-15
Coral Networks are composed of one or more Coral Systems, where each system
is described as a Network Node.
 Node Numbering PLan (NPL) includes a node numbering plan unique to the
network nodes and is not part of the system General Numbering Plan.
 Node Content defines all the node specifics, including Network routing and
filter information that relate to the local node in each network.
 Special Numbering Plan Functions formats information from the system

General Numbering Plan as it relates in particular to the Network.
Following is a partial list of terms relating to Networks:
PSTN Public Switching Telephone Network or the Central

Office (CO)
PINX Private Integrated Network Exchange
PISN (Network) Private Integrated Services Network consisting of

one or more PISN Exchanges. The PISN is
commonly referred to throughout the PI as the
“Network”.
Node Each Network exchange is defined by a node name

and number.
Internal Call Calls established within the PISN (Network)
External Call Calls external to the PISN (Network)
UDP Uniform Dialing Plan. Provides a uniform numbering

plan throughout the Network without deference to
the related Node number.
Non-UDP Non-Uniform Dialing Plan. This plan forces users to

access extensions from other Network Nodes
differently. Non-UDPs employ dial number filtering.
28-1
ISDNet™ PI Reference Manual
Procedure For Defining Networks:

1. Verify available numbers in the General NPL to use as dial numbers and
node numbers (NPL,0,1).
2. Assign a maximum number of Network Nodes in NET_NODES, as well as
for the other ROUTING: parameters listed in SIZ, (see page 4-21). In order to
use primary Network features, CALL_SERVICES (page 4-18) in SIZ should
also be defined.
3. Proceed to add the New Nodes in Node NPL as described in this chapter.
4. Define the different Route Access’ in Routing Access General Definitions
(LCR,1) relating to internal and external Network calls that are to be
defined in Node Content.
For private networks:
Define the NPID [3] (page 15-5) parameter for the Routing Accesses used in the
private network as Private.
5. Define each PRI card as a QSIG trunk in PROTOCOL_ID [6] (page 26-15),
DTDB,4.
6. Assign different TRUNK GROUPS in LCR, 3 for internal and external
Network calls (see ROUTING DEST NUM [9] on page 15-13).
Define Dial Services if not already defined.
7. Assign the list of Dial Services to the Route Elements needed in LCR,4.
8. Proceed to add the Node Content as described in this chapter.
9. Assign dial numbers to the newly added Nodes in the General Numbering
Plan (NPL, 0) and CHOOSE TYPE- 39 for Network. The system then
asks you to associate the new dial numbers with a Network node of your
choice.
28-2
PI Reference Manual ISDNet™
System Features - Network ç SFE,11 [0,0,4,1,11]
Network defines parameters for systems defined with networks. These parameters
must be defined identically at each node.
The following terms are used to define Coral QSIG Networks:
PINX: Private Integrated Services Network Exchange
PISN: Private Integrated Services Network
Cooperating PINX: the end PINX that establishes the new path
Requesting PINX: the end PINX that requests Path Replacement from the
cooperating PINX
Transferring PINX: the PINX that initiates Call Transfer
TRANSIT COUNTER 1..10..31

[0]
This counter prevents an infinite Routing loop scenario caused by call forwarding
between stations, from occurring within a Coral network node.
An infinite loop scenario can consist simply of David at Station A calling Steve at
Station B. Steve, however, leaves after 6PM, therefore Steve’s evening calls are
forwarded to Ruth at station C. Ruth does not work on Mondays or Thursdays, so
her calls are forwarded to Steve on those days. Therefore, when David calls Steve
at 6:30 PM on a Monday evening, the call may conceivably be routed ad infinitum.
This parameter limits the amount of times the call can be routed through the transit
Network node. The caller David in the above example, then receives a message
stating that the call was disconnected because there was no route to the destination

required.
INITIATE_TRANSFER_ Yes/No
BY_REROUTING [1]
Defines, system-wide, whether or not the Coral attempts to reroute calls in a
network.
When set to Yes, the Coral attempts to reroute the call, during call setup, using the
fewest trunks possible.
Normally, if a user from Node A calls a user from Node B and the call is transferred
to Node C, all trunks involved in establishing the communication remain busy until
the call is disconnected.
If the Coral is defined to reroute the call by setting this parameter to Yes, then all
the trunks used for the call connection are dropped and a new direct connection is
made between the user in Node A and the user in Node C. This facility helps avoid
congestion and maximizes the efficiency of the network and halves the rental costs.
28-3
Other types of transferred connections between nodes, also try to reconnect the end
users in the shortest, most direct available path when this parameter is set to Yes.
ALLOW_TRANSFER_ Yes/No
BY_REROUTING_TO_
Defines, system-wide, whether network calls to Voicemail applications are allowed
VM [2]
to be rerouted (i.e. when transferred, to reroute and drop extra adjoining trunk
lines).
Set this parameter to No, if DTMF digits must be sent to the connected Voicemail
application. DTMF digits are lost when rerouting.
ALLOW_TRANSFER_ Yes/No
BY_REROUTING_VIA_
The re-route feature works as follows: Station A, connected locally, calls station B,
NET_IP [3]
which is connected to a remote PBX. Station B transfers the call to station C, which
is connected to the same Coral system as station A. The re-route feature establishes
a direct link between A and C, cancelling the need for the remote link to B. This
option is transparent to the user and all the IP channels used for the call connection
are dropped and a new direct connection is made between Station A and station C.
Y (Yes) N (No)
B
B
Remote node
Remote node
QSIG QSIG
IP WAN over IP IP WAN
over IP
Local node
Local node
A
C A C
Call transfered with re-route Call transferred with join
This parameter is set for the local node.

When set to Yes (and INITIATE_TRANSFER_BY_REROUTING [1] parameter is set to
Yes), NET-IP calls will be re-routed after transfer to a local Coral-based phone.
When set to No, NET-IP calls will not be re-routed after transfer to a local
Coral-based phone, the call will continue to be routed via the remote PBX, and the
original link via remote PBX is maintained (transfer by join). The transferred call
occupies two NET-IP links.
28-4
MAX DIVERSIONS [4] 1..15..31

Determines how many times a call can be forwarded between local node or
network destinations. Setting this parameter avoids endless loop scenarios as in
Transit Counter above. However, this parameter also counts local destination
forwarding.
CAMP_ON [5] Yes/No

Defines whether or not the Camp On feature is supported for network calls. It does
not affect local camp on calls. Set to Yes only if all the PINXs in the Network
support QSIG Camp On.
NET MESSAGE [6] Coral/ECMA

Enables the Message Waiting Indication (MWI) feature by Coral or ECMA
standards.
Set to ECMA only if all the PABXs in the Network support MWI (Coral Generic
Version 11 and higher).
PATH REPLACEMENT Yes/No

[7] A NODE ID# (page 28-14) must be defined in the Node Content branch in
! order to implement the Path Replacement feature.
This parameter defines whether the Path Replacement (PR) feature can be
activated between Coral PINXs. Path Replacement is a standard QSIG feature
which allows replacing the path of an established Network call with a more
efficient or economical path when the previous path was set up using the Network

Call Forward or Network Call Transfer feature.
The Path Replacement (PR) is automatically activated by the Coral system after the
call is answered and after the DELAY_BEFORE_PR [6] (page 6-2) time out period
defined in Feature Timers expires.
 Note: 3-way Conference Circuits must be available to activate PR.

When this parameter is set to Yes, the following two parameters define which
features trigger the Path Replacement.
However, if this parameter is set to Yes, and one or both of the following two
parameters are set to No, then PR may still be employed because of a request from
the far side’s Coral PINX.
ACTIVATE PATH Yes/No

REPLACEMENT ON
Set this parameter to Yes to activate Path Replacement for Network Call Transfer
TRANSFER [8]
calls that have not been connected via a reroute (i.e. Path Replacement is used on
call transfer by trunk join). All path segments must be QSIG trunks.
28-5
The PR is activated only after the DELAY_BEFORE_PR [6] (page 6-2) time out
period defined in Feature Timers has expired.
ACTIVATE PATH Yes/No

REPLACEMENT ON
Set this parameter to Yes to activate Path Replacement for Network Call Forward
FORWARD [9]
calls (for any type of call forward) that have not been connected via a reroute (i.e.
Path Replacement is used on call forward by trunk join). All path segments must
be QSIG trunks.
The PR is activated only after the DELAY_BEFORE_PR [6] (page 6-2) time out
period defined in Feature Timers has expired.
NETWORKING_WIDE_ Yes/No;
VFAC [10] CC0 (USA): Yes/No
This parameter enables the account code to be displayed on the SMDR record of
the gateway node while using VFAC when a caller is connected to the gateway via
more than one node.
When this parameter is set to Yes from the caller’s node, the account code is
recorded and displayed on the gateway node.
When this parameter is set to No from the caller’s node, the account code is
recorded and displayed on the caller’s node.
Scenario: The network consists of nodes X and Y. Node X is the caller’s node, and
Y is the gateway node that routes all external calls.
1. A caller from node X places an external call, cleared with an account code
while using VFAC.
2. The call is routed via node Y.

3. One of the following occurs:
 When this parameter is set to Yes, the account code is displayed when the
SMDR is connected to node X and node Y.
 When this parameter is set to No, the account code is displayed only when the
SMDR is connected to node X.
28-6
NETWORKING_WIDE_ VFAC = Yes
Y X
PSTN
Account Code Account Code

displayed displayed
SMDR Device SMDR Device
NETWORKING_WIDE_ VFAC = No
Y X
PSTN
Account Code
displayed
SMDR Device
DEFAULT MLPP 0..6777215 or None

SERVICE DOMAIN
Defines a default domain number to be used when no Service Domain number was
[11]
entered for the station user’s COS MLPP SERVICE DOMAIN [82] (page 7-24).
MLPP NETWORK ID 0..65535

[12]
Defines the MLPP Network ID number used for QSIG messaging.
28-7
TBCT_TO_B_ Yes/No
CHANNEL_
Set this parameter to Yes in order to enable the TBCT (Two PRI B-channel
TRANSFER_
Transfer) for this Coral system.
ALLOWED [13]
The TBCT feature saves PRI resources. It enables the system to automatically
connect two different PRI calls via the PSTN and drop the PRI trunks. The two PRI
calls must be in answer state and are NOT involved in any of the following
features: IRSS, FlexiCall, Silent monitor, Call duration limit, Series or Conference.
User A
TBCT = No Coral system
PRI 1
Two Coral PRI channels Busy
are in used to transfer a PSTN
call from the Coral to an PRI 2
external station. Busy
User B
Connection via
the CORAL
User A
Coral system
TBCT = Yes PRI 1
Idle
Coral PRI channels are
PSTN
freed for more calls. (with TBCT)
PRI 2
Transferred call Idle
User B
progresses as before.
Connection via
the PSTN
Transferring an external PRI call via a Coral station to another external

station using another PRI channel engages two Coral PRI channels towards
the PSTN.
The TBCT allows the call to continue being conducted via the PSTN while
dropping both Coral PRI channels after the transfer, thereby limiting the
maximum number of channels used per PRI transfer by the Coral.
Billing for the two original calls continues in the same manner as if the
transfer had not occurred. The system allows the field service engineer to
reserve a specified number of SMDR records for call billing.
The TBCT scenario is possible only when the following PRI signaling
parameters for both PRI channels (DTDB,4 branch) are set as follows:
• PROTOCOL_ID [6] (page 26-15) is set to AT&T
• PROTOCOL_SIDE [8] (PRI[9]) (page 26-15) is set to User
• TBCT_FEATURE_ENABLED [19] (page 26-18) is set to Yes
• TBCT_SERVICE_PROVIDER_GROUP [20] (page 26-18) is set as required
28-8
In addition the TBCT feature requires:

• 2DT (PRI23/PRI30)
• UDT based PRI card (not old PRI) with firmware version 52.44 or higher
• CO trunk via PSTN should be NI2, Network
• TBCT feature activation according to GR-2865-CORE
ENABLE_TBCT_ Yes/No
WITHOUT_SMDR [14]
Set this parameter to Yes in order to enable the TBCT feature when no SMDR
records are available (i.e., TBCT_SMDR (page 4-16) in SIZES is set to 0, or all the
SMDR records are currently in use).
MAXIMUM_HOURS_ 1..24..250 hours

TBCT_CALL [15]
Defines the maximum call duration that can be listed in the SMDR records for a
TBCT call when an ENDCALL notification has not been received from the other
side.
28-9
Node NPL ç NODE,0 [ROOT,8,0,0]
The Coral Network consists of one or more Coral systems. Each Coral system is
defined as a Network Node with a related node number, node name and routing
information.
Node NPL is a numbering plan unique to the Network Nodes. It is operated
similarly to the General Numbering Plan but deals with manipulating the Network
Nodes and NOT their dial numbers. The dial numbers are manipulated as usual in
the General Numbering Plan.
The Network node number is limited to eight digits and is not displayed on the
keyset.
The following option menu is available for the Node numbering plan:
 Password Level 2 is needed to perform changes.

Option Description Success Message Failure Message
0 - Update Allows changing the Node Numbers Wrong Node NPL
existing Node Numbers. Updated Update-Please
Check !!!
1 - Display Displays the existing N/A Node NPL not
Node Numbering Plan by defined !!!
the Node numbers.
2 - Add Adds a Node to the Node Numbers Wrong Node NPL Add
Network. Added -Please Check !!!
3 - Remove Removes a Node from Node Numbers Wrong Node NPL
the Network. If Network Removed Remove -Please
dialing numbers are Check !!!
defined for this Node, the
Node cannot be
Node NPL NODE,0 [ROOT,8,0,0]
removed.
28-10
0 - Update
FROM/TO OLD All defined Network Nodes
NODE#
Enter the range of existing node numbers to be updated FROM the lowest node
number TO the highest node number.
FROM NEW NODE# All defined Network Nodes

Enter the beginning of the range of the new node numbers. The node number(s) and
their related index numbers are properly updated.
1 - Display
FROM/TO NODE # All defined Network Nodes
Enter the range of node numbers to be displayed FROM the lowest node number.
TO the highest node number.
The range of node numbers are displayed against their related index numbers.
2 - Add
FROM/TO NEW Any number (max: 8 digits)
NODE#
Enter the range of node numbers to be added FROM the lowest node number TO
the highest node number.
 Before adding new Nodes, ensure that NET_NODES (page 4-20) is defined.
ENTER INDEX # Any number (max: 8 digits)

Enter the index number for the beginning of the range of the new nodes. The
following node index numbers are automatically updated.
Node NPL NODE,0 [ROOT,8,0,0]

3 - Remove
FROM/TO NODE # All Network Nodes
Enter the range of node numbers to be removed FROM the lowest node number TO
 Before removing a node, all the dial numbers and other information in the
numbering plan relating to the node must first be erased.
A warning message appears confirming the delete operation.
28-11
Node Content ç NODE,1 [ROOT,8,0,1]
Node Content defines all information relating to each network node including
routing information as well as filter information relating to the local node.
Network Dial Numbers are defined in each node with a reference to the related
node. When manipulating Network dial numbers at a node, that node is considered
the local node in relation to the other nodes. For routing calls to other nodes within
the Network, the node must define a routing mechanism consisting of Routing
Accesses, Route Elements, Dial Services, etc.
Dialing within the network can consist of a uniform or a non-uniform dialing plan
method.
A Uniform Dialing Plan provides a unique numbering plan throughout the
Network. Thus, accessing extensions within a node is exactly the same as accessing
extensions within the Network (i.e. at other nodes). The network numbers are
defined in the numbering plan of each node and no filtering is performed on the
calling or called number. Network dial numbers in this plan are usually 4 or 5
digits.
When a Non-Uniform Dialing Plan is employed, accessing extensions within the
Network is different than accessing extensions within the local node. Within the
node, the extension is usually a shortened version of the full dial number. The dial
number is usually changed by filtering: adding, removing or changing the dial
number digits. Network dial numbers in a Non-UDP plan are usually 7 digits.
 The maximum number of digits employed in either type of dialing method

is eight.
All calls are then routed through a Route Element (i.e. a list of preferred Dial
Services) through the related Routing Access.
Node Content NODE,1 [ROOT,8,0,1]
Password Level 2 is needed in order to perform updates.
FROM/TO NODE# Any valid node number

Enter the range of node numbers to be defined FROM the lowest node number TO
The node number(s) must first be added. See Node NPL beginning on page 28-10.
FULL NAME 1..16 printable ASCII characters, R (Remove for BLANK);

Defines up to a sixteen character node name for network definition. The name is
provided for network maintenance only and is not displayed on the keyset during
dialing. See General Rules for Entering Names on page 2-10.
28-12
ROUTING_ACCESS # Any valid Routing Access dial number (see ROUTING_ACC [37] (page 5-44));
First Routing Access in Numbering Plan
 Only one local node is allowed for each Routing Access.

Defines the Routing Access number associated with the private Network. All nodes
in a Network belong to the same Routing Access. The local node uses the Routing
Access assigned to the destination node for the originating call setup message (see
Routing Access General Definitions-Chapter 15 for the call setup definition). This
parameter must receive a value, otherwise the Node cannot be defined.
LOCAL/REMOTE L (Local)/R (Remote)

Defines the Network node location as local or remote. When defining the Node
Content at each specific node, that specific node is considered the local node, and
all other nodes in the Network are considered remote nodes.
 Only one local node can be assigned per ROUTING_ACCESS #.

If a local node was previously defined for the relevant Routing Access #, then the
node definition as a local node is denied and the following message is displayed
informing you that the local node already exists and gives you the node's current
index number:
LOCAL NODE ALREADY EXISTS. INDEX OF LOCAL NODE 0, TRY
AGAIN.
When changing a node from Local to Remote, the local filters do not apply and the
following message appears:
Local Filters will be removed. Are you sure?
ROUT_ELEMENT # 0.. the number of ROUT ELEMENTS as defined in Sizes, (see Chapter 4)
All

Defines the Route Element which describes the list of Dial Services (trunk groups)
to route calls from the originating node to the destination node.
This parameter appears only for Nodes defined as Remote (see LOCAL/REMOTE
parameter above).
 If the node is defined as a Local network node, the following filter parameters
appear:
Filter parameters are used only for systems with non-UDP dialing systems.
DIAL_IN_FILTER See Table 8-3 on page 8-38

This filter is used for editing the incoming number.
The filter modifies received digits to match the internal network numbering plan.
Digits may be added, removed (i.e. ignored) or conditionally removed when they
match a specific pattern.
28-13
This filter produces a dial number of up to eight digits which is directed to a local
destination (e.g. station, hunt group, boss group, public library, etc.).
 Used only in non-UDP dialing systems.

DIAL_IN/CALLER_ 0 to max defined in SIZ (see OFFSET_FILTER (page 4-15))

OUT OFFSET R (Remove);
None
Defines which offset filter (see page 8-42) is relevant to the local node dial number.
This offset is used both to convert the incoming number to a local node dial number
and to send the calling extension number in an outgoing call.
OUTGOING: Performs the offset filter and then the node CALLER #OUT filter.
INCOMING: Performs the node DIAL_IN_FILTER and then the offset filter.
Used only in non-UDP dialing systems.
CALLER #OUT See DIAL_FILTER [10] on page 15-14; (Remove)

FILTER
Defines the filter applied on an outgoing ANI (Automatic Number Identification).
Used only in non-UDP dialing systems.
NODE ID# Range: Any available Coral NPL number; R (Remove for None)
Default: None (----)
Define a single and unique Node ID number for this Node. The Node ID# is used
to implement the PATH REPLACEMENT [7] (page 28-5) feature. If it is not defined,
Path Replacement cannot be implemented, an alarm is issued, and the following
message is displayed:
Warning: Advanced Features might misbehave!
A FEATURE index number (219) is automatically assigned in the NPL for this
NODE ID#, but it cannot be manipulated by the NPL. It can only be removed and
then reassigned a unused NPL dial number.
! This number is an ID number and while it is a dial number it cannot be

defined, changed or removed from the NPL.
In the NPL for the other Network Corals, this NODE ID# should be defined as a
NETWORK [39] (page 5-45) dial number.
28-14
Special Numbering Plan Functions ç NET,1 [ROOT,8,1]
This branch serves as an additional tool for accessing network information from the
system General Numbering Plan thus enhancing the user interface.
Password Level 2 is needed in order to perform changes.
0-DISPLAY The user can display node dial numbers by entering a range of network nodes. Each
(BY NODE) node is then listed against its related dial numbers.
1-MOVE Users, within the NPL at their Node, can move network dial numbers from one
NETWORK# network node to another node by using this option. The dial numbers, however,
BETWEEN remain exactly the same.
NODES
FROM/TO DIAL # All defined dial numbers

Enter the range of dial numbers to be moved from one node to another FROM the
lowest dial number TO the highest.
NODE# All defined Network Node numbers

Enter the node number to which the range of dial numbers should be moved to.
 The same procedure must be performed in each network node.

For Example: The dial numbers 530-4647 through 530-4649 are to be moved from
node XYZ to node 701.
Special Numbering Plan Functions NET,1 [ROOT,8,1]

Proceed to move the dial numbers to the new node by entering the information
requested:
FROM DIAL # 5304647
TO DIAL # 5304649
NEW NODE # 701
 This procedure is only a NPL procedure.

Therefore, if the dial numbers moved were saved as library numbers for
speed dialing or were saved in any programmed button, they must be
saved again and/or reprogrammed so that the PI system accesses the
numbers from the new node.
Requesting dial numbers that do not exist causes the following error message:
CANNOT EXECUTE THIS MOVE.
28-15
2-REMOVE This option removes node numbers from the General Numbering Plan.

NODE
NUMBERS Removing the node numbers removes all the dial numbers associated with
the node.
FROM/TO NODE # All defined Network Node numbers.

Enter the range of node numbers to be removed FROM the lowest node number TO
the highest. Enter the same number in both parameters to define just one node
number.
REMOVE NODE Yes/No

NUMBERS?
A warning notice appears before the node number/s are removed:
**WARNING** NODES dial numbers will be lost.
ARE YOU SURE (Y/N)? N
Enter Yes to remove the node/s or No to retract.
Special Numbering Plan Functions NET,1 [ROOT,8,1]
28-16
29 IP — Voice Over IP
This chapter is used to manage the Coral VoIP (Voice calls over Internet Protocol)
details and includes the following branches:
UGW (Universal Gate Way) ......................................................................29-7
UGW: Default Configuration.............................................................. 29-9
UGW: Current Configuration ........................................................... 29-13
IP Ports .....................................................................................................29-27
IP_Keyset .......................................................................................... 29-28
IP_SLT............................................................................................... 29-36
IP_LGS.............................................................................................. 29-38
IP_Net................................................................................................ 29-40
SIP Ports ...................................................................................................29-41

SIP Terminal ..................................................................................... 29-43
SIP Trunk .......................................................................................... 29-52
IP: Telephony Gateway (Coral Teleport) .................................................29-62

IP: General................................................................................................29-68
IP: Statistics ..............................................................................................29-79
IP: NET.....................................................................................................29-80
IP: ZONE..................................................................................................29-82
IP: SIP DOMAINS...................................................................................29-88
IP: SENTINEL Pro...................................................................................29-89
Software Upgrade .....................................................................................29-93

UGW Software Upgrade: Activate................................................... 29-94
UGW Software Upgrade: Cancel ..................................................... 29-97
IP Keyset Software Upgrade: Activate............................................. 29-99
IP Keyset Software Upgrade: Cancel ............................................. 29-103
Sentinel Software Upgrade: Activate ............................................. 29-106
Sentinel Software Upgrade: Cancel................................................ 29-110
29-1
IP — Voice Over IP PI Reference Manual
See the Coral Voice over IP Installation Manual for a description of the IP
system installation procedure as well as IP Keyset installation and initialization
instructions.
The Coral VoIP Advanced Communications Server provides an integrated IP
network while still maintaining use of the existing telecommunications network.
IP technology is incorporated by using standard Coral stations (keysets, SLTs and
Wireless) along with the latest IP station sets, such as the FlexSet-IP 280S, T207M,
T208M, T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Seies
(such as: P-335, P-450), T322, T328, FlexIP SoftPhone (FLIPS), SeaBeam
softphone,
or off-the-shelf third-party SIP units.
VoIP Glossary:
Bridge Device- A device interconnecting local area networks at the OSI Data Link
Layer, filtering and forwarding frames according to media access control (MAC)
addresses. (1) A device that connects two LANs. The LAN being connected can be
alike or dissimilar. (2) A network device that selectively determines the appropriate
segment to which it should send the signal. (3) The bridge performs two main
functions: Forwarding & Filtering.
Broadband - Wideband technology capable of supporting voice, video and data,
possibly using multiple channels.
DTE - Data Terminal Equipment, includes: monitor, computer, printer, server, etc.
DCE - Data Communication Equipment, includes: router, bridge, etc.
Enterprise Network - An information infrastructure, often combining private and
public facilities, to cover all of the locations operated by a single company or
corporate enterprise with a single communications fabric.
Ethernet - A local area network that connects devices like computers, printers and
terminals. Ethernet operates over twisted-pair or coaxial cable at speeds of 10 or
100 Mbps.
H.323 - A set of International Telecommunication Union (ITU) standards that
define a framework for the transmission of real-time voice communications by
means of IP-based packet-switched networks. Created in response to customers
who needed to use their existing IP networks to support voice communications, the
H.323 standards define a gateway and a gatekeeper.
Gateway - Gateways are points of entrance and exit from a communications
network. Viewed as a physical entity, a gateway is that node that translates between
two otherwise incompatible networks or network segments. Gateways perform
code and protocol conversion to facilitate traffic between data highways of
differing architecture. Gateway is a device that performs an application layer
conversion of information from one protocol stack to another. An older term
referring to a routing device.
29-2
PI Reference Manual IP — Voice Over IP
For example: A Coral system requiring a connection to the Internet (TCP/IP). The
PCM information is first sent to the PUGW card (and old discontinued cards: UGW
and UGW-E) which converts the information to TCP/IP.
Internet Address - Also known as an IP address. This is a 32-bit
hardware-independent address assigned to hosts using the TCP/IP protocol suite.
IP (Internet Protocol) - A networking protocol for providing a connection less
service to the higher transport protocol. It is responsible for discovering and
maintaining topology information and for routing packets across homogeneous
networks. Combined with TCP, it is commonly known as the TCP/IP platform.
IP Address - An address that uniquely identifies each host on a network or
Internet. A unique IP address is required for each host and network component that
communicates using TCP/IP. Each IP address includes a Network ID and a Host
ID. Network ID - identifies the systems that are located on the same physical
network bounded by IP routers. Host ID - identifies the host within the network.
Example: 131.107.3.24
Addressing Guidelines:
• Network ID cannot be 127. - 127 is reserved for loopback functions.
• Network ID and host ID cannot be 255 (all bits set to 1). 255 is a broadcast
address.
• Network ID and host ID cannot be 0 (all bits set to 0). 0 means “this network
only”.
• Host ID must be unique to the network.
IP Socket: An IP Socket is comprised of an IP address followed by a colon and an
IP Port number. A port is a 16-bit data value.
IP Telephony - The transmission of voice over an Internet Protocol (IP) network.
Also called Voice over IP (VoIP), IP telephony allows users to make phone calls
over the Internet, intranets, or private LANs and WANs that use the TCP/IP
protocol.
LAN (Local Area Network) - A network that interconnects devices over a
geographically small area, typically in one building or part of a building. The most
popular LAN type is Ethernet, a 10 Mbps standard that works with 10BaseT,
10Base2, or 10Base5 cables.
MAC (Media Access Control) - A protocol that defines the way workstations gain
access to transmission media, most widely used in reference to LANs. For IEEE
LANs, the MAC layer is the lower sub-layer of the data link layer protocol.
Primary functions: (1) Controls access to shared media. (2) Handles the network
topologies. (3) MAC address (Physical Address).
The MAC address is a 6 byte address coded on every: network adapter card (NIC),
FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL, etc.
29-3
MGCP - Protocol used to transfer media packets across the LAN or WAN. The
FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL are MGCP based
terminals.
Network - (1) A communication network is a collection of communication
channels. (2) An interconnected group of nodes. (3) A series of points, nodes, or
stations connected by communications channels; the collection of equipment
through which connections are made between data stations
Network Layer - A layer in the OSI reference model. The network layer provides
address resolution and routing protocols. Address resolution enables the network
layer to determine a unique network address for a node. Routing protocols allow
data to flow between networks and reach their proper destination. Examples of
network layer protocols are Address Resolution Protocol (ARP), Datagram
Delivery Protocol (DDP), Internet Control Message Protocol (ICMP), Interior
Gateway Protocol (IGP), Internet Protocol (IP), Internetwork Packet Exchange
(IPX) and Packet Layer Protocol (PLP).
NMS (Network Management System) - The system that controls network
configuration, fault and performance management, and diagnostic analysis
Node - A point of interconnection to a network
Peer-to-Peer Connections - A direct connection between two IP hosts (e.g.,
FlexSet-IP 280S to FlexSet-IP 280S) over the LAN, involving no intervention from
the Media Gateway Module.
PPP (Point-to-Point Protocol) - Provides a standard means of encapsulating data
packets sent over a single-channel WAN link. It is the standard WAN encapsulation
protocol for the inter-operability of bridges and routers over synchronous or
asynchronous circuits
RJ-45 Connector (Registered Jack-45) - A telephone connector that
accommodates up to eight wires. RJ-45 plugs and sockets are used in Ethernet and
Token Ring devices.
Router Device - An interconnection device that connects individual LANs. Unlike
bridges, which logically connect at OSI layer 2, routers provide logical paths at OSI
layer 3. Like bridges, remote sites can be connected using routers over dedicated
or switched lines to create WANs. Routers are responsible for tracking which
networks, or segments exist and how they can be reached. T router determines the
optimal path along which network traffic should be forwarded.
Routing - The process of selecting the most efficient circuit path for a message.
The process of finding a path for each packet, to a destination host.
Switch Device- A device interconnecting local area networks at the OSI Data Link
Layer. (1) A connectivity device that can perform bridging functions faster than a
bridge. (2) Increases usable bandwidth. (3) Overcomes traffic saturation problems.
SIP - Session Initiation Protocol - Signaling protocol for initiating, managing and
terminating voice and video sessions across packet networks. The P-Seies (such as:
29-4
P-335, P-450), T207S, T208S, T207S/NP, T208S/BL, T322, T328, SeaBeam are
SIP based terminals.
SIP Trunk - The SIP trunk allows customers to be connected directly to their ITSP
through pure IP connection. QoS is maintained (comply with the Service Level
Agreement) on one hand, and cost can be reduced on the other hand.
Subnet Mask - A method for determining the network ID in the IP address. A 32
bit value that is used to distinguish the network ID from the host ID. All bits that
correspond to the Network ID are set to 1(255). All bits that correspond to the Host
ID are set to 0.
Example:
• IP address: 131.107.16.200
• Subnet Mask: 255.255.0.0
• Network ID: 131.107.y.z
• Host ID: w.x.16.200
TCP/IP (Transmission Control Protocol/Internet Protocol) - A protocol
platform, known also as the Internet protocol suite, that combines both TCP and IP.
Widely used applications, such as Telnet, FTP and SMTP, interface to TCP/IP.
T.38 - The Coral provides the ability to handle Real-Time-Fax over IP using the
T.38 ITU standard in conjunction with a negotiation process through the Session
Description Protocol. This allows for reducing the required bandwidth, as well as
overcoming network impairments such as Packet-loss and Latency. The Coral
supports full Unified Messaging in conjunction with the SeaMail application to
provide Fax-to-email. G3 fax machines send the commands in compliance with the
T.30 standard to the Coral IPx Office system, which converts or encapsulates the
T.30 messages into T.38 data stream over UDPTL or RTP. These messages are sent
to the SeaMail (for Fax-to-email UM implementation) or to another IP
PBX/third-party gateway that converts it back to TDM-based signals and
terminates the fax on a T.30 device. Real Time Fax over IP utilizing the T.38 can
be sent over SIP Trunk to ITSP or to another IP-PBX of the customer's branch.
TFTP Server (Trivial File Transfer Protocol) - Protocol used when transferring
files over the Internet. This protocol is used to download FlexSet-IP 280S software
versions to the telephone from the internet.
URI (Uniform Resource Identifier) - URI is a compact string of characters used
to identify or name a resource on the Internet. The main purpose of this
identification is to enable interaction with representations of the resource over a
network, typically the World Wide Web, using specific protocols. URIs are defined
in schemes defining a specific syntax and associated protocols.
VoIP (Voice over IP) - Set of facilities for managing the delivery of voice
information using the Internet Protocol (IP). Voice information is sent in digital
form in discrete packets over the Internet instead of in analog form over the public
switched telephone network (PSTN). A major advantage of VoIP is that it avoids
the tolls charged by ordinary telephone service.
29-5
VPN (Virtual Private Network) - A restricted network that uses public wires to
connect nodes. A VPN provides a way to encapsulate, or “tunnel”, private data
cheaply, reliably, and securely through a public network, usually the Internet.
WAN (Wide Area Network) - A network that typically spans nationwide
distances and usually utilizes public telephone networks.
Coral VoIP Cards and Units:
MG: Media Gateway card that supports a number of media channels. T.38 Fax
relay is supported by this card. The MG module is a daughter board on the UGW
and UGW-E cards.
MRC: Media Resources Card that provides Media Channels and system resources
(DTR and MFR). The MRC is a daughter board on the PUGW and PUGWipx cards
and on the IPx Office system.
UGW (and UGW-E): Coral Universal Gateway Card used to provide for MGCP
VoIP endpoints in the Coral.
PUGW: Coral Universal Gateway card used to provide for SIP VoIP endpoints as
well as MGCP endpoints in the Coral.
CUGW: Coral Universal Gateway application used to provide for SIP VoIP
endpoints as well as MGCP endpoints in the Coral IPx Office.
Sentinel: Coral Units that provides for remote IP endpoints which enables
endpoint NAT traversal. The IP endpoints are regarded as internal endpoints
(i.e. Coral Stations).
Zone Isolation - Voice firewall capabilities can be created by defining separate
VoIP zones, such as Internet zone and Corporate LAN zone.
See the Coral Product Description for further product details.
29-6
UGW (Universal Gate Way) ç UGWC or IP,0 [9,0]
The PUGW, UGW-E, UGW, PUGWipx, UGW-Eipx, UGWipx, and CUGW

(herein referred to as the “UGW”) cards provide the Coral IPx/FlexiCom systems
with the ability to connect to the IP World.
All IP Keysets, IP terminals, IP trunks and external third-party IP Gateways receive
their Coral Signalling through a UGW type card (see IP Ports beginning on page
29-27).
The PUGW and PUGWipx incorporate a Media Resources Card (MRC) module
daughter board. The UGW-E, UGW, UGW-Eipx, and UGWipx incorporate a
Media Gateway (MG) module daughter board. In the Coral IPx Office, a CUGW
is used and it includes MRC media card.
The media modules provide media channels that convert PCM calls to IP packets.
Consequently, media channels are needed when
• one of the call parties is not an IP host
• for IP calls between different IP zones
• when using Coral features that rely on PCM based information (such as 3-way
conferences and Silent Monitor).
• Media channels are not necessary for pure peer-to-peer IP calls.
The PUGW, UGW-E, UGW, PUGWipx, UGW-Eipx, and UGWipx card can be
installed in any Coral peripheral slot or shared service slot. Since it requires no
input or output cables (i.e. no MDF connections), the manufacturer recommends
installing it in a service slot. RJ-45 connectors enable LAN/Ethernet connections
UGW (Universal Gate Way) UGWC or IP,0 [9,0]

via the front panel of the card or the rear panel of the IPx 800/3000 cages. See the
relevant Coral Installation Manual to determine the RJ-45 connector locations for
the various cards.
In the Coral IPx Office, the CUGW is imbedded on Shelf #6, Slot 5.
The PI allows configuring the “UGW” card parameters whether a card is currently
physically installed or not yet installed:
• To define UGW parameters before physically installing a UGW card, enter the
UGW: Default Configuration (page 29-9) branch [UGWC, 0]. The parameter
definitions in this branch will apply to all UGW cards installed in the future.
• After a UGW card is physically installed or defined in Hardware Configuration -
Card List on page 6-76, its parameter definitions must be changed in order to
customize the individual card. These changes are made in the UGW: Current
Configuration (page 29-13)branch [UGWC, 1].
29-7
• The PUGW / PUGWipx provides full support and services offered on the
enterprise network for up to 240 Media Channels and IP ports in any physical
location. The Coral system can accept as many PUGW cards as required (up to
60) and provides full support and services for up to 1950 IP ports in a single
system, including:
• IP stations, such as P-Series, T200 series, T300 series, FlexSet-IP 280S,
FlexIP SoftPhone, SeaBeam softphone software, Third-party SIP phones
• Coral SIP and NET_IP trunks
• External telephony gateways for analog SLTs and Loop-Start/Ground-Start
trunks
The maximum number (1950) of IP ports does not include Media Channels and
is also subject to change depending on the combination of peripheral cards
installed. The available number of IP ports and Media Channels in a Coral
system is subject to SAU authorization.
UGW (Universal Gate Way) UGWC or IP,0 [9,0]
29-8
UGW: Default Configuration ç UGWC,0 or IP,0,0 [9,0,0]

with the ability to connect to the IP World. Except for the description of the
physical layout of the different cards, the term “UGW” refers to the entire family
of UGW cards.
This branches used to display or modify the default configuration for the UGW and
media modules.
The Default Configuration for the UGW card database includes factory-set illegal
addresses for the signalling IP Address, Media Gateway (MG) MAC and Media
Gateway (MG). The technician/IP Manager should define a default address for
each of these items in the relevant parameter definition.
The parameter definitions given in this branch (default definitions) will be given to
any UGW card and media module that will be installed in the future.
For cards already installed or defined in Hardware Configuration - Card List on page
6-76, the configuration can be modified in the next branch: UGW: Current
Configuration beginning on page 29-13. To initialize the card, the
technician/installer must update the parameters in the Current Configuration
branch immediately upon installation. The technician/installer should obtain the IP
addresses from the Data Network Administrator or IT Manager on the installation
premises. The MAC number is displayed on a sticker on the module.
UGW: Default Configuration UGWC,0 or IP,0,0 [9,0,0]
29-9
SIGNALLING:
SUBNET_MASK (#/R) Range: Any valid IP address or R (Remove for Blank)
[0] See the IT Manager for legal IP Address
Default: 255.255.255.255
Defines the default Subnet Mask address for all UGW cards in this Coral system.
DEFAULT_ROUTER_ Range: Any valid IP address or R (Remove for Blank)

ADDRESS (#/R) [1] See the IT Manager for legal IP Address
Default: ---.---.---.---
Defines the default router address for all UGW cards in this Coral system.
MEDIA:
SUBNET_MASK(#/R) Range: Any valid IP address or R (Remove for Blank)
[2] See the IT Manager for legal IP Address
Default: 255.255.255.255
Defines the default Subnet Mask address for all media modules in this Coral
system.
?DEFAULT_ROUTER_ Range: Any valid IP address or R (Remove for Blank)

ADDRESS(#/R) [3] See the IT Manager for legal IP Address
Default: ---.---.---.---
Defines the default router address for all media modules in this Coral system.
29-10
CAPACITY:  The total capacity (maximum 240 ports) includes a combination of

MEDIA_CHANNELS [4], KEYSET [5], SLT [6], LGS [7], NET [8] and SIP [9]
resources allocated.
MEDIA_CHANNELS 0..30..24011
[4] see IP_MEDIA_CHANNELS (page 4-28) for maximum size
Defines the default number of the media channels provided for MG modules.
Media channels are needed when one of the calling parties is not an IP host or for
IP calls between different IP zones. Media channels are needed to convert
PCM calls to IP packets. Therefore, all Coral call features based on PCM (such as
IP to IP Zone paging, 3-way conferences and Silent Monitoring) also require the
use of the media channels.
IP Calls with a non-matching CODECs are also routed using the Media channel.
Only when none of the Media Gateway Compression definitions (see MG_
COMPRESSION_CAPABILITY on page 29-20) match the compressions defined for
the IP stations, then the call cannot be completed.
KEYSET [5] 0..30..2401

Defines the default number of IP Keysets stations (FlexSet-IP 280S) supported by
UGW cards.
SLT [6] 0..2401

Defines the default number of SLT supported by UGW cards. Coral Teleport/FXS
units are used as the interface between the SLTs and the UGW cards.

LGS [7] 0..2401

Defines the default number of LGS trunks supported by UGW cards. Coral
Teleport/FXO units are used as the interface between the LGS trunks and the UGW.
NET [8] 0..2401

Defines the default number of QSIG network trunks supported by UGW. Coral
Teleport/FXO units are used as the interface between the network and the UGW.
SIP [9] 0..2401

Defines the default number of SIP entities (SIP terminal stations and trunks)
supported by PUGW, PUGWipx cards and Coral IPx Office systems.
1. The maximum number of endpoints (i.e. total of all entries under CAPACITY) cannot exceed
240.
29-11
MRC Resource  The following parameters are available only for PUGW/PUGWipx cards and
DB: IPx Office systems and define the MRC resource values.
DTMF GAIN [10] -12dB..0..+12 dB (increments of 0.5dB)

Allows defining receiving value level for the DTMF receiver ports supported by
the MRC.
Defines the receiving level gain of incoming DTMF tones.
MFR GAIN [11] -12dB.. 0..+12 dB (increments of 0.5dB)

Allows defining receiving value level for the MFR receiver ports supported by the
MRC.
Defines the receiving level gain for the MFR ports.
CONF members [12] 1..8..14

1: Strongest Win conference mode (only the loudest speaker is heard)
2..14: Summation conference mode (all participants are heard simultaneously)
 MRC Conference ports are currently unavailable.

Define the maximum number of Meet-Me participants for conferences in
Summation mode, allowing every participant to hear all other speaking
participants.
When the number of conference participants exceeds this maximum, the
conference automatically switches to the Strongest Win mode where only the
loudest speaker in the conference is heard.
Set this parameter to one (1) for conferences requiring the Strongest Win
mode.
CONF switch delay 0..7..255 (1 unit = 10 ms)

[13]
 Notes:
• MRC Conference ports are currently unavailable.
• Relevant only for Strongest Win conference mode (see CONF members
[12], above).
Define the time delay required before switching from summation to strongest win
and vice versa (i.e., before switching from the previous loudest party to the new
loudest party). This time delay allows the MRC to avoid switching speakers
because of sudden spikes heard by the conference circuit.
29-12
UGW: Current Configuration ç UGWC,1 or IP,0,1 [9,0,1]

with the ability to connect to the IP World. Except for the description of the
physical layout of the different cards, the term “UGW” refers to the entire family
of UGW cards.
To initialize the UGW card, the technician/installer must update the following
parameters immediately upon installation. The technician/installer should obtain
the IP addresses from the Data Network Administrator or IT Manager on the
installation premises.
Upon initialization, the system checks its resource store. If the sizes of any port
type (media, IP endpoints) required by the UGW exceeds the maximum defined
system sizes, the card is not registered and the NO RESOURCES message is
displayed in Hardware Configuration - Card List on page 6-76. Alternatively, should
any of the technician defined REQUIRED CAPACITY (page 29-22) parameters
exceed their related PHYSICAL CAPACITY (page 29-21) for the specific card, a
CONFIG_ERR message is displayed in Hardware Configuration - Card List. Table 6-6
on page 6-83 includes a complete list of Hardware Configuration - Card List error
messages for cards that have not initialized properly.
One UGW card can be replaced with another UGW card without regard to the
number of its signaling and media resources. However, if the endpoint
requirements of the previous card exceed the requirements on the new card, the
card will not initialize and a Configuration error in Hardware Configuration - Card List
UGW: Current Configuration UGWC,1 or IP,0,1 [9,0,1]

will result.
When, replacing UGW cards, ensure that if a media module is installed on the
UGW card, the media module MAC number should be updated in this branch in
order for the UGW card to initialize. The media MAC address for the MRC
modules, however, is irrelevant and can be left blank in this branch.
The MRC (Main Resources Card) functions as a daughterboard to the PUGW,
PUGWipx and MCB Office. It integrates media channel gateway, DTMF Receiver
(DTR), and MFC-R2 (MFR) circuits. These circuits are embedded onto DSP units.
29-13

6: Coral IPx Office main unit
2..3: Coral IPx Office expansion cages 500X/800X
0..2: Coral IPx 500, 800
0..2: CDRS 200E
0..15: Coral IPx 3000, 4000


5: Coral IPx Office main unit (Shelf #: 6)
29-14
ZONE_LIST List of Zone numbers entered between parentheses in prioritized order

Default List: (0):
Define a list of IP Zones that this UGW card can service enabling the card to
service more than one network (private/public/LAN/WAN) simultaneously.
Therefore, each IP station serviced by the same UGW in the system can be defined
with a meaningful, yet different, IP Zone number defining each telephone
individually towards its connected network type.
The IP Zones may be dynamically allocated (for IP Keyset stations) when their
REQUIRED_ZONE [3] (page 29-30) definition is set to None (--), in which case, the
IP station inherits the first IP zone that is listed in its Call Agent (UGW) definition,
i.e. this parameter definition.
The Coral connects between different IP Zones by using PCM technology to ensure
IP isolation between Zones.
To add a single number or more, enter: (A, number 1, number 2,...)
To remove a single number or more, enter: (R, number 1, number 2,...)
To replace all numbers, enter: ( )
SIGNALLING: The following note is displayed only for IPx Office systems, indicating that the
UGW address in this parameter may also be used to define the CLA and MAP IP

addresses.
Warning: This is an IPx Office system!
IP Signaling Changes may affect other services hosted on
this card.
LOCAL_IP_ADDRESS Range: Any valid IP Socket address or R (Remove for Blank)

(#/R) See the IT Manager for legal IP Address
Default:---.---.---.---:2427 or ---.---.---.---:2727 (Port address is default value of
CA SIG PORT [5] (page 29-70))
 This parameter must be updated upon UGW card initialization.

Defines a static local IP address for the UGW card signalling. The local address is
used for IP devices located within the system network, i.e. between the Coral and
the Router.
 When no Router/NAT server is used, the Global and Local sockets are
identical.
Enter a valid IP Socket (IP Address and IP Port number).
• The Signalling IP port must be 2427 or 2727.
29-15
• If no IP port number is entered, the system automatically assigns the Port

valued defined in CA SIG PORT [5] (page 29-70) from the IP:General (IP,3)
branch.
• If this parameter is left blank, while the next (Global IP Address) is defined,
the Global IP Address will be deleted by the system.
! Updating this parameter with an IP address already used by the Coral

system (i.e., for an IP station or for another UGW or Media card) results
in any of the following error messages:
Already defined in IP station# wxyz, TRY AGAIN!
Already defined in another card, TRY AGAIN!
Already defined in this card, TRY AGAIN!
Already defined in External GW, TRY AGAIN
! Alternatively,
If the IP address is not entered correctly, the IP stations will not be able
to locate the Coral (UGW).
GLOBAL_IP_ Range: Any valid IP Socket address or R (Remove for Blank)

ADDRESS (#/R) See the IT Manager for legal IP Address
Default:---.---.---.---:----
 When no Router/NAT server is used, the Global and Local sockets are
identical.
Defines the static global IP Socket (IP Address and IP Port) for the UGW card
signalling. The global address is used for remote IP endpoints or nodes.
The Socket address is composed of an IP Address and a Signalling IP port number.
To enter the same address as LOCAL_IP_ADDRESS (#/R) above:
• When this parameter is empty (i.e. not previously defined),
after pressing ENTER for the above parameter (LOCAL_IP_ADDRESS),
this parameter is automatically defined with the Local IP Address from above.
SUBNET_MASK (#/R) Range: Any valid IP address or R (Remove for Blank)

See the IT Manager for legal Address
Default: as defined in SUBNET_MASK (#/R) [0] (page 29-10)
 This parameter must be updated upon UGW card initialization.

Defines the Subnet Mask address for UGW card.
29-16

ADDRESS (#/R) See the IT Manager for legal Address
Default: as defined in DEFAULT_ROUTER_ADDRESS (#/R) [1] (page 29-10)
Defines the Default Router Address for the UGW card.
Echo Cancellation 0 (32 ms);

Period 1 (64 ms);
2 (128 ms)
Define the echo cancellation period required for this
PUGW/CUGW/UGW/UGW-E card.
• Enter 0 to choose an echo cancellation period of 32ms.
Choosing this option reduces the MG endpoint capacity from 24 to 20 channels
or from 48 to 40 channels or from 72 to 60 channels.
Choosing this option reduces the MG endpoint capacity from 24 to 20 channels
 This note is irrelevant for MRC modules.

or from 48 to 40 channels or from 72 to 60 channels.
Defining an echo cancellation period 1&2 of greater than 32 milliseconds

reduces the MG endpoint capacity. MG24/48/72 will provide 20/40/60
channels respectively
Note: Options 1 & 2 will result in reduced capacity of
the MG modules.

MG24/48/72 will provide 20/40/60 channels respectively.
29-17
QoS: Defines whether QoS protocols are used in the IP Layer and Ethernet Layer for this
UGW card signalling.
DiffServ (Y/N) Yes/No

Defines whether this UGW card should use the defined DiffServ protocol for the
IP layer. This protocol is used to improve the Quality of Service given by Routers.
The DiffServ protocol values are defined system wide in QoS: DiffServ
Value: (page 29-71) in the IP General branch.
802.1Q/p (Y/N) Yes/No

Defines whether to use the defined 802.1Q/p protocol for the Ethernet Layer used
by Ethernet switches.
! Caution!
Set this parameter to Yes, only when the UGW signalling is routed by
Ethernet switches programmed to use this protocol.
Otherwise, no voice will be heard during calls using this Card.
The 802.1Q/p protocol values are defined system wide in QoS: 802.1Q/p
MEDIA:
MAC FF:FF:FF:FF:FF:FF or R (Remove for Blank)
For MG modules:
Enter the unique MAC (Media Access Control) number for the MG module fitted
on this UGW/UGW-E card. The MAC number can be found on a sticker on the MG
module.
! If no media card is installed on the UGW/UGW-E, then define this

parameter as blank, otherwise the UGW cannot initialize or is defined as
NO_CARD in Hardware Configuration - Card List.

For MRC modules:
This parameter is irrelevant for the MRC modules.
Any value can be entered in this parameter or the parameter may be left blank. The
entered value is saved in the PI regardless of the true MAC address.
In order to view the true MAC address for any MRC, browse to its PUGW address
via any Internet Browser. The MRC MAC address can also be found on the inside
of the Coral IPx Office motherboard.
29-18
LOCAL_IP_ Range: Any valid IP Socket or R (Remove for Blank)

ADDRESS(#/R) See the IT Manager for legal IP Address
Default:---.---.---.---:----
Defines the static, local IP socket (IP Address and IP Port) for the media module.
The local IP address is the address of the UGW card when accessed from the LAN.
GLOBAL_IP_ Range: Any valid IP Socket or R (Remove for Blank)

ADDRESS(#/R) See the IT Manager for legal IP Address
Default:---.---.---.---:----
Defines the static, global IP Socket (IP Address and IP Port) for the media module.
The global IP address is the address of the UGW card when accessed from the other
side of the NAT (the outside world).
SUBNET_MASK(#/R) Range: Any valid IP address or R (Remove for Blank)

See the IT Manager for legal Address
Default: as defined in Signalling: SUBNET_MASK(#/R) [2] (page 29-10)
Defines the Subnet Mask address for the media module.

ADDRESS(#/R) See the IT Manager for legal Address
Default: as defined in ?DEFAULT_ROUTER_ADDRESS(#/R) [3] (page 29-10) in
the UGW: Default Configuration branch
Defines the Default Router Address for the media module.

QoS: Defines whether QoS protocols are used in the IP Layer and Ethernet Layer for this
media module.
DiffServ(Y/N)  Yes/No (Display Only)

Displays whether this media module uses the defined DiffServ protocol for the IP
Layer. This protocol is used to improve the Quality of Service given by Routers.
The DiffServ protocol values are defined system wide in QoS: DiffServ
802.1Q/p(Y/N)  Yes/No (Display Only)

Displays whether this media module uses the 802.1Q/p protocol for the Ethernet
Layer, to ensure the Quality of Service given by Routers.
The 802.1Q/p protocol values are defined system wide in QoS: 802.1Q/p
29-19
Security Type:
DES  Yes/No (Display Only)
Displays whether this media module uses DES encryption for secured IP calls.
Pure IP calls between IP keysets encrypt the voice data in each packet using the
highest encryption supported by both IP keysets, as long as SECURED CALLS
[104] (page 7-31) is defined as Yes in the COS branch for at least one of the keysets.
Triple DES  Yes/No (Display Only)

Displays whether this media module uses triple DES encryption for secured IP
calls.
highest encryption supported by both IP keysets, as long as SECURED CALLS
MG_COMPRESSION_ Display Only of available codes

CAPABILITY
0=G.711 with 10ms; 7=G.729 with 40ms;
2=G.711 with 40ms; 9=G.723 with 60ms;
4=G.729 with 10ms; 11=G.711 with 80ms
5=G.729 with 20ms; 12=G.723 with 90ms;
6=G.729 with 30ms; 13=G.729 with 80ms;
 This parameter is not displayed when no physical UGW card is installed.

Defines the Compression Capabilities available with this media module.

29-20
PHYSICAL The following parameters are displayed only when a physical (UGW) card is
CAPACITY installed (i.e. not in 0/0 systems). The Physical Capacity displays the actual
maximum values for this card.
MEDIA_CHANNELS  (Display Only)

For MG Modules: UNKNOWN
For MRC Modules: MRC-XX (XX=8/16/32/64)
Displays the maximum number of media channels that can be supported by this
MRC module, based on the card hardware (regardless of what is defined in Sizes
Tab).
RESOURCES_TYPES  (Display Only) DTMF/Caller ID/3 Way/CONF/MFC

 This parameter is only relevant for MRC modules.
Only DTMF and MFC are available in the current version.
Displays a list of all the type of system resources supported by this MRC.
MAX_G711_MEDIA_  Display Only of Maximum number of media channels available

CHANNELS
 This parameter is only relevant for MRC modules.
Displays the maximum number of media channels that are available when using
G.711 protocol, when this card is used only for media channels.
When other media protocols are used, or if MRC resources are used, then this
number of media channels cannot be achieved.

TOTAL END POINTS  (Display Only)
Displays the maximum number of IP endpoints, which is a combination of IP
terminals and MRC media channels that can be supported by this card, based on
the card hardware (regardless of what is defined in Sizes).
The UGW card (or IPx Office main unit) is capable of supporting 240 endpoints
minus the number of MEDIA_CHANNELS (page 29-22) supported by the UGW.
Therefore, if the UGW is installed with a media module that supports 64 media
channels, there are 176 = ( 240 - 64) endpoints available for the other IP terminals
(MGCP stations, SIP terminals, SIP trunks, softphones, WiFi-enabled computers
handsets, etc.).
END POINT TYPES  (Display Only of relevant types: Keyset, SLT, LGS, NET, SIP, Media)
Displays a list of the IP endpoint types supported by this UGW card.
• t least one of the endpoints types in one of the system’s UGWs must be defined as
NET (page 29-25) to use IP Network dial numbers.
• A Trunk Group with IP_NET members must have the same IP Zone number defined for the
trunk, as in the UGWs.
29-21
REQUIRED This subsection defines the required capacity of Media Channels and of IP
CAPACITY terminals (keysets, SLTs, LGSs, SIPs or NETs). These capacities are limited by the
card’s physical capacity TOTAL END POINTS (page 29-21). When initializing the UGW
card, a **Configuration Error** is listed in Hardware Configuration - Card List and
no card update is performed, if any of the following situations occur:
• The REQUIRED CAPACITY: MEDIA_CHANNELS (page 29-22) exceeds its
Physical Capacity.
• The total number of endpoint types (IP Keysets, IP SLTS, IP LGS, IP NETs
and/or SIPs) defined in the Required Capacity subsection exceeds the number
of endpoint types supported by the card’s Physical Capacity.
• One of the endpoint types is not supported by this UGW, but its Required
Capacity exceeds 0.
• No media module is physically installed on the UGW, but the REQUIRED
CAPACITY: MEDIA_CHANNELS (page 29-22) exceeds 0.
Attempting to update an active UGW with more IP endpoints or media channels
than the card can physically support immediately results in the
UGW SIZE EXCEEDED error message disabling the technician from updating the
card in excess of its physical capacities and avoiding a configuration error.
The following parameters are also limited by their Sizes defined in Sizes Definition
and Sizes Tab. Attempting to enter a value greater than what is defined in Sizes,
immediately results in the SIZES EXCEEDED, TRY AGAIN message for that
parameter. Additionally, all these parameters must be authorized (and quantified)
in Feature Authorization (see Feature Authorization beginning on page 3-5).
MEDIA_CHANNELS 0..30..Max defined in IP_MEDIA_CHANNELS (page 4-28), in Sizes Tab)

The default for this parameter is set in MEDIA_CHANNELS [4] (page 29-11) in
the UGW: Default Configuration branch
Enter the maximum number of media channels that this media module can support
based on the media module type.
 A Configuration Error is received when the value for this parameter

exceeds the actual number of channels that the media module can support.
Media channels are needed when one of the calling parties is not an IP host or for
IP calls between different IP zones. Media channels are also needed to convert
PCM calls to IP packets, all Coral call features based on PCM (such as IP to IP
Zone paging, 3-way conferences and Silent Monitoring) also require the use of the
media channels.
No media channels are needed for pure peer-to-peer IP calls.
IP Calls with a non-matching CODECs are also routed using the Media channel.
Only when none of the Media Gateway Compression definitions (see MG_
COMPRESSION_CAPABILITY above) match the compressions defined for the IP
stations, then the call cannot be completed.
29-22
Defining a number larger than the defined value in the SIZ branch results in the
following error message:
Size Exceeded, try again.
Either increase the number in the Sizes Tab [Sysgen, 2] or decrease the required
number of media channels in this parameter.
Reserving MRC resources for IP Terminals

The TOTAL END POINTS capacity (maximum 240 endpoints (see page 29-21))
includes a combination of MEDIA_CHANNELS, KEYSETs, SLTs, LGSs, NETs, and
SIPs resources allocated.
Table 29-1 gives examples of how the number of IP terminals that can be
defined varies with the number of media channels programmed under
REQUIRED CAPACITY: MEDIA_CHANNELS for an MRC-16 card.
• Example-1: Media Channels Defined to Full Physical Capacity
• Example-2: Media Channels Defined to Half Physical Capacity
• Example-3: No Media Channels Defined
Table 29-1: Examples: MRC-16 - Media Channels
Required Capacity Parameter
Value
Name Example 1 Example 2 Example 3
MEDIA_CHANNELS 64 32 0
KEYSET 60 60 92

SLT 10 10 10
LGS 10 10 10
NET 60 60 60
SIP 36 68 68
Total IP Terminals 176 208 240
Total Endpoints 240 240 240
Reserving MRC resources for DTR and MFC receivers

The MRC provides media channel gateway, DTMF Receiver (DTR), and MFC-R2
(MFR) circuits. The actual number of DTR and MFC receivers supported by the
MRC varies.
To reserve MRC resources for DTR and MFC receivers, define the REQUIRED
CAPACITY: MEDIA_CHANNELS parameter to a value that is less than the physical
capacity of the card.
The number of resources reserved is equal to the difference between the physical
capacity of the card and the required capacity. Table 29-2 provides two examples
29-23
of defining the REQUIRED CAPACITY: MEDIA_CHANNELS parameter for an

MRC-16 card:
• Example 1 - Media channels defined reach the maximum card capacity. If all
media channels are simultaneously used, the MRC cannot support DTR or
MFC services.
• Example 2 - Media channels defined reach half the card capacity. If all media
channels are used, the card will still be able to support DTR and MFC services.
Table 29-2: Examples - Media Channel Definition
Media Channels
Min. Available
Example Defined
Physical DTR/MFC
Required Max. In use
Capacity
Capacity
1 64 64 64 0
2 64 32 32 32
KEYSET 0..30..Maximum defined in KEYSETS_IP (page 4-7), in SIZ)

The default for this parameter is set in KEYSET [5] (page 29-11) from the
UGW Default Configuration branch
Enter the maximum number of IP Keysets that this UGW is required to support.
Either increase the number in SIZ or decrease the required number of IP Keysets
in this parameter.
SLT 0..maximum defined in SLT_IP (page 4-5), in SIZ)

The default for this parameter is set in SLT [6] (page 29-11) from the UGW
Default Configuration branch
Defines the number of SLTs that are required to be supported by this UGW. Coral
Teleport/FXS units are used as the interface between the SLTs and the UGW cards.
Either increase the number in SIZ or decrease the required number of IP SLTs in
this parameter.
29-24
LGS 0..maximum defined in LGS_IP (page 4-10), in SIZ)

The default for this parameter is set in LGS [7] (page 29-11) from the UGW
Defines the number of LGS trunks that are required to be supported by this UGW.
Coral Teleport/FXO units are used as the interface between the LGS trunks and the
UGW cards.
Either increase the number in SIZ or decrease the required number of IP LGS
trunks in this parameter.
NET 0..maximum defined in NET_IP (page 4-11), in SIZ)

The default for this parameter is set in NET [8] (page 29-11) from the UGW
Defines the number of IP_NET (also known as NET_IP) ports that are required to
be supported by this UGW.
This NET port does not possess a UGW shelf/slot/circuit address but is a logical
circuit given IP_NET [45] (page 5-48) NPL type dial numbers and indexes.
The IP_NET dial numbers must be defined as members in a QSIG Trunk Group.
 When UGW IP_NET ports are defined, increase the number of ISDN_
TRANSIT_ SETUPS (page 4-26) in the Sizes Tab branch.
 In IP_Net systems, all UGW cards must be upgraded to the latest software

version, otherwise there might be compatibility problems in the IP_Net
network. See UGW Software Upgrade: Activate on page 29-94.
Either increase the number in SIZ or decrease the required number of IP NET
trunks in this parameter.
29-25
SIP 0..combined maximum defined for SIP_TERMINAL (page 4-8) and SIP_
TRUNK (page 4-11), in SIZ)
The default for this parameter is set in SIP [9] (page 29-11) from the UGW
Enter the maximum number of SIP entities that this UGW (PUGW, PUGWipx
cards and Coral IPx Office systems) is required to support. Both SIP Terminals as
well as SIP Trunks are supported by this parameter.
Either increase the number in SIZ or decrease the required number in this
parameter.
UPDATE? Yes/No (Yes or No must be entered)

Entering Yes loads the modified card information and resets the UGW card.
! WARNING:
Updating any parameter in this branch causes the UGW card to reset:
• All calls using media channels are dropped.
• All IP_NET (also known as NET_IP) calls are dropped.
• One or more of the IP endpoints (IP Keyset, IP SLT, IP LGS or
IP Net) may re-initialize on another UGW card with the same
zone.
Additionally, all Coral Teleport (FXS/FXO) calls are dropped if any

IP_SLT/IP_LGS ports re-initialize on another UGW.
Enter N to ignore all changes and return the card to previously assigned values.
 After updating the card, check the card in Hardware Configuration - Card List
to ensure that it has initialized properly and reports ACTIVE. Otherwise,
revert to the technical suggestions in Table 6-6 on page 6-83.
29-26
IP Ports ç IP,1 [9,1]
This branch is used to identify the various Coral IP ports (FlexSet-IP 280S, T207M,
T208M, T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL, P-Seies
(such as: P-335, P-450), T322, T328, IP SLTs, IP LGS, SIP Terminals and Trunks).
A range of dial numbers for each type of IP station port must first be defined in the
NPL. The available NPL types for IP stations are IP_KEYSET [41], IP_SLT [42], IP_
LGS [43], SIP_TERMINAL [46], SIP_TRUNK [47] (see page 5-46). The IP Zone
Number and MAC numbers are defined in the respective IP Port branches for these
stations.
IP_Keyset .......................................................................................... 29-28
IP_SLT............................................................................................... 29-36
IP_LGS.............................................................................................. 29-38
IP_Net................................................................................................ 29-40
IP Ports IP,1 [9,1]
29-27
IP_Keyset ç IPKEY or IP,1,0 [9,1,0]
This branch defines and displays information pertaining to all the IP Keyset
stations in the Coral that are defined as IP_KEYSET [41] (page 5-46) in the NPL.
These may include IP Keysets such as the T207M, T208M, T207M/NP, T208M/BL,
FlexSet-IP 280S, FlexIP SoftPhone (FLIPS), SeaBeam softphone or a Sentinel
unit. The requested range of IP Keysets may be displayed or updated as needed.
 The Music feature cannot be defined for idle FlexSet-IP 280S units.
In order to identify IP Stations in the Coral, the unique MAC associated with the
IP Keyset/Sentinel unit must be entered in this branch, per station (i.e. for each IP
Keyset). A Sentinel box including two units must be registered as two separate
units in the PI with two unique MAC addresses.
 Sentinel I and II are defined in this branch.

However, Sentinel Pro units are defined in their own branch, see IP:
SENTINEL Pro beginning on page 29-89.
The IP station sends its IP address periodically to the Coral, therefore, this address
is for display only in this branch.
The IP Keyset port parameters may be updated either by accessing their index
numbers (Route: IP,1,0,0), see 0-Index Access below, or their dial numbers (Route:
IP,1,0,1), see 1-Dial Number Access below. Each IP keyset is assigned a unique NPL
index number and dial number in the General Numbering Plan. Once the range of
requested ports is entered, the parameters are displayed after the dial number and
index number of each port.
IP_Keyset IPKEY or IP,1,0 [9,1,0]
29-28
Choose
Access:
Index or Dial
0-Index Access Access the IP Keyset port definitions by entering their NPL Index numbers
FROM/TO INDEX# Any range of valid IP Keyset index numbers

Enter the range of IP Keyset index numbers from the lowest number to the highest
index number.
 IP Port: Keyset parameters will now be listed by their index number for
each index number requested.
DIAL_NUMBER [0]  Any valid IP Keyset dial number (Display Only)

Displays the dial number associated with this index number for the IP Keyset.
The next parameter displayed is REQUIRED_ZONE [3] (page 29-30).
1-Dial Number Access the IP Keyset port definitions by entering their NPL dial numbers.
Access
FROM/TO DIAL# Any valid system IP Keyset dial number;

Default: All IP Keyset dial numbers
Enter the required range of IP Keyset dial numbers FROM the lowest dial number,
 IP Port: Keyset parameters will now be listed by their dial numbers for
each dial number requested.

INDEX [0]  Any valid NPL IP Keyset index number (Display Only)
Displays the index number associated with the displayed IP Keyset dial number.
The next parameter displayed is REQUIRED_ZONE [3] (page 29-30).
29-29
Parameters  NOTE! The remaining parameters in this branch are presented regardless of
which method (index or dial numbers) was requested to access the IP Port
Keyset branch.
TYPE [1]  Display Only (see Table 29-3)

Displays the Phone type associated with this index/dial number for IP (MGCP)
Keysets.:
Table 29-3: IP MGCP Keyset Type Messages
TYPE Models
FLEXSET IP FlexSet-IP 280S (5 soft keys)
FLIPS FlexIP SoftPhone that displays on a PC
T207M T207M or T207M/NP (MGCP, 3-line display and 4 soft keys)
T208M T208M or T208M/BL (MGCP, 6-line display and 4 soft keys)
CURRENT_ZONE [2]  (Display Only)

Displays the Current Zone assigned to this IP Keyset station.
REQUIRED_ZONE [3] 0..Max defined in SIZ for ZONE (page 4-19)/--/R (R: Remove for None --)
Define the required IP Zone for this IP Keyset station.
To enable the UGW to automatically and dynamically allocate an IP Zone to the
station, define this parameter as None: “--” (use R to remove assigned Zone). When
the station automatically initializes from the UGW, the first IP Zone number in the
ZONE_LIST (page 29-15) is allocated to the station.
 For FlexIP SoftPhones that move between different geographic locations,

define this parameter as None (--) for dynamic IP Zone allocation.

The FlexIP SoftPhone user must define all the Network Call Agents (UGWs) IP
addresses so that it may connect to any one from within the LAN or externally. The
Call Agent then automatically assigns an IP Zone to the station.
29-30
MAC [4] FF:FF:FF:FF:FF:FF or R (Remove for None)
 Changing this parameter causes the next field to automatically reset.

Enter the unique MAC number for this IP Keyset to register this keyset in the
Coral. An IP keyset that does not have a registered MAC number is inoperable.
The MAC (Media Access Control) number can be found on the back of the IP
Keyset or viewed on the keyset display when entering the correct menu, see the
relevant telephone User Guide for exact instructions.
 NOTE: MAC numbers can be automatically registered (useful when defining

a large amount of stations at one time, such as during an installation
procedure), see IP KEYSET AUTOMATIC REGISTRATION [1] (page 29-68) in the
IP-General branch.
IP_ADDRESS [5]  Display Only

Displays the IP address defined for this IP Keyset station. The Coral receives the
IP address directly from the IP Keyset. The IP address can only be changed via
MENU on the IP Keyset.
An IP address of 0.0.0.0 indicates that this IP Keyset has not been initialized or that
no IP Keyset is connected.
CONNECTED_VIA_  Yes/No (Display Only)

SENTINEL [6]
Displays whether the unit is connected to the Coral via a Sentinel unit.
Since the Sentinel unit may contain a global IP address, IP keysets located in
remote zones may initialize via a Sentinel unit.

EARLY_MEDIA_FOR_  Yes/No (Display Only)

BANDWIDTH_
Bandwidth defined within zones is designed to limit the number of calls to IP
CONTROL [7]
keysets per zone. It is possible to configure each IP keyset to accept or reject a call
depending on whether there is enough bandwidth in the zone to support an
additional call to the IP Keyset.
When set to N (No), any call made to an IP phone within a zone will ring even if
there is insufficient bandwidth available in the zone to support the call. In this
instance, the call will be terminated as soon as it is answered if bandwidth is not
freed between the ring and the answer.
When this parameter is set to Y (yes), any call made to an IP phone within a zone
will not ring when there is insufficient bandwidth available in the zone to support
the call.
29-31
STATUS [8]  Display Only (see Table 29-4)

Displays the IP Keyset’s current status:
:
Table 29-4: IP Keyset Status Messages
Status Description
Message
Active The Port is Active
Wrong Entity This IP Keyset is trying to initialize on an IP port already

defined as a Sentinel unit.
IP Contention This IP Address is already being used for another IP keyset.
Not Compat An incompatible IP Keyset Version is being used. FlexSet-IP

280S requires phone Version 3.xx or higher.
The FlexIP Softphone (FLIPS) requires phone Version 3.xx or
higher.
Wrong Zone This IP Keyset is trying to register via a call agent that does
not support its REQUIRED_ZONE definition.
Unauthorized The Authorization limit for IP Keysets has been exceeded.
No Resources No IP Keyset resources are currently available in this IP

zone.
If REQUIRED_ZONE is not defined in this branch, then this
status message indicates that there are no IP Keyset
resources system-wide.
IP Keyset resources are defined in the UGW Current
Configuration branch (IP,0,1) in KEYSET (page 29-24).
_____ Undefined port

29-32
QoS:
DiffServ [9] Yes/No
Defines whether this Keyset uses the defined DiffServ protocol for the IP layer.
This protocol is used to improve the Quality of Service given by the Routers.
The DiffServ protocol values are defined, system wide, in QoS: DiffServ
802.1Q/p [10] Yes/No

Defines whether to use the defined 802.1Q/p protocol for the Ethernet Layer used
by the Ethernet switches.
! Set this parameter to Yes, only when the Keyset signalling is routed by
Ethernet switches programmed to use this protocol.
Otherwise, voice will not be heard on this keyset.
The 802.1Q/p protocol values are defined, system wide, in QoS: 802.1Q/p
Security Type:
DES [11]  Yes/No (Display Only)
Displays whether this IP Keyset uses DES encryption for secured IP calls.
highest encryption supported by both IP keysets, when SECURED CALLS
Triple DES [12]  Yes/No (Display Only)

Displays whether this IP Keyset uses triple DES encryption for secured IP calls.
highest encryption supported by both IP keysets, when SECURED CALLS
AES [13]  Yes/No (Display Only)

 Relevant only for calls between T207M, T208M, T207M/NP, T208M/BL
phones.
Displays whether this IP Keyset uses encryption for secured IP calls.
Pure IP calls between IP keysets encrypt the voice data in each packet using
encryption supported by both IP keysets, when SECURED CALLS [104] (page 7-31)
is defined as Yes in the COS branch for at least one of the keysets.
29-33
COMPRESSION_  Display Only of available codes

CAPABILITY [14] 0=G.711 with 10ms; 7=G.729 with 40ms;
2=G.711 with 40ms; 9=G.723 with 60ms;
4=G.729 with 10ms; 11=G.711 with 80ms
5=G.729 with 20ms; 12=G.723 with 90ms;
6=G.729 with 30ms; 13=G.729 with 80ms;

G.723 defines compression ratio between 5 and 6 (Not Available)
VAD makes use of silence to gain even better call compression (Not Available)
 No value for this parameter is displayed if the IP Keyset is not installed.

Displays the call compression values available for calls to/from this IP Keyset.
When a call is established, the system checks which compression capabilities are
available based on its COS definition and the COS definition of the second party
and uses the highest priority compression defined for the call originator.
Both sides must have at least one matching compression definition in their COS
definition in order to speak to each other (assuming these compression capabilities
are physically supported by the endpoints as well). Otherwise, the call is rerouted
via the media module in order to match the compression capabilities via the
compression capabilities of the media module. If no match is found at this point,
then the call cannot be completed.
See USER_COMPRESSION_LIST [105] (page 7-31) in COS Station Definitions for
defining COS endpoint compression capabilities.

If one of the calling sides is not an IP endpoint, then that party assumes the
compressions available for the UGW card (based on the media module installed on
the UGW) handling the call.
When there are no compression matches in both party’s COSs, then the call is
denied and the message CODEC MISMATCH appears on the keyset display.
The keyset COS is defined in PRM_COS [0] on page 9-32.
PHONE_TIME_ZONE_ Yes/No
OVERRIDE_BY_
Enter Yes to enable the system to override the time zone definition set on the IP
SYSTEM [15]
Keyset with the time zone defined in the DELTA_TIME_FROM_GMT [16] parameter.
29-34
GMT [16] None
Defines the time zone of the IP station by defining a time offset (in hours and
minutes) from GMT time.
• Minute values are entered in increments of 15 minute (00, 15, 30, 45).
This parameter is relevant only if PHONE_TIME_ZONE_OVERRIDE_BY_SYSTEM
[15] is set to Yes. Otherwise when it is set to No, the time displayed in this
parameter is for display only and cannot be changed.
Special Case 1:
If the PHONE_TIME_ZONE_OVERRIDE_BY_SYSTEM [15] parameter is set to N, and
no value was entered for this parameter, this indicates that this IP station’s phone
never sent a request for a time zone offset. Therefore, the technician may manually
enter a time zone offset for the phone from this parameter.
In the future, if the phone sends a request for a time zone offset, this parameter will
automatically be updated with the phone’s request.
Special Case 2:
If the PHONE_TIME_ZONE_OVERRIDE_BY_SYSTEM [15] parameter is set to Y, but
no value has been entered for this parameter (i.e. R for Remove or blank), the IP
station phone is granted the time zone offset defined in the Time Set DELTA_TIME_
FROM_GMT on page 25-3.
Los New Madrid London Berlin Tel

Angeles York (GMT) Aviv

Delta Time from GMT -8:00 -5:00 -1:00 0 +1:00 +2:00
(Local Offset to GMT)
Displayed Local Time 02:00 05:00 09:00 10:00 11:00 12:00
Example:
If a IP station is located in New York, it is in a time zone that is 5 hours west of
GMT time, defined as “-5” (time difference in hours compared to GMT). If it is
05:00 o'clock in New York it is 10:00 o'clock in GMT “at the same moment”.
Define this parameter as -5:00, after defining the PHONE_TIME_ZONE_OVERRIDE_
BY_SYSTEM [15] parameter to N.
Keyset features such as the Idle Display Clock, Wake-up, Reminder, and Call Log
features are automatically adjusted to follow the localized time definitions.
29-35
IP_SLT ç IP,1,1 [9,1,1]
This branch is used to display all the information pertaining to all the Coral IP SLT
stations. The IP SLT stations are interfaced with the UGW cards by Coral
Teleport/FXS units. The units and their relevant names and numbers and other
details are only displayed in this branch. Assign the Teleport names, units and entry
numbers to these ports in IP: Telephony Gateway (Coral Teleport) beginning on
page 29-62.
• The requested range of IP SLT stations may be displayed or updated as needed.
• IP SLT stations must already be allocated in the NPL to activate this branch.
FROM/TO DIAL# Any valid system IP_SLT [42] (page 5-46) NPL dial number, All
Enter the required range of IP SLT dial numbers FROM the lowest dial number, TO
the highest dial number.
ZONE [0]  (Display Only)

Displays the IP Zone number for the interfacing IP SLT Coral Teleport (FXS) unit.
MAC [1]  (Display Only)

Displays the MAC (Media Access Control) number for the interfacing IP SLT
Coral Teleport (FXS) unit.
IP_ADDRESS [2]  (Display Only)

Displays the IP address for the interfacing IP SLT Coral Teleport (FXS) unit.

SENTINEL [3]
IP_SLT IP,1,1 [9,1,1]
Since the Sentinel unit may contain a global IP address, IP SLTs located in remote
zones may initialize via a Sentinel unit.
COMPRESSION_  (Display Only of available codes)

CAPABILITY [4]
Displays the available codes for the compression capability with this IP SLT Coral
Teleport (FXS) unit.
29-36
EXTERNAL_ The following parameters are for display only. They can be updated in the IP:
GATEWAY Telephony Gateway (Coral Teleport) (page 29-62) branch for the required IP SLT dial
number.
NAME [5]  Teleport Name (Display Only)

Displays the name for the interfacing IP SLT Coral Teleport (FXS) unit for this dial
number.
NUMBER [6]  Teleport Entry # (Display Only)

Displays the Entry number defined in IP: Telephony Gateway (Coral Teleport) for the
interfacing IP SLT Coral Teleport (FXS) unit.
END_POINT_NUMBER  Teleport Circuit (Entry) # (Display Only)

[7]
Displays the Coral Teleport (FXS) unit circuit number assigned for this dial
number. The port name is defined in SLT_INFO by Entry#: (page 29-67) in the IP:
Telephony Gateway (Coral Teleport) (IP,2) branch.
IP_SLT IP,1,1 [9,1,1]
29-37
IP_LGS ç IP,1,2 [9,1,2]
This branch is used to display all the information pertaining to all the Coral IP LGS
trunk stations. These trunks are interfaced with the UGW cards by Coral
Teleport/FXO units. The units and their relevant names and numbers are only
displayed in this branch. Assign the Teleport names, units and entry numbers to the
IP trunk stations in IP: Telephony Gateway (Coral Teleport) beginning on page
29-62.
• The requested range of IP LGS stations may be displayed or updated as needed.
• IP LGS stations must already be allocated in the NPL to activate this branch.
FROM/TO DIAL# Any valid system IP_LGS [43] (page 5-47) NPL dial number, All
Enter the required range of IP LGS dial numbers FROM the lowest dial number,
ZONE [0]  (Display Only)

Displays the IP Zone for the interfacing IP LGS Coral Teleport (FXO) unit.
MAC [1]  (Display Only)

Displays the MAC (Media Access Control) number for the interfacing IP LGS
Coral Teleport (FXO) unit.
IP_ADDRESS [2]  (Display Only)

Displays the IP address for the interfacing IP LGS Coral Teleport (FXO) unit.

SENTINEL [3]
IP_LGS IP,1,2 [9,1,2]
Since the Sentinel unit may contain a global IP address, IP LGSs located in remote
zones may initialize via a Sentinel unit.
COMPRESSION_  (Display Only of available codes)

CAPABILITY [4]
Displays the available codes for the compression capability with this IP LGS Coral
Teleport (FXO) unit.
29-38
EXTERNAL_ The following parameters are for display only. They can be updated in the IP:
GATEWAY Telephony Gateway (Coral Teleport) (page 29-62) branch for the required IP LGS
dial number.
NAME [5]  Teleport Name (Display Only)

Displays the name for the interfacing IP LGS Coral Teleport (FXO) unit for this
dial number.
NUMBER [6]  Teleport Entry # (Display Only)

Displays the defined Entry number for the dial number’s interfacing IP LGS Coral
Teleport (FXO) unit as defined in IP: Telephony Gateway (Coral Teleport).
END_POINT_NUMBER  Teleport Port # (Display Only)

[7]
Displays the Coral Teleport (FXO) unit circuit number assigned for this dial
number. The port is name is defined in LGS_INFO by Entry#: (page 29-67).
IP_LGS IP,1,2 [9,1,2]
29-39
IP_Net ç IP,1,3 [9,1,3]
This branch is used only to view the IP Network port details: the supporting UGW
IP address, its defined IP Zone and the dial number status.
 In IP_NET systems (also known as NET_IP systems), all UGW cards must
be upgraded to the latest software version, otherwise there might be
compatibility problems in the IP_Net network. See UGW Software Upgrade:
Activate on page 29-94.
.
FROM/TO DIAL# Any valid system IP_NET [45] (page 5-48) NPL dial number, All
Enter the requested IP Net trunk dial numbers from the lowest to the highest.
ZONE  (Display Only)

Displays the IP Zone assigned to this dial number.
The IP Zone is defined in the Trunk Definition Branch (TGDEF), see IP_
ZONE (page 8-19).
UGW_ADDRESS  A system UGW address

Displays the UGW physical address (Shelf/Slot) from which this dial number is
currently being served.
STATUS  Display Only

ACTIVE/No Resources/Unauthorized/Wrong_Zone/---
Displays the IP Network port’s current status:
Status Message Description

IP_Net IP,1,3 [9,1,3]
Active The Port is Active (a card has initialized on this port).
No Resources No IP NET resources are currently available (IP NET

resources are defined in NET (page 29-25), UGW Current
Configuration branch (IP, 0, 1)).
Unauthorized The Authorization limit for IP Networks has been

exceeded.
Wrong Zone No IP Zone group was defined in the Trunk Group

Definition branch for this dial number.
--- This dial number has not been defined in any Trunk
Group Definition.
29-40
SIP Ports
General
The Coral System (Main Software Version 15 or higher) is capable of processing
SIP requests and communication such that it may integrate standard off-the-shelf
third-party SIP phones and trunks. The PUGW, PUGWipx cards and Coral IPx
Office systems are used to support SIP protocol in the Coral.
The SIP phones are intelligent IP phones that include telephony features within the
phone and can communicate via the public internet (RTP and SIP signalling are
established) without the use of a Coral. However, when certain features are
required or when a telephony numbering plan is required, the Coral can act as a SIP
Proxy server to dispense these intelligences and “run the show”.
SIP Terminal ..................................................................................... 29-43
SIP Trunk .......................................................................................... 29-52
Third-party SIP terminals

These SIP phones require Coral main software version 15 or higher.
T207S, T208S, T207S/NP, T208S/BL
These SIP phones require Coral main software version 15.5 or higher.
T322, T328
These SIP phones require Coral main software version 16 or higher.
P-Seies (such as: P-335, P-450)
These SIP phones require Coral main software version 16.01.12 or higher.
SeaBeam Softphone
These SIP PC-phones require Coral main software version 15.84 or higher.
Coral SIP Implementation
SIP Ports IP,1,3 [9,1,3]

The Coral architecture is based on a Master/Slave application. The most similar
SIP architecture to a Master/Slave type application is the SIP B2BUA setup (see
SIP Glossary, below), where the Coral acts as SIP Registrar, Proxy, Redirect and
Location Server for all its SIP endpoints.
SIP Glossary
Register: SIP entities may register with their Servers. In Coral systems, the SIP
entities are required to register with their servers where the PUGW is the server. A
SIP entity (phone terminal or trunk line) registering with its server is analogous to
a Coral telephone or trunk initializing opposite its line or trunk card.
FQDN: Fully Qualified Domain Name. Domain name used by DNS server to
allocate IP Address on a per need basis.
User Agent (UA): A SIP endpoint, such as a SIP telephone, a PC, PDAs, a video
system, etc. using SIP protocol.
29-41
When trying to establish communication between two User Agents, there is a

client/server relationship such that the call initiator is designated as the UA client
and the call destination is the UA Server in which case the Coral serves as a
back-to-back User Agent (B2BUA).
Back-to-Back User Agent (B2BUA): a combination of SIP servers in one. It can
act as a client or a server as well as reconstruct communications requests. In most
cases the B2BUA serves as a Gateway to the regular telephony world. It may
change the communication messages to match Coral telephony messages or
otherwise.
SIP Registrar Server: A SIP database Server that includes all the legal SIP
addresses in the system. This server includes all the UA names included on the
Server’s domain.
SIP Proxy Server: receives the call setup requests from the UAs and queries the
registrar for the destination addresses. Once the destination details are received, the
Proxy sends the communication request directly to the UA if it resides on the same
domain.
If the destination does not reside in the same domain, the request for the destination
details is sent to a SIP Redirect Server to be redirected to another domain.
SIP Redirect Server: used to create routes to find destinations outside of the
Registrar’s domain. This server usually resides in the Proxy Server and operates
only when a negative response is received by the Registrar server.
SIP Trunk: Out trunk lines defined with trunk channels that run on SIP protocol,
similar to the virtual IP Network trunks.
SIP Address: based on URI scheme, similar to email address
(username@hostname) with the addition of a SIP: prefix. The host name may be
an explicit IP address.
SIP addresses are used in the From/To fields of the SIP protocol. These addresses
SIP Ports IP,1,3 [9,1,3]
are used by the Coral and assigned Coral dialing plan numbers in the IP Ports
SIP Terminal beginning on page 29-43 (IP, 1, 4) or SIP Trunk beginning on page
29-52 (IP, 1, 5) branch.
Here are some examples of SIP addresses:
sip: 5989@www.example.com
sip: 5930@192.10.10.1
29-42
SIP Terminal ç IP,1,4 [9,1,4]
SIP Terminals/phones; P-Seies (such as: P-335, P-450), T200S series (T207S,
T208S, T207S/NP, T208S/BL), T300 series (T322, T328), SeaBeam, SeaMail
voice and MWI ports, LxCMC voice and MWI ports, and all third-party SIP
phones; are intelligent endpoints which include support for telephony features
located within the phone itself. Since the Coral also offers telephony features,
feature control can sometimes be jeopardized. Certain Coral features are supported
by SIP while others are currently not supported by the SIP endpoints. See the
relevant terminal User’s Guide for a complete list, see also the New Developments
Summary, Version 15 for a complete list.
The SIP terminal features are defined in the Coral in the Keyset definition branch,
see Keyset Definition beginning on page 9-31.
This branch is used to Register the SIP terminal phone in the Coral system,
i.e. define its required IP Zone, Password, MAC and IP Addresses as well as other
pertinent IP information.
The SIP Terminal port parameters may be updated either by accessing their:
Index numbers (Route: IP,1,0,0), see 0-Index Access below, or their
Dial numbers (Route: IP,1,0,1), see 1-Dial Number Access below.
Each SIP Terminal is assigned a unique NPL index number and dial number in the
General Numbering Plan as SIP_TERMINAL [46] (page 5-48) types. Once the range
of requested ports is entered, the parameters are displayed after the dial number and
index number of each port.
SIP Terminal IP,1,4 [9,1,4]
29-43
Choose
Access:
Index or Dial
0-Index Access Access the SIP Terminal definitions by entering their NPL Index numbers
FROM/TO INDEX# Any range of valid SIP Terminal index numbers

Enter the range of SIP Terminal index numbers from the lowest number to the
highest index number.
 SIP Terminal parameters will now be listed by their index number for each
index number requested.
DIAL_NUMBER [0]  Any valid SIP Terminal dial number (Display Only)
Displays the dial number associated with this index number.The next parameter
displayed is CURRENT_ZONE [1] (page 29-45).
1-Dial Number Access the SIP Terminal definitions by entering their NPL dial numbers.
Access
FROM/TO DIAL# Any valid system SIP Terminal dial number;

Default: All SIP Terminal dial numbers
Enter the required range of SIP Terminal dial numbers FROM the lowest dial
number, TO the highest dial number.
 SIP Terminal parameters will now be listed by their dial numbers for each
dial number requested.
 Any valid NPL SIP Terminal index number (Display Only)

INDEX [0]
Displays the index number associated with the displayed dial number.
The next parameter displayed is CURRENT_ZONE [1] (page 29-45).
29-44
Parameters  NOTE!
The remaining parameters in this branch are presented regardless of which
method (index or dial numbers) was requested to access the SIP Terminal
branch.
CURRENT_ZONE [1]  Display Only

Displays the IP Zone currently assigned to the selected SIP Terminal.
Define the required IP Zone for this SIP Terminal.
For Dynamic Zone Allocation, i.e., to have the system automatically assign a Zone
for this entity, define this parameter as None: “--” (use R to remove assigned Zone).
The SIP terminal initializes on one of the PUGWs in the Coral and is assigned the
first zone listed in the PUGW’s Zone_List (see UGW: Current Configuration
AUTHENTICATION_ Yes/No
REQUIRED [4]
Defines whether or not there is support of SIP terminal without Authentication.
• Yes - authorization is required
or higher)
• No - the system does not ask for authentication and phone is registered
PASSWORD [5] R (remove),

characters case sensitive:

The maximum number of characters allowed for the password is defined by
MAXIMUM_PERSONAL_PASSWORD_LENGTH (page 4-19) in the Sizes Definition
branch.
'SIP Terminal Authentication - define a personal password for the SIP terminal to
be used in the Authentication process.
 If the password for the SIP endpoint is manually changed in the SIP
phone, it is not automatically updated in this parameter. The password
definition must be changed here as well. Otherwise, the SIP endpoint is
inoperable.
When no password is defined here, the system uses the password defined in the IP
General branch: AUTHENTICATION PASSWORD [14] (page 29-74).
29-45
Media Negotiation [6] Early/Late

Define the type of media negotiation to be used with this SIP endpoint, Early or
Late.
SIP phones incorporate their own individual media CODECs, such that the Coral
cannot know in advance which CODEC can be matched in order to setup the call.
The Coral supports both Early and Late Media setup.
• Early Media Negotiation:2
The Coral sends a list of the available CODECs during the call setup process
to the destination. A CODEC match (between the initiator and destination
sides) must be achieved, otherwise the call fails.
All SIP entities can handle the Early Media Negotiation, but it requires
immediately allocating a media resource, whereas if the CODECs of both sides
match, a media resource would not be needed. Therefore, it is only used for
phones that cannot handle the Late Media Negotiation.
Also, SIP stations defined with an Early Media setup cannot be defined with
Multi-Appearance or be members of a Boss Group.
• Late Media Negotiation:
The Coral first sets-up the call. When the call is answered the destination SIP
entity sends the CODEC list in order to try and find a CODEC match with the
call initiator3.
If the CODECs match, a peer-to-peer call is established, saving media
resources. If the CODECs do not match, the call must established via the
 When Announcer is set to Y (Yes), this parameter must be set to Early.

Media Gateway.
 Stations defined with an Early Media Negotiation cannot be:

• members in a Boss Group (the phones will not ring)
• defined as Multi-Appearance. Alternatively, stations defined with
Multi-Appearance cannot be defined with an Early Media setup.
Attempting either definition results in an error message and the update

cannot be accepted.
HOLD Support [7] Early/Late

Define the Hold support to be used with this SIP Terminal.
Terminals can be tested for this default, by trying to place the phone in a Hold state
while this parameter is defined by its default. If the Hold state cannot be achieved,
change this parameter definition to Early.
2.Early Media Negotiation: INVITE (SDP list of Codecs sent from Coral), OK (SDP se-
lected), ACK (empty)
3.Delayed Media Negotiation: INVITE (empty, no list of Codecs sent), OK (SDP list sent
from SIP entity), ACK (SDP selected)
29-46
TRANSFER METHOD Refer/re-Invite

[8]
When a Coral station tries to transfer a SIP terminal, the matching definition is
checked and the transfer proceeds accordingly. If the transfer is performed via
re-INVITE, and user B or user C are SIP stations, the transfer data will not appear
on the display panels.
PROGRESS_183 [9]
When set to Y (Yes) for a Coral SIP terminal, Coral relays the session progress
response from a remote device to that terminal. If the Coral SIP terminal does not
support the session progress response, set this parameter to N (No).
XFER_ON_RING_ Yes/No
WITHOUT_REPLACES
The Coral database can be configured to remove the REPLACES header field from
[10] the INVITE request of calls transferred to SIP endpoints that do not support this

header. This means that Coral can support call transfers to SIP endpoints that do
not recognize the REPLACES header.
When set to Y (Yes), the REPLACES header is removed from the INVITE request
before it is transferred to a SIP terminal that does not support the REPLACES
header. This parameter is applied to the terminal receiving the INVITE request.
29-47
NOTIFY_OF_XFER_ Yes/No
ALLOWED_AFTER_
Definse whether the SIP terminal supports notifications after BYE.

BYE [11]
(Coral version 16.01.16 When a SIP terminal ‘A’ transfers a call (i.e. transferring ‘B’ to ‘C’,
or higher) single step transfer, transfer on ring or after answer) it expects
notifications on the status of the call ‘B-C’. The Coral disconnects the call
‘A-B’ using BYE message and then it sends NOTIFY messages using the
dialog of that call.
• Yes - (Default) The Coral will disconnect the transferrer SIP terminal (‘A’) and
then send notifications of the status of the new call between the remaining
parties (‘B-C’).
• No - The Coral will immediately send a NOTIFY message with value 200=OK
on the existing call and then the Coral will disconnect the transferrer SIP
terminal (‘A’) using BYE.
The 200 OK is sent even if the transferred call was not answered yet.
HEADER_URI_TYPE
[12] When a call is forwarded to a SIP terminal, a diversion header can be sent. This
means that if party A calls party B and is forwarded to the SIP Voicemail of party
B, party A reaches the Voicemail of party B.
This parameter defines whether or not diversion headers are sent to SIP terminals.
When Sip or Tel is defined, diversion headers are sent to SIP terminals. When No
is selected, diversion headers are not sent to SIP terminals.

N_BLF_BUTTONS [13] 0..144

Defines the number of available DSS (Direct Station Selection) buttons used in this
or higher) phone for BLF (Busy Line Field) feature.
This parameter influences the total number defined in Sizes Tab definitions NO_OF_
SIP_SUBSCRIPTIONS parameter on page 4-31.
 Applicable for P-Seies (such as: P-335, P-450), T207S, T208S, T207S/NP,
T208S/BL, T322, T328 phones and any third-party SIP terminal with
SIP-Subscribe option.
29-48
BLF_REPORTS_ 0..3
TABLE [14]
Defines the conversion index used to convert the LED indications defined by Coral
(Coral version 16.01 into the same indications displayed by specific SIP terminal equipment.
or higher)
For terminal equipment other than the P-Seies (such as: P-335, P-450), T322,
T328, contact the manufacturer.
 This parameter is not relevant for T207S, T208S, T207S/NP, T208S/BL

phones.
SUPPORT_RING_ Yes/No..
TYPE [15]
Defines whether or not to send Ring Type to SIP terminal in Invite message.

or higher) The message format is: Alert-Info: <URL>;info= info text
Where info text is Internal or External or VoicePage.
• Yes - Coral will send Alert-Info (ring type, such as: Internal, External or
VoicePage).
• No - No Alert-Info is supported
ADD_VM_IND_TO_ Yes/No
MSG_LAMP [16]
This parameter is relevant for third-party SIP terminals (such as Polycom
phones) that require special treatment for simple MWI (Message Waiting
or higher)
Indicator) on/off instructions.In order to turn on/off the MWI lamp for
simple message waitng, these phones require that the Coral send a
Voicemail indication as well.
Defines whether or not to include Voicemail Indication (VM_IND) message to SIP

terminal with the MWI lamp message.
• Yes - Coral will send VM_IND for simple messages (required for P-Series).
• No - No VM_IND is sent (relevant for P-Series, T200S and T300 series)
IP_ADDRESS [17]  ---.---.---.---:---- (Display Only)

Displays the IP address given for the SIP Terminal or Trunk.
 The IP address is displayed only when the port is Active.

The SIP terminal is either manually configured with an IP address by the technician
or receives the IP address during the registration process from the DHCP.
The technician uses this parameter to view the SIP terminal’s IP address via the PI
(i.e. not at the SIP phone, which may not be available).
29-49
USER_AGENT [18]  (Display Only)

It displays the first 60 characters of phone manufacturer and version information.
Displays the SIP Terminal Manufacturer name, phone type and phone version as
reported in the Registration request. Therefore, if the phone is not registered, then
this information is not displayed.
For Example
USER_AGENT Message Displayed
for models
T207 VENG-0.9.35 T207S and

T207S/NP
T207+TEM VENG-0.9.35 T207S and

T207S/NP
with TEM
expansion
T208 VENG-0.9.35 T208S and

T208S/BL
T208+TEM VENG-0.9.35 T208S and

T208S/BL
with TEM
expansion
Tadiran SIP-T322P 7.50.19.3 00:15:65:11:d0:19 T322 *
Tadiran SIP-T328P 2.50.19.3 00:15:65:12:07:33 T328

with/without
X338
expansions
Manufacturer, Phone type, Soft Ver, Serial # or Mac Address P-Series
PolycomSoundPointIP-SPIP_335-UA/3.3.1.0769_000a6b0202e2 P-335
* Where 00:15:65:12:07:33 and 00:15:65:11:d0:19 are MAC addresses of the phones
29-50

Displays the SIP Terminal port’s current status:
Table 29-6: SIP Terminal Status Messages
ACTIVE The Port is Active (a SIP terminal is registered on this

port).
Missing_Pass The SIP terminal requires a password defined in this

branch as well as the identical password defined within the
SIP terminal’s internal definitions (via the HTTP port or
directly from within the phone).
Missing_Pass indicates that the SIP terminal is missing its
internal SIP terminal password definition
Wrong_Pass The SIP terminal requires a password defined in this
SIP terminal’s internal definitions (via the HTTP port or
directly from within the phone).
Wrong_Pass indicates that these passwords do not match.
Brief_KA_Time The Keep Alive timer defined for this SIP terminal is shorter
than the one defined in the IP:General (IP,3) branch. This
SIP terminal KA timer must be extended to any number
greater than the Coral’s KA in order for the SIP terminal to
register.
Wrong_Zone This SIP terminal is trying to register via a call agent that
does not support its REQUIRED_ZONE [2] (page 29-45)
definition.
Unauthorized The Authorization limit for SIP terminals has been

exceeded.
No Resources No SIP resources are currently available in this IP zone. If

REQUIRED_ZONE [2] (page 29-45) is not defined, then this
message means there are no SIP resources system-wide.
SIP resources are defined in the UGW: Current
Configuration branch.
___ This dial number has not been defined in any SIP Terminal
Definition.
29-51
SIP Trunk ç IP,1,5 [9,1,5]
A SIP trunk is a service offered by an ITSP (Internet Telephony Service Provider)

to use SIP to set up communications between an enterprise Coral system and the
ITSP. On the Internet, the ITSP provides connectivity to the PSTN (Public
Switched Telephone Network) for communication with mobile and fixed phones.
Since the voice traffic is now routed through the Internet connection to the ITSP,
no local connection to the PSTN is necessary at the Coral system. The gateways
needed to connect to the PSTN will reside in the ITSP’s premises.
The SIP trunk allows customers to be connected directly to their ITSP through pure
IP connection. QoS is maintained (in compliance with the Service Level
Agreement) on one hand, and cost can be reduced on the other hand.
The SIP trunks can be either registered or unregistered in any one of the following
manners:
SIP trunk Description
Registration
Registered Dedicated trunks per SIP entity. These trunks remain in idle
state after they initialized and are registered. A keep alive
signal continues to be sent from the trunk at pre-defined
intervals ensuring the trunk’s idle state.
Examples of registered SIP Trunks may include External
Gateways, FXO Teleport units MP-10x and MP-11x (x=4/8).
This is the most secure type of Coral SIP trunk. However, it
requires dedicated trunk resources which may not always be
in use. Therefore, when a large number of trunks must be
defined, it may be preferable to simply list the trunks within
the Coral via a Dial Service, and use Unregistered SIP
Trunks.
Unregistered A reserved pool of SIP trunks that can be accessed

whenever necessary. A Dial Service includes the destination
SIP Trunk IP,1,5 [9,1,5]
SIP trunk IP address.

The trunks remain in idle state, until they are needed, at
which point the Coral searches for the SIP trunk IP address
in its list of dial services. Once the trunk’s IP address is
found, any free PUGW SIP trunk channel can be used.
Examples of unregistered SIP trunks may include Service
Providers over IP (SIP), SIP Gateways, or a SIP trunk
between two Corals.
Guest Any SIP trunks that are not dedicated or listed within the
Coral.
The Guest trunks can be used only for incoming calls.
Examples of Guest SIP Trunks may include soft phones and
unregistered SIP terminals.
29-52
SIP Trunks Definition Procedure:

1. Define Sizes for the SIP Trunks in SIP_TRUNK (page 4-11) in Sizes.
2. Define the quantity for SIP in the PUGW card in the UGW: Current
Configuration (UGWC) branch, see SIP (page 29-26).
3. Define the SIP Trunk parameters in this branch with the INCOMING_
REGISTRATION [11] (page 29-60) parameter set to: :
SIP trunk Set to:
Registration
Registered Yes
Unregistered No
Guest No
4. Define the SIP trunks in a Trunk Group via the Trunk Group Definition
branch. The Trunk Group must hold the following settings:
• IP_ZONE (page 8-19): use the same definition as defined for REQUIRED_
ZONE [2] (page 29-56) in this SIP_Trunk branch.
• QSIG (page 8-19): must be set to Yes
• DIALING METHOD (page 8-25): must be set to Enblock
• add only SIP trunks as the trunk group members.
5. Complete the Registration process as follows: :

SIP trunk Description
Registration
Registered • Define the endpoint (i.e. FXO teleport unit) with the IP
Port 5060.
• The trunk should be in Idle state (1H) after successful
registration to Coral.
Unregistered • Define the SIP gateway address in the IP Address line

of the dial service:
• In the LCR branch, define a Dial Service with the Trunk
Group and IP Address of the other side. If the other side
has more than one IP Address, then create a separate
Dial Service for each PUGW card.
• On the other side, define a Dial Service for each PUGW
with SIP Trunks in your side.
• The trunk should be in Idle state (1H) after successful
PUGW registration and SIP allocation.
Guest These require defining a SIP_GUEST_TRUNK_GROUP (V.

15.85.37 or higher) DEFAULT_TRUNK_GROUP
(V. 15.85.16 or lower) (page 29-86) in the IP: Zones branch for
each IP Zone with a SIP Trunk. However, they also require the
use of a free SIP Trunk channel from the PUGW to be used as
the guest SIP Trunk.
29-53
:This branch is used to register as well as to define and/or view the Coral SIP
trunks.
Only trunks that are to be dedicated SIP trunks (i.e. Registered) require a password
definition (if the password is not defined in this branch, a default is assigned from
the IP-General branch).
Virtual-Unregistered or Guest SIP trunks must also be defined in this branch, but
with the INCOMING_REGISTRATION [11] (page 29-60) parameter set to No.
• No IP Address is displayed for the Virtual-Unregistered or Guest SIP trunks.
! Be careful when assigning the Dial Numbers to the SIP entities!

If the SIP entity was mistakenly given a non SIP entity NPL dial number,
the given dial number will not be shown in this branch.
The SIP Trunk port parameters may be updated either by accessing their index
numbers (Route: IP,1,0,0), see 0-Index Access below, or their dial numbers (Route:
IP,1,0,1), see 1-Dial Number Access below. Each SIP Trunk is assigned a unique
NPL index number and dial number in the General Numbering Plan as a SIP_
TRUNK [47] (page 5-49) NPL type. Once the range of requested ports is entered, the
parameters are displayed after the dial number and index number of each port.
29-54
Choose
Access:
Index or Dial
0-Index Access Access the SIP trunk definitions by entering their NPL Index numbers
FROM/TO INDEX# Any range of valid SIP trunk index numbers

Enter the range of SIP trunk index numbers from the lowest number to the highest
index number.
 SIP Trunk parameters will now be listed by their index number for each
index number requested.
DIAL_NUMBER [0]  Any valid SIP trunk dial number (Display Only)
Displays the dial number associated with this index number.
1-Dial Number Access the SIP trunk definitions by entering their NPL dial numbers.
Access
FROM/TO DIAL# Any valid system SIP trunk dial number;

Default: All SIP trunk dial numbers
Enter the required range of SIP trunk dial numbers FROM the lowest dial number,
 SIP Trunk parameters will now be listed by their dial numbers for each
dial number requested.
INDEX [0]  Any valid NPL SIP trunk index number (Display Only)

Displays the index number associated with the displayed dial number.
29-55
Parameters  NOTE!
The remaining parameters in this branch are presented regardless of which
method (index or dial numbers) was requested to access the SIP trunk branch.
CURRENT_ZONE [1]  Display Only

Displays the IP Zone currently assigned to the selected SIP trunk.
Define the required IP Zone for this SIP trunk.
For Dynamic Zone Allocation, i.e., to have the system automatically assign a Zone
for this entity, define this parameter as None: “--” (use R to remove assigned Zone).
The SIP trunk initializes on one of the PUGWs in the Coral and is assigned the first
zone listed in the PUGW’s Zone_List (see UGW:Current Configuration branch).
Define the required IP Zone for this SIP Terminal.
PASSWORD [4] R (remove), maximum 20* characters, case sensitive:

• The maximum number of characters allowed for the password defined by
MAXIMUM_PERSONAL_PASSWORD_LENGTH (page 4-19) in the Sizes
Definition branch.
 A password is required only for dedicated Registered Trunks.
SIP Trunk Authentication - define a personal password for the SIP trunk to be used
in the Authentication process.
When no password is defined here, the system uses the password defined in the IP
General branch: AUTHENTICATION PASSWORD [14] (page 29-74).
29-56
Media Negotiation [5] Early/Late

Define the type of media negotiation to be used with this SIP endpoint, Early or
Late.
SIP trunks incorporate their own individual media CODECs, such that the Coral
cannot know in advance which CODEC can be matched in order to setup the call.
The Coral supports both Early and Late Media setup.
This parameter, combined with COMPRESSION_CAPABILITY [20] on page 15-17
must be configured to match the CODEC settings of the proxy server. Early defines
media negotiation with SDP. Late defines media negotiation without SDP.
 For SIP trunks, this parameter must be defined as Early.

• Early Media Negotiation4: The Coral sends a list of the available CODECs
during the call setup process to the destination. A CODEC match (between the
initiator and destination sides) must be achieved, otherwise the call fails.
All SIP entities can handle the Early Media Negotiation, but it requires
immediately allocating a media resource, whereas if the CODECs of both sides
match, a media resource would not be needed. Therefore, it is only used for
trunks that cannot handle the Late Media Negotiation.
• Late Media Negotiation: The Coral first sets-up the call. When the call is
answered, the destination SIP entity sends the CODEC list in order to try and
find a CODEC match with the call initiator5.
If the CODECs match, a peer-to-peer call is established, saving media resources. If
the CODECs do not match, the call must established via the Media Gateway.
HOLD Support [6] Early/Late

Define the Hold support to be used with this SIP phone. The definition of this
parameter must be identical to the Media Negotiation [6] definition.
Trunks can be tested, by trying to place the trunk in a Hold state while this

parameter is defined by its default. If the Hold state cannot be achieved, change this
parameter definition to Early.
4.Early Media Negotiation: INVITE (SDP list of Codecs sent from Coral), OK (SDP se-
lected), ACK (empty)
5.Delayed Media Negotiation: INVITE (empty, no list of Codecs sent), OK (SDP list sent
from SIP entity), ACK (SDP selected)
29-57
TRANSFER METHOD Refer/re-Invite

[7]
When a Coral station tries to transfer a SIP trunk, the matching definition is
checked and the transfer proceeds accordingly. For unregistered trunks, the Dial
Service definition always overrides the port definition. If the transfer is performed
via re-INVITE, and user B or user C are SIP stations, the transfer data will not
appear on the display panels.
The REFER message does not work with SIP trunks. For SIP trunks, re-INVITE
must be defined.
PROGRESS_183 [8]
When set to Y (Yes) for a Coral SIP trunk, Coral relays the session progress
response from a remote device to that trunk. If the Coral SIP trunk does not support
the session progress response, set this parameter to N (No). If this parameter is
defined differently under DIAL SERVICES and SIP TRUNK, the definition under
DIAL SERVICES overrides the definition under SIP TRUNK for that trunk.
XFER_ON_RING_ Yes/No
WITHOUT_REPLACES
The Coral database can be configured to remove the REPLACES header field from
[9] the INVITE request of calls transferred to SIP endpoints that do not support this
header. This means that Coral can support call transfers to SIP endpoints that do
not recognize the REPLACES header.
Set to Y (Yes), to support transfer on ring to SIP trunk between two Coral systems.
When set to Y (Yes), the REPLACES header is removed from the INVITE request
before it is transferred to a SIP trunk that does not support the REPLACES header.
This parameter is applied to the trunk receiving the INVITE request.
29-58
HEADER_URI_TYPE
[10] When a call is forwarded to a SIP trunk, a diversion header can be sent. This means
that if party A calls party B and is forwarded to the SIP Voicemail of party B, party
A reaches the Voicemail of party B.
This parameter defines whether or not diversion headers are sent to SIP trunks.
When Sip or Tel is defined, diversion headers are sent to SIP trunks. When No is
selected, diversion headers are not sent to SIP trunks.
The definition for a given trunk under Dial Services: DIVERSION_HEADER_URI_
TYPE [30] on page 15-20 overrides the definition under SIP TRUNK.
INTERNAL_HOLD [10] Yes/No

Enables Music on Hold (MOH) to be heard by another party by using SENDRCV
instead of SENDONLY. When this parameter is set to Y (Yes), MOH is sent via
SENDRCV. When this parameter is set to N (No), MOH is sent via SENDONLY.
This parameter also appears under the Dial Services branch. See “Dial Services”
on page 11. The parameter definition under Dial Services overrides the parameter
definition under SIP Trunks.
29-59
INCOMING_ Yes/No
REGISTRATION [11]
This INCOMING_REGISTRATION [11] parameter is relevant for incoming calls only.
Enter Yes to define this SIP trunk as a dedicated SIP trunk in the Coral, i.e. when
defining Registered (page 29-52) SIP trunks.
Updating this branch registers the trunk opposite its endpoint. After the trunk is
registered, it remains in idle.
Enter No to list this trunk with the Coral and use it only on a per-need basis, for
Unregistered (page 29-52) and Guest (page 29-52) SIP trunks.
IP_ADDRESS [12]  ---.---.---.---:---- (Display Only)

This IP_ADDRESS [12] parameter is relevant only when INCOMING_REGISTRATION
[11] parameter is set to Yes.
Displays the IP socket given for the SIP trunk. The SIP trunk is either manually
configured with an IP address by the technician or receives the IP address during
the registration process from the DHCP.
The technician uses this parameter to view the SIP trunk’s IP address via the PI (i.e.
not at the SIP phone, which may not be available).
 The IP address is displayed only when the port is Active.

USER_AGENT [13]  (Display Only)

This USER_AGENT [13] parameter is relevant only when INCOMING_
REGISTRATION [11] parameter is set to Yes.
Displays first 60 characters of phone manufacturer and version information
Displays the SIP Trunk Manufacturer name, phone type and phone version as
reported in the Registration request. Therefore, if the trunk is not registered, then
this information does not display.
29-60

Displays the SIP trunk port’s current status:
Table 29-7: SIP Trunk Status Messages
ACTIVE The Port is Active (a SIP trunk is registered on this port).
UNREG_TRUNK Unregistered Trunk. This SIP trunk is internally defined to

be registered with the Coral, but incorrectly defined with its
INCOMING_REGISTRATION [11] (page 29-54) parameter
set to No. Change this parameter definition to Yes to
register the SIP trunk.
Missing_Pass The SIP trunk requires a password defined herein this

SIP trunk’s internal definitions (via the HTTP port or directly
from within the trunk).
Missing_Pass indicates that the SIP trunk is missing its
internal SIP trunk password definition.
Wrong_Pass The SIP trunk requires a password defined herein this

SIP trunk’s internal definitions (via the HTTP port or directly
from within the phone).
Wrong_Pass indicates that these passwords do not match.
Brief_KA_Time The Keep Alive timer defined for this SIP trunk is shorter
than the one defined in the IP:General (IP,3) branch. This
SIP trunk KA timer must be extended to any number
greater than the Coral’s KA in order for the SIP trunk to
register.
Wrong_Zone This SIP trunk is trying to register via a call agent that does
not support its REQUIRED_ZONE definition.
UNAUTHORIZED The Authorization limit for SIP trunks has been exceeded.

NO RESOURCES No SIP resources are currently available in this IP zone. If
REQUIRED_ZONE is not defined, then this message
means there are no SIP resources system-wide. SIP
resources are defined in the UGW: Current Configuration
branch.
 If the SIP entity was mistakenly given a non SIP entity NPL dial number,
the given dial number will not be shown in this branch.
29-61
IP: Telephony Gateway (Coral Teleport) ç IP,2 [9,2]
This branch is used to configure and display the Coral Teleport FXO and FXS VoIP
gateway units used to interface SLTs and LGS trunks via the UGW card with the
IP network.
These stand-alone, analog, VoIP Gateway subsystems provide superior voice
technology enabling Single Line Telephones (SLT) and loop start analog trunks to
connect to the Coral system via the UGW card through the IP world. The Coral
Teleport is available in Foreign eXchange Office (FXO) and Foreign eXchange
Station (FXS) versions each with a different number of ports.
The FXS units interface SLTs, while the FXO units interface LGSs with the UGW
card creating an extensive VoIP Coral PABX.
FROM/TO ENTRY# 0..Max defined in Sizes for EXTERNAL_GW (page 4-19)

Each FXO or FXS unit is given a unique Entry # to individually mark the unit
within the Coral. Enter the range of Entry numbers to be configured or displayed.
Define a descriptive name for the external gateway (up to 16 alphanumeric
characters) for this Entry.
A name defined as BLANK displays only the Entry number. Use “_” (underscore)
TYPE [1] 0: MP102/ MP112/ FXS (supports 2 IP SLT ports)

IP: Telephony Gateway (Coral Teleport) IP,2 [9,2]
2: MP104/ MP114/ FXS (supports 4 IP SLT ports)

3: MP104/ MP114/ FXO (supports 4 IP LGS ports)
4: MP108/ MP118/ FXS (supports 8 IP SLT ports)
5: MP108/ MP118/ FXO (supports 8 IP LGS ports)
6: MP124/FXS (supports 24 IP SLT ports)
R: for Remove or None
Choose the type of external gateway unit required by entering its representative
digit, i.e. enter 2 to define this Entry # as an MP104-S/FXS unit.
The system does not internally check the connected unit, therefore:
• If an 8 port unit is requested but only 4 ports were required, 4 ports are wasted
and cannot be used.
• Alternatively, should 8 ports be required, but a 4 port unit was chosen, then
only 4 ports are available on this Entry #.
When changing this parameter value, the following message is displayed:
**WARNING: All ports will be removed.**
ARE YOU SURE (Y/N)?
29-62
The previous MAC and IP address, and port details (SLT info and LGS info) are
deleted when TYPE is changed.
Enter Yes to continue or No to retract.
 When the TYPE [1] parameter is set to None, it is defined as “--” and the
following parameters in this branch are not displayed.
ZONE [2] 0..max defined in ZONE (page 4-19) - Sizes Def.

Enter the IP Zone for this IP SLT or LGS to be initiated upon by assigning it to a
UGW with the same Zone.
Different groups are defined in order to enable separating the LANs as well as to
enable routing all external signalling to a specific and predefined UGW that can
traverse a known firewall.
The IP gateways can only be initiated on a UGW assigned with the same IP Zone.
MAC [3] FF:FF:FF:FF:FF:FF or R (Remove for Blank)
 Changing this parameter causes the next field to automatically reset.

Enter the unique MAC (Media Access Control) number for this Teleport unit to
register the unit in the Coral.
! Carefully enter the MAC number correctly!

An incorrect MAC number will not be detected by the system and this
Teleport unit will not be identified in the system and is inoperable.

GLOBAL_IP_  Display Only

ADDRESS [4]
Displays the global IP address automatically defined for this Teleport unit by the
Coral.

SENTINEL [5]
Since the Sentinel unit may contain a global IP address, IP keysets located in
remote zones may initialize via a Sentinel unit.
29-63
ACTIVATE_RSIP [6] Yes/No (Note: RSIP stands for ReStart In Progress)

{V16.02 or higher}
Defines the UGW Redundancy mode.
Enter Yes for Asymmetric mode and No for Symmetric mode.
IP Telephony Gateways may be defined with IP addresses - One Primary Call
Agent (CA) and optional Secondary Call Agents. Upon initialization, each gateway
attempts to connect to one of the Coral systems according to these gateway
definitions. The gateway first attempts to register via the Primary CA; if there is no
successful response a toggling mechanism is invoked and the gateway attempts to
connect via the Secondary CA. In case of failure the gateway toggles back to the
"primary" and so on.
During normal operation while the gateway is registered at the Primary CA, the
gateway identifies cases where the Primary CA does not respond to signaling
messages. In these scenarios, the gateway registers to the Secondary CA and the
gateway seamlessly continues normal functionality, without the users noticing any
connectivity failure or malfunction with the Primary CA.
The Redundant CA includes two operational modes:

• Yes (Asymmetric mode) the Primary Coral via its UGW is assigned a higher
priority for registration than the Secondary Coral via its UGW. In the
Asymmetric mode, once the gateway is registered to the Primary UGW, its
Coral sends reset messages to the gateway after UGW initialization. (The
gateway might be registered to the secondary UGW in another Coral system.)
If the gateway does not respond, the gateway registers to the secondary UGW.
The primary UGW continues sending reset messages to the gateway for up to
24 hours every few minutes. If the gateway responds to these reset messages,
the gateway reregisters back to the primary UGW. Therefore, the gateway
assigns the primary UGW a higher priority for registration.
• No (Symmetric mode) (Default) both Coral systems are assigned the same
priority for registration. In the Symmetric mode, once the gateway is registered
to a Coral, it sends keep-alive messages to this Coral via its UGW. The gateway
switches UGW cards only once the UGW on the Coral to which it has
registered does not respond. Therefore, the gateway assigns both UGW cards
 Only one of the Coral systems defined as CA for a gateway may be

the same priority for registration.
defined as Activate RSIP = Yes. This Coral via its UGW card is the
Primary CA
29-64
UGW_ADDRESS [7]  Display Only

Displays the physical UGW port address (Shelf/Slot) that this Teleport unit
interfaces.

Displays the Teleport unit status:
Table 29-8: IP Gateway Status Messages
Active The unit is active and functioning properly
------ No unit is defined
Unauthorized There is no software authorization defined for Teleport units

in SLT_IP or LGS_IP of the FEAT,1 branch (SAU).
The IP number reported for this unit is already being used

IP# in Use
for another keyset or unit in the Coral.
No Resources There are not enough Teleport units defined in Sizes to

initiate this unit, see EXTERNAL_GW on page 4-19 in Sizes
Definition.
COMPRESSION_  Display Only of available codes

CAPABILITY [9]
0=G.711 with 10ms; 7=G.729 with 40ms;

2=G.711 with 40ms; 9=G.723 with 60ms;
4=G.729 with 10ms; 11=G.711 with 80ms
5=G.729 with 20ms; 12=G.723 with 90ms;
6=G.729 with 30ms; 13=G.729 with 80ms;
Displays the Compression Capabilities available with this Teleport unit.

29-65
GMT [10] None
Defines the time zone of the FXO/FXS IP endpoint by defining a time offset (in
hours and minutes) from GMT time.
Minute values are entered in increments of 15 minute (00, 15, 30, 45).
 The FXO/FXS IP endpoint cannot define its own time offset or cannot send
•
a request for a time zone offset from GMT.

When no value has been entered for this parameter (i.e. R for Remove or None),
the FXO/FXS IP endpoint is granted the time zone offset defined in the Time Set
DELTA_TIME_FROM_GMT on page 25-3, and the endpoint time is defined as with
the Coral system time.
Los New Madrid London Berlin Tel

Angeles York (GMT) Aviv
Delta Time from GMT -8:00 -5:00 -1:00 0 +1:00 +2:00
(Local Offset to GMT)
Displayed Local Time 02:00 05:00 09:00 10:00 11:00 12:00
Example:
If a FXO/FXS IP endpoint is located in Los Angeles, it is in a time zone that is 8
hours west of GMT time, defined as “-8” (time difference in hours compared to
GMT). If it is 02:00 o'clock in Los Angeles it is 10:00 o'clock in GMT “at the same
moment”. Define this parameter as -8:00.
29-66
SLT_INFO This information is available only for the FXS defined entries (TYPE= 0, 2, 4, 6).
by Entry#: Only the unit Names may be updated in this sub section.
DIAL# [11]  Display Only

Displays the IP_SLT [42] (page 5-46) dial number assigned by the NPL for this
Teleport circuit.
NAME: Short (5) [12] Any ASCII characters: max, 5 characters; R (Remove for BLANK)
Define the short name (up to 5 alphanumeric characters) for this Teleport circuit
dial number. This name is also used in Port List. When no name is defined, the word
BLANK appears as the dial number name.
NAME: Long (16) [13] Any ASCII characters: max, 16 characters; R (Remove for BLANK)
Define the full name (up to 16 alphanumeric characters) for this Teleport circuit
LGS_INFO This information is available only for the FXO defined entries (TYPE= 3, 5). Only
by Entry#: the unit Names may be updated in this sub section.
DIAL# [14]  Display Only

Displays the IP_LGS [43] (page 5-47) dial number assigned by the NPL for this

Teleport circuit.
NAME: Short (5) [15] Any ASCII characters: max, 5 characters; R (Remove for BLANK)
Define the short name (up to 5 alphanumeric characters) for this Teleport circuit
NAME: Long (16) [16] Any ASCII characters: max, 16 characters; R (Remove for BLANK)
Define the full name (up to 16 alphanumeric characters) for this Teleport circuit
29-67
IP: General ç IP,3 [ROOT,9,3]
The following parameters, when defined, are applied for all IP calls and stations
within the Coral system.
IP KEYSET Yes/No
AUTOMATIC
Enter Yes to instruct the system to automatically register the MAC (Media Access
REGISTRATION [1]
Control) numbers for the IP keysets when initializing IP stations.
When IP stations are initialized, the Coral first checks to see whether the keyset is
already registered by matching the broadcast MAC number to the MAC numbers
already registered in the database. If the MAC number is not found, the Coral
automatically registers the MAC number in the database against the first available
IP Station index number. The MAC number/s are registered, even if the IP Address
is already in use (i.e. IP Contention message is received) or insufficient Sizes are
allocated for the keyset/s (i.e., no UGW resources are allocated).
When To Use This Parameter:
This parameter is normally used when first installing a system. When this
parameter is set to Yes, the MAC numbers are automatically registered, however
the dial numbers are randomly assigned to the connected keysets. When installing
a small amount of IP stations, the technician may prefer to use the IP-Stations
branch (see IP_Keyset beginning on page 29-28), to manually assign the MAC
number as well as the station dial number.
To Control the Dial Number Assignment:
The Coral assigns the dial numbers to the IP keysets based on the first available
index number. Define a range of IP keyset index numbers with the required dial
numbers in the Coral Numbering Plan (see IP_KEYSET [41] on page 5-46).
After setting this parameter to Yes:
• Manually connect the IP Keysets to the LAN connection (Internet wall socket).
IP: General IP,3 [ROOT,9,3]
The first keyset connected to the LAN, initializes that keyset with its own
MAC number and the Coral dial number of the first available IP_KEYSET
index number.
• Connect the next keyset to the same LAN connection to define it with the next
available index number and associated dial number and so on.
• The keysets may now be moved to any new destination with a LAN
connection, while retaining their Coral dial number and MAC registration.
Alternatively, connect the IP Keysets in any order and then rearrange the dial
numbers in the Numbering Plan.
! The technician must reset this parameter to No after the keysets are
initialized to prevent unauthorized users from using the system.
This parameter is automatically reset to No at midnight, every evening.
29-68
RTP PORT BASE [2] 2000..16400..65000 in increments of 10
! The UGW cards and IP Keysets MUST be re-initialized manually to

enable the change to this parameter.
• Initialize the UGW card by manually pulling the card out and
then carefully pushing it back into its slot again.
• Alternatively the technician can perform an UPDATE? to the
Current Card Configuration without changing any parameter
definitions (useful for CUGW in the Coral IPx Office).
• Initialize the IP Keysets by disconnecting the LAN cable and
power source and reconnecting them again.
Defines the Real Time Protocol (RTP) port base, system-wide, for all IP voice calls.
 This parameter is also relevant for the iAPA feature and must be defined in
order for the iAPA port to be recognized by the CTI application computer
as an IP socket.
KEEP ALIVE 10..30..60 seconds

INTERVAL [3]
Define a Keep Alive interval for IP stations depending on your server/router
requirements. It must be shorter than the inactivity interval defined in the firewall
A proper Keep Alive interval can prevent closing IP ports between the Sentinel
units and the IP phones.
 This parameter is also relevant the iAPA feature and must be shorter than
the inactivity interval defined for the CTI computer application.
iAPA_TCP_PORT [4] 4450...5059

Defines the output port of the Serial Port to TCP/IP Redirector software.
This port is monitored by the PUGW for TCP/IP transmissions, which are
recognized as iAPA transmissions.
Serial Port to TCP/IP Redirector
A software which simulates an RS-232 serial port (creates a virtual serial port) for CTI computer
applications and redirects (converts the transmission) the data from the virtual serial port to a
designated IP address and vice versa. There are Serial Port to TCP/IP Redirectors that work in
TCP or UDP modes. The iAPA supports only TCP mode.
The Serial Port to TCP/IP Redirector is required to be installed ONLY onto each PC that runs a
legacy CTI application, which communicates through the PC COM port rather than NIC card. New
CTI application solutions developed for TCP/IP communication do not need the Serial Port to
TCP/IP Redirector.
Coral supports several third-party Serial Port to TCP/IP Redirector softwares. Contact the Coral
manufacturer's representative for the approved list of tested software.
29-69
CA SIG PORT [5] 0/1
0: 2427,
1: 2727
Defines the Call Agent (CA) Signalling IP port, system-wide.
 All Coral IP Keysets must have the same Call Agent signalling port
definition as defined in this parameter.
See the relevant keyset Installation Manual for defining CAs in IP Keysets.
! The UGW cards MUST be re-initialized to enable the change to this

parameter.
• Initialize the UGW card by manually pulling the card out and
then carefully pushing it back into its slot again.
• Alternatively the technician can perform an UPDATE? to the
Current Card Configuration without changing any parameter
definitions (useful for CUGW in the Coral IPx Office).
29-70
QoS: DiffServ Define the Quality of Service for the IP Layer analyzed by Routers, for both
Value: signaling and media parameters. These parameters define the Quality of Service
system wide.
SIGNALING: Signaling information in the Voice over IP PABX is less critical than the voice
(media) information and the parameter default values reflect this situation.
However, should signaling information be equally important at any given time,
these parameters may be easily changed to reflect such situations.
Forwarding Class [6] 0,1,2,3,4,5
0: Best Effort
1: AF1 (Assured Forwarding1)
2: AF2
3: AF3
4: AF4
5: EF (Expedited Forwarding)
Define the urgency for sending this signaling packet. 0 (Best Effort) is the least
prioritized option. 5 (EF) is the most prioritized option.
Drop Precedence [7] 0,1,2,3
0: None
1: Low
2: Medium
3: High
Define the importance of this signaling packet information for occasions when the
Router is overloaded and may need to drop packets.
Dropping Priority:

0 (None) indicates that the packet may be dropped first during congestion.
3 (High) indicates that the packet is very important and should be dropped last.
29-71
QoS: DiffServ Cont.

Value:
MEDIA: Define the Voice (media) Quality of Service parameters for IP Layer analyzed by
Routers. These parameters are used to enhance the IP call quality.
Forwarding Class [8] 0,1,2,3,4,5
0: Best Effort
2: AF2
3: AF3
4: AF4
Define the urgency for sending this media packet. 0 (Best Effort) is the least
prioritized option. 5 (EF) is the most prioritized option.
This parameter is defined with the highest priority because it relates to the sending
of voice (media) information (packets), and is used to improve call quality.
Drop Precedence [9] 0,1,2,3
0: None
1: Low
2: Medium
3: High
Define the importance of this media packet information for occasions when the
Router is overloaded and may need to drop packets.
Dropping Priority:
0 (None) indicates that the packet may be dropped first during congestion.
3 (High) indicates that the packet is very important and should be dropped last.
This parameter is defined with the highest priority in order to improve the voice
quality of the call.
29-72
QoS: 802.1Q/p Defines the Quality of Service for the Ethernet Layer used for the Ethernet
Value: Switches that are compatible with the 802.1Q/p protocol.
T207M, T208M, T207M/NP, T208M/BL phones ignore the values set here and
derive TOS values from the DIFFSERV Values as follows:
Diffserv = 0 TOS = 0
802.1Q/p is used for VLAN prioritization, it is layer 2.

TOS is a byte in the IPv4 header, so it is related to layer 3.
 Restart the phone after changing this parameter, otherwise the phone will
not follow the new DiffServ values defined here.
 An Ethernet switch may be capable of recognizing this protocol, but may

not be configured in this manner. See the IT manager.
Signaling Priority [10] 0,1,2,3,4,5

0: (Lowest Priority)
1:
2:
3:
4:
5: (Highest Priority)
Define the layer 2 priority for sending the signaling packets. 0 is least prioritized.
5 is highest priority.
Generally, signaling information is less critical than voice information.

Media Priority [11] 0,1,2,3,4,5

0: Best Effort
2: AF2
3: AF3
4: AF4
Define the layer 2 priority for sending the voice (media) packets. 0 is least
prioritized. 5 is highest priority.
Generally, voice information is most critical, reflected by the parameter default
values.
29-73
SIP:
DISPLAY NICKNAME  Yes/No
INSTEAD D.N. [12]
NOT USED
AUTHENTICATION 30..300..65000 seconds

INTERVAL [13]
Defines the maximum waiting period of the Coral system between an
authentication renewal signal from the SIP endpoint and the next request for
authentication
The authentication interval must be defined as larger than the Coral KEEP ALIVE
INTERVAL [3] (page 29-69) (above) in order for the SIP entities to remain as
registered Coral SIP entities.
AUTHENTICATION Default: 123456

PASSWORD [14] Range: Maximum 20 characters, case sensitive: A-Z, a-z, 0-9,
“*” (asterisk), “&” (ampersand), “+” (plus), “$” (dollar sign), “-” (hyphen), “_
” (underscore), “.” (period), “!” (exclamation point), “~” (tilde), “/” (slash mark).
SIP General Authentication - defines an Authentication password for the Coral
system for SIP endpoints that did not define a password for the SIP Terminal or
Trunk (with INCOMING_REGISTRATION [11] defined Yes) in IP Ports.
BACK_OFF_TIMER 1...5...60 minutes

[15]
Defines the time interval between a failed registration and the next attempt.
SUGGESTED_ 60..600..1200 seconds

EXPIRES_TIME [16]

NOTE: This parameter is relevant only for outgoing registration on SIP
trunk.
Defines the maximum system waiting time for the next Registration event (Keep
alive) on outgoing SIP trunks.
If Keep alive is not recognized, after this time-out period, the following actions
take place:
• The ISP rejects the SIP trunk
• The Coral system releases the SIP trunk to idle state
• STATUS [42] parameter for outgoing SIP trunk (on page 15-23) of the relevant
Dial Service reflects the new status. The status will be changed from Active,
according to the response from the ISP, or will be Blank when no response is
received from the ISP.
29-74
WAIT_FOR_ 4...40 seconds

RESPONSE_ON_
Defines the maximum system waiting time for receiving a response from an
TRUNK [17]
outgoing SIP trunk. The user (caller) will be prompted with Cause# 41 display
message.
The default value is 40 seconds, to prevent call disconnect when working with
DNS.
When LAR is required, reduce the default value.
SESSION_TIMER_ 90...3600 seconds

INTERVAL [18]
Defines the interval between times a SIP session is monitored for activity.
This means that the Coral system performing a routine check of SIP connectivity
has to wait the amount of time as defined here, before re-checking session activity.
RETRIES_NO. [19] 2..7

Defines the number of attempts to initiate a call with one service provider IP
address before moving on to the next IP address. Seven attempts take 40 seconds
to complete. If a DNS is used that includes an external ITSP (Internet Telephony
Service Provider) with several servers, it is recommended to reduce the number of
retries to prevent disconnect due to timeout.
29-75
Warning! Changing any of the following SIP parameters will cause

the PUGW/CUGW to initialize automatically.
Upon changing one or more of the following three SIP parameters:
SELF DOMAIN [20],
PRIMARY_DNS_ADDRESS(#/R) [21],
SECONDARY_DNS_ADDRESS(#/R) [22]
you must manually reset all system UGW cards. To reset a UGW card enter
UPDATE?=YES (see page 29-26) under UGW: Current Configuration (page 29-13)
branch [UGWC, 1].
! WARNING:
It is recommended to manually update the UGW cards. Otherwise, the
cards are automatically reset when the system detects that UGW
database values have changed, in which case all calls are dropped
without warning.
SELF DOMAIN [20] Default: ttbsmgc

Range: as follows
R(remove), or
Any valid IP address (except 0.0.0.0 or 255.255.255.255), or
Any legal domain name of maximum 60 characters, case sensitive:
A-Z, a-z, 0-9, “*” (asterisk), “&” (ampersand), “+” (plus), “$” (dollar sign),
“-” (hyphen), “_” (underscore), “.” (period), “!” (exclamation point),
“~” (tilde), “/” (slash mark), “%” (percent)
Defines the IP address or domain name to be sent to the proxy server.
Defines the SIP domain for this Coral to be used with the SIP protocol.
This domain name, also known as RealM, is used to identify the Coral SIP entities
(i.e., defines SIP FROM field when responding to a SIP Invite request).
! WARNING:
Upon changing this parameter, you must manually reset all system
UGW cards. To reset a UGW card enter UPDATE?=YES (see page 29-26)
under UGW: Current Configuration (page 29-13) branch [UGWC, 1].
It is recommended to manually update the UGW cards (as described in
the warning). Otherwise, the cards are automatically reset when the
system detects that UGW database values have changed, in which case
all calls are dropped without warning.
29-76
PRIMARY_DNS_ Default: 192.168.10.10 (appears as - - - . - - - . - - - . - - -)

ADDRESS(#/R) [21] Range: as follows:
R (remove for - - - . - - - . - - - . - - - that is equivalent to 192.168.10.10).
When 192.168.10.10 is defined, DNS is not supported by the system.
Defines the IP address of the primary DNS (Domain Name Server). The DNS
associates the current IP address of the SIP service provider domain name for SIP
trunks.
! WARNING:
SECONDARY_DNS_ Default: 192.168.10.10 (appears as - - - . - - - . - - - . - - -)

ADDRESS(#/R) [22] Range: as follows:
R (remove for - - - . - - - . - - - . - - - that is equivalent to 192.168.10.10).
When 192.168.10.10 is defined, DNS is not supported by the system.
Defines the IP address of the secondary DNS (Domain Name Server). The
DNS associates the current IP address of the SIP service provider domain
name with SIP trunks.
! WARNING:

29-77
MAP:  The following parameters are displayed only when a MAP card is installed in
the system.
The MAP software status information can be viewed in the MAP Card branch
on page 27-4 (Root, 3, 10).
 Notes:
1) For Coral IPx Office the following parameters are not relevant because
the MAP address (and the CLA address) is the UGW address, as
described in UGW: Current Configuration, SIGNALLING: on page 29-15.
2) MAP is not available for Coral IPx 4000 and FlexiCom 6000 systems.
3) For Coral IPx 3000 and FlexiCom 5000 systems that have dual cages
and cabinets for duplicated common control, two (2) MAP cards must
be used, one in each control section.Both MAP cards must be
configured with the same IP address so that when the system switches
to the secondary control section the applications will continue to work.
IP_ADDRESS [23] ---.---.---.--- or R (Remove)

Enter the IP Address for the MAP card.
SUBNET_MASK [24] 255.255.255.255 or R (Remove)

Enter the Subnet Mask IP Address for the MAP card.
DEFAULT_ROUTER_ ---.---.---.--- or R (Remove)

ADDRESS [25]
Enter the Default Router IP Address for the MAP card.
UPDATE MAPs IP Yes/No

parameters? [26]
Enter N to escape this branch without saving the changes.
Enter Y to change the IP Address information.
! WARNING:
Updating the MAP IP Address causes the card to initialize, thereby
interrupting the connection to all the applications hosted by the MAP,
which might cause the applications to initialize as well. The CLA is also
reset
29-78
IP: Statistics ç IP,4 [9,4]
NOT USED IN THIS SOFTWARE VERSION.
IP: Statistics IP,4 [9,4]
29-79
IP: NET ç IP,5 [9,5]
This branch is used to define one unique IP (MGCP) Signalling Channel for the IP
Network ports (IP_NET) supported on the UGW card. The signalling channel
defined in this branch is used by all the UGW cards installed in this Coral system.
network. See UGW Software Upgrade: Activate on page 29-94.
 When UGW IP_NET ports are defined, increase the number of ISDN_
TRANSIT_ SETUPS (page 4-26) in the Sizes Tab branch.
NAME [0] 1..16 printable ASCII characters, R (Remove for BLANK);

BLANK
Defines the name of this IP Network signalling channel. This name is for reference
only and is not displayed anywhere else in the Coral system.
PROTOCOL_ID [1]  (Display Only) Q: QSIG

(Internal Network Trunks: ECMA 143/ETSI 300172/ISO DIS11572 Standard)
Displays the private network protocol as QSIG.
Send Connected Yes/No

Number to Public
For Incoming Network Calls: The Coral sends a Connect message which includes
Network [2]
the Connected Number to the Public Network when this parameter is set to Yes.
If, however, the Public Network does not support the Connected Number feature
according to ETSI or National ISDN standards, set this parameter to No.
QSIG
IP: NET IP,5 [9,5]
Definitions
SUPPORT CALL Yes/No
INDEPENDENT
Set this parameter to Y in order to support CISC calls (D-channel signalling with
SIGNALLING
no B-channel (voice)) thus enabling using QSIG Network features between nodes
CONNECTION [3] such as Camp-On and Follow-Me. Once a connection is made between the two
parties, signalling continues between both sides as required by the application.
Set to N if any one of the network nodes does not support CISC.
29-80
TRANSIT COUNTERS Yes/No

IN CISC CALLS [4]
Defines whether to set Transit Counters for the CISC calls. The Transit Counters
help avoid an endless loop scenario of forwarded calls. See TRANSIT COUNTER [0]
on page 28-3 for more information.
NET DIVERSION [5] Yes/No

Defines whether or not the Coral attempts to re-route calls to forwarded
destinations (as opposed to direct switching) in other PBXs by using QSIG
protocol.
This parameter affects the features Call Forward and Call Divert Network features.
Set this parameter to No if one of the PBXs in the network does not support QSIG
Call Forward by re-routing (otherwise a delay in the Call Connect Process may be
incurred).
TRANSIT_COUNTER_ ECMA/ISO
CODING [6]
A Transit PBX sends the call information in code form. This parameter defines
which QSIG code form is implemented. Enter ISO when an international standard
is needed. Enter ECMA for older European standards. ECMA standards have been
altered to conform to ISO standards and is thereby used in most cases.
The technician should match the QSIG code form to the code form used in the
system that the Coral is connected to.
PROTOCOL PROFILE ECMA/ISO

[7]
Define the Protocol Profile used for all the IP Network ports. The Protocol Profile
is defined as 11H for ECMA or as 1FX for ISO.
IP: NET IP,5 [9,5]
29-81
IP: ZONE ç IP,6

Each IP Zone can be assigned a Maximum Bandwidth limit definition for IP
destinations which are known to have narrow bandwidths. This branch enables
defining a maximum bandwidth limit for all calls placed through the IP Zone,
thereby limiting the number of simultaneous calls per IP LAN/WAN.
The technician must consider the specific call bandwidth needed based on the call’s
setup, i.e., the a common CODEC (Compression Capability parameter value in the
PI) as defined by the Media Gateway Module, the IP station, the Dial Service used
as well as the CODEC/s defined for the callers’ COS.
Table 29-10 defines the required bandwidth per call according to the Compression
Capability (CODEC) definition.
Table 29-10: Compression Capability (CODEC) Bandwidth Conversion
Compression Protocol Sampling Period Max Packets Max Bandwidth

Capability # per Second (kbps)
0 G.711 10 ms 100 96
1 G.711 20 ms 50 80
2 G.711 40 ms 25 72
3 G.723 30 ms 33.3 17
4 G.729 10 ms 100 40
5 G.729 20 ms 50 24
6 G.729 30 ms 33.3 19
7 G.729 40 ms 25 16
8 G.723 30 ms +vad 33.3 17
9 G.723 60 ms 16.6 12
10 G.729 20 ms + vad 50 24
IP: ZONE IP,6
11 G.711 80 ms 12.5 68
12 G.723 90 ms 11.1 10
13 G.729 80ms 12.5 12
This branch is used to ensure that a specific channel bandwidth is not exceeded and
thus avoid degradation of voice quality to all existing calls. It also blocks all
following calls until at least one current call disconnects.
When the maximum bandwidth is exceeded, new calls fail and a bandwidth
overload indication, B.W. Overload, is displayed on keysets as well as in the
IP Zone Display table. A reorder tone is also heard.
The IP Net destination receives cause 88H LAR trigger.
29-82
Examples:
Situation
IP Lines Location Signalling COS Required

Channel CODEC # Bandwidth
Bandwidth per call
5800 to 5809 US-North 128 5 24
5810 to 5819 US-South 64 13 12
Example 1: Coral A - Lines 5800 - 5809

• Location: US-North
• CODEC #5: Protocol G.729A at a sampling rate of 20ms (COS,0)
• 128Kb IP line towards the WAN.
• Examining Table 29-10 indicates that CODEC# 5 (729A/20ms) requires 24Kb
bandwidth per call.
Because the IP line for these lines has a bandwidth of 128kbps and each call
requires 24kb bandwidth, this IP line can allow a maximum of 5 simultaneous
calls.
• IP Zone Definition:
Define a bandwidth limit (see LIMIT (page 29-84)) of 128 for this IP Zone to
allow a max of 5 simultaneous calls thereby preventing an overload situation
that would drop all calls in progress.
Example 2: Coral A - Lines 5810 - 5819
• Location: US-South
• CODEC #13: Protocol G.729A at a sampling rate of 80ms (COS,0)
• 64Kb IP line towards the WAN
Examining Table 29-10 indicates that CODEC #13 (729A/80ms) requires
12Kb bandwidth per call.
Because the IP line for these lines has a bandwidth of 64kbps and each call
requires 12kb bandwidth, this IP line can allow a maximum of 5 simultaneous
calls.
• IP Zone Definition:
IP: ZONE IP,6

Define a bandwidth limit (see LIMIT (page 29-84)) of 64 for this IP Zone to
allow a max of 5 simultaneous calls thereby preventing an overload situation
 The technician must decide whether these are tolerable limits.

that would drop all calls in progress.
Financial districts and other high traffic districts may require defining the
first 5 lines in one IP Zone and the next 5 lines in another IP Zone (with
the same Bandwidth Limit) to create a completely non-blocking system.
29-83
Suggested IP Zone Definitions
Lines IP Zone Bandwidth LIMIT (kbps)

5800 to 5809 1 128
5810 to 5819 2 64
0-UPDATE
NAME (16) Maximum 16 ASCII characters, R (Remove for BLANK)
Default: BLANK
Define a name for this IP Zone (up to 16 alphanumeric characters).
USED  0..60000 kbps (Display Only)

Shows the current call bandwidth being used.
MAX 0..60000 kbps

OVERLOAD
Shows the peak bandwidth actually used.
When a call Bandwidth Limit is defined in the next parameter, this parameter
displays the OVERLOAD message when it is greater than the defined limit.
Enter 0 to reset when needed.
LIMIT 10..60000 kbps/R for remove/-- (no limit)

Default: -- (no limit)
Define a bandwidth limit, in kbps, for this IP Zone.
When this limit is exceeded, new calls will fail until the bandwidth use drops below
IP: ZONE IP,6
the limit.
29-84
INTER_ZONE_ IP/PCM
SELECTION
Define the “traffic” direction for this IP Zone.
Usually, IP calls made within the same zone are conducted as pure IP calls (IP).
When there is a need to force the RTP stream via the system’s PCM, choose PCM
for this option.
Setting this parameter to PCM aids in the “automatic” zone definition for Coral IP
phones as follows:
In previous Coral Versions, the IP phone travelling in and outside of the LAN was
required to change its Call Agent definition depending on where it was physically
located, in order to change between the IP Zones.
In Coral Version 15, the IP phone user can remain defined in a unique IP zone
defined for IP phones that change physical locations frequently (mostly soft-phone
users). The unique zone is defined to use PCM, thereby forcing all the calls via the
media module and the UGW. In this manner, whether the IP phone is external or
internal to the LAN, it uses the same Call Agent.
CALC_BW_ON_ Yes/No
PURE_IP_CALLS
When set to N (No), the bandwidth of pure IP calls are not included in the
calculation of the bandwidth of a given zone. When set to Y (Yes), the bandwidth
of pure IP calls is included in the calculation of the bandwidth of a given zone.
IP_ADDR Global/Local
Define which UGW IP Address the RTP stream should be sent to when using this
Zone, Global or Local.
Choose Global for Zones serving mostly external calls via the WAN.
Choose Local for Zones serving internal Coral IP endpoints within the LAN.
 Although Sentinel units serve external IP endpoints, they are considered

internal Coral IP endpoints. Therefore, their Required Zone definitions
IP: ZONE IP,6

(see REQUIRED_ZONE [3] (page 29-30) for Sentinel units or
ZONE (page 29-91) for Sentinel Pro units) should always be defined with a
local Zone (i.e. a Zone that has this parameter definition set to Local).
29-85
SIP_GUEST_TRUNK_ Any valid Trunk Group number or R for Remove

GROUP (V. 15.85.37 Default: No default defined
or higher) ** Warning!
Verify that parameters associated with SIP_GUEST_TRUNK_GROUP (V. 15.85.37
DEFAULT_TRUNK_ or higher) DEFAULT_TRUNK_GROUP (V. 15.85.16 or lower)
GROUP are defined to prevent toll fraud **
(V. 15.85.16 or lower)
This trunk group definition is relevant for incoming calls only, and is used for
Guest (page 29-52) SIP trunks “travelling” in this Zone (i.e., their IP address is not
registered in the Coral via SIP trunk branch or listed in a Dial Service).
The warning above means, to prevent Guest users from using the Coral to place
external calls, define a trunk group that allows only internal Coral traffic for this
parameter.
 Ensure that only SIP trunks are listed as members for this trunk group and
that the Trunk Group Definition is defined as QSIG (on page 8-19).
IPNET_IN_BAND_ Yes/No .
TONE
Defines system-wide, on which channel the system tones (e.g., Ringback tone) are
(V. 16.01 or higher) sent by the Coral over IPNET.
No - Tones are sent over signalling channel (B5H / B6H).

Yes - Tones are sent over RTP channel .
Set this parameter to Yes only when the far end is a Sea Softswitch (CSS) and
the Coral is configured as PCM in INTER_ZONE_SELECTION on page 29-85.
IP: ZONE IP,6
29-86
1-DISPLAY
From/To Zone# 0..7
Default: All Zones
Enter the IP Zones to be displayed from the lowest to the highest Zone.
An example of the PI screen displayed is shown in Table 29-11.
Table 29-11: Zone Display
ZONE NAME Used (kbps) Max (kbps) Limit (kbps)
0 CO-North 48 96 128
1 CO-South 24 24 64
2 West End 96 Overload 64

Office
3 BLANK 0 0 --
4 BLANK 0 0 --
5 BLANK 0 0 --
6 BLANK 0 0 --
7 BLANK 0 0 --
IP: ZONE IP,6
29-87
IP: SIP DOMAINS ç IP,7

Not Used.
IP: SIP DOMAINS IP,7
29-88
IP: SENTINEL Pro ç IP,8

The Coral maintains a pure IP connectivity to the Service Provider through the SIP
Trunk. In order to enable NAT Traversal and Firewall penetration, the Coral works
in conjunction with the Sentinel Pro and supports the SIP Trunk for inbound and
outbound calls.
This branch is used to identify Sentinel Pro units towards the Coral as Sentinel Pro
units. The Sentinels are defined with IP Keyset NPL type index numbers and no
dial numbers, see IP_KEYSET [41] (page 5-46).
The branch allows the technician to
0-UPDATE, 1-DISPLAY, 2-ADD or 3-REMOVE the Sentinel unit definitions as
needed.
• Add or remove a Sentinel unit INDEX Number, via the Sentinel branch, using
the IP,7,2 (ADD) or IP,7,3 (REMOVE) option.
• To define a Sentinel Pro unit, choose an IP Keyset index number. If the port is
already defined for another entity, the ALREADY DEFINED error message is
displayed.
Alternatively, Sentinels can be automatically assigned their index numbers
when self-initializing. Sentinel units added in this manner are assigned
IP Keyset index numbers from the end of the IP Keyset index number list.
! Caution:
This branch and its parameters are intended for Sentinel Pro units only.
Do not define these parameters for any other Sentinel type (Sentinel
Terminal, Sentinel-I, Sentinel-II) as this may impact system operation.
FROM/TO INDEX # Any Valid Sentinel Index Number (IP Keyset NPL types)
Enter the range of Sentinel units index number(s) from the lowest to the highest.
 The Sentinel PROs are assigned IP Keysets Index numbers.
IP: SENTINEL Pro IP,8

Therefore, the default for this option will display the range for all the IP
Keysets. However, index details will be shown only for the Sentinel units.
 The following parameters are valid only for the 0-Update, 1-Display, and
2-Add options.
CONNECTED_VIA_ Yes/No (Display Only)

SENTINEL
 This parameter is irrelevant in the current version, it is a future option
that always shows NO.
Sentinel units can be chained from one to another. Therefore, a Sentinel unit may
be connected via another Sentinel unit.
29-89
This parameter defines whether this Sentinel is connected to the Coral via another
Sentinel unit (Yes) or not (No).
29-90
ZONE 0..max defined in Sizes for ZONE (page 4-19) or R (for Remove)
Define an IP Zone for this Sentinel unit. This parameter must be defined in order
to accommodate IP devices that are to “automatically” initialize via this Sentinel
unit and thereby inherit the Sentinel’s IP Zone (as opposed to the UGW’s IP Zone
in previous Coral versions.)
MAC FF:FF:FF:FF:FF:FF:FF or R (for Remove)

Enter the unique MAC (Media Access Control) number for this Sentinel unit.
IP_ADDRESS ---.---.---.---:---- (Display Only)

Displays the IP Socket for this Sentinel unit.
STATUS  Display Only (see table below)

Displays the current status for this Sentinel Unit.
Displays the IP Network port’s current status:
Active The Port is Active
IP Contention The IP Address defined for this Sentinel is already being

used by another Coral entity.
Not Compat This Sentinel Version is not compatible with the Coral
Software version. The compatible Sentinel Pro Version is
5 or higher.
Missing Zone This Sentinel does not have ZONE defined.
Wrong Zone This Sentinel is registered via a call agent that does not
support its ZONE definition.
Unauthorized The Authorization limit for Sentinel units has been

exceeded.
No Resources No IP Keyset resources are currently available in this IP

zone.
IP Keyset resources are defined in the UGW Current
Configuration branch (IP,0,1).
-----: This dial number has not been defined.
Are you sure? Yes/No

Enter Yes to remove the Sentinel Pro unit or No to retract.
29-91
 The following parameters are valid only for the 3-Remove option.
REMOVE SENTINEL? Yes/No

Enter Yes to Remove this Sentinel Unit from the Coral database.
Only Sentinel units in UNDEFINED state can be removed.
The others remain as Display only.
29-92
Software Upgrade ç [ROOT,3,7]

This branch is used for software version downloading from a TFTP server provided
that the manufacturer has uploaded the new software version to the local TFTP
Server.
UGW Software Upgrade: Activate................................................... 29-94
UGW Software Upgrade: Cancel ..................................................... 29-97
IP Keyset Software Upgrade: Activate............................................. 29-99
IP Keyset Software Upgrade: Cancel ............................................. 29-103
Sentinel Software Upgrade: Activate ............................................. 29-106
Sentinel Software Upgrade: Cancel................................................ 29-110
Software Upgrade [ROOT,3,7]
29-93
UGW Software Upgrade: Activate ç [ROOT,3,7,0,0]

The UGW (PUGW, CUGW, UGW, UGW-E) card software may be updated by
downloading a software version from a TFTP server provided that the
manufacturer has uploaded the new software version to the local TFTP Server.
The following requirements must be fulfilled:
• The UGW must be active and registered (i.e., in Hardware Configuration - Card
List, the card should identify itself as a UGW card both in I_TYPE and P_
TYPE)
• To update UGW cards refer to Chapter 10, Coral Service and Peripheral
Cards Installation Manual.
The Software Upgrade may be assigned for a future date. Should the upgrade need
to be cancelled before the requested time and date, a cancellation procedure is
possible from: UGW Software Upgrade: Cancel (page 29-97).
network.
FROM/TO SHELF# All shelves installed with a UGW card

0: Coral FlexiCom 300, 400, 400V (Coral I & II);
0..1: Coral FlexiCom 200 (Coral III/SVC & SL);
0..15: Coral FlexiCom 5000, 6000 (Coral III/4GC)

2..3: Coral IPx Office expansion cages 500X/800X
UGW Software Upgrade: Activate [ROOT,3,7,0,0]
0..2: Coral IPx 500, 800

0..2: CDRS 200E
0..15: Coral IPx 3000, 4000
highest shelf number for the UGWs that must be upgraded on these shelves.
29-94
FROM/TO SLOT# All Slots installed with a UGW card

1..18: Coral FlexiCom 5000, 6000)

1..8: Coral IPx 3000M main cage (Shelf #: 0,8)
highest slot number for the UGWs that must be upgraded on these slots.
TIME HH:MM (HH = 00..24, MM = 00..59) in 24 HOUR Format

Default: Current time
Define the time for the software upgrade to be performed. Time must be entered as
hours and minutes in a 24 hour format.
[(HH:MM) HH = hours, MM = minutes]. The current time is displayed if no other
time is entered.
YEAR 1987..2084 or 00..99

Default: Current year
Define the year for the software upgrade. The year is entered with four digits or the
last two digits of the required year.

MONTH 1..12
Default: Current month
Define the month for the software upgrade. The month is entered by the actual
number of the month in one or two digits; January = 1, December = 12.
DAY 1..31
Default: Current day
Define the day of the month for the software upgrade. The day of the month is
entered in one or two digits.
29-95
TFTP_SERVER_IP_ ---.---.---.---
ADDR Default: None for initial entry; old entry for any new entry
Enter the IP address for the TFTP server that holds the UGW software version
upgrade file. Once an address is entered, the same address is retained and displayed
the next time an upgrade is requested.
FILE_NAME Any type of file name, up to 30 characters, including suffix

Default: None for initial entry; old entry for any new entry
Enter the UGW software upgrade file name. Once a name is entered, the same
address is retained and displayed the next time an upgrade is requested.

**Note: All devices within range will be upgraded**
Enter Yes to enable the request for the software upgrade to ALL the UGWs in the
requested range of shelves and slots.
Enter No to retract.
Note: If this upgrade is requested for a future date (as opposed to the current date
and time), it is possible to cancel the request from UGW Software Upgrade:
Cancel (page 29-97).
29-96
UGW Software Upgrade: Cancel ç [ROOT,3,7,1,0]

This from branch is used to cancel a request for a remote UGW Software Upgrade
from the TFTP server.
FROM/TO SHELF# All shelves installed with a PUGW card


0..2: Coral IPx 500, 800
0..2: CDRS 200E
0..15: Coral IPx 3000, 4000
highest shelf number for the UGWs that are requesting to cancel the software
upgrade.
FROM/TO SLOT# All Slots installed with a PUGW card

1..18: Coral FlexiCom 5000, 6000)

UGW Software Upgrade: Cancel [ROOT,3,7,1,0]

1..8: Coral IPx 3000M main cage (Shelf #: 0,8)
highest slot number for the UGWs that are requesting to cancel the software
upgrade.
29-97

**Note: Upgrade for all devices within range will be
cancelled**
Enter Yes to cancel the request for the software upgrade to ALL the UGWs in the
requested range of shelves and slots.
UGW Software Upgrade: Cancel [ROOT,3,7,1,0]
29-98
IP Keyset Software Upgrade: Activate ç [ROOT,3,7,0,1]

The FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL, T207S, T208S,
T207S/NP, T208S/BL , T322, T328, P-Seies (such as: P-335, P-450) software
version may be updated from the TFTP Server provided that the manufacturer has
uploaded the new software version to the local TFTP Server.
 Coral Versions Lower than 15:

The TFTP Server must be located on the same LAN as the IP Keyset.
 FlexSet-IP 280Ss with versions lower than 1.11, must be active in order to
receive the upgrade. Therefore, software upgrades via a TFTP server to
these types of IP Keysets must be done via the IP Address method.
 P-Seies (such as: P-335, P-450) telephones need FTP (not TFTP) access
for software upgrading. .
All other types of IP Keysets must be initialized, but need not be active in order to
upgrade their software versions via the TFTP server.
possible from: IP Keyset Software Upgrade: Cancel (page 29-103).
This branch offers two different methods of upgrading the IP Keysets, either by
their dial numbers (0 - DIAL NUMBER), or by
their IP addresses (1 - IP ADDRESS).
IP Keyset Software Upgrade: Activate [ROOT,3,7,0,1]

Details for the IP Keyset Software Upgrade Activation are found on the following
pages:
IP Keyset Software Upgrade: Activate by Dial Number ......................29-100
IP Keyset Software Upgrade: Activate by IP Address..........................29-102
29-99
IP Keyset Software Upgrade: Activate by Dial Number ç [ROOT,3,7,0,1,0]

This branch allows to define a range of IP Keyset Dial numbers for which to
simultaneously perform IP Keyset software version upgrades.
possible from: IP Keyset Software Upgrade: Cancel (page 29-103).
FROM/TO DIAL# Any valid system IP Keyset station number, All

Enter the required range of IP Keyset (FlexSet-IP 280S, T207M, T208M,
T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL , T322, T328, P-Seies
(such as: P-335, P-450)) dial numbers FROM the lowest number TO the highest
number requiring this software version upgrade procedure.

time is entered.
YEAR 1987..2084 or 00..99

IP Keyset Software Upgrade: Activate by Dial Number

MONTH 1..12
DAY 1..31
TFTP_SERVER_IP_ ---.---.---.---
29-100
Enter the IP address for the TFTP server that holds the IP Keyset software version

Enter the software upgrade file name. Once a name is entered, the same address is
retained and displayed the next time an upgrade is requested.

Enter Yes to enable the request for the software upgrade to ALL the IP Keysets in
the requested range of dial numbers.
and time), it is possible to cancel the request from IP Keyset Software Upgrade:
IP Keyset Software Upgrade: Activate by Dial Number
29-101
IP Keyset Software Upgrade: Activate by IP Address ç [ROOT,3,7,0,1,1]

Use this option to update unregistered IP Keysets. This branch allows upgrading
via the IP Address, the upgrade is performed immediately.
IP_ADDR ---.---.---.---
Enter the IP address for the IP Keyset to be upgraded.
When the IP Keyset is defined with dynamic IP addresses, change the definition to
a static IP address for this software upgrade. Once the upgrade is performed, the
request for dynamic IP addresses can be reassigned.
TFTP_SERVER_IP_ ---.---.---.---
ADDR
Enter the IP address for the TFTP server that holds the IP Keyset software version

Enter the IP Keyset software upgrade file name. Once a name is entered, the same

IP Keyset Software Upgrade: Activate by IP Address
Enter Yes to enable the request for the software upgrade to this IP Keyset. This
request is performed immediately and is final, no cancellation is possible.
29-102
IP Keyset Software Upgrade: Cancel ç [ROOT,3,7,1,1]

This branch is used to cancel a request for a remote IP Keyset Software Upgrade
from the TFTP server to a range of FlexSet-IP 280S, T207M, T208M, T207M/NP,
T208M/BL, T207S, T208S, T207S/NP, T208S/BL , T322, T328, P-Seies (such as:
P-335, P-450) IP Keysets or to a single IP Keyset.
The cancellation request can be made by accessing either the IP Keyset
Dial number (0 - DIAL NUMBER) or its
IP Address (1 - IP ADDRESS) for unregistered IP Keysets.
Details for the IP Keyset Software Upgrade Cancellation are found on the
following pages:
IP Keyset Software Upgrade: Cancel by Dial Number .........................29-104
IP Keyset Software Upgrade: Cancel by IP Address ............................29-105
IP Keyset Software Upgrade: Cancel [ROOT,3,7,1,1]
29-103
IP Keyset Software Upgrade: Cancel by Dial Number ç [ROOT,3,7,1,1,0]

from the TFTP server to a range of FlexSet-IP 280S, T207M, T208M, T207M/NP,
P-335, P-450) IP Keysets or to a single IP Keyset.
FROM/TO DIAL# Any valid system IP Keyset station number, All

Enter the required range of IP Keyset (FlexSet-IP 280S, T207M, T208M,
T207M/NP, T208M/BL, T207S, T208S, T207S/NP, T208S/BL , T322, T328, P-Seies
(such as: P-335, P-450)) dial numbers FROM the lowest number TO the highest
number upon which this cancellation procedure is to be performed.

cancelled**
Enter Yes to cancel the request for the software upgrade to ALL the IP Keysets in
the requested range of dial numbers.
IP Keyset Software Upgrade: Cancel by Dial Number
29-104
IP Keyset Software Upgrade: Cancel by IP Address ç [ROOT,3,7,1,1,1]

Use this option to cancel the update for unregistered IP Keysets.
from the TFTP server to a single FlexSet-IP 280S, T207M, T208M, T207M/NP,
P-335, P-450) IP Keyset.
IP_ADDR ---.---.---.---
Enter the IP address for the IP Keyset for which the software upgrade is to be
cancelled.
When the IP Keyset is defined with dynamic IP addresses, change the definition to

cancelled**
Enter Yes to cancel the request for the software upgrade to this IP Keyset.
IP Keyset Software Upgrade: Cancel by IP Address
29-105
Sentinel Software Upgrade: Activate ç [ROOT,3,7,0,2]

The Sentinel software version may be updated from the TFTP Server provided that
the manufacturer has uploaded the new software version to the local TFTP Server.
All types of Coral Sentinels may be upgraded via this branch.
This branch offers two different methods of upgrading the Sentinel units, either by
their index numbers (0 - INDEX NUMBER), or by
their IP addresses (1 - IP ADDRESS).
The Sentinel units must be initialized, but need not be active in order to upgrade
their software versions via the TFTP server.
possible from: Sentinel Software Upgrade: Cancel (page 29-110).
Details for the Sentinel Software Upgrade Activation are found on the following
pages:
Sentinel Software Upgrade: Activate by Index Number .......................29-107
Sentinel Software Upgrade: Activate by IP Address.............................29-109
Sentinel Software Upgrade: Activate [ROOT,3,7,0,2]
29-106
Sentinel Software Upgrade: Activate by Index Number ç [ROOT,3,7,0,2,0]

This branch allows to define a range of Sentinel index numbers for which to
simultaneously perform the software version upgrades.
possible from: Sentinel Software Upgrade: Cancel (page 29-110).
FROM/TO INDEX# Any valid system Sentinel index number, All

Enter the required range of Sentinel index numbers FROM the lowest number TO
the highest number requiring this software version upgrade procedure.

time is entered.
YEAR 1987..2084 or 00..99
Sentinel Software Upgrade: Activate by Index Number

MONTH 1..12
DAY 1..31
29-107
TFTP_SERVER_IP_ ---.---.---.---
Enter the IP address for the TFTP server that holds the software version upgrade
file. Once an address is entered, the same address is retained and displayed the next
time an upgrade is requested.

Enter the software upgrade file name. Once a name is entered, the same address is
retained and displayed the next time an upgrade is requested.

Enter Yes to enable the request for the software upgrade to ALL the units in the
requested range of dial numbers.
and time), it is possible to cancel the request from Sentinel Software Upgrade:
Sentinel Software Upgrade: Activate by Index Number
29-108
Sentinel Software Upgrade: Activate by IP Address ç [ROOT,3,7,0,2,1]

When upgrading via the IP Address, the upgrade is performed immediately.
IP_ADDR ---.---.---.---
Enter the IP address for the Sentinel unit to be upgraded.
When the Sentinel is defined with dynamic IP addresses, change the definition to
TFTP_SERVER_IP_ ---.---.---.---
ADDR
Enter the IP address for the TFTP server that holds the Sentinel software version

Enter the Sentinel software upgrade file name. Once a name is entered, the same
Sentinel Software Upgrade: Activate by IP Address

Enter Yes to enable the request for the software upgrade to this Sentinel. This
request is performed immediately and is final, no cancellation is possible.
29-109
Sentinel Software Upgrade: Cancel ç [ROOT,3,7,1,2]

This branch is used to cancel a request for a remote Sentinel Software Upgrade
from the TFTP server to a range of Sentinels or to a single unit.
The cancellation request can be made by accessing either the Sentinel Pro
index number (0 - INDEX NUMBER) or its
IP Address (1 - IP ADDRESS) for unregistered Sentinels.
Details for the Sentinel Software Upgrade Cancellation are found on the following
pages:
Sentinel Software Upgrade: Cancel by Index Number ......................... 29-111
Sentinel Software Upgrade: Cancel by IP Address ............................... 29-112
Sentinel Software Upgrade: Cancel [ROOT,3,7,1,2]
29-110
Sentinel Software Upgrade: Cancel by Index Number ç [ROOT,3,7,1,2,0]

This branch is used to cancel a request for a remote Sentinel Pro Software Upgrade
from the TFTP server to a range of Sentinels or to a single unit.
FROM/TO INDEX# Any valid system Sentinel index number, All

Enter the required range of Sentinel index numbers FROM the lowest number TO
the highest number upon which this cancellation procedure is to be performed.

cancelled**
Enter Yes to cancel the request for the software upgrade to ALL the units in the
requested range of dial numbers.
Sentinel Software Upgrade: Cancel by Index Number
29-111
Sentinel Software Upgrade: Cancel by IP Address ç [ROOT,3,7,1,2,1]

Use this option to cancel the update for unregistered Sentinels.
This branch is used to cancel a request for a remote Sentinel Pro Software Upgrade
from the TFTP server to a single unit.
IP_ADDR ---.---.---.---
Enter the IP address for the Sentinel for which the software upgrade is to be
cancelled.
When the Sentinel is defined with dynamic IP addresses, change the definition to

cancelled**
Enter Yes to cancel the request for the software upgrade to this unit.
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l
Sentinel Software Upgrade: Cancel by IP Address
29-112
PI Reference Manual
29-113
IP — Voice Over IP

PI Reference Manual
IP — Voice Over IP
29-114
30 Coral Traffic Report (CTR)
This chapter describes the programming options for the Coral Internal Traffic
feature.
Internal Traffic: Definition .........................................................................30-4
Internal Traffic: Features and Events Control............................................30-6
Internal Traffic: Reports: Format Parms ..................................................30-10
Internal Traffic: Reports: View ................................................................30-14
General
The Coral Internal Traffic feature allows the technician to create traffic reports
based on Coral Features and Events for a range of Coral entities such as stations,
trunks, etc. (see DIAL_NUMBER_TYPES (page 30-14) for entity types). These reports
may be stored and monitored for future use.
 This feature may require the installation of an extra memory card

(DBM or XMM) to support its memory requirements.
The events can be collected on a daily basis for a maximum of 71 days. The
technician defines the start time for each day or set of days. The reports are built
and configured via the PI by the technician, as required. The Coral allows the
technician to create a maximum of 10 different reports and offers 5 pre-defined
reports. The pre-defined reports are ready for use and can also be used as templates
to create customized reports.
There are three sub-branches which enable defining the reports after the relevant
and appropriate traffic definitions have been entered into the Sizes branch
(see NO_OF_TRAFFIC_EVENTS_AND_FEATURES (page 4-19)
and TOTAL_NO_OF_DAYS_TO_STORE_TRAFFIC (page 4-19)).
Software Authorization is required for this feature.
The Internal Traffic sub-branches include:
Traffic Definitions: The technician must define basic traffic terms for the Coral
system based on the user’s preferences.
Traffic Features and Events: The technician chooses which
Coral Traffic Features (on page 30-2) and Coral Traffic Events (on page 30-3)
are to be monitored. For systems with limited memory space, the technician may
either monitor a minimum of required features or reduce the number of days for
which to store the traffic reports.
Reports: The technician may build templates for the traffic reports. It also enables
the technician to view reports based on the requested entity (station, trunk, group,
etc.) number and type.
1. This number is limited by Coral free memory.
30-1
Coral Traffic Report (CTR) PI Reference Manual
Coral Traffic Features

The following table lists the Coral Features that can be monitored by the Internal
Traffic feature. The table lists the feature against each entity upon which it may be
activated.
Table 30-1: Coral Features activated on Entities
Feature Name Feature Default Stations Trunks Hunt Boss Wait_

Acronym Feature Groups Groups Que
Code
Call Forward All CFWD #141 4 4 4

Call Forward No Answer CFNA #142 4 4 4
Do Not Disturb DND #145 4 4
Executive Privilege EXEC #170 4
Direct Pickup GRP_PU #180 4 4 4
Silent Monitor SMON #1981 4 4
Divert Call DIVERT #145 4 4 4
FlexiCall FLEX #17710 4
Freedom (IRSS) IRSS #17714 4
30-2
PI Reference Manual Coral Traffic Report (CTR)
Coral Traffic Events

The following table lists the Coral Events that can be monitored by the Internal
Traffic feature. The table lists each event against the entity upon which it may be
activated.
Table 30-2: Coral Features activated on which entities
Feature Name Feature Station Trunk Trunk Hunt Boss Library Wait_
Acronym Group Group Group Que
Trunk Incoming Call TK_IN 4 4 4 4 4 4

Trunk Outgoing Call TK_OUT 4 4
Internal Incoming Call ST_IN 4 4 4 4 4 4
Internal Outgoing Call ST_OUT 4 4
Libraries Access LIB 4
Busy BUSY 4 4 4 4 4
Not Answered Call NO_ANS 4 4 4 4
Hanged Up Call HANGUP 4 4 4 4
Congestion CONG NA (System Resources)
Call Time CTIME 4 4 4

Wait Time for Answer WTIME 4 4 4
Above Average Call ABOV_T 4 4
Duration
Unusual Call Time CLTIME 4 4 4 4 4

Above Average Wait WTANS 4
Time For Answer
Constantly Connected CBUSY 4 4

Port
Trunk Overflow TK_OVR 4

Intercept Call INTCPT 4 4
Undefined Port UNDEF 4 4
30-3
Internal Traffic: Definition ç Root,3,9,0

This Definition branch is used to define basic traffic terms for the Coral system
based on the user/customer preferences.
TRAFFIC START TIME HH:MM (HH = 00..24, MM = 00..59) 00:00

This parameter defines the start time for the Internal Traffic Reports. Each day
starts at the same time.
Enter time in Hours:Minutes notation in military notation.
AVERAGE WAIT FOR 0..5..120 seconds

ANSWER
Define an average acceptable wait time period for calls to be answered. This
parameter relates to Stations, Hunt and Boss Group members.
This definition is used by the Internal Traffic reports to record when calls are not
answered within an acceptable wait time.
AVERAGE CALL TIME 0..2..1440 minutes

Define an acceptable time period for the duration of an average call (for stations or
trunks).
This definition is used by the Internal Traffic reports to record when calls last
longer than average.
AVERAGE CONNECT 0..60..1440 minutes

TIME
Define an acceptable connect time period for ports. This parameter is used to detect
Internal Traffic: Definition Root,3,9,0
busy trunks or ports that have not been released, i.e., the connect time is greater
than the call time.
30-4
DATA INITIALIZATION 1: Init Today (i.e. without storing)

2: Store Today and Init
3: Init All
No Default is defined for this parameter.
Define the Data Initialization time period:
Option Description
1 – INIT TODAY Allows the technician to currently initialize the

reports. Any previous data is not stored.
For Example:
Reports are defined to begin each day at 1AM.
Currently at 6AM the technician would like a new
report, but does not want to store any previous
information for the same day. Init Today erases all the
information prior to 6AM and initializes the day at the
current time, 6AM. The previous information for the
same day (i.e. between 1AM and 6AM is erased).
2 – STORE TODAY Allows the technician to currently initialize the
AND INIT reports and store any previous report information
from the same day as the previous day’s report.
For Example:
Reports are defined to begin each day at 1AM.
Currently, at 6AM the technician wishes to create a
new day’s report.
• The information collected between 1AM and
5:59AM belong to Day’s 1 report.
Internal Traffic: Definition Root,3,9,0

• The information collected between 6AM and
12:50 the next day belong to Day’s 2 report.
• The report information for Day 3 begins at 1AM
on the next day.
3 – INIT ALL Allows the technician to erase all previously stored
data and begin anew.
After choosing one of the data initialization options, the following message is
displayed:
WARNING: Data initialization will be done.
ARE YOU SURE(Y/N)?
Enter Yes to initialize the information and continue.
30-5
Internal Traffic: Features and Events Control ç Root,3,9,1

This branch enables defining which Internal Traffic Features and Events are to be
monitored.
When the particular feature or event is set to No, while the feature/event title may
be displayed in the report, no values will be listed for item.
The Feature or Event is presented in this branch followed by its Report Header
name (i.e. the name used in the traffic report for the specific feature) listed in
parenthesis.
 Coral systems with limited memory may choose to set only specific
features and events to Yes, in order to save memory resources.
Alternatively, the number of stored days may be decreased in order to

increase memory resources.
FEATURE EVENTS AND (REPORT HEADER) CONTROLS:
TRAFFIC  Set any one of the following parameters to Yes in order to monitor the specific
FEATURES: item. Each time one of these events is encountered, its count is raised by one.
FWD ALL (CFWD) Yes/No
 This does not include any of the special Call Forward All features such as
Call Forward All External or Internal or Attendant Call Forward feature.
Monitors all station Call Forward (default feature code: #141) events.
Internal Traffic: Features and Events Control Root,3,9,1
FWD NOANS (CFNA) Yes/No

Monitors all station Call Forward No Answer (default feature code: #142) events.
DND (DND) Yes/No

Monitors all Do Not Disturb (default feature code: #145) events.
EXEC (EXEC) Yes/No

Monitors all Executive Privilege (default feature code: #170) events.
DIRECT PICKUP Yes/No

(GRP_PU)
Monitors all Direct Pickup (default feature code: #180) events.
SILENT MONITOR Yes/No

(SMON)
Monitors all Silent Monitor (default feature code: #1981) events.
30-6
DIVERT (DFLT) Yes/No

Monitors all Divert (default feature code: #145) events.
FLEXICALL (FLEX) Yes/No

Monitors all FlexiCall calls (default feature code: #17710).
IRSS/Freedom (IRSS) Yes/No

Monitors all Freedom (IRSS) calls (default feature code: #17714).
TRAFFIC The following parameters, monitor the specific traffic event. Each of these traffic
EVENTS: events can occur on a Coral entity as described in Table 30-2 on page 30-3. Each
time an event occurs, its count is raised by one.
TRUNK INCOMING Yes/No

CALL (TK_IN)
Monitors the incoming external calls for the chosen entity. The entity may be a
station, trunk or any of the entities listed in Table 30-2 on page 30-3.
TRUNK OUTGOING Yes/No

CALL (TK_OUT)
Monitors the outgoing external calls for the chosen entity. The entity may be a
INTERNAL INCOMING Yes/No

CALL (ST_IN)

Monitors the incoming internal calls for the chosen entity. The entity may be a
INTERNAL Yes/No
OUTGOING CALL
Monitors the outgoing internal calls for the chosen entity. The entity may be a
(ST_OUT)
LIBRARIES ACCESS Yes/No

(LIB)
Monitors all Coral Public Libraries Accesses (i.e. how many times a Public Library
was dialed).
BUSY (BUSY) Yes/No

Monitors the phone’s busy count (i.e. how many times the phone was busy when
someone tried calling it).
30-7
NOT ANSWERED Yes/No

CALL (NO_ANS)
Monitors all calls that were not answered (i.e. for the phone that kept ringing until
the no answer timer expired).
HANGED UP CALLS Yes/No

(HANGUP)
Monitors all abandoned calls (i.e., unanswered calls for the called party station
-before the no answer timer expired).
This item is counted only for the called party entity (and not the calling party).
For Example: Station A calls Station B and A hangs-up before B answered. The
HANGED UP CALLS count is raised by one for Station B.
CONGESTION Yes/No
(CONGES)
Monitors failed calls due to a lack of Coral shared resources such as Time Slots,
DTMF, DTD, or when the internal Coral call tables, call records or call pools are
full,.
The report only includes a count for each called table and does not describe the
reason for the call failure.
CALL TIME (CTIME) Yes/No

Monitors the call duration of each call.
WAIT TIME FOR Yes/No

ANSWER (WTIME)
Monitors the Wait time for Answer per station. This is the time duration that the
caller waited for the call to be answered.
This item is only counted for answered calls.
ABOVE AVERAGE Yes/No

CALL DURATION
Monitors the number of calls that lasted longer than the average time for a call as
(ABOV_T)
defined in AVERAGE CALL TIME (page 30-4) in the Internal Traffic: Definitions
branch (Root,3,9,0).
UNUSUAL CALL TIME Yes/No

(CLTIME)
Monitors the number of calls conducted during holiday and weekend hours as
defined in the NIGHT branches.
ABOVE AVERAGE Yes/No

WAIT TIME FOR
Monitors the number of calls that waited a greater time than average to be
ANSWER (WTANS)
answered. The average wait time for answer is defined in AVERAGE WAIT FOR
ANSWER (page 30-4) in the Internal Traffic: Definitions branch (Root,3,9,0).
30-8
This item is only counted for answered calls.

CONSTANTLY Yes/No
CONNECTED PORT
Monitors the number of trunks or ports that were not released within a reasonable
(CBUSY)
amount of time as defined in AVERAGE CONNECT TIME (page 30-4) in the Internal
Traffic: Definitions branch (Root,3,9,0).
TRUNK OVERFLOW Yes/No

(TK_OVR)
Monitors the number of trunk overflow occurrences.
INTERCEPT CALL Yes/No

(INTCPT)
Monitors the number of call break-ins.
UNDEFINED PORT Yes/No

(UNDEF)
Monitors the number of undefined ports.
An undefined port includes any of the following:
• SIP, FlexIP SoftPhone or IP Stations/trunks that have lost their Primary Call
Agent because of Network or UGW card problems.
• FlexIP SoftPhone or SIP users not currently connected to a Network
• Unplugged FlexSets/Keysets
• SLTs connected to extracted line cards or malfunctioning cards
30-9
Internal Traffic: Reports: Format Parms ç Root,3,9,2,0

This branch is used to define the templates for the Internal Traffic reports by
defining a name for the report as well as which features or events should be
included in the particular type of traffic report.
Ten independent Internal Traffic Report templates can be constructed by the
technician.
• Five reports (Report # 0 to 4) are pre-defined, but can be changed.
Table 30-3 lists the pre-defined reports by name and shows which traffic
features and/or events are included in the report, by default.
• The other 5 reports are empty and should be constructed as necessary.
Table 30-3: Pre-Defined Internal Traffic Reports
Report # and Description Features Included System

Name by Default Wide
0-Feature & Call Records feature usage by • Call Forward No

stations, trunks and groups for • DND
a specific date.
• Divert Call
• Call Pickup
• Silent Monitor
• IRSS
• Trunk Incoming Calls
• Trunk Outgoing Calls
• Station Incoming Calls
Internal Traffic: Reports: Format Parms Root,3,9,2,0
• Station Outgoing Calls
1-Busy and Records occurrences of Busy • Busy No

Abandon and Abandoned calls at the • No Answer
stations, trunks and groups for
a specific date. • Hang-up
2-Time Records Accumulation events • Call Time No

Accumulation and number of calls that • Above average Wait Time for
occurred at a specific date for
Answer
specific stations, trunks and
groups.
30-10
Table 30-3: Pre-Defined Internal Traffic Reports
Report # and Description Features Included System

Name by Default Wide
3-Traffic Records the number of Traffic • Above average wait time for No
Exception exception events that occurred answer
for a specific date.
• Above average call duration
These events are calculated
based on each event time • Unusual Call Time*
definition available from the PI. • Constantly Connected Port
Events that end before the • Trunk Overflow from...
TRAFFIC START TIME (page 30-4)
• Intercepted Calls
are recorded as part of the day
events. • Undefined Ports
4-Congestion Congestion occurs when a call • Congestion Yes

cannot be established because
of a lack of system resources.
This report records the number Limiting Items (System
of failed calls due to Resources) causing Congestion:
congestion. • Time Slots
• DTMF
• DTD
• Call Table
• Call Record
• Pools
* Defined by the Night Service parameters (Root, 0,0,4,0)
30-11
From/To Report# 0..9;

Default: All
Enter the Report # or range of Report#s to be updated or displayed from the lowest
to the highest.
NAME Any ASCII characters: max, 16 characters; R (Remove for BLANK)

Default: Report 0: Feature & Call
Report 1: Busy and Abandon
Report 2: Time Accumulation
Report 3: Exception
Report 4: Congestion
Create a descriptive Name for this report using a maximum of 16 alphanumeric
characters.
A name defined as BLANK displays only the Report #. Use “_” (underscore) for
space.
SYSTEM WIDE Range: Yes/No (Set this to Yes for Congestion reports only)
Default: Reports 0 to 3: N
Report 4: Y
Reports 5 to 9: N
Set this parameter to Yes only when selecting system-wide items for the ON_LINE_
PARAMS parameter below when defining the report items.
Currently this parameter should be set to Yes only when the Congestion item
(17-CONGES) is selected in ON_LINE_PARAMS for the report.
30-12
ON_LINE_PARAMS Range: (0, 1,..,25,26) or ( ) - Blank

Default: see also Table 30-3
Report 0: (0,2,6,4,5,8,9,10,11,12)
Report 1: (14,15,16)
Report 2: (18,19)
Report 3: (19,20,22,23,24,25,25)
Report4: (17)
Reports 5 to 9: ( ) undefined
 A maximum of 20 items may be selected for any report.

Select the Feature and/or Event items to add to report. Only features or events that
were defined as Yes in the Internal Traffic: Features and Events Control branch
(Root,3,9,1) can be included in the reports.
This parameter lists the acronym for the features/events with the number that
represents the feature/event.
Create a report based on the items needed by adding or removing the numbers in
this parameter.
For Example:
• To create a report that includes the number of calls that executed CFWD and
DND, enter (0,2) under the display line.
• To add those items to an existing report template, enter: (a,0,2).
0-CFWD 1-CFNA 2-DND 3-EXEC 4-PICKUP

5-SMON 6-DIVERT 7-FLEX 8-IRSS 9-TK_IN

10-TK_OUT 11-ST_IN 12-ST_OUT 13-LIB 14-BUSY
15-NO_ANS 16-HANGUP 17-CONGES 18-CTIME 19WTIME
20-CLTIME 21-ABOV_T 22-WTANS 23-CONST 24-TK_OVR
25-INTCPT 26-UNDEF
• To add number(s), enter: (a, number1, number 2,...)
• To remove number(s), enter: (r, number1, number 2,...)
 Only when 17-CONGES is selected, the above parameter SYSTEM WIDE

must be set to Yes.

30-13
Internal Traffic: Reports: View ç Root,3,9,2,1
This branch is used to view the reports. Reports can be printed one at a time. The
technician must choose the entity (station, trunk, group, etc.) for the report as well
the range of dial numbers for the requested entity.
 Reports can be printed for any given day. Therefore, a full week’s report
must be printed one day at a time.
Select Report# 0..9

Select the type of report (i.e., Report #) to be printed based on the Report templates
created in the Internal Traffic: Reports: Format Parms (page 30-10) (Root,3,9,2,0)
branch.
FROM/TO ENTITY # Any valid Dial number

Enter the range of dial numbers for the selected report type.
DIAL_NUMBER_ Range: 1-Trunk

TYPES 2-SLT
3-EKT
4-TRUNK_GR
5-HUNT
6-BOSS
7-LIB
8-WAIT_QUE
Default: (1,2,3,4)
Internal Traffic: Reports: View Root,3,9,2,1
Select the Dial Number Types for the range of dial numbers selected above.
Enter one or more Dial Number Types between parenthesis.
All the dial numbers (from within the requested range listed above) matching the
requested NPL type are displayed.
 This parameter limits the requested FROM/TO ENTITY # range.

Only dial numbers matching the requested NPL types are shown in the
report.
30-14
N Days ago 0: Today

1: Yesterday
2: Two days ago
3: Three days ago
4: Four days ago
5: Five days ago
6: Six days ago
Choose the day for which the report details are to be displayed.
Choose 0 to print today’s report.
Choose 1 to print yesterday’s report.
...
Choose 6 to print the report from 6 days ago.
The number of previous days for which this report can be printed is limited by the
TOTAL_NO_OF_DAYS_TO_STORE_TRAFFIC (page 4-19) parameter defined in the
Sizes branch.
 The report shows the day the report was printed and not the day for which
the report details are shown. See example report below.
Example Report
Date & Time Report was

printed.
Report Type
(Not date of report details)
* Report7
Internal Traffic: Reports: View Root,3,9,2,1

DATE 05/01/05 TIME 11:10
Entity# TK_IN TK_OUT ST_IN ST_OUT HANGUP NO_ANS PICKUP
7101 0 0 0 1 --- --- ---
7102 0 0 0 0 --- --- ---
7103 0 0 0 0 --- --- ---
7104 0 0 1 0 --- --- ---
7105 0 0 0 0 --- --- ---
Range of Dial Numbers that

match requested NPL type
30-15
30-16
PI Reference Manual List of Abbreviations
Abbrv. Meaning Abbrv. Meaning

4SH/S Four Single Line Telephone Interface Card with
#’s Hotel Circuit
4SK Four Station Key Telephone Card

2DT T1, 30T, 30TM, PRI-23 or PRI-30 application
card, jumper selection. 4T Four Trunk Circuit Card
Due to logistical requirements, the cards are
labelled: "PRI-2DT", “PRI-2DTipx" or 4T Office Four Look Start Trunk Circuit Card -
"PRI-2DT Office”, on the front panel and on with power failure (PF) transfer and a multi-pin
attached shipping documentation. connector to attach an optional 4 CID card in
piggyback fashion for the
2SD Two Station Data Circuit Card Coral IPx Office
2SK Two Station Key Telephone Card 4T-C 4 port Loop-Start/Ground-Start trunk interface
card with power failure (PF) transfer and a
2500 SET The basic SLT touch-tone desk telephone multi-pin connector to attach an optional 4/
8CID card in piggyback fashion
3-Way Three Way Party Call
4T-Cipx 4 port Loop-Start/Ground-Start trunk interface
30T,30T/E 30 Digital Trunk Circuit Card -
multi-pin connector to attach an optional 4/
E1 European Standard
8CID card in piggyback fashion for Coral IPx
systems
30T Office 30 Digital Trunk Circuit Card -
E1 European Standard for the
4T-CID 4 port Loop-Start/Ground-Start trunk interface
Coral IPx Office
card with power failure (PF) transfer 4TBR with
a 4/8CID card in piggyback fashion
30T/M 30 Digital Trunk Circuit Card -
E1 Mexican Standard
4T-CIDipx 4 port Loop-Start/Ground-Start trunk interface
30T/x 30 Digital Trunk Circuit Card - multi-pin connector to attach an optional 4/
E1 Standard Variations 8CID card in piggyback fashion for the Coral
IPx systems
4ALS Four ALS70 Trunk Circuit Card
4T-CID Office4 port Loop-Start/Ground-Start trunk interface
4BID Four Trunk Belgium Inward Dialing card with power failure (PF) transfer and a
Circuit Card multi-pin connector to attach an optional 4 CID
card in piggyback fashion for the Coral IPx
4CID Office Daughter Board on the 4T Office card in Coral Office
IPx Office systems
4TBR Four Trunk BRI Circuit Card
4DTR Four DTMF Receiver Circuit Card
4TBR Office Four Trunk BRI Circuit Card for the Coral IPx
4GC Four Circuit Group Controller Circuit Card Office
4IAA 4 Port Integrated Automated Attendant 4TEM Four Trunk E&M Tie-Line Circuit Card
4/8/20S OfficeFour, eight or 20 port, 2 Wire - Single Line 4TEMP Four Trunk E&M Pulsed Tie-Line Circuit Card
Telephone Interface Card for the Coral IPx
Office 4TMR Four Trunk with Metering Circuit Card
Provides a multi-pin connector for optional 8Fx
Office or 16Fx Office daughter board 4TPF Four Trunk Power Fail Circuit Card
4S8F Office Combination Station Card. Four Single Line 4TWL Four Two Way Loop Trunk Circuit Card
Telephone circuits (4S Office) and eight SFT
Office circuits (8Fx Office) Interface Card for 4VS Four Digitized Voice Circuit Card -
the Coral IPx Office No Longer Available
4S+8Fx OfficeCombination Station Card. Four Single Line 4VSN Four Digitized Voice Circuit Card- field
Telephone circuits (4S Office) and 16 SFT installable voice messages
Office circuits (16Fx Office) Interface Card for
the Coral IPx Office 500 SET The old SLT rotary dial telephone desk
8ALS Eight ALS70 Trunk Circuit Card
Abbrv.-1
List of Abbreviations PI Reference Manual

8BID Eight Trunk Belgium Inward Dialing 8SM, 8SMipxEight Magneto Telephone Circuit Card
Circuit Card
8T Eight Trunk Circuit Card
8CID Office 8 CID Daughter Board on the 8T Office card in
Coral IPx Office systems 8T Office 8 port Loop-Start/Ground-Start trunk interface
Includes 8 FSK tone receiver and decoders. card with 4 ports for power failure (PF) transfer
and a multi-pin connector to attach an optional
8DID Eight Trunk Direct Inward Dialing Circuit Card 4/8CID card in piggyback fashion for the
Coral IPx Office
8DTD Eight Dial Tone Detector Circuit Card
8T-C 8 port Loop-Start/Ground-Start trunk interface
8DTMF Eight DTMF Receiver Circuit Card card with power failure (PF) transfer and a
8DTR Eight DTMF Receiver Circuit Card 8CID card in piggyback fashion
8Fx Office Daughter Board on the 4S Office or 8S Office 8T-Cipx 8 port Loop-Start/Ground-Start trunk interface
cards in Coral IPx Office systems. card with power failure (PF) transfer and a
Supports 8 SFT ports. multi-pin connector to attach an optional 4/
8CID card in piggyback fashion for Coral IPx
8SD Eight Station Data Circuit Card systems
8/16/24SDT Standard Digital 8, 16 or 24 Line Telephone 8T-CID 8 port Loop-Start/Ground-Start trunk interface
Interface Card card with power failure (PF) transfer 4TBR with
a 4/8CID card in piggyback fashion
8/16/24SFT Standard Digital 8, 16 or 24 Line Telephone (2-
wire) Interface Card supporting the FlexSet as 8T-CIDipx 8 port Loop-Start/Ground-Start trunk interface
well as the DKT/DST/GKT series. card with power failure (PF) transfer and a
8CID card in piggyback fashion for the Coral
8/16SFTipx Standard Digital 8 or 16 Line Telephone
IPx systems
Interface Card for the Coral IPx 500 and
CDRS/CDRX 200E supporting the FlexSet as
well as the DKT/DST/GKT series. 8T-CID Office Combination Trunk Card. 8T Office and 8CID
card on 8T Office board in piggyback fashion
for the Coral IPx Office.
8S+8Fx OfficeCombination Station Card. Eight Single Line
Telephone circuits (8S Office) and eight SFT
Office circuits (8Fx Office) Interface Card for 8TBR Eight Trunk BRI Circuit Card
the Coral IPx Office
8TPF Eight Trunk with four Power Fail Circuit Cards
8S+16Fx
12Sx Office Daughter Board for the 8S Office card for Coral
Office Combination Station Card. Eight Single Line IPx Office systems that adds 12 SLT ports.
Telephone circuits (8S Office) and sixteen SFT Enables a total of 20 SLT ports.
Office circuits (16Fx Office) Interface Card for
the Coral IPx Office 16Fx Office Daughter Board on the 4S Office or 8S Office
cards in Coral IPx Office systems.
8/16/24SFT Supports 16 SFT ports.
Office Standard Digital 8, 16 or 24 Line Telephone
16SH/S 16 Single Line Telephone Interface Card with
(2-wire) Interface Card for the Coral IPx Office
Hotel Circuit
supporting the FlexSet as well as the DKT/
DST/GKT series.
16SKD 16 Station Key Digital Circuit Card
8SH/S Eight Single Line Telephone Interface Card
with Hotel Circuit A
8SK Eight Station Key Telephone Circuit Card
AA Automated Attendant (4IAA card)
8SKD Eight Station Key Digital Circuit Card
ACC Access
8/24SA 8 or 24 Line Standard 2-Wire Single Line
Station Interface Card for 2500 type phone ACCT Account Code
8/16/24SLS 8, 16 or 24 Line Standard 2-Wire Single Line ACD Automatic Call Distribution, Automatic Call
Station Interface Card for 500/2500 type phone Distributor
Abbrv.-2

ACK Acknowledge BRI Basic Rate Interface (ISDN) 2B+D
(see also 4TBR, 8TBR)
ACNR Automatic Call Number Redial
BSY Busy
ACSE CoraLINK-Application: Association Control
Service Element BUT Button on a keyset
AE Application Entity
C
ALI Automatic Location Identification. This is the
cross referenced location information based on
the caller’s ID. CAMA Centralized Automatic Message Accounting
(Used for USA systems only). CAMA telephony
ALS70 (Abonnee Lijn Signalering 1970) Trunk protocol detects MF tones sent by the
Circuit Card - Netherlands Standard telephony equipment and deciphers the caller
ID.
ANF Additional Network Feature
CAP Computerized Attendant Position
ANI Automatic Number Identification
CC Country Code
ANS Answer
CCS Continuous Communication Systems
ANSI American National Standards Institute
CCM Coral Call Master: Coral system to run ACD
APA Application Processor Adapter For a DKT2000 applications.
Telephone
CDB Card Database
APDL Applications Processor Data Link
CEPT European Conference of Postal and
APDU Application Protocol Data Unit Telecommunications Administration
API CoraLINK-Application Programming Interface CF Call Forward
APS AC Power Supply CFM Coral Fault Manager
ARS Automatic Route Selection CID Caller ID
ASCII American Standard Code for Information CISC Call Independent Signalling Connection
Interchange
CKT Circuit
ASN.1 Abstract Syntax Notation One
CLA CoraLINK Adaptor (piggy back) Baby card is
ASU Auxiliary Service Unit Circuit Card located on the MEX-IP2 or MCP-IPx2 card for
CTI applications.
ATT Attendant
CLI Calling Line Identification
B CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction

BCS Bearer Capability Support (ISDN)
CLIS <parameter name>Card List
BCCOS Bearer Capability COS
CNF Conference Circuit Card
BER Basic Encoding Rules
CO Central Office, Public Exchange (same as LEX)
BI_D Bi-Directional R2MFC Protocol for use with
30T/M card version 32.xx and later CONF Conference
BID Belgium Inward Dialing Coral Common

Control Coral systems based on a MEX-IP2, MCP-IPx2
BLF Busy Lamp Field and MCP-ATS;
BPS Bits Per Second (RS-232 parameter)
Abbrv.-3

Coral DID Direct Inward Dialing (same as DDI)
FlexiCom Family of Coral FlexiCom 200, 400, 5000, 6000
systems DIL Direct In-Line
Coral IPx Family of Coral IPx 500, 800, 3000, 4000 DIM Data Interface Module
Systems for 19” and 23” rack mounting
DISA Direct Inward System Access
COS Class of Service
DISC Disconnect
CPA Coral Paging Adapter
DKT Digital Key Telephone (Full Feature Phone), 2-
CPN Calling Party Number Wire Interface
CPS Control Power Supply DLIS Digital List
CSLX Coral FlexiCom 200 Expansion Unit. Maximum DND Do Not Disturb
of 2 Expansion units per Coral SL or FlexiCom
200 Base unit. DNIS Dialed Number Identification Service
CSTA Computer Supported Telecommunication DOD Direct Outward Dialing (same as DDO)
Applications; OSI Layer 7 Communication
between a computing network and a CoraLINK DP Dial Pulse
System
DPC Digital Protocol Converter Card
CSTS Coral Supported Telephony Services
CSTS, is a Coral protocol and is used for DPEM Digital Programmable Expansion Module for
communication between the CCM 3 and the DKT 2000 sets (FlexSet 40B for FlexSet 280
Coral, providing more data transfer ability and Series)
better stability. Using the CSTS, Coral includes
ANI and DNIS information in the messages DSE Dialogue Service Element
among other relevant data.
DSL Digital Subscriber Line
CTI Computer Telephony Integration
DSP48 Display Module, 2 rows by 24 characters
CTR Coral Traffic Report
DSP80 Display Module, 2 rows by 40 characters
D
DSS Direct Station Selection
DSS1 Digital Subscriber Signalling no.1

DB Database
DST Destination (used in database control)
DBX 1 MB Static RAM piggy-back located on the
MEX-IP2 or MCP-IPx2 card for database
software with battery backup (Coral Common DST Digital Standard Telephone or Digital Single-
Control) Line Telephone,
2-Wire Interface
DDI Direct Dialing Inward (same as DID)
DTD Dial Tone Detector
DDO Direct Dialing Outward (same as DOD)
DTE Data Terminal Equipment
DDT Distinctive Dial Tone
DTR Data Terminal Ready
DEST Destination
DTMF Dial Tone Multi-Frequency
DGT Digit (0 to 9, * or #)
DVMS Digitized Voice Message System, based on
4VS or 4VSN cards.
DGTL Digital Trunk
DI Diagnostics E
Dial Pad Telephone Dial Pad including the numbers 0
through 9 and * and #. E1 30 Digital Circuit Card - European Standards
Abbrv.-4

E911 Emergency 911 call
H
E&M Tie Trunk (Ear and Mouth)
ECMA European Computer Manufacturers Association HDLC High Data Level Control
EIS EKT to SLT Interface, Special Mode HI Human Interface (same as PI)
EKT Electronic Key Telephone, 4-Wire Interface HF Hookflash
EOD End of Dial HKFLS Hookflash
EOS End of Selection

I
ESIM Office Expansion Shelf Interface Card in the Main
Unit for the Coral IPx Office.
I/C Incoming Call
ESIX Office Expansion Shelf Interface Card in the
Expansion Unit for the Coral IPx Office. I/O In/Out
ETSI European Telecommunications Standards ICD International Code Designator

Institute
iCMC Integrated Coral Message Center
EU Europe
ID Identification
EVEN Evening
iDSP 64 circuit FSK (Frequency Shift Keying) tone
EXE Executive (Privilege) generator shared service card
EXCL Exclude IMC8 Integrated Memory Card with 8 Mbytes flash

memory capacity for the MEX-IP2 and
EXT External Call MCP-IPx2 Common Control Card. It contains
the generic software of the Coral and is used
to store the system database.
F
INT Internal Call
FAC Forced Account Code IP Internal Protocol
FCC Federal Communication Commission (USA) IPC Office/SFCSFC card for the Coral IPx Office
FIE Facility Information Element IPC Office/
FKT Fonetasy Key Telephone uCMC uCMC card for the Coral IPx Office
FWD Forward IPC Office/

WiCMC WiCMC card for the Coral systems
G
ISBX Integrated Services Business Exchange
GID German Inward Dialing ISDN Integrated Services Digital Network
GFT Generic Functional Transport IST Industry Standard Telephone (same as SLT)
GKT Graphic Key Telephone K

GRP Group
Keyset FlexSet/FlexSet-IP/T200/T300/P-Series/EKT/
GS Ground Start Trunk VDK/DKT/DST/GKT/FKT Telephone
KB Kilo Bytes (used for memory size)
Abbrv.-5

KB0 Keyboard Number 0 on Main Control Card MSG Message
(MCP-IPx2, MEX-IP2, MCP-ATS, MCB Office,
etc.) MSI Manufacturer Specific Information
KB1-24 Keyboard Number 1 -24 MSN Multiply Subscriber Number
KSI EKT to SLT Interface

N
L
N/A Not Applicable
LEX Local Exchange (CO) as used in Europe NA No Answer
LCR Least Cost Routing NFE Network Facility Extension
LDN Listed Directory Number (site LDN) NP, NPL Numbering Plan
LED Light Emitting Diode NPID Numbering Plan Identification (PRI calls)
LGS Loop/Ground Start Trunk NSF Network Specific Facility
LIB Public or Private Library NUM Number
LS Loop Start Trunk

O
M
OAI Open Application Interface
MCP-ATS MCP Card for Coral FlexiCom 6000 and Coral O/G Outgoing Call
IPx 4000 Common Control
OHVA Off-Hook Voice Announce
MCP-IPx MCP Card for Coral IPx 500 and FlexiCom 200
Common Control in Software Versions 14.6x ONHK Onhook
MCP-IPx2 MCP Card for Coral IPx 500 and CDRS/CDRX

200E Common Control in Software Versions 15 P
and later
MEX-IP2 MCP Card for Coral FlexiCom 300, 400, 5000 PABX Private Automatic Branch Exchange
and Coral IPx 800, 3000 Common Control in
Software Versions 15 and later PAD Packet Assembly Disassembly
MDF Main Distributing Frame PB Peripheral Buffer Circuit Card
MEM Member PBX Private Branch Exchange
MFC Multi-Frequency Code PC Personal Computer
MFR Multi Frequency Receiver Card PC-ACD Personal Computer Automatic Call Distributor
MIC Microphone PCB Printed Circuit Board
MIS Management Information System for Traffic PCC PC Console

Reports (old-see TAP)
PCM Pulse Code Modulation
MPEM Multi-Programmable Expansion Module for EKT
and VDK Sets PDB Port Database
MR Office Main Resources Card for the Coral IPx Office PEM Programmable Expansion Module for EKT and
VDK sets
MSDX Mass Storage DX
PEX Peripheral Expansion for DKT sets
Abbrv.-6

PF Power Fail RO Remote Operations
PI Program Interface (same as HI) ROSE CoraLINK-Remote Operation Service Element
PICS Protocol Implementation Conformance ROW Rest of the World

Statement
RPS Ringer Power Supply
PISN Private Integrated Services Network
RSIA Remote Shelf Interface Adaptor Card
PINX Private Integrated Services Network Exchange
RSIM Remote Shelf Interface Master Card
PLIS Port List
RSIS Remote Shelf Interface Slave Card
PMS Property Management System
RTSE Reliable Transfer Service Element
PPS Peripheral Power Supply
RTT Regie of Telegraphy and Telephone
PREF Preference (Belgium)
PRI 23 Primary Rate Interface Card, (23B+D) 1.5

Mbps, Enables Coral subscribers to connect to S
the ISDN public network
PRI 30 Primary Rate Interface Card, (30B+D) 2 Mbps, SAU Software Authorization Unit for controlling
Enables Coral subscribers to connect to the system software packages plugged on the
ISDN public network 32GC, MEX-IP2, MCP-IPx2 or MCB Office card
PRI 30 OfficePrimary Rate Interface Card, (30B+D) 2 Mbps SCM Signalling Carriage Mechanism
for the Coral IPx Office.
Enables Coral subscribers to connect to the SDT Secondary Dial Tone
ISDN public network
SDT Digital Key (DKT &DST) Station Card
PRIO Priority
SEC Secondary
PRIV Private Library
SER Serial Number
PRM Primary
SERV Service
PROG Program
SFT Coral Peripheral Station Cards supporting
PTS Proceed to Send FlexSets as well as the DKT/DST/GKT series.
PTT Post, Telegraph and Telephone Administration SG Stop/Go
PUB Public Library SIP Session Initiation Protocol
PWDS Ports Without Disconnect Supervision SKW Wireless Extension Interface Card with support
for base stations
R SLT Single Line Telephone (same as IST)
SLS Single Line Station Card

RAM Random Access Memory
SMDR Station Message Detail Recording
RBS Radio Base Station for Wireless Systems
Soft Keys Programmable Telephone Keys relating to
RCV Receive different telephone conditions
RJCT Reject SPKR Speaker
RMI Remote Maintenance Interface Circuit Card SRC Source (used in database control)
RMI Office Remote Maintenance Interface Circuit Card for SS Supplementary Service
the Coral IPx Office
Abbrv.-7

ST Station VDK Voice Data Keyset, 4-Wire Interface
STR Start Time/Day VDM Voice Data Module for DKT 2000 Series
SUSP Suspect VDU Video Display Unit
SZ/SZE Seize VFAC Verified Forced Account Code
VIC Vision-Impaired Console

T
VOL Volume
T1 24 Digital Trunk Circuit Card - VP Voice Page
North American Standard
VSM Voice Synthesizer Module for Visually Impaired
TAP Traffic Application Package operator connected to an EKT
TBR Trunk BRI Circuit Card
W
TBRP Trunk BRI Circuit Card with external power
option
WST Wireless Station (FlexAir/CoralAIR handset)
TC Trunk Code (GID)
WU Wakeup, Wake up
TDM Time Division Multiplexing
TERM Terminal X
TIM Terminal Interface Module

XFER Transfer
TK Trunk
TK-G Trunk Group
TK-N Trunk Number
TNNT Tenant
TRX/TX Transmit
U-MR Office Universal Main Resources Card for the Coral

IPx Office
U-RMI OfficeUniversal RMI Card for the Coral IPx Office
UCD Uniform Call Distributor
UDT Office T1 or PRI-23 application card, jumper selection
UM Universal Messaging
UNA Universal Night Answer
UNATT Unattended
VAC Verified Account Code
Abbrv.-8
PI Reference Manual Index
Index Shared Resources Ports 6-88

Sizes 4-15
8DRCM
Numerics Music Source Physical Location 4-45
PI Connections 1-10
0/0 Database Programming 6-61 PI Interface 1-2, 1-3
1st Digit Ports 4-17, 4-25
Incoming Trunk, Waiting Time 8-4 Ports,Paging and Music 23-8
Outgoing Trunk, Waiting Time 8-5 Required Ports 4-17, 4-25
Station, Wait Time 9-3 Shared Resources Ports 6-88
2/4 Wire Sizes 4-15
E&M Trunk Def. 8-87
2-Way Hold A
Boss Group 6-27
Abbreviated Dialing
30T
See Libraries
Sync. 8-98
Access Code
30T/M
See General Numbering Plan
Bi-Directional, R2MFC 8-95
Ignore Q.422, Supp 6 Protocol 8-115 Account Code
#Acct Dgts 6-9
3Way
Account, fail destination 6-38
Boss Groups 6-28
Caller ID 6-13
Conference Resources 4-17, 4-25
Forced Account Code Trunk Groups/Routing
Conference, URC 4-33
Access, COS 7-4
COS 7-6
NPL 5-33
define type, COS 7-6
Pass Account Code for Trunk upon Transfer
required for Path Replacement 28-5
6-10
URC Conf, SAU requirement 3-17
regular, COS 7-18
4IAA Card Station Options, during call 6-28
Sizes 4-16 Verified Forced, C OS 7-18
4TEMP ACD
Blocking by Continuance 8-70 Announcer, SLT Def. 9-10, 9-42
Blocking By No Response 8-71 Automatic Release, NPL 5-35
Blocking by Pulse 8-68 Busy/Idle Block 9-52
Clear By Continuance 8-78 Call Waiting Tone 10-13
Clear By Pulse 8-76 COS definitions 7-25–7-26
Clearing 8-74 First Announcer 10-15
Hookflash 8-67 Hunt Group Overflow Destination 10-6
Incoming Calls 8-79 Hunt Groups 10-2–10-17
Outgoing Calls 8-81 Inactive Group settings 10-6
4TWL IVR connection 10-4
Index
Card Database 8-84 IVR timer 10-13
4VS Card 23-2 Load ID, COS 7-25
4VSN Card 23-2 Load ID, Forced 10-5
802.1Q/p protocol 29-18, 29-19, 29-33, 29-73 Load ID, NPL 5-35
Login, COS 7-25
8DID
Login, NPL 5-35
Card Database 8-91–8-94
Mandatory 10-14
8DRCF max wait, NPL 5-28
Music Source Physical Location 4-45 Max Waiting Calls 10-11
PI Connections 1-10 Members 10-17
PI Interface 1-2 Music Source 10-9
Ports 4-17, 4-25 PC Console Protocol 9-49
Index-1
Index PI Reference Manual
Primary Login, NPL 5-37 Numbering Plan 5-18

Protocol Type,Keysets 6-25 Outgoing 8-141
Release, COS 7-25 Port Database 8-141–8-144
Ring/No Answer Hunt Group 10-8 Shelf #, Slot # 8-136
SAU requirement 3-20 Voice Transmission Controls 19-1
Second Announcer 10-16 Alternate Route
Statistical Search 4-26, 10-5 Libraries 8-34
Unavailable Hunt Group 10-7 Trunk Groups 8-34
VDK to PC Console 9-49 ANI
Waiting Calls Display 5-36 # of digits for CAMA 6-14
Waiting Calls Display, COS 7-26 Call Forwarding
Wrap Up Code, COS 7-25 Call Forward
Wrap Up Time, COS 7-25
control ANI 6-15
Wrap Up, NPL 5-35
Define Filters for Incoming ANI 8-27–8-30
ACD/UCD Define incoming ANI on Trunk Group 8-26
Announcer Def. 9-42 Dial Service, Offset Filter 15-12
ACNR Emergency Calls Center default 6-13
see Auto Redial FlexiCall
Activation Code 5-39 FlexiCall
Add-On Conference control ANI 6-16
See Conference Freedom
Adjacent Entity Number 26-18 Freedom
Advice of Charge control ANI 6-16
See AOC identify 3rd party CAP 6-33
Agent ISDN 26-9
See ACD/UCD Member ISDN Dial Filter 26-2, 28-14
ISDN Signaling Channel 26-16
Alarm
Routing Access 15-7
by ATT, COS 7-42
Screening 8-20
by Attendant, NPL 5-34
By PI, Diagnostic 22-5 Announcements
By PI, On-Line Diagnostics 17-4 MLPP 6-48
FlexAir button Def. 9-77 Announcer
Minor/Major Relay 6-53 ACD, First Announcer 10-15
Terminal Destination 17-8, 27-6 ACD, Mandatory 10-14
A-Law 6-52 ACD, Second Announcer 10-16
Coding Basic Tones 6-102 iVMF ports 17-32
SLT 9-10
Alerting
System Features 6-43
See Ring, Ringers
VM Group def 10-3, 10-4
ALI Wakeup, Destination 6-42
Index
ISDN 26-9
Announcer Cards
Keyset Def. 9-60
IPC/SFC 10-14
Sizes 4-20
iVMFipx 10-14
SLT Def. 9-13
Answer From Any Phone
All Call Paging
See Pickup
See Zone Page, Voice Page
Answer Supervision
ALS70 8-135–8-145
4TEMP 8-65
Card Database 8-138–8-140
4TEMP, Detection Time 8-82
Configuration 8-136
4TEMP, Pulse Duration 8-81
DID Port Database 8-143
4TEMP, Wait Timer 8-73
Incoming 8-138
4VS, SAU requirement 3-22
Loop Start Port Database 8-142
CoraLINK, Wait Queue 27-18
Meter 8-140
Index-2
DVMS Message 23-3 Authorization 2-11

E&M Cont., Minimum Period 8-61 example on PI screen 1-12
E&M Cont., Pulse Duration 8-60 Features 3-5–3-25
E&M Timers 8-61 SKW Card 6-59
E&M, Mandatory 8-88 Auto Answer
for Polarity Reversal 8-47 Keyset Def. 9-39
General Trunk Timers 8-5 Keyset, Timer 9-27
LS/GS, Digital Trunk 8-46 Magneto, Timer 9-4
AOC-E_Display NPL 5-24
Charges 6-10 Voice Page, Calls Timer 9-27
Keyset Def. 9-61 Voice Page, Keyset Def. 9-44
Keyset Timers 9-27 Auto Guard
Metering Unit Charge 8-31 Attendant, COS 7-38
APA Attendant, NPL 5-34
PC-ACD, Keyset Def. 9-49 System Features 6-53
PCC_CAP, System Features 6-32 Trunk General Definition 8-13
SAU requirement 3-15 Auto Redial
Setup 9-119 Capacity 7-29
Station Option definition for messages 6-32 COS 7-29
APDL Edit, NPL 5-39
ATT, Keyset Definition 9-35 Maximum Attempts 6-13
Multi-Appearance, Keyset Def. 9-37 NPL 5-31
PC_ACD, Keyset Def. 9-49 Timer between attempts 6-2
Setup 9-119 Tone Delay, Timer 8-5
APS Auto Release
Ringers 6-20 ACD Hunt Group 10-8
ARS (Automatic Route Selection) Auto Set Relocate
See Routing COS 7-22
ASU Keyset Def. 9-63
Sizes 4-15 NPL 5-22
Attendant SAU requirement 3-24
Auto Hold/Transfer, Keyset Def. 9-45 SLT Definition 9-15
Feature Activation 18-2 Temporary/Permanent 6-22
Keyset, Identification 9-36 Automated Attendant
Message Features 6-44 Button Programming 9-77
Multi-Appearance 9-37 Keyset, NPL 5-18
Numbering Plan 5-18 PCC (CAP), Keyset Def. 9-47
Operator Access 6-19 See 4IAA
SLT, identification 9-8 Automatic Callback
Speaker Key ON/OFF, Keyset Def. 9-46 See Camp-On
Attendant COS Automatic Dialing
Index
Station Controls 7-33–7-37 See Libraries

System Controls 7-41–7-43 Automatic Hold
Trunk Controls 7-38–7-40 Keyset Def. 9-45
Audible Indication Control Automatic Privacy
See Ring Level See Privacy, Data Line Security
Audio Transmission
See Voice Transmission B
Authentication
SIP Interval 29-74 B Channel
SIP Password 29-74 See PRI, TBR, BRI
Index-3
B_Channel_Negotiation 26-14 Exclusive Hold, NPL 5-32

Backup Full Name 10-19
See Database Backup Line Key, NPL 5-22
See SMDR Backup Maximum Boss Ringers 6-21
Balanced Network Members 10-21
See Voice Transmission Controls Numbering Plan 5-19
Privacy, NPL 5-32
Balanced Return Loss
Sizes 4-14
See Voice Transmission Controls
Boss Groups
Balancing Network 19-24
Reserve Public Lib to BG
Basic Tones
Break Dial
Defaults by Country 6-102
4T/8T O/G Trunk 8-53
Battery Backup 4TEM I/C Trunk 8-62
See MSX & DBX cards 4TEM O/G Trunk 8-62
BCCOS 4TEMP, I/C Trunk 8-80
Control 26-5 4TEMP, O/G Trunk 8-82
COS 7-30 Make/Break Dial 8-125
Dial Services 15-15 Break-In
Templates 26-3, 26-5 Conference Tone 23-5
Trunk Group 8-23 COS 7-8
Bell Relay Group Call Tone 10-31
NPL 5-40 Key 5-22
Bell/UNA special NPL 5-50
Group 10-25 Tennant Group 7-51
Pickup, NPL 5-32 Tone Plan 6-100
Ring On/Off Timer 6-3 Tone, Timer 6-4
Sizes 4-14 Warning Tone 6-51
Tenant Group 23-10 Warning Tone, Cadence 6-5
UNA activate, COS 7-15 BRI
BID 8-146–8-149 Busy On Trunk, Timer 8-5
DID 8-157 Physical Line Connected 26-20
NPL 5-41 QSIG Trunk Def. 8-19
Bit B Value See also ISDN, TBR
E&M Signalling 8-119 Signaling Channel 26-11
Blind Attendant Sizes 4-10
Keyset Def. 9-46 SPID 26-23
Voice Transmission Controls 19-1
Blocking
Collect Calls, 30TM 8-115 Broker Service
Collect Calls, 8DID 8-92 COS 7-6
Keyset Def. 9-32 Busy
Index
SLT Def. 9-6 Check Out 6-43

Station, By PI, FEAT 18-5 Busy Field Display 16-7
Boss Busy Out
effect of ELA on Boss 4-14 Attendant, COS 7-38
Boss Group By PI, FEAT 18-5
2-Way Hold 6-27 Trunk General Definition 8-13
Call Forward Busy Override 10-20 Busy Tone
Call Forward Dest, NPL 5-27 Active Call Camp Busy, LS/GS Trunk 8-48
Call Forward, COS 7-23 Busy On Trunk, Timer 8-5
Call Waiting Tone 10-20 Station, Duration 9-2
Canned Message 10-20 Tone Plan 6-100
Exclusive Hold, COS 7-14
Index-4
Busy/Idle Timed, periods defined 6-39

Block on all ports 9-52 Call Forward All
Button Programming External,NPL 5-28
By PI 9-76 Call Forward Busy
COS 7-28 All-ATT,NPL 5-29
by station, NPL 5-33 External,NPL 5-28
External-ATT,NPL 5-29
C Call Forward Busy Override
Boss Group 10-20
CA Signalling Port 29-70
Call Forward Busy/No Answer
Calibrated Opening External,NPL 5-29
see Flash Call Forward No Answer
See Hookflash
External,NPL 5-29
Call Charges External-ATT,NPL 5-29
SAU requirement 3-20
Call Forward Timed
Call Duration External,NPL 5-29
Keyset Def. 9-44 External-ATT,NPL 5-29
Timer 6-6
Call Log
Call Duration Limit allocate resources 4-30
by Dial Service, COS 7-6 records per Keyset 9-74
Call Forward records per system 4-30
All, by Attendant 5-27 records per user 4-30
All, by Attendant, COS 7-35 Call Offer
All, By PI 18-4 See Call Waiting
All, by Station 5-25
Call recording
Boss Group, COS 7-23
using Help destination 6-44
Busy or Not Answered by Station 5-25
Busy or Not Answered, by Station,COS 7-9 Call Trace
Busy, by Attendant 5-27 Activation, COS 7-21
Attendant, COS 7-36
Busy, by Attendant,COS 7-35
by ATT, NPL 5-28
Busy, By PI 18-4
by station, NPL 5-28
Busy, by Station 5-25
Keyset Def. 9-62
Busy, by Station,COS 7-9
Cancel While Check Out 6-43 SAU requirement 3-22
DVMS Message 6-47 Sizes 4-27
for Undefined stations,NPL 5-30 SLT Definition 9-14
Max Diversion in Node 28-3 Terminal 17-10
Network 28-3 Call Trace, Print
Network, Max Diversions 28-5 by ATT, NPL 5-28
No Answer, by Attendant 5-27 by station, NPL 5-28
No Answer, by Attendant, COS 7-35 Call Transfer, by rerouting
Index
No Answer, By PI 18-5 In Network 28-3
No Answer, by Station 5-25 Call Waiting
No Answer, by Station,COS 7-9 Answ with HF, KEY 9-39
No Answer, Multi-Appearance 6-39 Answ with HF, SLT 9-11
No Answer, One Step 6-39 System Wide Tone Def. 6-51
No Answer, Timer 9-4 Call Waiting Tone
System Features 6-39 ACD 10-13
Timed, by Attendant 5-36 Boss Group 10-20
Timed, by Attendant,COS 7-35
Called Waiting Tone
Timed, By PI 18-6
Tone Plan 6-101
Timed, by Station 5-36
Timed, by Station,COS 7-9
Index-5
Caller ID Cancellation Code 5-39

on SLT 9-12 Canned Messages 5-33
URC 4-33 COS, ATT 7-37
URC, SAU requirement 3-16 COS, Station 7-5
Caller ID Control Define Name 16-3
Analog Trunks 8-48 Message for Boss Group 10-20
Box # for Analog Trunks 8-48 Message for HUNT Group 10-9
COS 7-30 Message for Public Library 11-3
SAU requirement 3-23 Message for Wait_Q # 27-18
SLTs, SAU requirement 3-24 Override 2nd Line Display 6-26
St#/Account Code 6-13 SAU Requirement 3-20
Terminal Type for CID box 17-22 SAU requirement 3-25
Timeout on LS/GS 8-4 System Def. 6-26
Caller Number CAP 6-43
CAP station 6-33 ACD Hunt 10-5
Calling ID Control Busy Idle Message 6-32
internal calls 6-21 Caller Number 6-33
Keyset Def. 9-60 Coral configuration parameters 6-32
NPL 5-37 identify 3rd party 6-33
Restriction, By PI, FEAT 18-6 Multi-Appearance 6-33
SLT Def 9-12 SAU requirement 3-20
Calls System Features-Station Options 6-32–6-33
O/G Restricted, Attendant COS 7-34 Universal Message Destination 6-32
Simultaneous Wakeup 6-42 CAPS
Simultaneous,Sizes 4-26 key,Directory 5-34
Tenant 7-44 Card Database
Calls, Incoming 30TE 8-125–8-129
Internal/External Priority 6-41 30TM 8-114–8-119
CAMA 4SH/S, 8SH/S, 16SH/S 9-20–9-26
ANI digits 6-14 4T/8T 8-52–8-57
define Trunk Group 8-18 4TEM 8-62–8-63
define Trunk Type 8-12 4TEM Cont. 8-62
Dialing Method 8-25, 26-2 4TEMP 8-67–8-83
DTD Override 8-21 4TWL 8-84
8DID 8-92
Camp-On
8SM Magneto 9-125
Camp Off-Hook, COS 7-12
ALS70 8-138
Camp Off-Hook, special NPL 5-52
DID 8-91, 8-94
COS 7-12
E&M 8-62
DID Trunk Camp-On Hunt Group 6-41
GID 8-151–8-154
E&M Trunk Def. 8-88
Index
Meter (4TMR), 4T/8T 8-54

Immediate Camp 6-41
SLT, SLS 9-20
Networks 28-5
NPL 5-28 Card List 6-60–6-92
Queue Off-hook COS 15-10 0/0 Database Programming 6-61
Queue Off-hook/On-hook 15-3 Card Database Number 6-62
Queue On-hook COS 15-10 Coral FlexiCom 200 6-61
Sizes 4-18 I_Type 6-61
special NPL 5-50 Name 6-80
Station Camp on Hunt Group 6-41 Status Messages 6-63
Timeout after ring for activation 6-3 Sub Version 6-63
Timer 6-2 Version 6-63
Voice Mail 9-40 CCR
Tone Duration 6-6
Index-6
Tone Plan 6-101 COS Assigning 6-43

CCR, Override Keyset Def. 9-36
DID 8-40 SAU requirement 3-20
Trunk Group Def. 8-21 SLT Definition 9-9
Cellular System Features 6-43
SMS protocol 9-53 CID
Wireless 9-122 max on SLT 6-31
Central Office Block See Calling ID Control
30T/T1 8-111 CID, on SLT
30TE DDI 8-130 max digits 6-31
30TE DDO 8-132 Name Support 6-31
30TE NonDDI 8-133 Circuit Assurance
30TM DDO 8-122 System Features, Outgoing Trunks 6-16
30TM DID 8-120 Circuits
4T/8T 8-50 CKT 0-7 for 4T/8T, definition 8-56–8-57
Attendant, NPL 5-26 Circular Search
BID 8-148 ACD/UCD/Hunt 10-5
GID 8-155 Trunk Group 8-20
Central Office Disconnect CISC
30TE DDI 8-130 LAR on/off 15-12
30TE DDO 8-132 QSIG Signalling Connections, Sizes 4-27
30TE NonDDI 8-133 Support 26-21
30TM DDO 8-122 Transit Counters 26-21
30TM DID 8-120 Transit Node,Counter Coding 26-22
4T/8T(LS/GS) 8-50
CLA
4TWL 8-85
Attendant Message Originator 6-44
ALS70 8-142
CoraLINK 27-9
ALS70, DID 8-143
IP address, IPx Office 29-15
ALS70, NONDID 8-144
IPx Office, see MAP
BID 8-147
Disconnect Recall, 30TM 8-115 CLI
GID 8-155 DID/E&M Group 8-39
Trunk Group 8-31
CFM
Keysets,Send Failure Report 9-70 CLID
SAU requirement 3-25 URC, SAU requirement 3-16
Send Report to 17-5 CLID TYPE
SLTs,Send Failure Report 9-18 iDSP card 9-19
Chained Conf CLIS
URC2 4-34 see Card List
Charges Clusters
AOC, Currency Unit 6-11, 14-6 FlexAir SKK Links 6-57
Index
Print by Attendant, NPL 5-35 CNCM

Pulse Meter/Cost Type 6-10 see MAP
Reset and Print by Attendant, NPL 5-35 CNF
SAU requirement 3-20 Group Call 10-27
SMDR Split, COS 7-20 See also Conference
Check In/Out 6-43 CO Block
Check Out 30T/E, DDO Port DB 8-132
Activating When Busy 6-43 30T/E, DID Port DB 8-130
Attendant, COS 7-36 30T/E, Non DDI Port DB 8-133
by Attendant, NPL 5-34 30T/M, DDO Port DB 8-122
By PI, FEAT 18-6 30T/M, DID Port DB 8-120
Index-7
4T/8T Trunk 8-50 Release, NPL 5-36

4TEMP 8-66 Reserve Circuit 23-5
Attendant, COS 7-38 Supervision Recall, Timer 6-4
BID, Port DB 8-148 Tenant Group 23-4
By PI, FEAT 18-5 URC, SAU requirement 3-17
GID, Port DB 8-155 URC2 4-40
NPL 5-26 Conference Modes
T1/30T, Port DB 8-111 URC 4-33
CO Disconnect Configuration
See Central Office Disconnect 4T/8T Card 8-57
CODEC 4T/8T Port 8-46
Media Channels, MRC 4-28 8DID Card 8-91
Collect Call Block ALS70 8-136
Ignore Pulse 8-117 DID port 8-90
Pulse Times 8-116 E&M port 8-87
Collect Call Reject Tone T1 and 30T/X 8-96
See CCR Configuration Error 6-66, 29-22
Collect Calls Confirmation Tone
Blocking, 30TM Card 8-115 Keyset, Tone To Idle 9-27
Blocking, 4T/8T Card 8-55 Station, Duration 9-2
Blocking, 8DID Card 8-92 Tone Plan 6-100
COS 7-20 Congestion Report
Compression Capability Internal Traffic 30-11
Bandwidth conversion 29-82 Consultation Calls
COS def 7-31 COS 7-6
Dial Service 15-17 Continuous Conf
display for FXO Telephony Gateway 29-38 COS 7-6
display for FXS Telephony Gateway 29-36 Reserve CKT 23-5
display for Telephony Gateway Units 29-65 Continuous Conference
IP Keysets 29-34 override COS 7-7
IP Zones BW limit 29-82
Coral Cabinets
MG Module 29-20
Expansion cages Installation 3-3
CONF
Coral FlexiCom 200
See also Conference
Max Ringers 6-21
Conf Message Waiting Lamp 9-26
dynamic ports from MRC, Sizes 4-17 Ports, Music 23-8
Conference Ports, Paging 23-8
(CNF) Resources 4-25 Ring Cadence 9-26
Authorization 3-22 SAU requirement 3-23
Boss Group 6-28
Index
Slots 4 & 5, Base Unit 6-61

Break In/Out Tone Yes/No 23-5 Coral Highest Version
Break-In/Out Tone, Timer 6-4 SAU requirement 3-23
Continous Conference Support 6-28
Coral IPx 500
COS 7-16
Max Ringers, per SLS 6-21
Group Call 10-26
URC2 Card Database 4-33
Group Call Ring duration 6-5
Lock Key, NPL 5-37 Coral Navigator
Lock, COS 7-17 Third Party support 9-47, 9-50
MRC 29-12 Coral System
NPL 5-43 Active Unit, 4GC 4-50
ports, Sizes 4-17 Active Unit, ATS 4-52
Release, COS 7-16 Active Unit, HDC 4-48, 4-49
Index-8
PB-ATS Status 4-52–4-53 System Type 3-2

Power Supply Status 4-53 CPN
Unit Type, 4GC 4-51 ISDN Signaling Channel 26-16
Unit Type, ATS 4-54 CSTS
Coral Teleport Keyset to PC Protocol Type 9-47
IP Zones 29-63 SAU requirement 3-20
Coral View Traffic 17-9 Current Configuration
Terminal 17-9 UGW Physical Capacity 29-21
CoralAIR UGW Required Capacity 29-22
See Wireless CVA
CoraLINK SAU requirement 3-24
Call Services, Sizes 4-18 CVD
CLA Status 27-8 SAU requirement 3-24
Make Call 9-62 CVD_PRO
Music Source 27-17 SAU requirement 3-24
CVT
Sizes 27-15
Wait Queue 27-16
Wait Queue, NPL 5-45
Wait Queue, Sizes 4-18 D
Cord Disconnect DAA
FlexSets 9-75 See Direct Access Abbreviations
COS Data Features
Attendant, Room Status/Canned Messages Sizes, 4IAA 4-16
7-37 Data Fields, Locating 2-8
Dial Services 15-15
Data Line Security
DTD 7-21
Keyset Def. 9-33
Fail, Intercept 6-38
NPL 5-28
Keyset Definition, Primary 9-32
Security 5-28
Keyset Definition, Secondary 9-32
SLT Definition 9-7
Routing 15-9, 15-10
Security 7-19 Data Service
Sizes 4-16 E&M Trunk Def. 8-88
SLT, Primary/Secondary 9-5 Database Controls
Station, Consultation Calls 7-6 Backup 21-4
Stations and Trunks definitions 7-2 Copying Files On Diskette 21-8
Switchover, NPL 5-26 Disk 21-5
Tenant definitions 7-44, 7-48 First Initialization 21-3
Tenant Group Access 7-45 FlexiCom 200 systems 21-12
Tenant Voice Page Access 7-47 Restoring (Loading) From Diskette 21-7
Toll Barrier, Select Pattern 13-2 Saving To Diskette 21-5
Index
Trunk COS, assigning 8-11, 15-15 Date
VFAC 24-8 by Attendant Setting, NPL 5-32
While Check Out 6-43 Setting System Date 25-2
Cost Calculation 6-10 Day Service
Element Definition 15-38, 15-39 Attendant, NPL 5-27
Elements, Sizes 4-21 Automatic, NPL 5-34
Numbering Plan 15-40 Transfer, Attendant, NPL 5-32
Parameters 15-41 DDI Port Database
Country 30TE Definition 8-130
Codes 1-19 DDO
Sizes 4-2 30T/E, Card DB 8-128
Index-9
30T/M, Card DB 8-119 Trunk Seize To Dial, Timer 8-8

T1 and 30T/x Config. 8-95 Undefined, Intercept 6-38
T1/30T, Card DB 8-109 Dial Codes, Entering dial number,
DDO Port Database Private Library 11-10
30TE Definition 8-132 Public Library 11-16
Debugging Dial Filter
Control, at PI terminal 17-4 Dial Services 15-14, 15-16
Diagnostics 22-1 DID/E&M Group 8-37
Diagnostics Destination 17-8 Extended Internal Dial Services 15-13
Select for display 17-6 ISDN 26-2
Stimulus Destination 17-8, 27-6 Offset Filters 8-42
Terminal Destination 17-8 Routing Translators 15-31
Delay Start Trunk Group 8-25
DID 8-90 Dial Lock
DID, Trunk General Def. 8-15 By PI, FEAT 18-4
E&M 8-87 COS 7-11
Destination NPL 5-25
Attendant Message Waiting 6-44 Dial Number
Unattended Station 5-25 identify 3rd party, CAP 6-33
Wakeup Announcer 6-42 in Personal Directory 11-30
Devices for PI 1-4 Public Library 11-7
Diagnostic Dial Pulse
Tests 22-2 Trunk General Definition 8-12
Diagnostics Dial Services
Alarms 22-5 Compression Capability 15-17
Autoguard 6-53 dest UGW IP Address 15-18
Card Status 6-63 Emergency Centers, FAC COS 7-4
Major Relay 6-53 Extended Internal 15-13
RMI Relay 6-53 Keyset Display 15-4
System Features 6-53 LAR Service Timers, Sizes 4-29, 4-31
Terminal Messages 17-8 LAR set 15-12
Tests 22-2 LAR sys pref 15-25
Dial LAR trigger 15-35
1st Digit I/C Trunk 8-4 max LAR fails 15-25
1st Digit Outgoing, Timer 8-5 NPL 5-44
DID/E&M, #_Digits_Expected 8-39 Routing 15-11
Digit "1" for Hookflash 6-21 Sizes 4-21
Enhanced Mode, Keyset 9-64 Dial Tone
Fail, Intercept 6-38 See also Tone Plan
Filter, DID/E&M Groups 8-37 DID 6-19
Index
Filter, Trunk Group 8-25 DTD 6-19

Inter Digit I/C Trunk,Timer 8-4 E&M 6-19
Inter Digit Outgoing Trunk 8-5 Replace with Music Source 7-23
Maximum Digits on Trunk 6-8 Second Dial Tone, Trunk Group 8-21
Pulsing, See Rotary Tone Plan 6-100
SLT (DTMF/Hookflash) 6-31 Trunk 2nd Dial Tone, Timer 8-9
SLT, DTMF/Rotary, Type 9-10 Dial Tone Detectors
Station, 1st Digit Wait Time 9-3 URC 4-33
Station, Feat_Dial 9-3 Dialing Method
Station, Inter Digit Wait Time 9-3 ISDN 26-2
Toll Barrier Analysis 13-3 Trunk Group 8-25
Trunk Group, #_Digits_Expected 8-32
Index-10
DID Directory, Shared

1st Digit Timer 8-4 SLT/Keyset/Wireless Full Name 6-73, 6-79
30 TM Port DB 8-120 DISA
30T/E, Card DB 8-127 1st Digit Timer 8-4
30T/M, Card DB 8-118 Delay, Timer 8-4
8 DID Card DB 8-91 DTMF 6-19
BID 8-157 Inter Digit Timer 8-4
Card Database 8-94 Intercept Calls 6-37
Card List 8-91 New Call Digit 6-19
CCR 8-40 Supervision Recall 6-36
Collect Tone Override 8-40 Supervision Recall, Timer 6-4
Dial Tone 6-19 Sustain Digit 6-19
Filters 8-37 System Features, DISA 6-37
GID 8-157 Tone Plan 6-101
Groups 8-36 Trunk General Definition 8-11
Immediate/Wink, Trunk General Def. 8-15 Disconnect
Immediate/Wink/Delay 8-90 30T/M, Delay To Block, Timer 8-123
Immediate/Wink/SG, 8DID Card 8-91 4T/8T GS Trunk, Timer 8-53
Incomplete Calls 6-35, 6-36 4TEMP, Clear 8-65
Inter Digit Timer 8-4 4TEMP, Clear ACK 8-65
NPL 5-41 4TEMP, Clearing 8-74
Reserved Links 6-109 8DID Card Trunk 8-93
Sizes 4-9 ALS, Delay To Block, Timer 8-145
Test, GID 8-157 BID, Delay To Block, Timers 8-149
Test, NPL 5-36 E&M Cont., Onhook 8-59
Trunk COS 8-11, 15-15 GID, Clear Down/Flash Clear 8-152
Trunk Definition 8-90 Magneto, Min Ring In 9-126
Trunk Timer 8-11 T1/30T, DID 8-110
Type 8-90
Disconnect Recall
Type, 8DID Card 8-91
duration, 30TM 8-121
Outgoing Calls, 30TM 8-115
Digital Trunk
Disconnect Supervision
Configuration, DTDB 8-95
Ground Start, Incoming 8-47
Diagnostic 6-53
Ground Start, Outgoing 8-47
Diagnostics 6-53
Loop Start 8-15, 8-46
Metering Pulses 6-13
Onhook Polarity Reverse 8-47
Sync. 8-98
Trunk Port Database 8-120
Display
DIL
ACD Calls, NPL 5-36
Direct In Line 5-27
AOC-E_Display 9-27
Direct Access Abbreviations (DAA) 2-9 Call Elapsed Time 5-23
Index
Direct In Line Date Mode for System Time 6-25
Attendant, NPL 5-27 Dial Service On Keyset 15-4
Destination, Attendant, COS 7-40 DSP48 6-29
Destination, By PI, FEAT 18-4 Idle DKT 17-2
Dial Services, Destination 15-15 Idle Keyset 9-39
Directory Idle Keyset, COS 7-28
ABC mode, Numbering Plan 5-34 Language, NPL 5-24
CAPS mode,Numbering Plan 5-34 Name To Dial key, NPL 5-23
Hidden Entries 11-27 On/Off Idle Keyset, NPL 5-24
NPL 5-34 Size, Keyset Def. 9-55
SAU requirement 3-24 Waiting Calls 5-24
Index-11
Distinctive Dial Tone URC 4-33

Tone Plan 6-100 URC, SAU requirement 3-16
Divert Call Voice Mail, Keysets 9-40
Key, NPL 5-37 Voice Transmission Controls 19-1
DKT DTR
DPEM 9-66 required ports 4-25
Keyset 9-66 Resources 4-25
System Features 6-29 Duplication 21-20
Voice Transmission Controls 19-1 Load Database 21-8
DKT2320Z Master Side/Slave Side, Table of 21-20
Headsets 9-41 DVMS
DLIS 6-92 # of Messages 23-2
DND Answer Supervision 23-3
see Do Not Disturb COS 7-18
Diagnostic Test 22-4
Do Not Disturb
Maximum DVMS Messages 6-47
ATT Dest, COS 7-41
MLPP BPA Message 6-48
Attendant, COS 7-35
MLPP ICA Message 6-48
MLPP UPA Message 6-48
By PI, FEAT 18-4
MSG Ports, NPL 5-44
by station, NPL 5-25
No Answer Supervision, SAU requirement 3-22
Domain # Port Definition 23-2
for MLPP 7-24 Port With Special Message 23-2
DPEM Ports 23-2
# installed for Keysets/FlexSets 9-66 ports, Sizes 4-17
Allocation 9-66 System Features 6-47–6-48
Sizes 4-15 Tenant Group 23-3
Turret Console 9-68 Voice Transmission Controls 19-1
Drop No Dial Wakeup Announcer 6-42
Attendant, COS 7-39 Dynamic Conference
By PI, FEAT 18-5 NPL 5-49
DTD Dynamic Zone
COS 7-21 Inter Zone Select 29-85
DTMF, Outgoing Trunk 6-9
General Trunk Timers 8-5 E
Resources 4-25
Trunk Group 8-21 E&M
Trunk Timers 8-8 1st Digit Timer 8-4
Voice Transmission Controls 19-1 30T/E, Card DB 8-128
DTDB 30T/M, Card DB 8-118, 8-119
Index
Digital Trunk Config. 8-95 ESPA, Meet-Me Pager 6-14

DTMF Groups 8-36
Dialing 6-8 Immediate/Wink/Delay 8-87
Digits Before Answer, Trunk Group 8-19 Incomplete Calls 6-34
DISA 6-19 Inter Digit Timer 8-4
Disable Supervision 8-32 Intercept Calls 6-37
OCC, Key 5-22 Music on Hold/Transfer 8-89
Outgoing Trunk 6-9 Numbering Plan 5-18
send for Overlap dial 26-17 Seize To Wink, Timer 8-7
SLT Def. 9-10 Sizes 4-9
SLT digit "1" 6-31 T1 and 30T/x Config. 8-95
Tone On/Off Timer 6-5 T1/30T Card Database 8-108, 8-110
Trunk General Definition 8-12 Trunk Definition 8-87
Index-12
Type 8-87 ESN

Voice Transmission Controls 19-1 for NPL 5-45
Wink, Duration 8-7 Wireless Station 9-122
Wink/SG Delay, Timer 8-8 ESPA
E&M Group Pager 6-14
Filters 8-37 Paging, Trunk Group 8-22
E&M Pulsed Exclude Destination
4TEMP 8-65 Key 5-24
E&M Signalling Exclude Source
Bit B Value 8-119 Key 5-24
E911 Exclusive Hold
See Emergency Calls By PI, FEAT 18-6
ECMA Keyset Def. 9-33
Protocol Profile 26-22 NPL 5-32
Transit Node Coding 26-22 SLT Def. 9-6
Edit Executive Privilege
General Numbering Plan 5-39 feature code/index for Freedom (IRSS) 5-27
Names in Personal Directory 11-29 IRSS,COS 7-13
EIS 9-59 NPL 5-27
KSI 9-59 Expensive Route Tone
ELA Timer 6-3
effect of Boss Grp on ELA 4-14 Tone Plan 6-100
NPL 5-31 Expensive Tone
ELA Group 10-38 Dial Services 15-14
# of lines 10-39 Routing COS Definition 15-9
Ring Delay 10-40 Routing Priority 15-26
ELA group Extended DPEM
Sizes 4-14 Turret Console 9-68
Elapsed Time External Calls
Feature Code 5-23 FlexiCall 5-30
Keyset Definition 9-44 External Destination Appearance
Emergency Calls See XDA
Avoid VFAC on RA,COS 7-4 External Ring
Default Second ALI 6-13 Wireless Handsets 9-57
Error messages 22-8
Preempt by Disconnect or Break-In 6-22 F
Public Library def 11-4
Routing Access, COS 7-4 FAC
SAU requirement 3-23 SMDR recording for Network 28-6
Enblock Fax
Index
ISDN 26-2 IP Keyset 9-35

IP SLT 9-8
Encryption
on IP Trunk Port 8-16
IP 29-33
FEAT 18-2
Entries
per User, Shared Directory 4-13 Feature Codes, special
Environmental Noise 9-70 FlexiCall, IRSS 5-53
Feature Timers 6-2–6-6
EOS
30T/E, DID Port DB 8-130 Filter
30T/E, Non DDI Port DB 8-133 DID/E&M Group 8-37
ALS, DID Port DB 8-143 In, Trunk Group 8-25
ALS, Non DID Port DB 8-144 Network, Node Content 28-13
Index-13
Offset Filters 8-42 Third Line Display 9-103

Out, Trunk Group 8-26 Follow Me
Filters COS 7-10
DID/E&M Group 8-37 NPL 5-32
for Incoming ANI on Tk Grp 8-27, 8-29 Follow-Me
Firewall External, NPL 5-30
Keep Alive Interval 29-69 Forced Release
Flash Key, NPL 5-22
See Hookflash Freedom
Flash On Trunk COS 7-22
by Digit "1" 6-21 Executive Privilege, COS 7-13
COS 7-21 Help Destination 6-44
NPL 5-26 Help Requesting feature code 5-54
FlexAir IRSS, SAU requirement 3-25
Alarm button def 9-77 NPL
Alarm Destination 9-53 Passcode, KEY 9-36
Clusters, Master SKK 6-57 Passcode, SLT 9-9
Handset button defs 9-100 Password,COS 7-22
Search Tone 6-52 Special Feature Codes 5-53
SMS, SAU requirement 3-25 Verify Calling Dest as IRSS 6-22
FlexiCall with Executive Privilege, NPL 5-27
Call Forward Station Timer 9-4 See also FlexiCall 5-53
COS 7-22 FSK Tone Generator
Help destination 6-44 iDSP Card 9-19
Help Requesting feature code 5-54 Full Name
NPL 5-29 for Shared Directory 11-27
SAU requirement 3-24 FXO/FXS
Special Feature Codes 5-53 Sizes 4-19
FlexIP Softphone unit name by Entry 29-62
Sizes 4-7
FlexIP SoftPhones G
Dynamic IP Zone allocation 29-30
Gains
FlexSet 120S
DTD Gain, URC2 4-40
control 3rd line display 9-103
DTMF Gain, MRC 29-12
FlexSet 121S DTMF Gain, URC2 4-40
control 3rd line display 9-103 MFR Gain, MRC 29-12
FlexSet 280D-Z URC2 4-33
Headsets 9-41
General Numbering Plan 5-3–??
FlexSet 280S Alphabetical Order 5-7–5-16
Index
control 3rd line display 9-103 Display NPL type per dial# 5-55
FlexSet IP Features 5-21
SAU requirement 3-10 Field/Index Order 5-17–??
FlexSet-IP 280S Special Feature Codes 5-50–5-52
Headsets 9-42 General Trunk Timers 8-3–8-6
FlexSets MLPP Reserve 8-4
120S/280S, Version 3.5, support VM 6-33 Recall 8-3
280S/120S, Headsets 9-41 GID 8-150–8-157
choose idle set 9-73 Card Database 8-151–8-154
Control 3rd line 9-73 DID 8-157
Cord Disconnect Activates Keyset Button 9-75 Numbering Plan 5-18
SAU requirement 3-9 Operator Access 6-19
Index-14
Port Database 8-155–8-156 Hunt Group Ringback 10-9

Timers 8-157 Hunt, NPL 5-19
GMT Keyset Zone Page Member 10-24
Coral Time Zone 25-3 Pickup 10-23
See also Time Zone Pickup COS 7-14
Tenant 11-3, 11-15
Ground Start
Tenant Access COS 7-45
A-Type 8-56
Trunks, definition 8-18
Disconnect Time (4T/8T) 8-53
Proceed To Send Delay 8-5
Ring Pause (4T/8T) 8-53 H
Ring, With 8-57
Handset/Speaker
Trunks 8-46, 8-47
Key 5-24
Group Call
Handsets
Break-In Tone 10-31
Wireless Stations 9-122
Chained Groups 10-35
Conference 10-26 Hard Hold
default dial numbers 5-44 Keyset Def. 9-33
SLT Definition 9-6
Define Operator 10-35
Station Timers 9-3
Define Operator, COS 7-17
Define Operator, NPL 5-30 Hardware Set-Up Connections
Expanded 10-36 On-Site 1-5, 1-6
Group 10-26 Headsets
Group Operator-speech request timer 6-6 Audio Path 9-41
Join in Mute 10-32, 10-33, 10-34, 10-35 DKT230Z 9-41
Lock 10-34 FlexSet 280D-Z 9-41
Max for Simultaneous,Sizes 4-14 FlexSet 280S/120S 9-41
Operator Add Mem, NPL 5-23 NPL 5-25
Operator Release Mem, NPL 5-23 Ring Adjustment 9-30
Operator Release Participant, COS 7-17 Help
Public Library member 10-37 Key, NPL 5-37
Release Grp Call, NPL 5-37 Help destination
Speak Request Ringback duration 6-6 used in FlexiCall/Freedom 6-44
Temp Group Call, NPL 5-38
Help Requesting
Temporary 10-32
feature code for FlexiCall/Freedom calls 5-54
Temporary, COS 7-18
Tenant 10-31 Hidden directory Entries
Terminate, COS 7-17 Display 11-27
Trunk Definitions 8-13, 8-32 Hold
Group Calls Auto Active 6-25
Auto Hold, Keyset Def. 9-45
Release Participant, NPL 5-37
Request to Speak Button Dial # 5-37 Calls_Q,Sizes 4-26 Index
Ring Duration 6-5 COS 7-14
Sizes 4-14 Exclusive, NPL 5-32
Music Source, E&M 8-89
Trunk Def, join in mute 8-32
Music Source, SLT 9-16
Trunk Definitions 8-12
NPL 5-27
Groups SIP Terminal 29-46
Alternate Route 8-34 SIP Trunk 29-57
Bell/UNA 10-25
Hold, Exclusive
Boss 10-18, 10-19, 10-20
COS 7-14
Boss Privacy, COS 7-14
Groups, Keyset
Calls 10-26
Boss 9-33
Destination for Incomplete Calls 12-5
Groups, SLT
Hunt 10-2–10-17
Index-15
Boss 9-6 Announcer 10-15, 10-16

Hold, Hard Announcer Def 9-42
Hard Hold 9-33 Boss 10-19, 10-20
Hard Hold, SLT definition 9-6 Call Delay 6-5
Holiday Canned Message 10-9
Service 12-3 Full Name 10-3
Start/End Time 12-3 Inactive ACD Group 10-6
Timers 12-7 IVR 10-4
Max Calls Wait 10-10
Hookflash
Music Source 10-9
4TEMP, E&M Pulsed 8-67
Naming 10-3
Answer Call Waiting, KEY 9-39
Number of Calls Wait 10-10
Answer Call Waiting, SLT 9-11
Numbering Plan 5-19
Broker, Consultation, 3Way, COS 7-6
Overflow Destination 10-6
by Digit "1" 6-21
Pickup 10-24
E&M Cont. 8-59
Release/Resume, NPL 5-33
E&M, Accept 8-88
Ring/No Answer ACD settings 10-8
for internal dial tone 6-30
Search Groups 10-5
Recall Trunk 6-30
Sizes 4-14
SLT digit "1" DTMF 6-31
Unavailable ACD Group 10-7
SLT, Filter 9-3, 9-26
Voice Mail 10-4
SLT, Hot Immediate stations 6-30
SLT, Relevant 9-14
Hookswitch Flash
I
4SH/S, 8SH/S, 16SH/S Card Database 9-24 I_Type
Station Timers 9-3 Coral FlexiCom 200, Base Unit 6-61
Trunk Timers 8-7
iCMC
Hot Immediate, SLT Stations Keysets 3, Sizes 4-6
internal dial tone by HF 6-30 Multi-Appearance settings 9-37
Hot Lines Voice Mail 6-33
Trunks, Delay 8-13 Idle Display 17-2
Trunks, Immediate 8-13 COS 7-28
Hot Standby Display 6-29
SAU requirement 3-21 Keyset Def. 9-39
Hot Station Delayed On/Off, NPL 5-24
Attendant COS 7-34 iDSP Card Database 9-19
Attendant, NPL 5-31 Inactive Hunt Group
By PI, FEAT 18-4 Settings 10-6
Hot Station Immediate Incoming Only
Attendant Message Waiting 6-44 Attendant, COS 7-38
Attendant, NPL 5-27
Index
By PI, FEAT 18-5

By PI, FEAT 18-4 Trunk General Definition 8-12
Hot Trunk Delayed Incomplete Calls
Attendant, COS 7-39 Destination 12-5
Attendant, NPL 5-26 Supervision Recall 6-36
By PI, FEAT 18-5 System Features 6-34
Hot Trunk Immediate Wakeup Alert 6-42
Attendant, NPL 5-26 Individual Remote System Services
By PI, FEAT 18-5 See Freedom
Hotel/Motel Installation
System Features 6-42 Coral Expansion cages 3-3
Hunt Groups 10-2–10-17 Country, System Type 3-2
ACD 10-5
Index-16
Current 3-2 Sentinel, Cancel Remote Upgrade 29-112

Inter Digit Dial SMDR 14-12
30T/E O/G Trunk 8-125 TFTP server, for UGW Upgrade 29-96
30T/M, O/G Trunk 8-114 UGW dest for Dial Service 15-18
4T/8T O/G Trunk 8-53 IP Bandwidth
4TEM O/G Trunk 8-63 Zone Limit 29-82
4TEMP, O/G Trunk 8-82 IP Connectivity
GID, O/G Trunk 8-153 for PI ports, see MAP
Incoming Trunk, Waiting Time 8-4 IP Endpoints
O/G Trunk 8-139 Coral Time Zone Delta 25-3
Outgoing Trunk, Waiting Time 8-5 COS 7-31
Station, Feat_Dial 9-3
IP Glossary 29-2–29-6
Station, Wait Time 9-3
T1/30T, O/G Trunk 8-108 IP Keyset
Intercept Calls 6-38
EARLY_MEDIA_FOR_BANDWIDTH_
Destination 12-5
CONTROL 29-31
Internal Calls Connected via Sentinel 29-31
FlexiCall 5-29 display type 29-30
Internal Traffic ??–30-15 Ports, Status display 29-32
Control Features and Events 30-6 SIP display type 29-50
Define Reports 30-4 SIP Trunk display type 29-60
Format Reports 30-10 IP Keysets
max days to store, Sizes 4-19 Automatic MAC Registration 29-68
max events, Sizes 4-19 Compression Capability 29-34
SAU Requirement 3-25 DND Whisper Page Def. 9-34
View Report 30-14 Fax 9-35
IP Keyclick 9-42
AES Encryption 29-33 MAC def 29-31
Bandwidth Limit 29-84 Modem 9-35
DES Encryption 29-33 NPL 5-46
Fax on Trunk Port 8-16 SAU requirement 3-10
FXO/FXS Unit name 29-62 Security COS 7-19
Headset 9-42 Security Type 29-33
Keep Alive Interval 29-69 Sizes 4-7
Modem on Trunk Port 8-16 Software Upgrade 29-99–??, 29-100–??,
Network trunk,NPL 5-48 29-102–29-105
QSIG IP Trunks 8-19 Software Upgrade via Dial Num 29-100
System Parameters 29-68–29-78 Software Upgrade via IP Address 29-102
Triple DES Encryption 29-33 Voice Page, NPL 5-47
Zone, Sizes 4-19 Zone Number 29-30
IP Address IP LGS
Index
displayed for FXO 29-38 Connected via Sentinel 29-38
displayed for FXS 29-36 Numbering Plan 5-47
displayed for IP Keyset 29-31 SAU requirement 3-11
for IP Keysets remote upgrade 29-102 Sizes 4-10
for IP Zone 29-85 IP NET
Global for MG Module 29-19 Bandwidth Limit 29-82
IP Keyset, Cancel Remote Upgrade 29-105 Ports, Status display 29-40
Local for MG Module 29-19 QSIG Trunk Def. 8-19
Local for UGW card 29-15, 29-16 SAU requirement 3-11
local, displayed for Teleport units 29-63 Zone for Trunk Def 8-19
Remote IP Keyset Upgrade 29-102
Remote Sentinel Upgrade 29-109
Index-17
IP Network 29-80–29-81 IPx 500X

Protocol Profile 29-81 Expansion cage installation 3-3
QSIG code form 29-81 IPx 800X
IP Ports 29-27–29-39 Expansion Cage Installation 3-3
Display Zone 29-40 IPx Office
LGS, Sizes 4-10 MAP
Network, Sizes 4-11 CUGW
QSIG Net display 29-40 MAP 29-78
SAU requirement 3-10 SAU requirement 3-25
Sentinel, Keyset 29-28
IRSS
Survivability, LAR cause 15-35
See Freedom
Time Zone, Gateways (FXO/FXS) 29-66
Time Zone, Keysets 29-35 ISDN
Adjacent Entity Number 26-18
IP SLT
ALI 26-9
Connected via Sentinel 29-36
Alternate Line ID 9-60
Fax on IP SLT 9-8
BCCOS 7-30, 8-23, 15-15
Modem on IP SLT 9-8
BCCOS Control 26-5
Numbering Plan 5-46
BCCOS Templates 26-3
BRI, PRI, TBR 26-1
Sizes 4-5
Call by Call 15-11
IP Stations Calling ID Control, NPL 5-37
Undefined dest 18-8 Circuit Assurance 6-16
IP Telephony Gateway COS 7-30
Compression Capability 29-65 Enblock/Overlap 26-2
Connected via Sentinel 29-63 In Band Progress 8 message 26-18
define Coral Teleport units 29-62–29-67 Incomplete Calls 6-35, 6-36
FXO/FXS Unit name 29-62 IP Signalling Channel 29-80
LGS, NPL 5-47 Local Ringback 26-16
MAC def 29-63 modify incoming ANI by Type 8-28, 8-30
MAC display 29-38 NSF 15-11, 26-6
Sizes 4-19 Path Replacement 26-22
SLT, NPL 5-46 Protocol AT&T/ETSI 26-15
Status display 29-65 Protocol User/Symmetric 26-15
IP Zone Routing Access 26-2
define Local/Global IP Socket 29-85 Setups, Sizes 4-26
Dynamic Allocation 29-30, 29-45, 29-56 Signaling Channel 26-11
Looped Net 15-18 Sizes 4-10, 4-20
IP Zones SPID 26-23
Coral Teleport FXO 29-38 System Features 26-2
Coral Teleport FXO/FXS 29-63 TEI Assignment 26-20
Index
Display for IP NET Ports 29-40 Trunk Group 8-19

FXS 29-36 Wait Queue, Send Alert 27-18
IP Keyset 29-30 ISDNet
IP NET Trunks in TGDEF 8-19 QSIG 28-1
Max Bandwidth 29-82 ISO
Name for BW limited Zone 29-84 Protocol Profile 26-22
UGW 29-15 Transit Node,Counter Coding 26-22
IPC/SFC IST
Define Announcers 10-3, 10-4 See SLT
Define Hunt Group Type 10-3 iVMF ports
Live Record 10-17 Announcer 17-32
Live record 7-6
Sizes 4-6
Index-18
iVMFipx System Features-Station Options 6-25–6-29

Announcer Keyset Def. 9-42 Timers 9-27
Connection Process 17-32 Voice Mail 9-40
COS definition 7-6 Voice Mail Group 10-4
Define Hunt Group Type 10-3 Voice Transmission Controls 19-1
Define VM Hunt Group 10-4 Zone Page Groups 10-24
PCC def 9-47 Zone Page, Sizes 4-14
Sizes Allocation 4-6 Keysets
Voice Mail Port 9-40 max, Sizes 4-6
IVR SAU requirement 3-8
ACD group 10-4, 10-13 Third Line Control 4-29
Timer, ACD group 10-13 Keysets/FlexSets
Voice Mail, Keysets 9-40 send failure to CFM 9-70
KSI
K Installed 9-59
SLT Type 9-59
KB0 Master Terminal
PI Control Characters 1-15
Keep Alive Interval 29-69
L
Key Programming Lamp
By PI 9-76 Keyset/FlexSet Message 6-45
COS 7-28 LED On/Off Programming Key 5-25
Keyclick Message Lamp and Ring 6-45
Keyset Def. 9-42 SLT, Message Waiting 9-23
Keyset (EKT/VDK/DKT/DST) Language
PEM, Key Programming 9-76 Display, NPL 5-24
Keyset Definition Keyset Def. 9-56
Auto Set Relocate 9-63 PI 6-27
Call Duration 9-44 SAU requirement 3-20
iVMFipx Announcer 9-42 LAR
Music 9-63 Alarm messages 22-9
Keyset Station Block, NPL 5-35
Special Ring 9-15, 9-63 Cost vs Performance on DS 15-25
define Dial Service 15-12
Keyset/FlexSet
Feature Control 18-6
# of Programmable Keys (Buttons) 9-59
max fails on DS 15-25
ACD Protocol Type 6-25
max fails, Trunk Group Def. 8-23
Block Reorder Tone 9-42
Max Service Timers 4-29, 4-31
COS 7-27–7-29
on CISC 15-12
Display 9-55
Enhanced Dial Mode 9-64
System Pref, Cost vs. Performance 8-24
Extension ID 6-25
Index
Triggers, Bandwidth Limit 29-82
Key Programming 9-76
Triggers, Dial Services 15-35
Numbering Plan 5-18
Triggers, Trunk 15-36
Parameter Definitions 9-31–9-75
Trunk Group Def Trigger Set 8-24
PEM, equipped with 9-55
Preference, NPL 5-23 Last Number Redial
Ring Cadence 9-30 Internal and External Numbers 6-21
Routing Group Name Display 15-4 Keyset Def. 9-33
Shortened Display Message 6-24 NPL 5-25
Speaker (Microphone) 9-53 SLT Definition 9-6
Speaker Control 9-45 LDN
Stop Dial Key, NPL 5-23 Routing Access 15-7
Index-19
Least Cost Routing Loop Start/Ground Start

See Routing Access 4T/8T Card DB 8-52
Libraries Caller ID Timer 8-4
assign to Alternate Route 8-34 DISA, definition 8-11
Hunt Group Member 10-17 Incomplete Calls 6-36
Large Public Prefix, NPL 5-38 Intrinsic Multi-Appearance 9-37
max, Sizes 4-12 IP Ports, SAU requirement 3-11
Personal Directory 11-29 IP Ports, Sizes 4-10
Private 11-9 Loop Start, Proceed To Send 8-56
Public 11-2–11-8 Loop Start, Ring Pause (4T/8T) 8-52
Serial 11-18 Numbering Plan 5-18
Shared Directory 11-26 Port DB 8-50
Libraries, Large Public Sizes 4-9
Definition 11-18 System Features 6-34, 6-36
Sizes 4-12 Trunk General Def. 8-46
Trunks 8-46
Libraries, Private
COS 7-21
Keyset Def. 9-32 Loop, Key 5-22
NPL 5-41 LS/GS
Programming, NPL 5-32 See Loop Start/Ground Start
Sizes 4-12
SLT Def. 9-5 M
Libraries, Public
MAC
Def. 11-2
Emergency Calls 11-4 define for IP Keyset 29-31
Numbering Plan 5-20 define for IP Telephony Gateway (FXO/FXS)
Programming, NPL 5-32 29-63
Sizes 4-12 define for MG Module 29-18
display for Telephony Gateway (FXO/FXS)
Libraries, Serial
29-38
Def. 11-18
NPL 5-35 Magneto
Auto Answer 9-4
Line Key Disconnect 6-30
Boss Group, Number Of Lines 10-20 Numbering Plan 5-18
Line, Key 5-22 SLT Sizes 4-5
Live Record Supervision Recall 6-36
COS 7-6 Supervision Recall Timer 6-4
IPC/SFC Port 23 10-17 Voice Transmission Controls 19-1
Load ID Make Call
ACD, NPL 5-35 Keyset Def. 9-62
Sizes 4-18
Index
Locked Out
SLTs 9-18 Make Dial
Login 4T/8T O/G Trunk 8-53
ACD, NPL 5-35 4TEM I/C Trunk 8-62
Primary Login, NPL 5-37 4TEM O/G Trunk 8-62
Look Ahead Routing 4TEMP, I/C Trunk 8-80
See LAR 4TEMP, O/G Trunk 8-82
Loop Make/Break Dial
P Network 15-18 30T/E, DID 8-127
30T/E, E&M 8-128
Loop Originating, Key 5-22
30T/E, O/G Trunk 8-125
Loop Start 30T/M, DID 8-118
Trunks 8-46, 8-47 30T/M, I/C E&M 8-118
Index-20
30T/M, O/G Trunk 8-114 Leaving, COS 7-12

8DID, I/C Trunk 8-92 Leaving, NPL 5-28
ALS, I/C Trunk 8-138 Leaving, special NPL 5-50
ALS, O/G Trunk 8-139 MLPP 6-48
GID, I/C Trunk 8-151 Select Stimulus 17-6, 17-7
GID, O/G Trunk 8-153 Shortened Display 6-24
SLT, Timers 9-25 Sizes Exceeded 29-22
T1/30T, DID 8-110 Stimulus Destination 17-8
T1/30T, I/C E&M 8-109 System Features 6-44–6-49, ??–6-50
T1/30T, O/G Trunk 8-108 UGW Size Exceeded 29-22
Malicious Call Trace Voice Mail on SLT,Tone 6-46
See Call Trace Metering Pulses 6-10, 6-13
MAP 27-2 30T/E, Card DB 8-125
CLA in IPx Office 27-13 30T/M 8-117
define IP addresses 29-78 4T/8T Trunk 8-54
IP address, IPx Office 29-15 ALS Card 8-140
MCLA Charge Before Connect 6-10
CoraLINK 27-9 Enable on 30TM 8-117
GID, Card DB 8-153
Media
Metering Unit Charge 8-31
See also MRC
T1/30T, DDO 8-109
Media Channels T1/30T, Port DB 8-111
MFC
Sizes 4-28
Busy On Trunk, Timer 8-5
Media Negotiation Caller ID 6-13
SIP Terminal 29-46 Caller ID Control 8-32
SIP Trunk 29-57 General Trunk Definitions, in 8-12
Meet-Me Resources 4-25
Pager 6-14 Unique category 7-24
URC 4-33 MFR
URC, SAU requirement 3-17 Minimum Off 8-10
URC2 Conf 4-33 Minimum On 8-10
Memory Voice Transmission Controls 19-1
Directory Entries calculation 4-13 MG Module
Message Waiting See also Media Channels
Attendant COS 7-34 Compression Capability 29-20
by ATT, special NPL 5-52 MAC def 29-18
By PI 18-4 Sizes 4-28
Lamp, Coral FlexiCom 200 9-26 Microphone
NPL 5-26 Keyset Def. 9-53
SLT, Lamp & Ring 9-23
Minor Relay 6-53
Index
SLT, OPX, Lamp Disable 9-14
MLPP
Message Waiting Indication (MWI)
BPA Message, DVMS 6-48
ECMA support 28-5
Call Wait Tone 6-100
Messages D-Channel support 26-17
ATT waiting, Timer 6-3 define Domain# 7-24
Auto Active 6-26 Domain# default 28-7
Cancel, NPL 5-25 ICA Message, DVMS 6-48
CAP, Universal Message Dest 6-32 Network ID# 28-7
Clear upon Ring/Connect 6-45 NPL
Configuration Error 6-66, 29-22 Precedence Level 7-24
Control, at PI terminal 17-5 Preemption Ack timer 6-6
Keyset/FlexSet Lamp 6-45 Preemption COS 7-24
Index-21
Reserve Trunk 8-4 Source retained in Hunt Grp 10-9

Ringback Tone 6-101 Source retained in Wait Q 27-17
Routing Access 15-8 Source Selection, NPL 5-24
SAU Requirement 3-25 Sources 4-45
Stop Conf tone timer 6-6 Voice Transmission Controls 19-1
Stop Conference Tone 6-100 Wakeup Announcer 6-42
Tones, CC0 only 6-98, 6-99 Music on Hold/Transfer
UPA Message, DVMS 6-48 E&M Trunk Def. 8-89
Modem Keyset Def. 9-63
COS 7-16 SLT 9-63
IP Keyset 9-35 Mute
IP SLT 9-8 Group Call Member-Join in Mute 10-32, 10-33,
on IP Trunk Port 8-16 10-34, 10-35
VM Remote Access 17-32 Key 5-24
MRC
Conf CKTs NPL 5-49 N
Conf Switch Delay 29-12
Conference Members,Max 29-12 Name
dynamic conf ports, SIZ 4-17 BCCOS, ISDN 26-3
MAC 29-13 Boss Groups 10-19
resources, PUGW 29-12 CoraLINK, Wait-Queue 27-16
Sizes 4-28 Dial Services 15-11
Mu-Law 6-52 DID Group 8-37
Coding Basic Tones 6-102 DID Trunk 8-37
DSP48 (Short/Full) 6-29
Multi-Appearance
E&M Group 8-37
Call Forward No Answer 6-39
Calls_Q, Sizes 4-26 Extension ID 6-25
CAP 6-33 Group Call 10-30
Keyset 9-60 Hunt Groups 10-3
LS/GS 9-37 ISDN, Signaling Channel 26-14
Muted ring option 9-38 Network Node Content 28-12
Muted Ring, Timer 9-28 NSF, ISDN 26-6
Second Call Display 9-41 Password 17-2
Second Call on Keyset 9-38 Personal Directory 11-29
SIP 9-37 PI Language 6-27
SLT 9-11 Public Libraries 11-2
Room Status 16-3
Multi-Level Precedence and Preemption
Routing Access 15-5
See MLPP
Serial Library 11-14
Multi-Party Conference System Installation 17-2
creator from 3-way 6-28 Trunk Group 8-18
Index
Last Party Release, NPL 5-23

Name Retention
Music Call Forward 6-15
ACD/UCD/Hunt Group 10-9 FlexiCalls 6-16
as Dial Tone, SAU 3-25 Freedom Calls 6-16
CoraLINK 27-17
Name/Number Display
CoraLINK, Wait Queue 27-17
Timer 9-28
COS 7-28
Keyset Def. 9-44 Name/Number display 6-24
On/Off, NPL 5-23 Name/Number, Key 5-23
Page_Q 23-11 Naming Rules
Public Address 23-8 General 2-10
SLT, Hold/Transfer 9-16
Source as Dial Tone 7-23
Index-22
Network Night Service

See also CISC Attendant, NPL 5-27
See also QSIG Automatic, NPL 5-34
ANI 8-20 Automatic/Manual, ATT COS 7-42
Call Forwarding 28-3 Bell/UNA 23-10
Call Services, Sizes 4-18 Day 12-2
Call transfer by rerouting 28-3 Definition 12-5, 12-7
Camp On 28-5 Destination, Attendant, COS 7-40
CISC Counters 26-21 Dial Services, Destination 15-15
Emergency Public Libraries 11-4 Select, ATT COS 7-41
Feature Timers 6-2 Timers 12-2
Forwarding (Net Diversion) 26-21 Transfer, Attendant, NPL 5-32
IP Network,NPL 5-48 Node ID
IP Ports, SAU requirement 3-11 Feature Index Number 5-22
IP Ports, Sizes 4-11 NPID
ISDNet 28-1 ISDN, ALI 26-10
Max CF Diversions 28-5 Routing Access 15-5
MLPP 28-7
NSF
Node Content 28-12
Dial Services 15-11
Node ID, NPL 5-22
ISDN 26-6
Node Number, NPL 5-45
Sizes 4-20
Node Numbering Plan 28-10
Nodes, Sizes 4-20 Number Types
NSF for Dial Service 15-11 for incoming ANI on Trk Grp 8-28, 8-30
Numbering Plan 28-10 Numbering Plan
Path Replacement 28-5 See General Numbering Plan
Path Replacement Timer 6-2 Sizes 4-15
QSIG 8-19
QSIG CISC calls 26-21 O
QSIG Signalling, Sizes 4-27
QSIG, Protocol_ID 26-15 OCC, Key 5-22
Routing Destination Number, Dial Services Offhook
15-13 E&M Cont., Immediate 8-60
SAU requirement 3-21 E&M Cont., Wink/Delay 8-60
Services, Sizes 4-26 Magneto, Min Ring In 9-126
Special Numbering Plan 28-15 Seize 6-3
SPID 26-23 SLT, Timers 9-24
TEI Assignment 26-20 Timeout after ring for feature activation 6-3
VFAC,FAC recorded on SMDR 28-6 Offset Filter
Voice Mail rerouting 28-4 Definitions 8-42
Voice Page 5-52 Dial Services 15-12, 28-13
Night DID/E&M Group 8-39
Index
Cost Calculation 15-39 for Incoming ANI on Tk Grp 8-27, 8-29

Routing Element 15-27 ISDN 26-2
Night 1 Network, Node Content 28-14
Definition 12-5 Routing Translations 15-31
Destination, By PI, FEAT 18-5 Sizes 4-15
General Trunk Definitions 8-14 Trunk Group 8-25
Night 2 Onhook
Definition 12-5 Ack, E&M Cont. 8-59
Destination, By PI, FEAT 18-5 E&M Cont. 8-59
General Trunk Definitions 8-14 SLT, Timers 9-24
Index-23
On-Line Account Code NPL 5-31

enter during call 6-28 SLT, Identification 9-9
Operator Password
Attendant 6-19 PI 17-2
Originating Only SIP Authentication 29-74
Attendant, COS 7-33 SIP Terminal 29-45
Attendant, NPL 5-26 SIP Trunk 29-56
By PI, FEAT 18-5 VFAC 24-4, 24-9
Keyset Def. 9-32 Path Replacement
SLT Def. 9-5 3Way Conf 28-5
Outgoing Only def in Signalling Channel 26-22
By PI, FEAT 18-6 Feature Code for Node ID 5-22
Trunk General Definition 8-13 for Network nodes 28-5
Outgoing Restriction Timers 6-2
Attendant, NPL 5-26 PB-ATS
By PI, FEAT 18-5 Status 4-52
Keyset Def. 9-33 PC Console
Override 8-21 Keyset to ACD 9-49
Outgoing Trunks Keyset to PCC or CAP 9-47
LAR 6-14 PCC 9-47
Overflow destinations Busy Idle Destination 6-32
ACD 10-6 Update COS, SFE Hotel 6-43
Overlap PCM
ISDN 26-2 Coding A-Law/Mu-Law 6-52
send DTMF, PRI 26-17 Digital Trunk 6-52
Links 6-109
P PEM
# installed for EKT/DKT 9-65
P_Type Installed 9-65
Coral FlexiCom 200 (SL), Base Unit 6-61 Key Programming 9-76
Page Keyset/FlexSet Display 9-55
COS 7-16 Sizes 4-15
NPL 5-40 Perm/Temp Portability
Tenant Group 23-8 See Auto Set Relocate
Page/Public Address 23-7 Phone Lock
Page_Q By PI, FEAT 18-4
Calls_Q,Sizes 4-26 Dial Lock, COS 7-11
COS 7-21 NPL 5-25
Music 23-11 PI
Music Sources 23-11
Index
Connections, RMI, 8DRCM/F 1-10

NPL 5-44 Control Commands 1-14
Sizes 4-17 Interface, 8DRCM/F 1-2
Station Timers 9-3 Interface, Remote Connections 1-10
Pager 6-14 Programming Functions 2-7
Trunk Group 8-22 Pickup
Park Bell/UNA, NPL 5-32
Calls_Q, Sizes 4-26 Directed, COS 7-13
COS 7-14 Directed, NPL 5-31
NPL 5-31 Group Members 10-23
Station Timers 9-3 Group, COS 7-14
Passcode Group, NPL 5-31
Keyset, Identification 9-36
Index-24
Pickup Group COS 7-14

Sizes 4-14 Keyset Def. 9-33
PLIS NPL 5-32
Full Name for Shared Directory 11-27 SLT Def. 9-6
Polarity Reverse Programming Button
Answer 8-47 By PI 9-76
Onhook 8-47 COS 7-28
Port Database NPL 5-24
30T/E, DDO 8-132 Protocol Profile 26-22
30T/E, Non DDI 8-133 IP Network 29-81
30TE 8-130, 8-133 Protocol Types
30TM, DDI 8-122 ACD Keysets 6-25
4T/8T Definition 8-50, 8-51 PTS
4TEMP 8-65, 8-65–8-66 PTS Delay, Timer 8-5
ALS70 8-141 Public Address/Page 23-7
BID 8-147
Public Library
GID 8-155, 8-157
Canned Message Display 11-3
Port List 6-68 Dial Number 11-7
by Dial Number 6-74–6-92 Full Name 11-2
by Physical Location 6-69–6-73
PUGW
Digital Port 6-92
MRC resources 29-12
Ports
Pulse Times
max, Sizes 4-4
Collect Call Block 8-116
SAU requirement 3-7
Pulsed E&M
Ports List 26-13
4TEMP 8-65
Power Fail Transfer 8-44
Pulsing
Precedence Level Rotary 6-8
MLPP 7-24
PWDS
Preference Disconnect Supervision, Trunk General Def.
By PI 9-117 8-15
COS 7-29
NPL 5-23
Q
PRI
Busy On Trunk,Timer 8-5 Q.422 Protocol
Diagnostic 6-54 30T/M card 8-115
Intercept Calls 6-37 QOS
QSIG Trunk Def. 8-19 display for UGW 29-19
SAU requirement 3-20 System Definitions 29-71–??, 29-72–29-73
send DTMF, Overlap 26-17 UGW 29-18
Signaling Channel 26-11
QSIG
Index
Sizes 4-10
CISC 26-21
Sync. 8-98 code form, IP Network 29-81
Enable Speaker Status Tone 8-16
Printer IP NET Trunks
Terminal 17-1 SIP
Priority QSIG trunk 8-19
Incoming Calls 6-41 ISDN Card Signaling 26-15
Priority Preemption 11-4 Path Replacement 28-5
Type 6-22 Protocol ID 26-15
Privacy Routing Dest Number, Dial Services 15-13
By PI, FEAT 18-6 Signalling Connections, Sizes Tab 4-27
Index-25
SIP trunks 8-19 Bell/UNA 6-3

Trunk Group 8-19 Boss Group 10-20, 10-21
Trunk Group members 8-33 Coral FlexiCom 200 9-26
Group Call Ring duration 6-5
R Keyset 9-29
Keyset Mute Ring 9-27
R2MFC Magneto
on 30T/M card 8-95 External 9-125
Recall Internal 9-125
After Hard Hold, Duration 9-3 Ring Signal Reject 9-126
After Hold, Duration 9-2 Message Waiting 6-45
After Page_Q, Duration 9-3 Message Waiting Lamp and Ring 9-23
After Park, Duration 9-3 SLT, Incoming Trunk Calls 9-22
Recall Trunk, Timer 8-3 SLT, Internal Station Calls 9-21
Trunk After Hookflash 6-30 Wakeup 6-2
Reconnect Ring Control
30T/E, DDO 8-132 ELA Group 10-41
Redundancy Ring Delay
SAU requirement 3-21 ELA Group 10-40
Relay Ring Level, NPL 5-24
see RMI Ring/No Answer Hunt Group
Release Block Settings 10-8
General Trunk Timers 8-3 Ringback Tone
Release Trunk from local switch 26-16
General Trunk Timers 8-3 Hunt Group 10-9
Reminder Multi-appearance station 9-2
COS 7-11 Station, Duration 9-2
NPL 5-28 Tone Plan 6-100
Snooze Timer 6-2 Ringers 6-103–6-109
Snooze, special NPL 5-51 Maximum Ring 6-20
Remote Access Ringing
DISA 6-19 ALS, LS Port DB 8-142
Remote Connections ALS, Non DID Port DB 8-144
PI Interface 1-10 RMI
Reorder Tone Modem, COS 7-16
Block for Keyset 9-42 Modem, Port Definition 17-11
Block for SLT 8-16, 9-18 Modem, Tenant Group 23-9
Keyset, Tone To Idle 9-27 Modem, Terminal 17-8
Station, Duration 9-2 Page Relay,COS 7-16
Tone Plan 6-100 PI Connections 1-10
Index
Relay, Minor/Major Alarm 6-53

Reserved Trunk
Sizes 4-15
Att., NPL 5-26
By PI, FEAT 18-5 RMI Modem
Resources Port Definition 17-22
Sizes 4-25 Room Status
URC2 4-35 ATT COS 7-37
Attendant COS 7-37
Restricted
by Att., NPL
O/G Call, Attendant COS 7-34
Canned Messages
Ring Cadence
4T/8T Trunk 8-52
by Att, NPL 5-33
by Station, NPL 5-33
ALS Trunk 8-139
Define Name 16-3
Index-26
defining 16-3, 16-7 SDT 8-21

SAU requirement 3-20 Second ALI
Station COS 7-5 Default Def for System 6-13
Terminal 16-8 Second Line Display
Rotary Override 6-26
SLT Def. 9-10 Second Ringback Tone
Trunk General Definition 8-12, 9-10 Tone Plan 6-101
Routing 15-1 Secured IP Calls
Accesses, NPL 5-44 COS 7-31
Accesses, Sizes 4-21
Security
COS 15-3
COS 7-19
COS Definition 15-9, 15-10
Data Line Security 5-28
Dial Services 15-11, 15-14
IP Keysets Module 29-33
Elements, Sizes 4-21
MG Module 29-20
Expensive Tone 15-1
Extended Internal Dial Service 15-13 Seize
Holiday Definition 12-7, 12-8 30T/E, DDO, Fail Seize 8-128
Numbering Plan 15-28, 15-29 30T/E, DID Port DB 8-130
Route Elements 15-25, 15-26, 15-27 30T/E, DID, SZE ACK 8-131
SAU requirement 3-19 30T/E, Non DDI Port DB 8-133
See LCR 30T/M, DDO Fail Seize 8-119
System Definition 15-3 30T/M, DID Port DB 8-120
Translations 15-31 4TEMP, SZE ACK Detection Timers 8-81
Trunk Groups, Definition 15-3 4TEMP, SZE, ACK 8-65
Weekend Definition 12-3, 12-6 4TEMP, Timers 8-79
4TEMP, Wait For SZE ACK 8-73
Routing Access
4TWL 8-84
COS 7-4
8DID Card Trunk 8-93
COS, Emergency Calls 7-4
ALS, DID Port DB 8-143
defined for Directory 6-17
ALS, LS Port DB 8-142
Dial Services 15-11
ALS, Non DID Port DB 8-144
ISDN 26-2
BID, Port DB 8-147
MLPP 15-8
GID, Port DB 8-155
Network, Node Content 28-13
Minimum, 4T/8T Trunk 8-51
Night Service 12-7
Suspect Offhook, General Timer 6-3
Tone 15-3
Suspect, 4T/8T Trunk 8-50
Trunk Group 8-23
Suspect,4TWL 8-84
Routing Destination Number T1/30T, DDO Fail Seize 8-109
Dial Services 15-13 T1/30T, DID 8-110
Routing, Alternate 8-34 T1/30T, Port DB 8-111
RPS Sentinel
Ringers 6-20 connected IP Keysets 29-31
Index
RTP Port Base 29-69 connected IP LGSs 29-38

connected IP SLTs 29-36
S connected telephony gateways 29-63
IP Keyset Port 29-28
SAU Keep Alive Interval 29-69
see Authorization SAU requirement 3-11
Saved Number Sizes 4-7
COS 7-18 Software Upgrade 29-106–??, 29-107–??,
NPL 5-33 29-109–29-112
SDP Zone Selection 29-85
set for SIP stations 7-32
Index-27
Series Call Media Negotiation 29-46

COS 7-19 Status display 29-51
NPL 5-33 SIP Trunk
Shared Directory display type 29-60
Display Entries 11-26 Hold Support 29-57
Entries per User,Sizes 4-13 Media Negotiation 29-57
Full Name 11-27 registration procedure 29-53
Hide Entries 11-27 Status display 29-61
Name from Hunt Group 10-3 Sizes
Name from Public Lib 11-2 CoraLINK 27-15
Name/Number access 11-26 ELA groups 4-14
Shared Resources Service Cards 6-88 Maximum and Default Values 4-4–4-23
Shared Service Card SAU requirement 3-5
iDSP 9-19 Sizes Tab
Shortened Display Messages Maximum and Default Values 4-25–4-32
for Keysets 6-24 SKK
SHOW FlexAir Clusters 6-57
Dipslay NPL type per dial# 5-55 Wireless, SAU requirement 3-22
Signalling SKW
MLPP D-channel 26-17 Sizes 4-27
Silent Monitor Wireless, SAU requirement 3-22
NPL 5-36 SLS
SAU requirement 3-25 Max Ringers for IPx500 6-21
Sizes 4-27 See SLT 9-20
special NPL 5-52 SLT
Split, NPL 5-38 Attendant Identification 9-8
Tennant Group 7-49 Auto Set Relocate 9-15
SIP Block Reorder Tone 8-16, 9-18
Authentication Interval 29-74 Card Database 9-20–9-26
Authentication Password 29-74 CID max digits 6-31
General 29-41 CID Name Support 6-31
guest trunk, default TK GP 29-86 DTMF/Hookflash 6-30
max FOREIN_PROXY 4-19 Hunt Group UCD 10-15
max password length 4-19 IP Ports, SAU requirement 3-11
Multi-Appearance 9-37 max CIDs 6-31
Search Tone 6-52 max, Sizes 4-5
Terminal Password 29-45 NPL 5-18
Terminal, NPL 5-48 receive Caller ID 9-12
Terminal, SAU requirement 3-12 Ringers 6-20
Terminals 29-43–29-52 SAU requirement 3-8
Index
Transparent SDP 7-32 send failure to CFM 9-18

Trunk Password 29-56 Stop Dial, NPL 5-23
Trunk, NPL 5-49 System Features-Station Options 6-30–6-31
Trunk, SAU requirement 3-14 Timers 9-2
Trunk, Sizes 4-11 Voice Mail Group 10-4
Trunks 15-18, 29-52–29-62 Voice Transmission Controls 19-1
Zone Page 10-24 SMDR
SIP phones billing with TBCT 4-16
T207S,T208S, SAU requirement 3-13 Charge Print/Reset, by Attendant COS 7-43
SIP Terminal Display Internal Calls,Sizes 4-27
display type 29-50 Party Name Defined, Sizes 4-26
Hold Support 29-46, 29-47, 29-58 Routing 15-4
Index-28
SMDR Split, COS 7-20 Station Timers 9-2

VFAC 24-9 Station/Attendant Reports
VFAC, FAC recording for Networks 28-6 Call Trace Terminal 17-10
SMDR Backup Stations
SAU requirement 3-19 Auto Active, Message 6-26
Sizes 4-16 Camp-On Hunt Group 6-41
SMS 9-53 Default Boss Groups 10-19
for FlexAir Alarm station dest 9-53 Default Hunt Groups 10-3
Sizes 4-29 Default Pickup Groups 10-23
Snooze Keyset Multi-Appearance 9-37
Ring Timer 6-3 Magneto 9-4, 9-126
special NPL 5-51 Options, System Features 6-20–6-33
Timer 6-2 SLT Numbering Plan 5-18
Soft Keys 4-29 SLT, Type Identification 9-10
Undefined 6-38
Softkey
Wireless 9-122
Keyset Def. 9-53
Statistical Search
SoftKeys
ACD/UCD/Hunt 10-5
choose idle set 9-73
Enable 4-26
Control 3rd line 9-73
Stop Dial
Softkeys
Keyset, NPL 5-23
Idle Set options 9-104
Library 11-7, 11-10, 11-16, 11-23
Programming Idle Sets for third line 9-103
SLT, NPL 5-23
SoftPhone
Stop/Go
8DID Card, Type 8-91
Softset
Summation
Sizes 4-7
Conf mode,URC 4-33
Speaker
System Controls
Key ON/OFF 9-46
COS, Attendant 7-41–7-43
Key, NPL 5-22
Database
Speaker Phone Disk 21-5
Environment 9-70 Database, Basic Controls 21-2
Speaker Tone Routing 15-3
Enable on QSIG 8-16 System Definition
Receive Status for SLT 9-7 Canned Messages 6-26
Receive Status, Keysets 9-34
System Directory
Tone Plan 6-101
Personal 11-29
Speaker/Handset Routing Access Def 6-17
Combined Audio, Keyset Def. 9-54 Searching Names per Keyset 11-29
Key 5-24 Sizes 4-13
Speech Request
Index
System Directory, Shared
Timer for Group Operator 6-6 Name from Boss Group 10-19
SPID System Features
Signalling Channel 26-23 Announcer 6-43
Sizes 4-20 Check Out 6-43
Split Silent Monitor Circuit Assurance 6-16
SAU requirement 3-23 Dial Fail 6-38
Station Blocking DID, Dial Tone 6-19
Att., NPL 5-26 DISA 6-19, 6-37
Station Controls Duplication 21-20
Attendant 7-33–7-37 Incomplete Routing, Illegal or No Answer 6-36
Max Ring 6-20
Index-29
Max Ring on FlexiCom 200 6-21 TEI Assignment

Meet-Me Pager Prefix, European 6-14 ISDN 26-20
Operator Access 6-19 Teleport Units
Undefined Stations 6-38 See IP Telephony Gateway
Voice Page Ring After Transfer 6-26 TEM
System Time Active 9-67
Date Mode-US/Eu 6-25 Installed 9-67
System Type Sizes 4-15
Installation 3-2 Tenant
Sizes 4-2 Bell/UNA 23-10
Conference 23-5
T CoraLINK, Wait Queue 27-17
COS definitions 7-44, 7-45
T1 Dial Service 15-15
Sync. 8-98 DVMS Port 23-3
T207M Group Call 10-31
Display Type 29-30 Group Calls 23-5
NPL 5-46 Large Public Library 11-22
SAU requirement 3-10 Public Library 11-3
Sizes 4-7 RMI Modem 23-9
TEM 9-67 Serial Library 11-15
TEM Sizes 4-15 Voice Page Access, COS 7-47
T207S 29-50, 29-60 Zone Page Group 10-24
SAU requirement 3-13 Tennant Group
T208M Break-In 7-51
Display Type 29-30 Silent Monitor 7-49
NPL 5-46 Terminal 1-4
Sizes 4-7 Alarm Destination 17-8, 27-6
TEM 9-67 APA Setup 9-119
TEM Sizes 4-15 Baud Rate 17-26
T208S 29-50, 29-60 Character Length 17-27
SAU requirement 3-13 CID Setup 17-22
TADIMUX Clear, By Any Terminal 17-31
30T, E&M Logic 8-109 CVT Destination 17-9
30T/E, E&M Logic 8-128 KB0 Setup by ATT, COS 7-42
30T/M, E&M Logic 8-119 KB0 Setup by Attendant, Keyset 17-29
KB0 Setup by Attendant, NPL 5-34
TAP
Message Control 17-4, 17-5
Message Select 17-6, 17-7
TBCT Messages, Diagnostics 17-8
define PRI 26-18
Index
Messages, Stimulus 17-8

enable in Coral 28-8 Parity 17-27
enable without SMDR 28-9 Password Levels, definition 17-2, 17-3
max call length for SMDR 28-9
Reset, By Any Terminal 17-30, 17-32
reserve SMDR 4-16
Room Status Destination 16-8
TBR Setup 17-11–17-27
Diagnostics 6-53 Type 17-26
SAU requirement 3-21 Wakeup Paper, Records per Page 20-3
Signaling Channel 26-11
Terminal Search
Sizes 4-10
ACD/UCD/Hunt 10-5
Sync. 8-98
Trunk Group 8-20
Terminating Only
Attendant, NPL 5-26
Index-30
By PI, FEAT 18-5 IVR 10-13

Keyset Def. 9-32 Keyset 9-27
SLT Def. 9-5 Keyset Ring Cadence 9-29
Text Messages Maximum Flash 8-60
See Canned Message Minimum Flash 8-60
Third Line Control MLPP Preemption Timer for Tone 6-6
Softkeys 4-29 MLPP Stop Conf Tone 6-6
Name/Number display 9-28
Third Line Display
Night Service 12-2, 12-3
control at FlexSets 9-103
Outgoing E&M 8-60, 8-61
Third Party Support Recall 8-3
applicationl 9-47, 9-50 Release Block 8-3
ports 9-64 Route Elements 15-25, 15-26
Tick Tone Routing Queue Offhook 15-3, 15-10
Tone Plan 6-100 Routing Queue Onhook 15-10
Time of Day SLT Card Database 9-20–9-26
Cost Calculation Elements 15-38, 15-39 SLT Make/Break 9-25
Night Service Timers 12-2 Station Interdigit 9-3
Route Elements 15-25, 15-26, 15-27 Time Adjustment 25-5
Timed Forward 6-39 Tone Delay 8-5
Time of Day/Week Trunk Outgoing Interdigit 8-5
Weekend Start/Stop 12-3, 12-6 Trunk Timer Assignment 8-11
Time of Day/Week/Month Trunk Timers 8-7–8-9
Holiday Start/Stop 12-7, 12-8 Weekend Start/Stop 12-3, 12-6
Time Slots 4-47–4-54 Timers Station
General 9-2
Time Units
Keyset 9-27
Programming and Entering 2-6
Keyset Ring Cadence 9-29
Time Zone Magneto 8SM 9-125
Coral Time from GMT 25-3 SLT Card Database 9-20
IP Gateway Ports 29-66
Timers Trunk
IP Keyset Ports 29-35
30T/E - DDI Port Database 8-130
Override by system,IP Keyset Ports 29-34
30T/E - DDO Port Database 8-132
Time/Date 30T/E - Non DDI Port Database 8-133
Adjustment, By PI 25-5 30T/E Card Database 8-125
by Attendant Setting, NPL 5-32 30T/M - DDI Port Database 8-122
Military Time 6-29 30T/M - DDI/DDO/BID Port Database 8-120
Set, ATT COS 7-41 30T/M Card Database 8-108, 8-114
Set, By PI, Time 25-2 30T/M Timers 8-123
Visual Display, idle(EKT only) 9-39 4T/8T Card Database 8-52
Timers 4T/8T LGS Port Database 8-50
All Stations 9-2–9-4 4TEM Card Database 8-62
Index
ALS70, Delay To Block 8-145 4TEMP Card Database 8-67

Answer/Disconnect 8-60 8DID Card Database 8-91
BID Delay To Block, for 30TM 8-149 ALS70 Card Database 8-138
DDI Delay To Block, for 30TM 8-123 ALS70 Port Database 8-142
DDO Delay To Block, for 30TM 8-123 ALS70 Timers 8-145
E&M 8-59 BID Port Database 8-147
E&M, definition 8-87 BID Timers 8-149
Feature Interdigit 9-3 E&M Timers 8-59
GID Test Duration 8-157 GID Card Database 8-151
Holiday 12-3 GID Port Database 8-155
Hunt Group 10-9 GID Timers 8-157
Incoming E&M 8-60
Index-31
MFR, MFC 8-10 Trunk to Trunk 6-8, 6-39

T1 and 30T Card Database 8-108 Voice Page 6-26
Toll Barriers XFER Key, NPL 5-22
COS 7-3 Transit Calls
Define Dial Range 13-3 Disconnect 6-22
Definition 13-2 Trunk Access
Intercept Calls 6-38 COS 7-4
Large Public Override 11-22 Keyset, Outgoing Restriction 9-33
max # of digits,Sizes 4-16 SLT, Outgoing Restriction 9-6
max # of elements, Sizes 4-17 Trunk Busy Out
Public Library, Override 11-3 Attendant, NPL 5-26
Serial Library, Override 11-15
Trunk Controls
Attendant,COS 7-38–7-40
Tone Plan
Trunk Drop No Dial
Basic Tone 6-96
Attendant, NPL 5-27
Basic Tone by Country Code 6-102
Defaults 6-98 Trunk Group
Message Waiting/Voicemail 6-46 Default for Guest SIP trunk 29-86
Number of Segments 6-96 Trunk Group Definition
Special Tone Defaults 6-99 Define incoming ANI 8-26
Tone Definitions 6-100 define LAR trigger set 8-24
Tone Duration,ms 6-97 IP Zone for IP NET trunks 8-19
Tone Name 6-96 LAR max fails 8-23
Tone Number 6-96 LAR Pref 8-24
Tone Type 6-96 Trunk Groups
Tones Alternate Route 8-34
Block Reorder 8-16, 9-18, 9-42 COS 7-4
CoraLINK, Wait Queue 27-17 Dial Services Assignment 15-11
DID, Dial Tone 6-19 Hunt Group Member 10-17
FlexAir Search 6-52 Member Number 8-26
MLPP, CC0 only 6-98, 6-99 Name 8-18
SIP Search 6-52 Numbering Plan 5-19
Tick Tone 6-51 Override Dial Tone Detect (DTD) 8-21
Voice Mail on SLT 6-46 Paging 8-22
Traffic (TAP) QSIG 8-33
See Coral View Traffic Second Dial Tone 8-21
Second Dial Tone (SDT) 8-21
Transfer
Sizes 4-15
Accept Trunk, COS 7-20
skip search when busy 6-18
Auto Hold/Transfer, Keyset Def. 9-45
Station # in Caller ID 8-32
COS, Flash Trunk 7-21
Toll Barrier, Select Trunk 13-2
Index
Hookflash 6-21
Music Source, E&M 8-89 Trunk Incoming Only
Music Source, SLT 9-16 Attendant, NPL 5-26
Pass Account Code for Trunk upon Transfer Trunk Outgoing Only
6-10 Attendant, NPL 5-32
Recall Trunk, Timer 8-3 Trunk Timers
SIP Terminal 29-47 General 8-3–8-6
SIP Trunk 29-58 Supervision Recall 6-4, 6-36
SLT 6-31 Trunk To Trunk Connect
Automatic Unattended 9-9 Transfer 8-23
SMDR Split, COS 7-20 Trunk Group 8-23
Trunk Release After XFER, Timer 8-3 Trunk Type
Trunk to Station 6-8 define Pulse, DTMF, CAMA or mix 8-12
Index-32
Trunk Voice Controls OGR Override 8-21

Voice Transmission Controls 19-1 Outgoing, only 8-13
Trunks Outgoing, System Features 6-8–6-18
30T/T1 Circuit Database 8-111 Port Database, 4T/8T 8-50, 8-51
30T/T1 Port Database 8-111 Power Fail Definition 8-44
30TE Circuit Database 8-133 Reserved Links 6-109
30TE DDI Port Database 8-130 Reserved To 8-14
30TE NonDDI Port Database 8-133 SAU requirement 3-9
30TE Port Database 8-130 Search Type 8-20
30TM Circuit Database 8-120 Silent Monitoring,COS 7-8
30TM DDI Port Database 8-122 Sych with reference clock, 30T/T1 8-108
30TM DDI/DDO/Bi-D Port Database 8-120 Timer Assignment 8-11
4T/8T Port Database 8-50 Trunks, 30T/T1
4TEM Card Database 8-62 Card Database 8-110
4TWL Trunk Card Database 8-84 Incoming 8-109
ALS70 Card Database 8-138 Definition 8-111
Ans/Disc Pulse On xfer, E&M cont only 8-89 Trunks, 30TE
Auto Guard 8-13 Card Database 8-125, 8-126, 8-128
BCCOS, definition 15-15 E&M 8-128
BID 8-147 Definition 8-133
BID Trunk Port Database 8-147 Trunks, 30TM
Busy Out 8-13 Definition 8-120
CCR Override 8-21, 8-40
Trunks, 4TEM
COS 8-11, 15-15
Card Database
Cost Calculation 6-10
Incoming 8-62
Database, GID 8-157
DDO Port Database, 30TE 8-132 Trunks, 8DID
DID 8-11, 8-12, 8-13, 15-15 Card Database Definition 8-93
DID Groups, Naming 8-37 Trunks, DID
Direct In Line 8-14 Card Database Definition 8-94
Direct Inward System Access (DISA) 8-11 See DID, Links Reserved
Drop No Dial 8-13 Trunk Definition 8-90
General Definition 8-11–8-16 Trunks, E&M
General Timers 8-3–8-6 Answer Mandatory 8-88
GID 8-150–8-157 Answer/Disconnect 8-60
GID Port Database 8-155 Card Database
Ground Start 8-46, 8-47 Incoming 8-62
with Ring (C-gs) 8-57 Data Service 8-88
Ground Start/Loop Start Delayed/Immediate/Wink Start 8-87
A-Type 8-56 E&M Timer Assignment 8-87
Hot Delay 8-13 H.Flash Accept 8-88
Hot Immediate 8-13 Incompleted Calls 6-34, 6-36
Index
Incoming, only 8-12 Intercepted Calls 6-37

Incoming, System Features 6-19 Maximum Flash 8-60
Incomplete Calls for Night Service 12-5 Minimum Flash 8-60
LAR trigger 15-36 Timers 8-59
Links Reserved 6-109 Incoming 8-60
Loop Start 8-46, 8-47 Outgoing 8-60, 8-61
B-ls pts 8-56 Trunk Definition 8-87–8-89
max, Sizes 4-9 Voice Mail 8-88
Metering Pulses 6-10 Wink Start 8-8
Night 1 8-14 Wink Time 8-7
Night 2 8-14, 15-15 Wire, 2/4 8-87
Numbering Plan 5-18
Index-33
Trunks, GID 8-150–8-157 Undefined Stations

Incoming 8-151 Call Forward Dest 18-8
Meter 8-153, 8-154 Universal Gateway
Outgoing 8-153 See UGW
Trunks,TWL Upgrading
Trunk Card DB 8-84 from Version 15, expasion cage installation 3-3
Turret Console URC
Extended DPEM 9-68 3Way SAU requirement 3-17
Sizes 4-15 Card Database 4-33–4-39, ??–4-40
TWL CLID SAU requirement 3-16
Card Database 8-84 Conf SAU requirement 3-17
Numbering Plan 5-18 Conf Switch Delay 4-40
Voice Transmission Controls 19-1 Conference Members,Max 4-40
DTMF SAU requirement 3-16
U Max Resources 4-35
Shelf/Slot location 4-37
UCD UTAM
ACD 10-2 Wireless Code 6-59
uCMC
Live record,COS 7-6 V
Sizes 4-6
UGW VFAC
Capacity, Default Config 29-11 Account Code, #Acct Dgts 6-9
Compression Capability 29-20 Change Codes 24-5
Current Configuration 29-13–29-27, ??–29-93 Codes 24-7
Default Configuration 29-9–29-13 Generate Codes 24-3
IP Keysets defined 29-24, 29-26 Password 24-9
IP QSIG Networks defined 29-25 Public ACCT, COS 7-18
LGSs defined 29-25 SAU requirement 3-20
Media, Current Config 29-18 Sizes 4-17
Media, Default Config 29-10 SMDR recording for Networks 28-6
MG Security Type 29-20 VIP Ring
Physical Capacity, Current Config 29-21 Keyset Station 9-15, 9-63
Remote Software Upgrade 29-94–29-98 VM Remote
Required Capacity, Current Config 29-22 iVMFipx card COS Def 7-6
Signalling, Current Config 29-15 VMF card
Signalling, Default Config 29-10 See iVMFipx
SLTs defined 29-24
Voice Mail
Update 29-26
Access via FlexiCall/IRSS 5-54
Unanswered Calls Camp-on 9-40
Index
ACD 10-8 Disable DTMF, Trunks 8-32

Unattended E&M, Answer/Disconnect Pulse 8-89
ATT, Do Not Disturb 9-9 Hunt Group 10-4
Keyset Def. 9-36 iCMC 6-33
NPL 5-25 IPC/SFC Sizes 4-6
SLT Def. 9-9 iVMFipx port 9-40
Station Dest, NPL 5-25 Keyset & SLT, SFE 6-49
Unavailable Hunt Group Live Record, COS 7-6
Settings 10-7 Message Tone on SLT 6-46
Undefined Keysets Remote Access 17-32
send to CFM 9-70 SAU requirement 3-22
SLT Definition 9-16
Index-34
System Default Dest 6-49, 6-50 Fail Alert 6-42

Timer 6-5 Incomplete Alert 6-42
Transfer within a Network 28-4 Printing Paper, Records per Page 20-3
uCMC Sizes 4-6 Report by Attendant, COS 7-43
Voice Mail on E&M Report Sorting, Wakeup Control 20-2
E&M, Coral Mail 8-88 Report, by ATT, NPL 5-35
General Timers 8-6 Reports 20-4
Trunk, E&M 8-88 Ring Timer 6-2
Voice Mail on Keyset 9-40 SAU requirement 3-20
Save While Check Out 6-43
Voice Mail on SLT 9-16
Simultaneous Calls 6-42
Voice Page Snooze Timer 6-2
Auto Answer, NPL 5-23 Snooze, special NPL 5-51
for IP Keysets, NPL 5-47 Terminal Destination 20-3
for Keysets, NPL 5-19
Weekend
Keyset Def. 9-44
Service 12-3
Network 5-52
Timers 12-6
NPL 5-32
On/Off, COS 7-27 Whisper Page
On/Off, NPL 5-23 COS 7-15
Ring After Transfer, System Features 6-26 DND, COS 7-10
special NPL 5-52 DND, Keyset 9-34
Tone Plan 6-100 DND, NPL 5-28
Zone, NPL 5-42 DND, SLT 9-7
DND, Trunk Def. 8-15
Voice Transmission Controls
Music on Hold 6-46
Balancing Network 19-24
NPL 5-28
Feature Control 19-17
Tone Plan 6-101
Gains 19-3, 19-4
Tone Volume 6-51
General Description 19-2
Tone, Timer 6-4
Personal Port Gain, Compensation 19-22,
19-23 Wink
Personal Port Gain, Ports 19-22 8DID Card Trunk, Timers 8-93
PI Gain Decoding, Table of 19-23 8DID Card, Type 8-91
DID 8-90
DID, Trunk General Def. 8-15
W E&M 8-87
Wait Queue See E&M
CoraLINK 27-16–27-18 Wireless
Music Source, retained 27-17 CoralAIR Authorization 3-22
NPL 5-45 ESN 9-122
Sizes 4-18 ESN Code 9-123
Wait_Que# External Ring 9-57
Index
Canned Message Display 27-18 FlexAir Search Tone 6-52
Index# 9-123
Waiting Calls
NPL 5-45
Key 5-24
Sizes 4-9
Wakeup SMS def 9-53
Announcer Destination 6-42 SMS Sizes 4-29
Announcer, SLT Def. 9-10, 9-42
System Features 6-57–6-59
Attendant, COS 7-36
System ID# 6-57
Voice Mail Programming 9-77
by Station, NPL 5-28
Zone Page 10-24
Controls 20-2
Wrap Up Time
COS 7-11
ACD/UCD Groups 5-35
Index-35
X
XDA
Reserve Boss Group 11-3
Xfer, Key 5-22
Y
Yes/No
Entering Values 2-10
Z
Zip Tone
FlexSet 280S/120S 9-41
Zone
for Sentinel 29-85
Zone Page
Group 10-24
Members 10-24
Tone Plan 6-100
Zones
IP, Sizes 4-19
See IP Zones
Index
Index-36
International Headquarters
Tadiran Telecom (TTL) L.P.
23 Hayetzira Street P.O.Box 7607
Petach Tikva 49517 Israel
Tel. +972-3-9262000, Fax. +972-3-9262310
USA Headquarters
Tadiran Telecom, Inc.
265 Executive Dr., Suite 250
Plainview, NY 11803
Tel. +1-516-632-7200, Fax. +1-516-632-7210
http://www.tadirantele.com
C o r a l TM I P x O f f i c e
TM
Coral IPx 500, 800, 3000, 4000
TM
Coral CDRS 200E
TM
Coral FlexiCom 400 (with HDC controller), 5000, 6000
PI (Program Interface) Database Reference Manual

TM
D e p i c t C o r a l Ve r s i o n 1 6 . 0 3 . 0 0
D o c u m e n t E d i t i o n 2 5 M a r- 2 0 1 2

Coral PI 16.03

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Coral PI 16.03

Caricato da

Copyright:

Formati disponibili

Eliezer Katzenstein

Creating a new world of IPportunities

Information supplied by the Manufacturer is believed to be accurate and reliable. However, no

Any representation(s) in this document concerning performance of the Manufacturer's

© Copyright by TADIRAN TELECOM (TTL) L.P., 1993-2012.

Protected by U.S. Patents 6,594,255; 6,598,098; 6,608,895; 6,615,404

25 Mar 2012 Includes Software Version 16.03.00 Tadiran

22 Nov 2010 Includes Software Version 16.01.09 Tadiran

20 January 2010 Includes Software Version 15.85.37 Tadiran

See New Developments Summary

17 January 2008 Includes Software Version 15.68.20 Tadiran

The following hardware was added:

See New Developments Summary (Version

16 March 2007 Includes Software Version 15.5 Tadiran

The following hardware was added:

See New Developments Summary (Version 15.5

12 January 2004 Includes Software Version 14.65 with the Tadiran

The following hardware was added:

11 November 2002 Includes Software Version 14.1 Tadiran

The DX Version was cancelled.

8 September 2000 Includes Software Version 10.38. ECI

See New Developments Summary

5 November 1997 Feature Updates with Wireless Station, SLS, Tadiran

30T/E Cards ......................................................................................................8-124

15 Routing & Cost Calculation

19 Voice Transmission Controls

21 Special System Options-

23 Special Port Facilities

25 Time/Date Set and Adjust

27 MAP, CLA and CoraLINK™

30 Coral Traffic Report (CTR)

The Program Interface (PI) is a detailed, menu-driven, interface system for

Table 1-1: Programming Interface Terminal Communications

Terminal Type DEC VT-100 (Default)

Modem Compatibility 56 Kbps (V.90 ITU-T)

Modem Compatibility Bell 103/212A Answer-300/1200 bps

Parity None (Default), Odd, Even, Mark or Space

Data Word Length 7 or 8 (Default) bits

Stop Bits 1 bit

Format Asynchronous data

manufacturer’s operating manual in order to determine if the selected terminal

Set DIP Switch# 1

Coral IPx Office

IMC-x IMC-x KB0 RESET

KB0: Data Terminal Port: RS232-E DTE Interface.

Option Switches: MEX-IP2 and MCP-IPx2:

Reset Button: Forces the CORAL system to restart.

7-Segment Display: For alarms and diagnostics.

SAU Software Authorization Unit is attached here.

Table 1-2: KB0 RS-232 Interface Pin Functions

Pin #* Signal Mnemonic Function

2 RX (Receive) Receives serial data input fro

3 Tx (Transmit) Sends serial output to

4 DTR Data set is ready to establish a

6 DSR Data set is ready

7 RTS Indicates to data set that UART is

8 CTS Data set is ready to exchange data

Figure 1-2. PI DB9

Figure 1-3. PI DB25

5 - SIGNAL GROUND SIGNAL GROUND - 7

2 - RECEIVE DATA RECEIVE DATA - 3

KB0 PC Async. Serial Port

 When an external modem is connected to KB0, before first initialization,