RELEASE NOTE ETERNITY Range of IP-PBX

Transcription

1 RELEASE NOTE ETERNITY Range of IP-PBX DATE: 12 th June, 2017 AUTHOR: Vishal Govindiya VERSION: ETERNITY LE V12R5.4.1, ETERNITY ME V12R5.4.1, ETERNITY GE V12R5.4.0, ETERNITY PE V12R5.4.0 and ETERNITY NE V12R5.4.0

2 Affected Configuration Will this firmware upgrade affects system configuration? NO Defaulted Parameters Sr. GUI Page Link Parameters Remarks No 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 --

3 Upgrading Procedure 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 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.

4 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

5 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 ETERNITY NE: Login to the FTP of ETERNITY Step: 1 Delete/Remove everything from 'system' folder on FTP. Copy below files/folders in first phase: A) Files to be copied: o etne_cpu_dsp_boot1_v1r1.mfb o etne_cpu_dsp_boot2_v1r1.mfb o etne_dsp_app_adaptive_v*r*.mfb o etne_dsp_app_spirit_v*r*.mfb o etne_dspimgldr_v1r1.o o etne_ipccreate.o o etne_mstr_app_*.o o etne_slave_app_*.o o systemver

6 o wdtserver o ShellCommand.o o para.cfg B) Folders to be copied: o et_install o scripts o system_upgrade Now, reboot the system and wait for system up (GUI Access). (At this moment VoIP and Extended IP Phone will not function). Step 2) Now, do not delete anything and copy the remaining files/folders: A) Files: o build.txt, o EON48D_v*r*.mfb, o EON510_v*r*.mfb, o EON310_v*r*.mfb, o etne_voipserver_v1r*.o, o ExIP_BuildInfo.txt, o extip_v**r**.tar.gz B) Folders: o voip_upgrade o vopp

7 o drivers Do not use (Ignore) vsftpd.conf of system folder as its already present in system_upgrade folder. Reboot the system. System is now successfully upgraded. Firmware of SPARSH VP310, SPARSH VP330 and SPARSH VP510 IP phones o Remove all files from FTP path : /ExtendedFirmware/ o Copy all firmware files (*.tar.gz) from ETERNITY_NE_Pendrive/ExtendedFirmware folder to below path on FTP: /ExtendedFirmware/ o Verify all firmware file (*.tar.gz) information (File Version, Name & Checksum) in ExIP_BuildInfo.txt file in below path of FTP: /system/exip_buildinfo.txt o Caution: Do not copy and paste whole ExtendedFirmware folder on FTP path. Packages USB (Pendrive) Package ETERNITY ME_GE_PE File Name File Size MD5sum ETERNITY_ME_GE_PE_V12R5.4.1_USB.zip 11,464,953 bytes 36f3dbba105c0527f68695f62bf01c6a USB (Pendrive) Package ETERNITY LE Date Mar 30, 2017 File Name File Size MD5sum ETERNITY_LE_V12R5.4.1_USB.zip 11,467,419 bytes 14b4a2cee1231c15622ad5161eef025f

8 Field Package ETERNITY ME File Name File Size MD5sum ETERNITY_ME_V12R5.4.1_Field.zip 15,667,606 bytes 3880cefbb560e2e6b6e8f657f6f42544 Field Package ETERNITY LE File Name File Size MD5sum ETERNITY_LE_V12R5.4.1_Field.zip 10,067,434 bytes cbcaba e00d27b536bf51a31f2 Field Package ETERNITY GE File Name File Size MD5sum ETERNITY_GE_V12R5.4.0_Field.zip 16,123,396 bytes cb60226ab56707f240d103ba85bbea06 Field Package ETERNITY PE File Name File Size MD5sum ETERNITY_PE6S_V12R5.4.0_Field.zip 11,464,689 bytes aa c39f683b0db0a7481ea5ac

9 DDI Support for T1E1 in Network Mode. Modifications/Optimizations Notes We have received many requirements from field and use cases even, by considering we have supported DDI routing in Network mode logic and configuration will remain same as Terminal mode. NA System controlled "LEC"-Line echo cancellation support in EON 310 & EON 510 Notes Supported system controlled LEC in EON310 and EON510 for digital line echo cancellation.(i.e. mainly for ISDN and SIP) NA NEV2: Allow P2P table as a Trusted IP address for IC Call on P2P Trunk Notes Here P2P table works as a Trusted IP address for Incoming and Outgoing call on P2P Trunk NA E911 License for Direct 911 emergency dialing Notes We have restricted direct dialing of 911 as Emergency number without Hospitality E911 License. This is added to prevent illegal trading of system. NA

