Comdial Dxp General System Description Release 10a Instructions Manual

							Adding Boards Without Renumbering
When you install additional boards or relocate existing boards after the system is in service, the logical
numbers of the stations or lines on the added board continue from the last assigned logical number. For
example, if your last assigned station number was 116, the next station number will be 117, regardless of
the board’s physical slot. This is not true, however, when you remove and delete a board through
programming. After you remove and delete a board through programming, that board’s logical ports are
available for reassignment. So an added or relocated board would then take the logical port numbers from
the removed board and not from the end of the logical sequence. For example, if your system had 64
stations served by four 16-station station boards and you were to remove a station board that had held
logical stations 1–16, the next station board that you installed would occupy logical station ports 1–16 and
not logical ports 65–80. If you were to remove an 8-port board and replace it with a 16-port board, the
first eight ports on the new board would replace the original eight logical port numbers, and the remaining
eight ports would begin with the last assigned logical port. So using this scenario, the new 16-port board
would have logical ports 1–8 and logical ports 65–72.
Explaining The Software  Release 10A Features IMI89–259
Understanding The Board Configuration Feature – 7 
						

							Explaining Call Forward Outside System
The Call Forward Outside System (CFOS) feature allows the system to forward incoming or transferred
line calls to telephone numbers that are outside the system. The CFOS feature forwards calls over any
available outbound lines or line groups and does not use any conference circuits. Since CFOS involves
outbound calls, those calls are subject to all line access, toll restriction, and automatic route selection
restrictions normally imposed on the users. Any calls that CFOS can not service (no outbound line
available, toll restricted, and so forth), ring the system as normal calls. Note also that CFOS will not
forward calls associated with group intercoms and hunt groups. The CFOS feature is useful for
after-hours forwarding of business calls to an alternate site such as a home or cellular telephone. To help
system managers keep account of CFOS activity, the system marks CFOS calls with anFin the SMDA
records.
Users activate or deactivate CFOS by dialing a feature code, pressing a preprogrammed button or pressing
an interactive button on an LCD speakerphone. Once users activate CFOS, they select the outbound line
or line group in any of the normal line selection methods available to them. They also designate the
forward destination by dialing the number or pressing a speed dial button. (If users do not make a line and
destination choice, the system uses the most recently used selections.) DISA callers can activate and
deactivate CFOS remotely. When DISA callers activate CFOS, they receive several quick tone bursts and
the system awaits any program changes. When they deactivate CFOS, the system returns dial tone. After
they gain access to the system, they can dial the CFOS code, dial an outbound line or line group selection,
and dial the destination number. Once a user activates CFOS, it remains active and neither system resets
nor power outages will deactivate it. After activation, incoming or transferred calls to an idle
CFOS-enabled station forward outside the system to the CFOS destination over the selected outbound
line or line group. CFOS-forwarded calls are subject to the line-to-line disconnect timer action. If
time-out occurs, the system alerts the system operator. He or she can join the call as a conference member.
Before CFOS can occur for calls on incoming lines, programmers must enable those lines for CFOS
capability. Before a CFOS-enabled station can forward a call outside the system, the system must be able
to associate the call receiving line with the station.
·Programmers can take action to associate a CFOS-enabled line with an individual CFOS-enabled
station. With this arrangement, this station is the only one that can forward to an outside destination
for a call received on that line.
·At sites served by DID line blocks, programmers must enable those lines for CFOS capability but
they do not associate the individual lines with specific CFOS-enabled stations. The system uses the
DID translated station extension to check for the station’s CFOS forwarding ability.
·When another station transfers a call to a CFOS-enabled station, the feature does not require a line
association with the CFOS-enabled station for it to forward the transferred call outside the system.
In this case, the system identifies the CFOS-enabled station before it makes the transfer.
·In addition to the line programming action discussed previously, programmers enable CFOS
system-wide with a system programming choice. They then enable the feature in both station class
of service and individual station programming, and may map a CFOS button on the applicable
telephones. When mapping the button, programmers can also select a destination number; however,
any user selected destination number overrides this selection.
IMI89–259 Explaining The Software  Release 10A Features
8 – Explaining Call Forward Outside System 
						

							In summary, to fully enable CFOS for use, programmers must take the following programming actions:
– enable CFOS with system programming,
– enable CFOS in station class of service,
– assign the CFOS class of service to the CFOS stations,
– enable CFOS in individual station programming,
– map a CFOS button on non-LCD telephones,
– select a destination number while mapping the CFOS button,
(this is an optional step—any user selection overrides this selection),
– enable lines for CFOS capability,
– associate a CFOS-enabled line with an individual CFOS-enabled station,
– enable DID line blocks (when used) for CFOS capability.
CAUTION
Comdial has taken reasonable steps in the design of all product features, including CFOS, which protect
against unauthorized or fraudulent access to, or use of, a system, or which protect against unauthorized,
fraudulent or unaccounted-for access to, or use of, long distance lines. However, no system is entirely
invulnerable or immune from unauthorized or fraudulent access or use, or unaccounted-for access or use,
and therefore Comdial disclaims any and all liability, and makes no warranty, express or implied, relating
to unauthorized or fraudulent access or use, or unaccounted-for access or use.
NOTES:(1) CFOS will not work on loop start lines without disconnect supervision.
(2) Calls forwarded through CFOS may experience lower audio levels due to
the normal line resistance of CO lines. Low audio level is usually only noticeable
on long line loops. If signal loss is a problem at a particular site, the installer may
need to add a line amplifier (repeater) in the lines.
Explaining The Software  Release 10A Features IMI89–259
Explaining Call Forward Outside System – 9 
						

							Supporting the E1 Line Board
Beginning with software release 10A, the DXP supports the use of the DXPE1–nnn line board for
international applications. The E1 board provides 30 channels of voice transmissions over a single,
four-wire, 120 ohm cable or over two 75 ohm coaxial cables using multiplexing techniques. The DXP
accepts up to six DXPE1–nnn line boards in specified board slot locations—three in the main cabinet and
three in the expansion cabinet.
Different nations require different system parameters to enable E1 activation and operation; therefore,
Comdial supports each international application with a unique publication that provides complete
technical details for the E1 feature when used in a particular nation.
IMI89–259 Explaining The Software  Release 10A Features
10 – Supporting the E1 Line Board 
						

							Understanding Station Hunting
Station hunting is available to systems with a software revision of 10A and later. Station hunting provides
a means of routing both intercom and outside calls through an installer-determined grouping of stations.
This call routing continues to a designated overflow location in case of no answer or if all stations in the
hunt group are busy. Station hunting works equally well with intercom, standard central office (CO)
lines, direct inward dialing (DID/DNIS) lines, direct inward system access (DISA) lines, and E&M tie
lines.
For station hunting purposes, stations are considered busy under the following conditions:
·when they are currently connected with a call (internal or external),
·when they have an incoming call currently ringing,
·when they have a call on hold, in DND, call forwarded, out of service, or being intercepted by an
OAI application.
The installer can enable default call forwarding for a hunt group station. This feature allows the system to
forward the non-hunt group routed calls that a station receives. Calls routed to a station by the station
hunting feature ignore the default call forwarding settings. The installer can assign all types and any
number of lines to ring at a hunt group. He or she can assign the lines as direct, delayed, day 1, day 2, or
night ringing lines.
To configure station hunting, you program the following parameters:
Options:Programs the attributes, hunting type, and timers for the hunt group.
Member List:Programs the list of stations within a hunt group. This parameter shows the member
stations in their assigned hunting order and allows stations to be added, deleted or inserted at any point in
the list.
Delete:Deletes the selected hunt group from the system and frees its used resources.
CAUTION
Before you edit a member list for a hunt group, you must set the group’s hunt type to NONE; however,
before you view a hunt group’s member list, you must select a hunt type other than NONE.
Further, before you delete a hunt group, be sure that there are no un-answered calls ringing in the group
(that is, the hunt group must be idle). If the settings are not correct for either of these editing operations,
the system will not allow the operation to take place and will display messages as to the reason.
Explaining The Software  Release 10A Features IMI89–259
Understanding Station Hunting – 11 
						

							Hunt Group Attributes
