Comdial Dxp Plus Instructions Manual

							Ground Start Line Board(Impact FX Only)
Software Release 170 adds support for eight-port, ground-start line boards for the Impact FX system.
The product code for this new board type is FXGST-08.
Under BOARD CONFIGURATION/SLOT ASSIGNMENTS or CABINET VIEW, select8 Port
Ground-Startto configure the new board types. Installers can configure each port of these new line
boards as Loop Start, Ground Start, or AUX line types.
Idle System Restore
Prior to Software Release 170, a system performed a system reset after a database restore was complete.
VMMI displayed a warning that the system would reset itself after the database restore.
Beginning with Release 170, a CCB system places all its telephony boards out of service before it begins
a database restore operation. VMMI displays a warning that the system is taking all boards out of service
before it begins the database restore operation and that the system will reset itself after the restore is
complete.
IST Board For Avalon Pull-Cord Support(Impact FX only)
Engineers have designed a new industry-standard telephone (IST) circuit board that interfaces with an
Avalon Assisted Living pull-cord signalling device. The product code for this board is FXISTA–16. The
FXISTA–16 IST board has no audio circuitry since the pull-cord signalling device requires no audio
interface. Software Release 170 provides support for this interface.
Under BOARD CONFIGURATION/SLOT ASSIGNMENTS or CABINET VIEW, installers selectIST
for Avalonto configure the new board type.
Ground Start Line Board(Impact FX Only)–9
Explaining The Software Release Features GCA40–219 
						

							SCbus Interface Support(Impact FX only)
Beginning with Feature Set 15A, Release 170, the software supports the Signal Computer System
Architecture (SCSA) protocol. SCSA is a standard that specifies the signal processing system for
PC-based voice and call processing, and telecom switching. An SCbus is a standard bus for
communications within an SCSA node. The SCbus features an architecture that includes a serial
message path for signalling and control and a 16-wire parallel Time Division Multiplexing (TDM) data
path.
An integral part of the feature is the SCbus interface board. This board connects Computer Telephony
Interface (CTI) applications that reside on one or more SCbus compatible circuit boards in the FXSs
computer portion (for example; network, voice, facsimile, speech recognition, video, and so forth) to
digital station or line ports installed in the FXSs telephony portion through the SCSA protocol.
The conversion of a CTI application from traditional analog ports to digital SCbus ports provides a more
effective and efficient operation.
The SCbus board translates the CTI application’s Application Programming Interface (API), which
requests and carries out basic services performed by the computer and telephony portions of the system,
to an API that the FXS system supports. Typical API requested services include call control services
such as these following items: receive ring events, off- and on-hook, hookflash, dial digits, and so forth.
The SCbus interface board mounts in any universal board slot in telephony portion on an Impact FXS
system and cable connects to the CTI application board that is plugged onto the passive backplane in the
computer portion of the FXS system. The internal cable connection between the SCbus board and the
CTI application board routes the voice-path signalling between the two locations. In addition to this
internal cable, the installation requires external cabling between the systems computer and telephony
portions. The particular external cabling required is dependent upon the CTI application being operated.
An SCbus installation includes the following items:
•SCbus Interface Board (product code FXSCBUS)
•SCbus Application Board or Boards (as needed)
•SCbus Application Software Disk or Disks (as needed)
•Enterprise ToolKit Software (product code ENTRP-SW, release 6A or later)
10 – SCbus Interface Support(Impact FX only)
GCA40–219 Explaining The Software Release Features 
						

							Programming For SCbus Interface Support
VMMI programming for the SCSA protocol includes support for the SCbus interface board and the
SCbus ports.
Board Configuration
Under BOARD CONFIGURATION/SLOT ASSIGNMENTS or BOARD
CONFIGURATION/CABINET VIEW, installers select the desired cabinet slot and program an SCbus
board. This will automatically provision 32 SCbus ports within the CCB database.
PCTB Board Programming
Under BOARD CONFIGURATION/BOARD PROGRAMMING/PCTB BOARDS, installers select the
SCbus board to program and configure the board level programming options for that board.
•Master Clock (Enabled or Disabled)
•Bus Speed (4.096 / 2.048 Mbps).
SCbus Ports
Under BOARD CONFIGURATION/BOARD PROGRAMMING/SC BUS PORTS, installers select the
desired FX-SCB port to configure. Because Release 170 of the CCB supports only Station PCTB ports,
the options under port programming are limited to disabling the port or configuring it as a station port.
Phone Types
While the default value isnoneon the STATIONS/STATION PROGRAMMING/PHONE TYPES,
menu for SCbus ports configured as stations, installers can choose any digital station type valid in the
data base.
OAI Links
Installers can reserve the Scbus port for use only by an OAI application using a specified serial port (or
link). Under BOARD CONFIGURATION/BOARD PROGRAMMING/SC BUS PORTS, installers
program theOAI Linkfeature.
Port Time Slots
Under BOARD CONFIGURATION/BOARD PROGRAMMING/SC BUS PORTS, the system
displays, as read-only data, the time slots used by the port. The values are shown asnonein a new
database, and the system automatically assigns values when the circuit board synchronizes with the
SCbus. These values are dynamic and may change from time to time. The system only displays these
values for information and troubleshooting purposes.
SCbus Interface Support(Impact FX only)–11
Explaining The Software Release Features GCA40–219 
						

							Ring Monitoring