10 Validation flag for binding information received in Contact header Notes In one of the case of SIP Trunk provider, we found that Contact Header contains different IP Address then send in Register Request. Previously we were not allowing such Registration considering rule of RFC Now we have given customized flag to validate the binding information, considering multiple cases. Play ring for Waiting Call in EON510 Notes We have supported second ring for waiting in EON510 same as EON48 This feature is supported with New Hardware (i.e. Hardware version V2R4 onwards yet to be released) and Software combination only, for existing phones this features is not supported because there are hardware changes. NA Password will not get defaulted when system is upgrade from V12R5.X to V12R5.4 Notes In earlier version system password was getting defaulted when system was upgrade from V12R5.X to any above version. We have take care of the same in this version. Detecting_Digits_without_Playing_Dial_Tone_on_Radio_Port Notes When greet to dial is set in radio port parameters, the system will not play dial tone and will be in DTMF Receive state. NA NA

11 Copy Trusted IP address while copy SIP Trunk Parameters Notes Trusted IP address parameters will also be copied while using copy option in SIP Trunk Parameters. Previously this parameters were not copied. NA NA NA NA Reported from field: Bugs Solved FIT # FIT # FIT # FIT # FIT # In CLI based routing VMS Auto Attendant Profile is not configurable Added support of Call Forward to Voice mail for Open SIP phones In earlier version when call forward was set from any Open SIP phones it was not working, and user was redirected to Home node instead of User Mailbox. Simultaneous reminder alarm issue. We have increased number of Reminder Alarms to 250 for ETERNITY LE, ME and GE, to serve more numbers of Reminders simultaneously for Hospitality requirement. For ETERNITY PE, NE its 48. NA NA In E1-CAS MFCR-2 when called party is busy, calling party gets silence instead of busy tone. In case of MFCR-2 signaling when called party is busy, busy tone needs to be generated locally which we were not doing in earlier version as per standard. NA Transferred call is not getting retrieved if VP330 is busy In case of Blind Transfer of incoming call on SPARSH VP330 to other extension and the transferred party is not receiving the call, the call should come back to VP330 irrespective of Status of VP330 whether free or busy. This is achieved in the updated version.

12 FIT # FIT # FIT # FIT # NA SIP Trunk not getting registered in VoIP_V2R7 showing error "No contact in 2XX header" but getting registered in V2R5 As mentioned earlier we have now provided customized option to validate the contact header. Note: VoIP card version need to be upgrade to V2R9 it will be released in May-17 Noise on AOP when we make Conference call When 3 party conference is made with SLT as one of the member noise starts on AOP port and if that SLT goes On-Hook noise stops. NA When upgrade system to V12R5.2 to V12R5.3, Q.SIG with Service Provider(MSP) stops working When system upgrade is done from V12R5.2 to V12R5.3, the Incoming calls coming from the QSIG line rings for one ring on extension and then gets disconnected by its own. Sometimes, even the outgoing call gets disconnected with one ring at other end. This is now resolved. NA Missed call is not showing in DKP log This issue was observed on CO line randomly. FIT # In Multi-party conference, second call is coming even when call appearance is set to 1 FIT # Currently we have taken care this scenario, BLF interaction related to same is pending and it will be taken care in next release. Ring mute is not working properly Ring mute is set in SPARSH VP510 and Call capacity is more than 1. VP510 is busy on a call and a call comes on it. When current phone hangs up, the ring is played on VP510 for a fraction of seconds which actually should not be the case. This is now Resolved. NA

13 Found during testing: Sr. No. Issue Title with Summary #1 Black listed IP log entries are not shown in SNMP Notification. #2 In-built Voice Message upload is not working in ETERNITY ME CPU in case of two CPU cards in a Redundancy system #3 SNMP: removed VoIP link then it gives VoIP link down traps for LAN &WAN but at that time it gives LAN &WAN IP address #4 Incoming and Outgoing call stopped working through CDMA #3 When Registrar server address set as Router/Stun's IP address in Auto provisioning System does provide config file, and rejects the request with 404 not found response. #4 In IP Phone menu, Ring after delay Menu Option is not working, but set value is reflected in GUI. #7 SNTP Query fails on Power recycle of System when Domain Name is programmed as SNTP server #5 Wrong value of Hardware slot-port in the SFL for thermal shutdown event #6 Digits are not shown on LCD of EON 510 until whole number dialed out in Outgoing Call. #10 SLT HW test failed and retry option not shown #11 CO LED is not updating in all pages of EON74 #12 CPU 2 is taking 16 minutes to roll over from Active to Stand by mode in Hardware test #8 DKP gets Error tone while pressing Next key in DKP menu navigation #9 VMS Mailbox deletion in Range is not working properly #15 SMS Gateway: Check status of sms gateway client IP address #10 Keypad Lock/Unlock is not working from Extension Search Page #11 Network status Delete button is not working properly in DHCP Mode. #12 DSS key assigned to Emergency conference not working in DKP and SIP Extension #13 System getting reboot when Date & Time page is refreshed continuously #19 CLONE - System getting reboot when Date & time page is refreshed continuously #20 ME,LE Hardware test is getting failed in ETERNITY V12R5.4

