RELEASE NOTE ETERNITY LE/ME/GE/PE. DATE: 19 th January 2018 VERSION: V12R5.5.3 AUTHOR: Tapan Upmanyu

Transcription

1 RELEASE NOTE ETERNITY LE/ME/GE/PE DATE: 19 th January 2018 VERSION: V12R5.5.3 AUTHOR: Tapan Upmanyu

2 Contents Release Information:... 3 ETERNITY LE:... 3 ETERNITY ME:... 3 ETERNITY GE :... 4 ETERNITY PE :... 5 What s new in this release:... 6 Issue Fixed in this release:... 7 Affected Configuration:... 8 Upgradation Procedure:... 9 Limitations: Compatibility Charts:... 13

3 Release Information: ETERNITY LE: Product Name Product Variants Version Revision ETERNITY LE V12R5.5.3 Date 25/12/2017 Compatible CPLD Version/Revision Compatible PCB Version/Revision V1R3 V1R3 Field Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_LE_V12R5.5.3_Field.zip bytes 84f7ee57ed0f2cf8b e4fbed USB Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_LE_V12R5.5.3_USB.zip bytes d1e1e8e38085d7ad060322c60c6c0c7f ETERNITY ME: Product Name Product Variants Version Revision ETERNITY ME V12R5.5.3 Date 25/12/2017 Compatible CPLD Version/Revision Compatible PCB Version/Revision V1R1(C_ ) V1R3(P )

4 Field Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_ME_V12R5.5.3_Field.zip bytes 2d7e909aa924748d7c8e746cacd406ee USB Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_ME_GE_PE_V12R5.5.3_USB.zip bytes 17d07d2f01133bee2406ad39be78a87a ETERNITY GE : Product Name Product Variants Version Revision ETERNITY GE V12R5.5.3 Date 25/12/2017 Compatible CPLD Version/Revision Compatible PCB Version/Revision C P (which has 64 MB RAM) Field Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_GE_V12R5.5.3_Field.zip bytes a27ce7e3c958d294860aeda82d0dc094

5 USB Package: Date Dec 22, 2017 File Name File Size MD5sum ETERNITY_GE_Pendrive.zip bytes 7c92c860f60162bf0e130a725a ETERNITY PE : Product Name Product Variants Version Revision ETERNITY PE V12R5.5.3 Date 25/12/2017 Compatible CPLD Version/Revision Compatible PCB Version/Revision C_138_001_01_04 P Field Package: Date Dec 25, 2017 File Name File Size MD5sum ETERNITY_PE6S_V12R5.5.3_Field.zip bytes 83b18d5cc6f e831f98e7cdf USB Package: Date Dec 22, 2017 File Name File Size MD5sum ETERNITY_PE_Pendrive.zip bytes 1b0cf976813fde8912ae8b13f22c9ba2

6 What s new in this release: Configuration PTT count to detect the incoming call on Radio Port Till now, the no. of PTT events to detect incoming call over the radio port was fixed to 1. Now it is configurable in range of 1 to 5.and the defined range is 1-5. NA NA Support any card (i.e SLT,CO,DKP etc) with ILC card Previously with ILC card - we only support two card types i.e. VoIP card (to connect two ILC systems) and VMS card, no other cards were supported. Recently we have phased out ILC Card to support reduction of our inventory drive. But at the same time it is important for us to make sure that existing customer should not suffer with this take, they can continue to expand there existing deployments with the purchase of SLT or any other cards from this release onwards. NA NA CLI modification for region India is not provided To comply all the Government rules and regulation of India (i.e. Telecom Engineering Communication - TEC) we have removed CLI Modification for India Region. NA Call hold method options : RFC 2543 and RFC 3261 For interoperability with different IP Phones OEM s, we have provided support to Hold the calls as per RFC 2543 and RFC Option to select Call Hold method is provided in System Parameter Page of Jeeves. NA