Pilot Extension: This is the extension number that callers dial to call or route calls to this hunt group.
The pilot extension number is similar to a personal intercom number, or extension number, and follows
the same numbering plan restrictions. When station hunting is used with DID/DNIS, the pilot extension is
the extension number assigned in the DID/DNIS translation table. When station hunting is used with
DISA, the pilot extension can be the extension number assigned to the single digit translation for the
digital voice announce (DVA) message associated with the DISA line.
Name:The hunt group’s name is the seven character alphanumeric name of this group that is used for
LCD display and reference.
Full Name:The hunt group’s full name is the 20 alphanumeric character name of the group that is used
by OAI applications. (Future development will support OAI access and control of station hunting.)
Direct Ring Lines:The list of lines that directly ring at this hunt group when the system is not in the
night mode of operation. This list can contain any lines in the system.
Delayed Ring Lines: The list of lines that delay ring on this hunt group. This list can contain any lines in
the system.
Day 1, Day 2, Night Ring Lines:The lists of lines that can ring this hunt group during these programmed
times. These lists can contain any lines in the system.
Member Stations: The list of stations that are members of this hunt group. This list can contain all
stations in the system but is limited to personal intercom numbers only.
Overflow Destination: The overflow destination is a station intercom number, a group intercom number,
a voice mail number, or another hunt group pilot extension where the system routes unserviced hunt
group calls.
Queue Ringing Calls: With the queue ringing calls feature disabled and if all stations in the hunt group
are busy, the system immediately routes hunt group calls to the overflow destination. With the queue
ringing calls enabled, in the case of no answer or if all stations in the hunt group are busy, hunt group
calls wait in a queue to be answered until an overflow timer times out then route to the overflow
destination.
DID/DNIS Display for Station Hunt Groups: Beginning with software release 10A, if station hunt
group members need to differentiate incoming DID/DNIS calls, programmers can take  action to cause a
different display to occur. With this feature active, the display shows the incoming digits or translated
name instead of the station hunting name.
Multiple Call Handling For Station Hunt Groups:Beginning with software release 10A,
programmers can arrange the system to allow member stations within station hunt groups to handle
multiple calls. With this feature turned off, the system considers any hunt group member stations that
have calls on hold or in a park orbit to be busy to the station hunting call delivery process even though
these stations are otherwise idle. With this feature turned on, the system considers any hunt group
member stations that have calls on hold or in a park orbit to be available for additional call deliveries as
long as these stations have ring positions available (that is: an available personal intercom number, hunt
list and so forth).
IMI89–259 Explaining The Software  Release 10A Features
12 – Understanding Station Hunting 
						

							Types Of Hunting
Terminal Hunting:Terminal station hunting always delivers a call to the first idle station programmed
in the hunt group. If the station does not answer within a programmed amount of time (programmed as
the Call Advance Timer), the system delivers the call to the next sequential idle station programmed in
the hunt group. The system makes no attempt to balance the distribution of incoming calls as this is a
linear search through the programmed list. The search starts at the beginning of the list for each incoming
call.
Distributed Hunting:Distributed station hunting delivers a call to the next idle station in the hunt group
after the station that received the previous call. If that station does not answer within the programmed
call advance time, the system delivers the call to the next sequential idle station programmed in the hunt
group. This hunting method is a linear search through the programmed list; however, the search starts
wherever it left off after the previous call.
Longest Idle Station Hunting: Longest idle station hunting delivers a call to the station that has been
idle for the longest period of time since completing the last call that was routed to it by the station hunting
feature. In the case of stations with equal idle times (such as at system startup), the system picks the first
of the grouped stations with equal idle times. If that station does not answer within the call advance time,
the system delivers the call to the station with the next longest idle period.
Ring All Station Hunting: Ring all station hunting is not a true hunting method. This method delivers a
call to all idle stations simultaneously. This is a good method to use when the site requires that all calls
be answered as quickly as possible.
None (No Hunting): This selection disables hunting for the group. It allows a hunt group to be
completely programmed yet disabled. Any intercom calls to this group will receive busy and line ringing
ignores any programming within this group.
Explaining The Software  Release 10A Features IMI89–259
Understanding Station Hunting – 13 
						

							Station Hunting Timers
