Vcx 9.8.15 release notes 2011-03-31

March 31, 2011 of 85

VCX 9.8.15 Release Notes

Keywords: VCX Enterprise, VCX Connect, VCX MIM, IPT, IPM, FAC, CABC, CAC, ACD, LDAP,

Lock/Unlock, Auto-Attendant, Localization, Lotus Sametime, Global Directory, Multi-

Language, upgrade

Abstract: This release notes describes the VCX 9.8.15 release with respect to software and hardware

compatibility, released features and functions, software upgrading, and documentations.

Acronyms:

Acronym Full spelling

VCX Voice Core Exchange

IPT IP Telephony

IPM IP Messaging

IPC IP Conferencing

IPP IP Presence

IPCC IP Contact Center

CCC 3Com Convergence Center Client

LDAP Lightweight Directory Access Protocol

CDR Call Detailed Record

ACD Automatic Call Distribution

AA Auto Attendant

HG Hunt Group

MCT Malicious Call Trace

BLA Bridged Line Appearance

NTP Network Time Protocol

FTC First Time Configuration

VPIM Voice Profile for Internet Mail

MWI Message Waiting Indication

GVI Global Voicemail Integration

GVCS Global Voicemail Central Server

SNMP Simple Network Management Protocol

COS Class of Service

March 31, 2011 of 85

Acronym Full spelling

TOS Type of Service

DTMF Dual-tone multi-frequency

MOH Music on Hold

RTP Real-time Transport Protocol

RTCP RTP Control Protocol

SIP Session Initiation Protocol

SMS Short Message Service

BLF Busy Lamp Field

CSV Comma-Separated Value

IMAP Internet Message Access Protocol

POP3 Post Office Protocol V3

SMTP Simple Mail Transfer Protocol

TUI Telephone User Interfaces

TTS Text To Speech

ASR Automatic Speech Recognition

FMFM Find Me Follow Me

PAB Personal Address Book

SOAP Simple Object Access Protocol

FAC Forced Account Codes

CABC Customer Accounting and Billing Codes

CAC Call Admission Control

MIM Multi-function Interface Module

iMC Intelligent Management Center

VSM Voice Service Manager

OS Operating System

GD Global Directory

3Com VCX 9.8.15 Release Notes

March 31, 2011 of 85

Table of Contents

Version Information·········································································································································7 Version Number ·········································································································································7 Version History···········································································································································7 Applications in VCX Release 9.8.15 ··········································································································7 Hardware and Software Compatibility Matrix in VCX Release 9.8.15 ·······················································9

Restrictions and Cautions ····························································································································10

New Features in Release 9.8.15 ···················································································································11 Microsoft OCS & Microsoft Exchange Integration ···················································································11 Simultaneous Ringing Feature·················································································································12 HP ProLiant DL360 G7 Support···············································································································12 VCX System Status··································································································································12 Scheduled Backups ·································································································································12 ACD License Enhancement·····················································································································12 Selectively Delete a Message··················································································································12 Voicemail Return Receipt ························································································································12 VCX Extension Enhancement··················································································································13 Replication Setup Script Enhancement ···································································································13 Voice Mail File Name Change ·················································································································13 Background/Screen saver Image Enhancement ·····················································································13 IPM Web Enhancements ·························································································································13 IMC VCX Enhancements ·························································································································13

New Features in Release 9.5.13 ···················································································································13 3Com 350x Series IP Telephones ···········································································································13 HP ProLiant DL120 G6 and DL360 G6 support·······················································································13 VCX Scalability Improvements/Enhancements ·······················································································13 SSLv3 Support for IMAP··························································································································14 IPM support for Electronic Fax Sending ··································································································14 VCX Multi-Language Enhancement·········································································································14 VCX Extension Enhancement··················································································································14 ACD Call Detail Reports Enhancement ···································································································15 CAC Feature Enhancement·····················································································································15 Global Directory Enhancement ················································································································15 Standard SIP “user” Parameter Support··································································································16 Conference User Group/Class Support ···································································································16 VCX Applications Windows 7 32-bit Support···························································································16

New Features in Release 9.0.17 ···················································································································16 Forced Account Codes & Customer Accounting and Billing Codes ························································16 Call Admission Control (CAC)··················································································································17 Automatic Call Distribution (ACD)············································································································17 Active Directory/LDAP Integration ···········································································································17


March 31, 2011 of 85

MSR Voice Gateway Support ··················································································································18 Support for region/branch configuration for VCX on Power Systems······················································18 Increase support up to 50 branches on VCX Region-Branch Configuration ···········································18 VCX License Enforcement·······················································································································18 Lotus Sametime Support ·························································································································19 Enhanced Call Pickup Groups ·················································································································19 3Com 3103 Phone Select Button·············································································································19 Enhanced Busy lamp Field (BLF) ············································································································20 Lock/unlock Feature·································································································································20 FAX as PDF support ································································································································20 Auto-Attendant Enhancement··················································································································20 Voicemail CODEC Configuration ·············································································································20 Voicemail Language Pack Configuration·································································································21 IP Messaging Web User Portal················································································································21 Global Voicemail Central Server Subscribers··························································································21 Localization ··············································································································································21 Phone Identification··································································································································22 VCX Phone Profile Settings for Desktop Communicator ·········································································22 VCX System Configuration ······················································································································22 VCX System Statistics ·····························································································································22 SIP Trunking ············································································································································22

Known Anomalies in VCX Release 9.8.15 ···································································································23

List of Resolved Problems ···························································································································23 Resolved Problems in VCX Release 9.8.15 ····························································································23 Resolved Problems in VCX Release 9.5.13 ····························································································24 Resolved Problems in VCX Release 9.0.17 ····························································································25

Upgrading to VCX release 9.8 ······················································································································27

Related Documentation·································································································································30

A VCX version 9.8 upgrade overview ······································································································31 Provisioning Restrictions during an Upgrade ···················································································32 Preliminary Considerations ··············································································································33 Post-Upgrade Consideration ············································································································33 About the VCX System Administration Web Interface ·····································································34

B Upgrading VCX Enterprise Server Software from V7.1 to V9.8·························································35 Verifying Software Versions·····················································································································35 Upgrading a VCX Enterprise System with Two Servers··········································································36 Upgrading a VCX Enterprise System with Region and Branch ·······························································38 Upgrading a Legacy VCX Enterprise System with Four Servers ····························································41 Upgrading a Classic VCX Enterprise System step by step ·····································································44 Upgrading an Expand VCX Enterprise System step by step···································································49

C Upgrading VCX Software from V9.0/9.5 to V9.8 ··················································································53 Verifying Software Versions·····················································································································53 Upgrading a VCX Connect with One Server····························································································54


March 31, 2011 of 85

Upgrading a VCX Enterprise/Connect with Two Servers ········································································55 Upgrading a VCX Enterprise with Region and Branch ············································································57 Upgrading a Classic VCX Enterprise System step by step ·····································································58 Upgrading an Expand VCX Enterprise System step by step···································································61

D Upgrading VCX System to V9.8 (Web)·································································································63 To access the VCX System Administration Web Interface······································································63 Upgrading VCX Software·························································································································64

E Upgrading VCX Connect System to V9.8 ····························································································68 Verifying Software Versions·····················································································································68 Upgrading a VCX Connect System with One Server···············································································69 Upgrading a VCX Connect System with Two Servers·············································································70

F Switching Versions of VCX Server Software ······················································································73 Switch Version Overview ·························································································································74 VCX Software Rollback Considerations···································································································74 Provisioning Restrictions during an Version Switch·················································································75 Verifying Software Versions·····················································································································76 Rolling Back VCX Enterprise System with Two Servers to 7.1 ·······························································77 Rolling Back VCX Enterprise System with Region and Branch to 7.1·····················································77 Rolling Back VCX System with Single Server to 8.0/9.0 ·········································································79 Rolling Back VCX System with Two Servers to 8.0/9.0···········································································79 Rolling Back VCX System with Region and Branch to 9.0 ······································································80 Rolling Back VCX System through Web Interface···················································································81

G Upgrading VCX System by clean installation ·····················································································84 Clean and Install VCX software for one VCX server ···············································································84


March 31, 2011 of 85

List of Tables

Table 1 Version history .............................................................................................................................. 7

Table 2 Applications in VCX Release 9.8.15 ............................................................................................. 7

Table 3 Hardware and software compatibility matrix ................................................................................. 9

Table 4 Server Platform and VCX Release compatibility matrix ............................................................... 9


March 31, 2011 of 85

Version Information Version Number

VCX 9.8.15

Version History Table 1 Version history

Version number Last version Release Date Remarks

9.8.15 9.5.13 14-Jan-2011 -

9.5.13 9.0.17 25-Jun-2010 -

9.0.17 First Release 25-Sep-2009 -

Applications in VCX Release 9.8.15 In addition to the Release 9.8.15 system software, VCX Release was tested against the applications shown in the following table.

Table 2 Applications in VCX Release 9.8.15

Applications Detail Information

IP Conference VCX Enterprise and Connect: 7.3.203 or later

3Com Convergence Client 7.3.1

Call Detail Reports (CDR Application) R8.2.1

ACD Desktop Statistics (ACD RTS Client)

R7.0.0

MSR Software Minimum 5.20.R1910 or later

V7111x-05 Analog Gateway (FXS and FXO, original versions) – 4.60A.043 (2, 4, 8, and 24 ports)

V7111x-07 Analog Gateway (FXS, FXO, and combined FXS/FXO, new versions) – 5.60A.028, 6.00A.027.003 (2, 4, 8, and 24 ports)

V6000 Branch Office Solution – 5.60A.028, 6.00A.027.003

V7122-05 Digital Gateway – 4.60A.043

V6100 Branch Office Solution – 5.60A.028, 6.00A.027.003

Gateway Software

V7122-07 Digital Gateway – 5.60A.028, 6.00A.027.003

3Com Telecommuter Module 4.6.5 + patch, 4.7.5

3Com Desktop Communicator and

3Com Desktop Communicator Outlook

Edition

2.6.x or later


March 31, 2011 of 85

Applications Detail Information

iQNet Solutions (Attendant Console

Software) 4.0.0.88

Ingate SIParator (SIP Trunking B2BUA)

4.8.1

3Com eXchange/EPICCenter VCX Enterprise and Connect: 4.72.11+patches, 6.00.10.0004+patch

Nuance RealSpeak Telecom TTS 4.5

iMC PLAT 5.0 (E0101)

iMC VSM 5.0 (E0101)

Microsoft OCS OCS 2007R2 Lync Server 2010

Microsoft Exchange 2003, 2007, 2010

Microsoft Outlook 2003, 2007, 2010

IBM Lotus Domino 8.0, 8.5

IBM Lotus Sametime 8.0, 8.5

Note 1: To access any VCX system interface that requires a browser, use Internet Explorer 6.0 or Firefox 2.0 or later releases.

Note 2: An upgrade to Gateway Software version 5.2 is possible only from Version 5.0 or higher. Any Gateway running a version 4.X must be upgraded to 5.0 first.

Note 3: Except for 3Com Desktop Communicator 2.7.x or higher, VCX applications are designed and tested 32 bit applications and will only work (and be supported) on a 32-bit Operating System (OS) and 32 bit hardware architecture, regardless of the processor vendor. As an example, the Call Detail Reports is a 32 bit application, and it’s only supported on 32-bit OS’s (Windows 7/Vista/XP/2000/NT) and 32 bit processors.

Note 4: Please keep the same ACD RTS configuration on each server within a region (include the region and all branches). To watch all ACD Groups RTS data within a region, please setup ACD RTS Client connecting to the region.

Note 5: Remote workers can use the soft phone (3Com Convergence Client or 3Com Desktop Communicator) for receiving calls from an ACD but advanced functionality and feature use requires a 3Com phone that supports the full ACD features.


March 31, 2011 of 85

Hardware and Software Compatibility Matrix in VCX Release 9.8.15 Table 3 Hardware and software compatibility matrix

Items Specifications

Product family VCX Enterprise Server, VCX Connect Server

Hardware platform

VCX Enterprise: HP ProLiant Servers DL120 G6, DL360 G6/G7; IBM x86-based servers x306/x306m/x3250/x3250m2, x345/x346/x3650; VCX Enterprise Branch MIM; VCX V6x00 Enterprise Branch VCX Connect: HP ProLiant Servers DL120 G6; IBM x86-based servers x3250m2; VCX Connect 100; VCX Connect MIM

3Com VCX Telephones

Model 3500B, 3500, 3501, 3502, 3503 Model 3101, 3101SP, 3102, 3103, 3105 NOTE: Starting with VCX 9.0 or higher, the 210x Series IP Telephones are officially unsupported by 3Com. 3Com has retained the 2102 button mapping page for historical purposes only for existing customer installs – however, VCX 9.0 or higher features and functionality may or may not work as designed.

3Com-Polycom phones 3Com-Polycom Models – IP330, IP430, IP550 & IP650 with v2.2 code

Minimum Memory 1024M

VCX Linux 7.20.15

VCX Users 2.0.3-1.noarch

Oracle VCX Enterprise/Connect: 10.2.0.4-1.i386

IP Messaging Language Pack 9.8.15

TTS Adapter 2.0

TCSPI for Lotus Sametime 8.5 For Windows: 10.0.2.2

TCSPI for Lotus Sametime 8.0 For Windows: 9.0.0.1

Remarks -

Table 4 Server Platform and VCX Release compatibility matrix

9.8.15 9.5.13 9.0.21 9.0.17 8.0.4e 7.1.30c 7.1.21c/

7.1.28c 7.1.16c 7.1.xc (Note 1)

HP ProLiant DL360 G7 Yes No No No No No No No No

HP ProLiant DL360 G6, DL120 G6 Yes Yes Yes No No Yes No No No