14 #21 System is not getting up when System is prepared form V125R.3 Or Below Hex File when USB of same version is inserted. [When same system is upgraded using Ftp, system was working ok. Field reported: Known pending issues FIT # FIT # The Calling from SIP Extension through CO and GSM has stopped working Outgoing calls from CO line stops randomly while Incoming calls works but without Caller ID. FIT # E1 Over Fiber Optics gets down when data channel is increased to 3 -- Delay in LCD update for loop calls Internal known: #1 System shows called party in ringing state without providing RBT to caller when called SIP Extension is switch off/unreachable before sending the register request to system. #2 Unexpected notifications on SPARSH VP330 LCD when SPARSH VP330 is in call and redundancy occurs #3 In case of DSS key for SIP Extension is configured on any DKP or Proprietary SIP Phone and Call Pick-up is enabled in CoS then LED cadence of DSS key is not glowing in Blue color. #4 In SPARSH VP330 and SPARSH M2S, Call Pick-up through soft BLF key is not working if Call Pick-up group is different #5 Auto restart issue in UC20G #6 Device Management Page: Reboot option for VP248 is not working. #7 EON510 waiting call beeps is remaining ON when user enables Ring Mute feature during the call. #8 DKP loop key is not getting updated when conference is disconnect after redundancy Important Notes 1) E911 License a) System which are sent from Production with V12R5.4 or above versions is not downgradable to lower than V12R5.4. Doing so, system will not be functional. b) System which are sent from Production with version lower than V12R5.4, can be upgraded/downgraded to any versions. [E911- License is not required for these system] 2) Auto Provision feature for Panasonic IP phone 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

15 5) IP validation is not available in Static Routing Page (SE Login Master Ethernet Port Parameters Static Routing Table) 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. Re-Invite 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. Known Limitations System will ignore any SIP message having packet size more than 2048 bytes. In such case, System will not give any response to such SIP messages. In case of no CLI is received in the incoming call over SIP Trunk, then for such calls will not get recorded using Call Tapping. System will convert video call with SRTP to audio after hold - unhold activity. Call gets stuck when try to handover conference call to Extended SIP Phones. When the system is working under load condition with multiple DSS532 consoles connected, then system may lag.

16 Telephony Service Provider (TSP) Compatibility Charts 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 COMMUNICATION MANAGER (ETERNITY ME) For ETERNITY ME Card Communication Manager 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.

17 For ETERNITY ME CPU Card (Hot Redundancy Supported Card) V10Rx V11R1 Communication Manager V5R1 V5R2 V5R3 V5R4 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 VMS (ETERNITY ME/GE/PE/LE) VMS V6R5 V6R6 V6R7 V6R8 V6R9.1.0 V6R9.2.0 V6R9.3.0 V6R9.5.0 V10Rx X X X X X X V11R1 X X X X X X V11R2 X X X X X X V11R3 X X X X X X V11R4 X X X X X V11R5 X X X X X V12R1 X X X X X V12R2 X X X X X V12R3 X X X X X V12R4 X X X V12R5.1 Release3 X X X X X X V12R5.2 Release1 X X X X X X V12R5.3 Release1 X X X X X V X X X X X

18 V X X X X X V12R5.4.0 X X X X X VMS (ETERNITY NE) VMS V6R5 V6R6 V6R7 V6R8 V6R9.1.0 V6R9.2.0 V6R9.3.0 V6R9.4.0 V10Rx X X X X X X V11R1 X X X X X X V11R2 X X X X X X V11R3 X X X X X X V11R4 X X X X X V11R5 X X X X X V12R1 X X X X X V12R2 X X X X X V12R3 X X X X X V12R4 X X V12R5 and onward X X X X X

19 GSM Card (ETERNITY ME/LE) It is recommended to use firmware provided with package itself. VoIP CARD (ETERNITY LE/ME/GE/PE) VoIP Server Version V2R1 V2R2 V2R3 V2R4 V2R5 V2R6 V2R7 V2R8 V11R3 X X X X X X X V11R4 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 T1E1 CARD (ETERNITY ME/LE) T1E1 Card 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

20 DATA CARD (ETERNITY LE/ME) DATA Card V2R1 V2R2 V11R3 X V11R4 X V11R5 X V12R1 X V12R2 X V12R3 X V12R4 V12R5 onwards DATA CARD (ETERNITY GE) V12R5 onwards V2R3 DATA Card Radio Interface Card (ETERNITY ME/LE) Radio Interface Card V1R1 V1R2 V1R3 V1R4 V1R5 V10R12.31 X X X X V10R12.00 X X X X V11R1 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 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

21 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 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. SPARSH VP310 Phone Now onwards, compatible firmware will come with package itself. Use SPARSH VP310 firmware V1R8 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 V1R8 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 V1R4 provided with ETERNITY V12R5.4.0 package for GE/PE/NE and ETERNITY V12R5.4.1 package for LE/ME.

22 MATRIX SOFT UC CLIENTS SPARSH M2S (Android) SPARSH M2S (Android) V1R1 V1R2 V1R3 V1R4 V1R5 V1R6 V11R3 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5 and onward SPARSH M2S (ios) SPARSH M2S (ios) V1R1 V1R2 V1R3 V1R4 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5 and onward 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 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.3 V1R4