7 Issue Fixed in this release: Field Issues: Call on Hold Option : RFC 2543 and RFC 3261 (FIT-3155) - As mentioned above NA If no. of OG call in SMDR exceeds more than set limit, system process was not stopped even though buffer was full. NA When multiple conferences are on-going in system, some times conference merge issue like conversation from one conference was audible in second conference was observed in field. NA Call Release funcationality using Release key from DKP or Extended IP Phones was not working in Q.SIG Proceed and Progress State. NA When call is routed from SIP Trunk to PRI trunk (i.e. in RTP Relay and DRTP Mode) system was directly maturing the call in ringing stage. The option provide under SIP Trunk Parameters were not working as configured. Same is fixed in this release. NA If the user makes call from Open SIP phone to CO Trunk, the line was getting silent for 25 sec without any RBT. At the same time, called extension ring and even the speech path gets through. NA

8 Known/Pending issues: OG calls from CO line stops randomly while IC works but without CLI Issue in E1 over Fiber Optics use with Data Card. When data channels are assigned E1 link gets down. Doesn't get RBT when call is routed from one PRI to another PRI(Gateway call) QSIG calling between ME and LE stops working randomly EON 510 phones show the status as "Loading Firmware V2R2...Please wait" continuously. GUI of system is not working after upgrading it to V12R5.4.0 Redundancy occurs and system rebooted automatically. Eternity NE312 - Reset Problem GE CPU Not Reset Randomly CLI is not appearing on DKP and SLT phone while having Incoming call on CO. The same CLI information is not logged in SMDR. Affected Configuration: Will this firmware up gradation affects system configuration? NO Defaulted Parameters Sr. No. GUI Page Link Parameters Remarks --- NO -- Removed Parameters Sr. No. GUI Page Link Parameters Remarks --- NO -- Relocated Parameters Sr. No. GUI Old Page Link GUI New Page Link Parameters --- NO --

9 Upgradation Procedure: For ETERNITY LE: Login to the FTP of ETERNITY Delete all files from "system" folder Copy all files from " Field" folder to "system" folder Reboot the system The system is upgraded successfully Firmware of SPARSH VP310, SPARSH VP330 and SPARSH VP510 IP phones: a) After connecting Pen-drive in system, remove all files from system s FTP path: /ExtendedFirmware/ b) Extract ETERNITY_LE_Pendrive.zip file into Desktop of PC. Copy all firmware files (*.tar.gz) from ETERNITY_LE_Pendrive/ExtendedFirmware folder of PC to below path on FTP. /ExtendedFirmware c) Verify all firmware file (*.tar.gz) information (File Version, Name & Checksum) in ExIP_BuildInfo.txt file at system s ftp-path /system/ Caution: Do not copy and paste whole ExtendedFirmware folder on FTP path For ETERNITY ME, ETERNITY GE and ETERNITY PE: Login to the FTP of ETERNITY Delete all files from "system" folder Copy all files from " Firmware-Part-1" folder to "system" folder Reboot the system After "Firmware-Part-1" up gradation successfully it will show message as given below on web login.

10 Now again login to FTP of ETENRITY Delete all files from "system" folder Copy all files from " Firmware-Part-2" folder to "system" folder Reboot the system

11 The system is upgraded successfully Firmware of SPARSH VP310, SPARSH VP330 and SPARSH VP510 IP phones: d) After connecting Pen-drive in system, remove all files from system s FTP path: /ExtendedFirmware/ e) Extract ETERNITY_ME_GE_PE_Pendrive.zip file into Desktop of PC. Copy all firmware files (*.tar.gz) from ETERNITY_ME_GE_PE_Pendrive/ExtendedFirmware folder of PC to below path on FTP. /ExtendedFirmware f) Verify all firmware file (*.tar.gz) information (File Version, Name & Checksum) in ExIP_BuildInfo.txt file at system s ftp-path /system/ Caution: Do not copy and paste whole ExtendedFirmware folder on FTP path Checksum: Checksum_V12R xls Important Notes: System: 1) E911 License a) System with V12R5.4 or above versions is not allow to downgraded to lower than V12R5.4. System will not get up if system will be downgrade. Telnet/Ftp only can be accessible on default IP] b) System with version lower than V12R5.4, can be upgraded/downgraded to any versions. [E911- License will not required for these system] 2) Auto Provision feature for Panasonic IP will not work with IPv6 due to its own problem. 3) System takes 5 minutes to transfer configurations to VoIP server card on power initialization 4) IPv6 is not supported for VMS, CTI, Matrix Extended SIP Hard/Soft Phones 5) IP validation is not available in Static Routing Page (SE Login Ethernet Port Parameters Static Routing Table)