IBM x86-based server x3250m2 Yes Yes Yes Yes Yes Yes Yes No No

VCX Enterprise Branch MIM, VCX Connect

MIM Yes Yes Yes Yes No No No No No

VCX Release

Server Platform


March 31, 2011 of 85

VCX Connect 100 Yes Yes Yes Yes Yes No No No No

VCX V6x00 (Note 2) Yes Yes Yes Yes Yes Yes Yes Yes Yes

IBM x86-based servers x3250, x3650 Yes Yes Yes Yes Yes Yes Yes Yes No

IBM x86-based servers x306/x306m, 345/x346 Yes Yes Yes Yes Yes Yes Yes Yes Yes

Note 1: 7.1.xc indicates VCX 7.1.14c or earlier VCX 7.1 releases.

Note 2: V6x00 indicates V6000 or V6100 Enterprise Branch Server.

Restrictions and Cautions Microsoft OCS

In Microsoft OCS 2007 or OCS 2007R2, Microsoft doesn’t recommend taking Diversion header in the Invite SIP message. When VCX communicates with OCS 2007 or OCS 2007R2, please do the configuration to exclude the Diversion header by ‘conf SipExcludeDivHdr’ command through remote CLI.

To cooperate with Microsoft Lync Server 2010, you must UNCHECK ‘Enable refer support’ in the Microsoft Lync Server to prevent the call transfer failure.

MSR PSTN Survivability Limitation

1. MSR can’t switch FXS call to the secondary server immediately, when primary VCX server is down. FXS will register to secondary server within 300s when expire time set to 300s (start to register after 80%*300 and 11 times of retries, total 280s in the worst case. Best case within 30s).

2. MSR can’t switch FXS back to primary server when the primary server recovers. PSTN call will still be sent to secondary server. Administrator must manually switch back to the primary server.

Upgrading your gateway to v5.6

Before upgrading to v5.6 from v5.2 or earlier, please backup your configuration .INI file. Check the resulting .INI file to see if the following configuration parameters are defined:

LocalMediaDefaultGW = 10.1.10.1

LocalMediaIPAddress = 10.1.10.10

LocalMediaSubnetMask = 255.255.255.0

LocalControlIPAddress = 10.1.10.10

LocalControlSubnetMask = 255.255.255.0

LocalOAMIPAddress = 10.1.10.10

LocalOAMSubnetMask = 255.255.255.0

LocalOAMDefaultGW = 10.1.10.1


March 31, 2011 of 85

If these configurations do exist, and you have not configured your gateway for network resiliency (gateway models v6000, v6100, v7122), please remove them from your .INI file. Save the updated .INI file, reapply, and burn the .INI file to the gateway prior to upgrading to v5.6. We do not recommend applying the updated .INI during the software upgrade wizard. Leaving these parameters intact, if not needed, may cause the gateway to resolve back to the IP address settings seen in these parameters after the v5.6 upgrade.

VCX Connect System

If you upgrade an earlier VCX Connect system．．．．．．．．．．．．．．．． to VCX 9.8 or later, the built-in number translation “0*”

will conflict with the extension number starting with 0. You can remove this built-in number translation to avoid the confliction.

VCX Connect License

VCX Connect systems upgraded from VCX 8.0.4e may display an incorrect number of available licenses on the 'License Information' and 'License Usage' pages of the VCX Admin GUI after the upgrade to 9.0 or later. Note that customers are expected to purchase and install a 9.0/9.5/9.8 Upgrade license as part of the Upgrade process. Installing the correct 9.0/9.5/9.8 license will correct some of these errors. It is still possible, after installing the 9.0/9.5/9.8 license key, that a HIGHER number of available licenses are shown than the customer purchased (specifically Entry Phone, Business Phone, Convergence Center Client Softphone, Desktop Communicator Softphone and Mailbox licenses). This does not impact system functionality, and any customer purchased licenses are always available provided the customer installed the 9.0/9.5/9.8 Upgrade license.

ACD License

ACD License work with where ACD Group physically reside. Only the site on which the ACD groups reside on needs ACD License.

3Com Telephones

The Ethernet interfaces of 3500B do NOT support Auto-MDIX feature, so ONLY the crossover cable can be used for the PC port connecting and ONLY the straight-through cable can be used for the LAN port connecting.

EMS Support

Enterprise Management Suite (EMS) does not support VCX 9.0 or higher.

VCX on Power Systems

VCX on Power Systems are not supported by VCX 9.5 or higher.

New Features in Release 9.8.15 Microsoft OCS & Microsoft Exchange Integration

With VCX 9.8, VCX platforms support Microsoft OCS & Microsoft Exchange servers using direct SIP integration between the IP-PBX and the Microsoft servers. The following Microsoft OCS & Microsoft Exchange versions are supported by this release:

Microsoft OCS 2007 R2;


March 31, 2011 of 85

Microsoft Lync Server 2010;

Microsoft Exchange 2007;

Microsoft Exchange 2010.

NOTE: One OCS endpoint cannot make a call with VCX Hunt Group or ACD Group, because of the OCS endpoint cannot be held just when the call has been established.

Simultaneous Ringing Feature VCX will allow users to configure their IP telephones to do simultaneous ringing. This feature allows the user to cause their desk phone to ring at the same time as an external (gateway routed) number. When one of the ringing endpoints answers, the other ringing endpoint is cancelled. It allows a user to be reached at two different locations by ringing both locations at the same time.

HP ProLiant DL360 G7 Support The HP server ProLiant DL360 G7 is supported by this release.

VCX System Status The Web User Interface can display the replication status of primary/secondary pairs.

Scheduled Backups The Web User Interface can provide the capability to schedule static and reoccurring full backups of the system.

ACD License Enhancement With previous version, it is a static license strategy for ACD feature. That is, when administrator appoints one phone as agent, it will tie up one ACD license and the license will not be released until the appointment has been undone. In VCX 9.8, the static license strategy has been replaced by dynamic license strategy – the ACD license will be consumed just when the agent is online and its status in ACD group is “Login”.

Selectively Delete a Message VCX can provide the administrator the ability to selectively delete an individual future delivery message.

Voicemail Return Receipt If one mailbox is full and cannot receive more messages, IPM will deals with it as follows:

If the sender and receiver are located in the same server, IPM will prompt the sender that the receiver cannot accept more messages.

If the sender and receiver are not located in the same server, and the sender enables the global voicemail, IPM will send a Return Receipt (voicemail) to notify the sender.

If the sender and receiver are located in a combined global voicemail central server/local office server, IPM will send a Return Receipt (voicemail) to notify the sender.

Note that, IPM will not send a Return Receipt (voicemail) to the sender if a message is sent using VPIM or e-mail.


March 31, 2011 of 85

VCX Extension Enhancement VCX extension number starting with 0 has been supported by this release.

NOTE: If you upgrade an earlier VCX Connect system．．．．．．．．．．．．．．．． to VCX 9.8, the built-in number translation “0*”

will conflict with the extension number starting with 0. You can remove this built-in number translation to avoid the confliction.

Replication Setup Script Enhancement In order to ensure the replication data is correct, you MUST setup the replication from the primary schema. If replication is being setup for the first time after an upgrade, the setup script will not allow branch schema replication setup from the region server and inform the user that replication must be setup from the branch VCX server(s).

Voice Mail File Name Change When VCX is setup for voice mail to email delivery, the file will be renamed as “voice-message_YYYYMMDDThhmm_caller-id.wav” (such as “voice-message_20101009T0945_8001.wav”).

Background/Screen saver Image Enhancement The VCX Web Interface can provide the ability to reset Background/Screen saver Image to factory defaults. And, if the image is incorrect, VCX will display the notification to administrator.

IPM Web Enhancements IPM Web Pagination Support;

Button Map page is not accuracy;

MWI Active function improvement.

IMC VCX Enhancements MOS scoring & Packet loss notification MIB enhancements;

The license MIBs have been improved to support IMC system.

New Features in Release 9.5.13 3Com 350x Series IP Telephones

New 350x Series IP Telephones (3500B, 3500, 3501, 3502 and 3503) are supported by this release.

HP ProLiant DL120 G6 and DL360 G6 support The HP server ProLiant DL120 G6 and DL360 G6 are supported by VCX 9.5 release.

VCX Scalability Improvements/Enhancements Enhanced scalability improvements with HP ProLiant servers:

VCX Enterprise Classic

V7005 with HP ProLiant DL120 G6 server now supports up to 2,500 devices/mailboxes per region, up to 10 VCX Branch Offices per region, up to 12 regions, and up to 7,500 devices/mailboxes enterprise-wide


March 31, 2011 of 85


VCX Enterprise Expand



Enhanced VCX Connect scalability improvements with VCX v9.5

Upgrading to VCX v9.5, the following improved VCX Connect scalability is achieved:

VCX Connect 100 & VCX Connect MIM

VCX Connect 100 and VCX Connect MIM support up to 100 devices/mailboxes per region and now up to 12 regions for a total of 600 users per system

VCX Connect 200

VCX Connect 200 now supports up to 500 devices/mailboxes per region and up to 12 regions for a total of 3000 users per system.

Improved scalability achieved with existing IBM x-Series x3250M2 and HP ProLiant DL120 G6 servers

SSLv3 Support for IMAP In VCX 9.5, SSLv3 is supported for secure IMAP implementation within IP messaging.

IPM support for Electronic Fax Sending With the Electronic Fax Sending Feature, electronic fax can be sent to destination fax machine (Note that, analog fax machine is only supported) which located in PSTN through IPM. IPM works as a fax server. The electronic faxes are attached by email and sent to IPM, that is, IPM converts the attached faxes to the universal graphic format for fax machine, and then sends them to the specified fax machine. The supported electronic fax’s formats include TIF, JPG, PNG, GIF, BMP, and PDF (with embedded fonts).

NOTE: For Microsoft document, such as DOC, PPT, XLS or XLS etc., please firstly use the virtual printer called “Microsoft office Document Image Writer” to print the document into TIF format.

VCX Multi-Language Enhancement In VCX 9.5, for VCX Enterprise/Connect system, the user name or phone’s display name can support Unicode (UTF-8). User can input multi-language to these fields, such as Chinese, French, Spanish, Japanese, and Korean etc.

VCX Extension Enhancement The length of extension number (including phone extension, group address and so on) has been increased from 10 to 15.


March 31, 2011 of 85

ACD Call Detail Reports Enhancement In VCX 9.5, the CDR reports are supported for ACD feature.

CAC Feature Enhancement With previous version, CAC feature is not supported by VCX secondary server. In VCX 9.5, the CAC feature is supported by VCX primary server and secondary server. Between primary server and secondary server, the settings of CAC can be replicated each other. Note that, the CAC settings of primary or secondary server are independent. The replication of CAC setting between primary and secondary server is only for the settings backup each other.

Global Directory Enhancement In VCX 9.5, the new Global Directory (GD) mechanism can automatically detect the difference between the different VCX versions. With VCX 9.5 or later, the Global Directory can be synchronized when your system runs different VCX versions. However, we still strongly recommend that you upgrade all the VCX servers as soon as possible to maintain all features and functionality between the branches and the regions.

Note that, if your system runs one or more previous VCX version (9.0 or older), the new Global Directory feature has been limited. Please refer the following tables to understand whether the Global Directory can be synchronized or not:

− Distribute GD means VCX server will distribute the new Global Directory data to other VCX servers.

− Collect GD means VCX server will collect the new Global Directory data which distributed by the other VCX servers.

− ‘√’ means the Global Directory can be synchronized from the Distribute VCX server (Row) to Collect VCX server (Column).

− ‘×’ means the Global Directory cannot be synchronized from the Distribute VCX server (Row) to Collect VCX server (Column).

1. In multi regions, the Global Directory (GD) synchronizes between VCX region servers shown in the following table:

Collect GD (VCX Server) VCX versions

9.5 or later 9.0, 8.x, 7.x 9.5 or later √ ×

Distribute GD (VCX Server) 9.0,

8.x, 7.x

√ √

2. In one region, the Global Directory (GD) synchronizes between VCX region and branch servers, or between branch and branch servers shown in the following table: (Note: We assume the region server(s) has already been upgraded to VCX 9.5 version.)

Collect GD (VCX Server) VCX versions

9.5 or later 9.0, 8.x, 7.x Distribute GD (VCX Server)

9.5 or later √ √


March 31, 2011 of 85

9.0, 8.x, 7.x

× ×

Standard SIP “user” Parameter Support With previous version, VCX has used the SIP “user” parameter in a proprietary fashion with valid values “ip”, “phone”, “callp” and “pstn”. The allowed values for this parameter as defined in RFC 3261 are only “ip” and “phone." This leads to problems when the VCX sends SIP messages with “user=callp” or “user=pstn” to 3rd party equipment. To avoid this problem, VCX 9.5 introduces the option to use the SIP “user” parameter in a proprietary fashion or consistent with the RFC 3261 definition. VCX 9.5 also introduces a new proprietary parameter “vcx-user” in the SIP message to contain the proprietary information previously held in the “user” parameter.

Conference User Group/Class Support With VCX 9.5, VCX IP Conference can import users from VCX IP Telephony. You can define the User Group and User Class for IP Conference system through VCX Web interfaces.

NOTE: Conference User Group/Class will be supported in a future release of VCX IP Conferencing system. No provisioning is required or applicable at this time.

VCX Applications Windows 7 32-bit Support With VCX 9.5, VCX Windows applications support to work on Windows 7 32-bit Operating System (OS).

NOTE: For 3Com Desktop Communicator 2.7.x or higher, Windows 64-bit Operating System (OS) is supported.

New Features in Release 9.0.17 Forced Account Codes & Customer Accounting and Billing Codes

1. FAC - Forced Account Codes

