RELEASE NOTE ETERNITY Range of IP-PBXs

Size: px

Start display at page:

Download "RELEASE NOTE ETERNITY Range of IP-PBXs"

Ashlynn Strickland
5 years ago
Views:

1 RELEASE NOTE ETERNITY Range of IP-PBXs DATE: 29 th Sept, 2016 VERSION: V12R5.3.0 AUTHOR: Tapan Upmanyu

2 Contents Parameters getting default when upgraded to current Version/Revision from Previous Version/Revision... 3 Upgrading Procedure... 4 New Features/Functionalities... 7 Modifications/Optimizations... 8 Bugs Solved Known pending issues Important Notes Inter-op cases Known Limtations Compatibility Charts... 18

3 Parameters getting default when upgraded to current Version/Revision from Previous Version/Revision Below given configurations are going to be defaulted with this firmware upgrade from the last field Release. Sr. GUI Page Link Parameters Remarks No 1 SE LoginMaintenance Auto Update Firmware Update Flag 2 Front Desk Login Wakeup Call Log All 3 SE LoginMaintenance SNMP Security Settings 4 SE Login VoIP Configuration Device Management 5 SE Login Use Quick Installation Wizard - Standard PBX Following parameters are getting defaulted 6 SE Login Use Quick Installation Wizard - Standard PBX SIP Trunks 7 SE Login Key Template VP248 SE Login Key Template VP310 SE Login Key Template VP510 SE Login Key Template VP330 8 SE Login VoIP Configuration Third Party IP-Phone General Parameters Primary NTP Server for all Third Party IP-Phones and Matrix SPARSH VP110 All All All All 1. Name 2. Number 3. Password 4. Profile 5. CPU Group This is only applicable for SNMPv3 (SNMP Version 3) VP Key Template NTP Server for Open SIP Phone 9 SE Login VoIP Configuration Third Party IP-Phone General Parameters Language File Download Path for Cisco IP-Phone 10 SE Login VoIP Configuration Third Party IP-Phone General Parameters Phone User Language File Download Path for Snom IP- Phone All All Language Path for Open SIP Phone

For ETERNITY LE: Upgrading Procedure Login to the FTP of ETERNITY. Delete all files from "system" folder. Copy all files from " Field" folder to "system" folder. Reboot the system.

4 For ETERNITY LE: Upgrading Procedure 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. 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" successful upgrade completion, it will show a message during web login as shown below.

Now login to FTP of ETENRITY again. Delete all files from "system" folder. Copy all files from " Firmware-Part-2" folder to "system" folder. Reboot the system. The system is upgraded successfully.

5 Now login to FTP of ETENRITY again. Delete all files from "system" folder. Copy all files from " Firmware-Part-2" folder to "system" folder. Reboot the system. The system is upgraded successfully. For ETERNITY NE: Login to the FTP of ETERNITY. Delete all files from "system" folder. Copy all files except the following from " Field" folder to "system" folder: o build.txt, o EON48D_v*r*.mfb, o etne_voipserver_v1r*.o, o ExIP_BuildInfo.txt, o extip_v**r**.tar.gz Copy following folders from " Field" folder to "system" folder: o et_install o scripts

6 Reboot the system and wait for the system to get started. Now login to FTP of ETENRITY again. Do not delete any file or folder. Copy following remaining files from " Field" folder to "system" folder: o build.txt, o EON48D_v*r*.mfb, o etne_voipserver_v1r*.o, o ExIP_BuildInfo.txt, o extip_v**r**.tar.gz Copy following remaining folder from " Field" folder to "system" folder: o voip_upgrade o vopp o drivers Reboot the system. The system is upgraded successfully.

7 New Features/Functionalities DSS532 support added. Description Notes DSSS 532 is supported for VP510 and EON510 Added access of ping and traceroute commands for se login from telnet. Description Notes Now ping and traceroute command is added in telnet se login. User can check the ping and traceroute for network reachability. This feature is only given through telnet. Support of Assitant Present Beeps in Conference Description Notes In Army, call Transfers and Conference are processed via Operator/Assitant. Before trasferrring the call, Operator creates a conference for introduction of both the parties and then transfers the call. In such cases, it s required that the connectd parties should know that the operator has left the conference to intiate discussion. This is a configurable parameter.

