RELEASE NOTE. VoIP Server Card. DATE: 7 th January, 2016 VERSION: V2R7 AUTHOR: Vishal Govindiya

Size: px

Start display at page:

Download "RELEASE NOTE. VoIP Server Card. DATE: 7 th January, 2016 VERSION: V2R7 AUTHOR: Vishal Govindiya"

Dortha Hill
5 years ago
Views:

1 RELEASE NOTE VoIP Server Card DATE: 7 th January, 2016 VERSION: V2R7 AUTHOR: Vishal Govindiya

2 Upgrading Procedure: Login as se User in FTP of VoIP Server Card with Password of Master CPU Remove all old files from "/matrix/appl/" folder of board Copy all files from newly released "appl" folder to "/matrix/appl/" folder of board Reboot the system Wait for 5 minutes Now VoIP server card is upgraded New Features: Following features will work with Master V12R5.2.0 and onwards with VoIP Server V2R7 and onwards: 1. Added support for SPARSH VP510 Extended IP-Phone 2. Added support for VARTA WIN200 The Windows Desktop UC Client 3. Support of Redundancy for Extended Terminals: Extended Terminals will automatically get registered to Active CPU when Redundancy of CPU takes place in ETERNITY ME/LE without doing any configuration changes in Extended Terminals 4. Revised BLF and Presence Subscription Logic: Considering requirement of increasing Presence/BLF subscription due to added support of VARTA WIN200 now VoIP Card supports 300 Presence Subscription and 600 BLF subscription in total 5. Updated handling of nonce in VoIP Server Card to enhance security: VoIP Server Card will now generate unique nonce value for REGISTER, INVITE, SUBSCRIBE and PUBLISH request. This will enhance the security aspects of VoIP Server Card

3 Bugs Solved: In one of the call scenario, VoIP application crashes/reboots, on receiving BYE request from remote side. Issue was with call flow to stack which is resolved in this release DTMF were not getting detected when video call is made from SPARSH M2S to IP Door phone in RTP relay or Direct RTP mode While making call from SPARSH VP330 to an IVR, there was an issue in DTMF dialling Registration issue in SIP Extension will be observed if NAT keep alive is enabled. This was issue only in VoIP Server Card version V2R6 is solved Maximum Calls Supported: ETERNITY Variant IP Mode Addressing Number of Calls 1 Video =? Audio Port Range ME / GE / LE IPv4 Only 64(128 call legs) with Forking PE IPv4 Only 32(64 call legs) with Forking 1 Video = 4 Audio First 512 for Audio, Second 512 for Video 1 Video = 4 Audio First 512 for Audio, Second 512 for Video ME / GE / LE / IPv4 and IPv6 32(64 call legs) with 1 Video = 2 Audio First 512 for Audio, PE or IPv6 Only Forking Second 512 for Video Remarks: When H.263+ Video codec is used, quality of Video Call will degrade. Total call capacity per VoIP card will be 6 to 9 calls depending on the configuration

4 Compatibility with Matrix VoIP Products for Relay/DRTP Feature: Product ETERNITY CPU Card SPARSH VP248 IP Phone SPARSH M2S (Android client) SPARSH M2S (IPhone client) SPARSH VP510 IP Phone VARTA WIN200 Version V12R1 onwards V5R15 onwards V1R3 onwards V1R6 onwards (SRTP Feature) V1R1 onwards (Except SRTP Feature) V1R1 onwards V1R1 onwards Open/Known Issues: When audio call is initiated from Matrix SPARSH M2S/VARTA WIN200, during the call if called user request to switch the call from audio to video and if SPARSH M2S/ VARTA WIN200 user rejects the Video request, he will again receive one more dummy pop-up for video request. In this scenario, the 2 way speech remains unaffected When SPARSH VP310, SPARSH VP330 or SPARSH VP510 used with SRTP, may not work properly in RTP mode Relay/DRTP. Hence it is recommended to use RTP mode as Transcoding while using SRTP with above mentioned terminals. Transcoding mode can be set from VoIP Port Parameter page in GUI One way speech issue in SIP Extension or SIP Trunk in rare case

5 Inter-Operability Issues: In Yealink SIP-T20P phone with firmware version, when call is with DRTP and remote user hold Yealink user then MOH is not getting played on Yealink phone. This issue is not observed with Yealink SIP-T28P with firmware Other models of Yealink are not tested for this scenario In Yealink phone, when RTP Mode is Relay and negotiated codec in hold (on holding by remote user to Yealink user) is different than that of speech, MOH will not be played on Yealink phone One way speech with Yealink phone will be observed when ILBC codec is negotiated with different payload number in SDP negotiation When relay call is matured without SRTP in Grandstream GXV3175, it will not accept SRTP parameters in Re-Invite sent by VoIP card for Hold. Re-Invite will be rejected by 488 No speech in SRTP calls in Grandstream GXV3140, when GSM codec is negotiated Limitations: VoIP server card restarts when OPTIONS packets are flooded heavily Authentication ID must be unique for all the SIP extensions and Digest Authentication table. In case SE configures same Authentication IDs for two or more SIP extensions, they may face issues in registration. If you observe such issue then it is recommended to change Authentication ID for those extensions RTP Relay and Direct RTP mode is not supported with SPARSH VP248, when it is used in open SIP mode. Hence we shall always use it in Extended SIP mode only PTime (Packet Time) above 40 msec is not supported. This will result in speech distortion SDP negotiation is not supported in OPTION message

6 T38 RTP fax is not working between audio codes version 640 (VoIP Server Version V1R7 for ETERNITY GE/ME/PE) to 660 (VoIP Server Version V1R8 onwards for ETERNITY GE/ME/PE) & vice versa, but it is working fine between audio codes version 660 (VoIP Server Version V1R8 onwards for ETERNITY GE/ME/PE) Packets may get lost if PCAP is enabled This Version Revision will work with ETERNITY V10R10 and onwards Caution: Do not enable VoPP debug in VoIP card unless suggested by Matrix R&D Team, if VoPP debug is enabled then it will degrade the overall performance of VoIP card After upgrading VoIP Server card with firmware V2R3 or above one should not downgrade to older version using previously released field package. It must be downgraded with VoIP_Server_V2R2_Downgrade_firmware After upgrading VoIP Server card with firmware V2R6 or above one should not downgrade to older version using previously released field package. It must be downgraded with VoIP_Server_V2R4_Downgrade_firmware

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