Forced account codes (FAC) are special digit sequences of 2-16 digits that are used to control external calls. Forced account codes enforce and regulate the types of calls users can place based on the associated Class of Service. Even though users have FACs; they may not need to use it if the extensions they use to place the call have appropriate COS authorization for the number dialed. But if a FAC is entered, it must be valid before an outgoing call is routed. The account code and account name information are available in the CDR.

2. CABC - Customer Accounting and Billing Codes

Customer Accounting and Billing Codes (CABC) are special digit sequences of 2-16 digits used to associate calls with accounts for billing purposes. A user can enter a CABC to specify that the call relates to a specific client or billing account. If the CABC is invalid, the CDR will record as such. CABCs allow users to generate billing reports based on account codes / names. If the user enters multiple CABCs during a call; the newest CABC only overrides the existing CABC after it has been verified. Each CABC entered will be captured in CDR along with relevant call statistics (calling extension, phone number dialed, duration of the call, etc.).


March 31, 2011 of 85

Call Admission Control (CAC) Call Admission Control (CAC) is used to prevent congestion in media traffic. It is a preventive Congestion Control Procedure used in the Call Setup phase. Call Admission Control (CAC) is primarily aimed at monitoring and controlling bandwidth usage for groups of IP endpoints that share a common bandwidth resource.

The call is controlled based on the network region and site link. A network region is used to identify a logical group of IP endpoints that share a common bandwidth resource. A site link is used to identify a physical connectivity between two sites. Each site link must belong to one network region. A system administrator is able to set threshold limits for either bandwidth (in kbps or mbps) or number of allowable calls per network region or site link. If the administrative thresholds are exceeded, a call otherwise routed via the IP network will be routed through the local PSTN gateway of the calling party.

On multisite deployments with active global directory, VCX systems can automatically identify the CAC site links. VCX will automatically create a default CAC network region and all related CAC site links. A system administrator is able to manually change default settings of automatically created network regions and site links.

Automatic Call Distribution (ACD) Automatic Call Distribution (ACD) is a PBX feature that routes calls to available staff, known as agents, based on call-handling instructions programmed into the system. When the ACD receives an incoming call it will look for specific instructions as to how the call is to be handled. The ACD can route the call to an agent, a recorded message (or Interactive Voice Response – IVR – system), or place it on hold until a live person can receive it. ACD systems can route calls to agents or specific IVR menus based on many factors, including agent availability and expertise, and time of day, just to name a few possibilities.

The states of ACD Groups can be monitored by ACD RTS Client. The Call Detailed Reports can be generated by CDR Applications.

The main ACD features are listed as below:

ACD Group and ACD Agent Data;

ACD Algorithms like Linear, Circular, Calling Group, Most Idle Agent and Least Call Count;

Delayed Announcements & In-Queue Digit Processing;

Wrap-Up-Time (and agent override, agent extend);

ACD Reports (CDR);

Time Stamp based queuing of calls in ACD Group ;

ACD Agent List;

ACD Management – Web provisioning and Wizards;

ACD Queue Notification to Agents;

ACD Work shifts and Emergency Mode.

Active Directory/LDAP Integration LDAP synchronization feature has been extended in VCX 9.0. The new LDAP feature allows administrators to:


March 31, 2011 of 85

Use a supported LDAP directory source to perform a bulk import of users and their extensions into VCX, creating the user names and extensions in VCX and automatically assigning a default class of service to imported users;

Use the LDAP directory as an interface for basic user management (adding, removing and changing users and associated extensions);

Synchronizing changes made in the LDAP directory server with the VCX. Note that, this is a one-way synchronization, i.e. the changing flow only from the LDAP server to the VCX. Changes made to basic user information on VCX are not reflected in the LDAP directory. In case of a conflict, the LDAP server version of data wins over the data entered in VCX (so the LDAP directory server is the primary authority for basic user information);

LDAP Synchronization application can select appropriate users from an LDAP server and synchronize them into VCX directory via a LDAP filter.

VCX administrator can perform synchronization as a one-off activity (as part of first time to provision user accounts) or periodically at a set configurable time interval (users created or deleted in LDAP servers are then automatically synchronized with users in VCX).

LDAP integration can support the following LDAP servers:

IBM Domino Server 8.0 on IBM system I;

IBM Directory Server 8.0 on IBM system I;

IBM Domino Server 8.0 on IBM Power Systems;

IBM Domino Server 8.0 on Windows Server 2003 & 2008;

Microsoft Active Directory on Microsoft Windows Server 2003 & 2008;

OpenLDAP on Linux.

MSR Voice Gateway Support In VCX 9.0, MSR models 20-20/21/40 and 30-16/20/40/60 are supported to VCX System deployments that support Remote (PSTN) Survivability.

NOTE: MSR series gateways are only supported on VCX 9.0 or higher.

Support for region/branch configuration for VCX on Power Systems VCX 9.0 supports the region/branch configuration to VCX on Power System deployments by utilizing V6000 or V6100 gateways at branch offices.

Increase support up to 50 branches on VCX Region-Branch Configuration

In VCX 9.0, the maximum branch support has been increased from 40 total branches to 50 total branches on a VCX Region-Branch Configuration.

VCX License Enforcement In order for VCX services to load and run properly, VCX 9.0 MUST have the proper Right to Use (RTU) server license activation key installed:

IP Telephony Server RTU License – Authorizes to load and run Call Processor Server, Data Server and CDR Server;

IP Messaging Server RTU License – Authorizes to load and run IP Messaging Server;


March 31, 2011 of 85

IP Telephony and IP Messaging Server RTU License – Authorizes to load and run Call Processor Server, IP Messaging Server, Data Server and CDR Server;

Data Server RTU License – Authorizes to load and run Data Server;

CDR Server RTU License – Authorizes to load and run CDR Server.

In addition to entry phone license, third party license, basic phone license, business phone license, etc, the following licenses are new for VCX 9.0:

Desktop Communicator Softphone License;

Desktop Communicator Outlook Edition Softphone License;

ACD Agent License.

For the VCX Connect system, the built-in licenses include:

IP Telephony and IP Messaging Server RTU License;

4 Entry phone licenses;

25 Business phone licenses;

25 IP Messaging Seat licenses;

25 3Com Convergence Center Client soft-phone licenses;

25 3Com Desktop Communicator soft-phone licenses.

NOTE：The built-in license keys cannot be deleted, shared with or transferred to another VCX Connect.

For ALL VCX systems, the built-in licenses include:

2 ACD Agent try and buy demo licenses.

The ACD Agent demo licenses are just for trial purposes and cannot be deleted. When a purchased ACD Agent license is installed into the VCX system, the ACD demo licenses will be overwritten with the purchased amount.

Note that, VCX user and RTU licenses cannot be transferred from one VCX system to another VCX system after license registration unless the VCX server has an approved Returns Material Authorization number.

Lotus Sametime Support VCX support for Lotus Sametime Click to Call/Click to Conference and Telephony presence was previously available with the VCX on Power Platform only. Starting with VCX 9.0, this support has been extended to the VCX Connect and VCX Enterprise products, as well as, Lotus Sametime 8.0 and Domino 8.0 support running on Microsoft Windows Server 2003 and 2008.

Enhanced Call Pickup Groups The maximum number of Call Pickup Groups has been increased from 100 to 200.

3Com 3103 Phone Select Button In VCX 9.0, the 3Com 3103 Phone select button operation has been enabled across all menu options in a consistent manner similar to NBX.


March 31, 2011 of 85

Enhanced Busy lamp Field (BLF) With VCX 9.0, the BLF feature has been enhanced to allow a user to configure up to 12 phones so that corresponding LEDs will glow when the configured phones are busy. The BLFs can be configured by provisioning.

While 3102B type phones display/support 12 BLFs, the 3102A type phones support only 9 BLFs. Earlier, only up to 9 BLFs were allowed even for 3102B type phones.

Lock/unlock Feature VCX 9.0 now supports the lock/unlock feature across all platforms. The lock/unlock feature allows a user to lock a 3Com phone to prevent outgoing external calls and to unlock a 3Com phone, if it is already locked.

However, the lock/unlock feature allows the following outgoing calls even when locked:

Emergency calls;

Internal calls within the VCX or as defined in the Class of Service (COS) assigned to the phone.

Class of Service (COS) Settings: The user can disallow all outgoing external calls by locking the phone, when the phone profile contains the COS “Internal” element. But if the phone profile has default COS with “*” pattern, then the VCX will allow all outgoing calls even if the phone is locked.

Note: The administrator does not have permission to delete the “Default COS” or “Internal Elements” from the VCX provisioning interface.

To lock/unlock phone, it is mandatory to have the password. If a phone is locked, corresponding mapped LED will glow and a “lock” symbol will be displayed on the phone screen. A 3Com phone can be locked in the following ways:

By dialing the feature code;

By selecting feature mapped button;

By using the phone menu.

FAX as PDF support The FAX format may be configured system-wide for PDF or TIF using the AppMon utility (parameter name FAX_format_type). The default setting for the format is TIF. IP Messaging needs to be restarted after making the format setting changes described above.

Refer to the IP Messaging Module Operations and System Administration Guide for more information on configuration options.

Auto-Attendant Enhancement The Web User Interface allows the importing of Auto-Attendant and Music-On-Hold audio files. It allows audio files formatted in the IP Messaging required audio format (ccit u-law, 8 bit, mono).

Voicemail CODEC Configuration The Web User Interface can display the current codec selected for use with voicemail. It can also allow the selected codec to be changed and provide an option to convert the format of the audio prompts and voicemail messages to match the selected codec.


March 31, 2011 of 85

Voicemail Language Pack Configuration In VCX 9.0, the Web User Interface supports the configuration of Voicemail Language Pack:

The Web User Interface provides support for uploading, installing and activating a voicemail language pack on an IP Messaging system;

The Web User Interface can display which language packs have been installed on the system and display if the pack has been “activated” for use by the voicemail system;

The Web User Interface provides support for deactivating and removing a voicemail language pack from the system.

NOTE：The US English G.711U language pack is pre-installed by default and cannot be deleted or deactivated from the VCX system.

IP Messaging Web User Portal In VCX 9.0, the IP Messaging web user portal integrates with the IP Telephony portal so that the user does not need to switch web portals depending on what operation he is doing.

The web UI user portal can display the voicemail available on a user’s mailbox and allow the user to play the voicemail message on the user’s PC.

Global Voicemail Central Server Subscribers The Global Voicemail central server has been enhanced to allow subscriber mailboxes to reside in the same system. In VCX 9.0, the Web User Interface can identify at a glance which voice mailboxes are local to the Global Voicemail Central Server and which ones are shown from being part of a Global Voicemail.

Localization This release includes support for languages shown in the following table.

Voice Prompts

User and Admin Guides

User Web Interfaces

Admin Web Interfaces

User Online Help

Admin Online Help

US English Yes Yes Yes Yes Yes Yes

CA French Yes No US English US English US English US English

LAT Spanish Yes No Yes Yes Yes Yes

Brazilian Portuguese

Yes No Yes US English Yes US English

UK English Yes US English US English US English US English US English

Castilian Spanish

Yes No Yes US English Yes US English

Parisian French

Yes No Yes Yes Yes Yes

German Yes No Yes US English Yes US English

Italian Yes No Yes Yes Yes Yes

Chinese Simp. Yes Yes Yes Yes Yes Yes

Dutch Yes No Yes US English Yes US English


March 31, 2011 of 85

Russian Yes No Yes US English Yes US English

Korean Yes No Yes US English Yes US English

Australian English

Yes US English US English US English US English US English

Phone Identification In VCX 9.0, the following phone details on each device that is registered as a contact to an extension number are displayed on the web User Interface:

Device’s model number

MAC address

Download image version

The phone’s Serial Number (Note: The supported phones include 3102B, 3101B, 3101 Speaker B, 3105B and 3103A)

VCX Phone Profile Settings for Desktop Communicator In VCX 9.0, the following new phone profile settings were added to allow the new 3Com Desktop Communicator and 3Com Desktop Communicator Outlook Edition softphone to register successfully. Without these settings enabled and the appropriate licenses, the softphone will fail to register.

Profile must select either:

Enable Softphone DC

Enable Softphone DC Outlook Edition

VCX System Configuration In VCX 9.0, the System Information screen can display all configuration information provided to the system when it was first configured or reconfigured – constrained to each server only.

VCX System Statistics In VCX 9.0, the System Information screen can display the system activity data that is collected from the Linux operating system. The displayed information includes CPU utilization, swapping statistics, memory statistics, I/O and transfer rate statistics.

SIP Trunking VCX includes support for SIP Trunking as described in the following table:

Internet Telephony Service Provider (ITSP)

Carrier Equipment VCX Release

Comments

Bandwidth.com Level(3) Ingate (SIParator family, Version 4.7.1)

9.0.17 SIParator equipment is available through the 3Com/ON™ program or through calling Ingate Systems directly.


March 31, 2011 of 85

Known Anomalies in VCX Release 9.8.15 Microsoft OCS

One OCS endpoint cannot make a call with VCX Hunt Group or ACD Group.

Lotus Sametime

In some conditions, the three-way call users’ line status display abnormally on Sametime client. (ID RTD37358)

Sometimes the Preferred Device icon on Sametime 7.5/8.0 clients disappeared. This is an occasional failure between Sametime Connect and Sametime server. (ID RTD38762)

Workaround for ID RTD38762: Log out and log in again.

Domino Server

On occasion, the last new or modified user in Domino server can not be immediately synchronized to VCX directory. This user can be synchronized later (about several minutes). It is recommended that you try the command Tell LDAP ReloadSchema to manually refresh the schema from the Domino console. (ID RTD38678)

EPICCenter and eXchange