12 6) Due to a limitation of Android Client cannot register or work with Matrix Server on some devices when sip port is configured 5060 in server and client. This issue is at the Android OS level NAT Filter module for TCP Message. Workaround: Change the default SIP Port from 5060 to any other port in Matrix Server and Android Client. This will work in some devices. It may be possible that this will not work on some other devices. 7) Inter Operability Issues a) In Yealink SIP-T20P phone with firmware version, when Call is with DRTP and remote user hold Yealink user then MOH will not play on Yealink. This issue is not observed in Yealink SIP-T28P with firmware version. Other Yealink models are not tested for same. b) In Yealink phone, when RTPMode is Relay and negotiated codec in hold (on holding by remote user to Yealink user) is different than that of speech, MOH will not play on Yealink. c) One way speech with Yealink phone when ILBC codec is negotiated with different payload number. d) When relay call is matured without SRTP with Grandstream GXV3175, it will not accept SRTP parameters in Re-Invite sent by VoIP card for Hold. ReInvite will be rejected by 488. e) No speech in SRTP call with Grandstream(:GXV3140) when GSM codec is negotiated. f) TCP/TLS port close issue during keep alive with Grandstream phone(: GXV3140) The client (Grandstream) should send ping (double CRLF) and should wait for single CRLF from remote peer. When Our VoIP Card send single CRLF as Pong, the Grandstream IP Phone send FIN ACK and disconnect the TCP connection used for Registration. So next time onwards IP phone will send INVITE from port different than used for Register. So we will reject the call. So if user wants to use TCP/TLS for this Grandstream Phone, It is recommended that Keep-Alive should be disabled.

13 Limitations: Module/Feature QSIG System Performance SNMP Details Length for Supplementary Parameter 4, 5 & 6 for any Rose APDU received from Line are restricted to 24 Bytes. 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) If we decrease the number of ports from system prerequisites then same number of ports will not be reflected on third party software (snmpd). Trunk (CO, BRI, T1E1, MOBILE, and SIP) status notification traps may be received on power on start. Compatibility Charts: Telephony Service Provider (TSP) Application TSP Version Revision V12R2 Release 1 x x V12R2 Release 2 x x V12R3 Release 1 x x x V12R3 Release 2 x x x V12R3 Release 3 x x x V12R3 Release 4 x x V12R4 Release 1 x x V12R4 Release 2 x x V12R4 Release 3 x x x V12R4 Release 4 x x x V12R4 Release 5 x x x V12R5 and onward x x x

14 COMMUNICATION MANAGER (ETERNITY ME) For ETERNITY ME Card Communication Manager Application V4R1 V4R2 V4R3 V4R3 V10Rx V11R1 X (Note-1) X (Note-1) V11R2 X (Note-1) X (Note-1) V11R3 V11R4 V11R5 V12R1 V12R2 V12R3 V12R4 V12R5 and onward Note-1: - Compatibility Issue of Redundancy supported application (V11R2) and V4R2 Comm. Manager. This is solved in V4R3. For ETERNITY ME CPU Card (Hot Redundancy Supported Card) Communication Manager Application V5R1 V5R2 V5R3 V5R4 V10Rx V11R1 V11R2 X X V11R3 X X V11R4 X X V11R5 X V12R1 X V12R2 X V12R3 X V12R4 X V12R5.1 Release3 X V12R5.2 Release1 X V12R5.3 Release1 X V X V X V X

15 VMS (ETERNITY ME/GE/PE/LE) Application VMS V6R5 V6R6 V6R7 V6R8 V6R9.1.0 V6R V6R9.5.0 V6R 9.6 V6R V10Rx X X X X X X X V11R1 X X X X X X X V11R2 X X X X X X X V11R3 X X X X X X X V11R4 X X X X X X V11R5 X X X X X X V12R1 X X X X X X V12R2 X X X X X X V12R3 X X X X X X V12R4 X X X X V12R5.1 Release3 X X X X X V12R5.2 Release1 X X X X X V12R5.3 Release1 X X X X X V X X X X X V X X X X X V12R5.4.0 X X X X X GSM Card (ETERNITY ME/LE) It is recommended to use firmware will provided with package itself. VoIP CARD (ETERNITY LE/ME/GE/PE) VoIP Server Version Application V2R1 V2R2 V2R3 V2R4 V2R5 V2R6 V2R7 V2R8 V2R9 V2R10 V11R3 X X X X X X X X X V11R4 X X X X X X X X V11R5 X X V12R1 X X V12R2 X X V12R3 X X V12R4 X X V12R5 onward X X

