Lab Siemens Manual
Lab Siemens Manual
Table 3-1 lists the hardware that you can use with Model 40, 50, and 70 systems, shelf allocations, and
district types. This table will assist you in configuring the MAP screen (shown in Figure 3-1 on
page 3-8).
Table 3-1 (Page 1 of 2). Models 40, 50, and 70 Hardware, Shelf Allocations, and District Types
Card
Hardware Shelf District Type Mnemonic
Advanced diagnostics card CNFG, UNIV, or UNIV1 ADC, CRELEC, MUNI, or UNI ADC
Analog telephone interface CNFG, UNIV, or UNIV1 ATI, MUNI, or UNI ATI
(8-channel)
Conference bridge CNFG, UNIV, or UNIV1 CONF, CRELEC, MUNI, or UNI CONF
Data frontend II CNFG, UNIV, or UNIV1 CRELEC, DFEII, MUNI, or UNI DFEII
Direct inward dial trunk (8-channel) CNFG or UNIV1 MUNI or UNI DID8
Dual-tone receiver CNFG, UNIV, or UNIV1 CRELEC, DIGTRK, DTR, MUNI, or DTR
UNI
ISDN primary digital network (IPDN) CNFG, UNIV, or CRELEC, DIGTRK, MUNI, PRI, or UNI IPDN
UNIV1 2
Rotary register CNFG, UNIV, or UNIV1 CRELEC, MUNI, ROTR, or UNI ROTR
Rotary sender CNFG, UNIV, or UNIV1 CRELEC, MUNI, ROTS, or UNI ROTS
Tone sender CNFG, UNIV, or UNIV1 CRELEC, DIGTRK, MUNI, TONE, UNI TONE
4-wire tie trunk interface (4-channel) CNFG or UNIV1 MUNI, TTI, or UNI TTI
Note: Two mnemonics that were not shown in Table 3-1 on page 3-3 are EMPTY and VAC. An EMPTY
slot cannot be filled with a card. (The EMPTY mnemonic is not displayed on the screen.) A VAC
(vacant) slot can be filled with a card but happens to be unoccupied.
CPU Shelf when Model 40 has the 9030 CPU Card: The following are district types that reside on the
CPU shelf when the Model 40 has the 9030 CPU card:
• TASA
• TC
• CPUNR
• SMIOC
• PDC
• FDISK
• HDISK
CPU Shelf when the Model 40 has the 9030A CPU Card: The following are district types that reside on
the CPU shelf when the system has the 9030A CPU card:
• TASA
• TC
• TCTASA
• CPUNR
• IOBUS
• SMIOC
• PDC
• FDISK
• HDISK
The Model 40 nonredundant 9030A CPU system has two possible configurations:
• Both a TC and a TASA card
• A single TCTASA card
UNIV1 Shelf: The following is a district type that resides on the UNIV1 shelf:
• UNI
Figure 8-1 is an example of a universal district for standard analog telephones as it appears in the
MAP database of a Model 10.
HWMAP DISTRICT
PAD TYPE SL TYPE
------- ------ -- ------
DS 01/0218 UNI 18 ATI
DS 01/0219 UNI 19 MW8
DS 01/0220 UNI 20 OPS8
Refer to 2.2, “MAP for Model 10 Systems” on page 2-8 and 3.2, “MAP for Model 40, 50, and 70
Systems” on page 3-8 for further information on the MAP command.
In the command line, <physical address> is the PAD of the single-line extension you want to
configure. This address must exist in the MAP database.
| ACD
| MUSIC DIAL FLASH BSY HR
| PAD REF USE CHNL EXTN TYPE TEST PHONE USAGE%
| --------- ---- --- --- ---- - - - ---
| DF > 0 EXT > > D ? N ?
| CR 01/030603 0 MUS 2 *9008 D N N ?
| Figure 8-2. Sample SLI Screen—Line 1 in a System with Software Release 9005.6.83 and Above
If the PAD entered in the PAD field belongs to an OPS8 or MW8 card, the system automatically
refreshes the first line of the SLI screen, enters N in the TEST field, and then displays a new line of
fields. 1 Figure 8-3 shows the first line on the SLI screen after it has been refreshed.
| Figure 8-3. Sample SLI Screen—Line 1 Refreshed in a System with Software Release 9005.6.83 and Above
The new line of fields (shown in Figure 8-4) permits you to enter extra information needed for the OPS8
and MW8 PADs. This line appears only if the PAD entered belongs to an OPS8 or MW8 card.
| Figure 8-4. Sample SLI Screen—Line 2 (OPS8 and MW8 Only) in a System with Software Release 9005.6.83 and
| Above
1 When the TEST field is N, the TEST OPS and TEST MW8 CLI commands do not run. The system sets this field to N since the
OPS8 and MW8 cards do not have any tests that need to be disabled.
REF Reference number. This is an optional field. Enter up to four digits (0 to 9999) as a
comment referring to information sources such as a definition sheet, a cable
number, a floor number, a jack number, or an office number. This stored number
is displayed on the screen but is not used by the 9751 CBX. The default is 0.
USE Enter one of the following channel names:
CHI This channel is connected to the night chime source. Only one is permitted
per attendant console group. Universal night answer (UNA) trunks must be
configured for this feature to work.
DIC This channel is connected to a dictation device.
EXT This channel is connected to a single-line telephone.
FAX Software Release 9005.6.80 and Above with CorNet-N: This channel is
connected to a facsimile (FAX) device.
MOD This channel is connected to a system modem.
MPL Modem pool extension. Enter this value:
• For all modems in the system
• If you want CDR statistics gathered on any of the modems
• If this extension will be assigned to a data line that will be placed in a
modem pool
This extension number can be dialable.
MUS This channel is connected to the music on hold source. If music is part of
the 9751 CBX, define one music channel for each node.
REC This channel is connected to a recorded announcement device. Only one
modem is permitted (required) per node. (This value applies only if there
is no 9751 CBX monitor or 9751 CBX monitor II.)
The default is EXT.
Note: The customer provides the music, chimes, dictation, and recording
equipment.
| MUSIC CHNL This field indicates the music or recorded-source channel assigned to this
| single-line extension.
| Software Release 9005.6.82 and Below: The system enters 1 in this field and skips
| it.
a Software Release 9005.6.83: Enter the music (or other recorded-source) channel
| assigned to this COS. Enter a value from 1 to 3.
| Enter one of the following:
| 1 Music channel 1.
| 2 Music channel 2. This value applies only if the extension has
| multiple music on hold associated with its COS.
| 3 Music channel 3. This value applies only if the extension has
| multiple music on hold associated with its COS.
| There is no default.
| Ensure that the single-line PADs designated for music-on-hold are
| configured and connected to a music or recording source. Otherwise,
| silence (not music) is heard from the channel.
a Software Release 9005.6.84: Enter a value from 1 to 64.
Configuring the SLI Screen—Line 2 (OPS8 and MW8 Only): The fields shown in Figure 8-4 on page 8-5
are described in the following.
BALANCE NETWORK
This field determines which balance network will be used to match the impedances of
the OPS8 channel and the OPS facility.
Enter one of the following:
1 600 ohms impedance. Enter this value if the telco terminating equipment is
onsite.
2 Compromise network. This value enables most facility impedances to be
matched.
3 Longloop A. This value indicates a special network for long cable lengths.
4 Longloop B. This value indicates an additional special network for long cable
lengths.
Determine the correct value for OPS trunks as follows:
1. Permit this field to default.
2. Run the verify balance channel test (Test BALANCE).
3. Check the value recommended by the channel test.
4. Modify this field′ s value if the value given is not equal to the default.
The default is 2.
ON PREMISE Enter Y to indicate that this extension is on the premises; enter N if it is off the
premises. The default is N.
WINK OFF Enter Y to indicate that this extension should receive a wink-off signal; enter N if it
should not. The default is N.
TERM ONLY Enter Y to indicate that this extension is a terminating-only device; enter N if it is not.
The default is N.
Software Release 9005.1.75 and Above: If you enter Y in this field, ensure that this
extension has TRM COS.
| VRU PROTOCOL
| This field determines the outpulse protocol. Enter NONE or an 8-character
| alphanumeric name.
| Note: This protocol must already be configured in the system through the
| VRU_PROTOCOL command before it is entered in this field.
| Refer to 8.3, “VRU_PROTOCOL” on page 8-9 to configure the T1 OPS VRU protocol.
| Use the XREF_VRU command to list the OPS channels that reference a particular protocol. Refer to
| 12.9, “XREF_VRU” on page 12-88.
|
| COMMAND: CREATE VRU_PROTOCOL FOO
| P P
| A A
| U U
| S ANI/ S ANI/
| NAME E DELIMITER DNIS DELIMITER E DELIMITER DNIS DELIMITER
| -------- - ---------- ---- ---------- - ---------- ---- ----------
| DF> 0 NONE 0 NONE
| CR> FOO 1 1234567890 DNIS # 1 6789ABCD*# ANI #
|
Warning: Use the DELETE EXTEN command carefully. If you delete an extension using this command,
you will remove it from the software and the hardware. If you want to keep the extension in software,
delete the hardware in the SLI database using the DELETE SLI <physical address> command. You
cannot exchange extensions in software. The DELETE EXTEN command does not delete the extension
number from the SYSTEM FORWARDING TARGET fields.
FORWARD ON
SYSTEM FORWARDING BSY RNA DND
EXTN TYPE COS TARGET 1 TARGET 2 TARGET 3 TARGET 4 I E I E I E RINGDOWN
------- --- --- -------- -------- -------- -------- - - - - - - --------
DF > > 0 ------
CR 4020
ACD NAME
- ----------------
DF N
CR
Figure 8-6. Sample EXTEN Screen for Single-Line Attributes in a System with Software Release 9005.1.73 and
Above
Software Release 9005.1.60 and Below: There can be up to two forwarding targets.
Software Release 9005.1.73 and Above: There can be up to four forwarding targets.
2 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
3 Targets 3 and 4 are valid forwarding targets in a system with software Release 9005.1.73 and above.
4 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
| If the system has CorNet-N, this command lists available remote extensions.
| In the command line, when specifying the <range of extensions>, the upper and lower limits must
| have the same first-digit assignment. LIST AVAIL ALL lists the available extensions and data lines.
|
| COMMAND: LIST AVAIL ALL
| SEARCH BEGINNING...
| EXTENSIONS SEARCH
| ==================
| DATALINES SEARCH
| ==================
| Figure 8-7. Sample AVAIL Screen in a System with Software Release 9005.6.82 and Above
To list more than one LEX argument, you must use parentheses to surround the list of LEX arguments
as follows:
LIST LEX (2101 2201)
FORWARD ON
SYSTEM FORWARDING BSY RNA DND
EXTEN TYPE COS TARGET 1 TARGET 2 TARGET 3 TARGET 4 I E I E I E RINGDOWN
------- --- --- -------- -------- -------- -------- - - - - - - --------
DS 2101 EXT 15 5150 -1-1-1
ACD NAME
- ----------------
DS N CARL MARTIN
Figure 8-8. Sample LEX Screen in a System with Software Release 9005.1.73 and Above
FORWARD ON
SYSTEM FORWARDING BSY RNA DND
EXTEN TYPE COS TARGET 1 TARGET 2 TARGET 3 TARGET 4 I E I E I E RINGDOWN
------- --- --- -------- -------- -------- -------- - - - - - - --------
DS 2101 EXT 15 5150 -1-1-1
Figure 8-9. LEX Screen—Line 1 in a System with Software Release 9005.1.73 and Above
5 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
6 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
ACD NAME
- ----------------
DS N CARL MARTIN
Line 7 (no FAC): Figure 8-16 shows an example of Line 7 on the LEX screen of an extension without
any FACs configured.
See Figure 8-17 on page 8-37, Figure 8-18 on page 8-38, and Figure 8-20 on page 8-39 for examples
of the default layouts. On ROLMphone models 120, 240, and 400, there is also a call-waiting LED that
is not associated with any button; on the ROLMphone 300 and 600 series, the call-waiting LED is
associated with the CONNECT button.
Volume control buttons are not configurable. They appear in fixed locations for each model of
ROLMphone telephone.
Each line button must have an LED next to it. Therefore, the three large buttons at the bottom of the
ROLMphone 120, 240, or 400 cannot be assigned features that require LEDs (like line buttons). Use
these buttons for such standard features as hold, flash, connect, or transfer.
A ROLMphone telephone does not have a forwarding LED. The line LED next to the forwarded line
extension number flickers to indicate a forwarded condition.
8.7.3 Speakerphone
The ROLMphone 240 and 400 models, and the ROLMphone 600 series with the speakerphone option,
have a two-way speakerphone. You must configure a speaker (SPKR) button for these ROLMphone
telephones. You do not need to configure a speaker button on a ROLMphone 120 or 312 because they
only have a one-way speaker.
7 System parameter FOUR_DIG_SYS_SPD determines whether there can be 999 or 9999 system speed numbers.
8.8 BUTTON
The BUTTON command permits you to assign two types of feature button tables to a ROLMphone
telephone: default and unique. Default feature button tables, for each ROLMphone telephone model,
are already set up in the 9751 CBX. Unique feature button tables are tables that you can create and
modify to fit customer′s needs. You cannot delete a ROLMphone feature button table.
The easiest and most common way to assign features to ROLMphone buttons is to create a button
table and accept the defaults. The defaults are set for the commonly used features. This permits you
to quickly configure your customer′s ROLMphone telephones.
Unique ROLMphone feature button table: If your customer has telephone users with specialized
telecommunication needs, you have the option of creating unique feature button tables. Refer to
8.8.2.1, “Configuring the BUTTON Screen” on page 8-41 for additional information.
Refer to “FACEPLATE Notes” on page 8-67 for information regarding the extension number and its
appearance on the faceplate.
Software Release 9005.1.75 and Below: In the command line, < xxxx> is one of the following
ROLMphone types:
120
240
400
Software Release 9005.2.77 and Above: In the command line, < xxxx> is one of the following
ROLMphone types:
120
240
312
400
612
612K
624
624K
Refer to 16.21, “BUTTON for ACD” on page 16-47 for sample ROLMphone 600 series telephone feature
button tables.
PHONE
TYPE TABLE #
------- --
120 1
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- --- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
1 REPDL 1
2 FORWD
3 SVRPT
4 CAMP
5 CONF
6 FLASH
7 LINE 1
8 HOLD 9 CNCT 10 XFER
Figure 8-17. Sample Default ROLMphone 120 Feature Button Table Number 1
PHONE
TYPE TABLE #
------- --
240 6
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- --- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
1 FORWD 13 FLASH 18 CONF
2 PICK 14 PARK 19 CAMP
3 BUZZ 15 MSGWT 20 SPKR
4 REPDL 1 16 SYSSP 21 MUTE
5 REPDL 2
6 REPDL 3
7 REPDL 4
a 8 PREV
9 SET
10 SVRPT
11 LINE 1
12 HOLD 17 CNCT 22 XFER
a Figure 8-18. Sample Default ROLMphone 240 Feature Button Table Number 6 in a System with Software Release
a 9005.6.84
PHONE
TYPE TABLE #
------- --
312 2
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- --- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
a 1 PREV
2 SET
3 SVRPT
4 XFER
5 CNCT
6 HOLD
7 CAMP
8 CONF
9 FLASH
10 LINE 1
a Figure 8-19. Sample Default ROLMphone 312 Feature Button Table Number 2 in a System with Software Release
a 9005.6.84
PHONE
TYPE TABLE #
------- --
400 1
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- --- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
a Figure 8-20. Sample Default ROLMphone 400 Feature Button Table Number 1 in a System with Software Release
a 9005.6.84
PHONE
TYPE TABLE #
------- --
612 4
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- ---- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
a 1 PREV
2 SET
3 SVRPT
4 XFER
5 CNCT
6 HOLD
7 CAMP
8 CONF
9 FLASH
10 LINE 1
Figure 8-21. Sample Default ROLMphone 612 Feature Button Table Number in a System with Software Release
9005.6.84
PHONE
TYPE TABLE #
------- --
612K 3
a Figure 8-22. Sample Default ROLMphone 612K Feature Button Table Number 3 in a System with Software
a Release 9005.6.84
PHONE
TYPE TABLE #
------- --
624 1
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- ---- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
1 REPDL 1 11 REPDL 4 17 MSGWT
2 REPDL 2 12 REPDL 5 18 SYSSP
a 3 PREV 13 DND 19 CONF
4 XFER 14 PICK 20 CAMP
5 CNCT 15 FLASH 21 SPKR
6 HOLD 16 PARK 22 MUTE
7 FORWD
8 SET
9 SVRPT
10 LINE 1
a Figure 8-23. Sample Default ROLMphone 624 Feature Button Table Number 1 in a System with Software Release
a 9005.6.84
PHONE
TYPE TABLE #
------- --
624K 10
BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX BTN FEAT INDX
--- ----- ---- --- ----- --- --- ----- --- --- ----- --- --- ----- ---
1 LINE 7 11 REPDL 1 17 REPDL 7 23 REPDL 13 33 FORWD
2 LINE 6 12 REPDL 2 18 REPDL 8 24 REPDL 14 34 CONF
3 LINE 5 13 REPDL 3 19 REPDL 9 25 REPDL 15 35 FLASH
4 XFER 14 REPDL 4 20 REPDL 10 26 DND 36 SYSSP
5 CNCT 15 REPDL 5 21 REPDL 11 27 SET 37 SVRPT
a 6 HOLD 16 REPDL 6 22 PREV 28 STASP 38 MSGWT
7 LINE 4 29 PICK 39 TIME
8 LINE 3 30 PARK 40 AINTC
9 LINE 2 31 INTCM 41 SPKR
10 LINE 1 32 CAMP 42 MUTE
a Figure 8-24. Sample Default ROLMphone 624K Feature Button Table Number 10 in a System with Software
a Release 9005.6.84
8 System parameter FOUR_DIG_SYS_SPD determines whether there can be 999 or 9999 system speed numbers.
After initial configuration the 9751 CBX does not check if you have configured the appropriate number
of lines, the correct number of REPDIAL buttons, or a speaker button. Therefore, it is recommended
that you use the following procedure when in the MODIFY mode to ensure consistency between the
button tables and the ROLMphone database:
• Find a spare button table index not used anywhere in the system by entering the following
command:
LIST BUTTON ALL
• Create or modify this spare button table to the desired configuration.
• Find all the ROLMphone telephones that reference the original button table by entering the
following command:
LIST RPS_ON xxx <table number>
• Call up the RP database screen and modify the button table index number for each ROLMphone
telephone listed. You might also have to modify some of the fields to avoid inconsistencies.
• Use the following command again to verify that no records refer to the previous button table:
LIST RPS_ON xxx <table number>
Refer to 8.8.2.1, “Configuring the BUTTON Screen” on page 8-41 for further information on configuring
ROLMphone feature button tables.
Figure 8-27 is an example of an RLI district as appears in the MAP database of a Model 10.
HWMAP DISTRICT
PAD TYPE SL TYPE
------- ------ -- ------
DS 01/0308 UNI 8 RLI
Refer to 2.2, “MAP for Model 10 Systems” on page 2-8 and 3.2, “MAP for Model 40, 50, and 70
Systems” on page 3-8 for further information on the MAP command.
Each channel assignment accommodates only 1 line extension per ROLMphone 120 and 300, up to 10
line extensions per ROLMphone 612, up to 11 line extensions per ROLMphone 240 and 624, and up to
29 lines extensions per ROLMphone 400, 612K, and 624K.
In the command line, <physical address> can be a PAD, PAD list, or PAD range. The PAD format is
nn/xxyyzz, where:
nn is the node number
xx is the shelf number
yy is the slot number
zz is the channel number
DV S
AM P ACD
RLID T O REF TBL BUZZ KD BSY HR
PAD TYPE A D NO. NO. INTERCM VOICE C R T EXTN 1 R MW BI USAGE%
--------- ------- - --- ---- -- ------- ------- - - ------- - - - -
DF > > ?? 0 ? ?N> YY Y ?
CR 01/010801 RP240E Y RL 0 2 4452 N N 3456 Y Y N 75
CLLD
NAME
_
DF Y
CR N
DATALINE
NUMBER COMMENTS
------- ----------------------
DF ?
CR 3556 ACD AGENT
| V V V V
| S S S S
| #¢S EXTN I R MW BI EXTN I R MW BI EXTN I R MW BI EXTN I R MW BI
| ------ ------- - - - - ------ - - - - ------- - - - - ------- - - - -
| Figure 8-29. Sample RP Screen in a System with Software Release 9005.6.82 and Above
9 RP240E and RP400V2 are valid values in a system with software Release 9005.0.30 and above.
REF NO. Reference number. This is an optional field. Enter up to four digits (0 to 9999) as a
comment referring to information sources such as a definition sheet, a cable number, a
floor number, a jack number, or an office number. This stored number is displayed on
the screen but is not used by the 9751 CBX. The default is 0.
TBL NO. Enter the number of the feature button table for the type of ROLMphone telephone you
are configuring. Valid entries are 1 to 32. The default is 1. You must configure the
feature button table before entering the number in this field.
If the RLID TYPE field is DATA, the system skips this field.
Software Release 9005.2.77 and Above: The system skips this field if CY appears in the
VMOD field.
10 Refer to Chapter 14, “Dialed Number Identification Service” for more information.
Warning: Use the DELETE EXTEN command carefully. If you delete an extension using this command,
you will remove it from the software and the hardware. If you want to keep the extension in software,
delete the hardware in the RP database using the DELETE RP <physical address> command. You cannot
exchange extensions in software. The DELETE EXTEN command does not delete the extension number
from the SYSTEM FORWARDING TARGET fields.
FORWARD ON
SYSTEM FORWARDING BSY RNA DND
EXTN TYPE COS TARGET 1 TARGET 2 TARGET 3 TARGET 4 I E I E I E RINGDOWN
------- --- --- -------- -------- -------- -------- - - - - - - --------
DF > > 0 ------
CR 5101 EXT 50 ------
ACD NAME
- ----------------
DF N
CR Y
Figure 8-30. Sample EXTEN Screen for ROLMphone Telephones in a System with Software Release 9005.1.73
and Above
Software Release 9005.1.60 and Below: There can be up to two forwarding targets.
Software Release 9005.1.73 and Above: There can be up to four forwarding targets.
11 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
12 Targets 3 and 4 are valid forwarding targets in a system with software Release 9005.1.73 and above.
13 Software Release 9005.6.80 and Above with CorNet-N: This can be a remote extension.
To print the faceplates, follow the procedure listed in 8.13.3, “Printing Faceplates Using the RPFP Port
Printer” beginning with step 3, but note the following:
Important Notes: Due to the lack of handshaking between the terminal and the printer, only 1 to 10
faceplates should be printed this way. Since the faceplates are printed by PAD, it is possible to
limit the quantity of faceplates to be printed.
Print faceplates using the printer connected to the RPFP port as follows:
1. Set up the RPFP port using the SIO_PORTS command (refer to Chapter 30, “SMIOC Ports”).
Before printing ROLMphone 300 and 600 series faceplates, ensure that the CRLFO field on the
SIO_PORTS screen contains CRLF (refer to “TERMINAL CHARACTERISTICS Line” on page 30-7 for
more information).
2. Set the correct terminal type based on the type of printer being used.
3. Enter one of the following FACEPLATE commands:
• LIST FACEPLATE <physical address>
• LIST FACEPLATE ALL
When prompted by the faceplate facility (shown in Figure 8-31 on page 8-62), load the appropriate
faceplate forms so that the first line prints in the first rectangular box at the top of the form. Use the
following procedure before starting to print:
1. Load the appropriate faceplate forms into the printer.
2. Feed the forms off-line.
3. Place the forms on the tractor feeds.
In the command line, <physical address> can be a single PAD or a range of PADs.
After you have completed data entry, the faceplate facility begins printing faceplates. Figure 8-32 on
page 8-65 shows an example of a printed faceplate.
Software Releases 9005.1.73, 9005.1.75, and 9005.2.77: If, when the faceplate prints, the extension
number has more than 4 digits, it is converted to the xxx − yyyy format, where xxx − prints on
the first line and yyyy prints on the second line. For example:
xxx-
yyyy
Software Release 9005.2.78 and Above: Set system parameter FP_FIVE_DIGIT_EXT to Y and, when the
faceplate prints, a 5-digit extension number prints on one line. For example:
xyyyy
Com groups in the 9751 CBX are divided into small and large categories:
• Small com groups contain up to 10 members. The members call each other by dialing a 1-digit
access code plus a 1-digit index number. Figure 10-1 on page 10-4 shows an example of the small
com group as displayed in the COM_GROUP screen.
• Large com groups contain up to 100 members. The members call each other by dialing a 1-digit
access code, plus a 2-digit index number. Figure 10-2 on page 10-5 shows an example of a large
com group as displayed in the COM_GROUP screen.
There can be up to 1024 com groups (large and small combined) and up to 6000 com group members
per system.
Software Release 9005.6.80 and Above with CorNet-N: Com groups do not support remote extensions.
Notes:
• Modifying an extension number using the RP or SLI commands has no effect on the com group
unless the extension is moved to a different node. In that case, modify the database for that
group by line feeding through it. This permits the system to recalculate the control node.
• You must access the com group directly to delete an extension number from the group or use
the DELETE EXTEN command to delete the extension from all com groups.
• If when you modify this screen the majority of group members reside on a virtual node, the
control node defaults to 1 to avoid call processing interruptions. When the node is connected
and receiving updates, modify the database by line feeding through it. This permits the system
to recalculate the control node.
COM INDEX
0 1 2 3 4
----- ----- ----- ----- -----
CR 5360 5361 5362
COM INDEX
5 6 7 8 9
----- ----- ----- ----- -----
CR
COM INDEX
1ST 2ND DIGIT
DIG 0 1 2 3 4
- ----- ----- ----- ----- -----
CR 0
CR 1 5110 5111 2102
CR 2 5210 5211 2201
CR 3 5310 5311 2301
CR 4
CR 5
CR 6
CR 7
CR 8
CR 9
COM INDEX
1ST 2ND DIGIT
DIG 5 6 7 8 9
- ----- ----- ----- ----- -----
CR 0
CR 1
CR 2
CR 3
CR 4
CR 5
CR 6
CR 7
CR 8
CR 9
A pick group consists of up to 50 extension numbers. You do not have to place the extensions in any
particular order, but you can assign an extension to only one pick group. You can assign pick group
members to different nodes.
Software Release 9005.6.80 and Above with CorNet-N: Pick groups do not support remote extensions.
Note: Modifying an extension number using the RP or SLI commands has no effect on the pick group.
You must access the pick group directly to delete an extension number from the group or use the
DELETE EXTEN command to delete the extension from all pick groups.
PICK-UP
GROUP # EXTN EXTN EXTN EXTN EXTN
------- ---- ---- ---- ---- ----
CR
A hunt group can consist of up to 48 extensions. An extension can be in more than one hunt group. A
9751 CBX can have a total of 1024 hunt and distribution groups. You can assign hunt group members
to different nodes.
If a user plans to be away from his telephone, he must place his station in do not disturb (DND) mode
or station forward it to another extension in that group. This prevents a caller from getting a
continuous ring-no-answer.
Software Release 9005.6.80 and Above with CorNet-N: Hunt groups do not support remote extensions.
Notes:
• Modifying an extension number using the RP or SLI commands has no effect on the hunt group
unless the extension is moved to a different node. In that case, modify the database for that
group by line feeding through it. This permits the system to recalculate the control node.
• You must access the hunt group directly to delete an extension number from the group or use
the DELETE EXTEN command to delete the extension from all hunt groups.
• If when you modify this screen the majority of group members reside on a virtual node, the
control node defaults to 1 to avoid call processing interruptions. When the node is connected
and receiving updates, modify the database by line feeding through it. This permits the system
to recalculate the control node.
| Figure 10-4. Sample HD_GROUP Configuration Screen for Hunt Groups in a System with Software Release
| 9005.6.81 and Above
You can place an extension in any number of distribution groups and can arrange the extensions in
any order. A 9751 CBX can have a total of 1024 hunt and distribution groups. You can assign
distribution group members to different nodes.
If a user plans to be away from his telephone, he must place his station in DND mode or
station-forward it to another extension in that group. This prevents a caller from getting a continuous
ring-no-answer.
Software Release 9005.6.80 and Above with CorNet-N: Distribution groups do not support remote
extensions.
Notes:
• Modifying an extension number using the RP or SLI commands has no effect on the distribution
group unless the extension is moved to a different node. In that case, modify the database for
that group by line feeding through it. This permits the system to recalculate the control node.
• You must access the distribution group directly to delete an extension number from the group
or use the DELETE EXTEN command to delete the extension from all distribution groups.
• If when you modify this screen the majority of group members reside on a virtual node, the
control node defaults to 1 to avoid call processing interruptions. When the node is connected
and receiving updates, modify the database by line feeding through it. This permits the system
to recalculate the control node.
| Figure 10-5. Sample HD_GROUP Configuration Screen for Distribution Groups in a System with Software Release
| 9005.6.81 and Above
The security group consists of up to eight station extensions assigned to, and accessed by, a pilot
number. When someone calls the pilot number, all idle extensions in the group ring simultaneously.
The 9751 CBX connects the call to the first answering extension. Ringing at other extensions then
stops and they can make and receive calls independently.
| There are up to 50 security groups in a 9751 CBX, with up to 8 members per group.
| Software Release 9005.6.83 and Above: There are up to 350 security groups in a 9751 CBX, with up to
| 8 members per group.
An extension can be in more than one security group. However, an attendant console or an attendant
console group cannot be in a security group. You can assign security group members to different
nodes.
GROUP FWD/BUSY
PILOT# NO. COS C NUMBER
------- ---- --- - ------
DF > > 0 N?
CR 3575 2 0 N
When a CSF access code is activated on the pilot number (to cut off service to all stations, to put all
stations in DND mode, or for any other purpose), the control function applies to all members of that
control group.
For example, this feature is used by hospitals that do not want patients′ telephones ringing after a
certain hour; in an office environment, all the telephones can be put into DND mode, or a secretary can
forward all the telephones in the department when he or she is out to lunch.
Assign a pilot number to the control group. Forwarding the pilot number means forwarding all
member extensions of that control group. A COS number cannot be assigned to a control-group pilot
number for intercom blocking, since a control-group pilot number cannot be directly called.
The 9751 CBX can have a maximum of 50 control groups, with a maximum of 200 members per group.
You can assign control-group members to different nodes.
In the command line, <pilot number extension> can be one of, a list of, or a range of pilot number
extensions.
PILOT#
--------
CR 4445