In a given condition, the calls will get no-way audio when dialing an EPIC IRN from an Agent phone that is registered to the VCX secondary server. When VCX primary server status changes from unavailable to available, Agent phones will be re-registered to the primary server in a special switch time that is according to the interval of keepalive between the VCX server and the phones. During this time, some Agent phones are registered to primary server and the others are still on secondary server. Meanwhile, if dialing an EPIC IRN from an Agent phone that is registered to the VCX secondary server, the Agent phone that is registered to the VCX primary server will ring but when the agent answers the call you will get no-way audio. (ID 0779254)

Workaround for ID 0779254: If this condition occurs, the phones, which remain connected to the secondary server, can logout and login again to re-connect to the primary.

List of Resolved Problems Resolved Problems in VCX Release 9.8.15

Call Processing

VCX doesn't parse SDP correctly causing one-way audio. (ID 0912759)

VCX Call P cores when receiving an INFO sip message from FXO gateway. (ID 0912635)

CallP does not respond to UPDATE SIP (without session-expires). (ID 0912985)

Callp returns 480 Temporarily Unavailable if no caller ID from sip trunk provider. (ID 0912995)

Caller Name not displayed on Phone from MSR. (ID 0912562/0912769)


March 31, 2011 of 85

IP Messaging

IP Messaging 9.0.17 coring in app.dir directory. (ID 0871660)

Bridge Transfer from an Auto Attendant results in one-way audio. (ID 0912679)

When login to IP Messaging server via Cygwin, the Blue GUI raise errors – “Too many attempts for update script. Connection denied.” (ID 0880403)

VCXData

VCXData backup restore error on region primary for one branch. (ID 0912604)

Hunt Group

iQNet clients, other than the answering client, are not able to clear hunt group calls. (ID 0912698)

Daylight Savings Time changes can cause the Hunt Group schedule to be off by one hour. (ID 0836827)

VCX MIB

When iMC discovers a VCX telephone, the VCX system incorrectly sends VCX MAC address to iMC system. (ID 0896004)

VCX Installation/Configuration

TrustedEndPoints are lost after vcx-reconfigure whether adding by Web or CLI. (ID 0912791)

VCX-reconfigure don't allow valid netmask when configure SNMP Management. (ID 0913012)

vcx-raid-setup FAILS when executed on an HP DL360. (ID 0913162)

3Com Telephones

RTP payload 98(AMR-WB) is being offered twice in the same SDP with different attributes. (ID 0811869)

3102A Phones do not easily fail back to a branch when it is available again. (ID 0879213, 0912765)

Cannot dial non-emergency number with Pattern 9110345XXX without the Phone dialing first 3-digits. (ID 0886124, 0912711)

Resolved Problems in VCX Release 9.5.13 Call Processing

Diversion Header Exclusion (DHE) feature needed in VCX 9.0 or higher. (ID 0818817)

VCX 9.0.17 route priority ignored when call processor is listed. (ID 0815008)

IP Messaging

Future Delivery Messages re-occur as blank messages after being deleted. (ID 0800781)

IPM Web Interface - Misleading screen. Web for AA speak file selection appears on two screens, but only works on one screen to set the prompt. (ID 0843681)


March 31, 2011 of 85

Global Directory

Changing data in Active Directory followed by VCX LDAPSYNC update deletes non registers VCX Users. (ID 0824878)

VCX Installation/Configuration

Cannot bail out of vcx-reconfigure to stop services on secondary before replication is dropped. (ID 0826085)

VCX 9.0.17 Enterprise limit of 24 trusted end points. (ID 0832848)

3Com Telephones

VCX connect 9.0.17 phones show missed calls for huntgroup calls. (ID 0807438)

RTP payload 98(AMR-WB) is being offered twice in the same SDP with different attributes. (ID 0811869)

Change the payload type from 96 to 101. (ID 0826749)

Transfer to Voice Mail does not work when (Transfer, *441*<destination>, Transfer) is used. (ID 0829879)

VCX - Dashes in the LCD on all calls - Internal, External, in/outgoing, for US region. (ID 0840529)

3102B Phones intermittently Hang/Crash 'Network msg queue overflow'. (ID 0823313)

Billing Server

IPM CDR issue – no data in mailbox usage stat reports. (ID 0834021)

License

VCX Secondary Blue GUI error: Not enough licenses for existing mailboxes: short 13 licenses. (ID 0836828)

Adhoc Conference

Prevent error raise limits Error Operation not permitted (1) Failed to set maximum core file size. (ID 0823769)

Text to Speech

Text to Speech is not working in Latin American or Mexican Spanish. (ID 0820150)

VCX Documents

VCX Connect 100 FTC import files not working. (ID 0829888)

Resolved Problems in VCX Release 9.0.17 Call Processing

Routing issue related to pattern sorting. (ID 0674045)

If the called number beginning with 890, 3Com phone will show an anonymous call. (ID RTD36486)


March 31, 2011 of 85

Applications that only do G.729 can't call a HG. (ID 0722024)

DHCP scope Changed. Notifications not being sent to 3com 3105 console. (ID 0643930)

NOTE: When the IP address is changed, all active calls will be canceled. 3Com recommends that customers don’t adjust their DHCP settings during peak hours.

BLF does not work if call is through Ingate SIParator box. (ID 0640818)

Telephony Services completely stopped because clocks drifted. (ID 0638643)

3com phones don't show caller id name from sip trunks. (ID 0642915)

IP Messaging

IP Messaging bug when dialing out certain SIP trunk providers. (ID 0640826)

IPMSG Music on Hold Web Provisioning Screen not enhanced for the new Random MOH option. (ID 0643133)

IPM does not save personal greetings when German language pack is used. (ID 0644444)

Faxes are received as voice mail messages (wav files) instead of image tiff files. (ID 0654412)

IP Messaging VPIM sends FROM field as IP address; rejected by other vendors. (ID 0637070)

UMS doesn't send a SIP ACK in certain cases when dealing with SIP Trunking device. (ID 0619795)

If the ums_cbipi.log is too large, the UMS cannot start. (ID RTD37381)

IPMSG "Space" file missing in Codec directory tree. (ID 0706652)

Unchecking the box of Enhanced Voicemail Security, the function has been disabled. (ID RTD37537)

Global Directory

The multi records of one phone number exist in global directory in branches. (ID RTD37538)

Global Directory Web interface issue. (ID 0719993)

VCX Provisioning

Adding Trusted Endpoints in Web Interface causes error after initial install when adding endpoint. (ID 0667481)

VCX Provisioning has a problem with DELETE or EDIT for the Music on Hold numbers. (ID 0689512)

VCX Installation

Cannot successfully complete vcx-raid-setup on a clean installed 7.1.21c system. (ID 0661593)

vcx-config-backup script missing after upgrade to 7.1.21c. (ID 0688200)

Cannot log in server when customer name with the character ' or ". (ID RTD37825)


March 31, 2011 of 85

Branch VCX server disconnected, dropReplication is failed. (ID RTD38439)

VCX Linux

Some scripts missing (erasePartitionTable script, diskCopy script). (ID 0663330/ID 0663333)

The Power ON issue has been fixed. (ID 0665146)

7.1.21c USB port does not work. (ID 0678563)

In 7.1.21 there Missing entries in remoteCli for show siplog. These entries are present in 7.1.16c. (ID 0685991)

Enabling UPS Monitor fails (Could not start upstools) using CLI: vcx-ups-setup –enableupstools. (ID 0643097)

3Com Telephones

Dual DHCP servers cause Phones in VCX 7.1.16c system to fail to attain IP addr. (ID 0645776)

Billing Server

VCX - CDR Billing merge XML's missing transfer leg of PSTN call but info is in the ACCTXML files. (ID 0638646)

License

Remove the script of licensestatus from VCX 7.1. (ID 0663331)

Adhoc Conference

Meet Me Conference name does not get displayed on the Phone LCD when starting or during a Conference. (ID 0658054)

Upgrading to VCX release 9.8 IMPORTANT: All servers in a VCX system must be running the same version of the VCX software. Once you upgrade the region servers, the branch servers should be upgraded as soon as possible to maintain all features and functionality between the branch and the region. The same constraint applies in a multi-region configuration. Similarly, before you add a new server to an existing system, you must ensure that the new server is running the same VCX software version as the other servers in the system. For detailed instructions on how to upgrade your VCX system to Release 9.8, see Appendix A to G, at the end of these release notes.

IMPORTANT: For VCX 8.0.4e, you can only upgrade to VCX Release 9.8 through Command Line Interface (CLI).

For VCX Enterprise Server, you can upgrade to VCX Release 9.8 from the following VCX releases:

− From any release of VCX 7.0.x, you must first upgrade to VCX release 7.1.16c, and then upgrade to 9.8


March 31, 2011 of 85

− From VCX 7.1.16c or later VCX version, you can upgrade directly to 9.8; any other VCX 7.1.x release, you must first upgrade to VCX release 7.1.16c, and then upgrade to 9.8

− The known and verified upgrade path for VCX Enterprise server shown below:

Figure 1 Upgrade path for VCX Enterprise server

For VCX Connect Server, you can upgrade directly to VCX Release 9.8 from the following VCX releases:

− VCX Connect Release 8.0.4e

− VCX Release 9.0.17 or later

− The known and verified upgrade path for VCX Connect server shown below

Figure 2 Upgrade path for VCX Connect server

Note 1: The following VCX Release 9.0/9.5/9.8 licensing considerations:


March 31, 2011 of 85

− If you upgrade VCX system from VCX 7.1/8.0 or older version to VCX 9.0/9.5/9.8, before upgrading, please purchase and install the appropriate RTU server license for the VCX products first, otherwise the VCX system will not start up properly and you may not have access to all the functionality.

− The following new license classes are supported in VCX 9.0 and higher: Basic V9Plus license, Desktop Communicator Softphone License, Desktop Communicator Outlook Edition Softphone License and ACD Agent License.

− In VCX 9.0 and higher, VCX Connect server software includes built-in a license key for IP Telephony and IP Messaging Server RTU License, 4 Entry phones, 25 Business phones, 25 voice mailboxes, 25 Convergence Center Client soft-phones, and 25 Desktop Communicator soft-phones.

− All VCX systems come built with 2 ACD Agent try and buy demo licenses. The ACD Agent demo licenses are just for trial purposes and cannot be deleted, shared with or transferred to another VCX Connect. When a purchased ACD Agent license is installed into the VCX system, the ACD demo licenses will be overwritten with the purchased amount.

− For information on how to obtain a license for a new server, contact your authorized 3Com Reseller.

Note 2: When you upgrade from 7.0 or 7.1 to 9.0/9.5/9.8, VCX Enterprise system necessarily experiences downtime resulting in a loss of telephony and messaging services. For detailed information, please refer to the appendix at the end of these release notes.


March 31, 2011 of 85

Related Documentation For the most up-to-date VCX product documentation:

1) Go to http://csoweb4.3com.com/vcx/vcx_doc.cfm

2) Select the appropriate VCX software release revision and desired document.

Copyright © 2011 3Com Corporation. All Rights Reserved.

3Com and the 3Com logo are registered trademarks of 3Com Corporation or one of its subsidiaries. Unless otherwise indicated,

3Com registered trademarks are registered in the United States and may be registered in other countries.

Other brand and product names may be registered trademarks or trademarks of their respective holders.

Rev VCX-All 31-Mar-2011

http://csoweb4.3com.com/vcx/vcx_doc.cfm


March 31, 2011 of 85

A VCX version 9.8 upgrade overview This appendix provides an overview of the procedures required to upgrade a VCX server from previous software version to version 9.8. This appendix includes the following topics:

Provisioning Restrictions during an Upgrade

Preliminary Considerations

Post-Upgrade Consideration

About the VCX System Administration Web Interface

An upgrade operation transitions a server from one previous software release to a newer one. An upgrade preserves existing system state information, including configuration and provisioning data, and makes it available in the new release. These appendixes assume the VCX system is successfully operating at the older version before you perform the upgrade.

All servers in a VCX system MUST run the same version of VCX software. This requirement has the following implications:

You cannot upgrade or rollback one component in a VCX system and not upgrade or rollback the other components.

You cannot upgrade or rollback one VCX server and not upgrade or rollback the other VCX servers.

If you add a second server to an existing VCX system, the new server (secondary) must be installed with the same version of the VCX software running on the existing (primary) server.

With VCX software version 8.0 or later release enhances the server software upgrade process with the following improvements:

Zero-minute Downtime — Enable the availability of basic telephony and messaging services during an upgrade. This allows a phone to use the secondary call processor while the primary is upgraded. However, while telephone service is maintained, there are provisioning restrictions (See Provisioning Restrictions during an Upgrade). Note that, zero-minute downtime is only possible,

If your VCX configuration includes redundant servers.

If the current VCX system which you prepare to upgrade also supports zero-minute downtime feature. For example, when you upgrade from 7.x to 9.8, the VCX system necessarily experiences downtime resulting in a loss of telephony and messaging services because VCX version 7.x doesn’t support zero-minute downtime feature, but when you upgrade from 8.0/9.0/9.5 to 9.8, the basic telephony and messaging services are maintained during an upgrade.


March 31, 2011 of 85

Although basic telephony and messaging services are maintained during an upgrade, we strongly recommend that you perform an upgrade during OFF-PEAK hours to minimize disruption and feature-use restrictions.

Auto rollback — Built-in rollback capability enables the system to restore the previously active version of VCX software if an upgrade fails. This feature eliminates the need to perform backups before upgrading. However, we strongly recommend that you regularly backup your VCX configuration and provisioning databases.

On-demand Software Rollbacks — Enables you to resume use of a previous installed version of VCX software from the currently installed and running version.

Note that, this is a rollback, not a downgrade: configuration and database modifications made while running the newer version are not preserved. The rollback restores the system to a state as close as possible to that which existed when the previous installed version was last running, including configuration settings, operating system version, database version, and installed phone patches.