Ring Monitoring, which becomes available with Feature Set 15A, Release 170, gives aboss/secretary
(monitored station/monitoring station) functionality to system stations. With this functionality a
monitoring telephone rings whenever a monitored telephone rings with either an intercom or outside
line call.
Recall ring monitoring is an enhancement to the ring monitoring feature. This enhancement designates
whether any calls that are recalling to the monitored station (that is; transfer recalls, hold recalls, park
recalls) will trigger a ring monitor event at monitoring stations.
Programming For Ring Monitoring
Using VMMI programming, installers can arrange for a monitored station to have a maximum of four
monitoring stations (onebossmonitored by foursecretaries). The system permits one monitoring station
to monitor up to 16 different monitored stations (onesecretarymonitoring up to 16bosses).
Under STATION/STATION PROGRAMMING/RINGING ASSIGNMENTS, installers clickRing
Monitorthen select up to four stations to monitor the ringing of the station being programmed. The
system permits each of these installer-selected stations to serve as a monitoring station for up to 16
different monitored stations.
If installers wish to enhance the ring monitoring feature with a recall feature, they check theRecall Ring
Monitorbox. If enabled, this feature is only in effect for the ring monitoring feature. This recall ring
monitor enhancement is active as the default setting for a station.
Note that the copy station procedure will not copy ring monitor capability except for the recall ring
monitor setting.
Operating A Ring Monitoring Arrangement
Whenever a monitored telephone rings for a call, the associated DSS/BLF on a monitoring station
flashes. The display on a monitoring station matches the display on its monitored station. The Orange
flash indicates to a monitoring phone which of its monitored stations is currently ringing. If more than
one monitored station is ringing, the call with the highest ring priority rings at a monitoring station.
A ring monitor signal appears as an orange flashing light for the DSS/BLF of the monitored station
rather than appear at the monitoring station’s personal hunt list; however, after the monitoring user
answers, the call does appear under the monitoring station’s hunt list. The ring monitoring feature does
not require that a monitoring station have a DSS/BLF for a monitored station; however, if a DSS/BLF is
available, it indicates an audible ring monitor event as detailed above.
Users can forward a ring monitoring event; however, that event only follows theForward Allsetting for
the monitoring station. The station must be idle (that is, not ringing from any other ring monitor events)
when users forward their ring monitored calls. When users cancel call forwarding on forwarded stations,
only any new ring monitor events will ring at the station.
12 – Ring Monitoring
GCA40–219 Explaining The Software Release Features 
						

							Detailing Certain Ring Monitoring Operational Rules
•OAI applications receive normal ringing but stop any ringing for monitoring stations.
•Voice announce calls will not trigger ring monitoring operation.
•Zone paging will not trigger ring-monitoring operation.
•PC Attendant (Total Control) software does not support any ring monitoring functionality.
•Networking System software does not support ring-monitoring across nodes
•A station that is ring monitoring other stations cannot be, in turn, ring monitored.
•A voicemail port cannot be ring monitored.
•There is no delay ring monitor functionality.
•All existing line access/originate privileges apply.
•Installers must not program Direct/Delay Ringing for a monitoring station with same lines as a
monitored station.
•All current ringing priorities remain in effect for ring-monitoring calls (that is; line calls have priority
over intercom calls and recalls).
•If the ring monitoring feature coincides with another direct/delay ring situation then direct/delay
ringing light appearance takes precedence.
A monitoring station does not require a DSS/BLF for a monitored station; however, the system uses that
BLF light (if available) to indicate an audible ring-monitor event.
Station Headset Mode
Software release 170 allows installers to program a station as a headset mode port. When programmed
in this manner, the station can operate in a headset mode with a customer-supplied headset. Users can
activate the headset mode with a HEADSET button (installer-programmed on the telephone) or have he
headset mode as a permanent condition at the station.
Programming The Headset Mode
VMMI supports the headset mode feature with a setting labeledHeadsetunder STATIONS/STATION
PROGRAMMING/OPTIONS 3.
Station Headset Mode – 13
Explaining The Software Release Features GCA40–219 
						

							QSIG Networking Support(Stand Alone Feature)