8 Modifications/Optimizations Modifications have been made for Call routing mechanism in Routing Group when SIP Extension or DKP member rejects the call. Description Notes When a call is placed on DKP/SIP Extension which is a member of Routing Group and if that DKP/SIP Extension rejects the call, system was not placing the call back on that SIP Extension next time for the same call. This is a configurable parameter. Increased the range of SIP provisional Timer. Description Note The SIP Provisional Timer range is increased from 10 to 180 sec. to 10 to 600 sec. This is a configurable parameter. Guest privacy related changes have been made for the Hotel mode. Description Now Guest Name, Guest Title etc. will be removed on Check-Out, previously it was retained till next Check-In. Notes Changes have been made in the default settings for Italy region. Description Notes Default settings for Disconnect Tone Detection and BRI Layer mode have been changed as per the settings suggested by our Partner.

9 FTP password for Extended IP Phone separated from the system FTP password. Description Notes The exsting design, phones have to be necessarily restarted whenever the SE password is changed. In the new design FTP password is changed, which solves the dependency of common password.

10 Field reported: Bugs Solved Display Called Party number as CLI functionality was not working in case of BRI trunks. Not In ETERNITY NE, AC Impedance test fails on all the CO lines, but works on CO line 1. SPARSH M2S is not getting registered with Eternity ME 16S V1 board. Not Not Not Not ETERNITY GE system hanged due to internal invalid parameter. Not Not Not Not 6553 gets printed as default in SMDR posting as PIN No. even if PIN dialing was not used to make an OG call. Conference Tone is different in ETERNITY LE from other ETERNITY Systems when India Region is selected. Not Not Not Not Not getting busy tone if second call comes on the same DDI number. Barge in and Raid not working in case incoming call is received from a Mobile trunk. SIM card gives Busy signal after checking Balance when network quality was very poor. When a call is placed on SIP Extension which is a member of Routing Group and if the SIP Extension rejects the call, system was not placing the call back on that SIP Extension next time for the same call.

11 System got hanged when PRI Call disconnect due to Notify message received on PRI line. Not Calling and Dial tone stops working after system is restarted in E1-CAS DTMF line. Not Eternity NE firmware incorrectly identifies NE 4 as NE 6. Not Not Not Not Peer to Peer calling is not working with ILC Card in VoIP V2R7 version. Not able to make call to Radio extension from SPARSH M2S/ ADR100/ ios/100/win200 and VP330. Not Not PRI-QSIG link goes down during an incoming call. Not Found during testing: #1 Issue: In Matrix Extended IP Phone, "Please wait" message gets displayed due to delay in INVITE message response. Not Not #2 Issue: Incoming external call on extension is not getting picked up using DSS-soft keys available on SPARSH VP330 or SPARSH M2S. #3 Issue: Wrong message is displayed for selective call pickup when auto callback ring is played

12 on the extension. #4 Issue: Voice Mail settings were not saved when these are copied using Copy functionality. Not Not Not Not #5 Issue: Wrong SLT port was displayed in system usage after power fail recovery in PFT card. Not Not #6 Issue: After conference call is terminated, LCD of VP510 was not clear. #7 Issue: Invalid Report name shown in Hotel Motel Activity log report view. Not

13 Known pending issues Field reported: While using Redundancy in ETERNITY ME or ETERNITY LE if you Restart the Active Card using Restart the System from Web Jeeves then system will also send Restart command to all "Slave cards. Now, in this case we observed that slave card gets restarted first before Standby CPU takes control and goes to Standby mode i.e. slave card will not respond until Start FSM command is received from the CPU. As Standby CPU Card gets active after some interval and it is having wrong information that all cards are Present in the system (Due to Redundancy database), it will not send Start FSM command to slave card. Slave cards will not work but Status will show OK and Card will also get detected in the System details. Workaround: Solution 1: If you use Restart the System command then from Active CPU card Restart All the Slave cards from Maintenance -> Restart the card. Solution 2: Use Power Off and Power On, if you want to upgrade the system or Restart the system. Some strings are in English when we change language to Spanish.

