| Question |
| Explnation on the diff between Avaya cm 5.0 and below and avaya aura 6.0 cm ? |
| Answer |
| Whats new in CM 6.x. 1. Till cm 5.2.1 we have proprietary Linux from AVAYA but from cm 6.x onwards we have templates based solution from Avaya. 2. Till CM 5.2.1 lic needs to be generated from RFA.avaya.com but from cm 6.x lic needs to be generated from PLDS portal. |
| |
| Question |
| What is major diffrence in latest rel 6.x than the 5.2 |
| Answer |
| Few more differance are 3. Till CM 5.2.1 Lic are binded on Medi gateway / Golden IPSI serial no but from CM 6.x lic are binded on MAC ID of System platform in case of Simplex/Duplex/Embedded solution templates. 4. In case of MES solution lic are binded on System manager MAC ID. 5. Till cm 5.2.1 we required individual lic file to be install on main CM , LSP, ESS ¦but from cm 6.x we donate required individual lic file to be install on ESS and LSP has to be install on Main CM only. 6. Till CM 5.2.1 system is not DOT compliance customized patch is needed to stop the DOT violation for some specific features but from CM6.2 FP2 system is DOT compliance. 7. In PSTN and IP trunk environment Till cm 5.2.1 we cannot use features call forwarding, EC500 feature but from CM6.2 FP2 we can use those feature. 8. Till Cm 5.2.1 in built Voicemail Feature is only available on Embedded CM ie S8300.. But from CM 6.x CMM is available inbuilt in MES (Mie size enterprise solution) can be install on Dl360g7,dl360g8 , S8300 server. 9) From CM6.3 Virtualization has come up. 10) Till CM5.2.1 we donate have the inbuilt file server but from CM 6.x we have Utility server as in template which can be used for phone FW upgrade/ IP-phone backup. 11) Till CM 5.2.1 end customer doesn’t have the feasibility to change the password of their own extension…but from Cm 6.x end customer has feasibility to change the password of their own extension using the web link of the Utility server. |
| |
| Question |
| If want to upgrade any cm from 5.0 or below to 6.0 and above, what is the procedure that need to be follow ? |
| |
| Answer |
| CM Upgrade process from 5.2.1 to 6.0:- 1. Latest firmware on all Avaya H.248 Media Gateways 2. Latest firmware on the media modules within the Avaya H.248 Media Gateways 3. Communication Manager on any survivable remote server (formerly local survivable processors) 4. Communication Manager on any survivable core server (formerly enterprise survivable servers) 5. Communication Manager on the main server 6. Latest firmware on all TN circuit packs (if using port networks) 7. Latest firmware on all telephones |
| |
| Question |
| What is the minimum hardware or software requirement for upgrade? |
| Answer |
| Avaya Aura® run on the following servers: • S8300D • S8510 • S8800 • HP ProLiant DL360 G7 • Dell™ PowerEdge™ R610 • HP ProLiant DL360p G8 • Dell™ PowerEdge™ R620 Only S8300D, HP DL360 G7, HP DL360 G8, Dell R610, and Dell R620 are currently being sold. |
| |
| Question |
| Brief us the features of 6.0 cm ? |
| Answer |
| From CM6.x we have Template based soluction, virtulization has comes from cm 6.3 onwards |
| |
| Question |
| MVPIP TEL version supported for CM 6.3 ? |
| Answer |
| from cm 6.x onwards we have an option of utility server which we can use for Firmware updare , ip phone contacts backup |
| |
| Question |
| What a template based solution is and also its advantages if any? |
| Answer |
| CM 6.x comes with – Five new System Platform templates: 1.Avaya Aura® Main / Avaya Aura® for Survivable Core Duplex configuration (CM_Duplex). 2.Avaya Aura® Main / Avaya Aura® for Survivable Core Simplex configuration (CM_Simplex) 3.Avaya Aura® for Survivable Remote Simplex configuration (CM_SurvRemote140) 4.Avaya Aura® Main Embedded configuration (CM_onlyEmbed) – S8300D 5.Avaya Aura® for Survivable Remote Embedded configuration (CM_SurvRemoteEmbed140) S8300D. 6.MES Simplex solution can be install on Server & S8300D. |
| |
| Question |
| Can we restore configuration data directly from 5.X to 6.X or we need any data migration tool to do so? |
| |
| Answer |
| yes we can restore the xln file from cm 5.2.1 to cm 6.x. Procedure should be follows as below.. 1) Take the backup from existing server – cm 5.2.1 2) Restore the xln file on the newly built server ie CM 6.x eg dl360g7 or dl360g8 or S8300. |
| |
| Question |
| What is the procedure to migrate avaya 3.0 to 6.2 ? |
| Answer |
| we need to follow the below migration path using the pre upgrade patch. 1) first CM 3.0 needs to be upgraded to 5.2.1 2) Form Cm 5.2.1 need to upgraded to Cm 6.x…Hardware change is must. |
| |
| Question |
| Explain new feature accomodate in 6.3 for Avoid toll bypass ? |
| |
| Answer |
| On CM 6.2 FP2 – First we need to enable the On the System Parameters Special Applications screen, set the SA 9122 – Restrict Public- Private Network connections field to y. Below features are compliant with toll regulations. a) EC500:- Inward and Outward calls from/to EC500 handset will not be routed over CUG trunks b) Call Forward / Chain call forward:-CUG calls will not be forwarded over PSTN and vice versa. c) CM Conferencing – Meet-Me & Ad Hoc / Bridge-on:- CUG & PSTN will not merge in a single conference d) Endpoints:- – Both Audio & Video endpoints supported – Endpoint must not do local conferencing. If it does, it will have to be configured only in CUG network. (Network map) |
| |
| Question |
| If, directly upgrade the cm from 3.0 to 6.2, is there any chance for the corruption to be occoured after the installtion. |
| |
| Answer |
| |
| Practically we have implemented this soluction at one of the customer location.. Direct upgrade from 3.0 to 6.2 works.. 1) CM 3.0 was on S8700 server..we have taken the xln backup. 2) Install cm 6.2 on the newly delivered dl360g7…restore the backup taken from 3.0. It works…there is no corruption.Pls install the recommendation patch as per the avaya guide while doing this upgrade. |
| |
| Question |
| |
| Explain on licensing in CM 6.x ? |
| Answer |
| From Cm 6.x onwards lic file needs to be generated from PLDS. Earlier till cm 5.2.1 we need to generate the lic from RFA portal. also License files are not installed on survivable servers. Survivable servers receive licensing information from the main server. If you are licensing a duplicated pair configuration, you must install the license file on both servers. The license file is not synchronized from the active server to the standby server. A 30-day grace period applies to new installations or upgrades to Communication Manager 6.0. You have 30 days from the day of installation to install a license file. |
| |
| Question |
| Is CM 6.x having backword compaibilty with AES 5.2? |
| Answer |
| If aes is on 5.2.1 its compatible with CM 6.0 , 6.2.4 only. If cm is on 6.3 then we need to upgrade the AES to 6.x. |
| |
| Question |
| Which particular patch we require if we going to upgrade from 3.0 to 6.0 |
| Answer |
| Apply the pre upgrade patch as per the latest compatibility matrix available on support.avaya porta.. Post which we can directly restore the XLn file from CM 3.0 to CM 6.x on the newly delivered server. |
| |
| Question |
| Exiting hardware of 5.2 is supported on 6.X |
| Answer |
| yes s8800, s8300D server are compatible for cm 6.x. Not certified or supported servers for Cm 6.x: S8300B, S8300C, S8400A, S8400B, S8500B, S8500C, S8730, S8720, S8710. |
| |
| Question |
| |
| Can you use dl360g7 as a ess with cm 6.X and above ? |
| Answer |
| yes we can use S8300D, HP DL360 G7, HP DL360 G8, Dell R610, and Dell R620 server. |
| |
| Question |
| Is there any roadmap for V7.0? If yes how it would be different? |
| |
| Answer |
| currently avaya has a roadmap till 6.3. |