Call Advance Timer: This is the time interval that a station within a hunt group rings unanswered before
the system routes the call to the next station in the group. This timer is programmable from 10 seconds
though 5 minutes.
Overflow Timer: This is the maximum time interval that an unanswered call hunts within a group before
the system routes it to the designated overflow station for the group. This timer is programmable from 30
seconds through 15 minutes.
Recall Timer:This is the maximum time interval that an unanswered transferred call hunts within a
group before recalling to the source of the transfer. This timer is programmable from 30 seconds through
15 minutes.
Station Hunting Operation
When a system station user makes an intercom call to the hunt group pilot extension, the system rings the
first available station within the hunt group (based on the group’s selected hunting method). This ringing
appears on the station’s personal intercom. The system ignores all call announce settings as all intercom
calls into a hunt group are treated as voice announce block calls. If the station does not answer the call
within the programmed call advance time limit, the system rings the next station of the group. If no
station answers within the programmed overflow time, the call rings the designated overflow destination.
When a line rings at a hunt group, it rings at the first available station within the group (based on the
group’s selected hunting method). As the ringing line appears at the station, it follows the DXP
conventions for line appearances. If the station does not answer the call within the programmed call
advance time limit, the system rings the next member station. If no station answers within the
programmed overflow time, the system sends the call to the designated overflow destination.
The DXP supports a maximum of 32 hunt groups. Each hunt group can include the maximum number of
stations that the system can support; however, due to system memory limitations, all hunt groups can not
contain all stations simultaneously. Since the system makes a total of 16 Kbytes of memory available for
station hunt groups, you can use the following formula to determine possible station hunt group capacities.
[16384 bytes] – [(Stations per group) x (2) + (220 bytes of memory)] = memory remaining for next hunt
group
Detailing Toll/ARS 10A Software Considerations
Before you edit the toll/ARS restriction tables, you must disable the ARS system option; however, before
you view the toll/ARS restriction tables, you must enable the ARS system option.
If you do not observe these setting requirements for either of these editing operations, the system will not
allow the operation to take place and will display messages as to the reason.
IMI89–259 Explaining The Software  Release 10A Features
14 – Detailing Toll/ARS 10A Software Considerations 
						

							Introducing the Visual Man-Machine Interface
The Visual Man-Machine Interface (VMMI) is menu-driven programming software for the DXP digital
communications system. The VMMI software allows the programmer to enter choices in dialog boxes
and accept the entries as valid. The VMMI program includes a detailed, context-sensitive, on-line help
file that the programmer can reference at any time during the programming sequence. The software is
accompanied by GCA40–182,Understanding The VMMI,which details start-up and operation. VMMI
runs on an IBM*-compatible personal computer (PC) with a Microsoft Windows** operating system and
at least 4 Mbytes of memory capacity. The PC communicates with the DXP through the serial data
interface. The serial data connection can be either direct or remote through a modem hookup.
* IBM is registered trademark of International Business Machines Corp.
** Microsoft and Windows are trademarks of Microsoft Corp.
Viewing A Typical VMMI Banner Screen
Explaining The Software  Release 10A Features IMI89–259
Introducing the Visual Man-Machine Interface – 15 
						

							This page remains blank intentionally.