IP Office Technical Bulletin
Bulletin no:
90
17th December 2007
Date:
Title:
General Availability (GA) of IP Office 4.1
Software
Page 1 of 74
COMPAS ID 132759 Issue 1
IP Office Technical Bulletin number 90
Table of Contents
1
Product Overview......................................................................................................................... 4
2
IP Office Hardware ....................................................................................................................... 6
2.1
IP500 Universal PRI Daughter Card (not available in all territories)............. 6
2.2
New IP500 Expansion Modules................................................................... 8
2.3
New 3641 and 3645 IP Wireless (WiFi) Phones ........................................ 10
2.4
Simplified IP DECT Licensing.................................................................... 12
3
IP Office Software Enhancements............................................................................................. 13
3.1
VPN Phone support in 4600 and 5600 Series IP Phones .......................... 13
3.2
Embedded Voicemail Enhancements........................................................ 17
3.3
Internal Twinning of Appearance Keys ...................................................... 20
3.4
Tagging on Incoming Call Routes ............................................................. 21
3.5
Time of Day and Date Routing of calls ...................................................... 21
3.6
Time Profile Support on Incoming Call Routes .......................................... 22
3.7
Queue Threshold Alert .............................................................................. 22
3.8
Security Enhancements ............................................................................ 23
3.8.1
Transport Layer Security (TLS).............................................................. 23
3.8.2
Enhanced Password Policy ................................................................... 29
3.8.3
Additional Manager Security Changes ................................................... 34
3.9
Syslog support .......................................................................................... 34
3.10
Disable Speakerphone .......................................................................... 34
3.11
Group Listen .......................................................................................... 35
3.12
Manager Start-Up Banner...................................................................... 35
3.13
Manager Warning Dialogue ................................................................... 36
3.14
LAN2 Interface on port 8 of the IP406v2 ................................................ 37
3.15
Force Feed in Headset Mode ................................................................ 38
3.16
Local Administration Enhancements ...................................................... 38
3.17
Avaya SIP for Branch ............................................................................ 38
3.18
Recording Enhancements...................................................................... 43
3.19
Abbreviated Ring ................................................................................... 43
3.20
TAPI Enhancements.............................................................................. 43
3.21
Enhanced Meet Me Conferencing.......................................................... 44
3.22
Extension Number / Base Extension Number Mergeable....................... 44
3.23
Small Community Networking on IP500................................................. 45
3.24
System Status Application Enhancements............................................. 45
4
IP Office Applications ................................................................................................................ 46
4.1
VoiceMail Pro ............................................................................................ 46
4.1.1
Call Transfer Announcements ............................................................... 46
4.1.2
Call Transfer Data Tagging.................................................................... 47
4.1.3
LIFO/FIFO Message Playback............................................................... 47
4.1.4
Queuing Enhancements ........................................................................ 47
4.1.5
Variable Routing Action ......................................................................... 48
4.1.6
Castelle Fax Server Support .................................................................. 49
4.1.7
Connection Tool .................................................................................... 49
4.2
Phone Manager Pro Telecommuter Mode................................................. 49
5
Windows Operating System Support ...................................................................................... 53
6
Issues Resolved in IP Office 4.1 Software ................................................................................ 54
7
Known Issues .............................................................................................................................. 57
8
Technical Notes ........................................................................................................................... 59
8.1
Upgrade Installation Notes ........................................................................ 59
8.2
IP Office 4.1 Admin Suite Upgrades .......................................................... 60
COMPAS ID 132759 Issue 1
Page 2 of 74
IP Office Technical Bulletin number 90
8.3
Core Software Upgrade Instructions.......................................................... 63
8.4
Unit Compatibility - Expansion Unit Interoperability ................................... 65
8.5
Phone Firmware Support .......................................................................... 65
8.6
IP DECT Firmware Support....................................................................... 65
8.7
VoiceMail Pro Software Upgrade Summary .............................................. 66
8.8
Upgrading from 2.1 / 3.0 / 3.1 VoiceMail Pro ............................................. 66
8.9
Upgrading from 3.2 / 4.0 VoiceMail Pro ..................................................... 70
8.10
IP Office User Applications Software Upgrade Summary....................... 71
8.11
Upgrading from 2.1 / 3.0 / 3.1 User Applications .................................... 72
8.12
Upgrading from 3.2 / 4.0 User Applications............................................ 72
8.13
Delta Server Upgrade ............................................................................ 73
9
Assistance..................................................................................................................................... 73
9.1
Documentation .......................................................................................... 73
9.2
Software.................................................................................................... 73
9.3
IP Office Technical Training ...................................................................... 74
COMPAS ID 132759 Issue 1
Page 3 of 74
IP Office Technical Bulletin number 90
IP Office Technical Bulletin
Bulletin No:
90
17th December 2007
Date:
Region:
GLOBAL
General Availability (GA) of IP Office 4.1 Software
Avaya is delighted to announce the launch and availability of IP Office 4.1 software.
IP Office is Avaya's Small and Medium Enterprise (SME) solution designed as a
global solution for customers with up to 360 extensions and 240 trunks.
1
Product Overview
The Avaya IP Office 4.1 software is the latest advancement in converged voice and
data technology from Avaya. IP Office combines high-end voice and data
applications, allowing the smallest of businesses to deliver cutting edge customer
service.
IP Office 4.1 is the entry-level software to support the following new hardware:
·
IP500 Universal PRI Daughter Card
·
New IP500 Expansion Modules
·
New 3641 and 3645 IP Wireless (WiFi) Phones
·
Simplified IP DECT Licensing
As well as increased reliability through improvements to the core system software, IP
Office 4.1 also supports the following new features:
IP Office Core Software (Version 4.1.9)
VPN Phone support in 4600 and 5600 Series IP Phones
o
Embedded Voicemail Enhancements
o
Internal Twinning of Appearance Keys
o
Tagging on Incoming Call Routes
o
Time of Day and Date Routing of calls
o
Queue Threshold Alert
o
Security Enhancements
o
Syslog Support
o
Disable Speakerphone
o
Group Listen
o
Manager Start-up Banner
o
COMPAS ID 132759 Issue 1
Page 4 of 74
IP Office Technical Bulletin number 90
Manager Warning Dialogue
o
LAN2 Interface on port 8 of the IP406v2
o
Force Feed in Headset Mode
o
Local Administration Enhancements
o
Avaya SIP for Branch
o
Recording Enhancements
o
Abbreviated Ring
o
TAPI Enhancements
o
Enhanced Meet Me Conferencing
o
Extension/Base Extension Mergeable
o
Small Community Networking on IP500
o
System Status Application Enhancements
o
·
IP Office VoiceMail Pro (Version 4.1.27)
Call Transfer Announcements
o
Call Transfer Data Tagging
o
LIFO\FIFO Message Playback
o
Queuing Enhancements
o
Variable Routing Action
o
Castelle Fax Server Support
o
·
Phone Manager (Version 4.1.14)
Phone Manager Pro Telecommuter Mode
o
*************************************************************************************************
Note: IP Office 4.1 is not supported on the IP401, IP403, IP406v1 and early IP406v2
systems that only have 16mb of memory. If your IP406v2 unit does not meet the
minimum requirements then there is a procedure in place to enable you to upgrade
these units free of charge. Please refer to the Technical Notes section of this
document for further details.
*************************************************************************************************
COMPAS ID 132759 Issue 1
Page 5 of 74
IP Office Technical Bulletin number 90
2
IP Office Hardware
2.1
IP500 Universal PRI Daughter Card (not available in all territories)
IP Office 4.1 supports a new universal PRI daughter card for the IP500 hardware
platform. The daughter card is installed onto an IP500 base card (Phone, DS or VCM
but not the Legacy Card Carrier). The new card provides greater flexibility in
configuration owing to being a daughter card and therefore not taking up a slot in the
IP500 chassis as the Legacy Card Carrier does. Up to 4 IP500 universal PRI cards
can be installed into the system expanding the trunk capacity of the IP500 to a
maximum 240 E1 or 192 T1 channels.
The Universal PRI card is available in single and dual circuit varieties and supports
both T1 (1.544Mbps) and E1 (2.048Mbps), with DSP resources to support CAS
(Robbed bit and R2) signaling. For a Dual universal PRI card both circuits must be of
the same basic type: T1 or E1, E1 and E1R2. T1RBS and T1PRI may be mixed. The
card also offers protected test-points via RJ45 connectors to allow the monitoring of
the PRI line without disrupting the connection.
To provide lower pricing the channels on the Universal PRI card are licensed and will
initially support 8 channels per circuit without the need for a license key. Any
additional channels above this number will require a license key, available in 2 and 8
channel increments, to enable them. The Additional Channels license will specify the
number of channels that may be supported on circuits over and above the initial 8.
This licensing will not apply to IP400 PRI Trunk cards fitted to a Legacy Carrier Card.
Additional channels licenses are consumed by the number of configured channels on
each circuit, over and above the initial 8, starting from the first circuit (port number 9)
on the first card (number 1 - left hand side). Then onto the second circuit on that card
if it is a dual, then on to cards 2, 3 and 4. If a circuit has less than 8 channels
configured the difference between the number configured and 8 will not be added to
the additional channels count.
For a single Universal PRI card the line is connected on port 9 and the associated
monitoring port is port 11. For a dual Universal PRI card the lines are connected on
ports 9 and 10 with the associated monitoring ports being ports 11 and 12 (9
11,
10
12).
COMPAS ID 132759 Issue 1
Page 6 of 74
IP Office Technical Bulletin number 90
The LEDs on ports 9 and 10 act as Link state indicators and have the ability to show
connected, in use, AIS, and Loopback state, the same as IP400 PRI cards on a
Legacy Carrier Card.
st
nd
Link State
1 Circuit (LED 9)
2 Circuit (LED 10)
Link Detected
Green On
Green On
AIS
Red/Green Fast Flash
Green Fast Flash
In Use
Green Slow Flash
Green Slow Flash
Loopback
Red with Green Blink
Green Blink
No Link
Off
Off
The Line Type will default to T1 for IP Office systems with a U-Law Smart Card,
otherwise E1 will be the default. The Line Type (T1, E1 or E1R2) for the universal
PRI can be changed by a new option on the right click context menu when a
Universal PRI line is selected.
The IP Office Manager has been enhanced to indicate the Module and Socket/Port
number for each Line on the system. For example the first trunk on Card 2 is called
Line 5. In release 4.1 this is enhanced to include the physical address as printed on
the hardware; "Card 2, Port 9" similar to extensions.
This will apply for all physical Trunks, including:
·
IP400 trunk cards on legacy carriers.
·
IP400 trunk cards in IP400 control units.
·
Analogue Trunk 16 Expansion Modules.
COMPAS ID 132759 Issue 1
Page 7 of 74
IP Office Technical Bulletin number 90
A validation rule has also been added to Manager to produce an error if an IP Office
system has digital trunks without at least one having its Clock Quality set to
"Network". In order to have a stable synch source every system with digital trunks
should have one trunk set to supply synchronization.
IP500 Universal PRI Daughter Card Availability
Owing to the extended product approval processes, the IP500 Universal PRI
Daughter card may be delayed in the following countries: Argentina, Hong Kong,
India, Mexico, New Zealand and South Africa.
IP Office 500 hardware and license codes will not be orderable in these countries
until product approvals are complete. Please check with your local Avaya
representative for information about the IP500 Universal PRI availability. This does
NOT affect the availability of Release 4.1 software for existing platforms.
There are no plans to obtain product approvals for the IP500 Universal PRI cards in
the following countries: Brazil, Korea and Taiwan.
New IP500 Expansion Modules
2.2
Avaya has introduced new versions of the following IP Office expansion modules.
They are functionally identical to the existing IP400 versions but have been refreshed
in the look and feel of the IP500 (dark gray color) and require the IP500 rack
mounting kit. New modules:
·
IP500 DS 16
·
IP500 Phone 16
·
IP500 Analog Trunk 16 (North American version)
·
IP500 BRI So8
These new expansion modules work with IP406v2 and IP412 control units, as well as
the IP500.
COMPAS ID 132759 Issue 1
Page 8 of 74
IP Office Technical Bulletin number 90
Updated IP Office Control Unit Comparison
Feature
Small Office
IP406
IP412
IP500
Edition
V2
Digital Station (DS) Ports
0 or 8
8
0
Up to 24
Analog Phone (PHONE) Ports
2 or 4
2
0
Up to 32
Optional Embedded Voicemail Card
Slot
Integral WAN Ethernet Port (LAN 2)
Integral WAN Serial Port (X21/V35)
Expansion Ports
0
6
12
8
DTE Port
9-way
9-way
9-way
9-way
Audio In (MOH) Port
External O/P Switch Port
Conference Parties (max participants)
6
64
2 x 64
64
Maximum Extension Capacity
28
190
360
272
Digital (DS) Phones only
8
188
360
264
Analog Phones only
4
182
360
272
IP Phones only
16
190
360
272
IP400 Trunk Cards Supported
1
2
2
2*
Analog trunk cards
Quad BRI trunk cards
Single PRI trunk cards
(T1)
Dual PRI trunk cards
(Slot A only)
Serial WAN port card
IP500 Daughter Cards
0
0
0
4
IP500 Analog trunk card
IP500 BRI trunk card (4 or 8)
IP500 Universal PRI trunk card
VCM Cards
IP400 VCM Cards
1
2
2*
2
IP500 VCM Cards
Maximum
voice
compression
3 or 16
30
60
128
channels
Data Channels
18
40
100
48
Useable for Voicemail Pro/TAPI WAV
10
20
30
30
Dimensions
76x255x241mm
71x445x245mm
73x445x365mm
Height x Width x Depth
3"x10"x9.5"
2.8"x17.5"x9.7"
2.9"x17.5"x14.4"
- "supported"
- "not supported"
* Requires the IP500 Legacy Card Carrier
COMPAS ID 132759 Issue 1
Page 9 of 74
IP Office Technical Bulletin number 90
Material codes for the IP Office 500
The following table lists the new material codes for the IP500 Universal PRI Card,
Universal PRI additional channel licenses and new expansion modules.
Material Code
Description
700417439
IPO 500 TRNK PRI UNI SINGLE
700417462
IPO 500 TRNK PRI UNI DUAL
215180
IPO LIC IP500 T1 CHANNELS ADD 2
215181
IPO LIC IP500 T1 CHANNELS ADD 8
215182
IPO LIC IP500 T1 CHANNELS ADD 32
215183
IPO LIC IP500 E1 CHANNELS ADD 2
215184
IPO LIC IP500 E1 CHANNELS ADD 8
215185
IPO LIC IP500 E1 CHANNELS ADD 22
215186
IPO LIC IP500 E1R2 CHANNELS ADD 2
215187
IPO LIC IP500 E1R2 CHANNELS ADD 8
215188
IPO LIC IP500 E1R2 CHANNELS ADD 22
700449473
IPO 500 EXP MOD ANLG TRNK 16
700449499
IPO 500 EXP MOD DGTL STA 16
700449507
IPO 500 EXP MOD PHONE 16
700449515
IPO 500 EXP MOD BRI SO8
Note: For configurations using common channel signaling, the D-channel is always
enabled and does not consume a license. So the card by default supports 8 B-
channels plus one D-channel.
2.3
New 3641 and 3645 IP Wireless (WiFi) Phones
The new 3641 and 3645 IP wireless (WiFi) phones are supported on IP Office
Release 4.1 in all regions where available. Please contact your local Avaya
representative to establish local availability.
3641
3645
COMPAS ID 132759 Issue 1
Page 10 of 74
IP Office Technical Bulletin number 90
These handsets support the following:
·
128 x 96 backlit display with icons and line-status indicators
·
Standard Battery 4 hours talk time, 80 hours standby time
·
Optional Extended Battery 6 hours talk time, 120 hours standby time
·
Optional Ultra-Extended Battery 8 hours talk time, 160 hours standby time
·
802.11a, 802.11b, and 802.11g standard-compatible
·
Dust, shock and liquid damage resistant
·
Headset jack (2.5mm)
·
Speakerphone
·
Audible and vibrating alerting
·
Push-to-talk (3645 only)
Avaya WiFi telephony relies on special WiFi infrastructure that in combination with
the Avaya Voice Priority Processor can assure best of class Quality of Service and
battery run time. For details on supported infrastructure please go to:
http://www.spectralink.com/products/netlink/interfaces/wifi.jsp
A WiFi site survey should be done before installation to ensure sufficient network
coverage and to guarantee reliable functionality. If a technical ticket is raised against
these products Avaya Tier3 support will ask for the site survey results if any voice-
quality issues are raised. We recommend that the planning and installation team has
a deep understanding of WiFi infrastructure. Avaya recommends CWNA certification
or a similar level of expertise.
Please refer to: http://www.cwnp.com/cwna/ for more details.
The Avaya Wireless phones have received type approval in many regions. Currently
the 3641 and 3645 and the Classic phones have type approval in North America (US
and Canada) and Europe (all countries where the "CE" mark is recognized including
all of the EU).
The Classic phones in addition have type approval in some CALA and APAC
regions. APAC certification is in planning for the new 3641 and 3645 phones. Please
contact your Avaya representative to establish local availability if in doubt.
Material codes for the 3641 and 3645 phones are as follows:
Material Code
Description
700430408
AWTS 3641 WRLS PHONE
700430416
AWTS 3645 WRLS PHONE
AWTS 3641 Single Charger Bundle- includes
700436736
phone, standard battery and single charger
AWTS 3645 Single Charger Bundle- includes
700436744
phone, single charger and standard battery
AWTS 3641 Dual Charger Bundle- includes
700436751
phone, dual charger and two extended batteries
AWTS 3645 Dual Charger Bundle- includes
700436769
phone, dual charger and two extended batteries
Material codes for AVPPs, SMB Bundles, phones, power supplies, batteries,
chargers and accessories can be found in the IP Office Release 4.1 Product Update.
COMPAS ID 132759 Issue 1
Page 11 of 74
IP Office Technical Bulletin number 90
2.4
Simplified IP DECT Licensing
In IP Office 4.1, a new "Plug and Play Licensing" scheme for IP DECT is available. It
consists of a "Starter Kit" and "Upgrade Kits". Upgrade kits are pre-licensed IP DECT
base stations, making both first time installation and upgrades easier and more
flexible. Upgrade Kits will be available for both RFP 32 and RFP 34.
Installations start with a "Starter Kit" that includes:
·
a license key
·
two base stations
·
activation information
The "Starter Kit" can be expanded with the RFP32 and RFP34 Upgrade kits that
include the "built-in license", without the need to order any other upgrade licenses.
Once 8 upgrade kits have been added an unlimited license comes into effect (so
further unlicensed base stations can be added up to the maximum of 32 base
stations on the IP Office).
The current "Classic" license will stay available and can also be used going forward.
Upgrade kits can also be used with existing installations if they have been upgraded
to the latest ADMM software, currently this is version 1.1.9. It is possible to mix the
Classic License and the new licensing scheme.
This means there is no need ever to access the License server during installation. It's
easy to add a single base-station when required, no need to buy an upgrade license.
New material codes for the IP DECT Starter and Upgrade kits are as follows:
EMEA and APAC Starter Kit
Material Code
Description
700378995
IP DECT IPO BNDL 2 STR KIT LIC:CU
EMEA and APAC Upgrade Kits
Material Code
Description
700436561
IP DECT RFP32 UPG KIT INTL LIC:CU
700436587
IP DECT RFP34 UPG KIT INTL LIC:CU
North America Starter Kit
Material Code
Description
700436538
IP DECT IPO STARTER KIT NAR LIC:CU
North America Upgrade Kits
Material Code
Description
700436579
IP DECT RFP32 UPG KIT NAR LIC:CU
700436595
IP DECT RFP34 UPG KIT NAR LIC:CU
COMPAS ID 132759 Issue 1
Page 12 of 74
IP Office Technical Bulletin number 90
3
IP Office Software Enhancements
3.1
VPN Phone support in 4600 and 5600 Series IP Phones
IP Office Release 4.1 supports the connection of remote Avaya IP Phones over a
secure IPsec Virtual Private Network (VPN) without the need for a separate VPN
gateway at the remote location. The VPN phone uses a high-speed connection to the
Internet and then to the VPN solution in the corporate network. The VPN Phone is
compatible with the Avaya Security Gateway and with third-party security devices
using IKE Extended Authentication (Xauth) with Pre-shared Key.
A special version of the IP Phone firmware, which has the VPN client built-in, is used
to convert the phone into a remote VPN phone. Once downloaded to the IP phone all
of the same features and functions are available to the phone, the same as if it were
connected locally on the LAN to the IP Office.
The VPN phone feature is licensed on IP Office 4.1 with each VPN phone requiring a
license to enable it to register with the IP Office. A new checkbox, called "VPN
Phone Allowed", has been added to the Extension\VoIP configuration form for IP
Phones in the Manager application. This checkbox is greyed out until a valid VPN
Phone license has been loaded and once the number of VPN phones configured
matches the VPN IP Extension license value this checkbox will be greyed out again.
Note: This feature is only supported on the 4610, 4620, 4621, 5610, 5620 and 5621
telephones (not the 4625).
Supported Security Gateways
To create a successful VPN tunnel, the VPN phone must be capable of setting up an
IPsec tunnel between itself and a Security Gateway. The following SMB-targeted
VPN gateway devices are supported at launch:
·
Adtran Netvanta 3305 VPN Router
·
Kentrox Q2300 VPN Router
·
Netgear FVS338 VPN Router
·
SonicWALL TZ 170 SP Series
COMPAS ID 132759 Issue 1
Page 13 of 74
IP Office Technical Bulletin number 90
Application notes are available from http://support.avaya.com for the following VPN
gateways:
·
Global IP Office Technical Tip No. 184 - Configuring a VPN Remote IP
Phone with a Netgear FVS338 VPN Router
·
Global IP Office Technical Tip No. 185 - Configuring a VPN Remote IP
Phone with a Kentrox Q2300 VPN Router
·
Global IP Office Technical Tip No. 186 - Configuring a VPN Remote IP
Phone with an Adtran Netvanta 3305 VPN Router
·
Global IP Office Technical Tip No. 196 - Configuring a VPN Remote IP
Phone with a Sonicwall Tz170 Standard / Enhanced VPN Router
Note: These application notes were written for IP Office 4.0 software so they do not
show the "VPN Phone Allowed" checkbox option being selected where they cover the
required IP Office setup.
In addition, a number of enterprise class gateways have been tested and can also be
used:
Supported Device
Minimum Software Requirement
Cisco VPN 3000 Series Concentrators
Any
Cisco PIX 500 Series Security Appliances
Any
Juniper Networks NetScreen series VPN devices
Screen OS 5.1.0 or above
Juniper Networks Secure Services Gateway 500
Screen OS 5.1.0 or above
Series devices
Juniper Networks Integrated Security Gateway
Screen OS 5.1.0 or above
(ISG) Series devices
Nortel Contivity VPN Appliances
V06_00.310 or higher
Checkpoint VPN
Any
Note: The VPN tunnels must be terminated on 3rd party equipment. IPsec
connections directly to the IP Office are not supported.
Voice quality over an unmanaged IP network is unpredictable. While great care has
been taken to make the VPN Phone highly reliable, Avaya has no influence and
therefore cannot guarantee the quality of the IP network used. Avaya therefore
cannot assume responsibility for voice quality problems incurred.
.
Note: While Avaya has tested these gateways, they are not Avaya products and
must therefore be sourced and supported through third parties.
When setting up a Security Gateway you can verify the configuration by using the
manufacturer provided IPsec Client to setup a VPN tunnel using the protocol
selected. If the VPN tunnel is successfully established you have verified that the
security gateway is correctly configured and the step of creating a VPN tunnel
between the VPN phone and the security gateway should be successful.
IMPORTANT: Many VPN Routers will not allow a direct media path to be established
between two VPN Endpoints. It will be necessary to uncheck the Direct Media Path
checkbox in the Extension Configuration in IP Office. Failure to do so may result in
No Speech path when two VPN extensions try and establish a call.
COMPAS ID 132759 Issue 1
Page 14 of 74
IP Office Technical Bulletin number 90
Converting an IP Phone
The VPN Phone software package comes in zip format and can be found in the
\bin\VPN Phone directory on the IP Office 4.1 Administration CD and includes the
following Application files and script files.
1. 46xxvpn.scr
2. 46vpnupgrade.scr
3. 46vpnsetting_Template.txt
4. 46vpnsetting_readme.txt
5. Application Files for all supported 4600/5600 series IP
telephones
Copy the above files onto the TFTP Server that you currently use to provide the
firmware to the IP Phones. Also make sure that the latest 46xxupgrade.scr file
provided with and installed by the IP Office 4.1 Administration CD is copied over as
this has some modifications in it to allow the conversion of an IP phone into a VPN
phone.
Once the necessary files are on your TFTP server either setup and register a new IP
phone onto your IP Office system or go to an existing IP Phone that you want to
convert and use the following procedure to convert the phone into a VPN phone:
1) Allow the telephone to initialize and register with IP Office.
2) After the phone is registered, set the GROUP for each phone you want to
upgrade to a VPN telephone to 876. To initiate the GROUP command from
the telephone key pad, press: Mute 4-7-6-8-7 # (G-R-O-U-P #)
3) After the GROUP command is initiated, enter 8-7-6 # (V-P-N #) for the New
value. Use Page LEFT key to erase any errors.
4) Press # to save the new value. Save new value? * = no # = yes
5) Now restart the IP phone by entering: Mute 7-3-7-3-8 # (R-E-S-E-T #)
6) Press * when asked to Reset Values? * = no # = yes
7) Press # when asked to Restart Phone? * = no # = yes
Depending on the speed of your network and existing firmware version on the phone
it may take up to 5 minutes to load the necessary firmware.
When the phone has loaded the VPN firmware it should show the following screen
when it restarts. This error message is shown as the configuration details for the VPN
tunnel have not yet been entered.
COMPAS ID 132759 Issue 1
Page 15 of 74
IP Office Technical Bulletin number 90
When you press the `Edit' key you will be presented with the necessary screens to
setup the VPN configuration. The first thing you need to set is the type of VPN device
that you will be connecting to, there are eight possible choices:
1)
Avaya Security Gateway
2)
Cisco Xauth with Pre-Shared Key
3)
Juniper Xauth with Pre-Shared Key
4)
Checkpoint
5)
Cisco Xauth with Certificates
6)
Juniper Xauth with Certificates
7)
Generic Pre-Shared Key
8)
Nortel Contivity
When you select one of these options you are then presented with another set of
screens allowing you to enter the necessary information required to setup the tunnel.
Once you have entered the minimum configuration details required a `Done' option
will appear allowing you to save these details. At this stage the phone will attempt to
start the VPN connection. If it is unable to connect the phone will show an error
message.
When the tunnel has successfully been built and the phone is connected to the VPN
it will then attempt to register with the IP Office. The 56xx series IP phones will
automatically identify themselves to the IP Office as a VPN phone in the registration
request they pass to the IP Office, if the VPN Phone Allowed checkbox has not been
selected for this user when the phone attempts to register it will fail and `Wrong Set
Type' will be displayed on the phone.
If using a 46xx series IP phone by default it will attempt to register as a normal IP
phone meaning that the VPN is running un-licensed and will stop working after 180
days. To enable the phone to consume a license you need the phone to load a file
called `46vpnsetting.txt' that contains the relevant details. This file can also be used
to configure all of the parameters of the VPN setup on the phone which is useful if
deploying a large number of VPN phones.
You will need to use the file called 46vpnsetting_Template.txt file, provided with the
VPN firmware bundle, to create the 46vpnsetting.txt file.
Please read the
accompanying
file
provided
with
the
VPN
firmware
bundle,
46xxvpnsetting_readme.txt, for further information on which parameters need to be
setup.
The entry in this file that is required to allow the 46xx phones to register as IP phones
is `SMBLIC 1'. An easy way to test that the phone has picked this setting up is to
make sure that the VPN Phone Allowed checkbox is not selected for this user. If the
phone has correctly picked up this setting it will display `Wrong Set Type' on the
phone screen when it attempts to register. Once you see this message open the IP
Office configuration and select the VPN Phone Allowed checkbox and restart the
VPN phone to allow it to successfully register with the IP Office.
Note: The VPN phone does not need to be able to read the 46vpnsetting.txt file
every time it starts as it caches the settings.
Once the VPN phone is running you can make any changes to the VPN settings by
doing the following:
COMPAS ID 132759 Issue 1
Page 16 of 74
IP Office Technical Bulletin number 90
1) To view the VPN settings from the telephone key pad, press: Mute 8-7-6-6-6-
3 # (V-P-N-M-O-D #)
2) Press * to modify the settings * = Modify # = OK
3) You can then view the settings and make any changes required. Pressing the
button labelled `Profile' allows you to change the type of VPN device that you
are connecting to.
3.2
Embedded Voicemail Enhancements
Increased Number of Auto Attendants
The number of Auto Attendants available on the IP500, IP406v2 and Small Office
Edition has been increased to 40. These Auto Attendants are independent of each
other and to facilitate multi-tier operation are provided with the ability to link to each
other to enable multiple tiers (e.g. 8 attendants with 5 levels each, or other similar
permutations).
The new Auto Attendants will be allocated a number automatically by Manager,
starting from 01 through to 40. The number allocated to the Auto Attendant will be
two digits and will be the lowest number that is currently unused in the configuration.
For example, if 4 Auto Attendants had been created in a configuration file they will
have been allocated 01, 02, 03, 04 respectively, if at a later date the Auto Attendant
numbered 02 is deleted the next Auto Attendant created in this configuration file will
be allocated 02.
When creating a new Auto Attendant if recording short codes do not exist these will
be generated to provide access to the configured greeting recordings for the Auto
Attendant.
The short codes needed to access the greetings will follow the format *8NXX, where:
·
*8 is fixed
·
N represents the greeting being recorded
1 = Morning greeting
2 = Afternoon greeting
3 = Evening Greeting
4 = Menu Options.
·
XX = the AA number
When upgrading from older versions of IP Office existing Auto Attendants will be
allocated Auto Attendant numbers starting with the next unused number and short
code numbers will be converted to operate with the new mode of operation and
configuration.
Ability to give labels to and re-use Auto Attendant prompt files
The Auto Attendant form has a new "Recording Name" field added against the
Morning/Afternoon/Evening greeting options and the Menu Options. A prompt
recording file can be referenced by name and re-used in multiple Auto Attendants
without the need to create a recording for each occurrence.
COMPAS ID 132759 Issue 1
Page 17 of 74
IP Office Technical Bulletin number 90
To make use of this facility you can either record a file manually via the handset and
then re-use that recording or you could use pre-recorded prompts and then convert
the wav file to the correct format for the IP Office to use. This would be beneficial to
those customers that have a lot of sites and want to use the same greetings for
consistency.
For the first option of making a manual recording you must open the configuration in
Manager and setup the Auto Attendant. Type in a name to use for the recordings in
the Recording Name fields where appropriate and then save the configuration. Dial
into the Auto Attendant using the short codes and record each message required by
following the prompts. Once this has been done you can then re-use these
recordings in any Auto Attendants by selecting the Recording Name from the drop
down list.
If pre-recorded prompts are provided in wav format there is a utility in the 4.1
Manager that will convert the file to the correct format for use in the Auto Attendant.
The utility is launched via File | Advanced | LVM Greeting Utility.
Converting Pre-recorded Prompts
This process converts the source WAV file recording to the format required by the IP
Office Embedded Voicemail.
1. The original recording must be in the following WAV file format. If it is in a
different format convert the file using a tool such as Windows Sound
Recorder.
·
PCM/Uncompressed.
·
8000 KHz, 16bit, Mono.
2. Start IP Office Manager.
3. Select File | Advanced | LVM Greeting Utility.
4. Click on the ... button for Input File and select the WAV file.
5. Click on the ... button for Output File and select the location into which you
want the converted file saved.
·
Select the required file type. For Small Office Edition systems this should
be G723 Files (*.c23). For other IP Office systems use G711 Files
(*.c11).
·
Enter a name for the file (up to 8 characters with no spaces) and end the
file name as either .c23 or .c11 to match the selected file type.
COMPAS ID 132759 Issue 1
Page 18 of 74
IP Office Technical Bulletin number 90
6. Enter a name for the recording in the Recording Name field. This is the
name that will be entered into the IP Office configuration to use the recording.
Note that the field in case sensitive.
7. Ensure that the Format matches that selected for the Output File settings
chosen above.
8. Click OK.
Note: If there are any errors during the conversion an error message will appear and
a log file is output containing further information about the failure. The normal causes
of any failure are that the input file is not in the correct format or the output file
extension and format do not match.
Editing an Auto Attendant to Use Named Recordings
1. Start IP Office Manager and receive the IP Office configuration.
2. Select the Auto Attendant form and select or create the required auto
attendant.
3. In the Recording Name field enter the name of the greeting to be used. This
is the Recording Name entered during the files conversion, not the actual file
name. It is case sensitive.
4. If only converted greeting files are to be used with the auto attendant, it may
be advisable to disable the Enable Local Recording option to stop any
system user recording over the file.
5. Send the configuration back to the IP Office.
Transferring the Recording to the Embedded Voicemail Memory Card
This process uses TFTP to transfer the converted file to the Embedded Voicemail
memory card. It first requires the IP Office to be configured with the IP address of the
PC from which it should accept TFTP file transfers.
1. Determine the IP address of the PC from which you want to transfer the files.
2. Start IP Office Manager and receive the IP Office configuration.
3. Select the System configuration form.
4. Select the System tab.
5. In the File Writer IP Address field, type the IP address of the PC from which
you want the sending of files to the memory card to be allowed.
6. Click to send the configuration back to the control unit.
7. Open a command window in Windows (select Start | Run and enter cmd).
8. From the command window, you can use TFTP to upload files to the memory
card.
·
The command is tftp -i <IP Office IP address> put <source file>
a:\lvmail\AAG\<filename>
COMPAS ID 132759 Issue 1
Page 19 of 74
IP Office Technical Bulletin number 90
·
For example, to transfer the file c:\greeting01.c11 to an IP Office with a
LAN1 IP address of 192.168.42.1, the command would be tftp -i
192.168.42.1 put c:\greeting01.c11 a:\lvmail\AAG\greeting01.c11
Note: a:\lvmail\AAG is the destination folder on the Embedded Voicemail memory
card used for auto-attendant greetings.
Preventing Over Recording of Uploaded Files
Once uploaded to the IP Office, the converted files can still be recorded over using
the default short codes for recording auto attendant greetings. To prevent this de-
select the Enable Local Recording option of the auto attendant.
3.3
Internal Twinning of Appearance Keys
In IP Office 4.1 it is possible for appearance calls to a twinned user to alert on both
the primary and secondary phones. This applies to Internal Twinning only - not
external twinning.
A set of three additional checkboxes have been added to the User/Twinning tab in
Manager and will be enabled when the User's twinning is set to Internal. They are:
·
Twin Bridge Appearances
·
Twin Coverage Appearances
·
Twin Line Appearances
When a call alerts on a user's phone on an appearance button other than a Call
Appearance button the user's twinning setting for that type of button will be inspected
and if it is enabled the call will be presented to the internal twinning destination.
COMPAS ID 132759 Issue 1
Page 20 of 74
IP Office Technical Bulletin number 90
If the Appearance is configured for "Immediate" or "Delayed" ring the twinning will
occur immediately the call is presented to the Appearance, the delay setting will be
ignored. If the Appearance is set to "No Ring" the call will not be twinned.
3.4 Tagging on Incoming Call Routes
A new field has been added to the Incoming Call Route form to allow a tag to be
added to an incoming call. This is the same tagging as that done by PhoneManager
and SoftConsole.
The tag is shown on the phone display when the call is alerting but is removed from
the display when the call is answered. If the call is transferred the tag is displayed
again while the transferred call is alerting and removed from the display when the call
is answered.
The tag will also be displayed in the Phone Manager tag field and SoftConsole notes
fields, it will also be displayed in their call histories. Phone Manager and SoftConsole
can be used to change the tag text when transferring calls.
3.5 Time of Day and Date Routing of calls
A new calendar facility has been added to IP Office Time Profiles to define dates and
times for specific operations. This provides flexibility to use date and time on any
feature that makes use of Time Profiles, e.g. for public holidays. For a time profile
with multiple entries, for example a week pattern and some calendar entries, the
profile is valid when any entry is valid.
COMPAS ID 132759 Issue 1
Page 21 of 74
IP Office Technical Bulletin number 90
Note: The option to set calendar based entries is limited to the current year and
following year only it is not possible to set entries more than a year in advance.
3.6 Time Profile Support on Incoming Call Routes
In order to provide date based routing on the IP Office support for Time Profiles has
been added to the Incoming Call Route. A new tab called `Destinations' is added to
Incoming Call Routes and will support multiple destinations. For each destination a
Time Profile and a Fallback Extension will be configurable.
When multiple entries are added, they are resolved from the bottom up. The entry
used will be the first one, working from the bottom of the list upwards, that is currently
'true', i.e. the current day and time or date and time match those specified by the
Time Profile. If no match occurs the Default Value options are used.
In the example below each time profile would be checked in turn starting with the one
called "Holidays". As soon as an entry is matched then that is the routing that will
apply to that call.
Note: You will not be able to add multiple destinations to a call route until you have
configured a time profile.
3.7 Queue Threshold Alert
A new feature has been added to the Hunt Group Queuing tab in Manager that is
used to alert at a selected analog extension port when the number of calls queued
against a Hunt Group reach a specified threshold. Alerting is triggered when the
number of queued calls reaches the threshold. Alerting will stop only when the
number of queued calls drops back below this threshold. This value is affected by
Normalize Queue Length setting.
The design intention is that the analog extension port should be connected to a loud
ringer or other alerting device and is not used for making or receiving calls. The user
should not be a member of any hunt groups or the queuing alarm target for any other
hunt group queue. Attempting to answer the alerting device will just give ring tone.
The alert does not follow user settings such as forwarding, follow me, DND, call
coverage, etc or receive ICLID information.
COMPAS ID 132759 Issue 1
Page 22 of 74
IP Office Technical Bulletin number 90
Note: There will be no support for CTI type interactions with the Alerted User,
specifically TAPI (1st or 3rd party), Phone Manager and SoftConsole will not be
supported.
3.8 Security Enhancements
3.8.1
Transport Layer Security (TLS)
In IP Office 4.1 secured communication is supported between the IP Office system
and IP Office Manager using TLS for both authentication and encryption. Each of the
IP Office services (configuration and security administration) can be configured for
secure and/or unsecure communication.
Service
Method
Port Used
Default
IP Office
Unsecured
Base TCP Port
50804
3.2+
Configuration
Secured
Base TCP Port plus 1
50805
4.1+
System Status Interface
Unsecured
Base TCP Port plus 4
50808
4.0+
Unsecured
Base TCP Port plus 8
50812
3.2+
Security Administration
Secured
Base TCP Port plus 9
50813
4.1+
Note: The security settings can also be changed for the System Status Interface,
however SSA does not yet support secure connections so this should be left to
unsecure only.
The security administrator can select whether the session between Manager and IP
Office can utilize TLS v1.0. Enforcing the use will disable access to versions of
Manager that do not have TLS capability. The selection of whether TLS is to be
enforced resides within the security settings.
·
Unsecure Only (Default): This option allows only unsecured access to
the service. The service's secure TCP port is disabled.
·
Unsecure + Secure: This option allows both unsecured and secure
(Low) access. In addition, TLS connections are accepted without
encryption, just authentication.
·
Secure, Low: This option allows secure access to that service using
TLS, and demands weak (for example DES_40 + MD5) encryption and
authentication, or higher. The service's unsecured TCP port is disabled.
·
Secure, Medium: This option allows secure access to that service using
TLS, and demands moderate (for example DES_56 + SHA-1) encryption
and authentication, or higher. The service's unsecured TCP port is
disabled.
·
Secure, High: This option allows secure access to that service using
TLS and demands strong (for example 3DES + SHA-1) encryption and
authentication, or higher. In addition a certificate is required of the client
(usually Manager). The service's unsecured TCP port is disabled.
COMPAS ID 132759 Issue 1
Page 23 of 74
IP Office Technical Bulletin number 90
WARNING: Selecting a setting other than Unsecure Only will cause the IP
Office system to stop responding for a period of up to 5 minutes, depending on
the security level chosen, while the IP Office generates a unique security
certificate. This will also affect the response of the phones so should only be
done when the system is not in use.
Once security has been setup on the IP Office the Manager will need to be setup to
enable secure communication.
This is done through File | Preferences and then selecting the Security tab.
Secure Communications: Default = Off
When selected, any service communication from Manager to IP Office uses the TLS
protocol. This will use the ports set for secure configuration and secure security
access. It also requires the configuration and or security service within the IP Offices'
security configuration settings to have been set to support secure access. Depending
on the level of that secure access selected, it may be necessary for the Manager
Certificate Checks below to be configured to match those expected by the IP Office
configuration and or security service.
Note: When Secure Communications is set to on, a padlock icon is displayed at all
times in the lower right Manager Status field.
