Skip to end of metadata
Go to start of metadata


Table of Contents

 


About EdgeMarc 16.4.0 Release Notes

This document describes new features, the latest hardware and software requirements, known limitations, and other pertinent release information for the latest release of EdgeMarc VOS 16.4.0.

Related Documentation

The EdgeMarc VOS 16.4.0 documentation is located at the following Ribbon Wiki space: EdgeMarc VOS 16.4.x Documentation Home.

Release Notes Use and Distribution

Ribbon product release notes are protected under the copyright laws of the United States of America. This work contains proprietary information of Ribbon Communications, 6500 Chase Oaks Blvd, Suite 100, Plano, TX 75023 U.S.A.. Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from Ribbon Communications.

Problems or Questions

For problems or questions, contact the Global Support Assistance Center:

Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal

Voice: +1-833-RIBBON1 (1-833-742-2661)

About EdgeMarc VoIP Operating System (VOS)

The EdgeMarc is a flexible, easy-to-use session border controller that provides critical networking functions for IP-based voice and data. EdgeMarc VoIP Operating System (VOS) provides award-winning features for converged networking environments. These features enable the EdgeMarc to act as an enterprise session border controller and demarcation point for managed services.

Release History

ReleaseDatePurpose
Release 16.4.0

  8/15/2022

New Features, Improvements, Issues Resolved

Supported Platforms

EdgeMarc VOS version 16.4.0 supports the following platforms:

  • 2900 Series
  • 6000
  • 4800 Series
  • 7000 Series
  • 300 Series

Refer to EdgeView and EdgeMarc Interoperability Matrix for a detailed EdgeMarc VOS interoperability matrix.

New Features in This Release

The following new features are included in this release:

Issue IDFeatureDescription
EM-26650

Privacy header handling

A GUI option has been included such that the user can configure whether the SIP server(s) is trusted or not. EdgeMarc should pass through a privacy header in inbound INVITE to outbound INVITE in case the outbound SIP server or trunking device is trusted. EdgeMarc should remove a privacy header from INVITE before forwarding it to the outbound trunking device in case that outbound SIP server or trunking device is NOT trusted.

For detailed information, refer Best Practice - Configuring B2BUA with Header Manipulation Rules.

EM-26776

MS Team - SIP-ALL FQDN - Change

The Edgemarc supports updates to the trusted MS Teams server lists per Microsoft request.

For detailed information, refer the section Configure the SBC for Microsoft Teams Direct Routing#ConfiguringtheB2BUAandHeaderManipulationrules

EM-26679

SIP OPTION Pass through to PBX

The Edgemarc can now respond to SIP Options requests received from the IP network based on the status of a configured PRI.

For detailed information, refer ISDN PRI and Survivability.

EM-26900

Add VRRP support to the EM-7300

The Edgemarc 7300 series now supports VRRP.

EM-26632

Receiving ARP Trap

The Edgemarc can now communicate the LAN side ARP table contents to an Edgeview that is running code with corresponding support. This feature requires Edgeview 16.4.

EM-26371

Message Translation feature for 180/183 with/without SDP

The Edgemarc GUI contains new options to control SIP message translation between 180 and 183 messages.

For detailed information, refer Configuring Message Translation of 180/183 with or without SDP, and Use VoIP ALG settings.

EM-26947

SIP Proxy Load Balancing (Round Robin)

The Edgemarc now supports outbound load balancing across SIP servers.

For detailed information, refer Configure SIP Server Reachability, and Configure SIP Protocol Settings.

EM-27259

Enable sysloging of PRI from EdgeView

When the Edgemarc is used with a compatible Edgeview, ISDN logging can be enabled and disabled via Edgeview. This feature requires Edgeview 16.4.

Required Software Versions

The following software versions are required for this release and are available for download from the Customer Portal:

ProductDate
EM VOS 16.4.0

8/15/2022

How to Verify Currently Installed Software/Firmware Versions

Use the EdgeMarc WebUI to verify the currently installed software version.

  1. Open the WebUI and click the Admin tab.
  2. On the Admin page, you can see the current software version under Software Version.

Upgrade Notes

This section contains specific upgrade notes for customers planning to upgrade to EdgeMarc VOS 16.4.0. For details on supported releases and upgrades, see Upgrade Firmware.
To download a software package from the Ribbon Support Portal, refer Ribbon Support Portal - Download Center

Resolved Issues

Resolved Issues - Severity 1

Issue IDCase No.SevProblem DescriptionResolution

EM-26935

220119-4087451Three way conference calls with one or more SRTP legs are not processed correctly.

SRTP calls now correctly decrypted in a conference environment.

Workaround: None.

EM-26774

211115-4000341Phones that are registering without 'Expires' header were unable to register after the initial Register. The root cause is that the re-Registers without expires header were treated as de-register in EM.

If the received register doesn't contain an expires header or expires parameter in contact header, it will be treated as a 'register' instead of 'de-register'.

Workaround: N/A.

EM-26738

211111-3995221Multiple instances of codecs in SDP are not properly stripped with 'SDP Modification' configuration. Internal logic in EM was checking only for a single occurrence of a codec while stripping. 

Fix is done to handle 'codec-delete' to properly strip the codecs with multiple instances in SDP.

Workaround: N/A.

EM-27114

211213-4041311

The Edgemarc was not routing SIP REGISTER messages properly in some survivability failover scenarios.

Corrected handing of REGISTER messages in failover cases.

