RELEASE NOTE - Matrix Wiki · PDF fileRELEASE NOTE ETERNITY ... #4 Trusted IP address of SIP trunk is not copied from source trunk to destination trunk/s ... SPARSH VP248 will display

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

Upgradation Procedure ............................................................................................................................ 4

Modifications/Optimizations .................................................................................................................... 8

Bugs Solved ............................................................................................................................................... 8

Known pending issues ............................................................................................................................. 10

Important Notes...................................................................................................................................... 12

Inter-op cases .......................................................................................................................................... 14

Known Limitations .................................................................................................................................. 14

Compatibility Charts ............................................................................................................................... 15

Parameters which are getting default when upgraded to

current Version/Revision from Previous Version/Revision

None (With reference to V12R5.3.0)

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:



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.

Now again login to FTP of ETENRITY


Copy all files from " Firmware-Part-2" folder to "system" folder

Reboot the system


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

For ETERNITY NE:



Copy all the files except following files from " Field" folder to "system" folder

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

Copy following folders from " Field" folder to "system" folder

o et_install

o scripts

o system_upgrade

Reboot the system and wait to system get started

Now again login to FTP of ETENRITY

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 EON510_v*r*.mfb,

o EON310_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


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/Extended Firmware

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”

Caution: Do not copy and paste whole “ExtendedFirmware” folder on FTP path.

Modifications/Optimizations

Updated SLIC library

Description SLIC library related changes

Notes In case of ETERNTY ME & LE, SLT & TWTxSLT combo cards have their own firmware. SLIC library changes applicable to SLT and TWTxSLT combo cards. Firmware version of SLT card & TWTxSLT combo card should be V4R5.

Applicable Model

ETERNITY LE ETERNITY ME ETERNITY GE ETERNITY PE ETERNITY NE

NA NA √ √ √

Bugs Solved Field reported:

PMS string for Reminder Alarm was not working.

Applicable

Model


√ √ √ √ Not Applicable

LE CPU was not booting up properly

Description This is related to master application. System was getting stuck while reading IC SMDR

due to unexpected data received.

Applicable

Model


√ √ √ √ √

Eternity ME GSM Card firmware update issue

Description Wrong firmware was getting updated in GSM card through system.

Applicable

Model


√ √ Not Applicable Not Applicable Not Applicable

In CLI based routing VM Att. Profile was not configurable

Description User was not able to set VM Auto Att. Profile in CLI base routing.

Applicable

Model


√ √ √ √ √

Found during testing:

Issue VM Upload is not working in CPU in case of two CPU cards present in ETERNITY ME

Description SE can’t upload VM in Active CPU when Active & Stand by CPU are present in the

system.

Applicable

Model


√ √ Not Applicable Not Applicable Not Applicable

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 get 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 CPU. As Standby CPU Card is getting Active after some interval and it’s having wrong information that all cards are Present in system (Due to Redundancy database) so it will not send Start FSM command to slave card. Slave cards will not work but Status will show OK, Card will also get detected in 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

Internal known:

#1 Improper BLF status is displayed when subscribed party in multiparty conference

#2 System shows called party in ringing state without providing RBT to 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 delay by 3-4 second after submitting SLT Hardware Template. System will not provide dial tone for 3-4 second after this action

#7 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.

#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 using “Copy” functionality, Voice Mail parameters are not getting copied to other SLT ports

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 degrade 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 get registered with SARVAM UCS, the SARVAM UCS will give RBT to caller as the called SIP Extension will remain in Registered state for SARVAM UCS or the SIP Registration time.

In case of the monitored Extension is in Conference then its Presence/BLF status may be some arbitrary status

SPARSH VP248 will display number instead of character while searching name using “Dial by Name” feature. This might be happened when user presses keys too fast.

FTP and Telnet password will not be changed when we update configuration from one system to another system

With new SLIC (SI32260) supported, when Thermal alarm is generated and on returning to normal condition, when Thermal alarm clears, break in speech is observed. This happens generally 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 1254.

For ETERNITY ME CPU, there is some modification in the ETERNTIY V12R5.x onwards due to which the jumper J12 and J14 need to set as mentioned bellow. From factory, the

Jumper J12 and J14 position will be set as per mentioned in 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 of 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.

Inter-op cases