Provisioning Restrictions during an Upgrade

With VCX software version 8.0 or later release, for redundant VCX systems, zero-minute downtime ensures that the basic telephony and messaging services are maintained during the software upgrade to each server.

Although basic telephony and messaging services remain operational, changes to system and user data are restricted during the upgrade to preserve database integrity. These restrictions include to changes to user data and related configurations that fall into one of the following categories:

Changes that are not allowed. The following are not allowed:

Provisioning changes made through a VCX or IP Messaging provisioning interface. For example, you cannot add a telephone extension during an upgrade.

User management modifications made using the user-MAC command.

Database schema drop operations.

Database replication drop or setup operations.

Changes that are allowed and included in the upgraded database schema. The following changes are allowed because they are critical to core telephony:

Phone registrations

Emergency contacts

ELIN (Emergency Location Identification Number) usage state

The following changes are allowed through the Telephone User Interface (TUI) on a telephone:

Hunt Group membership status

Call logs

Changes that are allowed but not included in the upgraded database schema. These changes include all operations that can be performed through the TUI except hunt group membership status change and call log modifications. For example, if a user adds a personal speed dial number through the TUI during an upgrade, the number is not stored in the upgraded database.


March 31, 2011 of 85

Preliminary Considerations

Prior to performing an upgrade, you should note the following:

IMPORTANT: If you upgrade VCX system from VCX 7.1/8.0 or older version to VCX 9.8, before upgrading, please purchase and install the appropriate RTU server license for the VCX products first, otherwise the VCX system will not start up properly and you may not have access to all the functionality.

IMPORTANT: You’d better upgrade a server from a locally attached console because the upgrade procedure includes a reboot of the upgraded server. You can perform an upgrade remotely (using a secure shell client, for example), but you should be aware of the following considerations:

You will be logged out when the reboot occurs.

When you log back in, a system alert typically notifies you that the upgrade is still in progress. If you do not see an alert, you can check the upgrade status by entering the command,

vcx-switchversion --status

IMPORTANT: VCX software version 8.0 or later includes an auto-rollback feature. This built-in rollback capability enables the system to restore the previously active version of VCX software if an upgrade fails. This feature eliminates the need to perform backups before upgrading (required in previous VCX releases). However, we still strongly recommend that you perform backups of your VCX system on a regular basis, for example, weekly. These backups should include configuration, provisioning database, and voicemail database content. IMPORTANT: When run on a redundant VCX system, the upgrade procedure automatically stops database replication. Before starting the upgrade process on a redundant system, check replication status to make sure it is NORMAL. From VCX 9.5 systems, the upgrade process will check the replication status automatically. If you want to check replication status manually, login as ‘cworks’ and execute the following command before the upgrade process:

cd /opt/3com/VCX/vcxdata/bin

./checkReplication

The returned status should be NORMAL. If replication errors need to be cleared, enter the following command:

./deleteReplicationErrors

CAUTION: Do not attempt an upgrade if there are replication errors that cannot be deleted.

Post-Upgrade Consideration

The VCX 9.8 release includes new features that require additional fields on existing VCX Administrator web configuration pages. The new fields are configured with default values that enable a VCX system to function as it did prior to the upgrade. However, you may want to reconfigure the default values to take full advantage of the new features.

VCX Administrator web configuration pages with new fields include:

Microsoft OCS & Microsoft Exchange Integration;


March 31, 2011 of 85

Simultaneous Ringing Feature;

ACD License Enhancement;

VCX Extension Enhancement;

Background/Screen saver Image Enhancement.

Refer to the VCX Administration Guide for more information on configuration options.

About the VCX System Administration Web Interface

The VCX System Administration web interface supported in VCX release 8.0 or later, provides access to a suite of system management and maintenance applications. You can use these applications to perform routine tasks such as VCX configuration backup and restore, license management, and upgrade VCX server software.

IMPORTANT: For VCX 8.0.4e, you can only upgrade to new VCX Release through Command Line Interface (CLI).

To access the VCX System Administration interface:

1. In a web browser address bar (Internet Explorer 6.0 or higher, or Firefox 2.0 or higher), enter the IP address of the VCX server you want to manage.

The 3Com VCX Networked Telephony Solution main page appears.

2. Click VCX System Administration.

The VCX Server Administration login dialog box appears.

3. Enter the correct username and password, and click Submit.

The System Administration interface appears. The default page, System Information, displays VCX configuration information for a server. The second page lists the VCX components (and software version of each component) running on the VCX server.

4. On the left side of the page, move the mouse pointer over the main menu and click the appropriate option.

For more information, see the VCX System Administration interface online Help.


March 31, 2011 of 85

B Upgrading VCX Enterprise Server Software from V7.1 to V9.8 This appendix describes the procedures required to upgrade a VCX Enterprise system running VCX software version 7.1 to software version 9.8.

IMPORTANT: Before you begin the upgrade procedures on the Region servers, ensure the services must be stopped both on Region and Branch servers.

IMPORTANT: If you cannot upgrade all VCX region and branch servers at the same time, after the new version is active on the region primary and secondary servers, you can start the services of region and branch servers by command “service vcx start”. Although basic telephony and messaging services are maintained during the upgrade, you should upgrade the branch servers as soon as possible to maintain all features and functionality between the branch and the region.

CAUTION: During the upgrade, the global directory synchronization has been limited. When one VCX server has been upgraded to VCX 9.5/9.8, the global directory services will be activated automatically. But the global directory services of the servers, which have not been upgraded to new VCX version, will still be limited until these VCX servers are upgraded to the same VCX version. For detailed information, please refer Global Directory Enhancement of New Features in Release 9.5.13.

This appendix includes the following topics:

Verifying Software Versions

Upgrading a VCX Enterprise System With Two Servers

Upgrading a VCX Enterprise System with Region and Branch

Upgrading a Legacy VCX Enterprise System with Four Servers

Upgrading a Classic VCX Enterprise System step by step

Upgrading an Expand VCX Enterprise System step by step

This appendix describes how to perform an upgrade from VCX version 7.1 to version 9.8. This upgrade must be performed using the VCX Command Line Interface (CLI). Once the new VCX release is installed, subsequent upgrades may be performed using either the CLI or the System Administration web interface (see About the VCX System Administration Web Interface).

CAUTION: Before the upgrade process, please read the Appendix A carefully.


This section describes how to verify the software versions of individual components and entire releases.


March 31, 2011 of 85

Verifying Component Software Versions

To verify what the component software versions are:

1. Log onto the VCX system as root.

2. Enter this command:

vcx-showcomponents

This lists all of the components and their software versions that comprise the current running assembly.

Verifying Release Software Version

For any version of VCX software, you can determine the release running on the system by following these steps:


2. Enter the following command:

vcx-listversions

This command returns a list all of the installed releases and indicates the running VCX version, for example:

7.1.16c 2009-Jun-24 active

Upgrading a VCX Enterprise System with Two Servers

Follow the procedure in this section to upgrade a VCX system with two servers (primary server, secondary server, and no branch servers) from VCX software version 7.1 to version 9.8.

CAUTION: The upgrade process synchronizes software running on the primary server and the secondary server — you must upgrade both at the same time. Start the upgrade on the primary server, and then start the process on the secondary server.

The upgrade process stops database replication automatically. You must, however, manually restart replication when the upgrade process has finished on both servers.

To upgrade a redundant, two servers system:

1. Log in as root on the primary server and on the secondary server.

2. Obtain the oracle-10.2.0.4-1.i386.rpm Oracle upgrade file. Place a copy of the file in the /opt/installtemp directory on the VCX servers. You MUST install this version of the Oracle database before upgrading to the new VCX version.

3. Enter the following commands on each server to install the new version of Oracle:

cd /opt/installtemp

vcx-install oracle-10.2.0.4-1.i386.rpm

4. Obtain the vcx-x86-x.tar software upgrade file. Place a copy of the file in the /opt/installtemp directory on the VCX servers. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.

5. Enter the following command on each server to untar the software upgrade file:


March 31, 2011 of 85

tar xvf vcx-x86-9.8.15.tar

6. Enter the following commands on each server to install the new version of VCX software:

cd upgrade-9.8.15

./install-upgrade

The upgrade requires a new operating system version. The system prompts you to confirm the operating system installation and indicates which disk partition will be used after the upgrade. Press Enter at the prompt.

The system displays several status messages. The last two messages are:

----------------- Installation Completed Successfully ----------------

----------------- VCX version 9.8.15 is now available -----------------

7. Stop VCX services, first on the primary server and then on the secondary server by entering the following command:

service vcx stop

8. Install the license for VCX version 9.8 on primary server and secondary server, please login as root and enter the following commands:

cd /opt/installtemp

vcx-licenseinstall <license key filename>

CAUTION: Before installing the license for new VCX version, please ensure that you have already made a backup for the OLD license file and clear up the directory /opt/3com/licenses.

9. Switch to the new software version by entering the following command on the primary VCX server, at one time on the secondary VCX server:

vcx-switchversion 9.8.15

Note that, as part of the upgrade process, VCX will do some self checking to ensure the current VCX system can be upgraded to new VCX version:

If you upgrade from 9.0 or older version to VCX 9.8, upgrade process will first disable the Global Directory synchronization. When the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the global directory services have been disabled before the upgrade, you need reactivate the services manually.

The IP messaging service will be started automatically during the upgrade process.

Upgrade process will check the database replication and try to clear the replication errors. If there are replication errors that cannot be deleted, the upgrade process will be failed.

Upgrade process displays several status messages and determines whether the current configuration is valid for the new VCX version.

If the upgrade requires new configuration data (because the VCX upgrade software includes new components), the upgrade process prompts you for the required information.

And then, the upgrade process continues the version switch and reboots the VCX server. After the reboot process completes, the system starts VCX services.


March 31, 2011 of 85

10. The upgrade process will take about 20 to 60 minutes. After each server has completed the restart process, verify that the upgrade has occurred by entering this command on each server:

vcx-listversions


9.8.15 2011-Jan-25 active

7.1.16c 2009-Jun-24 installed

If the new version is not the active version, please wait for a while and reenter the command. The updated version must be active before proceeding. When the new version is active on both the primary server and secondary server, you can enable database replication.


service vcx stop

CAUTION: We strongly recommend you stop VCX services before setting up the database replication procedure.

12. Set up replication between primary and secondary by entering the following commands on the primary server:

su - cworks


./setupReplication

13. When replication setup is complete and status is reported as NORMAL by command “./checkReplication”, enter the command “exit” to exit the cworks account and return to the root account.

14. Start VCX services on the primary server, then on the secondary server by entering the following command:

service vcx start

Upgrading a VCX Enterprise System with Region and Branch

Follow the procedure in this section to upgrade a VCX Enterprise system with Region servers and Branch servers from VCX software version 7.1 to version 9.8.

CAUTION: Before you begin the upgrade procedures on the Region servers, ensure the services must be stopped both on Region and Branch servers.

For branch servers, the services must be stopped during the upgrade procedures on the Region servers. But the database replication need not be dropped manually. During the upgrade process when replication must be dropped the upgrade process takes care of that for you. But the upgrade does require that you manually set up database replication on branch server after you switch to new VCX version.


March 31, 2011 of 85

To upgrade a Classic, Region and Branch servers:

1. Log in as root on the Region and Branch servers.

2. Obtain the oracle-10.2.0.4-1.i386.rpm Oracle upgrade file. Place a copy of the file in the /opt/installtemp directory on the VCX servers. You MUST install this version of the Oracle database before upgrading to the new VCX version.


cd /opt/installtemp


4. Obtain the vcx-x86-x.tar software upgrade file. Place a copy of the file in the /opt/installtemp directory on the VCX servers. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.




cd upgrade-9.8.15

./install-upgrade



----------------- Installation Completed Successfully ---------------


7. You MUST upgrade region servers first. Before you begin the upgrade procedures on the Region servers, the VCX services must be stopped both on Region and Branch servers by entering the following command:

service vcx stop


8. You MUST install the license for VCX version 9.8 on primary server and secondary server:

cd /opt/installtemp







March 31, 2011 of 85



If the VCX system has branch servers, upgrade process will prompt you to stop the VCX services on these branch servers.






vcx-listversions


9.8.15 2011-Jan-25 active


If the new version is not the active version, please wait for a while and reenter the command. The updated version must be active before proceeding.


service vcx stop


12. Set up replication between primary and secondary server by entering the following commands on the primary server:

su - cworks


./setupReplication



March 31, 2011 of 85

NOTE: If you cannot upgrade all VCX servers at the same time, after the new version is active on the Region servers, you can start the services of Region and Branch servers by command “service vcx start”. Although basic telephony and messaging services are maintained during the upgrade, you should upgrade the branch servers as soon as possible to maintain all features and functionality between the branch and the region. However, you should not run vcx-config-restore on any of the servers until all Region and Branch servers have been upgraded.

14. When the new version is active on the Region servers, you can switch to the new software version by steps 9 and 10 on the Branch servers:


vcx-listversions

When the new version is active on both the Region servers and Branch servers, you can enable database replication on Branch server.

15. Set up replication between primary server and Branch servers by steps 12 and 13 on the Branch server.

16. Install the licenses for 9.8 on Branch servers.

17. Start VCX services on the Region servers, then on the Branch servers by entering the following command:

service vcx start

18. You MUST modify the firewall software of IP Messaging region server to permit traffic from the branch servers. Log in as root on Primary and Secondary server. Modify the firewall for Branch servers by the following command：

modfw –p ums allow <IP address for the Branch server>

19. After all VCX servers (regions and branches) within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. But if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.

Upgrading a Legacy VCX Enterprise System with Four Servers

