RELEASE NOTE ETERNITY ME

Transcription

1 RELEASE NOTE ETERNITY ME DATE: 11 th Jan, 2019 VERSION: V12R5.5.4 AUTHOR: Bhavin Parmar

2 Release Information: Product Name Product Variants Version Revision ETERNITY ETERNITY ME16SAC ETERNITY ME16SDC V12R5.5.4 Date Dec 21, 2018 Compatible CPLD Version/Revision Compatible PCB Version/Revision Microcontroller s Version/Revision V1R1(C_ ) V1R3(P ) V5R3 Field Upgrade Package: Date Dec 11, 2018 File Name File Size MD5sum Remarks ETERNITY_ME_V12R5.5.4_Field.zip bytes 2eebbc9e4d0ad19d581fb217a68a712d None USB Package: Date Dec 11, 2018 File Name File Size MD5sum Remarks ETERNITY_ME_GE_PE_V12R5.5.4_USB.zip bytes fc32ce08a184eae3a93d2e1d2c69eeff None

3 What s new in this release: Implemented CLI information to the transferor for return call during blind transfer feature. Field Issues: Sr. No Issue Title with Summary Title: Previous call CLI displaying on Analog Extension Screen Summary: When receiving calls on the GSM trunk, the CLI displayed on the analog phone was of the last call received on the same GSM trunk, which has been resolved in this release. Title: Outgoing calls from extension using TATA PROXY SIP TRUNK getting disconnected randomly Summary: Outgoing calls were done on the TATA Proxy SIP trunk randomly fails which has been resolved in this release. Title: Calls get matured in Gateway applications when 180 and 183 ringing is received from service provider Summary: When SARVAM used as a SIP to SIP gateway and 180 ringing received from 1st Call leg then Gateway Application was sending 200OK on 2nd call leg. So, the call on 2nd call leg was getting matured irrespective of the call answered on 1st call leg. Title: ETERNITY GE getting hanged, Master App Crashing Summary: When Call tapping was on in the system, the system Master application crashes due to Attendant transfer request received from any standard SIP Phone. Title: Priority calls in E&M MFC R2 Signaling is not working Summary: RAID feature was not working for any call on E&M trunk, which has been resolved in this release. Title: SA command ( ) to display Port Parameters should work from SPARSH VP310_VP510 Summary: SA command ( ) to display H/W Slot port Parameters was not working from SPARSH VP310/VP510, which has been resolved in this release. Title: Auto answer is not working on IP phone when auto answer timer is greater than acknowledge timer Summary: Auto answer feature was not working on IP phones when the autoanswer timer is greater than acknowledge timer. Title: VoIP card is getting restart on IC P2P SIP calls Summary: VoIP card was getting restart on incoming SIP calls, which has been resolved in this release. 9 Title: RBT When Transferred the call through QSIG to a Busy Extension

4 10 Summary: When the call is transferred between two extensions connected over QSIG, if the transferred extension was busy then transferee extension was not getting the busy tone. Instead, it was getting RBT. Title: Random calling of DKP phone Summary: EON48 having version V4R9 is automatically dialing Extension number of another DKP extensions. Issue Pending/Known in this release: Sr. No. 1 2 Issue Title with Summary Title: Wake-up Alarm does not get cleared from GUI (SA Mode/Front Desk) Summary: In ETERNITY systems, if we have set up a wake-up alarm, then it is not clear even after the cancelled by the administrator or the front desk log-in. Title: Not able to detect the DTMF for Inbound E&M call Summary: IF ETERNITY System is connected to the NEC PBX through E&M line and call is made from NEC to ETERNITY, then ETERNITY system is not able to detect the DTMF sent by NEC system. Affected Configuration: Will this firmware up gradation affects system configuration? NO Defaulted Parameters: Sr. No. GUI Page Link Parameters Remarks NA Removed Parameters: Sr. No. GUI Page Link Parameters Remarks NA

5 Relocated Parameters: Sr. No. GUI Old Page Link GUI New Page Link Parameters NA Firmware Up-gradation Procedure: To Update the System (Field) Package and USB Package into ETERNITY ME System follow procedure as below. (1) Upgrade Firmware Package : Unzip firmware package. (2) Log in to the system's FTP using Eternity s Link of Firmware Upgrade [Needs firefox ftp] or Open FTP directly. (3) Delete all the files from 'system' folder. (4) Copy all the files from "Firmware-Part-1" folder to "system' folder. (5) Reboot the system. Caution: kindly make sure that power does not go and system is not powered off till webpage is accessible else the kernel will be corrupted and system will be non-functional. (6) After completion of "Firmware-Part-1" up gradation successfully it will show a message as given below on web login.

6 (7) Now again Log in to the system's FTP using Firmware Upgrade Link or Open FTP directly. (8) Delete all the files from 'system' folder. (9) Copy all the files from "Firmware-Part-2" folder to "system' folder. (10) Reboot the system. On completion of reset cycle, now all the ports of the system will be functional. System is ready for use (11) Upgrade USB Package: Upgrade SPARSH VP310, SPARSH VP330 & SPARSH VP510 IP phones and SMS_Server Unzip usb package and copy contents of the folder to /eternity/usb NOTE: Please check system access on default IP and default password if in any case system is not being accessed. If Firmware Upgrade link is not working than use ftp directly. Caution: Do not copy and paste whole ExtendedFirmware folder on FTP path. Reference Documents: System Manual Sr. No. Version Month Document Name 1 V12 Feb, 2019 ETERNITY V12R5.5 System Manual

7 2 V12 Feb, 2019 ETERNITY V12R5.5 Hospitality System Manual User Guide Sr. No. Version Month Document Name 1 V1 Dec, 2018 EON510_SPARSH VP510 V1 User Guide 2 V1 July, 2016 SPARSH M2S iphone Application V1 User Guide 3 V1 July, 2016 SPARSH M2S Android Application V1 User Guide 4 V1 Dec, 2018 SPARSH VP330 V1 User Guide 5 V1 Dec, 2018 VARTA WIN200 V1 User Guide 6 V1 Dec, 2018 EON48_310_SPARSH VP248_310 V1 User Guide 7 V1 Dec SLT V1 User Guide 8 V1 Apr, 2015 VMS V6 User Card Quick Start Sr. No. Version Month Document Name 1 V12 Feb, 2019 ETERNITY V12R5.5 Quick Start Dec, 2015 Matrix TAPI V1 Developer's Guide Dec, 2015 Matrix TSP V1 User Guide 4 Matrix TAPI Service Provider TAPI Software Release Version (Setup)

8 Limitations: Module/Feature Details QSIG Length for Supplementary Parameter 4, 5 & 6 for any Rose APDU received from Line are restricted to 24 Bytes. System Performance System performance can be degraded when multiple users try to navigate menu from 6-line Matrix Phones at same time. System performance can degrade when multiple DSS64/DSS532 are connected with DKPs and system tries to update LEDs of all these connected DSS at same time. System performance can degrade when system is attacked by heavy IP data traffic (IP flooding) SNMP If we decrease the number of ports from system prerequisites, then same number of ports will not be reflected on third party software (SNMPs). Trunk (CO, BRI, T1E1, MOBILE, and SIP) status notification traps may be received on power on start.