14 Internal known: #1 Improper status is displayed when subscribed party is in multi-party conference. #2 System shows called party in ringing state without providing RBT to a caller when called SIP Extension is switch off/unreachable before sending deregister request to system. #3 In SPARSH VP510, Reminder call is not rejected after selecting Reject option. #4 Trusted IP address of SIP trunk is not copied from source trunk to destination trunk/s after using copy functionality. #5 Unexpected notifications on SPARSH VP330 LCD when SPARSH VP330 is in call and redundancy occurs. #6 In ETERNITY PE, system response is delayed by 3-4 seconds after submitting SLT Hardware Template. System will not provid dial tone for 3-4 seconds after this action. #7 In case of DSS key for SIP Extension is configured on any DKP or Proprtitary SIP Phone and Call Pick-up is enabled in CoS then LED cadence of DSS key is not glowing in Blue color. #8 In SPARSH VP330 and SPARSH M2S, Call Pick-up through soft BLF key is not working if Call Pick-up group is different. #9 In ETERNITY NE, when copy SLT parameters in Web GUI is using Copy functionality, Voice Mail parameters are not getting copied to other SLT ports. #10 VM Upload is not working in CPU in case two CPU cards are present in ETERNITY ME.

15 Important Notes It is recommended to use RTP mode as TRANSCODING when Matrix SPARSH VP310, SPARSH VP330 or SPARSH VP510 used with Secure RTP. It may not work properly in RTP Relay and Direct RTP modes. It is not recommended to configure SIP Trunk to treat incoming call as Station if Call Pick-Up using DSS key is required for SIP Trunk. If configures to treat incoming call as Station then call pickup of incoming call on SIP Trunk using DSS key will not work. It is recommended not to use the Extension number with having # in it in case of Matrix COSEC Door interface is used for Door Lock open application for Building Intercom solution. It is recommended to use H264 codec for Video calls. Quality of Video might get degraded if all Video calls are with H263/H263+ codec. IPv6 is not supported by VMS. IPv6 is not supported by ETERNITY NE. IPV6 for SPARSH VP Extended SIP Phones, VARTA UC Clients, VMS and CTI Interface is not supported. DRTP is not supported in VARTA UC Clients, viz., VARTA WIN200, VARTA ADR100, VARTA ios100. Redundancy is not supported for SPARSH M2S Android and ios clients. Call taping for incoming trunk call without CLI will not work. In case of IP Phone/UC Client gets switched off or lost connectivity after getting registered with SARVAM UCS, the SARVAM UCS will give RBT to a caller as the called SIP Extension will remain in Registered state for SARVAM UCS or the SIP Registration time. In case the monitored Extension is in Conference then its Presence/BLF status may be some arbitary status. SPARSH VP248 will display a number instead of characters while searching a name using Dial by Name feature. This might happen when a user presses the keys too fast. FTP and Telnet password will not change when we update configuration from one system to another system. With new SLIC (SI32260) supported, and a Thermal alarm is generated, on returning to normal condition, break in speech is observed. This generally happens when phone is put in speech for 12 or more hours and 40mA loop current is configured. System performance may degrade when multiple 6 line DKP/IP Phones try to navigate menu simultaneously, System performance may degrade when system is attacked with heavy IP flooding. The SE programming commands to set/clear DSS keys from extension (using SE command) are no longer supported from V12R5.3 onwards. Removed programming SE command is For ETERNITY ME CPU, there is some modification in the ETERNTIY V12R5.x onwards due to which the jumper J12 and J14 needs to set as mentioned bellow. From factory, the Jumper

16 J12 and J14 position will be set as mentioned in the following table for ETERNITY V12R5.x onwards Firmware Default Jumper Position What will be received on Comm. Port 2 J12 J14 Eternity V12R4.x and before AB AB Kernel Debug and Application Data (i.e., Debug, SAL, SFL, SMDR, PMS, etc.) Eternity V12R5.x and onwards BC BC Application Data In case, the ETERNITY ME is upgraded from V12R4.9 or below to V12R5.2 and onwards and Comm Port 2 stops working then change the jumper J12 and J14 position on CPU form AB to BC.