Follow the procedure in this section to upgrade a VCX Enterprise system with four servers (2 IPT, 2 IPM) at a single site from VCX software version 7.1 to version 9.8.

NOTE: You can check whether the Global Directory services are active or not in the VCX Central Management Console on region server. Branch servers will be activated automatically with their region server, so you need only to check Global Directory services on the region server. If any one of the servers fails to activate the Global Directory, the warning message will be shown on ‘Global Directory’ page:

WARNING: Global Directory Synchronization Services have been disabled due to a recent system upgrade. Please DO NOT restart the service until ALL VCX servers (regions and branches) within your solution have been upgraded. While directory updates are not being synchronized, the IP Telephony and IP Messaging services are still available. To REACTIVATE the synchronization, please login as 'cworks', and execute the command '/opt/3com/VCX/vcxdata/globaldir/bin/activegudd_all.pl'.


March 31, 2011 of 85

To upgrade a VCX Enterprise system with four servers:

1. Log in as root on IPT Primary and IPT Secondary server.

2. Obtain the oracle-10.2.0.4-1.i386.rpm Oracle upgrade file. Place a copy of the file in the /opt/installtemp directory on the IPT servers. You MUST install this version of the Oracle database before upgrading to the new VCX version.


cd /opt/installtemp


4. Log in as root on all VCX servers.

5. Obtain the vcx-x86-x.tar software upgrade file. Place a copy of the file in the /opt/installtemp directory on all VCX servers. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.




cd upgrade-9.8.15

./install-upgrade





8. Upgrade IPT Primary and IPT Secondary server. During the upgrading for IPT servers, you can upgrade IPM servers at one time. (See Upgrade IPM Primary and IPM Secondary server.)

9. Install the licenses for VCX version 9.8 on IPT Primary and IPT Secondary:

cd /opt/installtemp



10. Switch to the new software version by entering the following command on the IPT Primary server, at one time on the IPT Secondary server:



If you upgrade from 9.0 or older version to VCX 9.8, upgrade process will first disable the Global Directory synchronization. When the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the


March 31, 2011 of 85

global directory services have been disabled before the upgrade, you need reactivate the services manually.







11. The upgrade process will take about 20 to 60 minutes. After the IPT Primary and Secondary server have completed the restart process, verify that the upgrade has occurred by entering this command on each server:

vcx-listversions


9.8.15 2011-Jan-25 active




service vcx stop


13. Set up replication between IPT Primary and IPT Secondary server by entering the following commands on the IPT Primary server:

su - cworks


./setupReplication

14. When replication setup is complete and status is reported as NORMAL by command “./checkReplication”, then enter the command “exit” to exit the cworks account and return to the root account.

15. Upgrade IPM Primary and IPM Secondary server.

16. You MUST install the license for VCX version 9.8 on IPM Primary server and IPM Secondary server:

cd /opt/installtemp


March 31, 2011 of 85



17. You can switch to the new software version by steps 10 and 11 on the IPM Primary server:


vcx-listversions

18. After the IPM Primary server upgrade successfully and the service is running, then switch to the new software version by steps 10 and 11 on the IPM Secondary server:


vcx-listversions

19. Ensure the services are running on all VCX servers (2 IPT, 2 IPM). If the services are not running, restart the services by entering the following command:

service vcx start

20. You MUST modify the firewall software of IPM servers to permit traffic from the IPT servers. Log in as root on IPM Primary and IPM Secondary server. Modify the firewall for IPT servers by following command, for example:

modfw –p ums allow <IP address for the IPT Primary>

modfw –p ums allow <IP address for the IPT Secondary>

CAUTION: For Expand VCX system, in the region office, you MUST modify the firewall software of IP Messaging server to permit traffic from the IP Telephony Call Processor server.



Follow the procedure in this section is an example for upgrading a Classic VCX Enterprise system step by step from VCX software version 7.1 to version 9.8.

CAUTION: Before you begin the upgrade procedures on the Region servers, ensure the

NOTE: You can check whether the Global Directory services are active or not in the VCX Central Management Console on IPT server. If any one of the servers fails to activate the Global Directory, the warning message will be shown on ‘Global Directory’ page:



March 31, 2011 of 85

services must be stopped both on Region and Branch servers.


See Figure 3. There are two Regions in this example VCX system.

R1Pri/R2Pri – Region 1/2 Primary server

R1Sec/R2Sec – Region 1/2 Secondary server

GVCS – GVCS server for the Regions

R1B1 – Region 1 Branch 1 server, is replicated to R1Pri



Figure 3 An example for a Classic VCX Enterprise System

Upgrading the Classic VCX Enterprise System step by step:


2. Obtain the oracle-10.2.0.4-1.i386.rpm Oracle upgrade file. Place a copy of the file in the /opt/installtemp directory on all VCX servers except for GVCS server. You MUST install this version of the Oracle database before upgrading to the new VCX version.

CAUTION: If the GVCS server is located on an All-in-One VCX server, you also must install this version of the Oracle database before upgrading to the new VCX version.

3. Enter the following commands to install the new version of Oracle:

cd /opt/installtemp



5. Enter the following command to untar the software upgrade file on all VCX servers:


March 31, 2011 of 85

tar -xvf vcx-x86-9.8.15.tar

6. Enter the following commands to install the new version of VCX software on all VCX servers:

cd upgrade-9.8.15

./install-upgrade

7. The upgrade requires a new operating system version. The system prompts you to confirm the operating system installation and indicates which disk partition will be used after the upgrade. Press Enter at the prompt.




8. You must upgrade GVCS server first.

a. Stop VCX service on GVCS server by command :

service vcx stop

b. Switch to new software version by entering the following command:


c. The process will take about several minutes. During this process, the server will reboot. After the servers started, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active


d. Then install a license for 9.8 on GVCS server and the service will be started automatically.

9. Then upgrade the servers of Region 1.

10. Stop VCX services by entering the following command on the R1Pri, R1Sec, R1B1 and R1B2 server:

service vcx stop

11. Install the license for VCX version 9.8 on R1Pri and R1Sec server:

cd /opt/installtemp



12. Switch to the new software version by entering the following command on R1Pri server and R1Sec server first:




March 31, 2011 of 85








13. The upgrade process will take about 20 to 60 minutes. After each server has completed the restart process, verify that the upgrade has occurred by entering this command on R1Pri and R1Sec server:

vcx-listversions


9.8.15 2011-Jan-25 active


If the new version is not the active version, wait a few minutes and reenter the command. The updated version must be active before proceeding.


14. When the new version is active on the Region servers, you can switch to the new software version by steps 12 and 13 on the Branch servers (R1B1 and R1B2 server):


vcx-listversions

When the new version is active on both the Region and Branch servers, you can enable database replication.

15. Please ensure all VCX services have been stopped before the process of database replication, first on the Region servers and then on the Branch servers by entering the following command:


March 31, 2011 of 85

service vcx stop


16. Set up the replication between R1Pri server and R1Sec server by entering the following commands on the R1Pri server:

su – cworks


./setupReplication


18. Set up the replication between the Branch servers and Primary server by steps 16 and 17 on Branch servers (R1B1 and R1B2 server).

19. Install the licenses for 9.8 on R1B1 and R1B2 server.

20. Please ensure all VCX services have been started on the Region servers and Branch servers. You can start VCX services on the servers by entering the following command:

service vcx start

21. You MUST modify the firewall software of IP Messaging region server to permit traffic from the branch server. Log in as root on R1Pri and R1Sec server. Modify the firewall for Branch servers by the following command：

modfw –p ums allow 172.31.91.43


22. Then upgrade the servers (R2Pri, R2Sec and R2B1) of Region 2 by same steps as the upgrading for Region 1.

23. After all VCX servers (R1Pri, R1Sec, R1B1, R1B2, R2Pri, R2Sec and R2B1 server) within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. But if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.

NOTE: You can check whether the Global Directory services are active or not in the VCX Central Management Console on region server. Branch servers will be activated automatically with their region server, so you need only to check Global Directory services on the region server. If any one of the servers fails to activate the Global Directory, the warning message will be shown on ‘Global Directory’ page:



March 31, 2011 of 85


Follow the procedure in this section is an example for upgrading an Expand VCX Enterprise system step by step from VCX software version 7.1 to version 9.8.



See Figure 4. This is an example for expand VCX Enterprise System.

CallProcessor – call processor server for IP Telephony

VCXData – VCX Data server for IP Telephony

IPM-Primary – IP messaging primary server

IPM-Secondary – IP messaging secondary server

Branch1, Branch2, Branch3 – branch servers of this Expand VCX Enterprise System

Figure 4 An example for Expand VCX Enterprise System

Upgrading the Expand VCX Enterprise System step by step:

1. Log in as root on all VCX servers (Region and Branch servers).


March 31, 2011 of 85

2. Obtain the oracle-10.2.0.4-1.i386.rpm Oracle upgrade file. Place a copy of the file in the /opt/installtemp directory on VCXData server and all Branch VCX servers. You MUST install this version of the Oracle database before upgrading to the new VCX version.

3. Enter the following commands to install the new version of Oracle:

cd /opt/installtemp



5. Enter the following command to untar the software upgrade file on all VCX servers:

tar -xvf vcx-x86-9.8.15.tar

6. Enter the following commands to install the new version of VCX software on all VCX servers:

cd upgrade-9.8.15

./install-upgrade

7. The upgrade requires a new operating system version. The system prompts you to confirm the operating system installation and indicates which disk partition will be used after the upgrade. Press Enter at the prompt.




8. You MUST upgrade region servers first (CallProcessor, VCXData, IPM-Primary and IPM-Secondary server).

9. Stop VCX services by entering the following command on VCXData and all Branch servers:

service vcx stop


10. You MUST install the license for VCX 9.8 on IPM-Primary and IPM-Secondary server:

cd /opt/installtemp



11. Switch to the new software version by entering the following command on VCXData server, at one time on CallProcessor and IPM-Primary server:





March 31, 2011 of 85








12. The upgrade process will take about 20 to 60 minutes. During this process, the server will reboot. After the servers started, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active



13. Switch to new software version by steps 11 and 12 on the IPM-Secondary server.

14. Install the license for VCX 9.8 on CallProcessor and VCXData server.


15. When the new version is active on the Region servers, you can switch to the new software version by steps 11 and 12 on the Branch servers (Branch1, Branch2 …):


vcx-listversions

When the new version is active on both the Region servers and Branch servers, you can enable database replication.

16. Please ensure all VCX services have been stopped before the process of database replication, first on the VCXData server and then on the Branch servers by entering the following command:

service vcx stop


March 31, 2011 of 85


17. Set up the replication between VCXData server and Branch servers by entering the following commands on the Branch server:

su - cworks


./setupReplication


19. Install the licenses for VCX 9.8 on Branch servers.

20. Please ensure all VCX services have been started on the Region servers and Branch servers. You can start VCX services on the servers by entering the following command:

service vcx start

21. You MUST modify the firewall software of IP Messaging region server to permit traffic from the branch server and IP Telephony server. Log in as root on IPM-Primary and IPM-Secondary server. Modify the firewall for Branch servers and IP Telephony Call Processor server by following command, for example:



...

CAUTION: For Expand VCX system, in the region office, you MUST modify the firewall software of IP Messaging server to permit traffic from the IP Telephony Call Processor server.


NOTE: You can check whether the Global Directory services are active or not in the VCX Central Management Console on region CallProcessor server. Branch servers will be activated automatically with their region server, so you need only to check Global Directory services on the region server. If any one of the servers fails to activate the Global Directory, the warning message will be shown on ‘Global Directory’ page:



March 31, 2011 of 85

C Upgrading VCX Software from V9.0/9.5 to V9.8 This appendix describes the procedures required to upgrade a VCX system running VCX software version 9.0/9.5 to software version 9.8.

CAUTION: During the upgrade, the global directory synchronization has been limited. When one VCX server has been upgraded to VCX 9.5/9.8, the global directory services will be activated automatically. But the global directory services of the servers, which have not been upgraded to new VCX version, will still be limited until these VCX servers are upgraded to same VCX version. For detailed information, please refer please refer Global Directory Enhancement of New Features in Release 9.5.13.



Upgrading a VCX Connect with One Server

Upgrading a VCX Enterprise/Connect with Two Servers

Upgrading a VCX Enterprise with Region and Branch



This appendix describes how to perform an upgrade from VCX version 9.0/9.5 to version 9.8. With VCX 9.0 or later, you can perform an upgrade using the System Administration web interface. (See the Appendix D of these release notes).








vcx-showcomponents




March 31, 2011 of 85




vcx-listversions


9.0.17 2009-Sep-25 active

Upgrading a VCX Connect with One Server

Follow the procedure in this section to upgrade a VCX system with one server from VCX software version 9.0/9.5 to version 9.8.

First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. For VCX Connect system, the upgrade files use the filename format vcxconnect-x86-x.tar. The variable x indicates the version of VCX software (for example, vcxconnect-x86-9.8.15.tar) that will replace the current version.

Note that, this version of the VCX upgrade process provides automatic recovery from an upgrade failure. If an upgrade fails, the auto-rollback capability enables the system to restore the previously active version of VCX software.


1. Log in as root on the server.

2. To install the new VCX version, enter the following commands:

cd /opt/installtemp

tar xvf vcxconnect-x86-9.8.15.tar

cd upgrade-9.8.15

./install-upgrade

If the upgrade requires a new operating system version, the system prompts you to confirm the operating system installation and indicates which disk partition will be used after the upgrade. If you see such a prompt, answer y. The system displays several status messages. The last two messages are:

-----------------Installation Completed Successfully-----------------

-----------------VCX version 9.8.15 is now available-----------------

3. Switch to the new software version by entering the following command on the server:




March 31, 2011 of 85