In Yealink SIP-T20P SIP phone with firmware 9.16.0.70 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 2.72.0.1 version.

In Yealink SIP phone, when RTP Mode is RTP Relay and negotiated codec in hold (on holding 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 ping (double CRLF) and wait for single CRLF from remote peer. When SARVAM UCS send single CRLF as Pong, the Grandstream SIP Phone send FIN ACK and disconnect the TCP connection used for Registration. So next time onwards Grandstream SIP phone sends INVITE from 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 Limitations

System will ignore any SIP message having packet size more than 2048 bytes. In such case, System will not give any response of 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, and then system may lag.

Compatibility Charts

Telephony Service Provider (TSP)

Master Application TSP Version Revision 1.0.0.0 1.1.0.0 1.1.0.1 1.1.3.0

V12R2 Release 1 √ √ x x

V12R2 Release 2 √ √ x x

V12R3 Release 1 x √ x x



V12R3 Release 4 x x √ √



V12R4 Release 3 x x x √



V12R5 and onward x x x √

COMMUNICATION MANAGER (ETERNITY ME)

For ETERNITY ME Card

Master Application 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.

For ETERNITY ME CPU Card (Hot Redundancy Supported Card)

Master Application Communication Manager

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 √ √ √

V125.3.2 X √ √ √

VMS (ETERNITY ME/GE/PE/LE)

Master Application 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


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 √ √

V125.3.2 X X X X X √ √

VMS (ETERNITY NE)

Master Application 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



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 √ √

GSM Card (ETERNITY ME/LE)

It is recommended to use firmware will provide with package itself.

VoIP CARD (ETERNITY LE/ME/GE/PE)

Master Application 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 √ √ √ √ √ √

V12R5.3.2 X X √ √ √ √ √ √

T1E1 CARD (ETERNITY ME/LE)

Master Application 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





V12R1 √ √ √ √ X √ √ √ √ √

V12R2 √ √ √ √ X √ √ √ √ √

V12R3 √ √ √ √ X √ √ √ √ √

V12R4 √ √ √ √ X √ √ √ √ √

V12R5.1 Release3 √ √ √ √ X √ √ √ √ √

V12R5.2 Release1 √ √ √ √ √ √ √ √ √ √

V12R5.3 Release1 √ √ √ √ √ √ √ √ √ √

V12R5.3.2 √ √ √ √ √ √ √ √ √ √

DATA CARD (ETERNITY LE/ME)

Master Application DATA Card

V2R1 V2R2

V11R3 √ X

V11R4 √ X

V11R5 √ X

V12R1 √ X

V12R2 √ X

V12R3 √ X

V12R4 √ √

V12R5.1 Release3 √ √



V12R5.3.2 √ √

DATA CARD (ETERNITY GE)

Master Application DATA Card

V2R3

V12R5.1 Release3 √



V12R5.3.2 √

Radio Interface Card (ETERNITY ME/LE)

Master Application 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 √ √ √ √

V12R5.3.2 X √ √ √ √

SMS SERVER

Master Application SMS Server

V1R1 V1R2 V1R3 V1R4 V1R5 V1R6 V1R7 V1R8



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 onward 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 V5R20 provided with ETERNITY V12R5.3.2 package

SPARSH VP310 Phone



SPARSH VP330 Phone



SPARSH VP510 Phone



MATRIX SOFT UC CLIENTS

SPARSH M2S (Android) Master Application SPARSH M2S (Android)

V1R1 V1R2 V1R3 V1R4 V1R5 V1R6

V11R3 √ √ √ √ √ √

V11R4 √ √ √ √ √ √

V12R1 √ √ √ √ √ √

V12R2 √ √ √ √ √ √

V12R3 √ √ √ √ √ √

V12R4 √ √ √ √ √ √

V12R5 and onward √ √ √ √ √ √

SPARSH M2S (iOS)

Master Application 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

Master Application VARTA WIN200

V1R1.2.3

V12R5.2 Release-1 √

V12R5.3 Release-1 √

V12R5.3.2 √

Documents

RELEASE NOTE - Matrix Wiki · PDF fileRELEASE NOTE ETERNITY ... #4 Trusted IP address of SIP trunk is not copied from source trunk to destination trunk/s ... SPARSH VP248 will display