17 Inter-op cases In Yealink SIP-T20P SIP phone with firmware version, when Call is with Direct RTP and remote user hold Yealink user then MOH will not play on Yealink. This issue is not observed in Yealink SIP-T28P SIP phone with firmware version. In Yealink SIP phone, when RTP Mode is RTP Relay and negotiated codec is on hold (on hold by remote user to Yealink user) is different than that of ongoing speech, MOH will not play on Yealink. One way speech will happen with Yealink phone when ILBC codec is negotiated with different payload number. Auto Provision feature for Panasonic SIP Phones is not working with IPv6 due to its own problem. When RTP Relay call is matured without SRTP with Grandstream GXV3175 SIP Phone, it will not accept SRTP parameters in Re-Invite sent by SARVAM UCS for Hold. ReInvite will be rejected by 488. No speech in SRTP call with Grandstream GXV3140 SIP phone when GSM codec is negotiated. TCP/TLS port will get closed in case of Grandstream GXV3140 SIP phone sends keep alive. It is expected from SIP Phone/Soft phone to send a ping (double CRLF) and wait for single CRLF from remote peer. When SARVAM UCS sends a single CRLF as Pong, the Grandstream SIP Phone sends FIN ACK and disconnects the TCP connection used for Registration. So next time onwards Grandstream SIP phone will send INVITE from a port different than used for Register. Such requests will get rejected. If user wants to use TCP/TLS for this Grandstream Phone, it is recommended to disable Keep-Alive. Known Limtations 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 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.

18 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.1 Release3 x x x V12R5.2 Release1 x x x V12R5.3 Release1 x x x

19 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.1 Release3 V12R5.2 Release1 V12R5.3 Release1 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) V10Rx Communication Manager V5R1 V5R2 V5R3 V5R4 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

20 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 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.1 Release3 X X X X X V12R5.2 Release1 X X X X X V12R5.3 Release1 X X X X X

21 GSM Card (ETERNITY ME/LE) It is recomanded to use firmware provided with the 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.1 Release3 X X V12R5.2 Release1 X X V12R5.3 Release1 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

22 DATA CARD (ETERNITY LE/ME) DATA Card V2R1 V2R2 V11R3 X V11R4 X V11R5 X V12R1 X V12R2 X V12R3 X V12R4 V12R5.1 Release3 V12R5.2 Release1 V12R5.3 Release1 DATA CARD (ETERNITY GE) V12R5.1 Release3 V12R5.2 Release1 V12R5.3 Release1 DATA Card V2R3 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.1 Release3 X V12R5.2 Release1 X V12R5.3 Release1 X

23 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 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.1 Release3 X X X X X X X V12R5.2 Release1 X X X X X X X V12R5.3 Release1 X X X X X X X

24 MATRIX PHONES SPARSH VP248 IP Phone Now onwards, compatible firmware will come with the package itself. Use SPARSH VP248 firmware V5R19 provided with ETERNITY V12R5.3_Release 1 package. SPARSH VP310 Phone Now onwards, compatible firmware will come with the package itself. Use SPARSH VP310 firmware V1R6 provided with ETERNITY V12R5.3_Release 1 package. SPARSH VP330 Phone Now onwards, compatible firmware will come with the package itself. Use SPARSH VP330 firmware V1R7 provided with ETERNITY V12R5.3_Release 1 package. SPARSH VP510 Phone Now onwards, compatible firmware will come with the package itself. Use SPARSH VP510 firmware V1R2 provided with ETERNITY V12R5.3_Release 1 package.

25 MATRIX SOFT UC CLIENTS SPARSH M2S (Android) SPARSH M2S (Android) V1R1 V1R2 V1R3 V1R4 V1R5 V1R6 V11R3 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5.1 Release 3 V12R5.2 Release 1 V12R5.3 Release 1 SPARSH M2S (ios) SPARSH M2S (ios) V1R1 V1R2 V1R3 V1R4 V11R4 V12R1 V12R2 V12R3 V12R4 V12R5.1 Release 3 V12R5.2 Release 1 V12R5.3 Release 1 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 VARTA WIN200 V1R1.2.3

RELEASE NOTE ETERNITY Range of IP-PBX

RELEASE NOTE ETERNITY Range of IP-PBX DATE: 15-Dec-2016 VERSION: V12 R5.3.2 AUTHOR: Tapan Upmanyu Contents Parameters which are getting default when upgraded to current Version/Revision from Previous Version/Revision...