Software Release 170 adds support for Networking QSIG programming. With QSIG support, Comdial
systems can network with non-Comdial switches that are QSIG compliant. This means that telephones
behind Comdial CCB systems can communicate via intercom with telephones behind non-Comdial
QSIG compliant switches when the systems are combined together in a networking arrangement
Programming For QSIG Networking Support
The VMMI programming adds support for Networking QSIG programming. With a node configured as
a networking node, VMMI allows the installer to also mark the node as supporting the QSIG networking
protocol.
Enabling QSIG
Under SYSTEM/NETWORKING/NETWORK PROPERTIES, installers selectEnabled as QSIG Node
in theNetwork Database Statusfeature to enable the node as a QSIG network node. This option is only
available either if the system or database has QSIG enabled in the software key or if the system type
does not require a software key.
Connected Line ID Restriction
Under SYSTEM/NETWORKING/NETWORK PROPERTIES, installers selectConnected Line Id
Restrictionto enable or disable the presentation of the call identification display. When they check this
control, the system restricts the identification display of all connected calls. With the control not
checked, all calls provide line identification display.
Calling Line ID Restriction
Under SYSTEM/NETWORKING/NETWORK PROPERTIES, installers selectCalling Line Id
Restrictionto enable or disable the presentation of the call identification display during calling. With
the feature checked, the system restricts identification display of all calls. With the feature un-checked,
the system provides line identification for all calls during their calling state.
Display Presentation
Under SYSTEM/NETWORKING/NETWORK PROPERTIES, installers selectDisplay Presentationto
enable/disable the name display information. When checked, all calls will have their name displayed on
the called party’s display. When un-checked, calls will have only the number displayed (according to
the programming of the settings described above).
Node Configuration
When installers configure a database as a QSIG node, VMMI enables the
SYSTEM/NETWORKING/NODE CONFIGURATION. On this dialog, theNode ID,Node Name,and
Enabledcontrols are enabled. VMMI disables theSystem Typecontrol for QSIG nodes.
Network Extension Provisioning
VMMI fully enables the SYSTEM/NETWORKING/EXTENSION PROVISIONING dialog for QSIG
nodes.
14 – QSIG Networking Support(Stand Alone Feature)
GCA40–219 Explaining The Software Release Features 
						

							System Networking Feature Enhancements(Stand Alone Feature)
Basic Impact Attendant Support
Beginning with Software Release 170 basic Impact Attendant operation is available across the network.
The Impact Attendant can request extension information from both the node and hub systems; however
the names of remote extensions are not available. Basic Impact Attendant support includes intercom
calling and provides the following status indications for remote stations:
Out Of Service—the remote station is out of service at the remote site,
Idle—the remote station is not active on a call,
Busy—the remote station is busy on a call.
Dial Zero Extension
It is possible to override the local nodes setting for operator station and, through programming,
substitute a network station as the dial 0 extension. If the installer does not select a network station as
the dial 0 extension, dial 0 calls on a local node will route to that systems operator station if one is
available.
Under SYSTEM/NETWORKING/NETWORK PROPERTIES, installers select theDial Zero Ext…
feature to launch a pop-up dialog. From this dialog, they select the extension that rings when users dials
a zero.
Directed Call Pickup
With call pick up, station users can dial a code plus an intercom number of a ringing or on-hold station
and answer the call from the users station. Software Release 170 extends this feature across the nodes of
the network so that station users of one network node can pick up calls that are ringing at stations
connected to another node on the network.
DSS/BLF Support(Network Station Monitor)
Any station in a networked arrangement can direct station select (DSS) up to 30 remote network
stations. Any station in the network can have busy lamp field (BLF) status light appearance for up to 30
remote stations. This feature is available to Impact Attendant as well as telephone stations.
For each node (but not the hub), VMMI configures two extension lists. TheSendlist, identifies the
extension on that node that users elsewhere on the network can monitor. TheReceivelist identifies
extensions elsewhere on the network that users on that node can monitor. While both theSendand
Receivelists each accept up to 30 entries, the combined total of both lists cannot exceed 30 entries.
An extension must either be on the hub or on aSendlist of another node for the system to accept its
addition to aReceivelist. The hub system automatically monitors theSendlists of all nodes.
System Networking Feature Enhancements(Stand Alone Feature)–15
Explaining The Software Release Features GCA40–219 
						

							Programming For Network DSS/BLF Support