Workaround: N/A.

EM-27049220304-5624701The "401 Unauthorized" messages for SUBSCRIBE were not getting forwarded to the client. Also while monitoring mandlogs, mutex logs were observed immediately after receiving SUBSCRIBE.

The below fixes were done -
1. Fix done for forwarding 401 messages to the client with b2bua "Send To: Trunking Device: None" case.
2. Additional fix was done for mutex logs observed when DNS query fails without a response.

Workaround: N/A.

EM-27196

220409-5725831

Race condition/Mand crash when the challenged REFER request got 403 response.


Correction is done by assigning right transaction in the statemachine.

Workaround: N/A.

EM-27115

220112-4078041EM was not sending REGISTER to SBC with a new call-id even after the client sends a REGISTER with a new call-id.

Fix done to reset the register core, if the call-id changes for a client.

Workaround: N/A.

EM-27162

220411-5727851No Ring Back Tone provided for outbound call from PRI when 183 received without SDP.

Fixed logic to send alert while receiving 183 without SDP as well, similar to 180 without SDP.

Workaround: None

EM-27321220614-5901631

EM2009a refer domain used an not proxy ip. 

Corrected an issue where the Edgemarc used an incorrect IP when translating SIP Refer messages.

Workaround: N/A.

Resolved Issues - Severity 2/3

Issue IDCase No.SevProblem DescriptionResolution

EM-27068

220311-5644162Incorrect value for priority in the SIP Server Reachability table in the Survivability page. The root cause is that the priority value was stored in a variable that could not accommodate its 0-65525 range. Its variable type was unsigned char, which can only accommodate a 0-255 range. Thus, if the priority was over 255, the value could not be stored correctly.

Increased the size of priority in DNS structures to accommodate its 0-65535 range. A similar change was made for weight because it was also too small for its same range.

Workaround: N/A.

EM-27173220413-5736292Calls intermittently have incorrectly mangled Request URI line.

Change is done for EM to not preserve the Contact header from OPTIONS response.

Workaround: N/A.

EM-27366220622-5923492EdgeMarc incorrectly translating SIP REGISTER messages. The EdgeMarc continues to use the same address from the first REGISTER message it received for a particular DID regardless of external SIP device config changes including either change in request domain or call-id from LAN.

EdgeMarc will recreate a new SIP REGISTER cores with updated target and domain information for each new REGISTER anytime when there is a change in the request domain or SIP Call-ID.

Workaround: N/A.

EM-26173

210127-356013

3Not able to log in to EM GUI when browsing via an FQDN when session management is enabled. The root cause is that the domain field could not pass when enabled session management.

Ignore the domain field.

WorkaroundAn upgrade is required to resolve this issue.

EM-27216

220409-572583

3If Remote and Local URI Domain headers contain "anonymous.invalid" as domain, the EdgeMarc will use the custom domain from SIP Settings Page in REFER-TO header and local uri in REFERRED-By header respectively.

Made the fix by adding sipserver domain in REFER-TO header and local uri in REFER-BY header if the remote uri is "anonymous.invalid"

Workaround: None

EM-27275

211018-396087

2

RTP streams with invalid time stamps were observed on EM2900 running TCP SIP and HA. An improper value set to the protocol field while replicating RTP stream information to the standby system caused this issue.

Protocol information, RTP entry start, and last received timestamp information will be updated on standby every 60 seconds. Also updated debug logs to print the last RTP received time.

Workaround: N/A.

EM-26962Security - OpenSSL - New Version - Port - 1.1.1m2OpenSSL has been updated.

Code is fixed to updated the OpenSSL.

Workaround: N/A.

Known Issues

Known Issues - Severity 1

There are no known issues of high severity in this release.

Known Issues - All Other Severities

Issue IDCase NoSeverityProblem DescriptionWorkaround
EM-27420-2TLS registration of an FXS port on an ATA 302/304 does not work when IPv6 SIP proxy is specified. TLS with an IPv4 SIP proxy is functional as is UDP and TCP transport for IPv6 SIP proxies.N/A.
EM-27418-2After an upgrade from VOS version 15.8, configuration of VoIP and SIP parameters may become blocked if the SIP Server Transport is configured as Pass Through and one or more SIP transports is set to blocked on the VoIP page. A warning on the VoIP and GUI pages is displayed. As a workaround, change the SIP Server Transport setting to match the SIP transport protocol in use.N/A.
EM-27451-2In a LAN (RTP) to WAN (SRTP) call, multiple changes in codec in the media/audio stream during early media phase (before the call connects) can result in one way audio once the call connects.

Switch to RTP. This problem is not observed in RTP to RTP calls where the media is not encrypted. 

EM-27416-3A call destined for an FXS port that is processed by the B2BUA function does not ring with the ring pattern selected for the port on the SIPUA → Advanced page. The port uses only the default ring pattern.N/A.
EM-26273-3An incorrect Lost Packet counter may be displayed on the Survivability page if the configured SIP server can not be resolved by DNS.N/A.
EM-26923-3The EM accepts the following FQDN: some_fqdn.com but does not resolve it. Nor does an error indicate the Underscore character is illegal character according to RFC 1123.N/A.
EM-27435-3Inbound call from Microsoft Teams to SIP phone and then subsequently transferred (blind or consultative) to another SIP phone can lead to one-way audio. This occurs with media bypass disabled. It is not observed with media bypass enabled.  N/A.