16 T1E1 CARD (ETERNITY ME/LE) T1E1 Card Application V4R7 V4R8 V4R9 V4R10 V4R11 V4R12 V4R13 V4R14 V4R15 V5R1 V10Rx X X X X X X X X X V11R1 X X X X X X X X X V11R2 X X X X X X X X X V11R3 X X X X X X X X X V11R4 X X X X X X X X X V11R5 X X X X X X X X X V12R1 X V12R2 X V12R3 X V12R4 X V12R5.1 Release3 X V12R5.2 Release1 V12R5.3 Release1 V12R5.3.2 V12R5.3.3 V12R5.4.1 DATA CARD (ETERNITY LE/ME) DATA Card Application V2R1 V2R2 V11R3 X V11R4 X V11R5 X V12R1 X V12R2 X V12R3 X V12R4 V12R5 onwards DATA CARD (ETERNITY GE) Application V12R5 onwards DATA Card V2R3

17 Radio Interface Card (ETERNITY ME/LE) Radio Interface Card Application V1R1 V1R2 V1R3 V1R4 V1R5 V1R7 V1R8 V10R12.31 X X X X X X V10R12.00 X X X X X X V11R1 X X X X X X V11R3 X V11R4 X V11R5 X V12R1 X V12R2 X V12R3 X V12R4 X V12R5 onwards X SMS SERVER SMS Server Application V1R1 V1R2 V1R3 V1R4 V1R5 V1R6 V1R7 V1R8 V11R1 X X X X X X X V11R2 X X X X X X X V11R3 X X X X X X X V11R4 X X X X X X V11R5 X X X X X X V12R1 X X X X X X X V12R2 X X X X X X X V12R3 X X X X X X X V12R4 X X X X X X V12R5 and onwards X X X X X X X MATRIX PHONES SPARSH VP248 IP Phone Now onwards, compatible firmware will come with package itself. Use SPARSH VP248 firmware V5R21 provided with ETERNITY V12R5.4.0 package for GE/PE/NE and ETERNITY V12R5.4.1 package for LE/ME.

18 SPARSH VP310 Phone Now onwards, compatible firmware will come with package itself. Use SPARSH VP310 firmware V1R10 provided with ETERNITY V12R5.4.0 package for GE/PE/NE and ETERNITY V12R5.4.1 package for LE/ME. SPARSH VP330 Phone Now onwards, compatible firmware will come with package itself. Use SPARSH VP330 firmware V1R10 provided with ETERNITY V12R5.4.0 package for GE/PE/NE and ETERNITY V12R5.4.1 package for LE/ME. SPARSH VP510 Phone Now onwards, compatible firmware will come with package itself. Use SPARSH VP510 firmware V1R8 provided with ETERNITY V12R5.4.0 package for GE/PE/NE and ETERNITY V12R5.4.1 package for LE/ME. MATRIX SOFT UC CLIENTS: SPARSH M2S (Android) SPARSH M2S (Android) Application V1R1 V1R2 V1R3 V1R4 V1R5 V1R6 V1R7 V11R3 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5 and onward SPARSH M2S (ios) SPARSH M2S (ios) Application V1R1 V1R2 V1R3 V1R4 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5 and onward

19 Note: 1. For SPARSH M2S Android, V1R2 onwards versions support RTP Relay 2. For SPARSH M2S ios, V1R1 onwards versions support RTP Rely 3. Direct RTP is not supported by SPARSH M2S VARTA WIN200 Application V12R5.2 Release-1 V12R5.3 Release-1 V12R5.3.3 V12R5.4.0 for GE/PE/NE V12R5.4.1 for LE/ME VARTA WIN200 V1R1.2. V1R4 3