Installation instructions for MultiVOIP 210-AV/410-AV/810-AV software vs 9.06.DN MultiVOIP's Uninstall Solution Product Update PN: 82010180 Rev. A 02/16/04 Before uninstalling any old versions of MultiVOIP software, install the new MultiVOIP Software provided for this readme. 1. Run avaya_9.06.e2.exe to unzip the install files. The install files will be unzipped to the directory C:\avaya_906e2. 3. Go to the folder C:\avaya_906e2\Disk1 and run setup.exe to install the software to the pc. Accept the default installation folder and program group name. When prompted, select the comm. port that you will use with the MultiVOIP. Click "No" when asked if you would like to run configuration. 4. Connect the MVP210-AV/410-AV/810-AV to the PC comm. port and power it on. When the boot light is off. Notice: the boot light will be on solid, then start to blink, then go out completely as you power on the voip. 5. Run Start->Programs->MultiVOIP 9.06->Configuration and configure the MultiVOIP for your application. If you are retrieving this software and will upgrade the existing voip, refer to upgrade procedures below. 1. Upgrade from 9.04.05 to 9.06.E2 using GUI Steps Description 1 Install 9.06.E2 software 2 Run 'Download Firmware' from the Programs group menu items. 3 Change the search criteria from *.bin to *.upg, then hit enter on your keyboard, now select 'boot.upg' from the dialog box. 4 On successful download the GUI displays a message 'Waiting for Download. Please run upgrade software'. Click OK. 5 Run 'Upgrade Software' 6 A dialog box appears. Select 'Retain configuration' to retain the current configuration or select 'Use factory defaults' to load the factory defaults. 7 On successful completion of upgrade, the box is completely upgraded with 9.06. 8 Uninstall your old version of MultiVOIP software by selecting the "Uninstall" option from the program group. 9 The upgrade is complete. Note: You will be able to manage and configure the voip with WEB interface using a Java plug in for the browser. 2. Upgrade from 9.04.05 to 9.06.E2 using FTP (Remote Upgrade) This is not possible for 9.04.05 version files, as we need to upgrade the boot.upg first. 3. Upgrade from 9.05.10 or later to 9.06.E2 using GUI Steps Description 1 Install 9.06.E2 software 2 Run 'Upgrade Software' 3 A dialog box appears. Select 'Retain configuration' to retain the current configuration or select 'Use factory defaults' to load the factory defaults. 4 On successful completion of upgrade, the box is completely upgraded with 9.06.E2. 5 Uninstall your old version of MultiVOIP software by selecting the "Uninstall" option from the program group. 6 The upgrade is complete. Note: You will be able to manage and configure the voip with WEB interface using a Java plug in for the browser. 4. Upgrade from 9.05.10 or later to 9.06.E2 using FTP (Remote Upgrade) Note: When upgrading from v9.06.DN or earlier using FTP, it is recommended to delete all Gatekeeper endpoints before upgrading to prevent the endpoints from being corrupted. Steps Description 1 Using your current configuration software, delete all endpoints in the Gatekeeper. 2 Install 9.06.E2 software 3 Use an Passive FTP client (supported by IE) and DOS FTP client. 4 Initiate a FTP session to box running 9.05.10 or later. 5 Send mvpt1ftp.bin to the box. 6 On completion of ftp session, the box is completely upgraded with 9.06. 7 Uninstall your old version of MultiVOIP software by selecting the "Uninstall" option from the program group. 8 Re-enter the Gatekeeper endpoints using the configuration software (Web or GUI). 9 The upgrade is complete. Note: You will be able to manage and configure the voip with WEB interface using a Java plug in for the browser. You can retrieve vs. 1.4.02.01 from our ftp server at ftp://ftp.multitech.com/MultiVoip/Misc/java/j2re-1_4_2_01/ After installing, reboot your PC. Changes in MVP210/410/810-AV release 9.06.bd 1. Added DID (requires MVP210 rev B or MVP410/810 rev C hardware). 2. Added Caller ID. 3. Added audible message waiting feature. 4. Added G.729/G.711 and G.711/G.729 voice coder options. 5. Added Off-hook Alerting feature. 6. Added Remote Ping function to both web browser and gui interfaces. 7. The model number is now displayed in the System Information screen. 8. The serial number is now displayed in the System Information screen. 9. The gatekeeper will reject all registrations until it enters survivable mode. 10. The gatekeeper will reject registrations from IP phones that have calls active 11. Changed the Unregistration Request message sent to IP phones so the IP phones will immediately try to re-register with the top entry in it's gatekeeper list instead of rebooting and then re-registering.. 12. The MultiVOIP no longer sends Gatekeeper Request when registering FXO/DID trunks to Avaya Communication Manager. This prevents a "load balancing" problem on the Avaya switch that could prevent MultiVOIP trunks from getting registered. 13. Fixed a problem which caused the gui to gpf if "Retain Configuration" was selected while running Upgrade Software. 14. Fixed the following Message Waiting problems: 14.1. If Message Waiting is enabled or disabled on the FXS channel, multiple "Message Waiting Off" Setup messages sent down from the Avaya switch would cause the phone would ring on the voip until the ring count was exceeded or the phone was answered.. 14.2. If Message Waiting is disabled on the voice channel, "Message Waiting On" Setup messages would cause a brief ring on the voice channel. 15. Fixed problem where garbled voice would occur if the "Number of Days" option was enabled in the SMTP Parameters screen. The garbled voice would occur once the configured number of days had elapsed. The default was 4 days and SMTP did not need to be enabled for the problem to occur. 16. Added support for built-in command modem on MVP410/810 rev C hardware. 17. Fixed a problem where Packets Lost counter in Call Progress would display incorrect values. Changes in MVP210/410/810-AV release 9.06.df 1. Fixed the Dynamic Load Balancing problem where FXO/DID trunks would fail to register with Definity. To resolve the problem we no longer send Gatekeeper Request to Definity for FXO trunks. 2. Fixed the problem where SuperG3 fax machines attached to the MultiVOIP could not receive faxes. 3. Fixed the problem where calls from FXO to Definity would fail if Definity was running ACM 3.0 software. To fix this we changed the bearer capability sent in the SETUP message from “unrestricted 64 kbps” to “speech”. This problem only affected FXO/DID trunks. FXS stations worked fine. 4. Fixed the fax problem where the MultiVOIP channel could get stuck with XMT, RCV, and RSG lights on. You had to reset the MultiVOIP to clear the condition. 5. Fixed the problem where the MultiVOIP could repeatedly enter and exit survivable mode if the Definity is using multiple CLANs and the primary CLAN is unavailable. Changes in MVP210/410/810-AV release 9.06.dn Added support for the new IFM ATMEL 8253 modules. Bug Fixes 1. Made T38 faxing more robust Symptom: T38 Fax fails when multiple pages are sent Resolution: Use proper validations to distinguish RTP and T38 packets. 2. Made changes so MultiVOIP now also retrieves Subnet mask and Router IP address from the DHCP server. Symptom: MultiVOIP is not receiving the router IP address or Subnet mask from the DHCP server. Resolution: Send the 'Parameter Request List' with lease time, Subnet Mask and router in Discover. Changes in MVP210/410/810-AV release 9.06.e2 1. Added support for the 1600 series and 9600 series Avaya IP Phones. Symptom: When adding Endpoints in the MultiVOIP-AV Gatekeeper, there was no option for the 1600 series or 9600 series phones. Resolution: Added support for the 1600 series and 9600 series Avaya IP Phones. 2. Fix issue that cause calls to fail when using shuffling with Avaya Call Manager 5.0. Symptom: When “Direct IP-IP Audio Connections” is enabled on the Call Manager 5.0, calls between channels on the MultiVOIP-AV would ring, but would drop when answered. Resolution: Change the H.323 stack to be more robust in handling call setup messages. 3. Fix bug that caused to GUI to become unresponsive when using virtual COM ports. Symptom: When using the GUI on a PC with a virtual COM port, the GUI would sometimes become unresponsive. Resolution: Increased the length of the COM port string to more than 20 characters. 4. Fixed compatibility problem that sometimes causes T.38 faxes to fail during negotiation. Symptom: T.38 faxes fail during negotiation. Resolution: Changed T.38 sequence numbering to start at zero to be compatible with Avaya’s latest T.38 code changes.