4. The upgrade process will take about 20 to 60 minutes. After the server has completed the restart process, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active

9.0.17 2009-Sep-25 installed

If the new version is not the active version, please wait for a while and reenter the command.

Upgrading a VCX Enterprise/Connect with Two Servers

Follow the procedure in this section to upgrade a VCX system with two servers (primary server, secondary server, and no branch servers) from VCX software version 9.0/9.5 to version 9.8.

CAUTION: The upgrade process synchronizes software running on the region primary server and the region secondary server — you must upgrade both at the same time. Start the upgrade on the region primary server, and then start the process on the region secondary server.

The upgrade process setup new version database replication automatically. You must, however, do not continue to the next step until the replication is complete on the new VCX version.

First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. For VCX Enterprise system, the upgrade files use the filename format vcx-x86-x.tar, for VCX Connect system, the upgrade files use the filename format vcxconnect-x86-x.tar. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.




2. To install the new VCX version, enter the following commands on both servers:

cd /opt/installtemp


cd upgrade-9.8.15


March 31, 2011 of 85

./install-upgrade














vcx-listversions


9.8.15 2011-Jan-25 active



5. After all VCX servers within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.


March 31, 2011 of 85

Upgrading a VCX Enterprise with Region and Branch

Follow the procedure in this section to upgrade a VCX system with Region servers and Branch servers from VCX software version 9.0/9.5 to version 9.8.



First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. For VCX Enterprise system, the upgrade files use the filename format vcx-x86-x.tar. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.


To upgrade a Classic, Region and Branch servers:



cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade









March 31, 2011 of 85







vcx-listversions


9.8.15 2011-Jan-25 active



NOTE: If you cannot upgrade all VCX servers at the same time, after the new version is active on the Region servers, although basic telephony and messaging services are maintained during the upgrade, you should upgrade the branch servers as soon as possible to maintain all features and functionality between the branch and the region. However, you should not run vcx-config-restore on any of the servers until all Region and Branch servers have been upgraded.

5. When the new version is active on the Region servers, you can switch to the new software version by steps 3 and 4 on the Branch servers:


vcx-listversions

6. After all VCX servers (regions and branches) within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.


Follow the procedure in this section is an example for upgrading a Classic VCX Enterprise system step by step from VCX software version 9.0/9.5 to version 9.8.


March 31, 2011 of 85

First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. Upgrade files use the filename format vcx-x86-x.tar. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.


See Figure 3. Upgrading the Classic VCX Enterprise System step by step:



cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade




3. You must upgrade GVCS server first.

a. Switch to new software version by entering the following command:


b. The process will take about several minutes. During this process, the server will reboot. After the servers started, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active


4. Then upgrade the servers of Region 1.

5. Switch to the new software version by entering the following command on R1Pri server and R1Sec server first:





March 31, 2011 of 85







6. The upgrade process will take about 20 to 60 minutes. After each server has completed the restart process, verify that the upgrade has occurred by entering this command on R1Pri and R1Sec server:

vcx-listversions


9.8.15 2011-Jan-25 active


If the new version is not the active version, wait a few minutes and reenter the command. The updated version must be active before proceeding.


7. When the new version is active on the Region servers, you can switch to the new software version by steps 5 and 6 on the Branch servers (R1B1 and R1B2 server):


vcx-listversions

8. Then upgrade the servers (R2Pri, R2Sec and R2B1) of Region 2 by same steps as the upgrading for Region 1.

9. After all VCX servers (R1Pri, R1Sec, R1B1, R1B2, R2Pri, R2Sec and R2B1 server) within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.


March 31, 2011 of 85


Follow the procedure in this section is an example for upgrading an Expand VCX Enterprise system step by step from VCX software version 9.0/9.5 to version 9.8.

First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. Upgrade files use the filename format vcx-x86-x.tar. The variable x indicates the version of VCX software (for example, vcx-x86-9.8.15.tar) that will replace the current version.


See Figure 4. Upgrading the Expand VCX Enterprise System step by step:

1. Log in as root on all VCX servers (Region and Branch servers).


cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade




3. You MUST upgrade region servers first (CallProcessor, VCXData, IPM-Primary and IPM-Secondary server).

4. Switch to the new software version by entering the following command on VCXData server, at one time on CallProcessor and IPM-Primary server:







March 31, 2011 of 85




5. The upgrade process will take about 20 to 60 minutes. During this process, the server will reboot. After the servers started, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active



6. Switch to new software version by steps 4 and 5 on the IPM-Secondary server.


7. When the new version is active on the Region servers, you can switch to the new software version by steps 4 and 5 on the Branch servers (Branch1, Branch2 …):


vcx-listversions

8. After all VCX servers (regions and branches) within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually.


March 31, 2011 of 85

D Upgrading VCX System to V9.8 (Web) This appendix describes the procedures required to upgrade a VCX System running software version 9.0/9.5 to software version 9.8 through the VCX System Administration Web Interface.


To access the VCX System Administration interface

1Upgrading VCX Software

This appendix describes how to perform an upgrade using the System Administration Web Interface. With VCX release 9.0 or later, you also can perform an upgrade using the VCX Command Line Interface (CLI). (See the Appendix C of these release notes)


CAUTION: During an upgrade, A redundant system running VCX version 8.0 or later maintains the basic telephony and messaging services during an upgrade. A standalone, single-server system necessarily experiences downtime during an upgrade.

Users also may be able to make emergency calls, or make calls to and receive calls from destinations outside of the VCX system (that is, the PSTN). This capability depends on the availability, configuration, and capacity of the media gateway (or gateways) set up in the VCX system. See the VCX Installation Guide for information on configuring a fail-over call route point. Also refer to your gateway documentation.

To access the VCX System Administration Web Interface

1. In a web browser address bar (Internet Explorer 6.0 or higher, or Firefox 2.0 or higher), enter the IP address of the VCX server you want to manage.

The 3Com VCX Networked Telephony Solution main page appears.

2. Click VCX System Administration.

The VCX Server Administration login dialog box appears.

3. Enter the correct username and password, and click Submit.

The default username is admin and the default password is besgroup. However, we strongly recommend, for security reasons, that the default passwords be changed.

The System Administration interface appears. The default page, System Information, displays VCX configuration information for a server. The second page lists the VCX components (and software version of each component) running on the VCX server.

4. On the left side of the page, move the mouse pointer over the main menu and click the appropriate option.

For more information, see the VCX System Administration interface online Help.


March 31, 2011 of 85

Upgrading VCX Software

An upgrade operation transits a server from an older software release to a newer one. An upgrade preserves existing system state information, including configuration and provisioning data, and made it available in the new release.

To upgrade the VCX server using the System Administration Web Interface:

1. Select System Software > Upgrade. See Figure 5.

Figure 5 Software Upgrade Menu

2. The System Upgrade page appears. See Figure 6.

Click Browse… to select the new VCX software version.

Then Click Upload to obtain the copy of the new VCX software version.


March 31, 2011 of 85

Figure 6 Software Upgrade Page

3. Software upgrade installation. See Figure 7.

Figure 7 Software upgrade installation

4. The System Upgrade page appears. See Figure 8.

The new software version is being installed on your VCX server. Before upgrading, please read the notes carefully, and then click OK to upgrade, or click Cancel to cancel the upgrade operation.

Click OK to continue the upgrade process.


March 31, 2011 of 85

Figure 8 Click OK to upgrade

5. Software upgrade is in progress. See Figure 9.

Figure 9 Software upgrade is in progress

6. The upgrade operation is almost complete. See Figure 10.

The upgrade process continues the version switch and, if required, reboots the VCX server. After the reboot process completes, the system starts new VCX software services.


March 31, 2011 of 85

Figure 10 The operation is almost complete


March 31, 2011 of 85

E Upgrading VCX Connect System to V9.8 This appendix describes the procedures required to upgrade a VCX Connect system running software version 8.0/9.0/9.5 to software version 9.8.

IMPORTANT: For VCX 8.0.4e, you can only upgrade to VCX Release 9.8 through Command Line Interface (CLI).

IMPORTANT: VCX Connect systems upgraded from VCX 8.0.4e may display an incorrect number of available licenses on the 'License Information' and 'License Usage' pages of the VCX Admin GUI after the upgrade to 9.0 or later. Note that customers are expected to purchase and install a 9.0/9.5/9.8 Upgrade license as part of the Upgrade process. Installing the correct 9.0/9.5/9.8 license will correct some of these errors. It is still possible, after installing the 9.0/9.5/9.8 license key, that a HIGHER number of available licenses are shown than the customer purchased (specifically Entry Phone, Business Phone, Convergence Center Client Softphone, Desktop Communicator Softphone and Mailbox licenses). This does not impact system functionality, and any customer purchased licenses are always available provided the customer installed the 9.0/9.5/9.8 Upgrade license.



Upgrading a VCX Connect System With One Server

Upgrading a VCX Connect System With Two Servers

This appendix describes how to perform an upgrade using the VCX Command Line Interface (CLI). With VCX 9.0 or later, you can perform an upgrade using the System Administration web interface. (See the Appendix D of these release notes).


CAUTION: During an upgrade, A redundant system running VCX version 8.0/9.0 maintains the basic telephony and messaging services during an upgrade. A standalone, single-server system necessarily experiences downtime during an upgrade.

Users also may be able to make emergency calls, or make calls to and receive calls from destinations outside of the VCX system (that is, the PSTN). This capability depends on the availability, configuration, and capacity of the media gateway (or gateways) set up in the VCX system. See the VCX Installation Guide for information on configuring a fail-over call route point. Also refer to your gateway documentation.




March 31, 2011 of 85





vcx-showcomponents






vcx-listversions


8.0.4e 2009-Jul-1 active

Upgrading a VCX Connect System with One Server

This section describes how to upgrade a VCX Connect system that includes a single, standalone server. First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the server. Upgrade files use the filename format vcxconnect-x86-x.tar. The variable x

indicates the version of VCX software (for example, vcxconnect-x86-9.8.15.tar) that will replace the current version.


To upgrade the VCX Connect server:

1. Log in as root.

2. To install the new version, enter the following commands:

cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade





March 31, 2011 of 85

3. Switch to the new software version by entering the following command:






4. The upgrade process will take about 20 to 60 minutes. After the system has completed the restart process, verify that the upgrade has occurred by entering this command:

vcx-listversions


9.8.15 2011-Jan-25 active

8.0.4e 2009-Jul-1 installed


Upgrading a VCX Connect System with Two Servers

This section describes how to upgrade a VCX Connect system that includes a pair of redundant servers, a primary server and a secondary server.



First, obtain a copy of the software upgrade file and place it in the /opt/installtemp directory on the VCX server. Upgrade files use the filename format vcxconnect-x86-x.tar. The variable x

indicates the version of VCX software (for example, vcxconnect-x86-9.8.15.tar) that will replace the current version.


To upgrade a redundant VCX Connect system with a primary server and a secondary server:



March 31, 2011 of 85

2. To install the new version, enter the following commands on both servers:

cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade




3. Switch to the new software version by entering the following command on the primary server, at one time on the secondary server:









4. The upgrade process will take about 20 to 60 minutes. After the system has completed the restart process, verify that the upgrade has occurred by entering this command on each server:

vcx-listversions


9.8.15 2011-Jan-25 active

8.0.4e 2009-Jul-1 installed


5. After all VCX servers within your solution have been upgraded, the Global Directory services on all VCX servers should be running as well as before upgraded. That is, when the server has


March 31, 2011 of 85

been upgraded to the new VCX version, the Global Directory synchronization will be activated automatically. Note that, if the Global Directory services have been disabled before the upgrade, you need reactivate the services manually:

NOTE: You can check whether the Global Directory services are active or not in the VCX Central Management Console. If any one of the servers fails to activate the Global Directory, the warning message will be shown on ‘Global Directory’ page:



March 31, 2011 of 85

F Switching Versions of VCX Server Software This appendix describes how to switch the version of VCX software running on a VCX server. This operation is typically used to rollback the software running on a VCX system to a previously installed version. As the example, we select VCX 7.1.16c, 8.0.4e, 9.0.17 and 9.5.13 to describe the switch version procedures.

IMPORTANT: For one VCX System with Region and Branch, you MUST roll back the Branch VCX servers first, and then Region VCX servers.

IMPORTANT: The rollback procedure uses the vcx-switchversion command, which does not remove the newer VCX version from the server. This means that you can subsequently use the same command to switch back to the newer VCX version.

IMPORTANT: If you rollback one VCX Region and Branch system running new VCX version to 7.1, you MUST set up the database replication between Region and Branch manually after the rollback process.

IMPORTANT: For VCX 7.1, only the latest VCX 7.1 version can be rolled back.

This chapter includes the following topics:

Switch Version Overview

VCX Software Rollback Considerations

Provisioning Restrictions during an Version Switch


Rolling Back VCX Enterprise System with Two Servers to 7.1

Rolling Back VCX Enterprise System with Region and Branch to 7.1

Rolling Back VCX System with Single Server to 8.0/9.0

Rolling Back VCX System with Two Servers to 8.0/9.0

Rolling Back VCX System with Region and Branch to 9.0

Rolling Back VCX System through Web Interface

This appendix describes how to switch versions using the VCX Command Line Interface (CLI). With VCX release 9.0 or later, you can also switch versions using the System Administration web interface (see About the VCX System Administration Web Interface).

CAUTION: A redundant VCX system running VCX version 9.0 or later maintains the basic telephony and messaging services during a version switch. A standalone, single-server VCX system necessarily experiences downtime during a version switch.

Users also may be able to make emergency calls, or make calls to and receive calls from destinations outside of the VCX system (that is, the PSTN). This capability depends on the


March 31, 2011 of 85

Switch Version Overview