Installers use the SYSTEM/NETWORKING menu to choose theNetwork Station Monitoritem. Under
this heading, they can choose any node (but not the hub) system and configure theSendandReceive
monitor lists. Once the per node limit of 30 remote DSS/BLF appearances is reached, VMMI prevents
the addition of further remote appearances.
Under STATIONS/STATION PROGRAMMING/BUTTON MAPPING, installers select the station to
receive remote DSS/BLF appearance. Under the appropriate button map LKEY, they type the R####
mnemonic, for an extension on the far node (for example, type R2002 if 2002 is a far node extension).
Installers can select theBrowsebutton to view a list of valid far node extensions to choose from.
Installers may button map a remote extension to any telephone in the network. If the remote extension is
not in theReceivelist for the node the telephone resides on, the DSS button functions as a speed dial
button.
Ten Node Networking
Beginning with Software Release 170, Installers can program and configure up to 10 Nodes in addition
to the Hub to comprise a networking system. Previously the limit was 6 network nodes.
Under NETWORKING/NODE CONFIGURATION, NETWORKING/ NETWORK LINKS,
NETWORKING/EXTENSION PROVISIONING/ADD NODE EXTENSIONS, and
NETWORKING/EXTENSION PROVISIONING/REMOVE NODE EXTENSIONS, the number of
selectable nodes is 10 nodes.
Transfer To Voice Mail
With the networking status enabled, the system reserves voice mail port 32 for centralized voice mail on
the hub. This parameter has the following two consequences:
•Installers must not use voice mail port 32 for local node voice mail when networking status is active.
The system ignores any parameters programmed for that port.
•Installers must use port 32 for a Transfer to Voice Mail button whenever that button is planned to
cause a transfer to centralized voice mail to occur.
Programming For The Transfer To Voice Mail Networking Feature
The VMMI programming software allows installers to programXVM32in a station’s button map to
create a button that will transfer to centralized voice mail. Additionally, VMMI will not allow installers
to program voice mail port 32 in a networking database.
If installers use VMMI to translate a networking database to Release 170 or later (from an earlier
revision), or when they enable networking in a Release 170 or later database, VMMI removes any
programming from voice mail port 32. Further, VMMI changes the forwarding location of any voice
mail port that had been previously forwarded to port 32 to the new port 32 forward-to location.
16 – System Networking Feature Enhancements(Stand Alone Feature)
GCA40–219 Explaining The Software Release Features 
						

							VVP Serial Integration
A Versatile Voice Processing (VVP) voice mail operation that has one voice mail system connected to
the hub providing voice mail boxes to both hub and node stations is available with networked systems.
A serial integration feature that enhances VVP operation at the hub system has been available for some
time. Serial integration provides both visual displays and interactive buttons that makes VVP very
effective and easy to use.
Beginning with Software Release 170, serial integration provided by the voice mail system to stations
connected to the hub is also available to stations connected to node systems. When there are voice mail
systems connected to the nodes, every station on a node uses serial integration provided by its local
voice mail system through a voice mail port other than port 32 (specifically ports 1, 2, 3 and so forth in
that order). If a local voice mail system does not exist, the node stations then use the serial integration
provided by the voice mail system connected to the hub.
System Networking Feature Enhancements(Stand Alone Feature)–17
Explaining The Software Release Features GCA40–219 
						

							Programming The Features
Upgrading The DXP Software
To enable VMMI use on the DXP system, you must upgrade the DXP software to at least release 10A
(or to whatever software revision that is now current). Further, to preserve your existing database you
must convert it through the use of the PCMMI database programming software that is at software release
9x. The upgrade to software release 10A or later requires that you also install a new RAM card
(DXRAM–EXPC) as well as the software memory card (DXPSW–DLRC) on the DXP’s central
processor unit. If you need detailed instructions for installing this circuit board and card, refer to the
DXP System Hardware Instructionsin your service literature.
To ensure that you execute the database conversion and software upgrade correctly, you must perform
the following detailed operations in the sequence listed below:
1. Convert The Database
2. Translate The Database
3. Install The Memory Card (and RAM Card if needed)
4. Master Clear The System
5. Connect To The System
6. Restore The Converted Database
Discussions located on the following pages explain each of the above steps in detail.
Upgrading The DXP Software – 19
Programming The Features GCA40–219
3