BUSINESS COMMUNICATION SYSTEM
FEATURE DESCRIPTION ADDENDUM
Pub. No. 53-175-4700/C
Issue 1
Pub. No. 53-175-4700/C
Issue 1
Business Communication System
FEATURE DESCRIPTION A DDENDUM
Telrad Connegy, Inc.
Farmingdale, New York
PN 53-175-4700/C, Issue 1
Telrad Connegy, Inc.
Farmingdale, New York
NOTICE
The information in this publication refers to the Telrad Connegy AdvanceIP business communication
systems, Release 3.10, as of October 2005. Telrad Connegy reserves the right to make changes in the
equipment described in this manual without notification. However, changes in the equipment do not
necessarily render this manual invalid.
Additional copies of this manual may be obtained from Telrad Connegy . Reproduction of this manual or parts thereof, without
written permission from Telrad Connegy , is strictly prohibited.
© 2005 Telrad Connegy Inc.
Farmingdale, New York
The following are registered trademarks of the respective listed firms:
Trademark
Firm
Trademark
ACD I.Q.
Telrad Connegy Inc.
Pentium
Windows 95, 98, XP,
NT, 2K
Microsoft Corporation
Firm
Intel Corporation
CONTENTS
1. INTRODUCTION ...................................................................................... 1-1
1.1 General .................................................................................................... 1-1
1.2 Product definition .................................................................................... 1-1
1.3 Purpose of addendum.............................................................................. 1-2
1.3.1 New system features ................................................................................... 1-2
1.4 Scope of addendum ................................................................................. 1-2
1.5 Addendum structure ................................................................................ 1-2
1.6 Intended audience................................................................................... 1-2
2. SYSTEM FEATURES................................................................................... 2-1
2.1 General .................................................................................................... 2-1
2.2 30-Party Conference Bridge ..................................................................... 2-1
2.3 911 and service routing improvements ................................................... 2-1
2.4 911 Routing programming for the Helix................................................... 2-4
2.5 ACD Multi-Registration ............................................................................ 2-7
2.6 Additional programmable buttons .........................................................2-11
2.7 Audio Boost capability ...........................................................................2-12
2.8 Automatic Hold ......................................................................................2-13
2.9 Bridge button ........................................................................................2-13
2.10 Call Back on No answer .......................................................................2-14
2.11 Call Forward from the system administration PC...................................2-14
2.12 Call History ..........................................................................................2-16
2.13 Call Through ........................................................................................2-17
2.14 Changing Station names using System Speed Dial................................2-18
2.15 CID for Emergency (911) ......................................................................2-19
2.16 CID priority ..........................................................................................2-20
2.17 Custom Parameters ..............................................................................2-20
2.18 Delete Dialed Digits .............................................................................2-21
2.19 Dialing during conference....................................................................2-22
2.20 DISA Access to Speed Dial ....................................................................2-22
2.21 DND for SLT .........................................................................................2-22
2.22 Drop softkey ........................................................................................2-22
2.23 Forwarding calls from the Web Portal ..................................................2-22
2.24 Call Record to another mailbox ............................................................2-23
2.25 Fast Dialing..........................................................................................2-23
2.26 GAP Telephone support .......................................................................2-25
2.27 Languages on Display Telephones .......................................................2-26
2.28 MDN Group Improvements ..................................................................2-27
2.29 Memory Button on Attendant console .................................................2-27
CONTENTS
iii
CONTENTS
2.30
2.31
2.32
2.33
2.34
2.35
2.36
2.37
2.38
2.39
2.40
2.41
2.42
2.43
2.44
2.45
2.46
2.47
2.48
2.49
2.50
2.51
2.52
Multi Night modes ...............................................................................2-27
Multiple language support...................................................................2-34
Multiple Profiles ...................................................................................2-34
Mute Improvement ..............................................................................2-35
Network enhancements .......................................................................2-35
New System Default File.......................................................................2-35
New System Password..........................................................................2-36
New System Security ............................................................................2-36
NI2 Support for the PRI ........................................................................2-37
Phone Book .........................................................................................2-37
PRI Name .............................................................................................2-40
Redial from Idle....................................................................................2-40
SLT Near-End-Disconnect recognition ..................................................2-40
Software Downloading ........................................................................2-41
Speed dial bin enhancement ................................................................2-43
System Speed Dial button ....................................................................2-43
Time Zone compliance .........................................................................2-43
Universal Operating Code ....................................................................2-44
Universal Operating Code with ACD Login/Logout...............................2-45
Verified Account Codes ........................................................................2-46
View ....................................................................................................2-47
VIP List – Selective DND .......................................................................2-48
Virtual Station ......................................................................................2-48
3. PRIVATE NETWORKING BETWEEN TELEPHONE SYSTEMS ........................ 3-1
3.1 General .................................................................................................... 3-1
3.2 BLF over DPNSS ....................................................................................... 3-1
3.3 Digital Private Network Signaling System (DPNSS).................................... 3-4
3.3.1 Interworking ................................................................................................ 3-4
3.4 Full networking over IP ............................................................................ 3-4
3.5 Network analog protocol (NAP) ............................................................... 3-4
3.5.1 System cards supporting NAP...................................................................... 3-4
3.5.2 Network-wide availability of system communication features under NAP .. 3-4
3.6 Network cards ......................................................................................... 3-5
3.7 Networking features -- supplementary services ........................................ 3-5
3.7.1 Protocol independent features .................................................................... 3-5
3.7.2 Protocol dependent features ....................................................................... 3-6
3.7.3 Feature list ................................................................................................... 3-6
3.7.4 Interprotocol feature names........................................................................ 3-7
3.8 Private network media and connectivity................................................... 3-7
3.8.1 USA.............................................................................................................. 3-7
3.8.2 UK ................................................................................................................ 3-8
3.8.3 Other countries ........................................................................................... 3-8
3.9 QSIG ........................................................................................................ 3-8
3.9.1 Names over QSIG ........................................................................................ 3-8
iv
CONTENTS
Section 1
INTRODUCTION
1.1
G ENERAL
This section provides introductory information about this addendum .
Where not otherwise stated, it should be assumed that the characteristics and features of the various DIGITAL and current AdvanceIP
systems are identical. Therefore, unless stated otherwise, the name
AdvanceIP should be understood to include DIGITAL systems as
well.
1.2
PRODUCT
DEFINITION
This addendum includes a description of the software features that
are new to Release SB7 and up of the AdvanceIP systems, and
Release e2e-1 and e2e-2 of AdvanceIP. features requiring the emaGEN Messaging Platform are applicable to emaGEN release 2.0.
Table 1.1, below, lists the software versions applicable to each of
the currently supported AdvanceIP systems.
Table 1.1 AdvanceIP current software versions
Product
General
Software
Version
System
IPeX
S400
S128
S1000
SBS Rel. 7
SB7 (7)
SB7
--
DB7
LB7
AdvanceIP Rel. 1
e2e-1
eC1
eAC1
eD1
eM1
AdvanceIP Rel. 2
e2e-2
eC2
eAC2
eD2
eM2
AdvanceIP Rel. 3
e2e-3
--
EM3
-- a
EDA3b
a.IPeX 400 includes all system configurations up to 400 ports. These configurations
must all be equipped with IPeX 400 Server in order to run Release 3 (see exception
in footnote b).
b. Release ED3 supports 400-port systems using the old MPD-400 main control card.
This support is to be phased out in the future.
1-1
76-110-0690/I, Issue 2
For a description of the features of previous releases of the system,
you should consult the Release 6 Feature Description manual, the
SB7 DIGITAL Family of Systems Feature Description Addendum,
and the AdvanceIP 1000 Addendum.
1.3
PURPOSE OF
ADDENDUM
This addendum is intended to document the features new to
Releases SB7 and upwards of the AdvanceIP family of systems.
1.3.1 New system features
The AdvanceIP systems’ new features include:
•
•
•
•
•
•
•
•
1.4
SCOPE OF
ADDENDUM
Multi-system networking capability -- expanded to include IP
and Digital Private Network Signaling System (DPNSS) protocol
and QSIG basic call protocol;
Multi ACD Registration, enabling a station to register as up to
ten ACD agents;
Phone Book feature enabling system users with Avanti display
telephone sets, to enter, delete, revise, save in memory, search
for, and dial, selected name and telephone number entries;
Call forward from the administration PC;
Multiple language support;
Universal Operating Access (UOA).
Call Through capability
Multiple profiles
This Feature Description addendum covers the features introduced
in the system starting from Release 7 of the system software.
Unless otherwise specified, all the features described in this manual apply to all AdvanceIP systems.
1.5
ADDENDUM
This addendum includes the following sections:
STRUCTURE
1.6
INTENDED
AUDIENCE
1-2
Section 1
Includes a general explanation of the contents of the
addendum and information on applicable documents.
Section 2
Describes the new AdvanceIP system features.
Section 3
Details alternative configuration applications for
private networks comprising AdvanceIP systems.
This addendum is intended for personnel involved in AdvanceIP
system installation, servicing and customer training, as well as for
system distributors and customer service representatives.
Section 2
SYSTEM FEATURES
2.1
G ENERAL
This Section describes the software revisions and enhancements to
features and services applicable to the AdvanceIP systems made
since Software Release 7.00.
Unless stated otherwise, these characteristics and features apply to
all of the AdvanceIP systems (see Table 1.1, above, for a list of the
currently supported AdvanceIP software versions).
2.2
30-PARTY
CONFERENCE
BRIDGE
Release e2e-1
Description The Conference Bridge capacity has been increased
from eight participants to 30 digital lines, depending on provisioning. You can now have a maximum of 30 callers in a conference
bridge or up to five smaller bridges with the maximum number of
participants equal to 30 between all active bridges. There is no
increase in the capacity of a regular conference call.
No additional hardware is needed for the 30-party Conference
Bridge in e2e-1.
This option requires a software license.
NOTE
In a 30-party conference bridge, all participating trunks
must be digital.
2.3
911 AND
SERVICE
ROUTING
IMPROVEMENTS
Release e2e-3
Description IP extensions at remote sites can have emergency
and other numbers routed by LCR to local trunks, independently of
other routes defined in the system.
Service and emergency call numbers, such as 911, can be routed
according to IP site. This enables remote extensions over IP to have
these numbers routed to local destinations, instead of the default
routes defined for the rest of the system.
2-1
76-110-0690/I, Issue 2
(For a description of the IP site eManager field, see the AdvanceIP
Guide to Voice over IP, Section 5.4.6).
Although any site number can be used for configuring an LCR
routing profile, it is recommended to give the remote extensions
an outstanding site number.
Figure 2-1 Two new service routes
Two service routes -Service Route 2 and Service Route 3- have
been added in eManager’s LCR PARAMETERS screen (L-P) to provide extra flexibility to LCR routing.
Programming Different routes can be configured for service
numbers, or for any general interest number to be accessed by all
extensions at a specific location.
To program a service number so that it can be routed to different
trunks according to the IP site of the dialing extension, proceed as
follows:
1. Define the required service routes in eManager’s PUBLIC NETWORKS (L-N) screen (see below, Figure 2-2)
Figure 2-2 Defining special numbers
for the default service route
2-2
Section 2: SYSTEM FEATURES
2. Attach an LCR profile to the desired service route through the
LCR PARAMETERS (L-P) screen, as shown in Figure 2-1, above.
3. Using the LCR GLOBAL DEFINITIONS/LCR ROUTE PROFILE
screen see , define criteria for applying the appropriate routes
(Indirect Route fields) when a number defined as a service is
dialed. These criteria are defined in the Activation Device fields;
the system checks these fields from left to right, applying the
first condition that returns a true value.
Figure 2-3 LCR ROUTE PROFILE screen
Thus, in the example shown in Figure 2-3, above, the first condition established by LCR Profile 1 (first row) is: if the dialing
extension has IP site 10, then the call should be routed
through Route 2. Otherwise, if the dialed extension has Class
of Service 2, then the call should be routed though route 3.
4. In the ROUTE TABLES (L-T) screen (see below, Figure 2-4),
define a route for each of the possibilities in the profile. In our
example, detremined that stations with IP site 10 will dial service numbers through route 2. This route is defined in the
example as trunk group 2.
2-3
76-110-0690/I, Issue 2
Figure 2-4 LCR route definitions
5. Trunk group 2 (in the example) must be defined as a local
trunk group in the same location as the extensions with IP site
10; for example, trunks connected to a remote SIP gateway or
to a remote AdvanceIP system connected in a distributed IP
network configuration (see 2.3, " System deployment capabilities", the Guide to VoIP in AdvanceIP for more information on
IP configuration options).
6. If the extension dialing the service number does not have IP
site 10, then according to the LCR pofile in the example, it will
be routed according to its COS, or by default to route 1. This
route has been set to trunk group 1, which may be a regular
trunk group of the local system.
2.3
911 ROUTING
Release e2e-1
PROGRAMMING
FOR THE HELIX
Description With the introduction of the Helix gateway, it was
imperative that each remote location be able to dial 911 and
access their individual trunk add-on modules for the correct Caller
ID information. With the new 911 routing programming you will
be able to direct a 911 call depending on location of caller.
Operation
1. When X202 (Helix Station) dials 911 the system modifies this
number to 9300202911.
2. The system searches area routes for a match for area code 300
and then office code 202. When a match is found it directs
the call to Route Table 2 programmed for TG 2 Modification.
3. Modification table 2 will delete 7 digits (9300202) and dial 911.
2-4
Section 2: SYSTEM FEATURES
4. The call will then be processed out over the trunk associated
with the Helix station.
Programming One of the new LCR programming enhancements is the ability to set a route table TG as Internal. In doing
this, you instruct the system to modify the dialed number and redirect it to another route. You will also need to program a unused
area code. In the example we will use 300.
In the following example, X202 will belong to a Helix gateway and
it will have a trunk add-on module that will support trunk 802.
Trunk 802 will be programmed for Trunk Group 2.
1. At Least Cost Routing – Public Network (L-N) program 911 as
Type = Service (see Figure 2-5).
Figure 2-5 Programming Public Network
2. On the LEAST COST ROUTING – ROUTE TABLES screen (L-R)
program Route Table 1 for Internal. Also, program the Modification Table for this route as 1 (see Figure 2-6).
Figure 2-6 Programming Route Tables
3. Program LEAST COST ROUTING - MODIFICATION TABLES (LM). Table 1- Add Preceding digits 9300E (see Figure 2-7).
2-5
76-110-0690/I, Issue 2
Figure 2-7 Programming Modification Tables
4. Program Least Cost Routing-LCR Parameters (L-P) Service
Route to 1 (see Figure 2-8).
Figure 2-8 Programming LCR Parameters
5. Program Least Cost Routing – Route Tables (L-R), Route Table
2 -for TG1 Modification Table 2.
6. Program Least Cost Routing – Modification Tables (L-M) Table
2 to delete seven digits (see Figure 2-9).This will delete the
9300 and DN number generated in step 3.
Figure 2-9 Programming Modification Tables –
Delete seven digits
2-6
Section 2: SYSTEM FEATURES
7. Program Least Cost Routing – Area Routes (L-A). Enter the
unused area code 300 (see Figure 2-10).
Figure 2-10 Programming Area Routes
8. Press F9 to edit Area Route 300. Set a specific route for 202
(Helix station).
9. Program 202 to access TG2 in route table 2 (see Figure 2-11).
Figure 2-11 Programming office routing
2.4
ACD
MULTIREGISTRATION
Release e2e-3
Description
A station can register as an ACD agent into more than one ACD
group. Stations can register into a maximum of ten ACD groups,
each with a different Agent ID.
Appearance A station user registered into several ACD groups
will appear to the supervisors of all groups under the first ID with
which she logged in.
The same is true of ACD applications working with the system:
Novea reports will list the agent as having the first ID with which
2-7
76-110-0690/I, Issue 2
she registered, independently of what other groups she is registered into.
When the station is idle, the display shows the first agent that
logged in. When registering into additional groups, the display
shows the group and agent numbers for about five seconds.
When an ACD call arrives, the corresponding ACD queue button (if
programmed) flashes green, and the display shows relevant information such as ACD plan, caller ID, etc.
The supervisor can see all the agents in her group and all their
queues, but if an agent is in another group’s call, the supervisor
cannot monitor that call. The supervisor’s display shows the line
ANOTHER ACD CALL for all the agents that are handling calls of
other groups
When a station that performed Multi Registration is unavailable, it
is so for all the groups it has logged into. This applies to wrap up
and forced busy states as well:
A station user can check to see whether she is logged into a specific group if ACD specific queue buttons have been defined on her
station. These buttons, each dedicated to an ACD queue, appear
in the default station map as ACD Q1 through ACD Q24.
Priority Each agent ID has a priority level from 1 (highest) to 10
(lowest). ACD agent priority must be set separately for each agent
ID.
When Multi Registration is active, ACD handles its queues as follows:
•
•
In principle, ACD prioritizes agents according to the time they
have been available in all queues.
However, when calls arrive simultaneously at two queues into
which the same station is registered (as two different agents),
the call will be transferred to the agent with the highest priority.
In other words, when passing a call to an agent in a queue, ACD
checks first whether there are calls waiting in other queues where
the station is resitered as an agent with higher priority. If this is the
case, the call is not passed.
A station can register with two or more Agent IDs having the
same priority. If two or more Agent IDs of a station have the same
priority in queues where calls arrive at the same time, the call in the
queue where the station has been waiting for the longest time will
be passed to it
Automatic Registration Up to ten ACD Agent IDs can be
defined for Automatic Registration into pre-assigned ACD groups.
Every set has a “Master Agent ID”. When a station user logs into
ACD with the Master Agent ID, all the agent IDs defined in the set
log automatically into their respective pre-definedgroups.
2-8
Section 2: SYSTEM FEATURES
Note the following:
•
•
•
Only one registration ID from each ACD group can be assigned
to each set;
All the Agent IDs in a Multi Registration set must be different;
An Agent ID can appear in one Multi Registration set only.
Operation
Logging in and out is performed by entering the relevant feature
code for ACD login and logout. The user is then required to enter
the group number and the agent ID.
•
•
If the user enters her master ID, she will be logged into all the
groups defined for her.
If she enters the ID of one of the groups, she will be logged into
that group only.
The wrap up timer is activated separately for each queue, according to the value programmed for it. This way, a station may have
different wrap up times, according to the groups the station is currently logged into. However, when the agent is in wrap up status,
she is busy for all the groups in which she is registered
When a station registered as more than one agent goes into
forced busy state, this applies to all the groups it is logged into.
When the station is released from forced busy state, all the agents
that station was logged in as are logged back in.
To log out of all the groups at once, the user can enter an asterisk
(*) as both the group and the agent IDs. She can also log out of
each ACD group separately by dialing the ACD logout code and
entering the Agent ID registered in that group. However, if logging
out separately, the last Agent ID to unregister must be the first
one that logged in.
NOTE
If the user attempts to unregister the first Agent ID
while still registered in other groups, she will hear an
error tone and the logout will be canceled.
The programmable ACD queue buttons at the agent’s station
serve for displaying ring status and for answering calls to the
queues the station is logged into.
In idle state, pressing an ACD queue button for a group in which
the agent is registered, will display Group xx: agentname
(where xx is the group number, and agentname is the name of the
agent as defined in eManager) for about five seconds.
The station does not react if an ACD queue button for a group in
which the station is not registered is pressed.
All the ACD buttons that are relevant for an agent will be activated
for the agent’s calls. For example, when the agent presses the
2-9
76-110-0690/I, Issue 2
[Help Request] button, it will signal the supervisor of the call
queue currently active at the agent’s station.
The supervisor can use the Universal Operation feature (see Section 2.46, below) so as to operate as the station of an agent in her
group, then log in and out for that agent. This is convenient for
cases where the supervisor wishes to remove an agent from a
queue who is not available to perform logout by herself. However,
the supervisor should be careful to follow the appropriate order,
i.e. leave the first Agent ID with which the agent logged in for exiting last.
Conditions and limitations
A station cannot register in the same group under two agent IDs.
All registrations must be made to different groups.
ACD Multi Registration is subject to the same license limitations as
the previous versions of ACD. Each agent registered decreases the
total of agent seats allowed by the license purchased. If the total
number of agent seats is reached, no additional agents are
allowed to register, regardless of the number of agents defined in
eManager.
ACD Multi Registration requires eManager version 3.0.0.16 or
higher.
Programming
By default, ACD Multi Registration is disabled for all stations. To
enable it, access the GENERAL ACD PARAMETERS screen (C-A)
and set the Multi-Login Allowed parameter for the desired DN to
Yes.
Figure 2-12 Enabling ACD Multi Login
NOTE
When ACD Multi Registration is enabled, only
dedicated ACD queue buttons can be used on agents’
stations. Previously defined ACD Q buttons are
disabled. This is so regardless of whether ACD MultiRegistration is actually activated or not, i.e. whether a
station user has registered or not: enabling Multi
Registration is sufficient for disabling the Q buttons.
2-10
Section 2: SYSTEM FEATURES
Programming Priority When defining an agent, a priority level
must be assigned to it. Agents are defined through the AGENT
LIST screen, which is displayed by selecting the row of the required
group in the ACD GROUPS screen (C->G) and pressing F9.
Figure 2-13 Defining ACD Agents and their priority levels
Programming Automatic Registration To define sets of Agent
IDs for Automatic Registration, use the ACD AUTOMATIC MULTI
REGISTRATION screen (C-M).
Figure 2-14 The AGENT LIST screen
All remaining ACD programming is the same as for ACD without
the multi-login capability. For more information, see the AdvanceIP
ACD System manual.
Note the following:
•
•
•
2.5
ADDITIONAL
PROGRAMMABLE
BUTTONS
Only one registration ID from each ACD group can be assigned
to each set;
All the Agent IDs in a Multi Registration set must be different;
An Agent ID can appear in one Multi Registration set only.
Release e2e-1 and up
Description New programmable button options have been
added to the system. These include:
•
Audio Boost (see Section 2.6);
2-11
76-110-0690/I, Issue 2
•
•
•
•
•
•
Available vocoders (i.Picasso stations only);
Bridge button (see Section 2.8);
Drop from Conference;
Pick Up All;
System Speed Dial (see Section 2.44);
Voicemail (emaGen or SnapMail) access.
Programming The new programmable buttons are defined
through the STATION FEATURES/PROGRAMMABLE KEYS screen
(F-P-F9-F10) of eManager.
2.6
AUDIO BOOST
CAPABILITY
Release e2e-2
Description The volume of a station can be boosted on a permanent basis. This is useful for hearing-challenged users, or for those
working in a noisy environment. A special button can be defined
for this purpose, for the user to activate whenevr necessary.
Conditions and limitations The Audio Boost feature is not supported on IP telephones.
For the Audio Boost capability to work, the Avanti station firmware
must be, as a minimum, 03D2 (for old station hardware), or 60D2
(for new station hardware). "Old" station hardware refers to station
hardware releases older than those detailed in Table 2.1
Table 2.1 Audio Boost station hardware compatibility
Most
countries
UK
Israel
Executive, DIsplay HD, Display
FD
M12
M10
M9
Speakerphone HD, 15-Button
M13
M11
M10
Speakerphone Full Duplex,
M14
M11
M11
Monitor
M10
M8
M7
M8
M8
M8
Attendant
Operation Press the Audio Boost button.
Programming Program an Audio Boost button through the STATION FEATURES/PROGRAMMABLE KEYS screen (F-P-F9-F10) of
eManager. The button value is ABST, as shown in Figure 2-15,
below.
2-12
Section 2: SYSTEM FEATURES
Figure 2-15 Defining an Audio Boost button
2.7
AUTOMATIC
HOLD
Release e2e-1
Description Prior to Release e2e-1, when a station user was on
an outside call and another outside call rang into the station, the
user had to press the hold button to answer the second call without disconnecting the first call. With Release e2e-1, the first call is
automatically put on hold when the station user presses one of
the following keys to answer the second call - Display Soft-key, Private Trunk button, Trunk Group button, Floating button, PBX Button.
The general parameter Disconnect when answer new call determines how will the system behave when the user accesses an outside line while on a call. If the parameter is set to No (default), the
ongoing call will be placed on hold automatically.
NOTE
The original hold mode is available by setting Custom
Parameter 11 to the value of 1
2.8
BRIDGE BUTTON
Release e2e-2
Description A Bridge button may be defined on a station map.
The button may be used:
•
•
•
As a BLF to see the status of the specific bridge
To enter the bridge;
To transfer a call to the bridge by pressing it when the station
2-13
76-110-0690/I, Issue 2
is in idle or dial tone state.
Programming Bridge buttons are programmed through the
STATION ATTRIBUTES/PROGRAMMABLE KEYS screen (F-P-F9F10)). The button value is BRGxxx, where xxx is the DN of the
bridge defined.
2.9
CALL BACK ON
NO ANSWER
Release 7.30J.
Description Call Back to a busy station has been a feature on the
system since version 1. Starting with version 7.30J a callback
request can now be made to an idle station. Station A calls Station
B, which is in an idle condition. While station B is ringing Station A
presses the Callback key. The user of station B then comes back to
his office and goes offhook and makes a call. As soon as Station B
goes idle again the call back is processed. Station A then rings,
goes offhook and then Station B rings.
2.10 CALL F ORWARD
FROM THE
SYSTEM
ADMINISTRATION
PC
Release e2e-1
Description Call Forward can be programmed now in advance
from eManager, in addition to programming it from user stations.
Call Forwarding by telephone set users is described fully in the
AdvanceIP Family of Systems Feature Description manual; with
each of the main three types of Call Forwarding -- Call Forward
(formerly named Follow Me), Call Forward Busy and Call Forward
No Answer:
•
the Call Forward destination is programmed from the user’s
telephone set;
• internal calls can be forwarded to internal or external
destinations;
• the user can define either:
• a single Call Forward destination for all calls; or
• different Call Forward destinations for internal and external
calls.
In addition, the above types of Call Forwarding can now also be
programmed for any or all of the telephones in an AdvanceIP system, from the System Administration PC to reroute calls from an
extension to either:
another extension
a hunt group
an MDN group
an ACD group
an outside number via a private or system speed
dial bin
an extension in another system in a common
private network
Conditions and limitations If Call Forwarding is programmed to
an extension, a hunt group or an MDN group, ICM restriction will
be checked. The system will allow programming only if:
•
2-14
the ICM group of both the origin and the destination are equal,
Section 2: SYSTEM FEATURES
•
and
the ICM COS of the origin is less than or equal to that of the
destination.
The ICM restriction programming for an extension will be taken
from its Day COS programming.
Programming Call Forward from a particular DN to the same DN is
not allowed.
Programming of unconditional call forward to a hunt group from
an extension which is a member of this hunt group is not allowed.
Note that the same action with respect to an MDN group is
allowed, provided that the station and the MDN group don’t
share the same DN (not a primary station).
If Call Forward is programmed to an Attendant extension, the
eManager will automatically display the Attendant to which the
extension – or the MDN Call Forwarding extension -- is programmed. If the MDN Call Forwarding extension is programmed
to:
"All" – the first MDN group member is considered;
“-“ -- or no members – the first Attendant extension will be
chosen.
If Call Forward programming has been programmed for a particular extension, be it by the telephone set user at that extension and
in System Administration, the latter of the two will remain in effect
-- based on the time of programming completion at the extension
and the time of downloading a new programming to the system.
In all cases of either programming method, the last programming
will override previous programming of common elements.
•
•
•
•
•
•
NOTE
If Call Forward is programmed to a system speed dial number
– calls will be forwarded to the system speed dial array the
station is associated with.
If Call Forward is programmed to an IVM hunt group – the
eManager will insert the hunt group or system speed dial
number to which the IVM Hunt Group DN is programmed. If
this hunt group or system speed dial number is programmed –
the IVM Hunt Group DN will be displayed.
If the MDN Call Forwarding extension is programmed for "ALL"
– programming of private speed dial numbers is not allowed.
If any All field is changed – the new value is automatically
copied to both Internal and External relevant fields.
If one of the Internal or External fields is changed – the other
field is not changed, and the relevant All field is automatically
cleared.
2-15
76-110-0690/I, Issue 2
Programming The STATION FEATURES/CALL FORWARD screen
(F-F) in eManager groups the Call Forwarding types, as follows:
Call Forward
All
Call Forward Busy All
Call Forward
No Answer All
Call Forward Internal
Call Forward Busy
Internal
Call Forward
No Answer Internal
Call Forward external
Call Forward Busy
external
Call Forward
No Answer external
Figure 2-16, below, shows the CALL FOWARD screen.
Figure 2-16 Programming Call Forward from eManager
2.11 CALL HISTORY
Release e2e-1
Description Call History saves at the phone level all external and
networked calls to a station. This feature works on regular Avanti
Display Stations only. Call History will log all incoming, outgoing
and missed calls to a station and log them in the proper category.
Up to 90 numbers (30 in each category) will be stored. The user’s
display will change from Call Log to New Calls if there is a
new missed call entry only.From any of the Call History entries you
will be able to press the call button to dial that number.
NOTE
The Application External Route field on the STATION
ATTRIBUTES screen (F-A) must be programmed for the
Call History feature to work. This field determines the
route the system will take when returning calls from
the Missed or the Incoming Calls lists.
You may use the [HI-LO] button to scroll through call logs.The
Detail option under Call History allows a user in a system equipped
with Caller ID Name and Number to toggle between the name,
number and time of the call.Any new entries in the Call History
2-16
Section 2: SYSTEM FEATURES
logs will be identified by an * next to the category header.Only
Incoming calls with Caller ID will be listed under Call Log/Incoming.
The Call History log is saved in the telephone, not in the AdvanceIP
system. If a station is replaced, the call log will no longer be available.
Conditions and Limitations Call History is available on regular
Avanti stations with display only. It is not supported on IP stations
(i.Picasso, Avanti IP and Avanti SP15).
Call History requires Avanti station firmware version 0ED1 or
higher.
2.12 CALL T HROUGH
Release e2e-2
Description Outside numbers may be designated to access the
system from the outside and automatically access system
resources. The Call Through feature differs from DISA in that it
does not require the caller to enter the ECC number to identify
herself. Instead, the number is automatically validated and authorized to function as a system extension.
Lists of Call Through authorized numbers are defined in system
speed dial bins grouped by hundreds. When an outside call rings
through a DID trunk, the calling number is checked against the
system speed dial list.
On CDR printouts, Call Through calls are indicated by a "#" character followed by the speed dial bin associated with the calling number.
Dialing privileges or limitations of Call Through calls are allocated
according to a specific Class of Service programmed for each Call
Through group of hundred speed dial bins. Call Through COS
must be programmed from 41 upwards. The specific number
assigned the COS consists of 40 + the ordinal number of the hundred group where the Call Through number has been programmed. Thus, a Call Through programmed into the 300 group
will be 43.
Conditions and limitations The Call Through feature works for
calls made on TIE-DID trunks only.
The numbers stored in system speed dial for Call Through authorization must occupy the first consecutive places of each hundred of
bins.
The Call Through feature requires a license for a specified quantity
of authorized users.
Programming Call Through requires no special programming,
other than defining the speed dial numbers in groups of one hun2-17
76-110-0690/I, Issue 2
dred consecutive bins. These groups must be defined in the SYSTEM SPEED DIAL GROUPS screen (S-S-S) as hidden.
Also, the Call Through DID number must be routed to DISA. When
a call to that number arrives, the caller ID is checked for appearance in one of the hidden speed dial hidden groups. If it is found,
the caller is authorized to make use of system resources.
2.13 CHANGING
STATION NAMES
USING SYSTEM
SPEED DIAL
Release 7.34
Description It is possible to change station names using System
Speed Dial bins. This feature allows a customer who moves
employees around to change the name of a station without having to call their dealer.
In the same way, the customer can change Hunt, MDN, ACD
group, agent or supervisor, and DID destination names.
Programming From eManager:
1. Define a Programming Station for a System Speed Dial Group
(S-S-S).
2. Program a System Speed Dial Bin (S-S-N) with the name of a
station user.
3. Program the System Speed Dial Bin in the Name field of Station
Attributes (F-A).
Now whenever a name has to be changed for a station, the Programming Station for that System Speed Dial Group can access
the Speed Dial Bin and change the name via their keypad.
The same principle can be applied to change the name of a DID
destination, Hunt, MDN or ACD agent or supervisor. To do so,
substitute the following for step 3:
ACD group, agent or supervisor name: From Automatic Call
Distribution, program the Name field on the ACD GROUPS screen
(C-G), AGENT LIST screen (C-G-F9) or Supervisors and ACD
GROUPS screen (C-S) to Sy:xxx, where y: is a system speed dial
group, and xxx is the bin number that will contain the Hunt Group
name..
2-18
Section 2: SYSTEM FEATURES
Figure 2-17 Defining ACD supervisor names
as System Speed Dial codes
DID destinations: Set the Name/Message field on the DID
ROUTING screen (R) to Sy:xxx, where y: is a system speed dial
group, and xxx is the bin number that will contain the DID destination name.
Hunt groups: Set the Name field on the STATION GROUP FEATURES/HUNT GROUPS DEFINITION screen (I-H) to Sy:xxx, where
y: is a system speed dial group, and xxx is the bin number that will
contain the Hunt Group name.
MDN groups: Set the MDN Name field on the STATION GROUP
FEATURES/MDN GROUPS DEFINITION screen (I-M) to Sy:xxx,
where y: is a system speed dial group, and xxx is the bin number
that will contain the MDN Group name.
2.14 CID FOR
EMERGENCY
(911)
Release 7.34
Description The outgoing Caller ID information sent out on a PRI
can now be programmed on a per-station basis. This is important
for applications that require a unique number to be sent for each
station when calling 911. The Police department can then look up
the unique number in its database to determine the exact location
of the caller. Please note that at this time this feature is available
on PRI calls only.
An Avanti Station virtual DN can log into any station. It is also
important to note that the station types do not have to match for
the virtual station to work.
Programming There is a new field eManager labeled CID for
Emergency. A speed dial bin can be entered into this field per station. When the station user makes an outgoing call on the PRI the
contents of the speed dial bin is sent as the outgoing CID.
There is a system-wide setting to specify whether the CID for
Emergency is used for every outgoing PRI call or only calls directed
to 911. At default only calls to 911 will use the CID for Emergency
2-19
76-110-0690/I, Issue 2
entry. To have the entry go out for all calls set Custom Parameter 8
to a value = 32.
2.15 CID PRIORITY
Release 7.20
Description By default, an incoming DID call to a 3015 or 3020
station will show the DID name programmed in system administration. If you prefer to see the Call ID information, set CID priority
in station Attributes to Yes. Once the call is answered there are
three display options that can be seen by successively pressing the
time button:·DID Name·Caller ID information·Time and Date
Programming At eManager,, use the following path: Station
Features - Station Attributes (F-A). Then scroll over to CID Priority
and Select Y or N;
If caller ID priority is set to Y, the display order will change to 2, 1
and 3. 3025 stations show both DID Name and Caller ID information simultaneously. If the [Time] button is pressed after the call is
answered, the Time, Date and user's extension number will
replace the DID name and Trunk number.
2.16 CUSTOM
PARAMETERS
Release 6.07
Description Entering a specific value in the eManager CUSTOM
PARAMETERS screen is used to enable features.
Each feature is described below. The corresponding value and
parameter number to enable the feature is specified.
CID timer: The amount of time the system waits for Caller ID
information to be sent from the Central office after ring generator
is detected is programmable. At default the timer is 4 seconds. To
set the timer to 8 seconds change Custom Parameter 2 to value =
2. To change back to the default set the value back to 0.
Meet me conference tone: When entering or leaving a Meet Me
Conference a tone is generated by the system to all participants.
To eliminate the tone change Custom Parameter 4 to value = 4.
To change back to the default set the value back to 0.
SD2 display for incoming DID call: When an incoming DID call
rings an SD2 station the display shows the DID name specified in
the DID routing table. When the station user answers the call the
name is still displayed. To have the display change to the trunk
number when answered set Custom Parameter 4 to value = 8. To
change back to the default set the value back to 0.
PRI NI2 1+ toggle for long distance calls: Most Central offices do
not require a 1+ number entry in the D channel message for
“Called number”. If the CO requires a 1+ entry change Custom
Parameter 4 to value = 16. To change back to the default set the
value back to 0.
2-20
Section 2: SYSTEM FEATURES
Attendant position overflow for dial 0: On version 6 systems and
up, dial 0 calls to the attendant will route to the overflow destination. To stop dial 0 calls to the ATC from overflowing set custom
parameter 4 to value = 64.
PRI channel Out of Service (OOS) recovery: In installations with
layer 1 problems the PRI channels may become Out of Service. To
have the system automatically attempt to put the channels back in
service via a card reset, set Custom Parameter 2 to value = 3. To
change back to the default, set the value back to 0.
NOTE
Only enable this recovery feature if you actually
experience OOS problems on the system.
Two or more Tie type trunks in a conference call: An internal station user sets up a conference call with two trunks. The trunks are
programmed as Tie type. When the internal station hangs up the
two Tie trunks can remain connected in a conference. To automatically drop the Tie trunks when the internal party hangs up set
Custom Parameter 4 = 128. To change back to the default set the
value back to 0.
Programming Use the following path from the eManager main
menu to enter the CUSTOM PARAMETER PROGRAMMING screen.
System Parameters (S) > General Parameters (P) > Edit Custom
Parameters (press F9).
To enable a feature, a specific value is entered in one of the nine
Parameter fields.
NOTE
If there are two or more features you want to enable
that utilize the same Custom Parameter, add the
values together and enter the sum into the value field.
Example: To enable an SD2 display change and
attendant position overflow for dial 0 set Custom
Parameter 4 to value = 8 + 64 = 72.
2.17 DELETE DIALED
DIGITS
Release e2e-1
Description You can delete digits as you dial. If a wrong digit is
entered when dialing an external number, you can now press the
{DELETE} softkey to delete that digit. Multiple digits can be
deleted.
The {DELETE} softkey appears in the display of any Avanti Station. This feature eliminates the need to hang up on a misdialed
number and start the dialing process again.
NOTE
The Delete Dialed Digits feature does not work on
trunks programmed as overlap (Card Parameters –
PRI24/N24 Card Parameters).
2-21
76-110-0690/I, Issue 2
2.18 DIALING DURING
CONFERENCE
Release e2e-2
Description Digits dialed during a conference call will be sent to
a voicemail (if it is the last participant joined the conference) or
towards a trunk (the last trunk which joined the conference).
2.19 DISA ACCESS
TO SPEED DIAL
Release 7.34
Description Callers accessing the systemthrough Direct Inward
System Access (DISA) can activate Speed DIal numbers.
Operation After accessing the system through DISA:
1. Dial 773.
2. Dial the Speed dial code (two or three digits for a system Speed
dial code, or two digits for a personal speed dial code).
The number is dialed automatically.
2.20 DND FOR SLT
Release 7.34
Description Prior to Release 7.34, it was not possible to put an
SLT into DND (Do Not Disturb) mode. Now an SLT can enter DND
mode by simply entering the DND Feature Access Code. The user
will hear stutter dial tone when in DND.
Operation A Function Access Code must be programmed in
eManager.
To cancel DND on an SLT enter the Cancel Code (#) and the DND
Code again.
Programming The DND Function Access Code can be programmed in the FUNCTION CODES screen (S -F).
2.21 DROP SOFTKEY
Release e2e-1
Description Prior to Release e2e-1, when a user was on a call
and a second call rang in, they had to press the DND button to
reroute the ringing call into voice mail. Now with E2E1, the
{DROP} softkey will redirect a second incoming call to voice mail.
The {DROP} softkey may also be used during conference calls,
paging, and intrusion calls.
2.22 FORWARDING
CALLS FROM THE
WEB PORTAL
2-22
Release e2e-1.2
Description AdvanceIP system users can forward calls from the
AdvanceIP Web Portal. Not only IP extensions, but all users have
access to this feature.
Section 2: SYSTEM FEATURES
Operation On the Web Portal, open the Forwarding tab to display the FORWARDING RULES screen, as shown in Figure 2-18,
below:
Figure 2-18 Programming Call Forward from the Web Portal
Select the appropriate settings and click Update.
Conditions and limitations Requires that a TVSe Server card be
installed on the system.
All the Call Forwarding conditions and limitations detailed in Section 2.10, above, apply.
2.23 CALL R ECORD
TO ANOTHER
MAILBOX
Release 7.33
Description PBX extension users can record calls to the mailbox
belonging to the PBX DN in use at the time the [CR] button is
pressed.
This feature can be used also in networked systems where the
emaGEN system is not in the same system as the recording extension.
Conditions and requirements A mailbox must be defined for
the recording PBX DN. If no mailbox exists for the active DN, the
call will be recorded into the main DN’s mailbox of the station.
2.24 FAST D IALING
Release e2e-1.3
Description Dialing on PRI (PR24 and PR30) trunks with en-bloc
addressing mode, or numbers modified by LCR, the system needs
to wait for a timeout in order to detect the end of dialing and start
processing the digits dialed. The Fast Dialing feature renders this
timeout unnecessary. It is possible now to define series of numbers
for the system to recognize when the end of dialing has been
reached.
2-23
76-110-0690/I, Issue 2
A maximum number of digits to expect can be defined, so that the
system will be able to start processing when the maximum length
of the number is reached. Specific series of digits can be defined as
well, so as the defined length of number can be applied only to
them.
Example Assume that all numbers dialed by a sales representative to area codes 516 or 212 must be routed by LCR. You can
define 516 and 212 as lower limits, and a maximum length of 10
digits for the number dialed. This means "For any number beginning with 516, start processing after 10 digits are dialed".
Figure 2-19 Defining fast dialing
As shown in Figure 2-19, above, you can define a lower and an
upper limit for the sequence defined: line 3 of this example means:
"if a the digits dialed begin between 012 and 014, start processing
after the 15th digit is entered". Line 4 of htis example states: "if the
first three digits are between 050 and 054, start processing after
10 digits".
Programming Fast dialing series are defined in eManager under
LCR Global Definitions, on the FAST DIAL screen (D-F). This screen
has three fields:
Lower limit: enter up to eight digits to indicate the lower end of a
series of numbers to be analyzed. This field means that whenever
the sequence defined here is dialed, the system should wait until
the number defined in the Dialed number length field is reached.
Upper limit: enter up to eight digits to indicate the upper end of a
series of numbers to be analyzed. This field is optional: you may
leave it blank to indicate that any sequence of digits beginning
with those deifned in the Lower limit field must be analyzed.
Dialed number length: when the kength of the digits dialed
reaches this value, the system will know the user finished dialing
and processing can begin.
2-24
Section 2: SYSTEM FEATURES
2.25 GAP
TELEPHONE
SUPPORT
Release e2e-1.2
Description The AdvanceIP system supports now third-party
Digital Enhanced Cordless Telecommunications (DECT) cordless
telephones compliant with the Generic Access Profile (GAP) air
interface standard. These telephones can be connected to the
AdvanceIP and benefit from the following AdvanceIP features:
•
•
•
•
•
Basic calls;
CID (caller ID display)
Fixed button for Conference and Call Transfer;
One programmable key for all available AdvanceIP features;
Call progress tone (ring back tone and busy tone).
Conditions and limitations GAP stations require a license.
The maximum number of GAP extensions that can be defined is:
96 for 128-port systems, 256 for 384-port systems, and 500 for
1000-port systems.
Programming Up to 11 different profiles (Connegy (Avanti 3040),
GAP1 – GAP10) can be defined for GAP stations. Following are the
currently available profiles for supported commercially available
GAP handsets:
Table 2.2 GAP telephone profiles
Avanti 3040
Connegy
Kirk 4020
GAP3
Siemens Gigaset C100
GAP1
Siemens Micro 4010
GAP1
Philips/BOS HLBB 6700
GAP2
Voxtel PROFI 1500
GAP1(1)(2)
Binaton MD 1500
GAP1(1)(2)
Binaton Activity 1000
GAP1(1)(2)
Voxtel Active 1000
GAP1(1)(2)
Panasonic KX-TCA151RU
GAP5(3)
Remarks:
1 CID name displayed partially, or not at all.
2 Incoming ring in VOXTEL and Binaton handset stop after seven
rings.
3 Not yet implemented.
On the SYSTEM CONFIGURATION/CARD CONFIGURATION-MCC
EDITING screen (Y-S-F9) define the appropriate serial number and
profile type for each GAP telephone, as shown in Figure 2-20:
2-25
76-110-0690/I, Issue 2
Figure 2-20 Defining GAP profiles for cordless exensions
Define a map profile of DCT type in the Station Fetaures/Station
Maps Definition/Programmable Keys Map ((F-P-F9), as shown in
Figure 2-21, below.
NOTE
Buttons 8 and 9 in the default DCT map are not
applicable to GAP profiles GAP1 to GAP10.
Figure 2-21 DCT station map definition
2.26 LANGUAGES ON
DISPLAY
TELEPHONES
2-26
Release 7.20
Description This programmable option enables the administrator
to activate system prompts on display telephones in either English,
Spanish or French. A feature code will activate the language of
your choice for system prompts (Visual List, Dial by Name and CID
List are not translated).
Section 2: SYSTEM FEATURES
Programming At eManager, use the following path: System
Parameters - Function Access Codes (S-F). Enter the desired function codes for Language: 1 (English), Language 2 (Spanish) and
Language 3 (French).
NOTE
The above Language function codes are valid for the
USA. Function codes are factory-allocated to
languages on a country-by-country basis.
2.27 MDN G ROUP
IMPROVEMENTS
Release e2e-1
Description Prior to e2e-1, a member of a Key MDN group could
not dial that MDN group number. Now it is possible to be a member of a Key MDN and access the MDN group.
With the MDN enhancements in e2e-1, you will also be able to
program a PBX station as a member of a Key MDN group.
2.28 MEMORY
BUTTON ON
ATTENDANT
CONSOLE
Release e2e-1
Description It is now possible to program a memory button on a
DSS/BLF add-on unit.
Prior to e2e-1, only Speed Dial buttons, Automatic Redial buttons
and Extension Numbers could be programmed on an add-on console. The memory button can be used for DSS/BLF and can be
programmed from the eManager or the Attendant Console.
2.29 MULTI NIGHT
MODES
Release e2e-1.2
Description You can define more than one Night mode. There
will be four Night modes. These are controlled automatically by
means of a pre-programmed time schedule, or manually, by
means of programmed buttons. The modes affect the routing of
incoming calls and the COS of stations and trunks.
The Night modes are associated, as in previous versions, with an
attendant position. The stations, trunks and DID numbers should
be allocated to an attendant position to be affected by the Multi
Night modes.
For compatibility with previous versions, the Night1 mode is parallel to the old single Night mode. During upgrades all the old Night
keys and routing will be under Night1 mode. Configuration does
not need to be changed after upgrading the system to e2e 1.2.
All other features (other than call routing or COS), will operate in
Night2.. Night4 like in Night1. Examples: Recall night time (same
for all night modes), DISA night dialing (places the attendant position into Night1 only).
2-27
76-110-0690/I, Issue 2
The Multi Night feature affects the emaGEN in the following way:
When a Night mode is activated, the corresponding button will
light up.
If the user defines the AdvanceIP to control the emaGEN night
modes, the allocation will be as follows:
•
•
•
•
•
•
Day (AdvanceIP) = Day (emaGEN);
All Nights (AdvanceIP) = Night (emaGEN).
All operations that are currently defined in emaGEN for Night
mode are duplicated for Night2-4 modes. (e.g.: different
greeting, Attendant, etc).
Night3 = Night
Night4 = Night (future option, currently behaves like Night1]
The Emergency option of the emaGEN has a different context
than the night modes.
Night buttons may be defined for attendant positions and for the
maps of other stations. The available buttons are: Night, Night2,
Night3 and Night4. When one of the buttons’ LED is lit, the attendant position and all its associated stations and trunks are in the
corresponding Night mode. If none of the buttons are lit – it
means the mode is now Day.
A station user may press one of the Night buttons and set the
attendant position to the appropriate Night mode. When a Night
mode button is pressed, the attendant position exits the old mode
and enters the new mode (Only one Night LED may be lit). Pressing an already lit Night button means exiting all Night modes and
returning to Day mode.
Another way to exchange Day/Night modes is switching automatically according to a predefined schedule. See Programming for
instructions on how to do this.
Some new screens have been added to the eManager, under "System Profiles". These are:
Route profile – The user can define different route destinations for
calls of Day/Night1 through Night4. These Route Profiles may be
referred from all eManager screens where Day-Night routing columns exist (i.e. for private trunks, trunk groups, and DID numbers).
Instead of a specific destination, the user may route his call to one
of the new Route Profiles.
COS Profile – The user can define different COS for Day, Night1 …
Night4. In the STATION ATTRIBUTES screen and in all TRUNK/DID
screens, the user may define a COS Profile instead of the regular
COS.
Conditions and limitations This feature requires a license.
Programming For each Day or Night period, and for each attendant, you can define:
2-28
Section 2: SYSTEM FEATURES
•
•
•
A Class of Service that will determine the behavior of that
attendant during each Day/Night period;
A routing plan for incoming calls will be routed during specific
Day or Night periods;
Time schedules for Day and Night periods to become effective.
Setting COS profiles for Day/Night periods
A COS profile is a combination of classes of service to be applied to
a specific set of Day/Night periods. After defining classes of service
as required, you must apply them to specific Day/Night profiles,
and associate these profiles with specific extensions. To do so, proceed as follows:
From eManager:
1. At the STATION FEATURES/CLASS OF SERVICE screen (F-C)
define classes of service as appropriate
2. You can define a COS profile using the SYSTEM PROFILES/COS
PROFILE screen (O-C). Up to 60 COS profiles can be defined.
Figure 2-22 The COS PROFILE screen
3. Apply the profile to selected extensions and attendants
through the STATION FEATURES/STATION ATTRIBUTES screen
(F-A), as shown in Figure 2-23, below.
2-29
76-110-0690/I, Issue 2
Figure 2-23 Applying a COS profile to an extension’s
Day and Night service
Programming routing profiles for Day/Night periods
A routing profile is a combination of trunk and trunk group routing
schemes for a set of Day/Night periods. To define and apply Day/
Night routing profiles:
Figure 2-24 Defining Day/Night routing profiles
You can route incoming calls to a station or MDN, to a Meet Me
Conference number, a hunt group, a speed dial bin or a routing
list.
After defining routing profiles, you may associate them to specific
DID numbers on eManager’s DID ROUTING screen (R), as shown
in Figure 2-25, below.
2-30
Section 2: SYSTEM FEATURES
Figure 2-25 Attaching Day/Night routing profiles
to DID numbers
Defining Night buttons
You define Night buttons as you would any other Avanti station
button, by adding it to a station map. To do this, open the STATION FEATURES/STATION MAPS DEFINITION/PROGRAMMABLE
KEYS MAP screen (F-P-F9), and insert the appropriate button definition (NG, NG 2, NG 3, NG 4) on the desired button locations.
Figure 2-26 Defining Night buttons
on the Avanti Executive station map
Scheduling Day/Night periods in advance
Day and Night periods can be planned in advance to be activated
automatically according to a predetermined schedule. To do so,
you define day plans, which will determine in detail the Day/Night
schedule through the day and time periods through which a cer2-31
76-110-0690/I, Issue 2
tain Day/Night schedule will be effective. Finally, you can apply
both the day plans and the time periods to determine for long
periods beforehand how will the Day/Night schedule be activated.
Following are the steps involved in defining Day and Night schedules.
1. Defining a day plan
A day plan is a schedule for switching Day and Night modes along
a single day. You define times of the day and the Day or Night service the attendant using a specific plan will switch to. Each Day
Plan can include up to six switches between modes.
Day plans are defined through the SYSTEM PROFILES/DAY PLAN
screen (O-O), as shown in Figure 2-27, below:
Figure 2-27 Day Plan definition
2. Defining period plans
You can define periods longer than one day during which a specific
day plan will be applied. To do so, use the SYSTEM PROFILES/
PERIOD DEFINITION screen (O-P) as shown in Figure 2-28, below,
to program dates for day plans to be applied:
NOTE
Clicking on a field of the PERIOD DEFINITION screen
will display a monthly calendar. You can scroll forward
or backward through the calendar by clicking the
arrows at the top of the calendar box.
2-32
Section 2: SYSTEM FEATURES
Figure 2-28 Defining Time Periods
3. Planning long-term schedules
Having programmed day plans and time periods, you can
combine them to plan ahead long-term Day/Night schedules.
Using the SYSTEM PROFILES/ATTENDANT YEAR PLAN screen
(O-Y) as shown in Figure 2-29, you can determine, for each
attendant, up to 15 day plan-time period pairs.
If there are exceptions to time periods (for example if a day
plan is to be applied every day from May to September excepting Sundays) you can apply plan days to specific days of the
week, instead of time periods. When applying a specific time
schedule, the system will check first if the current date is
included within a specific time period, then if the day of the
week has been planned as an exception.
2-33
76-110-0690/I, Issue 2
Figure 2-29 Setting up long-term Day/Night schedules
2.30 MULTIPLE
LANGUAGE
SUPPORT
Release 7.34
Description An AdvanceIP system can be programmed to operate in three different languages, chosen from a selection of ten
languages, according to organizational needs.
This feature is especially useful to international companies or organizations working with a multilingual population.
The text on telephone set displays can appear in one of the three
programmed languages. The user of an Avanti telephone set can
select the preferred language by entering a feature code.
2.31 MULTIPLE
PROFILES
Release e2e-2
Description Several system parameters and timers are now available per COS Profile. This is relevant for parameters and timers
related to stations and trunks. To get a special timer or system
parameter the programmer must associate to the specific station,
trunk/trunk group or DID number, a specific COS profile (see
above), and to define a special timer/system parameter for that
COS Profile.Note that COS is now available for Analog Trunks too
(Private and TG).
Conditions and limitations This new feature is not controlled by
any special licensing, and is available for every e2e-1 system.
Programming There are four new screens in eManager, under
the "System Parameters" entry:
Trunk Profile Parameters which refer the programmer to Trunk Timers and to Trunk Parameters (these two screens contain timers and
parameters related to trunk calls functionality), and Station Profile
Parameters which refer the programmer to Station Timers and Station Parameters (these two screens contain timers and parameters
related to station calls and station functionality).
2-34
Section 2: SYSTEM FEATURES
The functionality of all these timers and parameters is not
changed. The only difference is that now they may be configured,as per COS Profile.
The trunk timers are:
Attendant recall time, Day recall time, Night recall time, 1st digit
timeout, Hold time, Open loop time, Patch time, Patch recall time,
TK ATT ring time.
The trunk parameters are:
Send elapsed time after ring tone stopped, trunk to trunk connection.
The station timers are:
Call forward no answer time, max inter digit dialing time, Preferred
connection time, TCOS time, Waiting for next char, Waiting tone
timeout.
The station parameters are:
Call mode, Memory key call mode, Display CID name, Flash mode.
2.32 MUTE
IMPROVEMENT
Release: e2e-1
Description: Until now, pressing the [MUTE] button on an
Avanti station would mute the microphone. From this version,
pressing [MUTE] while on a handset conversation will mute the
handset.
Programming: No programming is necessary.
2.33 NETWORK
ENHANCEMENTS
The networking capabilities of the AdvanceIP systems have been
enhanced to include the following network features:
•
•
•
•
Digital Private Network Signaling System (DPNSS) support;
QSIG support;
Automated Attendant/ImaGEN network enhancement;
NI2 (National ISDN 2) protocol support for PRI line cards in USA.
For a detailed description of these features, see Private Networks
Between Telephone Systems, Section 3.
2.34 NEW SYSTEM
DEFAULT F ILE
Release e2e-1
Description When building a system configuration from the
default file, the programmer was required to remove parameters
that no longer applied to most Telrad Connegy systems. In the
new system default configuration file, the ELD has been replaced
with a ULD, system timers have been updated to commonly used
values and an Attendant position is no longer programmed.
These changes will make it easier for the system programmer to
create a new .CFG file.
2-35
76-110-0690/I, Issue 2
Also in e2e-1 an empty .CFG file has been included in the eManager. This allows a new .CFG file to be created with no cards preprogrammed in the CARD CONFIGURATION screen.
2.35 NEW SYSTEM
PASSWORD
Release e2e-1
Description In e2e-1 no longer is there a backdoor password for
the Telrad AdvanceIP system. If a password is forgotten, a system
password string must be given to Technical Support in exchange
for a password key code that will allow you to enter the system
programming.
Programming From the System Terminal Main Menu, enter 1 for
System Password Programming.
Figure 2-30 The System Terminal Main Menu
From the Password Main Menu enter 2 to Get System String.
A 40-character alphanumeric code will be printed to the screen.
This code must be given to Technical Support in exchange for a
key generated password code (27-character alphanumeric code).
2.36 NEW SYSTEM
SECURITY
Release e2e-1
Description Starting with Release e2e1, a single password is
required for all password-protected operations.
The initial value of the system password is Carriage Return. It is
strongly recommended to change the default value after installation is complete. This change allows the Technician to access all
programming, System Administration screens and Debugger with
the same password.
If, after you have changed a System Password, you have misplaced
or forgotten the password, Telrad Connegy Technical support will
2-36
Section 2: SYSTEM FEATURES
be able to provide you with a new system password. By using the
new System Password menu, you will be able to provide Tech Support with a unique password string enabling them to assign a new
password for the system.
NOTE
The eManager password has not changed.
2.37 NI2 SUPPORT
FOR THE PRI
Release 6.07.
Description All systems support now NI2 protocol for the Primary
Rate ISDN lines. If you are installing a PRI with NI2 protocol please
contact the Field Service department to confirm that the correct
firmware is installed on the PRI card.
2.38 PHONE BOOK
Release 7.20.
Description The Phone Book feature enables AdvanceIP system
users, with Avanti display telephone sets, to enter, delete, revise,
save in memory, search for, and dial selected name and telephone
number entries.
Two types of Phone Book can be utilized:
•
•
A Private Phone Book, including the private list of names and
telephone numbers selected exclusively by each user in the
system, for that user’s convenience.
A System Phone Book, containing a series of up to 10 separate
lists, each of which includes a logical group of names and
telephone numbers.
Conditions and limitations Avanti telephone sets with a display
can use the Phone Book feature.
Analog family telephone sets and all telephone sets without display cannot access the Phone Book feature.
When entering the number of a Private or System Speed Dial bin,
make certain to include the lead zeros. For example, if the system
is programmed for two-digit bin numbers, for bin 1: enter 01; if the
system is programmed for three-digit bin numbers, for bin 1: enter
001.
In order to access the Phone Book feature on a telephone set that
has no softkeys, an available programmable button, on that set,
must be defined for this purpose in system administration.
The maximum permissible length of Phone Book entries is as follows:
•
•
•
list name -- 10 characters;
entry name -- 16 characters;
entry telephone number -- 16 digits.
2-37
76-110-0690/I, Issue 2
The maximum permissible number of entries in system Phone
Book lists is the actual system number of speed dial numbers available to the user(s), as defined in system administration programming.
Phone Book maintenance The system speed dial group programming station is designated to maintain each system Phone Book
list. Maintenance includes defining new entries and updating or
removing existing entries. All other users given access to a system
phone book list will not be allowed to make changes to the list,
but will be able to search for and dial that list’s names and numbers.
Maintenance of each system phone book list can be done, either
from the authorized user’s telephone set or from the system
administration PC.
In a private Phone Book list, however, the individual user is solely
responsible for new entries, as well as entry updating and removal.
The Phone Book feature is available for any Avanti telephone sets
with displays.
Operation Depending on the type of telephone set and the facilities it has, the user can activate Phone Book in one of the following four ways, by:
•
•
•
•
Pressing the {PHONE BOOK} softkey on Avanti 3025 and
Avanti 3020 telephone sets, and on Avanti Executive set with
expanded display;
Pressing the programmed [PHONE BOOK] button on all
Avanti display telephone sets;
Dialing the Phone Book FNP code on all Avanti display telephone
sets;
Pressing the fixed [PROGRAM] button and dialing a free speed
dial bin number on all Avanti display telephone sets.
The user can activate Phone Book dialing only if the telephone set
is in the idle state, or during speed dial programming, but not during a telephone conversation.
However, the Phone Book can be used to enter, update and
remove names and telephone numbers, either when the telephone set is in the “idle” state, or, during a telephone conversation.
The user can dial the desired party by alphabetic dialing -- dial by
name -- or by selecting the desired party from the display page of
the Phone Book list.
Phone Book entries
Each name entry defined can contain up to 16 characters -including letters, digits and the following three symbols: underscore, slash, and space.
2-38
Section 2: SYSTEM FEATURES
The Phone Book dialing approach assures unambiguous name
entry. Most dialpad buttons already commonly represent four
characters, including three letters and one digit. With the addition
of the underscore, slash, and space symbols, as well as special characters for foreign languages (in selected countries), some dialpad
buttons may be used to represent up to five characters. Therefore,
when pressing each telephone dialpad button, it may be necessary to press the button once, or a series of times in rapid succession, as shown in Table 2.3.
With each press of the dialpad button, the corresponding character -- letter, number, or symbol -- appears on the telephone set
display.
Table 2.3 Phone Book Dialing Equivalents
dialpad
number
for the following character -- press the dialpad button
the following number of times, rapidly
one
two
three
four
1
1
_
"space"
/
2
A
B
C
2
3
D
E
F
3
4
G
H
I
4
5
J
K
L
5
6
M
N
O
6
7
P
Q
R
S
8
T
U
V
8
9
W
X
Y
Z
0
0
five
7
9
Each telephone number defined can contain up to 16 digits.
The names in both private and system Phone Book lists are sorted
alphabetically.
As indicated in Table 2.4, the number of the entries that can
appear on a telephone set display varies with the telephone
model. Each entry occupies one line on the display.
Table 2.4 Phone Book Display
Telephone model
Number of
Phone Book
entries displayed
Avanti 3025
6
Avanti 3020
3
Avanti 3015D
1
2-39
76-110-0690/I, Issue 2
The user can search the Phone Book for a name, a telephone
number or a speed dial bin, by:
•
•
•
scrolling display pages;
pressing dialpad buttons corresponding to the name sought;
a combination of the two methods.
Caller Identification -- automatic search The type of Caller Identification for an incoming call depends on the type of outside line on
which it arrives -- either Caller Identification, Calling Line Identification, or Automated Number Identification -- appears on the called
telephone set display. By default, the name of the caller will automatically be searched for in all Phone Book lists, and -- if it has
been defined in Phone Book -- the name will appear on the called
telephone set display. If no name has been defined, the calling
number will appear.
2.39 PRI NAME
Release 7.34
Description A PRI circuit supporting NI2 protocol can now support PRI name (SP-PR). Prior to Version 7.34, the AdvanceIP systems only supported CLIP number on incoming calls. Now, if the
PRI provider also supports CID name, the name will be presented
to all display stations.
Conditions and limitations The system will provide CID Name
or Number but not both at the same time.
2.40 REDIAL FROM
IDLE
Release e2e-1
Description When using the [REDIAL] button prior to e2e-1, a
station user had to seize an outside line and then press redial to
access the last number stored. With e2e-1, a station user is able to
press only the redial button to complete a call with the stored
number. The redial feature will redial all external numbers and networked calls.
NOTE
The original redial mode is available by setting Custom
Parameter 10 to a value of 1.
2.41 SLT
NEAR-E NDDISCONNECT
RECOGNITION
Release 7.34
Description This feature addresses the common problem of conversations involving SLT devices, such as fax machines and
modems, where the other side hangs up. Previously, these devices
remained open, as they could not sense the dial tone on the line.
SLT devices can now detect that the other end of an internal or an
external (on CO or PRI lines) conversation has disconnected. When
the AdvanceIP system’s control detects that the other end to a
conversation with an SLT extension (SLT or fax machine) has disconnected, it cuts off the line for a brief period (Near-End-Discon-
2-40
Section 2: SYSTEM FEATURES
nect time). The SLT or fax machine sense the disconnect and can
act accordingly, usually by hanging up.
Programming On the eManager STATION FEATURES/STATION
ATTRIBUTES screen (F-A), SLT devices should have the Near End
Disconnect parameter set to Yes, as shown in Figure 2-31, below:
Figure 2-31 Programming the Near End Disconnect
parameter
You can also program the Near End Disconnect Time that the system will cut off the line to indicate a Near End Disconnect to the
SLT device. The Near End Disconnect Time is programmed on the
SYSTEM PARAMETERS/SYSTEM TIMERS screen (S-T):
Figure 2-32 Programming the Near End Disconnect Time
2.42 SOFTWARE
DOWNLOADING
Release 7.02
Description Software can be downloaded to the Avanti
Collection telephone sets and the Avanti DSS unit, except for the
2-41
76-110-0690/I, Issue 2
Avanti 3000 telephone set. The software download can be used to
update the firmware version in the telephone.
Appropriate software can be:
•
•
selected for each type of telephone set that supports the
software downloading function
and
downloaded to the telephone set.
Software Download is a separate PC software package which runs
under Windows.
NOTE
The Software Download software is currently
distribiuted as part of the eManager package.
Software downloading can be carried out to one of a variety of
individual destinations, or can be "broadcast" to composite destinations, such as the following:
•
•
•
all applicable Avanti telephone sets in the system -- that is,
excluding the Avanti 3000 telephone set;
a list of specific telephone sets -- for example, for telephone
set extension DNs 200, 240, 300, and 334.
a telephone set DN -- for example, only telephone set
extension DN 224;
Download programming can be performed online, for immediate
implementation -- without disrupting system operation -- or
offline, for downloading at a scheduled later time.
An initial list of resources capable of receiving a download is prepared by the software downloading program, and then modified
by the user.
Following each download operation, the program advises the
operator whether the software downloading has succeeded for
each unit, and if not the reasons for its failure.
The Software Downloading program maintains a running history
of the operations that have been carried out.
The Telrad Connegy AdvanceIP Gateway software, installed on a
PC connected to the MPD card of the AdvanceIP system, enables
external applications to access resources in the AdvanceIP system.
The AdvanceIP Gateway software supports communication
between the external application and the AdvanceIP system
resource.
The AdvanceIP Gateway and Software Download Manual explains
how to install the AdvanceIP Software Download and AdvanceIP
Gateway package, how to download software upgrades to
AdvanceIP system firmware, and how to use the AdvanceIP Gateway. It provides troubleshooting and error message indication
2-42
Section 2: SYSTEM FEATURES
tables to assist in resolving problems that may be encountered
when using the AdvanceIP Software Download or AdvanceIP
Gateway. See also Release 7 of the DIGITAL Family of Systems
Administration, Installation and Upgrade Addendum.
Conditions and limitations The following system resources can
receive software downloading:
•
•
2.43 SPEED DIAL BIN
ENHANCEMENT
Avanti telephone sets, except for the Avanti 3000 telephone
set;
Avanti DSS units.
Release 7.34
Description A speed dial bin, containing the user’s personal
speed dial list or any of the system speed dial lists, can contain not
only the telephone number corresponding to the speed dial number, but also the name of the person at that telephone number.
The speed dial lists, expanded to include names, now serve as the
Private Phone Book and System Phone Book lists.
2.44 SYSTEM SPEED
DIAL BUTTON
Release e2e-1.2
Description Avanti and i.Picasso station buttons can be programmed for system speed dial access.
This feature is especially suited to enable the System Administrator
to easily enable extension access to speed dial numbers and special applications.
Programming System speed dial buttons are programmed
through the STATION FEATURES/PROGRAMMABLE KEYS screen
(F-P-F9-F10) in eManager.
2.45 TIME Z ONE
COMPLIANCE
Release e2e-1.2
Description On IP extensions (i.Picasso, Avanti 3015ip and
3000ip) and on remote stations such as Avanti telephones connected through Helix, the AdvanceIP system will adjust the display
and alarm times to the time zone of the station’s physical location.
Example
Assume an AdvanceIP system is installed in Boston with an i.Picasso extension in Chicago. If the i.Picasso sets the alarm to 10:00
AM, the alarm will sound at 11:00 AM Boston time.
Programming For IP extensions, the Time Zone parameter is set
through TVSe programming on the Web Portal Preferences tab
(see Figure 2-33, below).
2-43
76-110-0690/I, Issue 2
Figure 2-33 Setting the Time Zone through the Web Portal
For stations connected to a Helix gateway, the time zone is programmed as follows:
*
1. Press [ ] and [#] together to enter programming mode.
2. Press {Time Zone}.
3. Enter the time difference. Legal values are -23 to +23 (hours).
NOTE
Use the [Lo/Hi] button to set the relevant value.
4. Press [#] or {Save} to save the value in the flash memory.
5. Go offhook and then onhook in order to exit the programming mode. The station automatically resets itself.
2.46 UNIVERSAL
OPERATING
CODE
Release 7.34
Description The Universal Operating Code allows one AdvanceIP
station to activate certain features on another AdvanceIP station.
The features that are programmable through the Universal Operating Code are:
•
•
•
•
•
ACD login/logout;
Alarm (activate and cancel);
Call Forward;
DND;
Travel COS.
The Universal Operating Code can be activated from any telephone, regardless of whether it has a display or not.
Operation By default, the Universal Operating Code is 86.
From any station:
1. Press [FEATURE] 862.
2-44
Section 2: SYSTEM FEATURES
If the station display shows ENTER NO:, Enter the DN of the
station you want to program;
If the station display shows ENTER ECC:, Enter the ECC
code of the station you want to program;
You will then hear dial tone
2. Press the [FEATURE] button and dial the code of the feature
you want to program (DND, Alarm, Call Forward, etc)
To cancel any of the features, follow the above steps but insert
the cancel code (#) before pressing the [FEATURE] button at
the beginning of step 2.
Programming The default code can be changed in Function
Access Codes (S-F).
2.47 UNIVERSAL
OPERATING
CODE WITH
ACD LOGIN/
LOGOUT
Release 7.34
Description With the Universal Operating Code the ACD Supervisor can log an agent in out of their ACD group and change the
ACD group that they are in.
Operation From the Supervisor station:
1. Press [FEATURE] 862.
If the station display shows ENTER NO:, enter the DN of the
station you want to lo gin
If the station display shows ENTER ECC:, enter the ECC
code of the station you want to program
You will hear dial tone
2. Press the [FEATURE] button and the ACD login code
If the station display shows ID CODE:, enter the ACD Agent
code for the station
If the station display shows ENTER NO:, you can enter
another station DN and repeat this step.
To log an ACD agent out of the group:
1. Press [FEATURE] 862.
If the station display shows ENTER NO, enter the DN of the
station you want to log in
If the station display shows ENTER ECC:, enter the ECC
code of the station you want to program
You will hear dial tone;
2. Press the [FEATURE] button and the ACD logout code
NOTE
To perform the above steps, the ACD Supervisor must
be logged in and the display of their phone must be
in normal mode. An ACD Agent can be logged out of
an ACD Group when on a call.
2-45
76-110-0690/I, Issue 2
2.48 VERIFIED
ACCOUNT
CODES
Release 7.34
Description Verified account codes can be pre-programmed for
users to insert them in order to perform outgoing calls. The system
will block outgoing calls if an illegal account code has been
inserted by the end user.
Using selected System Speed Dial Bins, you can now program Verified Account Codes to better control user dialing restrictions. An
Account Code may be programmed to regulate users access to
dialing privileges from which they are normally restricted.
Each Verified Account Code can be up to ten digits long. A name
can be assigned to the Verified Account Code for easy access
through the Phone Book. A Programming station can also be
assigned to the System Speed Dial Group/Verified Account Code
Group for easy programming and maintenance of the Verified
Account Code listing through any display station.
Operation The following two examples illustrate the way the
Verified Account Code feature operates.
Example 1
X200 is Toll Restricted from making long distance calls. If X200
needs to make a long distance call a Verified Account Code must
be entered. The TCOS for X200 is not Toll Restricted for Long Distance Calls.
·X200 presses their ACC button (feature code can be used) and
enters a Verified Account code. If the account code is correct
(matches a Verified Account Code entry), the system applies the
TCOS to X200 and allows the Long Distance call to be dialed.
·If the Verified Account Code was not valid, an error tone would be
heard and X200 would not be allowed to dial the Long Distance
call.
If X200 were to make a Local call, they would not have to enter a
Verified Account code.
Example 2
X200 has Forced Account Code programmed as YES in Class of
Service. This will prevent X200 from making any external calls without entering an Account Code.
·X200 presses their ACC button (a feature code can be used) and
enters a Verified Account code. If the account code is correct, the
system applies the TCOS to X200 and allows the call.
If the Verified Account Code is not valid, an error tone will be heard
and X200 will not be allowed to dial any external call.
Programming To program Verified Account Codes proceed as
follows:
2-46
Section 2: SYSTEM FEATURES
1. In the eManager System Parameters/System Speed Dial/System Speed Dial Groups (S-S-S), define a System Speed Dial
Group whose Verified Account Group field = Yes. All the System Speed Dial Bins in that group can now be used for Verified
Account Codes.
Figure 2-34 Defining Speed Dial Groups
with Verified Account Code
2. Program a Verified Account Code in the corresponding Speed
Dial bin.
3. On the STATION ATTRIBUTES screen (F-A) program which
Sysem Speed Dial List a particular station will acces for Verified
Account Codes.
Figure 2-35 Defining a Speed Dial Table for Verified Account Code
4. Program a Travel COS for each station that will be using Veriied Account Code. When a Verified Account Code is activated,
the Travelling Class of Service is applied to the station.
2.49 VIEW
Release e2e-1
2-47
76-110-0690/I, Issue 2
Description It is now possible to view the following information
(if relevant) during an incoming or outgoing call whether in conversation or during ringing:·
•
•
•
•
•
•
Trunk name
Trunk number
CID name
CID number
DID name
Time display
To view the above information press the {VIEW} softkey or
[TIME] button on any Avanti Station 30 during a conversation or
ringing call.
2.50 VIP LIST –
SELECTIVE DND
Release e2e-1
Description The user may designate up to five entries in her
address book to be VIP numbers which will override her DND.
Each entry has up to three numbers, so the maximal number of
VIP numbers is 15.
This application is available for all users in the system, not only IP
telephones. The i.Picasso may see the VIP numbers in the application screen.
Conditions and limitations To make this feature available a
minimum of 25 private speed dials have to be allocated to the station in eManager. Private Speed Dial bins 11—25 are reserved for
the VIP numbers.
2.51 VIRTUAL
STATION
Release e2e-1
Description This feature allows users to log into any extension of
the system as any DN designated as virtual. When a user logs in
with a virtual DN that physical station takes on all the characteristics of the virtual DN. Any routing, call forwarding, hunt groups,
DSS/BLF associated with the virtual DN appears on the station.
Three Virtual Station cards can be defined in the system:
•
•
•
ULV – Avanti Station 30
ELV – Station 20
ONV – SLT Telephones
Virtual Station Rules
An Avanti Station 30 virtual DN can log into an Avanti Station 30
physical station or a Station 20 physical station. This rule applies to
Station 20 virtual DNs as well. It is also important to note that the
station types do not have to match for the virtual station to work.
Example: At a Avanti 3015 station you can log-in a virtual DN for a
Avanti 3025. But be aware that not all of the 3025 programmed
keys will work since they physically do not exist on the Avanti 3015
station.
2-48
Section 2: SYSTEM FEATURES
•
•
•
An SLT virtual DN can only log into an SLT physical station.
A virtual DN cannot be logged in over a DPNSS Network.
A virtual DN can be logged in over the Helix.
An automatic log-out will occur if a user goes to another telephone and logs in with a DN that is already active. The physical
station will revert back to its original DN.
It will take up to a minute for a station to reset with the new DNs.
If a Virtual DN that is not logged in is called, the call will follow all
forwarding options for that station immediately. If no forwarding
options exist the caller will just hear ringing tone.
Conditions and limitations Virtual Station does not work for a
BRS Station or Synapse Station.
Operation From any physical station (Avanti Station 30, Station
20, or SLT):
1. Press [FEATURE] + Virtual Mask Log-in code.
The display shows Enter No:
2. Enter the number of the virtual DN.
After the DN is entered, the display shows Enter ECC.
3. Enter the ECC password associated with that virtual DN.
If the station is an SLT, an SLT virtual DN must be used.
NOTE
If the station does not have a display the above steps
still apply.
At this point, the station will reset and reinitialize with the virtual
DN. The station will subsequently have all the characteristics of the
virtual DN.
The physical station DN (DN assigned on ULD/UHD, ELD/EHD,
ONS/HONS) is now in reserve and can be used at another station
by following the virtual station log-in procedure. Make sure an
ECC Code is programmed for the physical station.
Logging in as a physical DN:
With the Virtual station feature you may also log in at any station
as another physical DN.
Programming There are three types of telephones that can have
virtual DNs: IP stations, Avanti Stations and Digital Stations (station
20). To designate a virtual DN for any of these types of stations
you must define a virtual station card in System Configuration –
Card Configuration (see Figure 1). Each virtual station card takes
up a slot in the system CFG but there is no physical card that must
be installed. Virtual cards can be programmed in cabinets that do
not exist.
2-49
76-110-0690/I, Issue 2
Once you have programmed the virtual station card in an available
slot, press F9 to edit the card. Program desired virtual station DN.
Select what type of station the DN is associated with. Each virtual
station DN programmed on a virtual station card will use a station
port in the system but it will not use a power port. This reduces
the total number of physical stations that may be configured and
installed by the total number of virtual stations assigned.
Figure 2-36 Defining virtual ports on a ULV card
Once you have programmed all the virtual DNs needed you must
program a log-in and log-out code:
•
System Parameters Function Access Codes
• Virtual Mask Log-in
• Virtual Mask Log-out
NOTE
Log-in code may be put on a Memory button. The
Log-out code is not programmable on a Memory
button.
On the STATION FEATURES/STATION ATTRIBUTES screen (F-A)
program the following for each virtual station:
•
•
ECC Allowed – YES
ECC Password – Any four digit combination
You may now assign any maps, features, hunt groups, call forwarding to the virtual station as you would to a physical station.
2-50
Section 2: SYSTEM FEATURES
To return to the physical DN of a station, simply enter the virtual
mask log out code or log in as the physical DN.Virtual DNs take up
station ports but not power ports.
Example
You need to work for the day in the conference room. You still
want to be able to receive all calls. Your DN is X202. The conference room phone is X250.
Programming the example
Program a Virtual Station card in the SYSTEM CONFIGURATION/
CARD CONFIGURATION screen (Y-S) (a Virtual Station card can be
one of ULV, ELV, ONV). Program Virtual Station DNs for the card.
Program a BUTTON MDN in the STATION GROUP FEATURES –
MDN GROUPS screen (I-M).
Program the MDN DN in the SYSTEM PARAMETERS/GENERAL
PARAMETERS – MDN screen (S-P) of Temporary Virtual DN.
Figure 2-37 Programming MDN DNs
The Virtual DNs programmed in the MDN group are used when a
physical station logs in as another physical station.
If a physical SLT is going to log in to another physical SLT station a
Virtual DN must be entered into the MDN group.
At X250 press [FEATURE] and the Virtual Login code.
You will enter X202 and the ECC password for X202. X250 will
reinitialize as X202. The AdvanceIP system will assign one of the
Virtual DNs in the MDN group assigned in General Parameters to
the physical station that was X202.
2-51
76-110-0690/I, Issue 2
To return X202 to its original state, just press [FEATURE] and the
Virtual Logout code. X202 and X250 will reinitialize with their original DNs.
2.52 U NIVERSAL
O PER ATING
A CCESS
Description The Universal Operating Access (UOA) feature
allows remote activation -- by an AdvanceIP system member -- of a
series of functions:
•
•
involving its own extension, while at another extension; or
involving another extension, while at its own extension.
The functions enabled by UOA to be activated remotely include:
•
•
•
•
programming and cancellation of three types of call forwarding
of internal and external calls -- known as:
• call forward;
• call forward busy;
• call forward no answer
programming of private speed dial;
activation of private or system speed dial;
Phone Book operation and entries.
Before remotely activating an applicable feature -- by means of
UOA -- at another extension, the activating extension is required
to:
•
•
•
Dial the UOA feature code;
Dial the DN of the activated extension; and
dial the ECC or Global Class of Service password of the
activated extension.
Conditions and limitations Both the activating extension and
the activated extension must be idle before UOA can be activated.
Although an Attendant can activate UOA at another extension,
the activated extension can never be an Attendant extension.
Content restrictions applicable to a remotely activated extension
will continue to apply, even if another extension attempts to override them.
Remote programming of the activated extension will remain applicable until reprogrammed or cancelled either at the activated
extension, or from a remote activating extension.
The display of the activating extension will be updated during the
remote activation process.
The LEDs and the fixed display of the activated extension will be
updated during and following the remote activation process.
2-52
Section 3
PRIVATE NETWORKING BETWEEN
TELEPHONE SYSTEMS
3.1
G ENERAL
This Section describes networking ehancements introduced to the
AdvanceIP system since Release 7.0.
The AdvanceIP systems’ networking capability enhancements presented in this secTion:
•
•
•
2.2
BLF OVER
DPNSS
utilize, in addition to the existing NAP protocol -- the Digital
Private Network Signaling System (DPNSS) and QSIG standard
digital protocols.
provide an expanded set of improved network-wide features
and services;
facilitate installation and operation of inter-system private
networks of all sizes, comprised of both Telrad Connegy’s
AdvanceIP systems, as well as telephone systems of other
manufacturers.
Release e2e-1
Description BLF buttons can be programmed for stations in a
DPNSS network. There is a maximum of 250 BLF for networked stations allowed in each system. This does not affect the number of
regular BLF buttons in the system.
A BLF buttons for a networked station can be used for busy indication, to transfer calls, or as a direct dial button to that station.
The BLF for a networked station cannot be used for Call Pickup. For
BLF over DPNSS to work each networked system must have a
unique numbering plan.
Viewing how many users programmed an extension on a BLF
button
You can view how many users on the other system have programmed a BLF over DPNSS button for a specific extension. To do
3-1
76-110-0690/I, Issue 2
so, open the Network/BLF Network/Other System Requestss
screen (N-B-R). The number of stations on the other system that
are requesting information about extensions on the local system
(i.e. have a BLF button programmed for a local system extension)
appears next to each local extension number.
The Other System Requests screen shows how many extensions
on the other system have requested information on a specific
extension of the local system. Selecting a row on the Network Station DN and pressing F9 will display a list of the network extensions requesting information on the local extension.
Figure 3-38 Requests for information from network system
Conversely, you can view how many extension in the local system
are requesting information from other systems in the network. This
information appears in the Network/BLF Network/Other System
DNs screen (N-B-O), as shown in Figure 3-39, below:
Figure 3-39 Requests for information from local system
3-2
Section 2: SYSTEM FEATURES
The Other System DNs screen shows how many extensions on
the local system have requested information on a specific extension of the other system. Selecting a row on the Network Station
DN and pressing F9 will display a list of the local extension requesting information on the network extension.
Programming In Network – Prefixes define a System ID Number.
Figure 3-40 Defining an ID number
In the Network Prefixes screen (N-P), program the Network System
ID. The BLF Memory buttons may be programmed by either the
end user or through the eManager..
Make sure that for each of the systems on the network, System
IDs are defined which are routed to the other system. This ID
number should start with the same digit as the extensions in the
other systems in the network. Thus, if the extensions in system A
begin with 4, and those in system B begin with 8, then the prefix
in system A for accessing the network should be 8, and the corresponding prefix in system B should be 4.
Figure 3-41 Programming the Network System ID
3-3
76-110-0690/I, Issue 2
3.3
DIGITAL P RIVATE
NETWORK
SIGNALING
SYSTEM
(DPNSS)
DPNSS is a British Telecommunications (BT) protocol, which is
mandatory in the UK, can provide a good private networking
option in other parts of Europe, the US, and Israel.
DPNSS works on a number of interface types -- 2M, 1.5M, as well
as some V- and X-series). It has many supplementary services
defined and already deployed, allows networking with many PBXs
from different manufacturers. Telrad Connegy selected DPNSS to
serve as the standard AdvanceIP system network protocol for
mixed networks, and as a proprietary protocol for private networks
comprised of AdvanceIP and AdvanceIP systems alone. DPNSS
operates only on PRI-type ISDN interfaces.
3.3.1 Interworking
With DPNSS, the AdvanceIP systems can serve:
•
•
3.4
FULL
NETWORKING
OVER IP
as a transit exchange between switches of other
manufacturers.
as a gateway for trunk calls that pass to the network.
Starting with Release 3, AdvanceIP systems can be connected into
IP Distributed networks. The connection is made through IP trunks
supporting the Session Initiation Protocol (SIP). All the functionality
afforded by DPNSS is also available for IP Distributed networks.
For complete information about setting up and configuring IP Distributed networks, see the AdvanceIP Guide to Voice over IP.
3.5
NETWORK
ANALOG
PROTOCOL
(NAP)
Public networking between telephone systems described in previous system releases utilizes a Telrad Connegy proprietary Network
Analog Protocol (NAP). Since this protocol facilitates the treatment
of various network call communication features in a manner satisfactory for small networks comprised of AdvanceIP systems only,
the NAP protocol will remain in service.
3.5.1 System cards supporting NAP
NAP (Network Analog Protocol) operates via the following interfaces, represented by the respective AdvanceIP system cards:
•E&M
•T1
•DC5
•E1
The availability of these cards depends on the country where the
system is installed.
3.5.2 Network-wide availability of system communication
features under NAP
The following communication features can be accessed and activated between AdvanceIP network member systems -- under NAP
-- as within an individual AdvanceIP system:
• Basic messages
• Call Forward No Answer;
• Internal Page;
3-4
Section 2: SYSTEM FEATURES
•
•
•
•
•
3.6
NETWORK
CARDS
External Page;
Call Forward;
Call Forward Busy;
Callback;
emaGEN messages
Special system cabinet cards -- supported by DPNSS or QSIG -- for
DIGITAL systems in private networks have been introduced. Cards
for both DPNSS and QSIG protocols are prefixed by the letter N,
followed by the number of connected channels, as follows:
• USA:
N12 and N24;
• ETSI:
N10, N20, and N30.
These following network cards are based on the AdvanceIP systems PRI card platform:
•
USA: PRI12 and PRI24 -- supported by any of the following
protocols:
• DMS100,;
• 4ESS (AT&T long distance);
• 5ESS (AT&T local);
• NI2 (National ISDN 2);
• ETSI: PRI30 (in the UK: also PRI10 and PRI20).
A DPNSS or QSIG networking card can be switched from one protocol to the other by changing the firmware chip.
Support protocol selection alternatives -- where applicable, as
listed above -- must be defined in system programming.
3.7
NETWORKING
FEATURES --
SUPPLEMENTARY
SERVICES
Networking features belong to two categories:
•
•
protocol independent features;
protocol dependent features.
3.7.1 Protocol independent features
Protocol independent features do not require inter-node signaling
-- between the systems that comprise the private network.
Most important among these features are:
•
•
uniform numbering plan;
and
flexible translation between public and private numbering
plans.
These features are achieved by integrating the following relevant
AdvanceIP and AdvanceIP system capabilities with the network:
•
•
•
•
LCR;
system speed dialing;
QSIG name display (see Section 3.9.1, below);
flexible DID number analysis.
3-5
76-110-0690/I, Issue 2
3.7.2 Protocol dependent features
Protocol dependent features require inter-node signaling, between
the systems that comprise the private network.
Most of these features in AdvanceIP systems are based on the
DPNSS protocol.
3.7.3 Feature list
Table 3.5: shows the list of private network features supported by
Release 7 AdvanceIP systems, according to the protocols with
which they comply.
Basic Call
Y
BLF
Y
Y
-
Call Back on No Answer
-
Y
-
Call Forward (Call Diversion)
Y
Y
-
Calling Line Identification Presentation (CLIP)
QSIG
Y
DPNSS*
Y
NAP
Call Back on Busy
Feature name
Y
Y
Y
Call Forward to Mailbox
Y
Y
-
Call Record
-
Y
-
Message LED
Y
Y
-
Message Retrieval from Mailbox
Y
Y
-
Voice Mail Screens
-
Y
-
Voice Memo
Y
Y
-
Conference Add-on
Y
Y
-
Hold + Transfer + Conference (3-party)
Y
Y
Y
Infinite Loop Avoidance
-
Y
Y
Interworking for Basic Call Services
-
Y
Y
Message
Y
Y
-
Name Display
-
Y
Y
Page
Y
Y
-
Centralized
voice mail
3-6
Y
QSIG
Feature name
DPNSS*
NAP
Table 3.5: AdvanceIP System Private Network Features
Section 2: SYSTEM FEATURES
Table 3.5: AdvanceIP System Private Network Features
Transit Capability
-
Y
-
Trunk Optimization
-
Y
-
•
In the UK, the DPNSS supported features are the same features
as supported on NAP, except for the addition of Call Back on
No-answer, Name Display, and Infinite Loop Avoidance and
the elimination of Page, which is considered unnecessary in the
UK.
3.7.4 Interprotocol feature names
Some of the names of supplementary services and system features
vary from one protocol to another. The following name variations
apply:
CBWF
Call Back when Free (CBWF) is also known as:
•
•
Call Back on Busy (CCB) -- DPNSS;
Completion of Calls to Busy Subscribers (CCBS) -- QSIG.
CBNU
Call Back when Next Used (CBNU) is also known as:
•
•
Call Back on No Answer (CCNA) -- DPNSS;
Completion of Calls on No Reply (CCNR) -- QSIG.
CF
Call Forward (CF) is also known as:
•
•
3.8
PRIVATE
NETWORK
MEDIA AND
CONNECTIVITY
Call Diversion (CD)
-- DPNSS;
Call Forwarding Unconditional (CFU) -- QSIG.
A AdvanceIP system will be connected to the private network in
either of the following ways:
•
•
•
digital lines running the DPNSS or QSIG protocol:
• 2M -- in ETSI domain, or
• 1.5M -- in US interfaces,
analog lines -- in the case of very small systems, where:
• a AdvanceIP-system-only network is built, and
only features available on NAP protocol are used.
3.8.1 USA
In the USA:
•
•
•
the interface for DPNSS is 1544 kbps -- 23B + D, while
standard requirements confine the D-channel to slot 24,
exclusively;
in order to answer the demands of smaller systems, a partial
span interface -- 12B + D -- will also be supported;
on DPNSS, the AdvanceIP system supports the previous set of
features, enriched with some centralized voice mail functions
(see Section 3.7.3, for a list of features supported);
3-7
76-110-0690/I, Issue 2
•
•
on NAP it is supported on E&M and T1 interfaces. The standard
requirements confine the D-channel to slot 24, exclusively.
There are no changes;
NAP will be continue to be used for existing networks, to avoid
forced upgrade to Release 7 DIGITAL systems.
3.8.2 UK
In the UK:
•
•
•
the interface for DPNSS is 2048 kbps -- 30B + D;
in order to answer the demands of smaller systems, partial
span interfaces -- 10B + D and 20B + D, as for PRI -- will also
be supported;
NAP will work on the DC5 interface, as in previous releases.
3.8.3 Other countries
In most other countries:
•
•
•
•
•
3.9
QSIG
the interface for DPNSS in most other countries is 2048kbps - 30B + D;
NAP will work on the E1 interface, as in previous releases;
on DPNSS, the AdvanceIP system supports the previous set of
features, enriched with some centralized voice mail functions
(see Section 3.7.3, for a list of features supported);
NAP will be continue to be used for existing networks, to avoid
forced upgrade to AdvanceIP systems;
Basic call on QSIG will be supported.
Release 7.34
QSIG is a standard protocol that defines signaling requirements at
a Q reference point. QSIG protocol is a multi-vendor signaling system.
3.9.1 Names over QSIG
Release e2e-1.2
Extensions connected to a network system over QSIG lines can
see the name of the network extension they are in conversation
with. This Supplementary Services feature works over both BRI and
PRI lines.
3-8
Download PDF