What’s New in
Avaya Communication Manager
for Release 3.1.X
03-300682
Issue 1.1
June 2006
© 2006 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc.
can assume no liability for any errors. Changes and corrections to the
information in this document may be incorporated in future releases.
For full legal page information, please see the complete document,
Avaya Legal Page for Software Documentation, document number
03-600758.
To locate this document on our Web site, simply go to http://
www.avaya.com/support and search for the document number in
the search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions
to the original published version of this documentation unless such
modifications, additions, or deletions were performed by Avaya.
Customer and/or End User agree to indemnify and hold harmless Avaya,
Avaya's agents, servants and employees against all claims, lawsuits,
demands and judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation to the extent
made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked
Web sites referenced elsewhere within this documentation, and Avaya
does not necessarily endorse the products, services, or information
described or offered within them. We cannot guarantee that these links
will work all of the time and we have no control over the availability of the
linked pages.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your
sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language, as well as information
regarding support for this product, while under warranty, is available
through the following Web site: http://www.avaya.com/support.
Copyright
Except where expressly stated otherwise, the Product is protected by
copyright and other laws respecting proprietary rights. Unauthorized
reproduction, transfer, and or use can be a criminal, as well as a civil,
offense under the applicable law.
Avaya support
Avaya provides a telephone number for you to use to report problems or
to ask questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site: http://www.avaya.com/support.
Contents
About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose of this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Terms and Conventions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
How to obtain Avaya books on the Web . . . . . . . . . . . . . . . . . . . . . . .
14
How to order documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
How to comment on this book . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
Chapter 1: What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
Release 3.1.X new features and enhancements . . . . . . . . . . . . . . . .
Called number added to display for Toshiba SIP telephone . . . . . . . .
Clearer display for trunk ID . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced list measurement occupancy command for duplicated servers
Faster backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List configuration by circuit pack . . . . . . . . . . . . . . . . . . . . . .
Manual Local Survivable Processor takeover . . . . . . . . . . . . . . . .
More info from list survivable-processor command . . . . . . . . . . . .
More simultaneous calls per multipoint endpoint . . . . . . . . . . . . .
New default backup time . . . . . . . . . . . . . . . . . . . . . . . . . . .
New reason code for attendant vector . . . . . . . . . . . . . . . . . . . .
Notification about 802.1q changes . . . . . . . . . . . . . . . . . . . . . .
Prompt alarm for C-LAN outage . . . . . . . . . . . . . . . . . . . . . . .
T.38 protocol for faxing . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tildes to hide names in directory . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
17
17
18
18
18
18
18
19
19
19
19
19
19
20
Release 3.1 new features and enhancements . . . . . .
802.1x multi supplicants . . . . . . . . . . . . . . .
Administrable size for Receive Buffer TCP Window
Administrable time-out for inactive SAT sessions .
Alarm messages for unregistered LSPs . . . . . . .
ASAI support for Aux Work reason codes . . . . .
Avaya Video Telephony Solution . . . . . . . . . .
Banner displayed to warn of reset . . . . . . . . . .
Block circuit pack installation if wrong suffix . . . .
Block CMS Move Agent events . . . . . . . . . . .
Call Log modifications . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
20
20
20
21
21
21
21
22
22
23
23
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Issue 1.1 June 2006
3
Contents
Clear the display of collected digits . . . . . . . . . . . . . . . . . . . .
Compress restart escalation sequence . . . . . . . . . . . . . . . . . .
Connection-preserving upgrades . . . . . . . . . . . . . . . . . . . . .
Detecting 655A power supply failures . . . . . . . . . . . . . . . . . . .
Dial backup over external ISDN modem . . . . . . . . . . . . . . . . . .
Direct-region preference for IP telephones . . . . . . . . . . . . . . . .
Duplicate power supply failure upgraded to alarm status . . . . . . . .
Enhanced feature integrations for Avaya Modular Messaging . . . . .
Enhanced password security . . . . . . . . . . . . . . . . . . . . . . .
Enhanced TN2602AP circuit pack . . . . . . . . . . . . . . . . . . . . .
Bearer signal duplication . . . . . . . . . . . . . . . . . . . . . . . .
Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reduced channels with duplicated TN2602AP circuit packs . . . .
Support of T.38 fax relay . . . . . . . . . . . . . . . . . . . . . . . .
V.32 modem relay . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise Mobility User . . . . . . . . . . . . . . . . . . . . . . . . . .
How Enterprise Mobility User works . . . . . . . . . . . . . . . . . .
Enterprise Survivable Server increase . . . . . . . . . . . . . . . . . .
Extended survivability to G250 Media Gateway . . . . . . . . . . . . . .
Gateway trunk preference selection . . . . . . . . . . . . . . . . . . . .
HTTP server on S8500 Media Server . . . . . . . . . . . . . . . . . . . .
Increased Classes of Restriction . . . . . . . . . . . . . . . . . . . . .
Increased text fields for feature buttons . . . . . . . . . . . . . . . . .
Increased quantity of NCA TSCs and FTSCs . . . . . . . . . . . . . . .
Increased trunk members for IP signaling groups . . . . . . . . . . . .
Incremental filesyncs . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Gateway Alternate Routing calls over Inter-Gateway Connections
Listen-only FAC for service observing . . . . . . . . . . . . . . . . . .
Local ringback administration . . . . . . . . . . . . . . . . . . . . . . .
More BRI Trunk circuit packs . . . . . . . . . . . . . . . . . . . . . . .
More Leave Word Calling messages . . . . . . . . . . . . . . . . . . . .
More than nine static routes allowed . . . . . . . . . . . . . . . . . . .
Music on hold played from nearest source . . . . . . . . . . . . . . . .
Notification about 802.1q changes . . . . . . . . . . . . . . . . . . . . .
Parameterized data for NSF . . . . . . . . . . . . . . . . . . . . . . . .
Prepend '+' to calling number . . . . . . . . . . . . . . . . . . . . . . .
Processor Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjuncts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.248 and H.323 registration . . . . . . . . . . . . . . . . . . . . . .
S8500 Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . .
QSIG path optimization simplified . . . . . . . . . . . . . . . . . . . . .
4 What’s New in Avaya Communication Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
24
24
24
24
24
25
25
25
25
26
26
27
27
27
28
28
28
29
29
30
30
30
30
30
31
31
31
32
32
32
32
32
32
33
33
33
33
34
34
34
35
Contents
QSIG redirection display is administrable . . . . . . . . . . . .
R2-MFC support on G250 Media Gateway . . . . . . . . . . . .
Remote upgrades for branch gateways . . . . . . . . . . . . .
Rerouting and path replacement by trunk group . . . . . . . .
Reset IP stations by subnet enhancement . . . . . . . . . . .
Secure Shell and Secure FTP . . . . . . . . . . . . . . . . . .
Applicable platforms or hardware . . . . . . . . . . . . . .
Using Secure Shell to retrieve backup information . . . . .
Security of IP telephone registration/H.323 signaling channel
Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature Interactions . . . . . . . . . . . . . . . . . . . . . .
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . .
Shadowing data on servers . . . . . . . . . . . . . . . . . . .
SIP Enablement Services . . . . . . . . . . . . . . . . . . . . .
Site data warning when adding station to TTI port . . . . . . .
Support caller ID on call waiting for MM711 and MM714 . . . .
Support for Enterprise Linux . . . . . . . . . . . . . . . . . . .
Translations file timestamps . . . . . . . . . . . . . . . . . . .
Web firewall settings simplified . . . . . . . . . . . . . . . . .
Web interface for synchronization plan . . . . . . . . . . . . .
Web upgrade tool checks file corruption/presence . . . . . .
Web upgrade tool common media module option . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
35
35
35
36
36
36
36
37
37
38
39
39
39
40
40
40
40
41
41
41
41
41
Release 3.0 new features and enhancements . . . . . . . . . . . . . .
Administrable Periodic Registration Timer . . . . . . . . . . . . .
Alarm log entries for MG-ICC . . . . . . . . . . . . . . . . . . . . .
Analog bearer frequency for IP encoding . . . . . . . . . . . . . .
Application Enablement Services . . . . . . . . . . . . . . . . . .
Software-only option . . . . . . . . . . . . . . . . . . . . . . .
Bundled server option . . . . . . . . . . . . . . . . . . . . . .
Adjunct Switch Application Interface . . . . . . . . . . . . . .
CVLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEFINITY LAN Gateway . . . . . . . . . . . . . . . . . . . . . .
Device and media control API . . . . . . . . . . . . . . . . . .
System Management Service . . . . . . . . . . . . . . . . . . .
Telephony Service . . . . . . . . . . . . . . . . . . . . . . . .
User Service . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto fallback to primary for H.248 media gateways . . . . . . . .
Button pushes in list trace station command . . . . . . . . . . . .
Connection preserving failover/failback for H.248 media gateways
Connection preserving upgrades for duplex servers . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
42
42
42
42
42
43
43
43
43
44
44
44
44
44
45
46
46
47
Issue 1.1 June 2006
5
Contents
Disable active logins . . . . . . . . . . . . . . . . . . . . . . . . .
Display for bridged no-ring calls . . . . . . . . . . . . . . . . . . .
E-mail backups no longer supported . . . . . . . . . . . . . . . .
Emergency calls from unnamed IP endpoints . . . . . . . . . . .
Enhanced quality for Music On Hold . . . . . . . . . . . . . . . .
Enterprise Survivable Servers . . . . . . . . . . . . . . . . . . . .
Enterprise Wide Licensing . . . . . . . . . . . . . . . . . . . . . .
Expanded Meet-me Conferencing . . . . . . . . . . . . . . . . . .
Extension to Cellular . . . . . . . . . . . . . . . . . . . . . . . . .
Improved button downloads for IP telephones . . . . . . . . . . .
Improved voice mail coverage at WAN failure . . . . . . . . . . .
Increased packet size supported . . . . . . . . . . . . . . . . . .
Integrating IP-connected port networks with direct/multi-connect
configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Gateway Alternate Routing . . . . . . . . . . . . . . . . . . .
List IP addresses for IP interface circuit packs . . . . . . . . . . .
Locally sourced announcements and music . . . . . . . . . . . .
MLPP privileges at any endpoint . . . . . . . . . . . . . . . . . . .
Modem over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More options for changing display messages . . . . . . . . . . .
More system-wide message retrieval extensions . . . . . . . . . .
Multiple SNMP trap destinations . . . . . . . . . . . . . . . . . . .
Native support of NI-BRI data . . . . . . . . . . . . . . . . . . . .
Prevent MLPP preemption of emergency calls . . . . . . . . . . .
QSIG support for Unicode . . . . . . . . . . . . . . . . . . . . . .
RAM disk for S8300 Media Server . . . . . . . . . . . . . . . . . .
Remove assigned DID . . . . . . . . . . . . . . . . . . . . . . . .
Ringback during coverage interval . . . . . . . . . . . . . . . . .
Secure Shell and Secure FTP for circuit packs . . . . . . . . . . .
Security of IP telephone registration/H.323 signaling channel . .
Serial number for license validation . . . . . . . . . . . . . . . . .
Shorter time-out for list trace ras command . . . . . . . . . . . .
Station licensing . . . . . . . . . . . . . . . . . . . . . . . . . . .
User-defined phone message files . . . . . . . . . . . . . . . . . .
Web interface from multiple IP addresses . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
47
47
47
48
48
48
49
49
49
50
50
51
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
51
52
52
52
53
53
53
53
53
54
54
54
54
54
55
55
55
56
56
56
57
57
Chapter 2: Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
Release 3.1.X hardware additions . . . . . . . . . . . . . . . . . . . . . . . . . .
G350 Media Gateway as a headquarters device . . . . . . . . . . . . . . . .
59
59
Release 3.1 hardware additions . . . . . . . . . . . . . . . . . . . . . . . . . . .
G250 DCP Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
60
6 What’s New in Avaya Communication Manager
Contents
USB support for G250 Media Gateway .
G250 DS1 Media Gateway . . . . . . . . .
MM316 HDMM for G350 Media Gateway . .
MM716 analog media module . . . . . . .
S8400 Media Server . . . . . . . . . . . . .
TN8412AP circuit pack . . . . . . . . .
S8720 Media Server . . . . . . . . . . . . .
Software Duplication . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
60
60
61
61
61
62
62
63
Release 3.0 hardware additions . . . . . . . . . . .
4621SW IP telephone . . . . . . . . . . . . . . .
4622SW IP telephone . . . . . . . . . . . . . . .
4625SW IP telephone . . . . . . . . . . . . . . .
Avaya Expanded Meet-me Conferencing Server
Converged Network Analyzer . . . . . . . . . .
DNS Resolver for gateways . . . . . . . . . . .
G250 Media Gateway . . . . . . . . . . . . . . .
Standard Local Survivability . . . . . . . . .
SP-1020A SIP business telephone . . . . . . . .
TN2602AP IP Media Resource 320 circuit pack .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
64
64
64
65
65
65
66
66
67
68
69
Chapter 3: New and changed screens . . . . . . . . . . . . . . . . . . .
71
Release 3.1 new screens
Enable Session . . .
Survivable Processor
Page 1. . . . . . .
Page 2. . . . . . .
Page 3. . . . . . .
Page 4. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
71
71
73
74
74
77
79
Release 3.0 new screens . . . . . . . . . . . . . . . . . . . . . . .
Announcement Group Board Usage . . . . . . . . . . . . . . .
Audio Group . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio Groups . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Music-on-Hold Groups . . . . . . . . . . . . . . . . . . . . . .
System Parameters Media Gateway Automatic Recovery Rule
TTI Service IP Stations . . . . . . . . . . . . . . . . . . . . . .
Virtual MAC Addresses . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
80
80
81
81
82
83
85
85
90
90
Release 3.1.X changed screens . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP-Options System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
91
91
Issue 1.1 June 2006
7
Contents
Feature-Related System Parameters . . . . . . . . . . . . . . . . . . . . . .
Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 3.1 changed screens . . . . . . . . . .
Class of Restriction . . . . . . . . . . . . . .
Class of Service . . . . . . . . . . . . . . . .
Console Parameters . . . . . . . . . . . . .
CTI Link . . . . . . . . . . . . . . . . . . . .
Enterprise Survivable Server Information . .
Feature Access Code (FAC) . . . . . . . . .
Page 2. . . . . . . . . . . . . . . . . . . .
Page 5. . . . . . . . . . . . . . . . . . . .
Feature-Related System Parameters . . . .
Page 3. . . . . . . . . . . . . . . . . . . .
Page 7. . . . . . . . . . . . . . . . . . . .
Page 9. . . . . . . . . . . . . . . . . . . .
Page 11 . . . . . . . . . . . . . . . . . . .
Page 13 . . . . . . . . . . . . . . . . . . .
Page 16 . . . . . . . . . . . . . . . . . . .
Group Paging Using Speakerphone . . . . .
Hunt Group . . . . . . . . . . . . . . . . . .
IP Interfaces . . . . . . . . . . . . . . . . . .
IP Network Region . . . . . . . . . . . . . .
IP Server Interface (IPSI) Administration . .
Language Translations . . . . . . . . . . . .
Media-Processor Status . . . . . . . . . . .
Optional Features . . . . . . . . . . . . . . .
Route Pattern . . . . . . . . . . . . . . . . .
Security-Related System Parameters . . . .
Station . . . . . . . . . . . . . . . . . . . . .
Page 2. . . . . . . . . . . . . . . . . . . .
Stations with Off-PBX Telephone Integration
Trunk Group . . . . . . . . . . . . . . . . . .
Variables for Vectors . . . . . . . . . . . . .
Vector Directory Number . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
95
95
97
98
99
101
102
103
104
104
105
107
108
109
110
112
112
113
114
117
119
120
121
122
123
124
125
125
127
132
139
142
Release 3.0 changed screens . . . . . . . . . . . . . . .
Announcements/Audio Sources . . . . . . . . . . . .
Configuration Set . . . . . . . . . . . . . . . . . . . .
Extensions To Call Which Activate Features By Name
Feature Access Code (FAC) . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
144
144
145
146
147
8 What’s New in Avaya Communication Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
93
94
Contents
Feature-Related System Parameters
Page 1. . . . . . . . . . . . . . . .
Page 3. . . . . . . . . . . . . . . .
Page 5. . . . . . . . . . . . . . . .
Page 7. . . . . . . . . . . . . . . .
Page 9. . . . . . . . . . . . . . . .
Gateway Status . . . . . . . . . . . .
Integrated Announcements/Audio . .
IP Interfaces . . . . . . . . . . . . . .
IP Network Region . . . . . . . . . .
Page 2. . . . . . . . . . . . . . . .
Page 3. . . . . . . . . . . . . . . .
IP-Options System Parameters . . .
Language Translations . . . . . . . .
List Usage Report . . . . . . . . . . .
Location Parameters . . . . . . . . .
Media-Gateway . . . . . . . . . . . .
Media-Gateway Report . . . . . . . .
Optional Features . . . . . . . . . . .
Page 1. . . . . . . . . . . . . . . .
Page 2. . . . . . . . . . . . . . . .
Page 4. . . . . . . . . . . . . . . .
Port Information . . . . . . . . . . . .
Security-Related System Parameters
System Capacity . . . . . . . . . . .
Page 6. . . . . . . . . . . . . . . .
Page 10 . . . . . . . . . . . . . . .
Vector Directory Number . . . . . . .
Page 1. . . . . . . . . . . . . . . .
Page 2. . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
148
148
150
151
151
152
153
154
154
158
158
160
161
163
164
164
165
167
168
168
169
170
171
171
172
173
174
174
175
176
Chapter 4: New and changed commands . . . . . . . . . . . . . . . . .
179
Release 3.1 new commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
add off-pbx-telephone station-mapping . . . . . . . . . . . . . . . . . . . . .
179
179
Release 3.0 new commands . . . . . . . . . . . .
add audio-group . . . . . . . . . . . . . . . . .
add moh-analog-group . . . . . . . . . . . . .
change system-parameters mg-recovery-rule
display virtual-mac-address . . . . . . . . . .
enable filexfer . . . . . . . . . . . . . . . . . .
180
180
181
181
181
182
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Issue 1.1 June 2006
9
Contents
enable session . . . . . . .
list audio-group . . . . . . .
list ip-interface medpro . . .
list moh-analog-group . . .
list tti-ip-stations . . . . . .
list usage integ-annc-board
reset media-gateway . . . .
set media-processor . . . .
.
.
.
.
.
.
.
.
182
183
183
183
183
184
184
185
Release 3.1 changed commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
change public-unknown-numbering . . . . . . . . . . . . . . . . . . . . . . .
list registered-ip-stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
186
186
186
Release 3.0 changed commands .
get boot-image . . . . . . . .
reset ip-stations . . . . . . . .
set boot-image . . . . . . . .
status ip-board . . . . . . . .
status media-processor . . .
.
.
.
.
.
.
187
187
187
188
188
188
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10 What’s New in Avaya Communication Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
About this book
Overview
Avaya Communication Manager is the centerpiece of Avaya applications. Running on a variety
of Avaya Media Servers and DEFINITY® Servers, and providing control to Avaya Media
Gateways and Avaya communications devices, Communication Manager can be designed to
operate in either a distributed or networked call processing environment.
Communication Manager carries forward all of a customer’s current DEFINITY capabilities, plus
offers all the enhancements that enable them to take advantage of new distributed
technologies, increased scalability, and redundancy. Communication Manager evolved from
DEFINITY software and delivers no-compromise enterprise IP solutions.
Communication Manager is an open, scalable, highly reliable and secure telephony application.
The software provides user and system management functionality, intelligent call routing,
application integration and extensibility, and enterprise communications networking.
Purpose of this book
This book describes the new and changed features and enhancements available with the most
recent release of Communication Manager (release 3.x) running on any of the following:
●
Avaya media servers
- DEFINITY® servers
- S8000-series media servers
- IBM eServer BladeCenter HS20 Blade Server Type 8832
Note:
●
Avaya media servers configured as a Local Survivable Processor (LSP) or Enterprise
Survivable Servers (ESS).
●
Avaya media gateways
Note:
This document does not contain information about prior releases of
Communication Manager. For information on previous releases of
Communication Manager, check the Avaya customer support Web site (see How
to obtain Avaya books on the Web on page 14 for more information).
Newer releases of Communication Manager contain the features of prior releases.
Issue 1.1 June 2006
11
About this book
Contents
This document includes the following chapters:
●
What’s New: presents short descriptions of each of the new features or changes in the
most recent release of Communication Manager.
●
Hardware: describes hardware that is introduced or changed with the most recent release
of Communication Manager.
●
New and changed screens: provides information about new administration screens, and
changes to existing screens, due to the most recent release of Communication Manager.
●
New and changed commands: provides information about commands that are new or
have changed for the most recent release of Communication Manager.
Terms and Conventions
Become familiar with the following terms and conventions. They help you use this book with
Communication Manager.
●
A "screen" is the display of fields and prompts that appear on a terminal monitor.
See for an example of a screen and how it is shown in this book.
●
Avaya uses the term "telephone" in this book. Other books might refer to telephones as
voice terminals, stations, or endpoints.
●
Keys and buttons are printed in a bold font: Key.
●
Titles of screens are printed in a bold font: Screen Name.
●
Names of fields are printed in a bold font: Field Name.
●
Text (other than commands) that you need to type into a field are printed in a bold font:
text.
●
Commands are printed in a bold constant width font: command.
●
Variables are printed in a bold constant width italic font: variable.
●
We show complete commands in this book, but you can use an abbreviated version of the
command. For example, instead of typing list configuration station, you can
type list config sta.
12 What’s New in Avaya Communication Manager
Admonishments
●
If you need help constructing a command or completing a field, remember to use Help.
- When you press Help at any point on the command line, the system displays a list of
available commands.
- When you press Help with your cursor in a field on a screen, the system displays a list of
valid entries for that field.
●
Messages that the system displays are printed in a bold font: system message.
●
To move to a certain field on a screen, you can use the Tab key, directional arrows, or the
Enter key on your keyboard.
●
If you use terminal emulation software, you need to determine what keys correspond to
Enter, Return, Cancel, Help, and Next Page keys.
●
We show commands and screens from the newest release of Communication Manager.
Substitute the appropriate commands for your system and see the manuals you have
available.
●
The status line or message line can be found near the bottom of your monitor. This is
where the system displays messages for you. Check the message line to see how the
system responds to your input. Write down the message if you need to call the helpline.
●
When a procedure requires you to press Enter to save your changes, the screen clears.
The cursor returns to the command prompt. The message line shows "command
successfully completed" to indicate that the system accepted your changes.
Admonishments
Admonishments that might appear in this book have the following meanings:
Note:
Note:
A note calls attention to neutral information or positive information that
supplements the main text. A note also calls attention to valuable information that
is independent of the main text.
!
Important:
Tip:
Important:
An important note calls attention to situations that can cause serious
inconvenience.
Tip:
A tip calls attention to information that helps you apply the techniques and the
procedures that the text describes. A tip can include keyboard shortcuts, or
alternative methods that might not be obvious.
Issue 1.1 June 2006
13
About this book
! CAUTION:
A caution statement calls attention to situations that can result in harm to
software, loss of data, or an interruption of service.
CAUTION:
!
WARNING:
A warning statement calls attention to situations that can result in harm to
hardware or equipment.
!
DANGER:
A danger statement calls attention to situations that can result in physical injury to
yourself or to other people.
!
SECURITY ALERT:
A security alert calls attention to situations that can increase the potential for toll
fraud or other unauthorized use of your telecommunications system.
WARNING:
DANGER:
SECURITY ALERT:
ELECTROSTATIC ALERT:
ELECTROSTATIC ALERT:
An electrostatic alert calls attention to situations that can result in damage to
electronic components from electrostatic discharge (ESD).
Trademarks
All trademarks identified by ® or ™ are registered trademarks or trademarks, respectively, of
Avaya, Inc. All other trademarks are the property of their respective owners.
How to obtain Avaya books on the Web
If you have internet access, you can view and download the latest version of Avaya
documentation products. To view any book, you must have a copy of Adobe Acrobat Reader.
Note:
Note:
If you don’t have Acrobat Reader, you can get a free copy at
http://www.adobe.com.
For example, to access an electronic version of this book:
1. Access the Avaya Web site at http://www.avaya.com/.
2. Click the Documentation link.
14 What’s New in Avaya Communication Manager
How to order documentation
3. To find a specific book, type the document number (for example, 03-300682 for this book) in
the Search text box.
4. In the resulting list, locate the latest version of the document, and then click the document
title to view the latest version of the book.
How to order documentation
In addition to this book, other description, installation and test, maintenance, and administration
books are available.
This document and any other Avaya documentation can be ordered directly from the Avaya
Publications Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax). Customers
outside the United States should use +1-410-568-3680 (voice) and +1-410-891-0207 (fax).
How to comment on this book
Avaya welcomes your feedback. Contact us through:
●
E-mail: document@avaya.com
●
Fax: 1-303-538-1741
●
Contact your Avaya representative
Mention the name, number, and issue of this document: What’s New in Avaya Communication
Manager for Release 3.1.X, 03-300682, Issue 1.1.
Your comments are of great value and help improve our documentation.
How to get help
If you suspect that you are being victimized by toll fraud and you need technical assistance or
support in the United States and Canada, call the Technical Service Center's Toll Fraud
Intervention Hotline at 1-800-643-2353.
If you need additional help, the following resources are available. You may need to purchase an
extended service agreement to use some of these resources. See your Avaya representative
for more information, or go to the Avaya Support Web site at http://www.avaya.com/support:
Issue 1.1 June 2006
15
About this book
16 What’s New in Avaya Communication Manager
Chapter 1: What’s New
This chapter presents highlights of features and enhancements as part of the most current
release of Avaya Communication Manager running on Avaya DEFINITY® servers, as well as
the Avaya S8000-series media servers with associated Avaya media gateways.
The most current release of Communication Manager contains all the features of prior releases.
In this document, each Communication Manager feature or enhancement is listed alphabetically
by release number.
●
For an overview of the features of Communication Manager, see the Overview for Avaya
Communication Manager, 03-300468.
●
For a more complete description of the features of Communication Manager, see the
Feature Description and Implementation for Avaya Communication Manager,
555-245-205.
●
For more information on how to administer these features, see the Administrator Guide for
Avaya Communication Manager, 03-300509.
Release 3.1.X new features and enhancements
Avaya Communication Manager release 3.1.X, which includes releases 3.1.1 and 3.1.2,
includes the following general telephony and system-wide features and enhancements.
Called number added to display for Toshiba SIP telephone
Depending on how you set the Outgoing Display field on the Trunk screen, a call from a
Toshiba SIP telephone over a non-ISDN trunk, to which another Toshiba SIP telephone is
added, now displays either the trunk name or the dialed number.
Setting the Outgoing Display field to Yes displays the trunk name. Setting the Outgoing
Display field to No displays the dialed number.
Clearer display for trunk ID
When an endpoint activates the Trunk ID feature, the display on the endpoint now clears all
other information and shows the Trunk ID for 30 seconds.
Issue 1.1 June 2006
17
What’s New
Enhanced list measurement occupancy command for duplicated
servers
In a configuration with duplicated media servers, the command list measurement
occupancy now displays information for both media servers spanning across interchanges.
Faster backups
The default configuration for backups no longer includes the command save translations.
Scheduled maintenance regularly saves translations, making this command redundant.
Omitting this command results in faster backups.
List configuration by circuit pack
The SAT command list configuration is now available for circuit packs. The format is:
list configuration n, where n is the type of circuit pack, such as a TN2312.
Manual Local Survivable Processor takeover
The Manual Local Survivable Processor (LSP) Takeover feature is used to detect and correct
an IP connectivity problem where network outages can cause media gateways and IP
telephones to repetitively disconnect and re-register with the primary server within an interval
that is too short for those endpoints to fail over to a Local Survivable Processor.
More info from list survivable-processor command
The output for the command list survivable-processor now includes two columns in
place of the Serv State column. Those two columns are:
●
Reg. When this column is Y, the processor is registered.
●
LSP Act. When this column is Y, the LSP is active. This column is blank when the
processor is not an LSP.
18 What’s New in Avaya Communication Manager
Release 3.1.X new features and enhancements
More simultaneous calls per multipoint endpoint
Communication Manager can handle multipoint endpoints that are capable of up to six calls at
once.
New default backup time
The default time at which backups occur is now 1:11AM rather than 2:00AM. This helps avoid
conflicts with other operations.
New reason code for attendant vector
Do Not Disturb (DND) calls that are routed to an attendant vector now display the reason
code ct. This reason code is consistent with the display for an attendant console.
Notification about 802.1q changes
If you change the settings for 802.1q on the IP Network Region screen, a message now
notifies you that the changes will not take effect until the server restarts.
Prompt alarm for C-LAN outage
When Communication Manager detects an outage for a TN799 (C-LAN) circuit pack, it now
immediately raises a warning alarm in addition to the minor alarm that is issued if the outage is
still present after approximately 20 minutes.
T.38 protocol for faxing
Communication Manager now supports sending faxes using T.38 protocol. To use this capability
with Avaya Modular Messaging, watch for the corresponding feature in that product.
Issue 1.1 June 2006
19
What’s New
Tildes to hide names in directory
Display names that begin with a single tilde (~) convert to extended ASCII characters and are
available to the Integrated Directory.
Display names that begin with two tildes (~~) are hidden from the Integrated Directory, but are
not converted to extended ASCII.
Display names that begin with three tildes (~~~) both are hidden from the Integrated Directory
and convert to extended ASCII.
Additional tildes in the display name turn conversion to extended ASCII off again (4, 6, etc.
tildes) and back on (5, 7, etc. tildes).
Release 3.1 new features and enhancements
Avaya Communication Manager, release 3.1, includes the following general telephony and
system-wide features and enhancements.
802.1x multi supplicants
Multi-supplicants are common in IP telephony where PC and IP endpoints are attached to the
same port. For better security and to reduce interdependency between the PC and IP
endpoints, the multi-supplicants mode enables each supplicant to independently authenticate
itself to gain access to the network. Multi-supplicants support C360 R3, G350, and G250
platforms.
In remote sites, the multi-supplicants mode provides:
●
An extra level of security by restricting access only to known users and devices
●
Consistency of security features offered in the gateways’ LAN interfaces in case of
multi-vendor networks (Avaya gateways and Extreme switches)
Administrable size for Receive Buffer TCP Window
The IP Interfaces screen now includes the Receive Buffer TCP Window Size field. You can
set the value of this field to any value from 512 to 8320 (the default value). The value is the
number of bytes that are allotted for the buffer that receives TCP data for a TN799 (CLAN)
circuit pack.
To see the IP Interfaces screen, type display ip-interface n, where n is the location of
the TN799 (CLAN) circuit pack.
20 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Administrable time-out for inactive SAT sessions
You can now administer the idle time that the system permits before the system shuts down a
SAT session. Set the Command Time-Out field on the Maintenance-Related System
Parameters screen to any value from 10 to 360 minutes.
The default value is 120 minutes.
Alarm messages for unregistered LSPs
Alarms are generated on both the main server and on an LSP if Keep Alive (KA) messages are
not periodically exchanged. In addition, an audit is required to verify that all LSPs have
registered within twenty minutes of system initialization.
ASAI support for Aux Work reason codes
You can now assign up to 99 Aux Work reason codes, rather than only 10. The description for
each reason code can now be up to 16 characters, rather than only 10 characters.
Note:
ASAI does not currently support two-digit reason codes.
Note:
To take advantage of the additional reason codes, set the:
●
Reason Codes field on the Customer Options screen to y
●
Expert Agent Selection (EAS) Enabled and the Two-Digit Aux Work Reason Codes
fields on the Feature-Related System Parameters screen to y.
Avaya Video Telephony Solution
The Avaya Video Telephony Solution makes video calls as simple and easy as a regular
telephone call. The Avaya Video Telephony Solution is fully integrated into your standard dial
plan, enabling totally transparent and seamless voice and video conferencing, both for the
desktop and for group video communications.
Communication Manager features such as hold, transfer, resume, and conference are
seamless with video conferencing adjuncts from Polycom. Avaya Video Telephony Solution
unifies Voice over IP with video, web applications, Avaya’s video enabled IP Softphone, third
party gatekeepers, and other H.323 endpoints.
Issue 1.1 June 2006
21
What’s New
The following components are part of the Avaya Video Telephony Solution feature:
●
Polycom VSX3000, VSX7000, and VSX 8000 conferencing systems with Release 8.03 or
later
●
Polycom V500 video calling systems
●
Polycom MGC video conferencing bridge platforms with Release 7.02
●
Third party gatekeepers
The solution requires Communication Manager Release 3.0.1, and Avaya IP Softphone release
5.2, with Avaya Integrator for Polycom Video release 2.0.1.
The Avaya Video Telephony Solution also supports the:
●
Logitech 4000 Pro web camera
●
Polycom Via Video
●
Creative Labs notebook webcam
Banner displayed to warn of reset
When a new license file is loaded which changes the value of FEAT_ESS from that of the
previous license files, a “reset sys 4“ is required in order for the change to take effect.
If the “reset sys 4“ is not done, a banner is displayed on the initial SAT screen warning the user
that a reset is required.
Block circuit pack installation if wrong suffix
In an Enterprise Survivable Server (ESS) system:
●
When a TN2305 or TN2306 Asynchronous Transfer Mode (ATM) Expansion Interface (EI)
suffix “A” circuit pack is inserted in a position where a suffix “B” circuit pack is required, the
circuit pack insertion is prevented and an alarm (MINOR ON_BOARD) is raised.
●
When a TN750 EI circuit pack, with a suffix other than “D,” is inserted in a position where a
suffix “D” circuit pack is required, the circuit pack insertion is prevented and an alarm
(MINOR ON_BOARD) is raised.
22 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Block CMS Move Agent events
This feature lets you prevent the system from sending the ASAI logout-login event messages,
that are related to an agent move. When this CTI link option is activated, the changes to the
agent state, such as logout followed by login and return to previous state, will not be reported to
the ASAI adjunct. This operation is required by Avaya IC since the initial logout causes IC to
permanently logout the agent, disrupting normal operation. IC does not need to be informed of
agent skill moves via this method. This option will be available to other applications for use
where needed.
Call Log modifications
In previous releases of Communication Manager, the extension number of some DCP and IP
telephones did not appear on the Call Log for call forwarded calls and for bridged call
appearance of extension calls. The word “Unavailable” appeared in the Number field of the Call
Log in these scenarios.
Communication Manager release 3.1 now displays the extension on the Call Log for call
forwarding and bridged call appearances on the following IP telephones:
●
4610
●
4620
●
4621
●
4622
●
4625
Communication Manager release 3.1 now displays the extension on the Call Log for call
forwarding only on the following DCP telephones:
Note:
●
2410
●
2420
Note:
At this time, the current firmware version of the 2410 and 2420 telephones do not
support an option for providing call logs for bridged appearances.
Issue 1.1 June 2006
23
What’s New
Clear the display of collected digits
You can define when the system clears the display of collected digits (Callr-info) from the agent
telephone. The system allows the:
●
Existing default option to clear the display when the next call is received
●
Option to clear the display when the call is released
●
Option to keep the displayed digits while the agent is in After Call Work (ACW) mode.
Compress restart escalation sequence
Problems that were not being fixed by a first cold2 restart were not necessarily being fixed by a
second cold2 restart. The escalation sequence is now compressed by proceeding to the next
restart level, which is a reload.
Connection-preserving upgrades
When upgrading an S8700-series Media Server from 3.0 to a later release, you can preserve
many connections through the course of the upgrade. For more detailed information, see the
Documentation Updates in the Release Notes for S8700-series Media Servers.
Detecting 655A power supply failures
If a 655A power supply should fail in a duplicated power G650 port network, it is now possible to
determine what 655A power supply out of a possible 10 has failed.
Dial backup over external ISDN modem
If there is a primary WAN failure, this feature offers a backup means for the control channel
between the branch office and the main site.
The gateway attempts to reestablish the control channel through an alternate route by dialing
back to the main site through an external modem that is connected to the serial port or the USB
port. The external modem, connected to the PSTN, allows dial-up connection to a router or
modem at the main site.
This feature is implemented on the G250 and G350 Media Gateways.
24 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Direct-region preference for IP telephones
In many customer configurations, IP telephones are placed into their own direct network regions
or indirect network regions. Voice over IP (VOIP) allocation can now favor direct-connected
regions over indirect connected regions.
Duplicate power supply failure upgraded to alarm status
A redundant power supply can fail looking like it has no AC input. Since the power supplies are
duplicated the customer experiences no service outage. This failure could occur if the power
cord to the power supply is disconnected, or switching off the equipment room that powers that
breaker.
This problem is first logged as a Warning. If the problem exists for 1-2 hours, the problem is
escalated to a Minor alarm status. At that time, Services can contact the customer to find out if
the external power is OK or if the external power is intentionally turned off.
If the external power is OK, then a technician can be dispatched to replace the 655A power
supply.
Enhanced feature integrations for Avaya Modular Messaging
This enhancement implements QSIG and IP integration for One-Step Recording, supporting
integration with Avaya Modular Messaging.
A new button type, audix-rec, is added to the Station screen for this feature. When
administered, the button requires the user’s Audix hunt group extension number along with it.
The new button type is not yet available on attendant consoles.
Enhanced password security
When you administer a new login, that login now requires a new password the first time it is
used.
Issue 1.1 June 2006
25
What’s New
Enhanced TN2602AP circuit pack
Communication Manager release 3.1 includes enhancements to the TN2602AP circuit pack,
described in the following paragraphs.
Note:
Note:
The TN2602AP IP Media Resource 320 is not supported in CMC1 and G600
Media Gateways. For more information about the TN2602AP circuit pack, see the
Hardware Description and Reference for Avaya Communication Manager,
555-245-207.
Bearer signal duplication
The capabilities of the TN2602AP circuit pack have been expanded to provide duplicated
bearer support. This enables customers to administer IP-PNC with critical bearer reliability. A
port network continues to support a maximum of two TN2602AP circuit packs, but they can now
be administered for duplication. This capability is in addition to the previously-offered load
balanced support (see Load balancing).
Two TN2602AP circuit packs may be installed in a single port network for bearer signal
duplication. In this configuration, one TN2602AP is an active IP media processor and one is a
standby IP media processor. If the active media processor, or connections to it, fail, active
connections failover to the standby media processor and remain active. This duplication
prevents active calls in progress from being dropped in case of failure.
Duplicated TN2602AP circuit packs operate in an Active-Standby mode. State of health
parameters exist between the two boards to determine when it is appropriate to interchange
duplicated TN2602AP circuit packs. It is also possible to manually invoke an interchange using
a software command.
For bearer duplication, both TN2602AP circuit packs must be Hardware Version 2, and must
have firmware version 211 or higher.
Note:
Note:
The 4606, 4612, and 4624 telephones do not support the bearer duplication
feature of the TN2602AP circuit pack. If these telephones are used while an
interchange from active to standby media processor is in process, calls might be
dropped.
!
Important:
Important:
If you change from load balanced to duplicated TN2602s, existing calls retain the
real IP address on the TN2602AP circuit pack. New calls are associated with the
virtual IP address of the TN2602AP circuit pack. If an interchange occurs during
this time, existing calls that are associated with the real IP address will drop.
26 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Load balancing
Up to two TN2602AP circuit packs can be installed in a single port network for load balancing or
duplication. When in a load balanced mode, calls are distributed evenly among the two TN2602
circuit packs.
The TN2602AP circuit pack is also compatible with, and can share load balancing with, the
TN2302 and the TN802B IP Media Processor circuit packs. Actual capacity may be affected by
a variety of factors, including the capacity of the circuit pack being used, the codec used for a
call, and fax support.
Note:
If duplicated TN2602 circuit packs are combined with a TN2302 or TN802,
Communication Manager uses the active, duplicated TN2602 to capacity before
using another media processor circuit pack.
Note:
Also, when media processor circuit packs in the same port network are in
different network regions, load balancing does not apply.
Reduced channels with duplicated TN2602AP circuit packs
If a pair of TN2602AP circuit packs, previously used for load balancing, are re-administered to
be used for bearer duplication, only the voice channels of the active circuit pack can be used.
For example,
●
If you have two TN2602 AP circuit packs in a load balancing configuration, each with 80
voice channels, and you re-administer the circuit packs to be in bearer duplication mode,
you have 80, not 160, channels available.
●
If you have two TN2602 AP circuit packs in a load balancing configuration, each with 320
voice channels, and you re-administer the circuit packs to be in bearer duplication mode,
you will have 320, not the maximum 484, channels available.
●
When two TN2602AP circuit packs, each with 320 voice channels, are used for load
balancing within a port network, the total number of voice channels available is 484, not
640. The reason is that 484 is the maximum number of time slots available for connections
within a port network.
Support of T.38 fax relay
T.38 fax relay over IP is now supported with the TN2602AP IP Media Resource 320 circuit pack.
The T.38 fax call set up may initiate as a G.711, but once fax tones are detected, traffic is
encoded/decoded using the T.38 specification.
In the case of duplicated TN2602 circuit packs that are in an active-standby mode, the system
sends this information to the standby circuit pack when an interchange occurs.
Issue 1.1 June 2006
27
What’s New
V.32 modem relay
V.32 modem relay is an option that provides a low-bandwidth solution for secure voice terminals
on the TN2602AP circuit pack. For customers wishing to use standard data modems, modem
passthru is the appropriate solution.
Both modem passthru and V.32 modem relay already exist on the TN2302AP circuit pack, so it
is now possible for these two circuit packs to interoperate.
Enterprise Mobility User
Enterprise Mobility User (EMU) is a software-only feature that gives you the ability to associate
the buttons and features of your primary telephone to a telephone of the same type anywhere
within your company enterprise.
Note:
In this document, any telephone that is not the primary telephone is referred to
the visited telephone and any server that is not the home server of the primary
telephone is referred to as the visited server.
Note:
The following is a list of requirements that you need for the EMU feature:
●
QSIG must be the private networking protocol in the network of Communication Manager
systems.
●
Communication Manager Release 3.1 and later software must be running on the home
server and all visited servers.
●
All servers must be on a Linux platform. EMU is not supported on DEFINITY servers.
●
The visited telephone must be the same model type as the primary telephone to enable a
optimal transfer of the image of the primary telephone. If the visited telephone is not the
same model type, only the call appearance (call-appr) buttons and the message waiting
light are transferred.
●
EMU is only supported on self-designating terminals (terminals with button labels) that are
downloaded from the Communication Manager server.
●
Uniform Dial Plan (UDP).
How Enterprise Mobility User works
On the dial pad of a visited telephone, a user enters the EMU activation feature access code
(FAC), the extension number of their primary telephone, and a security code. The visited server
sends the extension number, the security code, and the set type of the visited telephone to the
home server.
28 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
When the home server receives the information, the home server:
●
Checks the Class of Service (COS) for the primary telephone to see if it has PSA
permission.
●
Compares the security code with the security code on the Station screen for the primary
telephone.
●
Compares the station type of the visited telephone to the station type of the primary
telephone. If both the visited telephone and the primary telephone are of the same type,
the home server sends the applicable button appearances to the visited server. If a
previous registration exists on the primary telephone, the new registration is accepted and
the old registration deactivated.
If the registration is successful, the visited telephone assumes the primary telephone’s
extension number and some specific administered button types. The display on the primary
telephone shows Visited Registration Active: <Extension>. The <Extension> that displays
is the extension number of the visited telephone.
Note:
The speed dialing list that is stored on the primary telephone and the station logs
are not downloaded to the visited telephone. EMU does not allow users to
associate permissions from the home telephone to the remote telephone.
Note:
Enterprise Survivable Server increase
The number of Enterprise Survivable Servers (ESS) that you can administer in one ESS
configuration is increased to 63. For more information on Enterprise Survivable Servers, see the
Avaya Enterprise Survivable Servers (ESS) Users Guide, 03-300428.
Extended survivability to G250 Media Gateway
This feature provides basic survivable call processing functionality on the G250 Analog and IP
interfaces. The survivability feature is expanded to provide basic survivability functionality for
the:
●
G250-DCP analog and DCP interfaces
●
G250-DS1 analog interfaces
●
G250-BRI analog interfaces
Issue 1.1 June 2006
29
What’s New
Gateway trunk preference selection
When trunks from more than one Media Gateway (G350, G700, or G250) are in the same trunk
group, Communication Manager new “prefers” trunks on the same Media Gateway as the
originator.
HTTP server on S8500 Media Server
This feature supports downloading of firmware for IP telephones from Communication Manager
using HTTP.
Increased Classes of Restriction
The Classes of Restriction (COR) feature is increased from a total of 96 possible CORs to 996
possible CORs. Classes of Restriction are numbered from 0 to 999, with four CORs - 996, 997,
998, and 999 - reserved by the system. The CORs that are available for the user to assign are
from 0 to 995.
Increased text fields for feature buttons
If you are using certain newer phones with expanded text label display capabilities, the Increase
Text Fields for Feature Buttons feature allows you to program and store up to 13-character
labels for associated feature buttons and call appearances.
This feature is currently available for the 2410 (release 2 or newer) and 2420 (release 4 or
newer) DCP telephones. Support for the newer 46xx IP telephones may be added in the future.
Increased quantity of NCA TSCs and FTSCs
In an S87x0 Media Server or an S8500 Media Server configuration, you can now have up to
999 NCA TSCs system-wide, and up to 999 NCA TSCs per signalling group. You can also have
up to 250 FTSCs.
30 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Increased trunk members for IP signaling groups
The number of H.323 trunk members in a single signaling group that are supported on the
Trunk Groups screen is increased from 31 to 255. Users also have the option to administer
each trunk group member individually or automatically.
Incremental filesyncs
The system now supports two difference sets for incremental filesyncs, one for LSPs and one
for ESSs.
Inter-Gateway Alternate Routing calls over Inter-Gateway
Connections
The output of the command display internal-data s-tab now includes information
about IGAR (Inter-Gateway Alternate Routing) calls using shared connection (“dumbbell”)
topology over Inter-Gateway Connections (IGCs). An IGAR call can use up to 120 IGCs.
A new field igccount' displays the total quantity of dumbbell IGCs used by an IGAR call.
Dumbbell information for those IGCs appears on additional pages of the output.
The information listed for each PSTN IGC includes:
●
Fabric Type (PSTN)
●
Master Trunk Port ID
●
Slave Trunk Port ID
The information listed for each IP IGC includes:
●
Fabric Type (IP)
●
Master Ephemeral IP Address (on a port network or gateway)
●
Master Ephemeral Port
●
Slave Ephemeral IP Address (on a port network or gateway)
●
Slave Ephemeral Port
Issue 1.1 June 2006
31
What’s New
Listen-only FAC for service observing
The system provides a no-talk, listen-only service observing feature access code (FAC). This
FAC does not reserve a second timeslot for potential toggle to talk and listen mode. This feature
is for call recording applications that use Service Observing of stations/ACD agents to provide
increased call recording capacity by reducing the timeslot usage.
Local ringback administration
A new field is added to the Trunk Group screen, allowing the administrator to set if local
ringback tone should be sent to a caller.
If the Apply Local Ringback? field is set to y, and the system does not receive a PI_IBI in
ALERT, then the system sends a local ringback tone to the caller. The local ringback tone is
removed when the system receives a connect, and the channel will cut through.
More BRI Trunk circuit packs
An S8700, S8710, S8500, or S8300 Media Server running Communication Manager can now
have up to 250 TN2185 (BRI Trunk) circuit packs.
More Leave Word Calling messages
Communication Manager can now handle up to 12,000 Leave Word Calling (LWC) messages.
More than nine static routes allowed
A radio button is added to the Set Static Routes section of the configure server web pages that
allows more than nine static routes.
Music on hold played from nearest source
An IP telephone in one network region (the “calling party”) calls another IP telephone in another
network region (the “called party”). If the calling party places the called party on hold, the called
party hears music from the nearest music source. Assuming that the gateways in both network
regions had music installed, music would come from the called party’s gateway.
32 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Notification about 802.1q changes
If you change the settings for 802.1q on the ip-network-region screen, a message now notifies
you that the changes will not take effect until the server restarts.
Parameterized data for NSF
The isdn network-facilities screen now provides a new column, administrable for user-entered
Network Specific Facility (NSF) names. The value in this column indicates whether the NSF
handles parameterized data. The default value is n, but you can change it to y.
When this value is set to y for outwats-bnd or any user-administered NSF name, you can see
the Parm column on the route-pattern screen. The value in this column provides information for
handling the parameterized data. For instance, if the NSF is SCOCS, it defines the class of
service requested for the parameterized data. It is blank by default, but you can give it any
numeric value up to 5 digits.
Prepend '+' to calling number
The SIP Trunk Group screen now provides the field Prepend + To Calling Number. The
default setting is n. If you set the field to y, the character + is added at the beginning of the
calling number for that trunk group.
Processor Ethernet
The Processor Ethernet (PE) interface is one way of connecting VoIP and IP-based devices to
Communication Manager. The PE interface is the appearance of the computer’s native ethernet
interface inside of the Communication Manager application.
An Enterprise Survivable Server (ESS) and a Local Survivable Processor (LSP) registers with
the main server when it is first configured, and every time it receives a file sync from the main
server. An ESS server and an LSP uses the PE interface to register with the main server. You
do not have to administer the PE interface for registration purposes. The system software
enables the use of the PE interface on servers configured as an LSP or and ESS server.
! CAUTION:
CAUTION:
Do not disable the PE interface on an LSP or an ESS server. Disabling the PE
interface disables the LSP or ESS server’s ability to register with the main server.
The LSP or ESS server will not work if the PE interface is disabled.
Issue 1.1 June 2006
33
What’s New
On simplex main servers, you can administer the server where IP endpoints may register
through:
●
The PE interface only
●
CLAN interfaces only (requires the configuration to have CLANs)
●
Either the PE interface or specified CLAN interfaces (requires the configuration to have
CLANs) That is, both interfaces must be able to be enabled at the same time with some
endpoints registering through the PE interface and some through CLANs.
Adjuncts
If the main server is a simplex server, adjuncts that connect to the simplex main server using a
CLAN can also connect to the simplex main server using the server’s PE interface.
Three adjuncts are supported for connectivity to the PE interface of a LSP or an ESS server:
●
CMS
●
CDR
●
Application Enablement Services (AES)
An adjunct link is established between the LSP or the ESS server. Administration that allows
dedicated and shared connections between the adjuncts and the servers must allow for the link
to remain active at all times. When the LSP or ESS server is not active, the adjunct does not
receive data from that server.
For information on how to a administer the adjunct link, see the adjunct documentation that is
specific to your adjunct.
H.248 and H.323 registration
The system uses the PE interface on an LSP to register H.248 gateways and H.323 endpoints.
Starting with Communication Manager Release 3.1, the use of the PE interface to register
H.248 gateways and H.323 endpoints has been expanded to include the simplex main server.
S8500 Media Servers
With the increased functionality of the PE interface, the role of the S8500 Media Server has
been expanded. This expansion includes an S8500 configured as an LSP, and an S8500
configured as a main server in an IP configuration with no port networks.
The PE interface is not supported for H.248, H.323, and adjunct connectivity on a duplex
(S8700-series) server.
34 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
QSIG path optimization simplified
Improvements were made to the dial plan to simplify path replacement and diversion with
rerouting.
QSIG redirection display is administrable
When a Do-Not-Call (DNC) server authorizes a call through QSIG, the server returns the routing
number to the CM using QSIG Redirection. The word “forward” and the secret routing number
were displayed on the caller’s telephone display.
QSIG redirection is now administrable so a customer can turn off the information from the
caller’s telephone display if they choose.
R2-MFC support on G250 Media Gateway
Add support to the trunks of the G250 Media Gateway for MF Signaling (R2MFC, Russian AMI/
MFR) detection, and MF signaling generation, on analog trunks and on E1/T1 trunks (CAS
signaling).
Remote upgrades for branch gateways
This allows remote upgrade of software/firmware of the branch office server and media gateway
without the need for presence of a technician on site. An existing Communication Manager
Server CD-ROM serves as the vehicle for delivering major releases, minor releases, and
updates. Communication Manager delivers desired software and firmware to the branch
location, assuming there is a USB DVD-ROM/CDRW drive connected to the S8300B in a G250,
G350, or G700 Media Gateway.
There are three possible remote upgrade scenarios:
Note:
●
Upgrades performed over the customer network
●
Upgrades performed using Secure Access and Control (SAC)
●
Upgrades performed outside of the customer network
Note:
A USB modem, connected to the S8300B, is required when the remote upgrades
are performed outside of the customer network over an analog PSTN connection.
Issue 1.1 June 2006
35
What’s New
Rerouting and path replacement by trunk group
You can now administer individual QSIG trunk groups not to use rerouting and path
replacement, while leaving these capabilities active for other trunk groups. The Trunk Group
screen now provides a new page containing two new fields for this purpose:
●
Diversion By Reroute
●
Path Replacement
These two new fields are visible only if the Basic Supplementary Services and the
Supplementary Services With Reroute fields on the Optional Features screen are set to y,
and the Supplementary Service Protocol field on the Trunk Group screen is set to b. The
default value for both fields is y.
●
If you set the Diversion By Reroute field to n, the Call Diversion feature uses forward
switching rather than rerouting.
●
If you set the Path Replacement field to n, the Path Replacement With Retention and
the Path Replacement Method fields are no longer visible, and the trunk group does not
use path replacement.
Reset IP stations by subnet enhancement
Customers can reset telephones in a multi-floor building by subnet, and perform controlled
station resets using the reset ip-stations command to reset by subnet.
Secure Shell and Secure FTP
The Secure Shell (SSH) and Secure FTP (SFTP) capabilities are highly-secure methods for
remote access. Administration for this capability also allows disabling Telnet when it is not
needed, creating a more secure system.
SSH/SFTP functionality does not require a separate Avaya license, nor are there any entries in
the existing Communication Manager license needed.
Applicable platforms or hardware
You can log in remotely to the following platforms or hardware using SSH as a secure protocol:
●
G350 Media Gateway
●
C350 Multilayer Modular switch
●
S8300, S8500, S8700, or S8710 Media Server command line
36 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
●
IBM e-server BladeCenter Type 8677 command line
●
Communication Manager System Administration Terminal (SAT) interface on a media
server using port 5022.
Note:
The client device for remote login must also be enabled and configured for SSH.
Refer to your client PC documentation for instructions on the proper commands
for SSH.
Note:
Secure Shell (SSH) and/or Secure FTP (SFTP) remote access protocols are provided on these
circuit packs:
●
TN799DP (CLAN)
●
TN2501AP (VAL)
●
TN2312AP/BP (IPSI)
●
TN2602AP (Crossfire)
SAT commands enable S/FTP sessions through login/password authentication on the CLAN
and VAL circuit packs and SSH/Telnet on the Crossfire circuit pack. The Maintenance Web
Interface and a Communication Manager command line enable the IPSI session. Unencrypted
Telnet and FTP capabilities are enabled on these circuit packs.
Using Secure Shell to retrieve backup information
From the Maintenance Web page of Communication Manager, customers can perform a
backup such that the file can be either sent or retrieved using SSH/SCP/SFTP.
Security of IP telephone registration/H.323 signaling channel
The Security of IP telephone registration/H.323 signaling channel feature provides a secure
mechanism for an H.323 IP endpoint and a Communication Manager gatekeeper to mutually
authenticate each other. The IP endpoint and the Communication Manager gatekeeper
authenticate each other by implicitly showing that each knows the assigned PIN.
The system uses the procedures of H.235.5, formerly published as H.235 Annex H, Security
Profile 1 to accomplish this authentication. The system also used H.235.5 to negotiate a strong
shared secret using the Encrypted Key Exchange (EKE) method.
An authentication key, derived from the master key using a one-way function, is used to
authenticate the contents of the messages. The H.323 endpoint and a Communication Manager
gatekeeper exchange this authentication key during IP registration, admission, and status
(RAS) and during call signaling.
Issue 1.1 June 2006
37
What’s New
An encryption key, derived from the master key using a one-way function, is used to encrypt
private information that is carried within these messages. Two examples are media encryption
keys and proprietary signaling elements. The proprietary signaling elements carry display
information and dialed digits.
If one or the other parties does not possess the correct PIN, the computed shared secrets are
different. As a result, RAS message authentication fails and the parties refuse to communicate
with each other.
With the Security of IP Telephone Registration/H.323 Signaling Channel feature, the IP
endpoint and the Communication Manager gatekeeper:
●
Authenticate each other
●
Negotiate a strong shared secret
●
Authenticate each message that is sent or received
●
Digitally sign all RAS and call signaling messages
●
Encrypt selected elements of RAS and call signaling messages, such as:
- media session keys
- proprietary elements
You can also use H.235.5 procedures and security mechanisms for IP trunking by administering
the appropriate Signaling Group screen.
With this feature, the quality of the communication includes:
●
Privacy for selected elements of call signaling, including media session encryption keys
and dialed digits.
●
Security of past or future communications, even if one session is penetrated by an attacker
with knowledge of that session’s keys. This is known as “perfect forward secrecy.”
●
Efficient reuse of the negotiated strong secret, identified by a unique session ID, to derive
strong keys for new signaling links between Communication Manager and endpoints, or
between other Communication Manager servers, such as IP trunks.
Capacities
S8300 Media Servers - There are no capacity constraints on S8300 Media Servers when this
feature is enabled.
S8500 Media Servers - There are no capacity constraints on S8500 Media Servers when this
feature is enabled.
S8700 Media Servers - Fewer IP endpoints are supported on S8700 Media Servers when this
feature is enabled. Full system recovery from a network outage on an S8700 Media Server, with
1,500 IP endpoints and this feature enabled, will take roughly 15 minutes. Therefore, use of this
feature on an S8700 Media Server with more than 1,500 IP endpoints is not supported.
38 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
S8710 Media Servers - Fewer IP endpoints are supported on S8710 Media Servers when this
feature is enabled. Full system recovery from a network outage on an S8710 Media Server, with
3,000 IP endpoints and this feature enabled, will take roughly 15 minutes. Therefore, use of this
feature on an S8710 Media Server with more than 3,000 IP endpoints is not supported.
Feature Interactions
Survivable Remote Processor - Survivable Remote Processor (SRP) is not supported when
this feature is enabled.
IP Softphone - If an IP Softphone is in a network region that has the Security Procedures field
on the ip-network-region screen set either to pin-eke (H.235.5) or strong (which currently is
equivalent to pin-eke), the IP Softphone will not register. For the IP Softphone to register, the
Security Procedures field must be set either to any-auth or challenge.
Note:
Note:
Currently, IP Softphone does not support pin-eke (H.235.5). IP Softphone may
support pin-eke in a later release.
Use of Avaya IP Softphone in “Control Avaya Telephone (via the telephone)” configuration is
possible only if the Security Procedures field on the ip-network-region screen that applies to
the IP Softphone is set to challenge.
Compatibility
The Security of IP Telephone Registration/H.323 Signaling Channel feature requires IP
telephone software R2.3 or later.
IP telephone software R2.3 or later requires TN799C hardware, vintage 3 or later, circuit packs.
TN799C hardware, vintage 1 and 2 circuit packs, do not work with IP telephone software R2.3.
All versions of TN799DP circuit packs are compatible with IP telephone software R2.3.
Therefore, use of the Security of IP Telephone Registration/H.323 Signaling Channel feature
requires TN799DP or TN799C hardware vintage 3 or later circuit packs.
Shadowing data on servers
Prior to this update, if a server interchange occurs, a customer might like to review the
occupancy of the system prior to the interchange to see if the load might possibly have been a
catalyst. The customer must interchange back to the other server in order to review the
information.
For example, Server A is active from 13:00 to 15:30 when something causes an interchange.
Now Server B becomes active. At 15:40, the customer or service representative tries to review
system occupancy using the list measurement occupancy last or list
measurement occupancy summary command.
Issue 1.1 June 2006
39
What’s New
The only occupancy information that is provided on Server B is data prior to 13:00 when
Server B was the active server, and from 15:30 to 15:40.
Now, list measurement information is shadowed (shared) between servers so that the
customer can see the data.
SIP Enablement Services
Session Initiation Protocol (SIP) is an endpoint-oriented signaling standard. SIP is a text-based
protocol based on elements of Hypertext Transfer Protocol (HTTP) and Simple Mail Transfer
Protocol (SMTP). SIP Enablement Services (SES) supports several types of communication
sessions that include voice, video, or instant text messaging.
For a complete description of SES updates and enhancements for release 3.1, including
updates to screens and commands, see:
●
SIP Support in Release 3.1 of Avaya Communication Manager Running on the Avaya
S8300, S8400, S8500, S8500B, S8700, and S8710 Media Server, 555-245-206
●
Installing and Administering SIP Enablement Services R3.1, 03-600768
Site data warning when adding station to TTI port
If you add a station to a TTI port which already has site data, you now receive a warning
message informing you that this action affects the site data.
Support caller ID on call waiting for MM711 and MM714
Calling Identity Delivery on Call Waiting (CIDCW) provides visual information on an incoming
call while the called party is on an existing call. This feature combines the functionality of Call
Waiting (CW) and Calling Identity Delivery (CID).
Support for Enterprise Linux
This feature ports Communication Manager from Red Hat Linux 8.0 to Red Hat Enterprise Linux
4.0.
40 What’s New in Avaya Communication Manager
Release 3.1 new features and enhancements
Translations file timestamps
The resolution on the translations file timestamps is now adequate to differentiate consecutive
incremental filesyncs.
Web firewall settings simplified
The firewall script was changed to generate the list of services that can be administered using
the web page. The list of services is maintained in a new firewall configuration (config) file, and
the list was reduced to only protocols that are implemented by some command that is installed
on the server. This list is in a separate config file to allow on the fly changes (e.g., in the field).
! CAUTION:
CAUTION:
There is no backup and restore capability, which means changes to this new
config file will have to be manually propagated to new loads.
The Firewall web page was changed to handle the new line format from the firewall script, and
use that output as the list of services that can be administered instead of /etc/services. The web
page was also changed to use the punch/patch option to the firewall script for changing
administrations rather than creating a temporary config file.
Web interface for synchronization plan
A customer can now use a web interface to check if their synchronization plan is working
correctly.
Web upgrade tool checks file corruption/presence
When attempting a switch/LSP/MG upgrade, if an upgrade file is not present or corrupted, the
upgrade will fail. An upgrade to the Web upgrade tool now lists the cause of the failure and
what, if any, remaining upgrade tasks failed to begin (i.e., MG FW upgrade).
Web upgrade tool common media module option
The upgrade tool requires entry of file names for G700 and G350 Media Gateways. Some
media modules are common to both platforms. The upgrade tool now has the option to use the
same file name for common media modules for both gateways.
Issue 1.1 June 2006
41
What’s New
Release 3.0 new features and enhancements
Avaya Communication Manager, release 3.0, includes the following general telephony and
system-wide features and enhancements.
Administrable Periodic Registration Timer
The IP-Options System Parameters screen now provides the Periodic Registration Timer
(PRT) field. This field governs the interval, in minutes, between instances of re-registering
endpoints that are unregistered due to moving to another telephone, for example, when IP
Softphone has controlled the extension. You can administer the number of minutes to any value
from 1 to 60 minutes. The default value is 20.
Alarm log entries for MG-ICC
When a KA failure happens for an LSP, entries in the alarm log now show MG-ICC instead of
ICC.
Analog bearer frequency for IP encoding
The Signaling Group screen now provides a new field, DCP/Analog Bearer Capability, when
the Group Type is H.323. The default value of this field is 3.1kHz, but you can also set it to
speech. If you set the field to speech, the bearer channel is available for IP speech encoding to
networks that do not support 3.1kHz encoding.
Application Enablement Services
Application Enablement Services (AE Services) provides a connection between applications
and Communication Manager. This connection allows development of new applications and
new features without having to modify Communication Manager or to expose its proprietary
interfaces.
AE Services provides a single common platform architecture for call control, device control,
media control, and management. AE Services enables internal Avaya developers and external
partners to create powerful applications that harness the extensive Communication Manager
feature set.
42 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
Avaya provides two different AE Services deployment options:
●
Software-only option
●
Bundled server option
The same client applications and software development kits (SDK) can run against both
options.
Software-only option
Avaya provides the AE Services software, which is the AE Services connector server software
and the AE Services SDK. The customer obtains the prerequisite hardware, platform software,
and third-party software. The customer then installs and maintains all software and hardware.
Bundled server option
Avaya provides the hardware server and all of the necessary software:
●
AE Services connector server software
●
AE Services SDK
●
Platform
●
Third-party software
Avaya service technicians install the hardware and software. If the customer buys a
maintenance and/or a service contract, Avaya also provides maintenance and/or service for the
system. Otherwise, the customer maintains the system.
Adjunct Switch Application Interface
Adjunct Switch Application Interface (ASAI) links Communication Manager and adjunct
applications. The interface allows adjunct applications to access Communication Manager
features and supply routing information to the system.
ASAI is the Avaya recommendation for Computer Telephony Integration (CTI). ASAI is based
on the Q.932 protocol.
CVLAN
CallVisor LAN (CVLAN) is an application programming interface (API) that enables applications
to communicate with Communication Manager. CVLAN sends and receives ASAI messages
over shared ASAI links on TCP/IP. An application can use ASAI messages to monitor and
control Communication Manager resources.
CVLAN software consists of a client component and a server component. The CVLAN client
can be installed on a server or on a client workstation. The CVLAN client provides clients with
access to the switch using the CVLAN server.
Issue 1.1 June 2006
43
What’s New
DEFINITY LAN Gateway
DEFINITY LAN Gateway (DLG) is a software service that tunnels the ASAI call control protocol
messages onto IP packets for transport between a customer Computer Telephony Integration
(CTI) server or application and Communication Manager.
Device and media control API
Device and media control API provides a connector to Communication Manager that allows
clients to develop applications that provide first party call control. Applications can register as IP
extensions on Communication Manager and then monitor and control those extensions.
Device and media control API consists of connector server software and a connector client API
library. The connector server software runs on a hardware server that is independent from
Communication Manager. That is, device and media control API does not run co-resident with
Communication Manager.
Ask your Avaya representative for a complete list of device and media control API
documentation.
System Management Service
System Management Service (SMS) is a web service that exposes management features of
Communication Manager to clients. SMS enables its clients to display, list, add, change, and
remove specific managed objects on Communication Manager that are available through the
OSSI protocol and SAT screens.
SMS is one of the web services that resides on the Application Enablement Services platform
(AE Services).
Telephony Service
Telephony Service (TS) is a web service that exposes basic outbound call control features of
Communication Manager. Telephony Service enables its clients to originate an outbound call,
drop a call, transfer a call, or conference a party into a call.
Telephony Service is one of the web services that resides on the Application Enablement
Services platform (AE Services).
User Service
User Service provides a common way of administering, retrieving, and programmatically
operating on user data. User Service provides a common user store and a programmable
interface for products and applications with which to integrate. User Service has a common
industry-standard data store (LDAP) as the repository for common user profile data.
44 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
User Service has web services as the infrastructure. This infrastructure allows products to
integrate with User Service at your schedule. User Service exposes a programmatic SOAP
interface that allows clients to write third party applications to utilize its functionality.
This integration occurs through the use of software adapters to User Service. The adapter and
web services technology allows User Service to publish user events to the product spaces, and
the product spaces to publish events to the common user area.
So if an administrator adds a user to the common store, a user event is sent to all participating
products with the appropriate information. Likewise, if a product level administrator modifies a
user record in its own user system, an event is sent to User Service for the modified data to be
stored in the common store. User Service then relays this user event to the other participating
product areas.
Auto fallback to primary for H.248 media gateways
This feature automatically returns a fragmented network, where a number of H.248 media
gateways are being serviced by one or more Local Survivable Processors (LSP), to the primary
media server. This feature is targeted to H.248 media gateways only.
This feature allows the administrator to define any of the following rules for migration:
●
Whether or not the media gateways, serviced by LSPs, should automatically migrate to the
primary media gateway.
●
Whether or not the media gateway should migrate immediately when possible, regardless
of active call count.
●
Whether or not the media gateway should only migrate if the active call count is 0.
●
Whether or not the media gateway should only be allowed to migrate within a window of
opportunity, by providing day of the week and time intervals per day. This option does not
take call count into consideration.
●
Whether or not the media gateway should be migrated within a window of opportunity by
providing day of the week and time of day, or immediately if the call count reaches 0. Both
rules are active at the same time.
Internally, the primary call controller gives priority to registration requests from those media
gateways that are currently not being serviced by an LSP. This priority is not administrable.
For more information, see Administration for Network Connectivity for Avaya Communication
Manager, 555-233-504.
Issue 1.1 June 2006
45
What’s New
Button pushes in list trace station command
The list trace station n command, where n is the station that you want to trace, now
provides information on button pushes at the traced station.
Connection preserving failover/failback for H.248 media gateways
The Connection Preserving Migration (CPM) feature preserves existing bearer (voice)
connections while an H.248 media gateway migrates from one Communication Manager server
to another. Migration might be caused by a network or server failure.
Only stable calls are preserved. Call that are not preserved are:
●
Unstable calls. An unstable is any call where the call talk path between parties has not
been established, or is not currently established. Some examples are:
- Calls with dial tone
- Calls in dialing stage
- Calls in ringing stage
- Calls listening to announcements
- Calls listening to music
- Calls on hold (soft, hard)
- Calls in ACD queues
- Calls in vector processing
●
IP trunks, both SIP and H.323
●
ISDN-BRI telephones
●
ISDN-BRI trunks
Users on connection-preserved calls cannot use such features as Hold, Conference, or
Transfer.
For more information, see Maintenance Procedures for Avaya Communication Manager 3.0,
Media Gateways and Servers, 03-300432.
46 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
Connection preserving upgrades for duplex servers
The connection preserving upgrades for duplex servers feature provides connection
preservation on upgrades of duplex servers for:
●
connections involving IP telephones
●
connections involving TDM connections on port networks
●
connections on H.248 gateways
●
IP connections between port networks and media gateways
Stable calls are preserved. Unstable calls are dropped.
Note:
Note:
This feature applies to upgrades from Communication Manager release 3.0 to a
future release of Communication Manager. This feature does not apply to
upgrades from a previous release of Communication Manager to Communication
Manager release 3.0.
Disable active logins
In the Days To Disable After Inactivity field on the Login screen, you can specify the number
of days of inactivity, from 1 to 180, before the login is automatically disabled. The default value
is blank, which means that the disabling feature is turned off for this login.
Display for bridged no-ring calls
The Feature-Related System Parameters screen now provides a new field, Display
Information With Bridged No Ring Call. The default value for this field is n. If you set this field
to y, the caller's name and number appear on the display of a telephone receiving a bridged
no-ring call.
E-mail backups no longer supported
The email option for performing server backups on an S8X00 Media Server is no longer
supported.
Issue 1.1 June 2006
47
What’s New
Emergency calls from unnamed IP endpoints
With the Emergency calls from unnamed IP endpoints feature, an IP telephone can register
without an extension number. The Emergency calls from unnamed IP endpoints feature places
the IP telephone into Terminal Translation Initialization (TTI) service. Users can dial a feature
access code (FAC) to either associate an extension number with a telephone, or to dissociate
an extension number from a telephone.
If Communication Manager is appropriately administered, a user can use an IP telephone that is
in TTI service to make emergency or other calls.
The Emergency Calls from Unnamed IP Endpoints feature requires IP telephone software R2.3
or later, and TN799C hardware circuit packs vintage 3 or later.
Note:
Note:
Turning on the Emergency Calls from Unnamed IP Endpoints feature turns off the
re-registering of endpoints that are unregistered. An example is when an
extension is moved to another telephone when using IP Softphone (IP Softphone
has control of the extension).
Enhanced quality for Music On Hold
Music On Hold delivered using the G.711 codec by a source that is not on the same media
gateway or port network as the caller has better quality than if delivered using the G.729 codec.
To ensure using the G.711 codec, set the Always Use G.711 (30ms, No SS) For Intra-Switch
Music-On-Hold field on the IP-Options System Parameters screen to y.
Enterprise Survivable Servers
The Enterprise Survivable Server (ESS) provide survivability by allowing backup servers to be
placed in various locations in the customer network. The backup servers supply service to port
networks in the case where the S8500-series media server, or the S8700-series media server
pair fails, or connectivity to the main server or server pair is lost.
In an ESS environment, there can only be one main server, either one S8500-series media
server, or one pair of S8700-series media servers. If the main server is an S8500-series media
server, all ESSs in the configuration must also be S8500-series media servers. During normal
operation, the main server communicates with and controls all the port networks. The main
server contains a license file that identifies the server as the main server and activates the ESS
functionality.
For more complete information on ESS, see the Avaya Enterprise Survivable Server (ESS)
Users Guide, 03-300428.
48 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
Enterprise Wide Licensing
Enterprise Wide Licensing (EWL) is a technology within Communication Manager release 3.0
and Remote Feature Activation (RFA). EWL is used to partially support a developing offer
known as Enhanced Software License Program (ESLP). ESLP gives customers the ability to
bulk purchase and then share license capacities across multiple locations.
Note:
Launch of the ESLP offer is to be announced at a later date.
Note:
Expanded Meet-me Conferencing
Use the Expanded Meet-me Conferencing application to set up multi-party conferences
consisting of more than six parties. The Expanded Meet-me Conferencing application supports
up to 300 parties.
The actual number of ports that are available for Expanded Meet-me Conferencing is
determined by the Communication Manager license file. The license file allocates ports in
groups of 50. For example, the license file can allocate 50, 100, 150, 200, 250, or 300 ports.
The maximum number of parties included in any single conference is administered with
Communication Manager.
The Expanded Meet-me Conferencing application requires an external Avaya Expanded
Meet-me Conferencing S8500B Server. For more information, see the Expanded Meet-me
Conferencing section of the Feature Description and Implementation for Avaya Communication
Manager, 555-245-205. See also Avaya Expanded Meet-me Conferencing Server on page 65.
Extension to Cellular
In addition to features in previous releases of Communication Manager and Extension to
Cellular, Extension to Cellular enhancements for release 3.0 include the following:
●
The Self Administration Feature (SAFE) Access Code allows users to self-administer their
cell phone number. Users can add or change their cell phone number through this feature
access code. An administrator can still enter or change cell phone numbers.
●
A barge-in tone increases security for Extension to Cellular calls. The tone alerts parties
on an active Extension to Cellular call when another person joins the call on the Extension
to Cellular associated office phone. The barge-in tone works only when the exclusion
feature is not activated.
Issue 1.1 June 2006
49
What’s New
●
Calls are redirected by Redirect on OPTIM Failure (ROOF) procedures if a call terminates
to an Extension to Cellular user cell phone (of any application type) that does not have an
associated office phone (or other method of terminating to a physical phone) or the office
phone is out of order and Communication Manager receives a disconnect prior to the call
being answered. The procedure redirects the call so that the caller does not hear ringback
forever. In general, the ROOF procedures apply to busy treatment.
●
Three new Feature Name Extensions are added:
- Automatic Call Back allows a user to choose whether they want an extension to
automatically call them back. Users are called back when they place a call to a busy or
unanswered telephone and after the called telephone becomes available to receive a
call.
- Call Pickup Extended Group allows a user to answer calls that were directed to another
call pickup group.
- Whisper Page Activation allows a user to make whisper pages. A whisper page is a low
volume message. Users can send a whisper page when they want only one person on a
conference call to hear a message.
For more information, see the following documents:
●
Avaya Extension to Cellular and Off-Station PBX (OPS) Installation and Administration
Guide, 210-100-500
●
Avaya Extension to Cellular User Guide, 210-100-700
Improved button downloads for IP telephones
This feature greatly reduces the time that the system needs to send button labels to an
IP telephone upon a new registration. This feature also reduces system traffic that is sent to
IP telephones upon a re-registration when button labels have not changed.
This improvement applies to IP telephones that are running 3.0 firmware. This feature does not
apply to DCP telephones.
Improved voice mail coverage at WAN failure
When a Wide Area Network (WAN) failure occurs and a Local Spare Processor (LSP) takes
over, Communication Manager now includes called-party information in voice mail.
50 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
Increased packet size supported
On the IP Codec Set screen, Communication Manager supports packets of up to 120
milliseconds for voice and modem-relay calls using codec G.729, G.723-5.3K, or G.723-6.3K.
Integrating IP-connected port networks with direct/multi-connect
configurations
Starting with Communication Manager release 3.0, the system allows configurations that mix
IP-connected port networks with existing center stage switches (CSS), asynchronous
transmission mode (ATM) networks, and direct-connected port networks.
Communication Manager allows the S8700-series media servers to support configurations that
combine IP-connected port networks (PNs) with direct-connect PNs, CSS-connected PNs, or
ATM-connected PNs.
Additionally, Communication Manager allows the media servers to support configurations that
contain both single control networks and duplicated control networks, and both single bearer
networks and duplicated bearer networks.
A Communication Manager configuration can contain a mix of the following port network
connectivity (PNC) methods:
Note:
●
IP-connect and direct-connect
●
IP-connect and Center Stage Switch (CSS)
●
IP-connect and Asynchronous Transmission Mode (ATM)
Note:
You cannot mix CSS and ATM port network connections in the same
configuration. You also cannot mix direct-connect PN connections with ATM or
CSS port network configurations.
Issue 1.1 June 2006
51
What’s New
Inter-Gateway Alternate Routing
Inter-Gateway Alternate Routing (IGAR) is designed for single-server systems that use the
IP-WAN to connect bearer traffic between port networks or media gateways. IGAR provides a
means of alternately using the public switched telephone network (PSTN) when the IP-WAN is
incapable of carrying the bearer connection.
IGAR may request that bearer connections be provided by the PSTN under the following
conditions:
●
The number of calls allocated or bandwidth allocated via Call Admission
Control-Bandwidth Limits (CAC-BL) has been reached
●
VoIP RTP resource exhaustion in a MG/PN is encountered
●
A codec set is not specified between a network region pair
●
Forced redirection between a pair of network regions is configured
IGAR takes advantage of existing public and private network facilities provisioned in a network
region. Most trunks in use today can be used for IGAR. Examples of the better trunk facilities for
use by IGAR are:
●
Public or Private ISDN PRI/BRI
●
R2MFC
IGAR provides enhanced Quality of Service (QoS) to large distributed single-server
configurations.
For more information, see Administration for Network Connectivity for Avaya Communication
Manager, 555-233-504.
List IP addresses for IP interface circuit packs
The command list ip-interface now provide the IP address that is associated with each
IP interface circuit pack.
Locally sourced announcements and music
Use the Locally Sourced Announcements and Music feature to access announcement and
music audio sources on a local port network or media gateway.
Locally sourced audio can:
●
Improve the quality of audio
●
Reduce resource usage, such as VoIP resources
●
Provide a backup mechanism for announcement and music sources
52 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
MLPP privileges at any endpoint
You can now activate the MLPP privileges specified on the Multiple Level Precedence &
Preemption Parameters screen at any endpoint by entering a special code. To administer this
code, set the Limited Line Load Control Origination field on the Multiple Level Precedence
& Preemption Parameters screen to y. Then set the Authorization Access Code field on the
MLPP Features page of the Feature Access Codes (FAC) screen to the desired code.
Modem over IP
The modem over IP (MoIP) feature allows for transport of data over a 64kbps unrestricted clear
channel. Starting with Communication Manager release 3.0, when a clear channel data call is
originated, the system communicates to the media processor or VoIP engine to allow a 64kpbs
clear channel to be opened for transport.
For more information, see Administration for Network Connectivity for Avaya Communication
Manager, 555-233-504.
More options for changing display messages
You can now change user-defined static display messages not only when you type the change
display-messages command, but also by editing the files /etc/opt/defty/i18n/
avaya_user-defined.txt and /etc/opt/defty/i18n/custom_user-defined.txt.
More system-wide message retrieval extensions
The number of extensions on the Feature-Related System Parameters screen, that can have
the System-Wide Message Retrieval capability on an S8710, S8700, S8500, or S8300 Media
Server, has increased from 10 endpoints to 30 endpoints.
Multiple SNMP trap destinations
The bash command almsnmpconf now supports multiple SNMP trap destinations.
Issue 1.1 June 2006
53
What’s New
Native support of NI-BRI data
Communication Manager supports U.S. national ISDN (NI-1 and NI-2) NI-BRI endpoints, as well
as NI-BRI data. This feature meets the criteria that is set by the U.S. Government Department of
Defense to be certified as a small end office (SMEO) solution.
This enhancement also allows the S8300 and S8700 media servers, with G350 and G700
H.248 media gateways, to support BRI endpoints.
Prevent MLPP preemption of emergency calls
You can now prevent emergency calls from being preempted by the Multiple Level Precedence
& Preemption (MLPP) feature. To do so, set the Pre-Empt Emergency Call field on the
Multiple Level Precedence & Preemption Parameters screen to n.
QSIG support for Unicode
The QSIG support for Unicode feature extends the Unicode support on a single server to
multi-node Communication Manager networks. This feature allows Unicode support across
large campus configurations.
Many configurations contain multiple Communication Manager servers due to scalability
requirements. This feature also allows Unicode support across large corporate networks,
frequently multinational corporations, where multiple Communication Manager servers are
almost always provisioned.
RAM disk for S8300 Media Server
RAM disk capabilities are now available on an S8300 Media Server.
Remove assigned DID
In the Property Management System (PMS), you can now remove the direct inward dial (DID)
number that is assigned to a room using a VIP message without going through the checkout
process.
54 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
Ringback during coverage interval
The Hunt Group screen now contains the Provide Ringback field. This field is available if the
value of the Message Center field is qsig-mwi.
If you set the Provide Ringback field to y, a call covering to the message center provides
ringback to the caller during the coverage interval.
Secure Shell and Secure FTP for circuit packs
This development addresses customers security concerns by adding Secure Shell (SSH) and
and secure FTP (SFTP) remote access protocols to these circuit packs:
●
TN799DP (CLAN)
●
TN2501 (VAL)
●
TN2312AP/BP (IPSI)
New SAT commands enable SFTP sessions through login/password authentication on the
CLAN and VAL circuit packs. The Maintenance Web Interface and command line interface (CLI)
continue to enable the IPSI session. The Telnet and FTP capabilities remain enabled on these
circuit packs.
Security of IP telephone registration/H.323 signaling channel
Note:
Note:
Please check with your Avaya Sales Representative or your Avaya Authorized
Business Partner for availability of this feature.
This feature provides a secure mechanism for an H.323 endpoint and a Communication
Manager gatekeeper to mutually authenticate themselves and the contents of the messages
that they exchange during IP registration, admission, and status (RAS). This authentication is
based on the simple 3-to-8 digit PIN administered for each extension, the H.235 Annex H SP1
Execution of Encrypted Key Exchange (EKE) procedures during RAS results in the negotiation
of a strong secret that is shared between the endpoint and the gatekeeper. This strong secret is
used to derive a set of secrets which are used to digitally sign all RAS and call signaling
messages, and to encrypt selected elements of call signaling messages, media session keys
and CCMS messages. If one or the other parties does not possess the correct PIN, the
computed shared secrets will, in fact, be different. Message authentication fails, and the parties
refuse to communicate.
Issue 1.1 June 2006
55
What’s New
In summary, these procedures permit:
●
The endpoint and the gatekeeper to authenticate each other;
●
The endpoint and the gatekeeper to sign/authenticate each message sent;
●
Privacy for selected elements of call signaling, including media session encryption keys
and dialed digits.
●
Security of the endpoint/gatekeeper communication even if an observer obtains the user's
PIN.
●
Security of past or future communications even if one session is penetrated by an attacker
with knowledge of the PIN. (This is known as "perfect forward secrecy".)
●
Reuse of the negotiated strong secret (identified by a unique session ID) to secure new
signaling links between parties for re-registration or trunking.
Serial number for license validation
The License Serial Numbers screen, that you can access with the list configuration
license command, displays the serial number for validating the server license.
Shorter time-out for list trace ras command
The list trace ras command from OSSI times out if it does not complete in 2 minutes,
rather than 15 minutes.
Station licensing
Prior to release 2.0, Communication Manager was sold by licensed ports that included stations
and trunks. The system displayed the total of licensed ports in the Maximum Ports field on the
Optional Features screen.
As of release 2.0 of Communication Manager, Avaya sells licenses for stations, but not trunks.
Currently, the Maximum Ports field on the Optional Features screen is used for licensing
ports, which include both trunks and stations.
With Communication Manager release 3.0, a separate field, Maximum Stations, is created on
the Optional Features screen to track station licenses only. Customers can easily identify the
number of station licenses on the system.
56 What’s New in Avaya Communication Manager
Release 3.0 new features and enhancements
User-defined phone message files
The Communication Manager Phone Message File web page (formerly the Unicode Message
File web page) now shows user-defined files currently installed or available for installation.
Web interface from multiple IP addresses
You can now choose to enable access to the Web interface to Communication Manager from
multiple IP addresses.
By default, as a security measure, only the IP address that first accesses the interface has
permission to do so again. However, you can now disable this restriction with the bash
command webchkip disable. To re-enable the restriction, use the bash command
webchkip enable. To see the current status of the restriction, use the bash command
webchkip by itself.
Issue 1.1 June 2006
57
What’s New
58 What’s New in Avaya Communication Manager
Chapter 2: Hardware
This chapter presents highlights of any hardware as part of the most current releases of Avaya
Communication Manager running on Avaya DEFINITY® servers, as well as the Avaya S8000
series Media Servers (with associated Avaya Media Gateways).
Release 3.1.X hardware additions
Avaya Communication Manager, release 3.1.X, which includes 3.1.1. and 3.1.2, includes the
following general hardware additions.
G350 Media Gateway as a headquarters device
You can deploy multiple G350 Branch Gateways in branch offices and benefit from increased
telephony capacities and more configuration options. In the advanced mode, you can build any
G350 configuration and verify whether it meets the system resources limitation.
The G350 with an S8300B ICC can act as primary server for up to five G250 or G350 Media
Gateways, and you can install any combination of Media Modules, subject to certain rules.
Note:
Note:
The maximum capacities depend on the specific configuration of the Branch
Gateway.
Release 3.1 hardware additions
Avaya Communication Manager, release 3.1, includes the following general hardware
additions.
Issue 1.1 June 2006
59
Hardware
G250 DCP Media Gateway
The G250 DCP Media Gateway supports:
●
Four analog trunks, Loop Start only (no support for Ground Start or CAMA)
●
Two analog stations and/or DID trunks.
●
Twelve DCP ports
●
Two Ethernet LAN ports
●
One 10/10 Ethernet WAN port
●
One expansion slot for an ACM server module
●
One expansion slot for a data WAN media module
●
One console RS232 interface
●
One USB host interface
●
One contact closure relay control
●
ETR
USB support for G250 Media Gateway
Through the USB port on the front panel of the G250 Media Gateway, you can connect external
modems for WAN dial-up backup.
G250 DS1 Media Gateway
The G250 DS1 Media Gateway supports:
●
One T1/E1/PRI trunk with fractional trunks allowed
●
One analog trunk with loop start only (no support for ground start or CAMA)
●
Two analog lines and/or DID trunks (one with ETR)
●
ETR
●
Eight Ethernet LAN PoE ports
●
10/100 Ethernet WAN
●
One expansion slot for an ACM server module
●
One expansion slot for a data WAN media module
●
One console RS232 interface
●
One USB host interface
●
One contact closure relay control
60 What’s New in Avaya Communication Manager
Release 3.1 hardware additions
MM316 HDMM for G350 Media Gateway
The MM316 HDMM Media Module for the G350 branch gateway supports 40 10M/100M PoE
ports with 1G/100 Copper port. The MM316 HDMM allows supporting up to 40 IP endpoints
connected to the G350 Media Gateway with no external switch power.
MM716 analog media module
The MM716 Analog Media Module is a 24 port analog circuit pack. All ports are dedicated for
station (line). The station (line) ports support an LED Message Waiting Indicator, and are used
for DID trunk (wink or immediate start) port connections.
The MM716 is supported in the G350 and G700 Media Gateways. Communication Manager 3.0
or higher, and equivalent gateway software, is necessary to support the MM716.
S8400 Media Server
The S8400 Media Server is a Linux-based server that occupies a single slot in a standard TN
carrier. The S8400 Media Server provides Communication Manager processing functionality in
stand alone, single port network (PN), telephony systems requiring up to 900 stations.
The S8400 Media Server is composed of the:
●
TN8400AP Media Server circuit pack
●
TN8412AP S8400 IP Interface (SIPI) circuit pack
The S8400 Media Server can replace the:
●
CSI
●
DEFINITY One/S8100
●
IP600/S8100
The S8400 Media Server consists of a TN8400 hardware/software platform, Communication
Manager, and optionally, IA770 messaging software.
For new installations, the PN uses the G650 Media Gateway. In current installations, the S8400
Media Server is used as an upgrade path for a current PN based on G650 and G600 Media
Gateways and CMC carriers.
Issue 1.1 June 2006
61
Hardware
TN8412AP circuit pack
The S8400 Media Server uses the TN8412AP S8400 IP Interface (SIPI) circuit pack to provide:
●
Circuit pack control within its port network
●
Cabinet maintenance
●
Tone-clocks
●
Emergency transfer switch functionality
●
Customer/external alarms.
Note:
An S8400 system is shipped with a TN8412AP SIPI circuit pack. However, the
TN2312BP IPSI circuit pack is also compatible with S8400 systems.
Note:
The TN799DP Control-LAN (C-LAN) circuit pack provides firmware download functionality while
the TN2501 Voice Announcement over LAN (VAL) circuit pack provides announcement
functionality.
The S8400 Media Server provides a Voice over Internet Protocol (VoIP) based integrated
messaging capability for up to 450 light duty users. This option requires 8 ports of VoIP
resources be provisioned with the S8400 Media Server. The hard disk drive (HDD) stores the
messages and a TN2302AP IP Media Processor circuit pack usually provides the VoIP
resources.
S8720 Media Server
The S8720 (HP DL 385) is the next generation S87XX-series media server, succeeding the
S8710 media server. Most aspects of the S8720 are the same as the S8710, including:
●
Hardware architecture
●
Interfaces
●
Call flow
●
maIntenance
●
Serviceability
●
Software initialization, recovery, redundancy
●
Availability, reliability, and survivability strategies
Differences between the S8720 and S8710 include:
●
The S8720 has greater call processing performance than the S8710.
●
Software duplication is available on the S8720. The S8720 is ordered without the DAL1
card used for hardware duplication. Hardware duplication, and the DAL1 card, can be
purchased as an option.
62 What’s New in Avaya Communication Manager
Release 3.1 hardware additions
●
If software duplication is used with the S8720, the functions of the Eth0 and Eth2
interfaces are reversed with respect to the hardware duplication functions.
●
The S8720 has an additional (third) USB port located on the front panel.
●
There are minor differences in the mounting rails and how the rails attach to the S8720
and the rack.
Software Duplication
The software duplication feature eliminates the need for the DAL1 memory duplication cards in
duplicated S8720 servers. This feature is supported only on the S8720 media server.
The S8720 is shipped without the DAL1 hardware duplication card. Hardware duplication is an
option for the S8720. If purchased, the DAL1 hardware duplication cards, and the dual fiber
cable linking the DAL1 cards, are installed in the S8720 media servers at the customer site. The
duplication type (hardware or software) is administered as a Configure Server step on a new
Server Duplication web page in the Maintenance Web Interface.
For software duplication, memory duplication messages are sent over the server duplication
TCP/IP link. This link uses a dedicated or non-dedicated TLS connection and TCP port 5098.
Memory duplication messages can optionally use AES encryption.
! CAUTION:
CAUTION:
Software duplication degrades the performance of the communications system
as compared with hardware duplication. Encrypting duplication messages will
further degrade performance. For software duplication, Avaya recommends a
dedicated duplication link. If the duplication link is routed or switched, the link
should have a bandwidth of 1 Gigabit per second.
Issue 1.1 June 2006
63
Hardware
Release 3.0 hardware additions
Avaya Communication Manager, release 3.0, includes the following general hardware
additions.
4621SW IP telephone
The 4621SW IP telephone is based on the 4620SW IP telephone. The 4621SW IP telephone
has a large screen with an adjustable backlit graphic display. The 4621SW IP telephone does
not support IR interface.
The 4621SW IP telephone has the following features:
●
The same interface as the 4620SW IP telephone
●
A backlight that can be adjusted by the user. The backlight can be administered to turn off
when the telephone is idle, or it can stay lit continuously.
●
Native support that gives the customer the ability to administer and maintain the telephone
without using an alias
●
The 4621SW IP telephone supports the EU24BL adjunct. The EU24BL is the same as the
EU24 adjunct, except that the EU24BL adjunct has a backlit display.
4622SW IP telephone
The 4622SW IP telephone is based on the 4620SW IP telephone. The 4622SW telephone
provides the same advanced feature functionality, with an intuitive and innovative user interface
as the 4620SW IP telephone. The 4622SW telephone is designed for the call center
environment. The 4622SW IP telephone does not support IR interface.
The 4622SW has the following features:
●
Two headset jacks
●
A large screen backlit graphic display
●
A backlight that can be adjusted by the user. The backlight can be administered to turn off
when the telephone is idle, or it can stay lit continuously.
●
The telephone stand has one extra height setting. This setting is the same as the highest
setting for the 4610SW telephone.
●
Native support that gives the customer the ability to administer and maintain the telephone
without using an alias
●
The 4622SW IP telephone supports the EU24BL adjunct. The EU24BL is the same as the
EU24 adjunct, except that the EU24BL adjunct has a backlit display.
64 What’s New in Avaya Communication Manager
Release 3.0 hardware additions
4625SW IP telephone
The 4625SW IP telephone is similar to the 4620SW IP telephone. The 4625SW provides the
same advanced feature functionality with an intuitive and innovative user interface as the
4620SW IP telephone. The 4625SW telephone provides telephony, speed dial, call log, and
Web browsing functionality. The 4625SW IP telephone has all of the applications and options of
the 4620SW IP telephone.
The 4625SW has the following features:
●
A color 1/4-VGA backlit display
●
Native support that gives the customer the ability to administer and maintain the telephone
without using an alias
The 4625SW IP telephone does not support:
●
Multi-byte characters
●
Multi-byte user interface languages
●
An IR interface
Avaya Expanded Meet-me Conferencing Server
The Avaya Expanded Meet-me Conferencing Server is an S8500B server that connects to a
Communication Manager server over the customer LAN to provide Expanded Meet-me
Conferencing. Expanded Meet-me Conferencing supports a conference bridge of up to 300
ports. This increase in the number of parties on a conference is much greater than the limit of a
6-port conference bridge on a Communication Manager system without Expanded Meet-me
Conferencing.
All SIP-enabled media servers can use the Avaya Expanded Meet-me Conferencing Server and
the Expanded Meet-me Conferencing feature of Communication Manager. All Communication
Manager telephones can use Expanded Meet-me Conferencing. However, for SIP telephones
and SIP softphone to be able to use Expanded Meet-me Conferencing, the Communication
Manager configuration also requires the Converged Communication Server (CCS).
Converged Network Analyzer
The Converged Network Analyzer (CNA) is a distributed system for real-time monitoring of IP
networks. CNA uses active measurements. CNA supports various network tests including
connectivity tests with pings, topology tests with traceroute, and QoS tests with synthetic RTP
streams.
Issue 1.1 June 2006
65
Hardware
Within a CNA system, test plugs are the entities that execute the tests according to instructions
from CNA schedulers, and return the results. For more information about administrating the
CNA system, see IM R3.0 Converged Network Analyzer (CNA) Configuration.
DNS Resolver for gateways
The G350/G250 supports the DNS Resolver application, as part of VPN enhancements. A DNS
Resolver resolves host names to IP addresses. It does this by querying DNS servers according
to an ordered list. The list of DNS servers is compiled using either DNS servers entered
manually by the user, or DNS servers gathered automatically by means of DHCP or PPP
protocols, or both.
The user can also optionally aid the DNS Resolver by specifying a list of domain names that the
DNS Resolver adds as a suffix to non-FQDN names, to help resolve them to an IP address. The
DNS Resolver feature is intended to provide a backup mechanism for VPN hubs using DNS.
For more information see the Technical Summary for G350/G250 R3.0 VPN.
G250 Media Gateway
The G250 Media Gateway is designed for very small branch offices (2-8 users) of large
enterprises that seek a centrally-managed branch solution, a seamless element of the
enterprise’s communication network.
The G250 is available in two different models:
●
G250-Analog
●
G2500-BRI
Each model has a different front-panel configuration based on the interface(s) necessary the
the endpoints that connect to the two media modules that it houses. Each of these G250 models
provides:
Note:
●
Analog and IP telephony
●
Local connectivity to the PSTN
●
LAN/PoE infrastructure
●
Secured WAN connectivity to the enterprise headquarters
Note:
The G250 Media Gateway supports legacy analog telephones, but not DCP
telephones.
66 What’s New in Avaya Communication Manager
Release 3.0 hardware additions
G250 is a gateway subtending to a Communication Manager server located at a larger branch
or at the enterprise headquarters. This means that the gateway gets its call control from the
Communication Manager server in its intermediary position between the server and the
endpoints that it serves. The WAN connection between the small office (gateway and endpoints)
and the server can be over a public IP network and/or private network (frame relay, leased line,
etc.).
The G250 Media Gateway has two survivability options:
●
Basic local survivability functionality, or Standard Local Survivability that is resident in the
media gateway firmware
●
Full survivability with a S8300B server as its Local Survivable Processor (LSP), offering
complete Communication Manager functionality.
Gateways that are connected to a non-private network have these security features:
●
IPSec VPN capabilities for up to 3 tunnels for signal and/or bearer information to the
enterprise headquarters
●
Pre-configured firewall for general access to public IP networks
For more information on the G250 Media Gateway, see the Overview for the Avaya G250 and
the Avaya G350 Media Gateways, 03-300435.
Standard Local Survivability
Standard Local Survivability (SLS) provides a local G250 Media Gateway with a limited subset
of Communication Manager functionality when there is no IP-routed WAN link available to the
main server.
Note:
SLS is not supported on the G250-BRI.
Note:
SLS provides:
●
Outbound dialing through the local PSTN (local trunk gateway) from analog and IP phones
●
Inbound calls from each trunk to pre-configured local analog or IP phones that have
registered
●
Local call progress tones (dial tone, busy, etc.)
●
Emergency Transfer Relay (ETR) in survivable mode on the media gateway hardware in
cases of power loss
Issue 1.1 June 2006
67
Hardware
SP-1020A SIP business telephone
The SP-1020A SIP business telephone, also known as the Toshiba® SIP handset,
communicates with Communication Manager through a SIP trunk group. The SP-1020A SIP
business telephone requires Communication Manager release 3.0 or later.
The SP-1020A SIP business telephone is designed by Toshiba initially for the Japanese market,
but has long-range implications for other markets as well.
The SP-1020A SIP business telephone has:
●
24-feature buttons
●
duplex speakerphone
●
4-line display supporting English and Japanese characters
●
Menu key and navigation keys for operations, including a 20-entry call log
●
Full SIP-compliant signaling with these expanded features:
- automatic callback
- whisper page
- speed dial list
- send all calls
- message waiting indication and full integration with Avaya voice mail systems
- VIP priority calling
- Call pickup - directed, group, and extended
- Distinctive alerting - priority, internal, external, and intercom
- Intercom calling
- Hold recall
- Transfer recall
●
Other features include:
- Automatically downloadable “personality” including volume levels, button placement, and
ringer settings to provide true mobility from handset to handset across the network
- IEEE standard power over Ethernet
- Terminal upgrades
68 What’s New in Avaya Communication Manager
Release 3.0 hardware additions
TN2602AP IP Media Resource 320 circuit pack
The TN2602AP IP Media Resource 320 circuit pack provides high-capacity voice over Internet
(VoIP) protocol audio access to the switch for local stations and outside trunks. The TN2602AP
IP Media Resource 320 circuit pack provides audio processing for the following types of calls:
●
TDM-to-IP and IP-to-TDM
●
IP-to-IP
The TN2602AP IP Media Resource 320 circuit pack has two capacity options, both of which are
determined by the license file installed on Communication Manager:
●
320 voice channels, considered the standard IP Media Resource 320
●
80 voice channels, considered the low-density IP Media Resource 320
Up to two TN2602AP circuit packs may be installed in a single port network for load balancing.
The TN2602AP circuit pack is also compatible with and can share load balancing with the
TN2302 IP Media Processor circuit pack. Actual capacity might be affected by a variety of
factors, including the codec that is used for a call and fax support.
Note:
The TN2602AP IP Media Resource 320 is not supported in CMC1 and G600
Media Gateways.
Note:
The TN2602AP IP Media Resource 320 circuit pack supports hairpin connections and shuffling
of calls between TDM connections and IP-to-IP direct connections. The TN2602AP can also
perform the following functions:
●
Echo cancellation
●
Silence suppression
●
Adaptive jitter buffer (120 ms)
●
Dual-tone multifrequency (DTMF) detection
●
AEA Version 2 and AES media encryption
●
Conferencing
●
802.1p and 802.Q layer 2 QoS mechanisms
●
RSVP protocol
The TN2602AP IP Media Resource 320 circuit pack supports the following codecs for voice,
conversion between codecs, and fax detection:
●
G.711, A-law or Mu-law, 64 kbps
●
G.726A-32 kbps
●
G.729 A/AB, 8 kbps audio
Issue 1.1 June 2006
69
Hardware
The TN2602AP also supports transport of the following devices:
●
Fax, Teletypewriter device (TTY), and modem calls over a corporate IP intranet using
pass-through mode
●
64-kbps clear channel transport in support of firmware downloads, BRI secure telephones,
and data appliances
●
Fax and TTY calls using proprietary relay mode
Note:
Note:
The path between endpoints for fax and modem transmissions must use Avaya
telecommunications and networking equipment. T.38 fax is not supported.
!
SECURITY ALERT:
SECURITY ALERT:
Faxes sent to non-Avaya endpoints cannot be encrypted.
70 What’s New in Avaya Communication Manager
Chapter 3: New and changed screens
This chapter displays the new and changed administration screens for Avaya Communication
Manager.
Release 3.1 new screens
Avaya Communication Manager, release 3.1, includes the following new screens. For a more
complete explanation of the screens and their function, see the Administrator Guide for Avaya
Communication Manager, 03-300509.
Enable Session
Use this screen to enable a SSH instead of a Telnet session. This screen was prompted by the
Secure Shell and Secure FTP feature.
To view the Enable Session screen:
1. Type enable session. Press Enter.
The system displays the Enable Session screen (Figure 1: Enable Session screen on
page 71).
Figure 1: Enable Session screen
enable session a03
Page 1
ENABLE SESSION
Login:______
Password:___________
Password:___________
Secure?
Time to Login:
Issue 1.1 June 2006
71
New and changed screens
Field descriptions
Login - Enter your login.
Valid entries
Usage
3 to 6 alphanumeric characters
Enter your login.
Password - Enter your password.
Valid entries
Usage
7 to 11 characters, with at least one number
Enter your password.
Password - Repeat your password for verification. Entry must be identical in both Password
fields.
Valid entries
Usage
7 to 11 characters, with at least
one number
Repeat your password for verification. Entry must be
identical in both Password fields.
Secure - Enter y to indicate that SSH is used instead of Telnet.
Valid entries
Usage
y/n
Enter y to indicate that SSH is used instead of Telnet. Default is y.
Time to Login - This field appears only if the board in question is a TN2302.
Valid entries
Usage
0 to 255
Enter the number of minutes to login before the session times out. Default
is blank.
72 What’s New in Avaya Communication Manager
Release 3.1 new screens
Survivable Processor
Use the Survivable Processor screen to add information specific to a Local Survivable
Processor (LSP) or an Enterprise Survivable Server (ESS). Before administering this screen,
you must first assign node names for each LSP and ESS media server on the IP Node Names
screen. This screen was prompted by the Processor Ethernet feature.
While this screen is administered on the active main server, the information entered applies only
to LSPs and ESSs and does not apply to main servers. When translations are copied to an LSP
or ESS, the LSP/ESS replaces like translations for the main server with the overrides
administered on the Survivable Processor screens. That is, use the Survivable Processor
screen to administer overrides against adjunct links that have already been administered for the
main server(s).
Note:
Note:
The ESS server is first administered on the IP Node Names screen and then on
the System Parameters - ESS screen before it is administered on the
Survivable Processor screen. The information from the System Parameters ESS screen is automatically copied to the Survivable Processor screen. You do
not need to use the Survivable Processor screen for an ESS server unless one
of the supported adjuncts connects to the PE interface of the ESS server.
To view the Survivable Processor screen:
1. Type add survivable-processor node-name. Press Enter.
The system displays the Survivable Processor screen (Figure 2: Survivable Processor Processor Ethernet screen on page 73).
Figure 2: Survivable Processor - Processor Ethernet screen
add survivable-processor node-name
page 1 of x
SURVIVABLE PROCESSOR - PROCESSOR ETHERNET
Node Name:
IP Address:
ID:
Type:
node-name
135. 9. 72.106
30
LSP
Network Region: 1
Issue 1.1 June 2006
73
New and changed screens
Page 1
Field descriptions
The first page of the Survivable Processor screen displays the Processor Ethernet interface
information for the LSP or the ESS server. The information includes the node-name, the IP
address, the server type, the cluster ID, and the network region.
Network Region - The only administrable field on this page is the Network Region field.
Valid entries
Usage
1 to 250
Enter the network region in which the PE interface of the LSP or ESS
server resides.
2. Click Next to view the next page.
The system displays page 2 of the Survivable Processor screen (Figure 3: Survivable
Processor - Processor Channels screen on page 74).
Figure 3: Survivable Processor - Processor Channels screen
page 2 of x
SURVIVABLE PROCESSOR - PROCESSOR CHANNELS
Proc
Chan
Enable
1
i
Appl.
mis
Mode
s
Interface
Link/Chan
9
5001
Destination
Node
Port
CMS_hogan
0
Session
Local/Remote
1
1
Page 2
Field descriptions
Use this page to administer processor channels.
Appl - This display-only field identifies the server application type or adjunct connection used
on this channel. Currently mis is the only application displayed.
74 What’s New in Avaya Communication Manager
Release 3.1 new screens
Destination Node - This field identifies the server or adjunct at the far end of this link. This field
changes to display-only when you enter i(nherit) in the Enable field, showing the value
administered on the main server.
Valid entries
Usage
valid
administered
node name
Enter an adjunct name, server name, far end IP address, node name, or
leave blank for services local to this media server.
Destination Port - This field specifies the far-end port number of this link. This field changes to
display-only when you enter i(nherit) in the Enable field, showing the value administered on the
main server.
Valid entries
Usage
0, 5000 to 64500
Enter the number of the destination port. An entry of 0 means any port can
be used.
Enable - Use this field to specify how data for this processor channel is transferred to the
survivable processor.
Valid entries
Usage
i(nherit)
Enter i(nherit) to indicate that this link is to be inherited by the LSP or ESS
server. When you enter i(nherit), all fields in the row for this processor
channel change to display-only. The survivable processor inherits this
processor channel just as it is administered on the main server. You
generally use the i(nherit) option in the following situations:
● The main server connects to the adjuncts using a CLAN and you
want the ESS server to use the same connectivity
● The main server connects to the adjuncts using the PE interface of
the main server and you want the LSP or ESS server to connect to
the adjunct using its PE interface
n(o)
This processor channel is disabled on the LSP or the ESS server. The
survivable processor does not use this channel. This is the default.
o(verwrite)
The survivable processor overwrites the processor channel information
sent from the main server with the information from this screen. The
o(verwrite) option causes the Interface Link field to change to
display-only with a value of p. Use the remaining editable fields to enter
the processor channel information for the LSP or ESS server.
Interface Channel - This field identifies the channel number or the TCP/IP listen port channel
to carry this processor (virtual) channel. For TCP/IP, interface channel numbers are in the range
5000 to 64500. The value 5001 is recommended for CMS, and 5003 is recommended for DCS.
Issue 1.1 June 2006
75
New and changed screens
This field changes to display-only when you enter i(nherit) in the Enable field, showing the
value administered on the main server.
Valid entries
Usage
1 to 64
For link type x.25.
0, 5000 to 64500
For ethernet or ppp. The channel number 0 means any port can be
used.
Interface Link - This display-only field identifies the physical link carrying this processor
(virtual) channel. When you enter o(verwrite) in the Enable field, the value of this field changes
to p (processor).
Mode - Indicate whether the IP session is passive (client) or active (server). This field changes
to display-only when you enter i(nherit) in the Enable field, showing the value administered on
the main server.
Valid entries
Usage
c(lient)
Indicate whether the IP session is passive c(lient) or active s(erver).
s(erver)
Proc Chan - This display-only field shows the processor channel number used for this link
when it was administered on the Processor Channel Assignment screen.
Session - Local/Remote - Local and Remote Session numbers must be consistent between
endpoints. These fields change to display-only when you enter i(nherit) in the Enable field,
showing the values administered on the main server.
Valid entries
Usage
1 to 256 (si)
1 to 384 (r)
or blank
For each connection, the Local Session number on this media server must
equal the Remote Session number on the remote media server and vice
versa. It is allowed, and sometimes convenient, to use the same number
for the Local and Remote Session numbers for two or more connections.
3. Click Next to view the next page.
The system displays page 3 of the Survivable Processor screen (Figure 4: Survivable
Processor - IP-Services screen on page 77).
76 What’s New in Avaya Communication Manager
Release 3.1 new screens
Figure 4: Survivable Processor - IP-Services screen
page 3 of x
SURVIVABLE PROCESSOR - IP-SERVICES
Service
Type
Enabled
CDR1
CDR2
i
i
Local
Node
Local
Port
Remote
Node
Remote
Port
gert_clan6
gert_clan1
0
0
cdr_1
cdr_rsp
9003
9000
Page 3
Field descriptions
Use this page of the Survivable Processor screen to administer IP services.
Enabled - Use this field to specify how data for each specified service type is transferred to the
survivable processor.
Valid entries
Usage
i(nherit)
Enter i(nherit) to indicate that this link is to be inherited by the LSP or ESS
server. When you enter i(nherit), all fields in the row for this service type
change to display-only. The survivable processor inherits this service type
just as it is administered on the main server. You generally use the
i(nherit) option in the following situations:
● The main server connects to the adjuncts using a CLAN and you
want the ESS server to use the same connectivity
● The main server connects to the adjuncts using the PE interface of
the main server and you want the LSP or ESS server to connect to
the adjunct using its PE interface
n(o)
This IP services link is disabled on the LSP or the ESS server. This is the
default.
o(verwrite)
The survivable processor overwrites the service type information sent from
the main server with the information from this screen. Entering o(verwrite)
causes the Local Node field to change to procr. Use the remaining
editable fields to enter the information for the LSP or ESS server.
Local Node - This display-only field contains the node name as defined on the IP Node Names
screen.
Issue 1.1 June 2006
77
New and changed screens
Local Port - This display-only field contains the originating port number. For client applications
such as Call Detail Recording (CDR), this field defaults to 0.
Remote Node - This field becomes editable when you enter o(verwrite) in the Enable field.
Specify the name at the far end of the link for the CDR. The remote node should not be defined
as a link on the IP Interfaces or Data Module screens. This field does not apply for AESVCS.
Remote Port - This field becomes editable when you enter o(verwrite) in the Enable field.
Specify the port number of the destination. Valid entries range from 5000 to 65500 for CDR or
AESVCS. The remote port number must match the port administered on the CDR or AESVCS
server.
Service Type - This field is display-only and reflects the value administered in the Service
Type field on the IP Services screen. Valid entries include CDR1 or CDR2, and AESVCS.
4. Click Next to view the next page.
The system displays page 4 of the Survivable Processor screen (Figure 5: Survivable
Processor - IP-Services - Session Layer Timers screen on page 78).
Note:
Note:
This page appears if CDR1 or CDR2 is administered on the Survivable
Processor - IP-Services page of the Survivable Processor screen. These
fields are only administrable if the Enable field on that page is set to o(verwrite).
Figure 5: Survivable Processor - IP-Services - Session Layer Timers screen
page 4 of x
SURVIVABLE PROCESSOR - IP-SERVICES - Session Layer Timers
Service
Type
CDR1
CDR2
Reliable
Protocol
n
y
Packet Resp
Timer
30
30
78 What’s New in Avaya Communication Manager
Session Connect
Message Cntr
3
3
SPDU
Cntr
Connectivity
Time
3
3
60
60
Release 3.1 new screens
Page 4
Field descriptions
Connectivity Time - Use this field to set the amount of time that the link can be idle before
Communication Manager sends a connectivity message to ensure the link is still up. This field is
only administrable if the Enable field on the SURVIVABLE PROCESSOR - IP-SERVICES page
of the Survivable Processor screen is set to o(verwrite).
Valid entries
Usage
1 to 255
Enter the desired interval in seconds. Default is 60.
Packet Resp Timer - Use this field to specify the number of seconds to wait from the time a
packet is sent until a response (acknowledgement) is received from the far-end, before trying to
resend the packet. This field is only administrable if the Enable field on the Survivable
Processor - IP-Services page of the Survivable Processor screen is set to o(verwrite).
Valid entries
Usage
1 to 255
Enter the desired interval in seconds. Default is 30.
Reliable Protocol - Use this field to indicate whether you want to use a reliable protocol over
this link. This field is only administrable if the Enable field on the Survivable Processor IP-Services page of the Survivable Processor screen is set to o(verwrite).
Valid entries
Usage
y/n
Enter y to indicate that you want to Use reliable protocol if the adjunct on
the far end of the link supports it. Default is y.
Service Type - This field is display-only and corresponds to the Service Type entry on the
Survivable Processor - IP-Services page of the Survivable Processor screen.
Session Connect Message Cntr - The Session Connect Message counter indicates the
number of times Communication Manager tries to establish a connection with the far-end
adjunct.
Valid entries
Usage
1 to 5
Enter the desired number of connection attempts.
Issue 1.1 June 2006
79
New and changed screens
SPDU Cntr - The Session Protocol Data Unit (SPDU) counter indicates the number of times
Communication Manager transmits a unit of protocol data before generating an error.
Valid entries
Usage
1 to 5
Enter the desired number of transmission attempts.
Release 3.0 new screens
Avaya Communication Manager, release 3.0, includes the following new screens. For a more
complete explanation of the screens and their function, see the Administrator Guide for Avaya
Communication Manager, 03-300509.
Announcement Group Board Usage
A new screen, the Announcement Group Board Usage screen, displays all the audio groups
in a system. This change is prompted by the Locally sourced announcements and music
feature.
To view the Announcement Group Board Usage screen:
1. Type list usage integ-annc-board n, where n is the 5-character circuit pack
location number. Press Enter.
The system displays the Announcement Group Board Usage screen
(Figure 6: Announcement Group Board Usage screen).
Figure 6: Announcement Group Board Usage screen
list usage integ-annc-board 01B18
Page 1
ANNOUNCEMENT GROUP BOARD USAGE
USED BY
Announcement
Audio Group
Audio Group
Announcement
Group
Group
2087
4
23
80 What’s New in Avaya Communication Manager
Extension
Member
Member
3005
28
101
Release 3.0 new screens
Audio Group
The Audio Group screen allows an administrator to add, change, or delete audio source
locations in an audio group. This change is prompted by the Locally sourced announcements
and music feature.
To view the Audio Group screen:
1. Type add audio-group n, where n is the group number. Press Enter.
The system displays the Audio Group screen (Figure 7: Audio Group screen on page 81).
Figure 7: Audio Group screen
add audio-group 1
Page 1 of 4
AUDIO GROUP 1
Group Name: Relaxation Music__
AUDIO SOURCE LOCATION
1: __01A0905
2: ___ 019v9
3: ________
4: ________
5: ________
6: ________
7: ________
8: ________
9: ________
10:________
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
________
________
________
________
________
________
________
________
________
________
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
________
________
________
________
________
________
________
________
________
________
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
________
________
________
________
________
________
________
________
________
________
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
________
________
________
________
________
________
________
________
________
________
Field descriptions
Group Name - The Group Name field is an identifier name for the audio group.
Audio Source Location - The Audio Source Location field contains the list of VAL boards or
V VAL location designators for each audio source in the audio group.
Audio Groups
The Audio Groups screen is a display-only screen that lists the identifying group number,
name, and the number of sources of all audio groups in a system. This change is prompted by
the Locally sourced announcements and music feature.
Issue 1.1 June 2006
81
New and changed screens
To view the Audio Groups screen:
1. Type list audio-group. Press Enter.
The system displays the Audio Groups screen (Figure 8: Audio Groups screen on
page 82).
Figure 8: Audio Groups screen
list audio-group
AUDIO GROUPS
Group
Name
1
Relaxation Music
12
Forgive the wait
23
Best deals for today
At End of Member List
Number of Sources
2
20
30
Field descriptions
Group - The Group field displays the assigned number for the group.
Name - The Name field displays the assigned name for the group.
Number of Sources - The Number of Sources field displays the number of assigned audio or
music sources for the group.
IP Interfaces
The IP Interfaces screen, when you use the list command, is a display-only screen. The
screen lists all of the TN2302AP Media Processor and TN2602AP Media Resource 320 circuit
packs in a system. The screen also indicates whether a circuit pack is duplicated. This change
is prompted by the TN2602AP IP Media Resource 320 circuit pack.
Note:
Note:
For release 3.0, duplication is not yet available.
To view the IP Interfaces screen:
1. Type list ip-interface medpro.
The system displays the IP Interfaces screen (Figure 9: IP Interfaces screen on page 83).
82 What’s New in Avaya Communication Manager
Release 3.0 new screens
Figure 9: IP Interfaces screen
list ip-interface medpro
IP INTERFACES
ON Slot
-- ---y 01A04
y 01B10
y 01A13
y 64B09
y 64B10
y 01B09
y 01A11
y 26A05
y 01B11
y 26B02
y 26B03
y 26A02
y 26A06
y 64A05
y 64A10
Code Sfx
---- --TN2302
TN2302
TN2302
TN2302
TN2302
TN2302
TN2602
TN2302
TN2302
TN2302
TN2302
TN2302
TN2302
TN2302
TN2302
IP Address
--------------172.22.22.179
172.22.22.182
172.22.22.185
172.23.23.32
172.23.23.33
172.22.22.233
172.22.22.234
172.22.22.249
172.22.22.191
172.22.22.192
172.22.22.193
172.22.22.194
172.22.22.195
172.23.23.30
172.23.23.31
Subnet Mask
--------------255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
Gateway Address
--------------172.22.22.254
172.22.22.254
172.22.22.254
172.23.23.254
172.23.23.254
172.22.22.254
172.22.22.254
172.22.22.254
172.22.22.254
172.22.22.254
172.22.22.254
172.22.22.254
172.22.22.254
172.23.23.254
172.23.23.254
Net
Rgn
--1
1
1
3
3
1
1
2
1
2
2
2
2
3
3
VLAN Dup
---- --0
n
0
n
0
n
0
n
0
n
0
n
n
n
0
n
0
n
0
n
0
n
0
n
0
n
0
n
0
n
MOH Group
Use the new MOH Groups screen to administer music on hold groups. This change is
prompted by the Locally sourced announcements and music feature.
To view the MOH Groups screen:
1. Type add moh-analog-group n, where n is the music-on-hold group number. Press
Enter.
The system displays the MOH Groups screen (Figure 10: MOH Group screen on
page 84).
Issue 1.1 June 2006
83
New and changed screens
Figure 10: MOH Group screen
add moh-analog-group 1
Page 1 of 4
MOH GROUP 1
Group Name: Relaxation Music__
MOH SOURCE LOCATION
1: __01A0905
2: __019v401
3: ________
4: ________
5: ________
6: ________
7: ________
8: ________
9: ________
10: _______
11: _______
12: _______
13: _______
14: _______
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
________
________
________
________
________
________
________
________
________
________
________
________
________
________
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
________
________
________
________
________
________
________
________
________
________
________
_______
________
________
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
________
________
________
________
________
________
________
________
________
________
________
________
________
________
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
________
________
________
________
________
________
________
________
________
________
________
________
________
________
Field descriptions
Group Name - The Group Name field is an identifier name for the music-on-hold group.
Valid entries
Usage
1 to 27
alpha-numeric
characters
Type a free form identifier of the music-on-hold group.
MOH Source Location - The MOH Source Location field contains the list of VAL boards or
V VAL location designators for each audio source in the music-on-hold group.
Valid entries
Usage
1 to 5
alpha-numeric
characters
Type a valid VAL board or V VAL location designator
of an audio source.
84 What’s New in Avaya Communication Manager
Release 3.0 new screens
Music-on-Hold Groups
A new screen, the Music-On-Hold Groups screen, displays all the music-on-hold groups in a
system. This change is prompted by the Locally sourced announcements and music feature.
To view the Music-On-Hold Groups screen:
1. Type list moh-analog-group. Press Enter.
The system displays the Music-On-Hold Groups screen (Figure 11: Music-on-Hold
Groups screen on page 85).
Figure 11: Music-on-Hold Groups screen
list moh-analog-group
Page 1
MUSIC-ON-HOLD GROUPS
Group
8
10
11
Name
Elevator Music
Latin Renditions
Polka music
Number of Sources
5
20
30
At End of Member List
System Parameters Media Gateway Automatic Recovery Rule
A new screen, the System Parameters Media Gateway Automatic Recovery Rule screen,
defines the rules for automatically returning a fragmented network, where a number of H.248
Media Gateways are being serviced by one or more Local Survivable Processors (LSPs), to the
primary media server. This change is prompted by the Auto fallback to primary for H.248 media
gateways feature.
To view the System Parameters Media Gateway Automatic Recovery Rule screen:
1. Type change system-parameters mg-recovery-rule n., where n is the recovery
rule number. Press Enter.
The system displays the System Parameters Media Gateway Automatic Recovery Rule
screen.
Issue 1.1 June 2006
85
New and changed screens
Note:
Note:
The system displays a different time screen and warning message depending on
the option that you select for the Migrate H.248 MG to primary field. The
following four figures show the screen that appears for each option in the Migrate
H.248 MG to primary field:
- immediately (Figure 12: System Parameters Media Gateway Automatic Recovery
Rule screen on page 86).
- 0-active-calls (Figure 13: System Parameters Media Gateway Automatic
Recovery Rule screen on page 87).
- time-day-window (Figure 14: System Parameters Media Gateway Automatic
Recovery Rule screen on page 87).
- time-window-OR-0-active-calls (Figure 15: System Parameters Media Gateway
Automatic Recovery Rule screen on page 88).
Figure 12: System Parameters Media Gateway Automatic Recovery Rule screen
change system-parameters mg-recovery-rule 1
SYSTEM PARAMETERS MEDIA GATEWAY AUTOMATIC RECOVERY RULE
Recovery Rule Number: 1
Rule Name: Rule 1
Migrate H.248 MG to primary:
immediately
Minimum time of network stability: 3
WARNING: The MG shall be migrated at the first possible opportunity. The MG may be
migrated with a number of active calls. These calls shall have their talk paths
preserved, but no additional call processing of features shall be honored. The
user must hang up to regain access to all features.
Note: set ’Migrate H.248 MG to primary’ to Blank to disable rule.
86 What’s New in Avaya Communication Manager
Release 3.0 new screens
Figure 13: System Parameters Media Gateway Automatic Recovery Rule screen
change system-parameters mg-recovery-rule 1
SYSTEM PARAMETERS MEDIA GATEWAY AUTOMATIC RECOVERY RULE
Recovery Rule Number: 1
Rule Name: Rule 1
Migrate H.248 MG to primary:
0-active-calls
Minimum time of network stability: 3
WARNING: The MG shall only be migrated when there are no active calls.
Note: set ’Migrate H.248 MG to primary’ to Blank to disable rule.
Figure 14: System Parameters Media Gateway Automatic Recovery Rule screen
change system-parameters mg-recovery-rule 1
SYSTEM PARAMETERS MEDIA GATEWAY AUTOMATIC RECOVERY RULE
Recovery Rule Number: 1
Rule Name: Rule 1
Migrate H.248 MG to primary:
time-day-window
Minimum time of network stability: 3
WARNING: The MG may be migrated with a number of active calls. These calls shall
have their talk paths preserved, but no additional call processing of features
shall be honored. The user must hang up in order to regain access to all features.
Valid registrations shall only be accepted during these intervals.
Time of Day
Day of Week
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
00
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
12
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
23
__
__
__
__
__
__
__
Note: set ’Migrate H.248 MG to primary’ to Blank to disable rule.
Issue 1.1 June 2006
87
New and changed screens
Figure 15: System Parameters Media Gateway Automatic Recovery Rule screen
change system-parameters mg-recovery-rule 1
SYSTEM PARAMETERS MEDIA GATEWAY AUTOMATIC RECOVERY RULE
Recovery Rule Number: 1
Rule Name: Rule 1
Migrate H.248 MG to primary:
time-window-OR-0-active-calls
Minimum time of network stability: 3
WARNING: The MG shall be migrated ANY time when there are no active calls OR the
MG may be migrated with a number of active calls when a registration is received
during the specified intervals. These calls shall have their talk paths preserved,
but no additional call processing of features shall be honored.
Time of Day
Day of Week
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
00
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
12
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
23
__
__
__
__
__
__
__
Note: set ’Migrate H.248 MG to primary’ to Blank to disable rule.
Migrate H.248 MG to primary
Use the Migrate H.248 MG to primary field to indicate the auto-fallback preferences. For each
option, the system displays a unique warning message and screen.
Valid entries
Usage
immediately
This is the default value. The first media gateway
registration that comes from the media gateway is
honored, regardless of call count or time of day.
0-active calls
The first media gateway registration reporting “0 active
calls” is honored.
88 What’s New in Avaya Communication Manager
Release 3.0 new screens
Valid entries
Usage
time-day-window
A valid registration message received during any part
of this interval is honored. When this option is selected
the system displays a grid for defining desired hours/
days for the time window.
time-window-OR-0-active-calls
A valid registration is accepted anytime, when a 0
active call count is reported OR if a valid registration
with any call count is received during the specified
time/day intervals. When this option is selected the
system displays a grid for defining desired hours/days
for the time window.
Note: You must specify an x or X for each hour during
which you want to permit the return migration. If you do
not want to permit a given hour, then they leave it
blank. This method helps with overlapping time issues
between days of the week. You can specify as many
intervals as you wish.
Minimum time of network stability
Use this field to administer the time interval for stability in the H.248 link before auto-fallback is
attempted.
Valid entries
Usage
3 to 15
Enter the number of minutes before auto-fallback is attempted. The default
value is 3.
Recovery Rule Number
Valid entries
Usage
1 to the server maximum
Enter the number of the recovery rule.
Rule Name
Use this field for an optional text name for the rule, as an aid in associating rules with media
gateways.
Issue 1.1 June 2006
89
New and changed screens
TTI Service IP Stations
A new screen, TTI Service IP Stations, lists IP telephones that are in TTI service. The
Registered IP Stations screen does not list telephones that are in TTI service. An IP telephone
that is in TTI service also does not appear in the Unregistered IP Telephones report. This
change is prompted by the Emergency calls from unnamed IP endpoints feature.
To view the TTI Service IP Stations screen:
1. Type list tti-ip-stations. Press Enter.
The system displays the TTI Service IP Stations screen (Figure 16: TTI Service IP
Stations screen on page 90).
Figure 16: TTI Service IP Stations screen
list tti-ip-stations
Page 1
TTI SERVICE IP STATIONS
Station
IP Address
135.9.159.130
Product
ID
IP_Phone
Prod
Rel
2.200
Net
Rgn
1
Gatekeeper
IP Address
135.9.159.128
Port
S00074
All fields are display only. The system sorts the information on the screen by the Station IP
Address field.
Virtual MAC Addresses
The Virtual MAC Addresses screen is a read-only display of virtual Media Access Control
(MAC) addresses that are shared by duplicated TN2602AP Media Resource 320 circuit packs.
The duplicated TN2602AP Media Resource 320 circuit packs must be in an S8500 or
S8700-series Media Server system. This change is prompted by the TN2602AP IP Media
Resource 320 circuit pack.
To view the Virtual MAC Addresses screen:
1. Type display virtual-mac-address n, where n is the MAC address table number.
The system displays the Virtual MAC Addresses screen (Figure 17: Virtual MAC
Addresses screen on page 91).
90 What’s New in Avaya Communication Manager
Release 3.1.X changed screens
Figure 17: Virtual MAC Addresses screen
display virtual-mac-address 1
Page 1 of 2
VIRTUAL MAC ADDRESSES - TABLE: 1
MAC Address
Used
MAC Address
Used
00:04:0d:4a:53:c0
y
00:04:0d:4a:53:cf
n
00:04:0d:4a:53:c1
n
00:04:0d:4a:53:d0
n
00:04:0d:4a:53:c2
n
00:04:0d:4a:53:d1
n
00:04:0d:4a:53:c3
n
00:04:0d:4a:53:d2
n
00:04:0d:4a:53:c4
n
00:04:0d:4a:53:d3
n
00:04:0d:4a:53:c5
n
00:04:0d:4a:53:d4
n
00:04:0d:4a:53:c6
n
00:04:0d:4a:53:d5
n
MAC Address
Valid entries
Usage
Obtained from list
Virtual MAC address shared by duplicated TN2602AP
circuit packs.
Used
The system populates the Used field, and indicates whether a virtual MAC address has been
assigned in the system.
Valid entries
Usage
y/n
If y, the associated virtual MAC address has been
assigned in the system.
Release 3.1.X changed screens
Avaya Communication Manager release 3.1.X, which includes releases 3.1.1 and 3.1.2,
includes the following changed screens. For a more complete explanation of the screens and
their function, see the Administrator Guide for Avaya Communication Manager, 03-300509.
IP-Options System Parameters
Changes are made to the IP-Options System Parameters screen, prompted by the Manual
Local Survivable Processor takeover feature.
Issue 1.1 June 2006
91
New and changed screens
To view the IP-Options System Parameters screen:
1. Type change system-parameters ip-options. Press Enter.
The system displays the IP-Options System Parameters screen.
2. Click Next until you see the Detection And Alarming Of Hyperactive Media Gateway
Registrations section (Figure 18: IP-Options System Parameters screen on page 92).
Figure 18: IP-Options System Parameters screen
change system-parameters ip-options
Page 2 of x
IP-OPTIONS SYSTEM PARAMETERS
Always use G.711 (30ms, no SS) for intra-switch Music-On-Hold?
IP DTMF TRANSMISSION MODE
Intra-System IP DTMF Transmission Mode: in-band-g711
Inter-System IP DTMF: See Signaling Group Forms
DETECTION AND ALARMINIG OF HYPERACTIVE MEDIA GATEWAY REGISTRATIONS
Feature Enabled?
Parameters for Media Gateway Alarms:
Hyperactive Registration Window (minutes):
Number of Registrations within the Window:
Parameters for Network Region Reigistration (NR-REG) Alarms:
% of Gateways in Network Region with Hyperacive Registration Alarms:
Feature Enabled
Use this field to enable or disable the hyperactive media gateway registration feature. The default
value is n.
Valid entries
Usage
y/n
Parameters for Media Gateway Alarms:
Hyperactive Registration Window (minutes)
This field appears when the Feature Enabled field is y.
Valid entries
Usage
1 to 15
Time in minutes for checking hyperactive media gateway registrations.
The default value is 4 minutes.
92 What’s New in Avaya Communication Manager
Release 3.1.X changed screens
Parameters for Media Gateway Alarms:
Number of Registrations within the Window
This field appears when the Feature Enabled field is y.
Valid entries
Usage
1 to 19
Number of registrations that occur within the hyperactivity window for
generating a Gateway alarm. The default value is 3.
Parameters for Network Region Registration (NR-REG) Alarms:
% of Gateways in Network Region with Hyperactive Registration Alarms
This field appears when the Feature Enabled field is y.
Valid entries
Usage
1 to 99
Percent of gateways within an ip-network region that should be alarmed
before an IP-registration alarm is generated. The default value is 80%.
Feature-Related System Parameters
The Call Center Miscellaneous section of the Feature-Related System Parameters screen
now offers a new field, Allow Ringer-off With Auto-Answer. The default value for this field is
No.
To view the Feature-Related System Parameters screen:
1. Type change system-parameters features. Press Enter.
The system displays the Feature-Related System Parameters screen.
2. Click Next until you see the Call Center Miscellaneous section
(Figure 19: Feature-Related System Parameters screen on page 93).
Figure 19: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
Page 13 of X
CALL CENTER MISCELLANEOUS
Clear Callr-info: next-call
Allow Ringer-off with Auto-Answer? n
Issue 1.1 June 2006
93
New and changed screens
Allow Ringer-off With Auto-Answer
Valid entries
Usage
y/n
If n, calls on an endpoint set to auto-answer continue to
ring even when the Ringer Off field is set to Yes.
If y, calls do not ring unless the Ringer Off field is set to
No.
Trunk Group
When you set the Group Type field to sip and the SCCAN field to No, the system displays a
new field, Preferred Minimum Session Refresh Interval (Sec).
To view the Trunk Group screen:
1. Type change trunk-group n, where n is the trunk group that you want to change. Press
Enter.
The system displays the Trunk Group screen (Figure 20: Trunk Group screen on
page 94).
Figure 20: Trunk Group screen
change trunk-group 5
Page 1 of X
TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access:
Queue Length:
Service Type:
5
Group Type:
__________________________ COR:
two-way
Outgoing Display?
n
0
__________________
Auth Code?
sip
___
n
CDR Reports? y
TN: ___
TAC: ____
Night Service: ________
n
Signaling Group: ___
Number of Members: ___
2. Set the Group Type field to sip.
Click Next until you see the Trunk Parameters section (Figure 21: Trunk Group screen on
page 95).
94 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 21: Trunk Group screen
change trunk-group 5
Group Type: sip
Page 2 of X
TRUNK PARAMETERS
Unicode Name? y
Redirect On OPTIM Failure: 5000
SCCAN? n
Digital Loss Group: 18
Preferred Minimum Session Refresh Interval (Sec): 120
3. Set the SCCAN field to n.
The system displays the Preferred Minimum Session Refresh Interval (Sec) field.
Preferred Minimum Session Refresh Interval (Sec)
Valid entries
Usage
90 to 1800
seconds
The value is the shortest refresh interval used for
sessions in SIP-based applications. Set the value that is
appropriate to your SIP-based applications and SIP
trunk connectivity. The default value is 120 seconds.
Release 3.1 changed screens
Avaya Communication Manager, release 3.1, includes the following changed screens. For a
more complete explanation of the screens and their function, see the Administrator Guide for
Avaya Communication Manager, 03-300509.
Class of Restriction
The Class of Restriction screens changed. You can now assign up to 995 CORs. This change
is prompted by the Increased Classes of Restriction feature.
Beginning with page #3 of the Class of Restriction screens, you can assign Classes of
Restriction 0-99. Additional pages are added to assign CORs 100-199, 200-299, and so on.
Beginning with page #13, you can assign Service Observing permissions on the CORs. The
following screens show the changes.
Issue 1.1 June 2006
95
New and changed screens
To view the Class of Restriction screen:
1. Type change cor n, where n is the Class of Restriction that you want to change. The
value n can be a number between 0 and 995. Press Enter.
The system displays the Class of Restriction screen.
2. Click Next until you see the Calling Permission section (Figure 22: Class of Restriction
screen on page 96).
Figure 22: Class of Restriction screen
change cor 5
Page 3 of 22
CLASS OF RESTRICTION
CALLING PERMISSION (Enter "y" to grant permission to call specified COR)
0?
1?
2?
3?
4?
5?
6?
7?
8?
9?
10?
11?
12?
13?
14?
n
n
n
n
n
y
n
n
n
n
n
n
n
n
n
15?
16?
17?
18?
19?
20?
21?
22?
23?
24?
25?
26?
27?
28?
29?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
30?
31?
32?
33?
34?
35?
36?
37?
38?
39?
40?
41?
42?
43?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
44?
45?
46?
47?
48?
49?
50?
51?
52?
53?
54?
55?
56?
57?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
58?
59?
60?
61?
62?
63?
64?
65?
66?
67?
68?
69?
70?
71?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
72?
73?
74?
75?
76?
77?
78?
78?
80?
81?
82?
83?
84?
85?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
86?
87?
88?
89?
90?
91?
92?
93?
94?
95?
96?
97?
98?
99?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
3. To assign Service Observing permissions to a COR, click Next until you see the Service
Observing Permission section (Figure 23: Class of Restriction screen on page 97).
96 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 23: Class of Restriction screen
change cor 5
Page 13 of 22
CLASS OF RESTRICTION
SERVICE OBSERVING PERMISSIONS
(Enter "y" to grant permission to service observe the specified COR)
0?
1?
2?
3?
4?
5?
6?
7?
8?
9?
10?
11?
12?
13?
14?
n
n
n
n
n
y
n
n
n
n
n
n
n
n
n
15?
16?
17?
18?
19?
20?
21?
22?
23?
24?
25?
26?
27?
28?
29?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
30?
31?
32?
33?
34?
35?
36?
37?
38?
39?
40?
41?
42?
43?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
44?
45?
46?
47?
48?
49?
50?
51?
52?
53?
54?
55?
56?
57?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
58?
59?
60?
61?
62?
63?
64?
65?
66?
67?
68?
69?
70?
71?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
72?
73?
74?
75?
76?
77?
78?
78?
80?
81?
82?
83?
84?
85?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
86?
87?
88?
89?
90?
91?
92?
93?
94?
95?
96?
97?
98?
99?
n
n
n
n
n
n
n
n
n
n
n
n
n
n
Class of Service
The Class of Service screen did not change with Communication Manager release 3.1.
However, the Enterprise Mobility User feature prompted a change to the Personal Station
Access (PSA) field.
Personal Station Access (PSA) - the Personal Station Access (PSA) field allows users to
associate a telephone to their extension with their programmed services using a feature access
code (FAC). This field must be set to n for virtual telephones. This field must be set to y at a
user's home station in order for that user to use the Enterprise Mobility User (EMU) feature at
other stations.
Issue 1.1 June 2006
97
New and changed screens
Console Parameters
A new field, Busy Indicator for Call Parked on Analog Station Without Hardware?, is added
to the Console Parameters screen.
To view the Console Parameters screen:
1. Type change console-parameters. Press Enter.
The system displays the Console Parameters screen.
2. Click Next until you see the Busy Indicator for Call Parked on Analog Station Without
Hardware? field (Figure 24: Console Parameters screen on page 98).
Figure 24: Console Parameters screen
change console-parameters
Page
2 of x
CONSOLE PARAMETERS
TIMING
Time Reminder on Hold (sec): 10
Time in Queue Warning (sec):
Return Call Timeout (sec): 10
INCOMING CALL REMINDERS
No Answer Timeout (sec): 20
Alerting (sec): 40
Secondary Alert on Held Reminder Calls? y
ABBREVIATED DIALING
List1: group
1
List2:
List3:
SAC Notification? n
COMMON SHARED EXTENSIONS
Starting Extension:
Count:
Busy Indicator for Call Parked on Analog Station Without Hardware?
Field descriptions
Busy Indicator for Call Parked on Analog Station Without Hardware? Valid entries
Usage
y/n
Enter y to indicate that the Busy Indicator lamp will light for incoming calls
parked on AWOH stations. Default is n.
98 What’s New in Avaya Communication Manager
Release 3.1 changed screens
CTI Link
Change 1
The field description for the CTI Link field is changed on the CTI Link screen. A new field,
Two-Digit Aux Work Reason Codes?, is also added to the CTI Link screen. These changes
are prompted by the ASAI support for Aux Work reason codes feature.
Note:
Note:
The CTI Link screen is available only if, on the Optional Features screen, either
the ASAI Link Core Capabilities and/or the Computer Telephony Adjunct
Links field is y.
To view the CTI Link screen:
1. Type add cti-link next. Press Enter.
The system displays the CTI Link screen (Figure 26: CTI Link screen on page 100).
Figure 25: CTI Link screen
add cti-link next
Page 1 of x
CTI LINK
CTI Link:
Extension:
Type:
Port:
Name:
1
40001
ASAI
1C0501
ASAI CTI Link 1
COR: 1
BRI OPTIONS
XID? y
MIM Support? n
Fixed TEI? n
CRV Length: 2
Field descriptions
CTI Link - This field is display-only, and indicates the CTI link number.
Valid entries
Usage
1 to system
max
Avaya Communication Manager on a DEFINITY Server CSI, DEFINITY G3i,
S8300 Media Server, S8700 Series Multi-Connect
Issue 1.1 June 2006
99
New and changed screens
2. Click Next until you see the Two-Digit Aux Work Reason Codes? field (Figure 26: CTI
Link screen on page 100).
Figure 26: CTI Link screen
add cti-link next
Page 2 of x
CTI LINK
FEATURE OPTIONS
Event Minimization?
Special Character for Restricted Number?
Send Disconnect Event for Bridged Apppearance?
Two-Digit Aux Work Reason Codes?
Block CMS Move Agent Events?
Field descriptions
Two-Digit Aux Work Reason Codes? Valid entries
Usage
y/n
Enter y to enable sending two-digit Reason Codes over the ASAI link. All
messages that include Aux Work Reason Codes will allow a codes of 1 to
99. This field can only be set to y when Two-Digit Aux Work Reason
Codes? on the System-Parameters Features screen is set to y. Default
is n.
Change 2
A new field, Block CMS Move Agent Events?, is added to the CTI Link screen. This change is
prompted by the Block CMS Move Agent events feature.
Field descriptions
Block CMS Move Agent Events? Valid entries
Usage
y/n
When this option is set to y, if CMS sends an agent-move-while-staffed
message (MVAGSFD8), ASAI does not send the associated agent Logout
Event Report (C_Logout), Login Event Report (C_login) and Agent Work
Mode Change event report messages to report the changes involved with
the move of agents while staffed. Default is n.
100 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Enterprise Survivable Server Information
Beginning with Communication Manager release 3.1, node names are used in place of IP
addresses for ESS servers on pages 1 through 5 of the Enterprise Survivable Server
Information screen. Other field values are increased.
To view the Enterprise Survivable Server Information screen:
1. Type change system-parameters ess. Press Enter.
The system displays the Enterprise Survivable Server Information screen
(Figure 27: Enterprise Survivable Server Information screen on page 101).
Figure 27: Enterprise Survivable Server Information screen
change system-parameters ess
Page 1 of x
ENTERPRISE SURVIVABLE SERVER INFORMATION
Cl
Plat
Server A
Server B
Pri Com Sys Loc Loc
ID
Type
ID
Node Name
ID
Node Name
Scr
Prf Prf Only
__________________________________________________________________________
MAIN SERVERS
___ _______ ___ _______________ ___ _______________ ___ ___ ___
___
___
___
___
___
___
___
_______
_______
_______
_______
_______
_______
_______
___
___
___
___
___
___
___
ENTERPRISE SURVIVABLE SERVERS
_______________ ___ _______________
_______________ ___ _______________
_______________ ___ _______________
_______________ ___ _______________
_______________ ___ _______________
_______________ ___ _______________
_______________ ___ _______________
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
___
Field descriptions
Server A ID - The valid entries are increased to 256.
Valid entries
Usage
1 to 256 or blank
Enter the Server ID (SVID) of the S8400 or S8500 Media Server, or the
SVID of the A-side of the S8700 series media server. If this field is blank,
all other entries on the line display default values.
Issue 1.1 June 2006
101
New and changed screens
Server A Node Name - This field is changed from IP Address to Node Name.
Valid entries
Usage
Valid node name
administered on
the IP Node
Names screen.
Enter the node name for the S8400 or S8500 Media Server, or the A-side
of the S8700-series Media Server.
Server B ID - The valid entries are increased to 256.
Valid entries
Usage
1 to 256 or blank
S8700-series Media Servers only. Enter the Server ID (SVID) of the B-side
of the S8700-series Media Server.
Server B Node Name - This field is changed from IP Address to Node Name.
Valid entries
Usage
Valid node name
administered on
the IP Node
Names screen.
S8700-series Media Servers only. Enter the node name for the B-side
S8700-series Media Server.
Feature Access Code (FAC)
Note:
Note:
There are numerous changes to the Feature Access Code (FAC) screen for
Communication Manager release 3.1. The changes are all listed here, by page.
The information also mentions what feature prompted the change.
To view the Feature Access Code (FAC) screen:
1. Type change feature-access-codes. Press Enter.
The system displays the Feature Access Code (FAC) screen.
2. Click Next until you see the Enterprise Mobility User Activation field (Figure 28: Feature
Access Code (FAC) screen on page 103).
102 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 28: Feature Access Code (FAC) screen
change feature-access-codes
Page
2 of
FEATURE ACCESS CODE (FAC)
Data Origination Access Code:
Data Privacy Access Code:
Directed Call Pickup Access Code:
Emergency Access to Attendant Access Code: *11
EC500 Self Administration Access Code:
Enhanced EC500 Activation: *81
Deactivation:#81
Enterprise Mobility User Activation: *55
Deactivation:#56
Extended Call Fwd Activate Busy D/A: *23 All: *24
Deactivation:#23
Extended Group Call Pickup Access Code:
Facility Test Calls Access Code:
Flash Access Code: *88
Group Control Restrict Activation: *15
Deactivation: #15
Hunt Group Busy Activation: *82
Deactivation: #83
ISDN Access Code:
Last Number Dialed Access Code: *54
Leave Word Calling Message Retrieval Lock: *48
Leave Word Calling Message Retrieval Unlock: #45
Leave Word Calling Send A Message: *60
Leave Word Calling Cancel A Message: #60
Malicious Call Trace Activation:
Deactivation:
Meet-me Conference Access Code Change:
x
Page 2
Change 1
Two new fields, Enterprise Mobility User Activation and Enterprise Mobility User
Deactivation, are added to the Feature Access Code (FAC) screen. These changes are
prompted by the Enterprise Mobility User feature.
Field descriptions
Enterprise Mobility User Activation - Type a feature access code number to allow users to
activate the Enterprise Mobility User feature, associating the features and permissions of their
primary telephone to a telephone of the same type anywhere within the customer’s enterprise.
Enterprise Mobility User Deactivation - Type a feature access code number to allow users to
deactivate the Enterprise Mobility User feature.
3. Click Next until you see the Service Observing No-Talk Access Code field
(Figure 28: Feature Access Code (FAC) screen on page 103).
Issue 1.1 June 2006
103
New and changed screens
Figure 29: Feature Access Code (FAC) screen
change feature-access-codes
FEATURE ACCESS CODE (FAC)
Page 5 of x
Automatic Call Distribution Features
After Call Work
Assist
Auto-In
Aux Work
Login
Logout
Manual-In
Service Observing Listen Only
Service Observing Listen/Talk
Service Observing No Talk
Add Agent Skill
Remove Agent Skill
Remote Logout of Agent
Access
Access
Access
Access
Access
Access
Access
Access
Access
Access
Access
Access
Access
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
Code:
___
___
___
___
___
___
___
___
___
___
___
___
___
Page 5
Change 2
A new field, Service Observing No-Talk Access Code, is added to the Feature Access Code
(FAC) screen. This change is prompted by the Listen-only FAC for service observing feature.
Field descriptions
Service Observing No-Talk Access Code - This field appears only if Expert Agent Selection
(EAS) Enabled is set to y on the Feature-Related System-Parameters screen. Enter the code
that must be dialed to allow a station with Service Observing permission (COR) to listen only
without reserving a 2nd timeslot for potential toggle to talk and listen mode. When this FAC is
used for activation, the observing connection is listen only. Any attempt to toggle to talk via the
Service Observing (SO) feature button is denied.
Feature-Related System Parameters
Note:
Note:
There are numerous changes to the Feature-Related System Parameters
screen for Communication Manager release 3.1. The changes are all listed here,
by page. The information also mentions what feature prompted the change.
104 What’s New in Avaya Communication Manager
Release 3.1 changed screens
To view the Feature-Related System Parameters screen:
1. Type change system-parameters features. Press Enter.
The system displays the Feature-Related System Parameters screen.
2. Click Next until you see the Call Processing Overload Mitigation section
(Figure 30: Feature-Related System Parameters screen on page 105).
Figure 30: Feature-Related System Parameters screen
change system-parameters features
Page 3 of 17
FEATURE-RELATED SYSTEM PARAMETERS
TTI/PSA PARAMETERS
WARNING! SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE
Terminal Translation Initialization (TTI) Enabled?
TTI State: ________
TTI Security Code:
Record CTA/PSA/TTI Transactions in History Log?
Enhanced PSA Location/Display Information Enabled?
Default COR for Dissociated Sets:
CPN, ANI for Dissociated Sets:
Customer Telephone Activation (CTA) Enabled?
__
_______
__
__
___
__
CALL PROCESSING OVERLOAD MITIGATION
Restrict Calls: ____________
Page 3
Change 1
The Call Processing Overload Mitigation section, Restrict Calls field, is moved from the
Maintenance-Related System Parameters screen to the Feature-Related System
Parameters screen.
Since changes to this field control how the system reacts to overload, and since the system
currently denies all intercom and outband calls on overload, changes to this field only improves
the way in which the system reacts to overload conditions.
When the Restrict Calls field was part of the Maintenance-Related System Parameters
screen, a user could not change the field unless the user had maintenance system permissions
(MSP). Without MSP, the user had to call services to have them change the field. By moving the
Restrict Calls field to the Feature-Related System Parameters screen, users with super-user
permissions can now change this field without having to call services for help.
Issue 1.1 June 2006
105
New and changed screens
Field descriptions
Restrict Calls - This field indicates the type of calls to block first during overload traffic
conditions on the system.
Valid entries
Usage
stations-first
Deny new traffic generated by internal stations, allowing inbound calls
only (works best in call center environments).
all-trunk-first
Deny all out-bound calls to trunks, tie-lines and stations, and all
station-originated calls.
public-trunks-first
Deny all in-bound calls from trunks and tie-lines.
3. Click Next until you see the AUDIX One Step Recording section
(Figure 31: Feature-Related System Parameters screen on page 106).
Figure 31: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
page 7 of x
CONFERENCE/TRANSFER
Abort Transfer?
Transfer Upon Hang-Up?
Abort Conference Upon Hang-Up?
No Hold Conference Timeout:
ANALOG BUSY AUTO CALLBACK
Without Flash?
No Dial Tone Conferencing?
Select Line Appearance Conferencing?
Unhold?
Maximum Ports per Expanded Meet-me Conf:
Announcement:
Voice Mail Hunt Group Ext:
AUDIX ONE-STEP RECORDING
Recording Delay Timer (msec):
Apply Ready Indication Tone To Which Parties In The Call?
Interval For Applying Periodic Alerting Tone (seconds):
106 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Page 7
Change 2
Two new fields, Apply Ready Indication Tone to Which Parties in the Call? and Interval for
Applying Periodic Alerting Tone (seconds), are added to the Feature-Related System
Parameters screen. These changes are prompted by enhancements to Avaya Modular
Messaging.
Field descriptions
Apply Ready Indication Tone to Which Parties in the Call? - This field is for administering
who hears the AUDIX recording ready tone.
Valid entries
Usage
all, initiator, or
none
Enter a value for which party or parties on the call should hear the
ready-to-record indication tone. The default is all. This field cannot be
left blank.
Interval for Applying Periodic Alerting Tone (seconds) - This field appears only if the Apply
Ready Indication Tone To Which Parties In The Call? field is set to all.
Valid entries
Usage
0 to 60
Enter a number from zero to 60 for the number of seconds desired
between alerting tones, where zero disables the tone. The default value
is a 15 second interval.
4. Click Next until you see the Caller ID on Call Waiting Parameters section
(Figure 32: Feature-Related System Parameters screen on page 108).
Issue 1.1 June 2006
107
New and changed screens
Figure 32: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
page 9 of x
CPN/ANI/ICLID PARAMETERS
CPN/ANI/ICLID Replacement for Restricted Calls:
CPN/ANI/ICLID Replacement for Unavailable Calls:
INTERNATIONAL CALL ROUTING PARAMETERS
Local Country Code: 1
International Access Code: 011
ENBLOC DIALING PARAMETERS
Enable Enbloc Dialing without ARS FAC?
CALLER ID ON CALL WAITING PARAMETERS
Caller ID on Call Waiting Delay Timer (msec): 200
Page 9
Change 3
A new section heading, Caller ID on Call Waiting Parameters, and a new field, Caller ID on
Call Waiting Delay Timer (msec), are added to the Feature-Related System Parameters
screen. These changes are prompted by Support caller ID on call waiting for MM711 and
MM714.
Field descriptions
Caller ID on Call Waiting Delay Timer (msec) Valid entries
Usage
5 to 1275, in
increments of 5
Enter the desired delay in 5-millisecond intervals. Default is 200.
5. Click Next until you see the Vectoring section (Figure 33: Feature-Related System
Parameters screen on page 109).
108 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 33: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
CALL CENTER SYSTEM PARAMETERS
EAS
Expert Agent Selection (EAS) Enabled? n
Minimum Agent-LoginID Password Length:
Direct Agent Announcement Extension: ________
Message Waiting Lamp Indicates Status For: station
page 11 of x
Delay: ___
VECTORING
Converse First Data Delay:
Converse Signaling Tone (msec):
Prompting Timeout (secs):
Interflow-qpos EWT Threshold:
Reverse Star/Pound Digit For Collect Step?
Available Agent Adjustments for BSR?
Selection on BSR Ties?
0
100
10
2
n
_
SERVICE OBSERVING
Service Observing: Warning Tone? n
Service Observing Allowed with Exclusion? n
Second Data Delay: 2
Pause (msec): 70_
or Conference Tone?
Page 11
Change 4
A new field, Selection on BSR Ties?, is added to the Feature-Related System Parameters
screen.
Field descriptions
Selection on BSR Ties? - This field appears only when the Vectoring (Best Service Routing)
field on the Optional Features screen is y.
Valid entries
Usage
1st-found
BSR uses the first selection for routing. This is the default.
alternate
Allows alternating the BSR selection algorithm when a tie in EWT or
available agent criteria occurs. Every other time a tie occurs for calls from
the same active VDN, the selection from the consider step with the tie is
used instead of the first selected split/skill or location to send the call. This
helps balance the routing over the considered local splits/skills and remote
locations when cost of routing remotely is not a concern.
Issue 1.1 June 2006
109
New and changed screens
6. Click Next until you see the Call Center Miscellaneous section
(Figure 34: Feature-Related System Parameters screen on page 110).
Figure 34: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
CALL CENTER MISCELLANEOUS
Clear Callr-info:
Allow Ringer-off with Auto-Answer?
page 13 of 17
Page 13
Change 5
A new page and two new fields are added to the Feature-Related System Parameters screen.
Field descriptions
Clear Callr-info - Use this field to specify when collected digits from a previous caller is to be
removed from the agent/station display.
Valid entries
Usage
leave-ACW
Leaves the display up while the agent is in ACW (After-call work) mode.
next-call
Clears the display when the next call is received. This is the default.
on-call-release
Clears the display on the 2nd line of a two-line display as soon as the call
is released, either because of receiving call disconnect or the agent/station
user presses the release button.
110 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Allow Ringer-off with Auto-Answer - Use this field to prevent ringing on EAS auto-answer
calls.
Valid entries
Usage
y/n
Enter y to allow a user to use the ringer-off feature button to prevent
ringing on EAS auto-answer calls.
7. Click Next until you see the IP Parameters section (Figure 35: Feature-Related System
Parameters screen on page 111).
Figure 35: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
Page 16 of x
AUTOMATIC EXCLUSION PARAMETERS
Automatic Exclusion by COS?
Automatic Exclusion Coverage/Hold?
Automatic Exclusion with Whisper Page?
Recall Rotary Digit:
Password to Change COR by FAC:
Duration of Call Timer Display (seconds):
y
y
y
2
*
3
WIRELESS PARAMETERS
Radio Controllers with Download Server Permission (enter board location)
1.
2.
3.
4.
5.
IP PARAMETERS
Direct IP-IP Audio Connections? n
IP Audio Hairpinning? n
RUSSIAN MULTI-FREQUENCY PACKET SIGNALING
Re-try?
T2 (Backward Signal) Activation Timer (secs):
Issue 1.1 June 2006
111
New and changed screens
Page 16
Change 6
The IP Audio Hairpinning? field on the Feature-Related System Parameters screen now
defaults to n.
Note:
Note:
In addition to the Feature-Related System Parameters screen, the IP Audio
Hairpinning? field now defaults to n on the following additional screens:
- Attendant Console
- IP Network Region
- Signaling Group
- Station
Group Paging Using Speakerphone
A new field, TN, is added to the Group Paging Using Speakerphone screen. This new field
allows the system administrator to assign group paging at the tenant partition level, instead of to
an entire campus.
To view the Group Paging Using Speakerphone screen:
1. Type change group-paging n, where n is the number of the paging group. Press Enter.
The system displays the Group Paging Using Speakerphone screen (Figure 36: Group
Paging Using Speakerphone screen on page 113).
112 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 36: Group Paging Using Speakerphone screen
change group-paging 1
Page 1
GROUP PAGING USING SPEAKERPHONE
Group Number: 1
Group Extension:
Group Name:
COR: 1
GROUP MEMBER ASSIGNMENTS
TN: 1
Ext
Name (first 26 characters)
Ext
Name (first 26 characters)
1:
17:
2:
18:
3:
19:
4:
20:
5:
21:
6:
22:
7:
23:
8:
24:
9:
25:
10:
26:
11:
27:
12:
28:
13:
29:
14:
30:
15:
31:
16:
32:
Field descriptions
TN - The TN field identifies the number of a tenant partition.
Hunt Group
A new field, Provide Ringback?, is added to the Hunt Group screen.
To view the Hunt Group screen:
1. Type change hunt-group n, where n is the number of the hunt group. Press Enter.
The system displays the Hunt Group screen.
2. Click Next until you see the Provide Ringback? field (Figure 37: Hunt Group screen on
page 114).
Issue 1.1 June 2006
113
New and changed screens
Figure 37: Hunt Group screen
change hunt-group 3
Page 2 of X
HUNT GROUP
Message Center: ________
Voice Mail Number: _________________
Routing Digits (e.g. AAR/ARS Access Code): ____
Send Reroute Request? y
Provide Ringback? n
AUDIX Extension: ________
Message Center AUDIX Name: ______
Primary? _
Calling Party Number to INTUITY AUDIX? _
LWC Reception: _______
AUDIX Name: _______
Messaging Server Name: _______
First Announcement Extension: 1234 ___ Delay (sec): 20
Second Announcement Extension: ________ Delay (sec): __ Recurring? _
Field descriptions
Provide Ringback? - This field appears only if Message Center on the Hunt Group screen is
fp-mwi or qsig-mwi. Use this field if you are using an SBS trunk for the QSIG MWI hunt group.
If set to y, a call covering to the message center provides ringback to the caller during the
coverage interval.
Valid entries
Usage
y/n
When set to y, ringback is provided to the calling party until a Connect is
received for the call to the Messaging system. Ringback is discontinued
upon receipt of the Connect indication. Default is n.
IP Interfaces
Change 1
Six new fields are added to the IP Interfaces screen, prompted by the Processor Ethernet
feature. The six new fields are:
●
Allow H.323 Endpoints?
●
Allow H.248 Endpoints?
●
Gatekeeper Priority
●
Target socket load
114 What’s New in Avaya Communication Manager
Release 3.1 changed screens
●
Target socket load and Warning level
●
Link
To view the IP Interfaces screen:
1. Type change ip-interface procr.
The system displays the IP Interfaces screen for Processor Ethernet (Figure 38: IP
Interfaces screen on page 115).
Figure 38: IP Interfaces screen
change ip-interface procr
Page 1 of x
IP INTERFACES
Type: PROCR
IP Address: 172.28.4.1
Subnet Mask: 255.255.255.0
Enable Ethernet Port? y
Network Region: 20
Allow H.323 Endpoints?
Allow H.248 Gateways?
Gatekeeper Priority?
Target socket load:
Field descriptions
Allow H.323 Endpoints? - This field controls whether or not IP endpoints can register on the
interface.
Valid entries
Usage
y/n
On a simplex main server, enter y to allow H.323 endpoint connectivity to
the Processor Ethernet (PE) interface. Enter n if you do not want H.323
endpoint connectivity to the PE interface.
Note: For an Enterprise Survivable Server (ESS), this field is display -only
and is set to n. H.323 endpoint connectivity using the PE interface on an
ESS server is not supported. For a Local Survivable Processor (LSP), this
field is display-only and is set to y.
Issue 1.1 June 2006
115
New and changed screens
Allow H.248 Endpoints? - This field controls whether or not H.248 media gateways (G7000,
G350, G250) can register on the interface.
Valid entries
Usage
y/n
On a simplex main server, enter y to allow H.248 endpoint connectivity to
the PE interface. Enter n if you do not want H.248 endpoint connectivity to
the PE interface.
Note: For an Enterprise Survivable Server (ESS), this field is display-only
and is set to n. H.248 endpoint connectivity using the PE interface on an
ESS server is not supported. For a Local Survivable Processor (LSP), this
field is display-only and is set to y.
Gatekeeper Priority - This field appears only if the Allow H.323 Endpoints is y, and the
Communication Manager server is a main server or an LSP. This field does not display on an
ESS server. This field allows a priority to be set on the interface. This affects where the interface
appears on the gatekeeper list.
Valid entries
Usage
1 to 9
Enter the desired priority number. The value in this field is used on the
alternate gatekeeper list. The lower the number, the higher the priority. The
default is 5.
Target socket load - This field appears when the Type is procr. Use this field for load
balancing endpoint traffic across multiple IP interfaces. The value that you enter in the Target
socket load field controls the percentage of sockets allocated to each ip-interface within the
same Gatekeeper Priority. When all the ip-interfaces within the same Gatekeeper Priority
exceeds the target number that you allocate, the system continues to add sockets until the
interface is at its maximum capacity.
Valid entries
Usage
1 to platform maximum as follows:
● S8700 series: 3500
● S8500: 3500
● S8400: 2500
● CHAWK/BOXTER: 2000
● VM/BLADE: 1700
Enter the maximum number of sockets targeted for
this interface. The default is 80% of the platform
maximum.
Target socket load and Warning level - This field appears when Type is clan. The value that
you enter in the Target socket load and Warning level field controls the percentage of sockets
allocated to each ip-interface within the same Gatekeeper Priority. When all the ip-interfaces
within the same Gatekeeper Priority exceeds the target number that you allocate, the system
continues to add sockets until the interface is at its maximum capacity. If the targeted
percentage is exceeded on a CLAN a warning alarm is generated.
116 What’s New in Avaya Communication Manager
Release 3.1 changed screens
If there is only one ip-interface within a priority, the Target socket load and Warning level field
is no longer used for load balancing. You can still enter a value in this field to receive an error or
a warning alarm if the targeted value is exceeded.
Valid entries
Usage
1 to 499
Enter the maximum number of sockets targeted for this interface. If the
number of sockets exceeds the targeted number, a warning alarm is
generated. The default is 400.
Link - This display-only field shows the administered link number for an Ethernet link.
Valid entries
Usage
y/n
This display-only field shows the unique number for the Ethernet link
assigned on the Data Module screen.
Change 2
The IP Interfaces screen, when you use the list command, is a display-only screen. The
screen lists all of the TN2302AP Media Processor and TN2602AP Media Resource 320 circuit
packs in a system.
The IP Interfaces screen also indicates whether a TN2602 circuit pack is duplicated.
Duplicated TN2602 circuit packs are listed together, that is, one after the other.
For more information on the IP Interfaces screen using the list command, see IP
Interfaces on page 154.
IP Network Region
The IP Audio Hairpinning? field on the IP Network Region screen now defaults to n.
To view the IP Network Region screen:
1. Type change ip-network-region n, where n is the network region that you want to
change. Press Enter.
The system displays the IP Network Region screen (Figure 39: IP Network Region
screen on page 118).
Issue 1.1 June 2006
117
New and changed screens
Figure 39: IP Network Region screen
change ip-network-region 1
Page
1 of
19
IP NETWORK REGION
Region: 1
Location:
Authoritative Domain:
Name:
MEDIA PARAMETERS
Intra-region IP-IP Direct Audio: yes
Codec Set: 1
Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048
IP Audio Hairpinning? n
UDP Port Max: 3048
DiffServ/TOS PARAMETERS
RTCP Reporting Enabled? n
Call Control PHB Value: 34
RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46
Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 7
Audio 802.1p Priority: 6
Video 802.1p Priority: 5
AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS
RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
On page 2 of the IP Network Region screen, the LSP Servers in Priority Order section was
renamed to Backup Servers in Priority Order.
2. Click Next to see page 2.
The system displays the IP Network Region screen (Figure 40: IP Network Region
screen on page 118).
Figure 40: IP Network Region screen
change ip-network-region 1
Page
IP Network Region
INTER-GATEWAY ALTERNATIVE ROUTING
Incoming LDN Extension:
Conversion To Full Public Number - Delete:
Maximum Number of Trunks to Use:
BACKUP SERVERS IN PRIORITY ORDER
1
node-10-LSP_____
2
________________
3
________________
4
________________
5
________________
6
________________
118 What’s New in Avaya Communication Manager
Insert:
SECURITY PROCEDURES
1
challenge
2
3
4
2 of 19
Release 3.1 changed screens
IP Server Interface (IPSI) Administration
Use the IP Server Interface (IPSI) Administration screen to add a TN2312 IPSI (IP Server
Interface) circuit pack.The S8700 Series Media Server uses the IP Server Interface (IPSI) to
control port networks and provide tone, clock, and call classification services. The IPSI board
connects to the control network by way of Ethernet.
This change was prompted by the S8400 Media Server.
To view the IP Server Interface (IPSI) Administration screen:
1. Type change ipserver-interface n, where n is the number of the port network that
you want to change. Press Enter.
The system displays the IP Server Interface (IPSI) Administration screen (Figure 41: IP
Server Interface (IPSI) Administration screen on page 119).
Figure 41: IP Server Interface (IPSI) Administration screen
add ipserver-interface n
IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 2
IP Control? y
Socket Encryption? y
Ignore Connectivity in Server Arbitration?
Enable QoS? y
Administer secondary ip server interface board?
Primary IPSI
--------------Location: 1A02
Host: ipsi-A01a
DHCP ID: ipsi-A01a
VAL on IPSI? y
Secondary IPSI
-------------Location: 1B01
Host: ipsi-A01b
DHCP ID: ipsi-A01b
VAL on IPSI? y
QoS Parameters
--------------Call Control 802.1p: 4
Call Control DiffServ: 42
Field descriptions
VAL on IPSI? - This field appears only for TN8400/S8400 systems.
Valid entries
Usage
y/n
Indicates whether the primary TN2312BP/TN8412AP circuit pack has VAL
functionality running on it.
Issue 1.1 June 2006
119
New and changed screens
Language Translations
A new field, Audix Record, was added to the Button Labels section of the Language
Translations screen. This change is prompted by enhancements to Avaya Modular Messaging.
To view the Language Translations screen:
1. Type change display-messages button-labels. Press Enter.
The system displays the Station screen.
2. Click Next until you see the Audix Record field (Figure 42: Language Translations
screen on page 120).
Figure 42: Language Translations screen
change display-messages button-labels
LANGUAGE TRANSLATIONS
English
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Alternate FRL
ANI Request
Assist
ASVN Halt
AttQueueCall
AttQueueTime
Audix Record
Auto Callback
Auto Ckt Halt
AutoIC
Auto In
AutoWakeAlarm
Auto Wakeup
AuxWork
Busy
Translation
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
120 What’s New in Avaya Communication Manager
*************
*************
**********
*************
*************
*************
*************
*************
*************
*******
**********
*************
*************
********
*****
Page 2 of x
Release 3.1 changed screens
Media-Processor Status
The Media-Processor Status screen now shows duplication of a TN2602 circuit pack. This
change is prompted by Bearer signal duplication on page 26.
To view the Media-Processor Status screen:
1. Type status media-processor all. Press Enter.
The system displays the Media-Processor Status screen (Figure 43: Media-Processor
Status screen on page 121).
Note:
Note:
For information on the status media-processor all command, see status
media-processor on page 188.
Figure 43: Media-Processor Status screen
status media-processor all
Page 1 of x
MEDIA-PROCESSOR STATUS
Slot
02A04
03A04
04A05
Alarms
Links
Code
Mj Mn Wn Pr Cl El Dup St
TN2602 0 14 0|dn|up|up|n/a|act
TN2302 0 0 0|na|na|up|n/a|n/a
TN2602 0 12 0|dn|up|up|n/a|act
Slot
Code
Alarms
Links
Mj Mn Wn Pr Cl El Dup St
Pr=Peer Link, Cl=Control Link, El-Ethernet Link, Dup-Duplicate Slot, St=State
Issue 1.1 June 2006
121
New and changed screens
Optional Features
Two new fields, Enterprise Survivable Server and ESS Administration, are added to the
Optional Features screen. These changes are prompted by the Enterprise Survivable Server
increase feature.
To view the Optional Features screen:
1. Type display system-parameters customer-options. Press Enter.
The system displays the Optional Features screen.
2. Click Next until you see the Enterprise Survivable Server field (Figure 44: Optional
Features screen on page 122).
Figure 44: Optional Features screen
display system-parameters customer-options
OPTIONAL FEATURES
Emergency Access to Attendant?
Enable ‘dadmin’ Login?
Enhanced Conferencing?
Enhanced EC500?
Enterprise Survivable Server?
Enterprise Wide Licensing?
ESS Administration?
Extended Cvg/Fwd Admin?
External Device Alarm Admin?
Extended Cvg/Fwd Admin?
External Device Alarm Admin?
Five Port Networks Max per MCC?
Flexible Billing?
Forced Entry of Account Codes?
Global Call Classification?
Hospitality (Basic)?
Hospitality (G3V3 Enhancements)?
IP Trunks?
Page
4 of
y
IP Stations?
y
Internet Protocol (IP) PNC?
y
ISDN Feature Plus?
y
ISDN Network Call Redirection?
y
y
ISDN-BRI Trunks?
y
ISDN-PRI?
y
Local Survivable Processor?
y
Malicious Call Trace?
y
Mode Code for Centralized Voice Mail?
y
y
Multifrequency Signaling?
y Multimedia Appl. Server Interface(MASI)?
y
Multimedia Call Handling (Basic)?
y
Multimedia Call Handling (Enhanced)?
y
y
y
x
y
y
y
y
y
y
y
y
y
y
y
y
y
IP Attendant Consoles? y
(NOTE: You must logoff & login to effect the permission changes.)
Field descriptions
Enterprise Survivable Server - This license file-activated field indicates that this server is an
Enterprise Survivable Server (ESS).
ESS Administration - This license file-activated field allows administration of an Enterprise
Survivable Server (ESS) on the Enterprise Survivable Server Information screen.
122 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Route Pattern
A new field, Secure SIP?, is added to the Route Pattern screen. This change is prompted by
CSS Unique Certificates for SIP.
To view the Route Pattern screen:
1. Type change route-pattern n, where n is the pattern number. Press Enter.
The system displays the Route Pattern screen (Figure 45: Route Pattern screen on
page 123).
Figure 45: Route Pattern screen
change route-pattern 1
Page 1 of X
Pattern Number: 1_
SCCAN? n
No.
Grp. FRL NPA Pfx Hop Toll Del
No.
Mrk Lmt List Dgts
1: ___
_ ___ _ __
__
__
2: ___
_ ___ _ __
__
__
3: ___
_ ___ _ __
__
__
4: ___
_ ___ _ __
__
__
5: ___
_ ___ _ __
__
__
6: ___
_ ___ _ __
__
__
BCC VALUE TSC CA-TSC
0 1 2 3 4 W
Request
1:
2:
3:
4:
5:
6:
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
n
n
n
n
n
n
y
y
y
y
y
y
none
Pattern Name:
Secure SIP? n
DCS/
Inserted
QSIG
Digits
Intw
________________________________
n
________________________________
n
________________________________
n
________________________________
n
________________________________
n
________________________________
n
IXC
user
user
user
user
user
user
ITC BCIE Service/Feature BAND
No. Numbering LAR
Dgts
Format
Subaddress
___ both ept outwats-bnd____
_
________ none
rest
_______________
_
________ next
rest
_______________
_
________ rehu
rest
_______________
_
________ none
rest
_______________
_
________ none
rest
_______________
_
________ none
Field descriptions
Secure SIP? Valid entries
Usage
y/n
Specify whether the SIP or SIPS prefix will be used, if the call is routed to a
SIP trunk preference. If SIP trunks are not specified on the Route Pattern
screen, the call will be routed over whatever trunk is specified. Therefore,
to ensure a SIP TLS connection when such a route pattern is invoked, only
SIP trunks should be specified. The only instance for entering y in this field
is when the source provider requires a secure SIP protocol. Default is n.
Issue 1.1 June 2006
123
New and changed screens
Security-Related System Parameters
A new section, Remote Managed Services, and three new fields, RMS Feature Enabled?,
Port Board Security Notification, and Port Board Security Notification Interval, are added
to the Security-Related System Parameters screen.
To view the Security-Related System Parameters screen:
1. Type change system-parameters security. Press Enter.
The system displays the Security-Related System Parameters screen.
2. Click Next until you see the Remote Managed Services section
(Figure 46: Security-Related System Parameters screen on page 124).
Figure 46: Security-Related System Parameters screen
change system-parameters security
SECURITY-RELATED SYSTEM PARAMETERS
Page 2 of x
SECURITY VIOLATION NOTIFICATION PARAMETERS
SVN Station Security Code Violation Notification Enabled? y
Originating Extension: _____
Referral Destination: _____
Station Security Code Threshold: 10
Time Interval: 0:03
Announcement Extension: _____
STATION SECURITY CODE VERIFICATION PARAMETERS
Minimum Station Security Code Length: 4
Security Code for Terminal Self Administration Required? y
Receive Unencrypted from IP Endpoints? n
REMOTE MANAGED SERVICES
RMS Feature Enabled? y
Port Board Security Notification? y
Port Board Security Notification Interval? 60
ACCESS SECURITY GATEWAY PARAMETERS
MGR1? n
EPN? n
INADS? n
NET? n
Field descriptions
RMS Feature Enabled - This field enables the Remote Managed Services (RMS) feature.
Valid entries
Usage
y/n
Enter y to enable the Remote Managed Services feature. Default is n.
124 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Port Board Security Notification - This field appears only if the RMS Feature Enabled field is
set to y.
Valid entries
Usage
y/n
Enter y to enable port board denial of service notification. Default is n.
Port Board Security Notification Interval - This field appears only if the Port Board Security
Notification field is set to y.
Valid entries
Usage
60 to 3600, in
increments of 10
Enter the desired interval, in seconds, before port board denial of service
notification is sent. Default is 60.
Station
Note:
There are numerous changes to the Station screen for Communication Manager
release 3.1. The changes are all listed here, by page. The information also
mentions what feature prompted the change.
Note:
Page 2
Change 1
Two fields are renamed, and new values assigned.
●
The Call Waiting Indication? field was changed to Call Waiting Indication:. A value of c
was added to the accepted values for this field.
●
The Att. Call Waiting Indication? field was changed to Att. Call Waiting Indication:. A
value of c was added to the accepted values for this field.
These changes are prompted by Support caller ID on call waiting for MM711 and MM714.
To view the Station screen:
1. Type change station n, where n is the telephone extension. Press Enter.
The system displays the Station screen.
2. Click Next until you see the EMU Login Allowed? field (Figure 47: Station screen on
page 126).
Issue 1.1 June 2006
125
New and changed screens
Figure 47: Station screen
change station n
Page 2 of X
STATION
FEATURE OPTIONS
LWC Reception?
LWC Activation?
LWC Log External Calls?
CDR Privacy?
Redirect Notification?
Per Button Ring Control?
Bridged Call Alerting?
Switchhook Flash?
Ignore Rotary Digits?
Active Station Ringing:
H.320 Conversion?
Service Link Mode:
Multimedia Mode:
MWI Served User Type:
Automatic Moves:
AUDIX Name:
spe
y
n
n
y
n
n
n
n
single
Auto Select Any Idle Appearance?
Coverage Msg Retrieval?
Auto Answer:
Data Restriction?
Call Waiting Indication:
Attd. Call Waiting Indication:
Idle Appearance Preference?
Bridged Idle Line Preference?
Restrict Last Appearance?
Conf/Trans On Primary Appearance?
EMU Login Allowed?
n
Per Station CPN - Send Calling Number?
as-needed
Busy Auto Callback without Flash?
basic
______
Display Client Redirection?
_
Recall Rotary Digit? n
n
y
none
n
n
y
y
n
_
y
n
Select Last Used Appearance? n
Coverage After Forwarding? _
Multimedia Early Answer? n
Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections? n
Emergency Location Ext: 75001
Always use? n
IP Audio Hairpinning? n
Precedence Call Waiting? y
Field descriptions
Call Waiting Indication Valid entries
Usage
y
Enter y to activate Call Waiting (without Caller ID information) for the
telephone. This is the Default.
n
Call Waiting is not enabled for the station.
c
Enables the Caller ID Delivery with Call Waiting feature, which displays
CID information on for the waiting call. This value can only be entered
when the Type field is CallrID.
126 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Att. Call Waiting Indication Valid entries
Usage
y
Enter y to activate Call Waiting (without Caller ID information) for the
telephone. This is the Default.
n
Call Waiting is not enabled for the station.
c
Enables the Caller ID Delivery with Call Waiting feature, which displays
CID information on for the waiting call. This value can only be entered
when the Type field is CallrID.
Change 2
A new field, EMU Login Allowed?, is added to the Station screen. This field allows the station
to be used as a visited station by an Enterprise Mobility User (EMU) visitor user. This change is
prompted by the Enterprise Mobility User feature.
EMU Login Allowed Valid entries
Usage
y/n
Enter y to allow the station to be used as a visited station by an Enterprise
Mobility User (EMU) visitor user. Default is n.
Stations with Off-PBX Telephone Integration
A new screen, Stations with Off-PBX Telephone Integration, is added as part of the
Extension to Cellular feature. New commands are also added (see Release 3.1 new
commands on page 179).
Use the Stations with Off-PBX Telephone Integration screen to map an office telephone to a
cell phone through the Extension to Cellular feature. The office telephone can be a standard
office number or an administration without hardware (AWOH) station.
For more information on Extension to Cellular, see Feature Description and Implementation for
Avaya Communication Manager, 555-245-205.
To view the Stations with Off-PBX Telephone Integration screen:
1. Type add off-pbx-telephone station-mapping. Press Enter.
The system displays the Stations with Off-PBX Telephone Integration screen
(Figure 48: Stations with Off-PBX Telephone Integration screen on page 128).
Issue 1.1 June 2006
127
New and changed screens
Figure 48: Stations with Off-PBX Telephone Integration screen
add off-pbx-telephone station-mapping
Page 1 of 2
STATIONS WITH OFF-PBX TELEPHONE INTEGRATION
Station
Extension
43001
43001
43009
43011
43013
_______
_______
_______
_______
_______
_______
_______
_______
_______
_______
Application
EC500
OPS
OPS
CSP
SCCAN
______
______
______
______
______
______
______
______
______
______
Dial
Prefix
____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ -
Phone Number
9736831204
12345
67890
6095343211
9738765432
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
Trunk
Selection
ars
ars
aar
ars
ars
____
____
____
____
____
____
____
____
____
____
Configuration
Set
1
5
2
3
4/1
__
__
__
__
__
__
__
__
__
__
Field descriptions
Station Extension - The Station Extension field is an administered extension in your dial plan.
This number is the extension of the office telephone.
Valid entries
Usage
a valid number in
your dial plan
Type an extension number of the office phone up to eight digits. Default
is blank.
Application - The Application field indicates the type of off-PBX application that is associated
with the office telephone. You can assign more than one application to an office telephone.
Valid entries
Usage
blank
Default is blank.
EC500
cell phone with Extension to Cellular
OPS
SIP-enabled telephone
CSP
cell phone with Extension to Cellular provided by the cellular service provider
SCCAN
wireless SIP telephone and cell phone
128 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Dial Prefix - The system prepends the Dial Prefix to the off-PBX phone number before dialing
the off-PBX phone. The system deletes the dial prefix when a user enters their cell phone
number using the Self Administration Feature (SAFE) access code. You must set the routing
tables properly so that the dial prefix “1” is not necessary for correct routing.
Valid entries
Usage
blank
0–9, *, #
Type up to four digits, including “*” or “#”. If included, “*” or “#” must be in the
first digit position. Enter a “1” if the telephone number is long-distance. Enter
“011” if the phone number is international. Default is blank.
Phone Number - Enter the telephone number of the off-PBX telephone.
Valid entries
Usage
0–9
Type up to fifteen digits. Enter the complete 10-digit number. Default is blank.
Trunk Selection - This field defines what trunk group you will use for outgoing calls.
Valid entries
Usage
ars
aar
trunk group
number
Configuration Set - Use the Configuration Set field to administer the Configuration Set
number. This number contains the desired call treatment options for the Replace variable w/
short feature name station. Ninety-nine Configuration Sets exist.
The SCCAN application requires two different configuration sets selected for each station. The
first set is the value for the WLAN followed by a slash. The second is the value for the cellular
network.
Valid entries
Usage
1–99
Type the number of the Configuration Set(s). Default is blank.
2. Click Next to view page 2 of the Stations with Off-PBX Telephone Integration screen
(Figure 49: Stations with Off-PBX Telephone Integration screen, page 2 on page 130).
Finish the administration steps to map an office telephone to an off-PBX telephone. The
information that you entered on page 1 appears as read-only information on page 2.
Issue 1.1 June 2006
129
New and changed screens
Figure 49: Stations with Off-PBX Telephone Integration screen, page 2
add off-pbx-telephone station-mapping
STATIONS WITH OFF-PBX TELEPHONE INTEGRATION
Station
Extension
43001
43001
43009
43011
43013
Call
Limit
2
2
2
2
2/2
__
__
__
__
__
__
__
Mapping
Mode
both
both
both
both
both
___________
___________
___________
___________
___________
___________
___________
Calls
Allowed
all
all
all
all
all
________
________
________
________
________
________
________
Page 2 of 2
Bridged
Calls
both
both
both
both
both
___________
___________
___________
___________
___________
___________
___________
Call Limit Valid entries
Usage
blank
1–10
Set the maximum number of Replace variable w/ short feature name calls
that can be active simultaneously. Default is 2.
Mapping Mode - Enter the mode of operation for the Extension to Cellular cell phone. Use
these modes to control the degree of integration between the cell phone and the office phone.
The modes are valid for Replace variable w/ short feature name calls only. For each office
phone, you can only assign one cell phone as the origination mode. You cannot assign a cell
phone as either the origination or both mode more than once.
Valid entries
Usage
both
Default = both when the Phone Number field was previously administered
for another extension with a Mapping Mode of termination or none.
Default = termination when the Phone Number field was previously
administered with a Mapping Mode of origination or both.
In the both mode, users can originate and receive calls from the office phone
with the cell phone.
130 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Valid entries
Usage
termination
In termination mode, users can only use their Replace variable w/ short
feature name cell phone to receive calls from the associated office phone.
Users cannot use the cell phone to originate calls from the associated office
phone. Calls originating from the cell phone independent of the office phone
are independent of Extension to Cellular and behave exactly as before
enabling Extension to Cellular.
origination
In origination mode, users can only originate Replace variable w/ short
feature name cell phone calls from the associated office phone. Users cannot
use the cell phone to receive calls from the associated office phone.
none
In the none mode, users cannot originate or receive calls from the office
phone with the cell phone.
Calls Allowed - Identify the call filter type for an Replace variable w/ short feature name station.
The Calls Allowed values filter the type of calls to the office phone that a user can receive on
an Replace variable w/ short feature name cell phone.
Valid entries
Usage
all
Default is all.
The cell phone receives both internal and external calls.
internal
The cell phone receives only internal calls.
external
The cell phone receives only external calls.
none
The cell phone does not receive any calls made to the associated office
phone.
Bridged Calls - Use the Bridged Calls field to determine if bridged call appearances extend to
the Replace variable w/ short feature name cell phone. The valid entry definitions are the same
as the Mapping Mode field entries.
Valid entries
Usage
both
termination
origination
none
Default is both.
Issue 1.1 June 2006
131
New and changed screens
Trunk Group
Note:
Note:
There are numerous changes to the Trunk Group screen for Communication
Manager release 3.1. The changes are all listed here, by page. The information
also mentions what feature prompted the change. Some changes are specific to
the value that is in the Group Type field on page 1 of the Trunk Group screen.
Change 1
A new field, Apply Local Ringback?, is added to the Trunk Group screen. This new field
allows the system administrator to set the system to provide ringback tone to a caller. This
change is prompted by the Local ringback administration feature.
Note:
Note:
For this field to appear, the Carrier Medium field on page 1 of the Trunk Group
screen must be set to PRI_BRI.
To view the Trunk Group screen:
1. Type change trunk-group n, where n is the number of the trunk group. Press Enter.
The system displays the Trunk Group screen
2. Click Next until you see the Apply Local Ringback? field (Figure 50: Trunk Group
screen on page 132).
Figure 50: Trunk Group screen
change trunk-group 1
ACA Assignment? n
Page 3 of x
TRUNK FEATURES
Measured: none____
Maintenance Tests? y
Data Restriction? n
Abandoned Call Search? n
Suppress # Outpulsing? n
Charge Conversion: 1
Decimal Point: none
Currency Symbol:
Charge Type: units
Per Call CPN Blocking Code:
Per Call CPN Unblocking Code:
Outgoing ANI:
132 What’s New in Avaya Communication Manager
Ds1 Echo Cancellation? n
Apply Local Ringback? y
Release 3.1 changed screens
Field descriptions
Apply Local Ringback? - This field appears for ISDN and H.323 trunk groups when the
Carrier Medium field on page 1 is PRI_BRI.
Valid entries
Usage
y/n
Enter y to provide a local ringback tone to the caller. The local ringback is
removed when the call is connected. Default is n.
Change 2
A new field, Send EMU Visitor CPN?, is added to the Trunk Group screen. This change is
prompted by the Enterprise Mobility User feature.
3. Click Next until you see the Send EMU Visitor CPN? field (Figure 51: Trunk Group
screen on page 133).
Figure 51: Trunk Group screen
change trunk-group 1
Page 3 of x
TRUNK FEATURES
ACA Assignment?
Long Holding Time(hours):
Short Holding Time(sec):
Short Holding Threshold:
Used for DCS?
_
Measured: ____
Wideband Support?
_
Maintenance Tests?
_ Data Restriction? _
NCA-TSC Trunk Member:
__
Send Name: _
Send Calling Number:
_
Send EMU Visitor CPN?
_
_
_
_
n
Suppress # Outpulsing? _ Numbering Format: _______
Outgoing Channel ID Encoding: _________
UUI IE Treatment: ______
Maximum Size of UUI IE Contents: ___
Replace Restricted Numbers? _
Replace Unavailable Numbers? _
Send Connected Number: _
Hold/Unhold Notifications? _
Send UUI IE? _
Send UCID? _
BRS Reply-best DISC Cause Value: __
Ds1 Echo Cancellation? _
US NI Delayed Calling Name Update? _
Network (Japan) Needs Connect Before Disconnect? _
Time (sec) to Drop Call on No Answer:_
Outgoing ANI:_
R2 MFC Signaling:_
DSN Term? n
Precedence Incoming _______
Precedence Outgoing _______
Issue 1.1 June 2006
133
New and changed screens
Send EMU Visitor CPN - Use this field to control which calling party identification (extension of
the primary telephone or extension of the visited telephone) is used when a call is made from a
visited telephone. If you want to use the calling party information of the primary telephone, set
this field to n.
There are areas where public network trunks disallow a call if the calling party information is
invalid. In this case, there can be instances where the extension of the primary telephone is
considered invalid and the extension of the visited telephone must be used. To use the
extension of the visited telephone, set the Send EMU Visitor CPN? field to y.
Valid entries
Usage
y
Sends calling party identification information on the extension of the EMU
user’s telephone.
n
Sends calling party identification information on the primary telephone.
Change 3 (for ISDN trunks)
A value on the Carrier Medium field is changed, and three new fields, Member Assignment
Method, Signaling Group, and Number of Members, are added to the Trunk Group screen.
These changes are prompted by the Increased trunk members for IP signaling groups feature.
To view the Trunk Group screen for ISDN trunks:
1. Type change trunk-group n, where n is the trunk group number. Press Enter.
The system displays the Trunk Group screen (Figure 52: Trunk Group screen on
page 134). Make sure that the Group Type field is set to isdn.
Figure 52: Trunk Group screen
change trunk-group 1
Page
1 of xx
TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:
1
OUTSIDE CALL
outgoing
n
0
Group Type:
COR:
Outgoing Display?
Busy Threshold:
Auth Code:
Far End Test Line No:
TestCall BCC:
134 What’s New in Avaya Communication Manager
isdn
1
n
255
CDR Reports: y
TN: 1
TAC:
Carrier Medium: H.323
TestCall ITC: rest
Member Assignment Method:
Signaling Group:
Number of Members:
Release 3.1 changed screens
Field descriptions
Carrier Medium. The value IP was replaced with H.323.
Member Assignment Method - This field appears when the Carrier Medium field is set to
H.323.
Valid entries
Usage
manual
Default. Users manually assign trunk members to a signaling group.
auto
The system automatically generates members to a specific signaling
group. Entering Auto causes the Signaling Group and Number of
Members fields to appear.
Signaling Group - This field appears when Carrier Medium is H.323 and Member
Assignment Method is auto.
Valid entries
Usage
1 to 650, or blank
Enter assigned H.323 or SIP signaling group number between 1 and 650,
or blank.
Number of Members - This field appears when Carrier Medium is H.323 and Member
Assignment Method is auto. Indicates the number of virtual trunk members to be
automatically assigned to the signaling group number entered in the Signaling Group field.
Valid entries
Usage
0 to 255
Enter the number of trunks assigned to this signaling group. Default is 0.
Change 4 (for ISDN trunks)
A new page, QSIG Trunk Group Options, and two new fields, Display Forwarding Party
Name and Character Set for QSIG Name, are added to the Trunk Group screen. The fields
on this screen appear only when the Group Type field is isdn, and the Supplementary
Service Protocol field is b.
2. Click Next until you see the QSIG Trunk Group Options screen (Figure 53: QSIG Trunk
Group Options screen on page 136).
Issue 1.1 June 2006
135
New and changed screens
Figure 53: QSIG Trunk Group Options screen
change trunk-group 1
Page x of y
QSIG Trunk Group Options
Display Forwarding Party Name? y
Character Set for QSIG Name: eurofont
Field descriptions
Display Forwarding Party Name - This field appears only when the Group Type field on
page 1 is isdn, and the Supplementary Service Protocol field on page 2 is b.
Valid entries
Usage
y/n
Enter y if you want the system to display the name of the party who is
forwarding the call. Default is y.
Character Set for QSIG Name - This field appears only when the Group Type field on page 1
is isdn, the Supplementary Service Protocol field on page 2 is b, and the Display Character
Set field on the System Parameters Country-Options screen is Roman.
Valid entries
Usage
eurofont
This option sets the Roman Eurofont character set. This option is the default.
iso-8859-1
All data (i.e., characters) in the Name value transmitted over QSIG are
converted from Eurofont (Avaya proprietary encoding) to ISO 8859-1.
Note: ISO 8859-1, more formally known as ISO/IEC 8859-1, or less formally
as Latin-1, is part 1 of ISO/IEC 8859, a standard character encoding defined
by ISO. It encodes what it refers to as Latin alphabet no. 1, consisting of 191
characters from the Latin script, each encoded as a single 8-bit code value.
136 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Change 5 (for SIP trunks)
A new page, Protocol Variations, and one new field, Mark Users as Phone?, is added to the
Trunk Group screen. This screen appears only when the Group Type field is sip.
To view the Trunk Group screen for SIP trunks:
1. Type change trunk-group n, where n is the trunk group number. Press Enter.
The system displays the Trunk Group screen. Make sure that the Group Type field on
page 1 is set to sip.
2. Click Next until you see the Protocol Variations page (Figure 54: Trunk Group screen on
page 137).
Figure 54: Trunk Group screen
change trunk-group 1
Page 3 of x
PROTOCOL VARIATIONS
Mark Users as Phone?
Field descriptions
Mark Users as Phone? Valid entries
Usage
y/n
When the field is set to y, URIs in call control signaling messages
originated at the gateway are encoded with the “user=phone” parameter.
No subscription messages are encoded with the “user=phone” parameter
even when the field is set to y. Default is n.
Note: Do not change the default of 'no' (n) for this field unless you are sure
that every recipient of SIP calls via this trunk can accept and properly
interpret the optional “user=phone” parameter. Enterprise users without
support for “user=phone” in their SIP endpoints will experience adverse
effects, including rejected calls.
Change 6 (for SIP trunks)
A new field, Preferred Minimum Session Refresh Interval (sec), is added to the Trunk
Group screen. This screen appears only when the Group Type field is sip.
Issue 1.1 June 2006
137
New and changed screens
To view the Trunk Group screen for SIP trunks:
1. Type change trunk-group n, where n is the trunk group number. Press Enter.
The system displays the Trunk Group screen. Make sure that the Group Type field on
page 1 is set to sip.
2. Click Next until you see the Trunk Parameters section (Figure 55: Trunk Group screen on
page 138).
Figure 55: Trunk Group screen
change trunk-group 1
Group Type: sip
Page 2 of x
Trunk Parameters:
Unicode Name? y
Redirect on OPTIM Failure: 5000
SCCAN? n
Digital Loss Group: 18
Preferred Minimum Session Refresh Interval (sec): 120
Field descriptions
Preferred Minimum Session Refresh Interval (sec) - This field appears when the Group
Type field on page 1 is sip, and the SCCAN field on page 2 is n. This field sets the session
refresh timer value of a SIP session for non-SCCAN applications. The timer starts once a SIP
session established. Avaya Communication Manager then sends a session refresh request as a
Re-INVITE or UPDATE after every timer interval. In this way, an ongoing session is maintained.
If a session refresh request is not received before the interval passes, the session terminates.
Valid entries
Usage
90 to 1800
Administer the desired number of seconds for the session refresh interval.
Default is 120.
138 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Variables for Vectors
A new screen, Variables for Vectors, is added for Call Center-related enhancements for
Communication Manager release 3.1.
Use this screen to create variables and define the necessary parameters for each variable type.
You can specify the variable type, the name to use for the variable, the size of the variable, how
the variable gets set/assigned and whether the variable is local or global.
To view the Variables for Vectors screen:
1. Type change variables. Press Enter.
The system displays the Variables for Vectors screen (Figure 56: Variables for Vectors
screen on page 139).
Figure 56: Variables for Vectors screen
change variables
Page
1 of x
VARIABLES FOR VECTORS
Var
A:
B:
C:
D:
E:
F:
G:
H:
I:
J:
K:
L:
M:
Description
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
Type
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
Scope
__
__
__
__
__
__
__
__
__
__
__
__
__
Length
____
____
____
____
____
____
____
____
____
____
____
____
____
Start
___
___
___
___
___
___
___
___
___
___
___
___
___
Assignment
VAC
2. Click Next to view page 2 of the Variables for Vectors screen (Figure 57: Variables for
Vectors screen on page 140).
Issue 1.1 June 2006
139
New and changed screens
Figure 57: Variables for Vectors screen
change variables
Page
2 of x
VARIABLES FOR VECTORS
Var
N:
O:
P:
Q:
R:
S:
T:
U:
V:
W:
X:
Y:
Z:
Description
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
_______________
Type
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
_____
Scope
__
__
__
__
__
__
__
__
__
__
__
__
__
Length
____
____
____
____
____
____
____
____
____
____
____
____
____
Start
___
___
___
___
___
___
___
___
___
___
___
___
___
Assignment
VAC
Var Valid entries
Usage
A to Z
Display only. The letter identifying the row of a specific vector variable.
Description Valid entries
Usage
up to 27 alphanumeric
characters, or blank
Optionally enter an identifying name or description of the vector
variable. Default is blank.
140 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Type Valid entries
Usage
ani
asaiuui
collect
dow
doy
stepcnt
tod
value
vdn
vdntime
Enter the vector variable type.
Scope - This field only allows an entry for variables that can be either local or global. For those
variables that can only be one or the other, the L or G value is pre-populated automatically after
you enter the Type.
Valid entries
Usage
G/L
Indicate whether the variable is to be used locally (L) or globally (G).
Length - This field specifies the maximum number of digits from the data to assign to the
variable. Length does not apply to the tod, doy, dow or vdn variables. When Type is value, the
length is pre-populated with 1. A length entry is required for all types to which it applies.
Valid entries
Usage
1 to 16
Enter the maximum length of digits to use in the variable.
Start - This field specifies the beginning character position of the data digits string to be used for
assigning to the variable. The combination of the Start position and maximum length of the
digits string defines what is to be assigned to the variable. If the number of digits to be used is
less than the maximum length specified, only that portion is assigned to the variable. Start only
allows entry when Type is collect or asaiuui.
Valid entries
Usage
1 to 96
Enter the character position of the first digit to be stored in the variable.
Issue 1.1 June 2006
141
New and changed screens
Assignment - This field only allows entry when the Type field is set to value or collect G. Entry
of an Assignment for value or collect G is optional. That is, it can be left blank. The current
value/assignment for each global variable is always displayed in the Assignment column when
you access the Variables for Vectors screen. This includes the doy, dow, and tod types,
which show the current values from the switch clock as a display-only entry in the Assignment
column.
Valid entries
Usage
digits
Enter a number to pre-assign to the variable. This field displays the current
value for global values
VAC - The VAC (Variable Access Code) column only allows entry (1 to 9 or blank) when the
Type is value. Entry is not required for this type. If VAC is left as a blank, assignment is done
using the Assignment column. The VVx entry is one of the Vector Variable feature items on the
Feature Access Code (FAC) screen that can be assigned a FAC.
Valid entries
Usage
1 to 9 or blank
Displays the Vector Variable Feature Access Code (FAC) to use for
changing the value.
Vector Directory Number
A new field, Selection on BSR Ties, is added to the Vector Directory Number screen.
To view the Vector Directory Number screen:
1. Type change vdn n, where n is the extension of the vector directory number (vdn). Press
Enter.
The system displays the Vector Directory Number screen.
2. Click Next until you see the Selection on BSR Ties field (Figure 58: Vector Directory
Number screen on page 143).
142 What’s New in Avaya Communication Manager
Release 3.1 changed screens
Figure 58: Vector Directory Number screen
change vdn 4567
Page
2 of
x
VECTOR DIRECTORY NUMBER
AUDIX Name:
Return Destination:
VDN Timed ACW Interval:
BSR Application:
BSR Available Agent Strategy:
Selection on BSR Ties:
Observe on Agent Answer?
Display VDN for Route-To DAC?
VDN Override for ISDN Trunk ASAI Messages?
BSR Local Treatment?
Field descriptions
Selection on BSR Ties - This field appears only when the Vectoring (Best Service Routing)
field on the Optional Features screen is y.
Valid entries
Usage
system
The setting of the Selection on BSR Ties? field on the Feature-Related
System Parameters screen applies. This is the default.
Note: For more information, see Page 11 of the Feature-Related System
Parameters screen.
1st-found
BSR uses the first selection for routing. That is, BSR uses the current best
selected from the previous consider commands.
alternate
Allows alternating the BSR selection algorithm when a tie in EWT or
available agent criteria occurs. Every other time a tie occurs for calls from
the same active VDN, the selection from the consider step with the tie is
used instead of the first selected split/skill or location to send the call. This
helps balance the routing over the considered local splits/skills and remote
locations when cost of routing remotely is not a concern.
Issue 1.1 June 2006
143
New and changed screens
Release 3.0 changed screens
Avaya Communication Manager, release 3.0, includes the following changed screens. For a
more complete explanation of the screens and their function, see the Administrator Guide for
Avaya Communication Manager, 03-300509.
Announcements/Audio Sources
The Group/Port field is modified in the Announcements/Audio Sources screen. This change
is prompted by the Locally sourced announcements and music feature.
To view the Announcements/Audio Sources screen:
1. Type change announcements. Press Enter.
The system displays the Announcements/Audio Sources screen
(Figure 59: Announcements/Audio Sources screen on page 144).
Figure 59: Announcements/Audio Sources screen
change announcements
Page 1
ANNOUNCEMENTS/AUDIO SOURCES
1:
2:
3:
4:
5:
Ext.
55526___
55525___
33627___
________
________
Type
COR
integrated 1_
integ-mus 1_
integrated 1_
_________ 1_
_________ 1_
TN
1_
1_
1_
1_
1_
Name
business-hours
Music4Queue____
PresWelcome____
_______________
_______________
Q
y
b
y
n
n
QLen
N/A
N/A
N/A
Pro
n
n
n
Group/
Rate Port
64
01B18
64
G1
64
G2
Field descriptions
Group/Port - The Group/Port field identifies the group number or the port location of an audio
source.
Valid entries
Usage
Gnn
port location
Gnn, where nn represents a one or two-digit group number.
The location of the TN2501AP or the TN750 announcement
circuit pack. In this example, the location is 01B18.
ggv9 for media gateway V VAL, where gg is the number of the
media gateway, and n is the slot number.
ggvn
144 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Configuration Set
The Configuration Set screen introduces the Barge-in Tone field. This change is prompted by
the Extension to Cellular feature.
To view the Configuration Set screen:
1. Type change off-pbx-telephone configuration-set n, where n is the number
that is assigned with a coverage path command. Press Enter
The system displays the Configuration Set screen (Figure 60: Configuration Set
screen on page 145).
Figure 60: Configuration Set screen
change off-PBX-telephone configuration-set 1
CONFIGURATION SET: 1
Configuration Set Description:
Calling Number Style:
CDR for Origination:
CDR for Calls to EC500 Destination?
Fast Connect on Origination?
Post Connect Dialing Options:
Cellular Voice Mail Detection:
Barge-in Tone?
Identity When Bridging?
Standard
network
phone-number
y
n
dtmf
none
n
station
Field descriptions
Barge-in Tone - The Barge-in Tone field indicates whether the barge-in tone is enabled or
disabled.
Valid entries
Usage
y/n
Type y to enable the barge-in tone.
Type n to disable the barge-in tone.
Issue 1.1 June 2006
145
New and changed screens
Extensions To Call Which Activate Features By Name
Three new fields are added to the Extensions To Call which Activate Features By Name
screen. The new fields are Automatic Call Back, Extended Group Call Pickup, and Whisper
Page Activation. This change is prompted by the Extension to Cellular feature.
To view the Extensions To Call which Activate Features By Name screen:
1. Type change off-pbx-telephone feature-name-extensions. Press Enter.
The system displays the Extensions To Call which Activate Features By Name screen
(Figure 61: Extensions To Call Which Activate Features By Name screen on page 146).
Figure 61: Extensions To Call Which Activate Features By Name screen
change off-pbx-telephone feature-name-extensions
Page 1 of 1
EXTENSIONS TO CALL WHICH ACTIVATE FEATURES BY NAME
Active Appearance Select:
Automatic Call-Back:
Automatic Call-Back Cancel:
Call Forward All:
Call Forward Busy/No Answer:
Call Forward Cancel:
Call Park:
Call Park Answer Back:
Call Pick-Up:
Conference on Answer:
Calling Number Block:
Calling Number Unblock:
Directed Call Pick-Up:
Drop Last Added Party:
Exclusion (Toggle On/Off):
Extended Group Call Pick-up:
Held Appearance Select:
31001
_______
_______
31002
31003
31004
31005
________
________
________
________
________
________
________
________
________
________
Idle Appearance Select:
Last Number Dialed:
Malicious Call Trace:
Malicious Call Trace Cancel:
Off-PBX Call Enable:
Off-PBX Call Disable:
Priority Call:
Send All Calls:
Send All Calls Cancel:
Transfer On Hang-Up:
Transfer to Voice Mail:
Whisper Page Activation:
31020
________
________
________
________
________
________
________
________
________
________
________
Field descriptions
Automatic Call Back - Automatic Call Back allows users to choose whether they want an
extension to automatically call them back. If a user places a call to a busy or unanswered
telephone, the system calls the user back when the called telephone becomes available.
Extended Group Call Pickup - Extended Group Call Pickup allows a user to answer calls
that were directed to another call pickup group.
Whisper Page Activation - Whisper Page Activation allows a user to make whisper pages. A
whisper page is a low volume message. Users can send a whisper page when they want only
one person on a conference call to hear a message.
146 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Feature Access Code (FAC)
The Feature Access Code (FAC) screen introduces two new fields:
●
EC500 Self Administration Access Code
●
Enhanced EC500 Activation / Deactivation
This change is prompted by the Extension to Cellular feature.
To view the Feature Access Code (FAC) screen:
1. Type change feature-access-codes. Press Enter
The system displays the Feature Access Code (FAC) screen.
2. Click Next until you see the EC500 Self Administration Access Code field
(Figure 62: Feature Access Code (FAC) screen on page 147).
Figure 62: Feature Access Code (FAC) screen
change feature-access-codes
Page
2 of
FEATURE ACCESS CODE (FAC)
Data Origination Access Code:
Data Privacy Access Code:
Directed Call Pickup Access Code:
Emergency Access to Attendant Access Code: *11
EC500 Self Administration Access Code:
Enhanced EC500 Activation: *89
Deactivation:#89
Extended Call Fwd Activate Busy D/A: *23 All: *24
Deactivation:#23
Extended Group Call Pickup Access Code:
Facility Test Calls Access Code:
Flash Access Code: *88
Group Control Restrict Activation: *15
Deactivation: #15
Hunt Group Busy Activation: *81
Deactivation: #81
ISDN Access Code:
Last Number Dialed Access Code: *54
Leave Word Calling Message Retrieval Lock: *48
Leave Word Calling Message Retrieval Unlock: #45
Leave Word Calling Send A Message: *60
Leave Word Calling Cancel A Message: #60
Malicious Call Trace Activation:
Deactivation:
Meet-me Conference Access Code Change:
8
Field descriptions
EC500 Self Administration Access Code - The EC500 Self Administration Access Code
field indicates the access code in accordance with an customer dial plan.
Enhanced EC500 Activation / Deactivation - The Enhanced EC500 Activation /
Deactivation fields allow a user to activate and deactivate the enhanced EC500 features.
Issue 1.1 June 2006
147
New and changed screens
Feature-Related System Parameters
Note:
Note:
There are numerous changes to the Feature-Related System Parameters
screen for Communication Manager release 3.0. The changes are all listed here,
by page. The information also mentions what feature prompted the change.
To view the Feature-Related System Parameters screen:
1. Type change system-parameters features. Press Enter.
The system displays the Feature-Related System Parameters screen
(Figure 63: Feature-Related System Parameters screen on page 148).
Figure 63: Feature-Related System Parameters screen
change system-parameters features
Page 1 of 15
FEATURE-RELATED SYSTEM PARAMETERS
Self Station Display Enabled? n
Trunk-to-Trunk Transfer? none
Automatic Callback - No Answer Timeout Interval (rings): 4_
Call Park Timeout Interval (minutes): 10
Off-Premises Tone Detect Timeout Interval (seconds): 20_
AAR/ARS Dial Tone Required? y
Music/Tone On Hold: music__ Type: Group 1_
Music (or Silence) On Transferred Trunk Calls: all
DID/Tie/ISDN/SIP Intercept Treatment: attd
Internal Auto-Answer of Attd-Extended/Transferred Calls?
Automatic Circuit Assurance (ACA) Enabled?
ACA Referral Calls:
ACA Referral Destination:
ACA Short Holding Time Originating Extension:
ACA Long Holding Time Originating Extension:
Abbreviated Dial Programming by Assigned Lists:
Auto Abbreviated/Delayed Transition Interval(rings):
Protocol for Caller ID Analog Terminals:
Display Calling Number for Room to Room Caller ID Calls?
y
y
local
________
______
______
Bellcore
Page 1
The Music/Tone On Hold field is modified to change the source type for music-on-hold. This
change is prompted by the Locally sourced announcements and music feature.
148 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Field descriptions
Music/Tone On Hold - The Music/Tone On Hold field assigns audio as music on hold or tone
on hold.
Valid entries
Usage
none
music
tone
Type none for no music-on-hold.
Type music for music-on-hold.
Type tone for tone-on-hold.
If you type music or tone, the Type field appears.
Type - Use the Type field to assign music to an extension, a group, or a port.
Valid entries
Usage
ext
Type ext and the corresponding extension number of the
integ-mus announcement/audio group.
Type group and the corresponding music-on-hold
analog group number.
Type port and the corresponding port location of the
music-on-hold analog/aux-trunk source.
group
port
2. Click Next until you see the TTI/PSA Parameters area (Figure 64: Feature-Related
System Parameters screen on page 149).
Figure 64: Feature-Related System Parameters screen
change system-parameters features
FEATURE-RELATED SYSTEM PARAMETERS
Page 3 of 15
TTI/PSA PARAMETERS
WARNING! SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE
Terminal Translation Initialization (TTI) Enabled? y
TTI State: voice
TTI Security Code: 123456
Record CTA/PSA/TTI Transactions in History Log? n
Enhanced PSA Location/Display Information Enabled? n
Default COR for Dissociated Sets: 94
CPN, ANI for Dissociated Sets: 1234567
Customer Telephone Activation(CTA) Enabled? n
Issue 1.1 June 2006
149
New and changed screens
Page 3
●
The COR for PSA Dissociated Sets field in earlier releases of Communication Manager
is renamed Default COR for Dissociated Sets.
●
The CPN, ANI for PSA Dissociated Sets field in earlier releases of Communication
Manager is renamed CPN, ANI for Dissociated Sets.
This change is prompted by the Emergency calls from unnamed IP endpoints feature. The
function of these two fields did not change.
3. Click Next until you see the Enable Inter-Gateway Alternate Routing? field
(Figure 65: Feature-Related System Parameters screen on page 150).
Figure 65: Feature-Related System Parameters screen
change system-parameters features
Page 5 of 15
FEATURE-RELATED SYSTEM PARAMETERS
SYSTEM PRINTER PARAMETERS
Endpoint: ____
Lines Per Page: 60
EIA Device Bit Rate:
SYSTEM-WIDE PARAMETERS
Switch Name: ________________
Emergency Extension Forwarding (min): 10
Enable Inter-Gateway Alternate Routing? n
MALICIOUS CALL TRACE PARAMETERS
Apply MCT Warning Tone? n
MCT Voice Recorder Trunk Group: ___
Delay Sending Release (seconds)?
SEND ALL CALLS OPTIONS
Send All Calls Applies to: station
Auto Inspect on Send All Calls? n
UNIVERSAL CALL ID
Create Universal Call ID (UCID)? n
UCID Network Node ID: ___
150 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Page 5
●
The Emergency Extension Forwarding (min) field is moved under the System-Wide
Parameters area.
●
A new field, Enable Inter-Gateway Alternate Routing?, is added to the Feature-Related
System Parameters screen. This change is prompted by the Inter-Gateway Alternate
Routing feature.
Valid entries
Usage
y/n
Type y to enable the Inter-Gateway Alternate Routing
feature. The default is n.
4. Click Next until you see the Maximum Ports per Expanded Meet-me Conf field
(Figure 66: Feature-Related System Parameters screen on page 151).
Figure 66: Feature-Related System Parameters screen
change system-parameters features
Page 7 of 15
FEATURE-RELATED SYSTEM PARAMETERS
CONFERENCE/TRANSFER
Abort Transfer?
Transfer Upon Hang-Up?
Abort Conference Upon Hang-Up?
No Hold Conference Timeout:
ANALOG BUSY AUTO CALLBACK
Without Flash?
No Dial Tone Conferencing?
Select Line Appearance Conferencing?
Unhold?
Maximum Ports per Expanded Meet-me Conf:
Announcement:
Voice Mail Hunt Group Ext:
AUDIX ONE-STEP RECORDING
Apply Ready Indication Tone To Which Parties In The Call?
Interval For Applying Periodic Alerting Tone (seconds):
Page 7
A new field, Maximum Ports per Expanded Meet-me Conf, allows you to administer the
maximum number of conferees in an Expanded Meet-me Conference. This is a system-wide
limit. You cannot administer the maximum number of conferees on a per Expanded-Meet-me
VDN basis.
Issue 1.1 June 2006
151
New and changed screens
The Maximum Ports per Expanded Meet-me Conf field is hidden if the Maximum Number of
Expanded Meet-me Conference Ports field on the Optional Features screen is set to 0. This
change is prompted by the Expanded Meet-me Conferencing feature.
Valid entries
Usage
0 to 300, in
increments of 50
Enter the maximum number of parties allowed for each
conference on your system.
5. Click Next until you see the International Call Routing Parameters area
(Figure 67: Feature-Related System Parameters screen on page 152).
Figure 67: Feature-Related System Parameters screen
change system-parameters features
Page 9 of 15
FEATURE-RELATED SYSTEM PARAMETERS
CPN/ANI/ICLID PARAMETERS
CPN/ANI/ICLID Replacement for Restricted Calls:
CPN/ANI/ICLID Replacement for Unavailable Calls:
INTERNATIONAL CALL ROUTING PARAMETERS
Local Country Code: 1
International Access Code: 011
ENBLOC DIALING PARAMETERS
Enable Enbloc Dialing without ARS FAC?
Page 9
The SBS Parameters area in earlier releases of Communication Manager is renamed
International Call Routing Parameters. This change is prompted by the Inter-Gateway
Alternate Routing feature.
152 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Gateway Status
A new value, pd, is added to the Lk field on the Gateway Status screen. This change is
prompted by the Auto fallback to primary for H.248 media gateways feature.
To view the Gateway Status screen:
1. Type status media-gateways. Press Enter.
The system displays the Gateway Status screen (Figure 68: Gateway Status screen on
page 153).
Figure 68: Gateway Status screen
status media-gateways
ALARM SUMMARY
Major: 3
Minor: 0
Warning: 0
Page 1 of x
BUSY-OUT SUMMARY
Trunks: 0
Stations: 0
H.248 LINK SUMMARY
Links Down: 3
Links UP: 0
# Logins: 1
GATEWAY STATUS
Alarms
MG Mj Mn Wn Lk
1
1| 0| 0|dn
2
1| 0| 0|up
3
1| 0| 0|pd
Alarms
MG Mj Mn Wn Lk
Alarms
MG Mj Mn Wn Lk
Alarms
MG Mj Mn Wn Lk
Alarms
MG Mj Mn Wn Lk
Lk
The value pd indicates a pending link status when all three of these conditions are met:
●
The media gateway has a recovery rule administered
●
At least one registration request has been denied
●
The media gateway has still not registered with the primary server
Issue 1.1 June 2006
153
New and changed screens
Integrated Announcements/Audio
The Group Number field is added to the Integrated Announcements/Audio screen. This
change is prompted by the Locally sourced announcements and music feature.
To view the Integrated Announcements/Audio screen:
1. Type list integrated-annc-boards. Press Enter.
The system displays the Integrated Announcements/Audio screen (Figure 69: Integrated
Announcements/Audio screen on page 154).
Figure 69: Integrated Announcements/Audio screen
list integrated-annc-boards
Page 1
INTEGRATED ANNOUNCEMENTS/AUDIO
Board Location: 08A05
Annc.
Number
1:
2:
3:
4:
5:
Internal
Number
NA
NA
NA
NA
NA
Group
Number
6
31
11
10
9
Time Remaining at 64 Kbps: 255
Announcement
Extension
658001
658002
658003
658004
658005
Name
Collect_1_digit
No_digits_coll_Goodbye
Collect_5_digits
voa1
Music4
Rate
64
64
64
64
32
Length in
Seconds
4
5
5
6
60
Field descriptions
Group Number - The Group Number field identifies the audio group number of the audio
sources on a specific VAL or V VAL.
IP Interfaces
Numerous fields have either been added or changed on the IP Interfaces screen. These
changes are prompted by the new TN2602AP IP Media Resource 320 circuit pack.
To view the IP Interfaces screen:
1. Type change ip-interface n, where n is the slot location.
The system displays the IP Interfaces screen (Figure 70: IP Interfaces screen on
page 155).
154 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Figure 70: IP Interfaces screen
change ip-interface 1a03
Page 1 of 1
IP INTERFACES
Critical Reliable Bearer? y
MEDRPRO
01A03
Slot:
TN2602
Code/Suffix:
Node Name:
IP Address:
255.255.255.0
Subnet Mask:
Gateway Address:
y
Enable Ethernet Port?
20
Network Region:
n
VLAN:
xxx
VOIP Channel:
255.255.255.255
Virtual MAC Table:
ETHERNET OPTIONS
Auto? n
Auto?
Speed: 100Mbps
Duplex: Full
Type:
Slot:
Code/Suffix:
Node Name:
IP Address:
Subnet Mask:
Gateway Address:
Enable Ethernet Port?
Network Region:
VLAN:
VOIP Channel:
Shared Virtual Assress:
Virtual MAC Table:
01B03
TN2602
255.255.255.0
y
20
n
xxx
y
Field Descriptions
Critical Reliable Bearer?
The system displays this field when the:
●
Board code of the slot location that you entered in the command is TN2602
●
Software version is V13 or greater
This field indicates that two TN2602AP circuit packs are (y) or are not (n) duplicated in a port
network.
Valid entries
Usage
n (the default)
Indicates that two TN2602AP circuit packs are not duplicated in a port
network.
y
Indicates that two TN2602AP circuit packs are duplicated in a port
network. The fields on the right side of the screen appear. The system
auto-fills the Subnet Mask and Network Region fields from the values on
the left side of the screen.
Issue 1.1 June 2006
155
New and changed screens
Slot - The Slot field is display only. The system populates the left side of the screen with the
slot location that you entered in the command. If the Critical Reliable Bearer? field is y, you
must enter the slot location of the second TH2602 circuit pack in the Slot field on the right of the
screen.
Code/Suffix - The Code/Suffix field is display only. The system populates the left side of the
screen with the proper value based on the slot location that you entered in the command. If the
Critical Reliable Bearer? field is y, the system populates the right side of the screen with the
same value.
Node Name - Type the node name value on the left side of the screen that is associated with
the IP Address of the TN2602 circuit pack. If the Critical Reliable Bearer? field is y, type the
node name value of the second TN2602 circuit pack on the right side of the screen.
IP Address - Type the IP address on the left side of the screen that is associated with the Node
Name of the TN2602 circuit pack. If the Critical Reliable Bearer? field is y, type the IP address
of the second TN2602 circuit pack on the right side of the screen.
Subnet Mask - Type the subnet mask, if any, on the left side of the screen that is associated
with the IP address. If the Critical Reliable Bearer? field is y, the system populates the right
side of the screen with the same value.
Gateway Address - The Gateway Address field is display only. The system populates the left
side of the screen with the gateway address that is associated with the IP address. If the
Critical Reliable Bearer? field is y, the system populates the right side of the screen with the
same value.
Enable Ethernet Port? - This field indicates that two TN2602AP circuit packs are (y) or are not
(n) duplicated in a port network.
Valid entries
Usage
n
Indicates that the ethernet port that is associated with the TN2602AP
circuit pack is disabled.
● You cannot disable the ethernet port if the active TN2602AP circuit
pack is part of an active/standby pair.
● You can disable the ethernet port if either:
- There is no standby TN2602AP circuit pack
- The standby TN2602AP circuit pack has already been disabled
y (the default)
Indicates that the ethernet port that is associated with the TN2602AP
circuit pack is enabled.
Network Region - Type the network region on the left side of the screen that is associated with
the TN2602AP circuit pack. If the Critical Reliable Bearer? field is y, the system populates the
right side of the screen with the same value. You can override the value on the right side of the
screen.
156 What’s New in Avaya Communication Manager
Release 3.0 changed screens
VLAN - This field is the virtual LAN (VLAN) that is associated with the TN2602AP circuit pack. If
the Critical Reliable Bearer? field is y, override the default value, if necessary, on both sides of
the screen.
Valid entries
Usage
n (the default)
There is no VLAN ID that is associated with the TN2602AP circuit pack.
0-4094
A four-digit alpha-numeric character, between 0 and 4094, that indicates
the VLAN ID and user priority (802.1p/Q).
VOIP Channels - The VOIP Channels field identifies the number of VoIP channels that are
allocated to the associated TN2602AP circuit pack.
Valid entries
Usage
0 (the default)
80
320
Type the number of VoIP channels - 0, 80, or 320 - that are associated with
the TN2602AP circuit pack.
●
If two TN2602AP circuit packs are administered (the Critical Reliable Bearer? field is y)
in a load balanced configuration, you can give each VoIP channel setting the value of 320,
for a total of 640.
●
If two TN2602AP circuit packs are administered (the Critical Reliable Bearer? field is y)
in a critically duplicated configuration, the system populates the right side of the screen
with the value that you typed in the left side. The field on the right side of the screen is
display only.
Shared Virtual Address - The system displays the Shared Virtual Address field only when
the Critical Reliable Bearer? field is y. Type the virtual IP address for the duplicated bearer
circuit packs.
Virtual MAC Table and Virtual MAC Address - The system displays the Virtual MAC
Address field only when the Critical Reliable Bearer? field is y. The system populates the
Virtual MAC Address field based on the value in the Virtual MAC Table field.
Issue 1.1 June 2006
157
New and changed screens
IP Network Region
Note:
Note:
There are numerous changes to the IP Network Region screen for
Communication Manager release 3.0. The changes are all listed here, by page.
The information also mentions what feature prompted the change.
To view the IP Network Region screen:
1. Type change ip-network-region n, where n is the network region that you want to
change. Press Enter.
The system displays the IP Network Region screen.
2. Click Next until you see the Inter-Gateway Alternate Routing area (Figure 71: IP Network
Region screen on page 158).
Figure 71: IP Network Region screen
change ip-network-region 1
Page 2 of 19
IP NETWORK REGION
INTER-GATEWAY ALTERNATE ROUTING
Incoming LDN extension:_________
Conversion to Full Public Number - Delete:
Maximum Number of Trunks to Use:___
LSP NAMES IN PRIORITY ORDER
1
2
3
4
5
6
Insert:_________
SECURITY PROCEDURES
1. strong___
2. challenge
3. _________
4. _________
Page 2
A new field area, Inter-Gateway Alternate Routing, is added to the IP Network Region
screen. This change is prompted by the Inter-Gateway Alternate Routing feature.
Incoming LDN Extension
Valid entries
Usage
Valid unused
extension
Assign an unused Listed Directory Number for incoming
IGAR calls.
158 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Conversion to Full Public Number - Insert
Valid entries
Usage
up to 13 digits
Enter up to 13 digits to insert. International numbers
should begin with a plus sign (+), or blank.
The optional plus sign (+) at the beginning of the inserted
digits is an international convention indicating that you
must dial the local international access code before the
number.
Maximum Number of Trunks to Use
It is necessary to impose a limit on the trunk usage in a particular PN/MG in a network region
when IGAR is active. The limit is required because if there is a major IP WAN network failure, it
is possible to use all trunks in the network region(s) for IGAR calls.
Note:
Valid entries
Usage
1 to 999, or blank
Enter the maximum number of trunks to be used for
alternate routing.
Note:
The S8500 supports up to 800 IP trunks (via license file limitations), which is less
than the S8700 limit, but the overall maximum number of trunk members is the
same as on the S8700: 8000.
A new field area, Security Procedures, is added to the IP Network Region screen. This
change is prompted by the Security of IP telephone registration/H.323 signaling channel
feature.
The permitted values for the Security Procedures area fields are:
strong - To permit use of any strong security profile. Only the pin-eke profile fits this category.
pin-eke - The mechanism used by this feature.
challenge - Includes the various methods of PIN-based challenge/response schemes in current
use. These schemes support mechanisms prior to Communication Manager release 3.0.
any-auth - Includes any of the above.
By default, each network region has challenge enabled for a new installation, or when
upgrading from a release prior to the implementation of this requirement.
Issue 1.1 June 2006
159
New and changed screens
IP telephones register based upon capability and administration:
●
If you select either strong or pin-eke, IP telephones that do not support this feature
cannot register or make calls.
●
If you select challenge, all IP telephones use the registration mechanism prior to
Communication Manager release 3.0.
●
If you select any-auth, all telephones use whatever registration mechanism they support
to register.
3. Click Next until you see the Inter Network Region Connection Management area
(Figure 72: IP Network Region screen on page 160).
Figure 72: IP Network Region screen
change ip-network-region 1
Page 3 of 19
Inter Network Region Connection Management
src
rgn
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
dst
rgn
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
codec
set
1
1
1
1
1
1
1
direct
WAN
y
n
n
n
y
y
WAN-BW limits
256:Kbits
Intervening-regions
1
___
___
___
1
6
___
___
___
___
___
___
Dynamic CAC
Gateway
IGAR
:NoLimit
10:Calls
Page 3
A new column, IGAR, is added to the IP Network Region screen. This change is prompted by
the Inter-Gateway Alternate Routing feature.
160 What’s New in Avaya Communication Manager
Release 3.0 changed screens
IGAR
This field allows pair-wise configuration of Inter-Gateway Alternate Routing (IGAR) between
network regions. If the field is set to y, the IGAR capability is enabled between the specific
network region pair. If it is set to n, the IGAR capability is disabled between the network region
pair. The (f)orced option moves all traffic onto the PSTN.
Valid entries
Usage
y
Enter y to enable IGAR capability between this network
region pair.
n
IGAR capability between this network region pair is
disabled. The default is n, except when codec set is
pstn. When codec set is pstn, this field defaults to y.
f
Forced. This option can be used during initial installation
to verify the alternative PSTN facility selected for a
network region pair. This option may also be used to
temporarily move traffic off of the IP WAN if an edge
router is having problems or an edge router needs to be
replaced between a network region pair.
IP-Options System Parameters
A new field, Periodic Registration Timer (min), is added to the IP-Options System
Parameters screen.
To view the IP-Options System Parameters screen:
1. Type display system-parameters ip-options. Press Enter.
The system displays the IP-Options System Parameters screen (Figure 73: IP-Options
System Parameters screen on page 162).
Issue 1.1 June 2006
161
New and changed screens
Figure 73: IP-Options System Parameters screen
display system-parameters ip-options
IP-OPTIONS SYSTEM PARAMETERS
IP MEDIA PACKET PERFORMANCE THRESHOLDS
Roundtrip Propagation Delay (ms)
High:
Packet Loss (%)
High:
Ping Test Interval (sec):
Number of Pings Per Measurement Interval:
120
10
10
10
Page 1 of 2
Low: 75
Low: 5
RTCP MONITOR SERVER
Default Server IP Address: 192.168.15 .25
Default Server Port: 5005
Default RTCP Report Period(secs): 5
AUTOMATIC TRACE ROUTE ON
Link Failure? y
H.248 MEDIA GATEWAY
Link Loss Delay Timer (min): 5
H.323 IP ENDPOINT
Link Loss Delay Timer (min): 1
Primary Search Time (sec): 15
Periodic Registration Timer (min): 20
Field descriptions
The range for the Periodic Registration Timer (min) field is 1 to 120 minutes. The default
value is 20 minutes. The purpose of this field is to set the time, in minutes, when a
previously-registered IP telephone attempts to reregister. For example, a registered IP
telephone becomes unregistered because another telephone has taken over the extension.
After the number of minutes in the Periodic Registration Timer (min) field have elapsed, the
unregistered telephone attempts to reregister.
If the reregistration is unsuccessful, the telephone again attempts to reregister. For example, if
the Periodic Registration Timer (min) field is set to 20 minutes, the telephone attempts to
reregister after 20 minutes has elapsed. If unsuccessful, the system waits another 20 minutes
and tries again. This process continues until the system can reregister the telephone.
162 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Language Translations
Message 4, ^-party conference in progress, is added to the Language Translations screen
for transfer/conference. This change is prompted by the Expanded Meet-me Conferencing
feature.
To view the Language Translations screen for transfer/conference:
1. Type change display-messages transfer-conference. Press Enter.
The system displays the Language Translations screen (Figure 74: Language
Translations screen on page 163).
Figure 74: Language Translations screen
change display-messages transfer-conference
LANGUAGE TRANSLATIONS
Note:
1.
English: Transfer completed.
Translation: ********************************
2.
English: Call next party.
Translation: ****************************************
3.
English: Press conference to add party.
Translation: ****************************************
4.
English: ^-party conference in progress.
Translation: ****************************************
5.
English: Conference canceled.
Translation: ****************************************
6.
English: Select line ^ to cancel or another line.
Translation: ****************************************
Page 1 of x
Note:
You manually must change the character “^” in your user-defined language.
Communication Manager does not update automatically.The character “^” is a
place holder character.
Message 4
English Text
Replacement Info
^-party conference in progress
Communication Manager replaces the “^”
character with the number of parties that are
currently on the conference call.
Issue 1.1 June 2006
163
New and changed screens
List Usage Report
The List Usage Report screen displays an IP telephone that is in TTI service. This change is
prompted by the Emergency calls from unnamed IP endpoints feature.
To view the List Usage Report screen:
1. Type list usage ip-address n, where n is the IP address that you want to review.
Press Enter.
The system displays the List Usage Report screen (Figure 75: List Usage Report
screen on page 164).
Figure 75: List Usage Report screen
list usage ip-address 135.9.159.130
LIST USAGE REPORT
Used By
TTI Station
Port Number s00074
Station IP Addr
Location Parameters
Two new fields, International Access Code and Local E.164 Country Code, are added to the
Location Parameters screen. This change is prompted by the Inter-Gateway Alternate Routing
feature.
To view the Location Parameters screen:
1. Type change location-parameters n, where n is the location code. Press Enter.
The system displays the Location Parameters screen (Figure 76: Location Parameters
screen on page 165).
164 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Figure 76: Location Parameters screen
change location-parameters 1
Page 1 of 4
LOCATION PARAMETERS 1
Tone Generation Plan: 1
Analog Ringing Cadence:
Analog Line Transmission:
DCP Terminal-parameters Plan:
Country code for CDR:
Companding Mode:
1
1
1
1
Mu-law
International Access Code:
Local E.164 Country Code:
RECALL TIMING
Flashhook Interval? _
Disconnect Timing (msec): 150
Upper Bound (msec): 1000
Lower Bound (msec): 200
Forward Disconnect Timer (msec): 600
MF Interdigit Timer (sec): 10
Outgoing Shuttle Exchange Cycle Timer (sec): 4
International Access Code
Valid entries
Usage
up to 5 digits
(0 to 9), or blank
Enter up to 5 digits for the International Access Code.
Default is blank.
Local E.164 Country Code
Valid entries
Usage
up to 3 digits
(0 to 9), or blank
Enter up to 3 digits for the E.164 Country Code. Default
is blank.
Media-Gateway
A new field, Recovery Rule, is added to the Media-Gateway screen. This change is prompted
by the Auto fallback to primary for H.248 media gateways feature.
Issue 1.1 June 2006
165
New and changed screens
To view the Media-Gateway screen:
1. Type change media-gateway n, where n is the number of the gateway. Press Enter.
The system displays the Media-Gateway screen (Figure 77: Media-Gateway screen on
page 166).
Figure 77: Media-Gateway screen
change media-gateway 1
Page 1 of 1
MEDIA-GATEWAY
Number:
Type:
Name:
Serial No:
Network Region:
Registered?
Recovery Rule:
Slot
V1:
V2:
V3:
V4:
V5:
V6:
V7:
V8:
V9:
1
IP Address:
g250
FW Version/HW Vintage:
____________________
MAC Address:
____________________ Encrypt Link? y
Location:
n
Controller IP Address:
____
Site Data: ____________________
Name: ____________________
Module Type
________
_________
________
________
________
________
________
________
________
Max Survivable IP Ext:
Recovery Rule
The Recovery Rule field allows you to associate an auto-fallback recovery rule with this media
gateway. By associating the recovery rule to the Media Gateway screen, you can use the list
media-gateway command to see what media gateways have the same recovery rules. All the
administration parameters for the media gateways are consolidated on a single screen. The
actual logic of the recovery rule is separate, but an administrator can start from the Media
Gateway screen and find the recovery rule.
For more information, see the System Parameters Media Gateway Automatic Recovery Rule
screen.
Valid entries
Usage
1 to the server maximum,
or none
Type a valid recovery rule number.
Type none to disable.
166 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Media-Gateway Report
Two new fields, RecRule and Reg?, are added to the Media-Gateway Report screen. These
changes are prompted by the Auto fallback to primary for H.248 media gateways feature.
To view the Media-Gateway Report screen:
1. Type list media-gateway. Press Enter.
The system displays the Media-Gateway Report screen (Figure 78: Media-Gateway
Report screen on page 167).
Figure 78: Media-Gateway Report screen
list media-gateway
MEDIA-GATEWAY REPORT
Num Name
Serial No/
FW Ver/HW Vint
IP Address/
Cntrl IP Addr
Type
NetRgn Reg?
RecRule
5
MG5
01DR12310234
220.66 .0 ./0
172.154.658.251
g700
205
none
n
7
MG5
01DR12310234
220.66 .0 ./0
172.154.658.251
g700
205
none
y
11
MG5
01DR12310234
220.66 .0 ./0
172.154.658.251
g700
205
1
n
19
MG5
01DR12310234
220.66 .0 ./0
172.154.658.251
g700
205
none
p
RecRule
The RecRule field displays the auto-fallback recovery rule that is associated with the media
gateway.
For more information, see the System Parameters Media Gateway Automatic Recovery Rule
screen and the Media-Gateway screen.
Reg?
The Reg? field displays the registration status of the media gateway. A new value, p, appears
during a pending registration state.
Issue 1.1 June 2006
167
New and changed screens
Optional Features
Note:
There are numerous changes to the Optional Features screen for
Communication Manager release 3.0. The changes are all listed here, by page.
The information also mentions what feature prompted the change.
Note:
To view the Optional Features screen:
1. Type display system-parameters customer-options. Press Enter.
The system displays the Optional Features screen (Figure 79: Optional Features
screen on page 168).
Figure 79: Optional Features screen
display system-parameters customer-options
Page 1 of 10
OPTIONAL FEATURES
G3 Version: V13
Location: 1
Platform: 6
RFA System ID (SID): 1
RFA Module ID (MID): 1
Platform Maximum Ports:
Maximum Stations:
Maximum XMOBILE Stations:
Maximum Off-PBX Telephones - EC500:
Maximum Off-PBX Telephones OPS:
Maximum Off-PBX Telephones - SCCAN:
44000
36000
100
5
5
0
USED
9605
7807
1
1
3
0
(NOTE: You must logoff & logon to effect the permission changes.)
Page 1
●
A new field, Maximum Stations, is added to the Optional Features screen. This change
is prompted by the Station licensing feature. This field tracks station licenses only.
Customers can easily identify the number of station licenses on the system.
2. Click Next until you see page 2 (Figure 80: Optional Features screen on page 169).
168 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Figure 80: Optional Features screen
display system-parameters customer-options
Page 2 of 10
OPTIONAL FEATURES
IP PORT CAPACITIES
Maximum Administered H.323 Trunks:
Maximum Administered IP Trunks:
Maximum Concurrently Registered IP Stations:
Maximum Administered Remote Office Trunks:
Maximum Concurrently Registered Remote Office Stations:
Maximum Concurrently Registered IP eCons:
Max Concur Registered Unauthorized H.323 Staions:
Maximum Video Capable H.323 Stations:
Maximum Video Capable IP Softphones:
Maximum Administered SIP Trunks:
Maximum Number of DS1 Boards with Echo Cancellation:
Maximum TN2501 VAL Boards:
Maximum G250/G350/G700 VAL Sources:
TN2602 80-VoIP Channel Licenses:
TN2602 320-VoIP Channel Licenses:
1500
100
10
0
0
0
0
0
0
450
USED
419
96
10
0
0
0
0
0
0
20
0
1
0
20
4
0
0
0
12
3
Maximum Number of Expanded Meet-me Conference Ports: 50
0
(NOTE: You must logoff & logon to effect the permission changes.)
Page 2
●
The Maximum G250/G350/G700 VAL Sources is renamed to include the new G250
Media Gateway.
●
Two new fields, TN2602 80-VoIP Channel Licenses and TN2602 320-VoIP Channel
Licenses, are added. These changes are prompted by the new TN2602AP IP Media
Resource 320 circuit pack.
●
A new field, Maximum Number of Expanded Meet-me Conference Ports, is added. This
change is prompted by the Expanded Meet-me Conferencing feature.
3. Click Next until you see the Enterprise Survivable Server? field (Figure 81: Optional
Features screen on page 170).
Issue 1.1 June 2006
169
New and changed screens
Figure 81: Optional Features screen
display system-parameters customer-options
Page 4 of 10
OPTIONAL FEATURES
Emergency Access to Attendant?
Enable ’dadmin’ Login?
Enhanced Conferencing?
Enhanced EC500?
Enterprise Survivable Server?
Enterprise Wide Licensing?
ESS Administration?
Extended Cvg/Fwd Admin?
External Device Alarm Admin?
Five Port Networks Max Per MCC?
Flexible Billing?
Forced Entry of Account Codes?
Global Call Classification?
Hospitality (Basic)?
Hospitality (G3V3 Enhancements)?
IP Trunks?
y
y
y
y
n
n
y
y
y
n
n
n
y
y
y
y
IP Stations?
Internet Protocol (IP) PNC?
ISDN Feature Plus?
ISDN Network Call Redirection?
ISDN-BRI Trunks?
ISDN-PRI?
Local Survivable Processor?
Malicious Call Trace?
Media Encryption over IP?
Mode Code for Centralized Voice Mail?
Multifrequency Signaling? n
Multimedia Appl. Server Interface (MASI)? n
Multimedia Call Handling (Basic)? y
Multimedial Call Handling (Enhanced)y
IP Attendant Consoles? y
(NOTE: You must logoff & logon to effect the permission changes.)
Page 4
Two new fields, Enterprise Survivable Server? and ESS Administration?, are added to the
Optional Features screen. This change is prompted by the Enterprise Survivable Servers
feature.
Field descriptions
For the main server:
●
Make sure that the Enterprise Survivable Server? field is set to n.
●
Make sure that the ESS Administration? field is set to y.
For each Enterprise Survivable Server:
●
Make sure that the Enterprise Survivable Server? field is set to y.
●
Make sure that the ESS Administration? field is set to y.
For a complete set of screens that apply to ESS, see the Avaya Enterprise Survivable Server
(ESS) Users Guide, 03-300428.
170 What’s New in Avaya Communication Manager
y
n
y
n
y
y
n
y
y
n
Release 3.0 changed screens
Port Information
The IP address of an IP telephone that is in TTI service appears in the Identification field on
the Port Information screen. This change is prompted by the Emergency calls from unnamed
IP endpoints feature.
To view the Port Information screen:
1. Type display port n, where n is the port number. Press Enter.
The system displays the Port Information screen (Figure 82: Port Information screen on
page 171).
Figure 82: Port Information screen
display port s00001
PORT INFORMATION
Port: S00001
Equipment Type: TTI port
Identification: 172.22.22.122
Security-Related System Parameters
A new field, Receive Unencrypted from IP Endpoints?, is added to the Security-Related
System Parameters screen. This change is prompted by the Security of IP telephone
registration/H.323 signaling channel feature.
To view the Security-Related System Parameters screen:
1. Type change system-parameters security. Press Enter.
The system displays the Security-Related System Parameters screen.
2. Click Next until you see the Receive Unencrypted from IP Endpoints? field
(Figure 83: Security-Related System Parameters screen on page 172).
Issue 1.1 June 2006
171
New and changed screens
Figure 83: Security-Related System Parameters screen
change system-parameters security
Page 2 of 2
Security-Related System Parameters
SECURITY VIOLATION NOTIFICATION PARAMETERS
SVN Station Security Code Violation Notification Enabled? n
STATION SECURITY CODE VERIFICATION PARAMETERS
Minimum Station Security Code Length: 4
Station Security Code for Terminal Self-Administration Required? Y
Receive Unencrypted from IP Endpoints? n
Field descriptions
The system can transmit the user PIN in the clear for IP telephones that do not support
encryption. System administrators have the option to enable or disable this capability.
System Capacity
Note:
Note:
There are numerous changes to the System Capacity screen for
Communication Manager release 3.0. The changes are all listed here, by page.
The information also mentions what feature prompted the change.
To view the System Capacity screen:
1. Type display capacity. Press Enter.
The system displays the System Capacity screen.
2. Click Next until you see the TN2602 80-VoIP Channel Licenses field (Figure 84: System
Capacity screen on page 173).
172 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Figure 84: System Capacity screen
display capacity
Page 6 of 12
SYSTEM CAPACITY
Recorded Announcement Analog Queue Slots:
TN2501 VAL Boards:
G700 VAL Sources:
TN2602 Boards with 80-VoIP Channels:
TN2602 Boards with 320-VoIP Channels:
TEMPORARY SIGNALING CONNECTIONS (TSC)
Administered TSCs:
NCA-TSC Calls:
Used Available Limit
----------------------0
1000
1000
0
0*
0
1
9
10
12
8
20
3
1
4
1
0
127
256
128
256
'*' Available VAL Boards limited by other inserted integ type annc boards
Page 6
Two new fields, TN2602 80-VoIP Channel Licenses and TN2602 320-VoIP Channel
Licenses, are added to the System Capacity screen. These display-only fields indicate the
current usage, license limit, and available 80-VoIP and 320-VoIP channel license capacities
that are associated with the system. This change is prompted by the TN2602AP IP Media
Resource 320 circuit pack.
3. Click Next until you see the Concurrent Registration Counts area (Figure 85: System
Capacity screen on page 173).
Figure 85: System Capacity screen
display capacity
Page 10 of 12
SYSTEM CAPACITY
CONCURRENT REGISTRATION COUNTS
IP Stations:
IP Stations in TTI State:
IP Attendant Consoles:
Remote Office Stations:
Currently
System
Registered Available Limit
----------------------------1009
4091
5100
0
0
1
1
3
997
1000
Issue 1.1 June 2006
173
New and changed screens
Page 10
A new field, IP Stations in TTI State, is added to the System Capacity screen. This change is
prompted by the Emergency calls from unnamed IP endpoints feature.
Vector Directory Number
Note:
Note:
There are numerous changes to the Vector Directory Number screen for
Communication Manager release 3.0. The changes are all listed here, by page.
The information also mentions what feature prompted the change.
To view the Vector Directory Number screen:
1. Type change vdn n, where n is a valid vector directory number. Press Enter.
The system displays the Vector Directory Number screen (Figure 86: Vector Directory
Number screen on page 174).
Figure 86: Vector Directory Number screen
change vdn 5000
Page 1 of x
VECTOR DIRECTORY NUMBER
Extension:
Name:
Vector Number:
Attendant Vectoring:
Meet-me Conferencing?
Allow VDN Override?
COR:
TN:
Measured:
Acceptable Service Level (sec):
VDN of Origin Annc. Extension:
1st Skill:
2nd Skill:
3rd Skill:
174 What’s New in Avaya Communication Manager
5000
234
n
n
n
59
1
none
301
Release 3.0 changed screens
Page 1
A new field, Meet-me Conferencing?, is added to the Vector Directory Number screen. This
change is prompted by the Expanded Meet-me Conferencing feature.
The Meet-me Conferencing? field appears only if the Enhanced Conferencing field is set to y
on the Optional Features screen. This field determines if the VDN is a Meet-me Conferencing
VDN.
Note:
Note:
If the VDN extension is part of your DID block, external users can access the
conference VDN. If the VDN extension is not part of your DID block, only internal
callers on the your network (including DCS or QSIG) or remote access callers
can access the conference VDN.
Valid entries
Usage
y/n
Enter y to enable Meet-me Conferencing for this VDN. If
Meet-me Conferencing is y, only Extension, Name,
Vector Number, Meet-me Conference, COR, and TN
fields display and the fields for page 2 change.
Both Attendant Vectoring and Meet-me Conferencing
cannot be enabled at the same time.
If Enhanced Conferencing is y, but no other vectoring
options are enabled, only Meet-me Conferencing
vectors can be assigned.
2. Click Next until you see the Meet-me Conference Parameters area (Figure 87: Vector
Directory Number screen on page 175).
Figure 87: Vector Directory Number screen
change vdn 5000
Page 2 of x
VECTOR DIRECTORY NUMBER
MEET-ME CONFERENCE PARAMETERS
Conference Access Code:123456
Conference Controller:
Conference Type: expanded
Route-to Number:
Issue 1.1 June 2006
175
New and changed screens
Page 2
Conference Access Code
To ensure conference security, you should always assign an access code to a Meet-me
Conferencing VDN.
Valid entries
Usage
6-digit number or
blank
Enter a 6-digit access code for the Meet-me Conferencing VDN. If you do
not want an access code, leave blank.
Once an access code is assigned, an asterisk displays in this field for
subsequent change, display, or remove operations by all users except the
"init" superuser login.
Conference Controller
This field controls which user is allowed to change the access code for a Meet-me Conferencing
VDN using a feature access code. This can be a local user or someone dialing in through
remote access trunks.
Valid entries
Usage
extension
number or blank
If an extension number is entered, only a user at that
extension can change the access code for that VDN
using a feature access code.
If this field is blank, any station user that is assigned
with console permissions can change the access code
for that VDN using a feature access code.
Conference Type
Use this field to select the conference type that is appropriate for your call. For six or fewer
participants, enter 6-party. For a conference with more than six participants, select expanded.
Valid entries
Usage
6-party or
expanded
Type expanded to enable the Expanded Meet-me
Conferencing feature. The default is 6-party.
176 What’s New in Avaya Communication Manager
Release 3.0 changed screens
Route-to Number
The Route-to Number field appears only if the Conference Type field is expanded. This field
allows administration of the routing digits (the ARS/AAR Feature Access Code with the routing
digits and the Conference ID digits for the VDN).
Valid entries
Usage
up to 16 digits
Enter the ARS or AAR Feature Access Code (FAC)
followed by the routing digits. Or you can enter the
unique UDP extension.
The Route-to Number must be unique across all
Expanded Meet-me Conferencing VDNs.
Issue 1.1 June 2006
177
New and changed screens
178 What’s New in Avaya Communication Manager
Chapter 4: New and changed commands
This chapter displays the new and changed commands for Avaya Communication Manager.
Release 3.1 new commands
Avaya Communication Manager, release 3.1, includes the following new commands.
add off-pbx-telephone station-mapping
A new command, add off-pbx-telephone, displays a new screen, Stations with Off-PBX
Telephone Integration. For more information, see the Stations with Off-PBX Telephone
Integration on page 127.
Valid parameters
Action
Object
Qualifier
add
off-pbx-telephone
station-mapping
change
off-pbx-telephone
station-mapping
<station extension>
display
off-pbx-telephone
station-mapping
<station extension>
list
off-pbx-telephone
station-mapping
<variable>
●
The add off-pbx-telephone station-mapping command displays the blank
Stations with Off-PBX Integration screens. You can add up to sixteen associations
between an office phone and an external phone.
●
The change off-pbx-telephone station-mapping <station extension>
command displays the Stations with Off-PBX Integration screens. You can change the
associations between office telephones and external telephones. The first line on the
screen contains the information for the station extension that you entered as the command
variable. You can also add additional associations in this screen.
Issue 1.1 June 2006
179
New and changed commands
●
The display off-pbx-telephone station-mapping <station extension>
command displays the Stations with Off-PBX Integration screens. The <station
extension> variable is not mandatory These screens list up to sixteen entries, starting
with the station extension you entered as the command variable. If this extension is not
administered for an off-PBX, the display starts with the next administered off-PBX
extension in numerical order.
●
The list off-pbx-telephone station-mapping <variable> command
information about the association between an office phone and an off-PBX phone. The
command variable specifies the office phone number or numbers of interest. The
<variable> can be:
- a complete phone number
- a partial phone number followed by an asterisk, which is a “wildcard” character
- blank
Release 3.0 new commands
Avaya Communication Manager, release 3.0, includes the following new commands.
add audio-group
A new command, add audio-group n, where n is the audio group number, displays a new
screen, Audio Group. For more information, see the Audio Group on page 81. This change is
prompted by the Locally sourced announcements and music feature.
Valid parameters
Action
Object
Qualifier
add
audio-group
n | next
change
audio-group
n
remove
audio-group
n
display
audio-group
n | n to n
180 What’s New in Avaya Communication Manager
Release 3.0 new commands
add moh-analog-group
A new command, add moh-analog-group n, where n is the music-on-hold group number,
displays a new screen, MOH Group. For more information, see the MOH Group on page 83.
This change is prompted by the Locally sourced announcements and music feature.
Valid parameters
Action
Object
Qualifier
add
moh-analog-group
number n | next
change
moh-analog-group
number n
remove
moh-analog-group
number n
display
moh-analog-group
number n | to-number n
list
moh-analog-group
[1-Max] (number n |
(to-number n) | (count n)
change system-parameters mg-recovery-rule
A new command, change system-parameters mg-recovery-rule n, where n is the
recovery rule number, displays a new screen, System Parameters Media Gateway Automatic
Recovery Rule. For more information, see the System Parameters Media Gateway Automatic
Recovery Rule on page 85. This change is prompted by the Auto fallback to primary for H.248
media gateways feature.
display virtual-mac-address
A new command, display virtual-mac-address n, where n is the MAC address table
number, displays a new screen, Virtual MAC Addresses. For more information, see the Virtual
MAC Addresses on page 90. This change is prompted by the TN2602AP IP Media Resource
320 circuit pack.
Issue 1.1 June 2006
181
New and changed commands
enable filexfer
Two new commands, enable filexfer n and disable filexfer n, where n is the slot
location of a circuit pack, act as a toggle switch, and enable a file transfer protocol (ftp) session.
Note:
Note:
These commands are intended for use on the bearer 10/100 Ethernet port on the
back plane. These commands are not intended for use on the services port.
This change is prompted by the TN2602AP IP Media Resource 320 circuit pack.
Valid parameters
Action
Object
Qualifier
enable
filexfer
n
disable
filexfer
n
enable session
Two new commands, enable session and disable session <circit pack slot
location>, act as a toggle switch, and enable a telnet session.
Note:
Note:
These commands are intended for use on the bearer 10/100 Ethernet port on the
back plane. These commands are not intended for use on the services port.
This change is prompted by the TN2602AP IP Media Resource 320 circuit pack.
Valid parameters
Action
Object
enable
session
disable
session
182 What’s New in Avaya Communication Manager
Qualifier
<circit pack slot location>
Release 3.0 new commands
list audio-group
A new command, list audio-group, displays a new screen, Audio Groups. For more
information, see the Audio Groups on page 81. This change is prompted by the Locally sourced
announcements and music feature.
Valid parameters
Action
Object
list
audio-group
Qualifier
list ip-interface medpro
A new command, list ip-interface medpro, displays a new screen, IP Interfaces. For
more information, see the IP Interfaces on page 82. This change is prompted by the TN2602AP
IP Media Resource 320 circuit pack.
list moh-analog-group
A new command, list moh-analog-group, displays a new screen, Music-On-Hold
Groups. For more information, see the Music-on-Hold Groups on page 85. This change is
prompted by the Locally sourced announcements and music feature.
Valid parameters
Action
Object
list
audio-group
Qualifier
list tti-ip-stations
A new command, list tti-ip-stations, displays a new screen, TTI Service IP Stations.
This new screen lists IP telephones that are in TTI service. For more information, see the TTI
Service IP Stations on page 90. This change is prompted by the Emergency calls from
unnamed IP endpoints feature.
Issue 1.1 June 2006
183
New and changed commands
list usage integ-annc-board
A new command, list usage integ-annc-board n, where n is the 5-character circuit
pack location number, displays a new screen, Announcement Group Board Usage. This change
is prompted by the Locally sourced announcements and music feature.
Valid parameters
Action
Object
Qualifier
list
usage integ-annc-board
n
reset media-gateway
reset media-gateway [ n | all ] level [1 | 2 | 3 ]
Use the reset media-gateway command from the primary server to reset one or more
media gateways. This change is prompted by the Connection preserving failover/failback for
H.248 media gateways.
Action/Object
Qualifier
Qualifier Description
reset media-processor
n
The specific media gateway number to reset.
This command drops all connections to the
specified media gateway.
All registered media gateways. This
command drops all connections to all media
gateways.
The reset media-gateway level 1
command forces a reset of the entire
platform and is destructive to user
connections. The media gateway attempts to
register with the media gateway controllers
on its MGC list.
The reset media-gateway level 2
command resets the H.248 link and does not
tear-down calls. The media gateway
attempts to register with the media gateway
controllers on its MGC list. Use reset
media-gateway level 2 to force a
media gateway off of an LSP.
The reset media-gateway level 3
command resets all media modules and
tears down all calls.
all
level 1
level 2
level 3
184 What’s New in Avaya Communication Manager
Release 3.0 new commands
set media-processor
set media-processor location [ lock | unlock ] [ override ]
Use the set media-processor command to request a demand interchange of IP Media
Resource 320 circuit packs on duplicated circuit packs only. Use set media-processor
location lock to manually specify the active TN2602AP IP Media Resource 320 circuit pack
when duplicated TN2602AP circuit pack exist in a port network. For more information, see the
TTI Service IP Stations on page 90. This change is prompted by the TN2602AP IP Media
Resource 320 circuit pack.
Action/Object
Qualifier
Qualifier Description
set media-processor
location
lock
location of the Media Resource to be active
circuit packs remain in their current state (active or
standby)
clear the locked state
force an interchange to a less-healthy board
unlock
override
When the set media-processor command does not produce an interchange, an error
message appears.
SAT error message
Description
Command only supported by a
TN2602AP and greater board
The board location specified is not a TN2602 IP Media
Resource. Use list config to verify the TN code and
identify the board in this location.
Duplication not administered for
this media-processor
This IP Media Resource is not administered as a
duplicated board. Use display ip-interface to
verify administration of the board.
Invalid duplication state for this
media-processor pair
This pair of duplicated IP Media Resources has not
transitioned to a state where one is active and one is
standby. Use status media-processor to verify the
duplication status of the IP Media Resources.
Standby media-processor is not
refreshed; use “override”
The standby IP Media Resource does not have the
same set of calls up as the active board. An interchange
making the standby active would cause a loss of some
or all of the calls. Use set media-processor
location override to ignore the warning and
continue the interchange.
Issue 1.1 June 2006
185
New and changed commands
Release 3.1 changed commands
Avaya Communication Manager, release 3.1, includes the following changed commands.
change public-unknown-numbering
change public-unknown-numbering n [ext-digits]
Use the change public-unknown-numbering n command to administer the desired digits
for name and number display on display-equipped stations in an ISDN network.
Action/Object
Qualifier
Qualifier Description
change
public-unknownnumbering
n
Number of digits (extension length, Ex -Len) in the
extension being administered.
Enter 0 for attendant.
extdigits
Displays the first extension on the screen.
Example:
change public-unknown-numbering 5
change public-unknown-numbering 5 ext-digits
10010
See Administrator Guide for Avaya Communication Manager, 03-300509, for a screen example
and field descriptions, and for more information on ISDN Call Identification Display and
Numbering-Public/Unknown.
list registered-ip-stations
The list registered-ip-stations command has a new option, count n, where n is a
number of extensions that you want to list.
When used with the ext option, the system administrator can now list IP telephones within a
specific range and “count” a specific number of consecutive extensions from that beginning
number. Previously, the user had to list all registered IP telephones and scroll until the user
found the range of extensions.
For example, if you want to list three consecutive registered IP endpoints beginning with
extension 1000000, type list registered-ip-stations ext 1000000 count 3. The
system displays information on the Registered IP Stations screen (Figure 88: Registered IP
Stations screen on page 187):
186 What’s New in Avaya Communication Manager
Release 3.0 changed commands
Figure 88: Registered IP Stations screen
list registered-ip-stations ext 1000000 count 3
REGISTERED IP STATIONS
Station
Ext
1000000
1000001
1000001
1000002
1000002
Set
Type
MDW9000
MDW9000
MDW9000
8434D
8434D
Product
ID
1234567890
1234567890
2222222222
1212121212
2222222222
Prod
Rel
9.123
9.123
2.222
8.888
2.222
Station
IP Address
100.101.102.103
1.2.3.4
2.2.2.2
5.6.7.8
2.2.2.2
Net
Rgn
250
1
1
2
2
Orig
Gatekeeper
TCP
Port
IP Address
Skt
01A0404 123.124.125.126 y
16.17.18.19
y
32.33.34.35
n
250V101 16.17.18.21
n
250V101 32.33.34.35
y
Release 3.0 changed commands
Avaya Communication Manager, release 3.0, includes the following changed commands.
get boot-image
The system now recognizes a Code type of TN2602AP to support the TN2602AP IP Media
Resource 320 circuit pack.
reset ip-stations
The reset ip-stations command has a new option, tti. The complete command is now:
reset ip-stations [ip-phones | all | tti] [network-region(1-250) |
all-regions].
The system administrator can use the reset ip-stations tti command to unregister
IP telephones that are in TTI service without unregistering other IP telephones. This change is
prompted by the Emergency calls from unnamed IP endpoints feature.
Issue 1.1 June 2006
187
New and changed commands
set boot-image
The system now recognizes a Code type of TN2602AP to support the TN2602AP IP Media
Resource 320 circuit pack.
status ip-board
The system now recognizes and provides status for a TN2602AP circuit pack. This change is
prompted by the TN2602AP IP Media Resource 320 circuit pack.
status media-processor
The system now recognizes the argument all to display all media processor circuit packs in a
system. This change is prompted by the TN2602AP IP Media Resource 320 circuit pack.
188 What’s New in Avaya Communication Manager
Index
Index
Numerical
4621SW IP telephone .
4622SW IP telephone .
4625SW IP telephone .
802.1x multi supplicants
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
64
64
65
20
Adjunct Switch Application Interface (ASAI) . . . . .
administrable Periodic Registration Timer . . . . . .
administrable size for Receive Buffer TCP Window . .
administrable time-out for inactive SAT sessions . . .
AE Services, see Application Enablement Services
(AE Services)
alarm log entries for MG-ICC . . . . . . . . . . . .
alarm messages for unregistered LSPs . . . . . . .
analog bearer frequency for IP encoding . . . . . .
Application Enablement Services (AE Services) . . .
Adjunct Switch Application Interface (ASAI) . . .
bundled server option . . . . . . . . . . . . . .
CVLAN. . . . . . . . . . . . . . . . . . . . .
DEFINITY LAN Gateway (DLG) . . . . . . . . .
software-only option . . . . . . . . . . . . . .
System Management Service (SMS) . . . . . . .
Telephony Service (TS) . . . . . . . . . . . . .
User Service . . . . . . . . . . . . . . . . . .
ASAI support for Aux Work reason codes . . . . . .
ASAI, see Adjunct Switch Application Interface (ASAI)
auto fallback to primary for H.248 media gateways . .
Avaya Expanded Meet-me Conferencing Server . . .
Avaya Video Telephony Solution . . . . . . . . . .
43
42
20
21
A
42
21
42
42
43
43
43
44
43
44
44
44
21
45
65
21
B
banner displayed to warn of reset . . . . . .
bearer signal duplication on TN2602AP . . .
block circuit pack installation if wrong suffix .
block CMS Move Agent events . . . . . . .
button pushes in ‘list trace station’ command
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
22
26
22
23
46
C
Call Log modifications . . . . . . . . . . . . . . . 23
called number added to display for Toshiba SIP
telephone . . . . . . . . . . . . . . . . . . . . 17
Calling Identity Delivery on Call Waiting (CIDCW) . . 40
changed commands
release 3.0 . . . . . . . . . . . . . . . . .
get boot-image . . . . . . . . . . . . . .
reset ip-stations . . . . . . . . . . . . .
set boot-image . . . . . . . . . . . . . .
status ip-board . . . . . . . . . . . . . .
status media-processor . . . . . . . . . .
release 3.1 . . . . . . . . . . . . . . . . .
change public-unknown-numbering . . . .
list registered-ip-stations . . . . . . . . .
changed screens
release 3.0 . . . . . . . . . . . . . . . . .
Announcements/Audio Sources . . . . . .
Configuration Set. . . . . . . . . . . . .
Extensions to Call Which Activate Features
By Name . . . . . . . . . . . . . . . .
Feature Access Code (FAC) . . . . . . .
Feature-Related System Parameters . . .
Gateway Status . . . . . . . . . . . . .
Integrated Announcements/Audio . . . . .
IP Interfaces . . . . . . . . . . . . . . .
IP Network Region . . . . . . . . . . . .
IP-Options System Parameters . . . . . .
Language Translations . . . . . . . . . .
List Usage Report . . . . . . . . . . . .
Location Parameters . . . . . . . . . . .
Media-Gateway . . . . . . . . . . . . .
Media-Gateway Report . . . . . . . . . .
Optional Features . . . . . . . . . . . .
Port Information . . . . . . . . . . . . .
Security-Related System Parameters . . .
System Capacity . . . . . . . . . . . . .
Vector Directory Number . . . . . . . . .
release 3.1 . . . . . . . . . . . . . . . . .
Class of Restriction . . . . . . . . . . . .
Class of Service . . . . . . . . . . . . .
Console Parameters . . . . . . . . . . .
CTI Link . . . . . . . . . . . . . . . . .
Enterprise Survivable Server Information .
Feature Access Code (FAC) . . . . . . .
Feature-Related System Parameters . . .
Group Paging Using Speakerphone . . . .
Hunt Group . . . . . . . . . . . . . . .
IP Interfaces . . . . . . . . . . . . . . .
IP Network Region . . . . . . . . . . . .
IP Server Interface (IPSI) Administration . .
Language Translations . . . . . . . . . .
Media-Processor Status . . . . . . . . .
Optional Features . . . . . . . . . . . .
Route Pattern . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
187
187
187
188
188
188
186
186
186
. 144
. 144
. 145
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Issue 1.1 June 2006
146
147
148
153
154
154
158
161
163
164
164
165
167
168
171
171
172
174
. 95
. 95
. 97
. 98
. 99
101
102
104
112
113
114
117
119
120
121
122
123
189
Index
changed screens, release 3.1, (continued)
Security-Related System Parameters . . . . .124
Station . . . . . . . . . . . . . . . . . . .125
Stations with Off-PBX Telephone Integration . 127
Trunk Group . . . . . . . . . . . . . . . .132
Variables for Vectors. . . . . . . . . . . . .139
Vector Directory Number . . . . . . . . . . .142
release 3.1.X . . . . . . . . . . . . . . . . . . 91
Feature-Related System Parameters . . . . . 93
Trunk Group . . . . . . . . . . . . . . . . 94
CIDCW, see Calling Identity Delivery on Call Waiting
(CIDCW)
clear display of collected digits . . . . . . . . . . . 24
clearer display for trunk ID . . . . . . . . . . . . . 17
CNA, see Converged Network Analyzer (CNA)
comment on this book . . . . . . . . . . . . . . . 15
compress restart escalation sequence . . . . . . . . 24
connection preserving failover/failback for H.248
media gateways . . . . . . . . . . . . . . . . . 46
Connection Preserving Migration (CPM) . . . . . . . 46
connection preserving upgrades for duplex servers . 47
connection-preserving upgrades . . . . . . . . . . 24
conventions . . . . . . . . . . . . . . . . . . . . 12
Converged Network Analyzer (CNA) . . . . . . . . 65
CPM, see Connection Preserving Migration (CPM)
CVLAN . . . . . . . . . . . . . . . . . . . . . . 43
Enterprise Survivable Servers (ESS) . . . . . . .
Enterprise Wide Licensing (EWL) . . . . . . . .
ESLP, see Enhanced Software License Program
(ESLP)
ESS, see Enterprise Survivable Servers (ESS)
EWL, see Enterprise Wide Licensing (EWL)
Expanded Meet-me Conferencing . . . . . . . .
extended survivability to G250 Media Gateway . .
extension to cellular . . . . . . . . . . . . . .
. . 48
. . 49
. . 49
. . 29
. . 49
F
faster backups . . . . . . . . . . . . . . . . . . . 18
G
G250 DCP Media Gateway . . . . .
G250 DS1 Media Gateway . . . . .
G250 Media Gateway . . . . . . . .
G250-Analog . . . . . . . . . .
G250-BRI . . . . . . . . . . . .
Standard Local Survivability (SLS)
G350 Media Gateway as HQ device .
gateway trunk preference selection .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
60
60
66
66
66
67
59
30
H
D
DEFINITY LAN Gateway (DLG) . . . . . . . . .
detecting 655A power supply failures . . . . . .
dial backup over external ISDN modem . . . . .
direct-region preference for IP telephones . . . .
disable active logins . . . . . . . . . . . . . .
display for bridged no-ring calls . . . . . . . . .
DLG, see DEFINITY LAN Gateway (DLG)
DNS Resolver for gateways . . . . . . . . . .
duplicate power supply failure upgraded to alarm
status . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
44
24
24
25
47
47
. . 66
. . 25
E
e-mail backups no longer supported . . . . . . .
emergency calls from unnamed IP endpoints . .
EMU, see Enterprise Mobility User (EMU)
endpoints, see telephones
enhanced feature integrations for Avaya Modular
Messaging . . . . . . . . . . . . . . . . . .
enhanced list measurement occupancy command
for duplicated servers . . . . . . . . . . . . .
enhanced password security . . . . . . . . . .
enhanced quality for Music On Hold . . . . . . .
Enhanced Software License Program (ESLP) . .
enhanced TN2602AP circuit pack . . . . . . . .
Enterprise Mobility User (EMU) . . . . . . . . .
Enterprise Survivable Server increase . . . . . .
. . 47
. . 48
. . 25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
25
48
49
26
28
29
190 What’s New in Avaya Communication Manager
HDMM for G350 Media Gateway . . . . . . . . . . 61
help, numbers to call . . . . . . . . . . . . . . . . 15
HTTP server on S8500 Media Server . . . . . . . . 30
I
IGAR, see Inter-Gateway Alternate Routing (IGAR)
improved button downloads for IP telephones . . .
improved voice mail coverage at WAN failure. . . .
increased Classes of Restriction . . . . . . . . . .
increased packet size supported . . . . . . . . . .
increased quantity of NCA TSCs and FTSCs . . . .
increased text fields for feature buttons . . . . . .
increased trunk members for IP signaling groups . .
incremental filesyncs . . . . . . . . . . . . . . .
integrating IP-connected port networks with direct/
multi-connect configurations . . . . . . . . . . .
Inter-Gateway Alternate Routing (IGAR) . . . . . .
Inter-Gateway Alternate Routing calls over
Inter-Gateway Connections . . . . . . . . . . .
.
.
.
.
.
.
.
.
50
50
30
51
30
30
31
31
. 51
. 52
. 31
L
list configuration by circuit pack . . . . . . .
list IP addresses for IP interface circuit packs .
listen-only FAC for service observing . . . .
load balancing on TN2602AP . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
52
32
27
Index
local ringback administration . . . . . . . . . . . . 32
locally sourced announcements and music . . . . . 52
M
manual Local Survivable Processor takeover . .
MLPP privileges at any endpoint . . . . . . . .
MM716 analog media module . . . . . . . . .
Modem over IP (MoIP) . . . . . . . . . . . . .
MoIP, see Modem over IP (MoIP)
more BRI Trunk circuit packs . . . . . . . . . .
more info from list survivable-processor command
more Leave Word Calling messages . . . . . .
more options for changing display messages . .
more simultaneous calls per multipoint endpoint .
more system-wide message retrieval extensions .
more than nine static routes allowed . . . . . .
multiple SNMP trap destinations . . . . . . . .
music on hold played from nearest source . . . .
.
.
.
.
.
.
.
.
18
53
61
53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
32
18
32
53
19
53
32
53
32
N
native support of NI-BRI data . . . . . . . . . . . . 54
new commands
change system-parameters mg-recovery-rule . . . 181
disable filexfer . . . . . . . . . . . . . . . . .182
disable session . . . . . . . . . . . . . . . . .182
display virtual-mac-address . . . . . . . . . . .181
enable filexfer . . . . . . . . . . . . . . . . .182
enable session . . . . . . . . . . . . . . . . .182
release 3.0 . . . . . . . . . . . . . . . . . . .180
add audio-group . . . . . . . . . . . . . . .180
add moh-analog-group . . . . . . . . . . . .181
list audio-group . . . . . . . . . . . . . . .183
list ip-interface medpro . . . . . . . . . . . .183
list moh-analog-group . . . . . . . . . . . .183
list tti-ip-stations . . . . . . . . . . . . . . .183
list usage integ-annc-board. . . . . . . . . .184
reset media-gateway. . . . . . . . . . . . .184
set media-processor . . . . . . . . . . . . .185
release 3.1 . . . . . . . . . . . . . . . . . . .179
add off-pbx-telephone station-mapping . . . .179
new default backup time . . . . . . . . . . . . . . 19
new features and enhancements
release 3.0 . . . . . . . . . . . . . . . . . . . 42
Adjunct Switch Application Interface . . . . . 43
administrable Periodic Registration Timer . . . 42
alarm log entries for MG-ICC . . . . . . . . . 42
analog bearer frequency for IP encoding . . . 42
Application Enablement Services (AE Services) 42
bundled server option . . . . . . . . . . . 43
CVLAN . . . . . . . . . . . . . . . . . 43
software only option . . . . . . . . . . . 43
new features and enhancements, release 3.0, (continued)
ASAI support for Aux Work reason codes . . . 21
auto fallback to primary for H.248 media
gateways . . . . . . . . . . . . . . . . . . 45
button pushes in ‘list trace station’ command . . 46
connection preserving failover/failback for
H.248 media gateways . . . . . . . . . . . 46
connection preserving upgrades for duplex
servers . . . . . . . . . . . . . . . . . . . 47
DEFINITY LAN Gateway . . . . . . . . . . . 44
device and media control API . . . . . . . . . 44
disable active logins . . . . . . . . . . . . . 47
display for bridged no-ring calls . . . . . . . . 47
e-mail backups no longer supported . . . . . . 47
emergency calls from unnamed IP endpoints. . 48
enhanced quality for Music On Hold . . . . . . 48
Enterprise Survivable Servers (ESS) . . . . . 48
Enterprise Wide Licensing (EWL) . . . . . . . 49
Expanded Meet-me Conferencing . . . . . . . 49
extension to cellular . . . . . . . . . . . . . 49
improved button downloads for IP telephones . 50
improved voice mail coverage at WAN failure . 50
increased packet size supported . . . . . . . 51
integrating IP-connected port networks with
direct/multi-connect configurations . . . . . . 51
Inter-Gateway Alternate Routing (IGAR) . . . . 52
list IP addresses for IP interface circuit packs . 52
locally sourced announcements and music . . . 52
MLPP privileges at any endpoint . . . . . . . 53
Modem over IP (MoIP) . . . . . . . . . . . . 53
more options for changing display messages. . 53
more system-wide message retrieval
extensions . . . . . . . . . . . . . . . . . 53
multiple SNMP trap destinations. . . . . . . . 53
native support of NI-BRI data . . . . . . . . . 54
prevent MLPP preemption of emergency calls . 54
QSIG support for Unicode . . . . . . . . . . 54
RAM disk for S8300 Media Server . . . . . . . 54
remove assigned DID . . . . . . . . . . . . 54
ringback during coverage interval . . . . . . . 55
Secure Shell and Secure FTP for circuit packs . 55
security of IP telephone registration/H.323
signaling channel . . . . . . . . . . . . . . 55
serial number for license validation . . . . . . 56
shorter time-out for ‘list trace ras’ command . . 56
station licensing . . . . . . . . . . . . . . . 56
user-defined phone message files . . . . . . . 57
Web interface from multiple IP addresses . . . 57
Web services
System Management Service . . . . . . . 44
Telephony Service . . . . . . . . . . . . 44
User Service . . . . . . . . . . . . . . . 44
Issue 1.1 June 2006
191
Index
new features and enhancements, (continued)
release 3.1 . . . . . . . . . . . . . . . . . . .
802.1x multi supplicants . . . . . . . . . . .
administrable size for Receive Buffer TCP
Window . . . . . . . . . . . . . . . . . .
administrable time-out for inactive SAT
sessions . . . . . . . . . . . . . . . . . .
alarm messages for unregistered LSPs . . . .
Avaya Video Telephony Solution . . . . . . .
banner displayed to warn of reset . . . . . . .
bearer signal duplication on TN2602AP . . . .
block circuit pack installation if wrong suffix . .
block CMS Move Agent events . . . . . . . .
Call Log modifications . . . . . . . . . . . .
clear display of collected digits . . . . . . . .
compress restart escalation sequence . . . .
connection-preserving upgrades . . . . . . .
detecting 655A power supply failures . . . . .
dial backup over external ISDN modem . . . .
direct-region preference for IP telephones . . .
duplicate power supply failure upgraded to
alarm status . . . . . . . . . . . . . . . .
enhanced feature integrations for Avaya
Modular Messaging . . . . . . . . . . . .
enhanced password security . . . . . . . . .
enhanced TN2602AP circuit pack. . . . . . .
Enterprise Mobility User (EMU) . . . . . . . .
Enterprise Survivable Server increase . . . .
extended survivability to G250 Media Gateway
gateway trunk preference selection . . . . . .
HTTP server on S8500 Media Server . . . . .
increased Classes of Restriction . . . . . . .
increased quantity of NCA TSCs and FTSCs .
increased text fields for feature buttons . . . .
increased trunk members for IP signaling
groups. . . . . . . . . . . . . . . . . . .
incremental filesyncs. . . . . . . . . . . . .
Inter-Gateway Alternate Routing calls over
Inter-Gateway Connections . . . . . . . . .
listen-only FAC for service observing . . . . .
load balancing on TN2602AP . . . . . . . .
local ringback administration . . . . . . . . .
more BRI Trunk circuit packs . . . . . . . . .
more Leave Word Calling messages . . . . .
more than nine static routes allowed . . . . .
music on hold played from nearest source. . .
notification about 802.1q changes . . . . . .
parameterized data for NSF . . . . . . . . .
prepend ’+’ to calling number . . . . . . . . .
Processor Ethernet (PE) . . . . . . . . . . .
QSIG path optimization simplified . . . . . . .
QSIG redirection display is administrable . . .
R2-MFC support on G250 Media Gateway . .
reduced channels with duplicated TN2602AP
circuit packs . . . . . . . . . . . . . . . .
remote upgrades for branch gateways . . . .
20
20
20
21
21
21
22
26
22
23
23
24
24
24
24
24
25
25
25
25
26
28
29
29
30
30
30
30
30
31
31
31
32
27
32
32
32
32
32
33
33
33
33
35
35
35
27
35
192 What’s New in Avaya Communication Manager
new features and enhancements, release 3.1, (continued)
rerouting and path replacement by trunk group . 36
reset IP stations by subnet enhancement . . . 36
Secure Shell and Secure FTP . . . . . . . . . 36
Secure Shell to retrieve backup information . . 37
security of IP telephone registration/H.323
signaling channel . . . . . . . . . . . . . . 37
shadowing data on servers . . . . . . . . . . 39
SIP Enablement Services (SES) . . . . . . . 40
site data warning when adding station to
TTI port . . . . . . . . . . . . . . . . . . 40
support caller ID on call waiting for MM711 and
MM714 . . . . . . . . . . . . . . . . . . . 40
support for Enterprise Linux . . . . . . . . . . 40
support of T.38 fax relay on TN2602AP . . . . 27
translations file timestamps . . . . . . . . . . 41
V.32 modem relay on TN2602AP . . . . . . . 28
Web firewall settings simplified . . . . . . . . 41
Web interface for synchronization plan. . . . . 41
Web upgrade tool checks file
corruption/presence . . . . . . . . . . . . . 41
Web upgrade tool common media module
option . . . . . . . . . . . . . . . . . . . 41
release 3.1.X . . . . . . . . . . . . . . . . . . 17
called number added to display for Toshiba
SIP telephone . . . . . . . . . . . . . . . 17
clearer display for trunk ID . . . . . . . . . . 17
enhanced list measurement occupancy
command for duplicated servers . . . . . . . 18
faster backups . . . . . . . . . . . . . . . . 18
list configuration by circuit pack . . . . . . . . 18
manual Local Survivable Processor takeover. . 18
more info from list survivable-processor
command . . . . . . . . . . . . . . . . . 18
more simultaneous calls per multipoint
endpoint . . . . . . . . . . . . . . . . . . 19
new default backup time . . . . . . . . . . . 19
new reason code for attendant vector . . . . . 19
notification about 802.1q changes . . . . . . . 19
prompt alarm for C-LAN outage . . . . . . . . 19
T.38 protocol for faxing . . . . . . . . . . . . 19
tildes to hide names in directory . . . . . . . . 20
new hardware
release 3.0 . . . . . . . . . . . . . . . . . . . 64
4621SW IP telephone . . . . . . . . . . . . 64
4622SW IP telephone . . . . . . . . . . . . 64
4625SW IP telephone . . . . . . . . . . . . 65
Avaya Expanded Meet-me Conferencing
Server . . . . . . . . . . . . . . . . . . . 65
Converged Network Analyzer (CNA) . . . . . . 65
DNS Resolver for gateways . . . . . . . . . . 66
G250 Media Gateway . . . . . . . . . . . . 66
SP-1020A SIP business telephone . . . . . . 68
TN2602AP IP Media Resource 320 circuit
pack . . . . . . . . . . . . . . . . . . . . 69
Index
new hardware, (continued)
release 3.1 . . . . . . . . . . . . . . . . . . .
G250 DCP Media Gateway. . . . . . . . . .
G250 DS1 Media Gateway . . . . . . . . . .
MM316 HDMM for G350 Media Gateway . . .
MM716 analog media module . . . . . . . .
S8400 Media Server . . . . . . . . . . . . .
S8720 Media Server . . . . . . . . . . . . .
software duplication on S8720 Media Server .
TN8412AP circuit pack . . . . . . . . . . . .
USB support for G250 Media Gateway . . . .
release 3.1.X . . . . . . . . . . . . . . . . . .
G350 Media Gateway as HQ device . . . . .
new reason code for attendant vector . . . . . . . .
new screens
release 3.0 . . . . . . . . . . . . . . . . . . .
Announcement Group Board Usage . . . . .
Audio Group . . . . . . . . . . . . . . . .
Audio Groups . . . . . . . . . . . . . . . .
IP Interfaces . . . . . . . . . . . . . . . .
MOH Group . . . . . . . . . . . . . . . . .
Music-On-Hold Groups . . . . . . . . . . .
System Parameters Media Gateway Automatic
Recovery Rule . . . . . . . . . . . . . . .
TTI Service IP Stations . . . . . . . . . . .
Virtual MAC Addresses . . . . . . . . . . .
release 3.1 . . . . . . . . . . . . . . . . . . .
Enable Session . . . . . . . . . . . . . . .
Survivable Processor . . . . . . . . . . . .
notification about 802.1q changes . . . . . . . . 19,
59
60
60
61
61
61
62
63
62
60
59
59
19
80
80
81
81
82
83
85
85
90
90
71
71
73
33
O
overview . . . . . . . . . . . . . . . . . . . . . 11
P
parameterized data for NSF . . . . . . . .
PE, see Processor Ethernet (PE)
perfect forward secrecy . . . . . . . . . .
prepend ’+’ to calling number . . . . . . . .
prevent MLPP preemption of emergency calls
Processor Ethernet (PE) . . . . . . . . . .
adjuncts . . . . . . . . . . . . . . . .
H.248 and H.323 registration . . . . . .
S8500 Media Servers . . . . . . . . . .
prompt alarm for C-LAN outage . . . . . . .
. . . . 33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
38
33
54
33
34
34
34
19
Q
QSIG path optimization simplified . . . . . . . . . . 35
QSIG redirection display is administrable . . . . . . 35
QSIG support for Unicode . . . . . . . . . . . . . 54
R
R2-MFC support on G250 Media Gateway . . . . .
RAM disk for S8300 Media Server . . . . . . . . .
redirect on OPTIM failure (ROOF) . . . . . . . . .
reduced channels with duplicated TN2602AP circuit
packs . . . . . . . . . . . . . . . . . . . . .
release 3.0
changed commands . . . . . . . . . . . . . .
get boot-image . . . . . . . . . . . . . . .
reset ip-stations . . . . . . . . . . . . . .
set boot-image . . . . . . . . . . . . . . .
status ip-board . . . . . . . . . . . . . . .
status media-processor . . . . . . . . . . .
changed screens . . . . . . . . . . . . . . .
Announcements/Audio Sources . . . . . . .
Configuration Set. . . . . . . . . . . . . .
Extensions to Call Which Activate Features
By Name . . . . . . . . . . . . . . . . .
Feature Access Code (FAC) . . . . . . . .
Feature-Related System Parameters . . . .
Gateway Status . . . . . . . . . . . . . .
Integrated Announcements/Audio . . . . . .
IP Interfaces . . . . . . . . . . . . . . . .
IP Network Region . . . . . . . . . . . . .
IP-Options System Parameters . . . . . . .
Language Translations . . . . . . . . . . .
List Usage Report . . . . . . . . . . . . .
Location Parameters . . . . . . . . . . . .
Media-Gateway . . . . . . . . . . . . . .
Media-Gateway Report . . . . . . . . . . .
Optional Features . . . . . . . . . . . . .
Port Information . . . . . . . . . . . . . .
Security-Related System Parameters . . . .
System Capacity . . . . . . . . . . . . . .
Vector Directory Number . . . . . . . . . .
new commands . . . . . . . . . . . . . . . .
add audio-group . . . . . . . . . . . . . .
add moh-analog-group . . . . . . . . . . .
change system-parameters mg-recovery-rule
disable filexfer . . . . . . . . . . . . . . .
disable session . . . . . . . . . . . . . .
display virtual-mac-address . . . . . . . . .
enable filexfer . . . . . . . . . . . . . . .
enable session . . . . . . . . . . . . . . .
list audio-group . . . . . . . . . . . . . .
list ip-interface medpro . . . . . . . . . . .
list moh-analog-group . . . . . . . . . . .
list tti-ip-stations . . . . . . . . . . . . . .
list usage integ-annc-board . . . . . . . . .
reset media-gateway . . . . . . . . . . . .
set media-processor . . . . . . . . . . . .
Issue 1.1 June 2006
. 35
. 54
. 50
. 27
187
187
187
188
188
188
144
144
145
146
147
148
153
154
154
158
161
163
164
164
165
167
168
171
171
172
174
180
180
181
181
182
182
181
182
182
183
183
183
183
184
184
185
193
Index
release 3.0, (continued)
new features and enhancements . . . . . . . .
Adjunct Switch Application Interface . . . . .
administrable Periodic Registration Timer . . .
alarm log entries for MG-ICC . . . . . . . . .
analog bearer frequency for IP encoding . . .
Application Enablement Services (AE Services)
bundled server option . . . . . . . . . . .
CVLAN . . . . . . . . . . . . . . . . .
software only option . . . . . . . . . . .
ASAI support for Aux Work reason codes . . .
auto fallback to primary for H.248 media
gateways . . . . . . . . . . . . . . . . .
button pushes in ‘list trace station’ command .
connection preserving failover/failback for
H.248 media gateways . . . . . . . . . . .
connection preserving upgrades for duplex
servers . . . . . . . . . . . . . . . . . .
DEFINITY LAN Gateway . . . . . . . . . . .
device and media control API
device and media control API . . . . . . .
disable active logins . . . . . . . . . . . . .
display for bridged no-ring calls . . . . . . . .
e-mail backups no longer supported . . . . .
emergency calls from unnamed IP endpoints .
enhanced quality for Music On Hold . . . . .
Enterprise Survivable Servers (ESS) . . . . .
Enterprise Wide Licensing (EWL) . . . . . . .
Expanded Meet-me Conferencing . . . . . .
extension to cellular . . . . . . . . . . . . .
improved button downloads for IP telephones .
improved voice mail coverage at WAN failure .
increased packet size supported . . . . . . .
integrating IP-connected port networks with
direct/multi-connect configurations . . . . .
Inter-Gateway Alternate Routing (IGAR) . . .
list IP addresses for IP interface circuit packs .
locally sourced announcements and music . .
MLPP privileges at any endpoint . . . . . . .
Modem over IP (MoIP) . . . . . . . . . . . .
more options for changing display messages .
more system-wide message retrieval
extensions . . . . . . . . . . . . . . . . .
multiple SNMP trap destinations . . . . . . .
native support of NI-BRI data . . . . . . . . .
prevent MLPP preemption of emergency calls .
QSIG support for Unicode . . . . . . . . . .
RAM disk for S8300 Media Server . . . . . .
remove assigned DID . . . . . . . . . . . .
ringback during coverage interval . . . . . . .
Secure Shell and Secure FTP for circuit packs
security of IP telephone registration/H.323
signaling channel . . . . . . . . . . . . .
serial number for license validation . . . . . .
shorter time-out for ‘list trace ras’ command . .
station licensing . . . . . . . . . . . . . . .
42
43
42
42
42
42
43
43
43
21
45
46
46
47
44
44
47
47
47
48
48
48
49
49
49
50
50
51
51
52
52
52
53
53
53
53
53
54
54
54
54
54
55
55
55
56
56
56
194 What’s New in Avaya Communication Manager
release 3.0, new features and enhancements, (continued)
user-defined phone message files . . . . . . . 57
Web interface from multiple IP addresses . . . 57
Web services
System Management Service . . . . . . . 44
Telephony Service . . . . . . . . . . . . 44
User Service . . . . . . . . . . . . . . . 44
new hardware . . . . . . . . . . . . . . . . . . 64
4621SW IP telephone . . . . . . . . . . . . 64
4622SW IP telephone . . . . . . . . . . . . 64
4625SW IP telephone . . . . . . . . . . . . 65
Avaya Expanded Meet-me Conferencing
Server . . . . . . . . . . . . . . . . . . . 65
Converged Network Analyzer (CNA) . . . . . . 65
DNS Resolver for gateways . . . . . . . . . . 66
G250 Media Gateway . . . . . . . . . . . . 66
SP-1020A SIP business telephone . . . . . . 68
TN2602AP IP Media Resource 320 circuit pack 69
new screens . . . . . . . . . . . . . . . . . . 80
Announcement Group Board Usage . . . . . . 80
Audio Group . . . . . . . . . . . . . . . . . 81
Audio Groups . . . . . . . . . . . . . . . . 81
IP Interfaces . . . . . . . . . . . . . . . . . 82
MOH Group . . . . . . . . . . . . . . . . . 83
Music-On-Hold Groups . . . . . . . . . . . . 85
System Parameters Media Gateway Automatic
Recovery Rule . . . . . . . . . . . . . . . 85
TTI Service IP Stations . . . . . . . . . . . . 90
Virtual MAC Addresses . . . . . . . . . . . . 90
release 3.1
changed commands . . . . . . . . . . . . . . 186
change public-unknown-numbering . . . . . 186
list registered-ip-stations . . . . . . . . . . 186
changed screens . . . . . . . . . . . . . . . . 95
Class of Restriction . . . . . . . . . . . . . . 95
Class of Service . . . . . . . . . . . . . . . 97
Console Parameters . . . . . . . . . . . . . 98
CTI Link . . . . . . . . . . . . . . . . . . . 99
Enterprise Survivable Server Information . . 101
Feature Access Code (FAC) . . . . . . . . 102
Feature-Related System Parameters . . . . 104
Group Paging Using Speakerphone . . . . . 112
Hunt Group . . . . . . . . . . . . . . . . 113
IP Interfaces . . . . . . . . . . . . . . . . 114
IP Network Region . . . . . . . . . . . . . 117
IP Server Interface (IPSI) Administration . . . 119
Language Translations . . . . . . . . . . . 120
Media-Processor Status . . . . . . . . . . 121
Optional Features . . . . . . . . . . . . . 122
Route Pattern . . . . . . . . . . . . . . . 123
Security-Related System Parameters . . . . 124
Station . . . . . . . . . . . . . . . . . . 125
Stations with Off-PBX Telephone Integration . 127
Trunk Group . . . . . . . . . . . . . . . . 132
Variables for Vectors . . . . . . . . . . . . 139
Vector Directory Number . . . . . . . . . . 142
Index
release 3.1, (continued)
new commands . . . . . . . . . . . . . . . . .179
add off-pbx-telephone station-mapping . . . .179
new features and enhancements . . . . . . . . 20
802.1x multi supplicants . . . . . . . . . . . 20
administrable size for Receive Buffer TCP
Window . . . . . . . . . . . . . . . . . . 20
administrable time-out for inactive SAT
sessions . . . . . . . . . . . . . . . . . . 21
alarm messages for unregistered LSPs . . . . 21
Avaya Video Telephony Solution . . . . . . . 21
banner displayed to warn of reset . . . . . . . 22
bearer signal duplication on TN2602AP . . . . 26
block circuit pack installation if wrong suffix . . 22
block CMS Move Agent events . . . . . . . . 23
Call Log modifications . . . . . . . . . . . . 23
clear display of collected digits . . . . . . . . 24
compress restart escalation sequence . . . . 24
connection-preserving upgrades . . . . . . . 24
detecting 655A power supply failures . . . . . 24
dial backup over external ISDN modem . . . . 24
direct-region preference for IP telephones . . . 25
duplicate power supply failure upgraded to
alarm status . . . . . . . . . . . . . . . . 25
enhanced feature integrations for Avaya
Modular Messaging . . . . . . . . . . . . 25
enhanced password security . . . . . . . . . 25
enhanced TN2602AP circuit pack. . . . . . . 26
Enterprise Mobility User (EMU) . . . . . . . . 28
Enterprise Survivable Server increase . . . . 29
extended survivability to G250 Media Gateway 29
gateway trunk preference selection . . . . . . 30
HTTP server on S8500 Media Server . . . . . 30
increased Classes of Restriction . . . . . . . 30
increased quantity of NCA TSCs and FTSCs . 30
increased text fields for feature buttons . . . . 30
increased trunk members for IP signaling
groups. . . . . . . . . . . . . . . . . . . 31
incremental filesyncs. . . . . . . . . . . . . 31
Inter-Gateway Alternate Routing calls over
Inter-Gateway Connections . . . . . . . . . 31
listen-only FAC for service observing . . . . . 32
load balancing on TN2602AP . . . . . . . . 27
local ringback administration . . . . . . . . . 32
more BRI Trunk circuit packs . . . . . . . . . 32
more Leave Word Calling messages . . . . . 32
more than nine static routes allowed . . . . . 32
music on hold played from nearest source. . . 32
notification about 802.1q changes . . . . . . 33
parameterized data for NSF . . . . . . . . . 33
prepend ’+’ to calling number . . . . . . . . . 33
Processor Ethernet (PE) . . . . . . . . . . . 33
QSIG path optimization simplified . . . . . . . 35
QSIG redirection display is administrable . . . 35
R2-MFC support on G250 Media Gateway . . 35
reduced channels with duplicated TN2602AP
circuit packs . . . . . . . . . . . . . . . . 27
release 3.1, new features and enhancements, (continued)
remote upgrades for branch gateways . . . . . 35
rerouting and path replacement by trunk group . 36
reset IP stations by subnet enhancement . . . 36
Secure Shell and Secure FTP . . . . . . . . . 36
Secure Shell to retrieve backup information . . 37
security of IP telephone registration/H.323
signaling channel . . . . . . . . . . . . . . 37
shadowing data on servers . . . . . . . . . . 39
SIP Enablement Services (SES) . . . . . . . 40
site data warning when adding station to
TTI port . . . . . . . . . . . . . . . . . . 40
support caller ID on call waiting for MM711
and MM714 . . . . . . . . . . . . . . . . 40
support for Enterprise Linux . . . . . . . . . . 40
support of T.38 fax relay on TN2602AP . . . . 27
translations file timestamps . . . . . . . . . . 41
V.32 modem relay on TN2602AP . . . . . . . 28
Web firewall settings simplified . . . . . . . . 41
Web interface for synchronization plan. . . . . 41
Web upgrade tool checks file
corruption/presence . . . . . . . . . . . . . 41
Web upgrade tool common media module
option . . . . . . . . . . . . . . . . . . . 41
new hardware . . . . . . . . . . . . . . . . . . 59
G250 DCP Media Gateway . . . . . . . . . . 60
G250 DS1 Media Gateway . . . . . . . . . . 60
MM316 HDMM for G350 Media Gateway . . . 61
MM716 analog media module . . . . . . . . . 61
S8400 Media Server . . . . . . . . . . . . . 61
S8720 Media Server . . . . . . . . . . . . . 62
software duplication on S8720 Media Server . . 63
TN8412AP circuit pack . . . . . . . . . . . . 62
USB support for G250 Media Gateway . . . . 60
new screens . . . . . . . . . . . . . . . . . . 71
Enable Session . . . . . . . . . . . . . . . 71
Survivable Processor . . . . . . . . . . . . . 73
release 3.1.X
changed screens . . . . . . . . . . . . . . . . 91
Feature-Related System Parameters . . . . . 93
Trunk Group . . . . . . . . . . . . . . . . . 94
new features and enhancements . . . . . . . . . 17
called number added to display for Toshiba
SIP telephone . . . . . . . . . . . . . . . 17
clearer display for trunk ID . . . . . . . . . . 17
enhanced list measurement occupancy
command for duplicated servers . . . . . . . 18
faster backups . . . . . . . . . . . . . . . . 18
list configuration by circuit pack . . . . . . . . 18
manual Local Survivable Processor takeover. . 18
more info from list survivable-processor
command . . . . . . . . . . . . . . . . . 18
more simultaneous calls per multipoint
endpoint . . . . . . . . . . . . . . . . . . 19
new default backup time . . . . . . . . . . . 19
new reason code for attendant vector . . . . . 19
notification about 802.1q changes . . . . . . . 19
Issue 1.1 June 2006
195
Index
release 3.1.X, new features and enhancements, (continued)
prompt alarm for C-LAN outage . . . . . . . 19
T.38 protocol for faxing . . . . . . . . . . . 19
tildes to hide names in directory . . . . . . . 20
new hardware . . . . . . . . . . . . . . . . . 59
G350 Media Gateway as HQ device . . . . . 59
remote upgrades for branch gateways. . . . . . . . 35
remove assigned DID . . . . . . . . . . . . . . . 54
rerouting and path replacement by trunk group. . . . 36
reset IP stations by subnet enhancement . . . . . . 36
ringback during coverage interval . . . . . . . . . . 55
ROOF, see redirect on OPTIM failure (ROOF)
T
T.38 protocol for faxing . . . . . . . . . . . . .
telephones, use of . . . . . . . . . . . . . . .
terms and conventions . . . . . . . . . . . . .
tildes to hide names in directory . . . . . . . . .
TN2602AP IP Media Resource 320 circuit pack .
TN8412AP circuit pack . . . . . . . . . . . . .
Toshiba SIP handset, see SP-1020A SIP business
telephone
trademarks . . . . . . . . . . . . . . . . . . .
translations file timestamps . . . . . . . . . . .
TS, see Web services, Telephony Service (TS)
.
.
.
.
.
.
.
.
.
.
.
.
19
12
12
20
69
62
. . 14
. . 41
S
S8400 Media Server . . . . . . . . . . . . . . . . 61
S8720 Media Server . . . . . . . . . . . . . . . . 62
SAFE, see self administration feature access code
(SAFE)
Secure Shell and Secure FTP . . . . . . . . . . . 36
Secure Shell and Secure FTP for circuit packs . . . . 55
Secure Shell to retrieve backup information . . . . . 37
security of IP telephone registration/H.323 signaling
channel . . . . . . . . . . . . . . . . . . . 37, 55
self administration feature access code (SAFE) . . . 49
serial number for license validation . . . . . . . . . 56
SES, see SIP Enablement Services (SES)
shadowing data on servers . . . . . . . . . . . . . 39
shorter time-out for ‘list trace ras’ command . . . . . 56
SIP Enablement Services (SES) . . . . . . . . . . 40
site data warning when adding station to TTI port . . 40
SLS, see G250 Media Gateway, Standard Local
Survivability (SLS)
SMS, see Web services, System Management Service
(SMS)
software duplication on S8720 Media Server . . . . . 63
SP-1020A SIP business telephone . . . . . . . . . 68
station licensing . . . . . . . . . . . . . . . . . . 56
stations, see telephones
strong shared secret . . . . . . . . . . . . . . . . 37
support caller ID on call waiting for MM711 and
MM714 . . . . . . . . . . . . . . . . . . . . . 40
support for Enterprise Linux . . . . . . . . . . . . 40
support of T.38 fax relay on TN2602AP . . . . . . . 27
196 What’s New in Avaya Communication Manager
U
USB support for G250 Media Gateway . . . . . . . . 60
user-defined phone message files . . . . . . . . . . 57
V
V.32 modem relay on TN2602AP . . . . . . . . . . 28
voice terminals, see telephones
W
Web firewall settings simplified . . . . . . . . .
Web interface for synchronization plan . . . . . .
Web interface from multiple IP addresses . . . .
Web services
System Management Service (SMS) . . . . .
Telephony Service (TS) . . . . . . . . . . .
User Service . . . . . . . . . . . . . . . .
Web upgrade tool checks file corruption/presence
Web upgrade tool common media module option .
. . 41
. . 41
. . 57
.
.
.
.
.
.
.
.
.
.
44
44
44
41
41
Download PDF
Similar pages
What is Power over Ethernet(POE)?
Avaya Aura Communication Manager Maintenance and
Avaya 5V User's Manual
Avaya Aura® Messaging Administration, Maintenance
Avaya 12xx User's Manual
Avaya 4610SW User's Manual