This section provides an overview of the VCX software switch version process. There may be multiple versions of VCX software installed on one server. The VCX software upgrade process includes three basic steps:

Copy the new software version to the server.

Install the software.

Switch to the new version using the vcx-switchversion command.

Note that, unless you intentionally remove it, an older version of software remains on the server. This means you can use the vcx-switchversion command to change the running VCX software to a newer version (an upgrade) or to an older version (a rollback).

Normally, a VCX software upgrade is successful and the new version runs satisfactorily. If an upgrade is not successful, the upgrade procedure automatically rolls back to the previous version. You can, however, perform a manual, on-demand rollback to a previous version. Rolling back VCX server software has significant system implications, which are discussed in VCX Software Rollback Considerations and Provisioning Restrictions during an Version Switch.

You should also be aware of the consequences of an upgrade–rollback–switch version operation. Consider the following sequence:

1. If you upgrade from 8.0 to 9.0 or later. The upgrade operation preserves data configured in the 8.0 database.

2. You make changes to the 9.0 or later database.

3. You rollback to 8.0. The rollback operations restore the database to its 8.0 state. The 9.0 or later database modifications are lost.

4. You switch versions from 9.0 or later to 8.0. This operation restores the data configured in the 8.0 database. The changes made to the 9.0 or later database are not available.

VCX Software Rollback Considerations

This section describes the implications of switching (rolling back) the software running on a VCX system to a previously installed version.

A software rollback restores a VCX system to a state as close as possible to that which existed when the previous installed version was last running, including configuration settings, operating system version, database version, and installed phone patches.

A rollback is typically performed because an upgrade is successful but unsatisfactory.

availability, configuration, and capacity of the media gateway (or gateways) set up in the VCX system. See the VCX Installation Guide for information on configuring a fail-over call route point. Also refer to your gateway documentation.


March 31, 2011 of 85

Note the following implications of a software rollback:

A successful rollback is not possible if you have made significant configuration changes in the working version. For example, if you have run the vcx-reconfigure command, you cannot rollback to a previous version.

A successful rollback is not possible if you have run the vcx-config-reset command because this command removes all inactive versions of VCX software (there is no version to rollback to).

A successful rollback is not possible if you have run the vcx-config-restore command because this command removes all inactive database schemas (there is no available database schema for rollback operation).

Generally, configuration and database modifications made while running the newer software version are not preserved when you rollback to a previous version. However, because VCX applications can be common between VCX releases, some types of changes made running the newer release may still be present if a rollback is preformed. We strongly recommends that you not rollback after major changes have been made to the configuration of the newer version.

If you upgrade a single server VCX system from an older software version (such as 9.0, 8.0 or older) to newer VCX software version, and then convert to a redundant system by adding a secondary server, both servers must run the same new VCX software version. In this case, you cannot rollback the system to the previous VCX version because the previous VCX version is not present on the secondary server and because you have changed the system configuration from standalone (single server) to redundant (two servers).

A VCX system can configured as a single, standalone server or as a pair of redundant servers. If you are rolling back the software on a redundant system, you must rollback both servers at the same time.

If you upgrade a VCX server and subsequently implement a RAID solution on that server, you cannot rollback to a previous version.

IP Messaging does not identify voicemail messages according to the currently running version of software. Therefore, voicemail messages removed in one version cannot be recovered by rolling back to a previous version.

Provisioning Restrictions during an Version Switch

For redundant VCX system, zero-minute downtime ensures that the basic telephony and messaging services are maintained during the software version switch on each server. Although basic telephony and messaging services remain operational, changes to system and user data are restricted during the version switch to preserve database integrity. These restrictions include to changes to user data and related configurations that fall into one of the following categories:

Changes that are not allowed. The following are not allowed:

Provisioning changes made through a VCX or IP Messaging provisioning interface. For example, you cannot add a telephone extension during a version switch.

User management modifications made using the user-MAC command.

Database schema drop operations.

Database replication drop or setup operations.


March 31, 2011 of 85

Changes that are allowed and included in the database schema in the switched version. The following changes are allowed because they are critical to core telephony:

Phone registrations

Emergency contacts

ELIN (Emergency Location Identification Number) usage state

The following changes are allowed through the Telephone User Interface (TUI) on a telephone:

Hunt Group membership status

Call logs

Changes that are allowed but not included in the database schema in the switched version. These changes include all operations that can be performed through the TUI except hunt group membership status change and call log modifications. For example, if a user adds a personal speed dial number through the TUI during a version switch, the number is not stored in the resulting database.







vcx-showcomponents





2. Enter the following commands:

vcx-listversions


7.1.16c 2009-Jul-1 active

9.5.13 2010-May-20 installed


March 31, 2011 of 85

Rolling Back VCX Enterprise System with Two Servers to 7.1

Follow the procedures in this section to rollback the VCX software on a redundant VCX Enterprise system to version 7.1.

CAUTION: The rollback procedure synchronizes software running on the primary server and the secondary server — you must rollback both at the same time. Start the rollback on the primary server, and then start the process on the secondary server.

To rollback the VCX software on a redundant VCX Enterprise system with a primary server and secondary server:

1. Log in as root on the primary VCX server and on the secondary VCX server.

2. Rollback to a previous software version by entering the following command on the primary server, then on the secondary server:

vcx-switchversion 7.1.16c

This rollback requires a reboot because an older operating system version is required. The rollback process continues the version switch and reboots each VCX server. After the reboot process completes, the system starts VCX 7.1.16c services.

NOTE: For a redundant system with replication running, you should start the version switch on both the primary and the secondary at the same time. During the version switch, synchronization between servers is done automatically so that only one server is out of service at a given time.

3. The process will take several minutes. After the system has completed the restart process, verify that the rollback has occurred by entering this command on both servers:

vcx-listversions




If the switched version is not the active version, please wait for a while and reenter the command. The rollback is not complete until the command indicates the correct version is active.

CAUTION: After verifying that the correct version of VCX software is running on each VCX Enterprise server, you should manually restart that database replication and verify the replication status is normal.

Rolling Back VCX Enterprise System with Region and Branch to 7.1

Follow the procedures in this section to rollback the VCX software on a Region and Branch VCX Enterprise system to version 7.1.



March 31, 2011 of 85


IMPORTANT: If you rollback one VCX Region and Branch system running new VCX version to 7.1, you MUST set up the database replication between Region and Branch manually after the rollback process.

To rollback the VCX software on a VCX Enterprise system with Region and Branch servers:


2. You MUST do the rollback process on Branch servers first. Rollback to a previous software version by entering the following command on Branch servers:


This rollback requires a reboot because an older operating system version is required. The rollback process continues the version switch and reboots each VCX server. After the reboot process completes, the system starts VCX 7.1.16c services.

3. The process will take several minutes. After the system has completed the restart process, verify that the rollback has occurred by entering this command on the servers:

vcx-listversions





4. After the rollback process is complete on all Branch servers, you can do the rollback on the primary server, at one time on the secondary server:


vcx-listversions


5. When the old version is active on both the Region servers and Branch servers, you need manually enable database replication between Region and Branch servers by entering the following commands on the Branch servers:

su - cworks


./setupReplication

When replication setup is complete and status is reported as NORMAL by command “./checkReplication”, enter the command “exit” to exit the cworks account and return to the root account.


March 31, 2011 of 85

CAUTION: After verifying that the correct version of VCX software is running on each VCX Enterprise server, you should manually restart that database replication and verify the replication status is normal.

Rolling Back VCX System with Single Server to 8.0/9.0

Follow the procedures in this section to rollback the VCX software on a single server VCX system to version 8.0/9.0. With VCX release 9.0.17 or later, you can perform a rollback using the System Administration web interface (see Rolling Back VCX System through Web Interface).

To rollback the VCX software on a single server VCX system:

1. Log in as root.

2. Rollback to previous VCX version by entering the following command:

vcx-switchversion 8.0.4e

This rollback requires a reboot because an older operating system version is required. The rollback process continues the version switch and reboots the VCX server. After the reboot process completes, the system starts VCX 8.0 services.

3. After the system has completed the restart process, verify that the rollback has occurred by entering this command:

vcx-listversions





Rolling Back VCX System with Two Servers to 8.0/9.0

Follow the procedures in this section to rollback the VCX software on a two servers VCX system to version 8.0/9.0. With VCX release 9.0.17 or later, you can perform a rollback using the System Administration web interface (see Rolling Back VCX System through Web Interface).


To rollback the VCX software on a redundant VCX system with a primary server and secondary server:

1. Log in as root on the primary VCX server and on the secondary VCX server.

2. Rollback to a previous VCX version by entering the following command on the primary server, at one time on the secondary server:


March 31, 2011 of 85

vcx-switchversion 8.0.4e

This rollback requires a reboot because an older operating system version is required. The rollback process continues the version switch and reboots each VCX server. After the reboot process completes, the system starts VCX 8.0 services.

3. After the system has completed the restart process, verify that the rollback has occurred by entering this command on both servers:

vcx-listversions





NOTE: After verifying that the correct version of VCX software is running on each VCX server, you should verify the replication status is normal.

Rolling Back VCX System with Region and Branch to 9.0

Follow the procedures in this section to rollback the VCX software on a Region and Branch VCX system to version 9.0.



To rollback the VCX software on a VCX system with Region and Branch servers:


2. You MUST do the rollback process on Branch servers first. Rollback to a previous software version by entering the following command on Branch servers:


This rollback requires a reboot because an older operating system version is required. The rollback process continues the version switch and reboots each VCX server. After the reboot process completes, the system starts VCX 9.0.17 services.

3. The process will take several minutes. After the system has completed the restart process, verify that the rollback has occurred by entering this command on the servers:

vcx-listversions



March 31, 2011 of 85

9.0.17 2009-Sep-25 active



4. After the rollback process is complete on all Branch servers, you can do the rollback on the primary server, at one time on the secondary server:


vcx-listversions


NOTE: After verifying that the correct version of VCX software is running on each VCX server, you should verify the replication status is normal.

Rolling Back VCX System through Web Interface

With VCX release 9.0.17 or later, you can perform a rollback using the System Administration web interface.

To roll back the VCX Server using the System Administration Web Interface:

1. Select System Software > Switch Version. See Figure 11

Figure 11 Switch Version Menu

2. The Switch Version page appears. See Figure 12.


March 31, 2011 of 85

Select the version which you want to roll back.

Click Switch Version. Before rolling back, please read the notes carefully, and then click OK to switch the VCX system software version, or click Cancel to cancel the switch version operation.

Click OK to continue the rollback process.

Figure 12 Switch Version page

3. Software switch version is in progress. See Figure 13.

Figure 13 Software switch version is in progress

4. The rollback operation is almost complete. See Figure 14.

The rollback process continues the version switch and, if required, reboots the VCX server.


March 31, 2011 of 85

Figure 14 The operation is almost complete


March 31, 2011 of 85

G Upgrading VCX System by clean installation This appendix describes how to upgrade a new VCX server that is factory preinstalled with a lower VCX software version to a recent VCX software version. This operation is typically used to upgrade a VCX server when you need to add the server to your current VCX system/network that is running a recent VCX software version.

IMPORTANT: If one server has already been configured, we strongly recommend you don’t do clean installation on the server. That is, if the server has already completed the FTC (First Time Configuration) procedure, you can upgrade the server by the steps which described in Appendix A to Appendix F.

IMPORTANT: If the server has been factory preinstalled multiple VCX software versions, you cannot do clean installation for this server.

IMPORTANT: If you do the clean installation more than one times on a server, please ensure the ACTIVE OS is compatible with the new VCX software version. You can use the “vcx-os-query” command to check the current active OS. If the ACTIVE OS is not compatible with the new VCX software version, you MUST switch the OS manually by “vcx-os-switch” command.

This chapter includes the following topics:

Clean and Install VCX software for one VCX server

Clean and Install VCX software for one VCX server

You can upgrade a new VCX server that is factory preinstalled with a lower VCX software version to a recent VCX software version that is already running in your environment by the following steps:

1. Log in as root on the server.

CAUTION: Before cleaning the VCX system, please ensure that you have already made a backup for the license file on the server.

2. Obtain the clean_vcx_rv03.pl VCX clean script file. Place a copy of the file in the /opt/installtemp directory on the server.

3. Enter the following commands to clean the original VCX software version:

cd /opt/installtemp

chmod +x clean_vcx_rv03.pl

./clean_vcx_rv03.pl

The clean script will clean the system and the server will be automatically rebooted.

4. After the server has completed the reboot process, you MUST install vcx-users, Oracle database and VCX software for this server.


March 31, 2011 of 85

5. Log in as root on the server again.

6. Obtain the following VCX software upgrade files and place a copy of the files in the /opt/installtemp directory on the server,

vcx-users-x.noarch.rpm

oracle-y.i386.rpm

vcx-x86-z.tar (or vcxconnect-x86-z.tar)

The variable x, y and z indicate the version number of vcx-users, Oracle database and VCX software that will be replaced by the actual version number. As an example, for VCX 9.8.15, the compatible upgrade files are shown as below,

vcx-users-2.0.3-1.noarch.rpm

oracle-10.2.0.4-1.i386.rpm

vcx-x86-9.8.15.tar

For every VCX release, please refer the “Hardware and software compatibility matrix” table of the release notes for the compatible versions.

7. Enter the following commands on the VCX server to install vcx-users and Oracle database:

cd /opt/installtemp

vcx-install vcx-users-2.0.3-1.noarch.rpm


8. Enter the following commands on the server to install VCX software:

cd /opt/installtemp


cd upgrade-9.8.15

./install-upgrade

9. When the installation process completes, reboot the server and do configuration for the server. For more information, please refer VCX Administration Guide.

Vcx 9.8.15 release notes 2011-03-31

Technology

Transcript of Vcx 9.8.15 release notes 2011-03-31