SBC 06.02.01R000 Release Notes

V06.01.00F001

V05.00.04R000

V05.00.05F004

V05.01.01F001

V05.01.01F004

V05.01.01F005

V05.01.00F007

V05.01.02F003

V05.01.02R001

The password encryption method must be changed to SHA-512 method. The current BMC user password encryption method is md5sum, which is easy to brake the password.

Platform/Feature: SBC 5000/7000 Series: BMC

Re-installing the SBC from an ISO image followed by restoration of a previous configuration backup file can lead to the loss of encrypted configuration parameters. This can cause Radius authentication to fail unless the radiusSharedSecret is re-entered and CDRs also fails to be sent to the CDR server.

Platform/Feature: SBC Core: Platform

Restoration from backup configuration will re-install the encrypted keys required for the restoration of the encrypted configuration parameters.

Note: The backup configuration must be obtained from the SBC versions, which has the fix for SBX-46014.

Platform/Feature: SBC 7000 Series: EMA/EMS

The code has been modified to verify:

• the display of the appropriate messages in case of error scenarios.
• the password change per day for non-admin users in the CLI.
• that there is no discrepancy in EMA GUI and auth.log error message.

Platform/Feature: SBC Core: SIP

The wrong display of CPU utilization data in top command output after the SBC was upgraded to Kernel version 3.16. This is a known issue with all 3.16 and higher kernels.

Platform/Feature: SBC SWe: Call Control/Platform

To resolve this issue, the 06.02.01 documentation is updated with the following note:

Platform/Feature: SBC Core: Application: SBC Swe Cloud: Application

 kod nomodify notrap nopeer.

The BMC does not support DHCP. The DHCP option is available in BMC WEB UI.

Platform/Feature: SBC 5000/7000 Series: BMC

Platform/Feature: SBC 7000 Series: Media

During upgrade of standby server, availability of upgrade packages, is checked on active server, which can sometimes return errors and cause upgrade failure.

Product/Feature: SBC Core: Application

Platform/Feature: SBC 7000 Series: SIP

The file permissions do not follow least privilege.

Platform/Feature: SBC 5000/7000 Series: BMC

Platform/Feature: SBC Core: SIP

Time zone once set to any zone resets after reboot and after firmware upgrade.

Platform/Feature: SBC 5000/7000 Series: BMC

The BMC's version of ipmitool does not disable watchdog properly.

Platform/Feature: SBC 5000/7000 Series: BMC

The output from the AIDE cron job contains false positive indicators that the software was changed.

Platform/Feature: SBC Core: Platform

 In a downstream forking scenario, the SBC is adding SDP to the 200 OK response to an INVITE from the ingress leg when the 200 OK received from the egress leg did not contain SDP.

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: SIP

Invalid username format when user contains ".". When the username contains "." in the name, the user is created in the CDB instead of OS.

Platform/Feature: SBC Core: Platform

In SBC 5400, chassis.sh -r was reading wrong register values.

Platform/Feature: SBC 5000/7000 Series: BMC

The EMA node name displays incorrect value.
There was no predicate condition with cename.

Platform/Feature: SBC Core: Platform

SIP INFO DTMF to RFC2833 Inter working fails when ICE is enabled.

Platform/Feature: SBC Core: Platform

SBX-64232

An unexpected response from the licensing server caused the licensing client to repeatedly loop trying to retrieve the SWE-INSTANCE License. 

Platform/Feature: SBC SWe: Application

Platform/Feature: SBC 7000 Series: Call Control

SBX-64313 /
SBX-63782

Platform/Feature: SBC 7000 Series: Call Control

In a forking scenario, the SBC does not relay PRACK and UPDATE messages properly between the different dialogs.

Platform/Feature: SBC 7000 Series: Call Control

SBX-64322 /
SBX-63863 /
SBX-63862

In a forking scenario, the SBC does not relay the SDP in the second dialog 18x message if it is received at the same time as the first dialog 18x.

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: SIP

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: Call Control

User sftpadmin account expiration is not automatically extended with each usage.

Platform/Feature:SBC Core: Platform

Platform/Feature: SBC 7000 Series: Call Control

The SBC sends a 481 response to a reINVITE requesting to retrieve a call that is on hold. 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to properly respond to a reINVITE request for a call on hold and does not return error responses.

In an SBC cloud environment, when a snapshot of an instance is taken, metadata and user data are missing when attempting to use the snapshot to restore the instance.

Platform/Feature: SBC SWe/SBC SWe Cloud: Platform

Platform/Feature: SBC 5000/7000 Series: Application

SBX-64724 /

The SBC fails to load new announcements into NP Memory and the standby instance is not running the 10-minute timer.

Platform/Feature: SBC Core: Application

SBX-64730 /
SBX-64498 /
SBX-64729

The SBC is adding a 100rel to reINVITE requests.

Platform/Feature: SBC 7000 Series: Call Control

The SBC now sets the PRACK level to off when a call is connected, and it does not insert 100rel in reINVITE requests.

SBX-64732 /

Platform/Feature: SBC 7000 Series: Call Control

The SBC does not properly process a 183 response without SDP received after an UPDATE message.

Platform/Feature: SBC 7000 Series: Call Control

In a downstream forking scenario with preconditions, the SBC is not properly negotiating the preconditions for multiple forked 18x responses.

Platform/Feature: SBC Core: SIP

Platform/Feature: SBC Core: DSP

• to load during the server startup, or
• during the normal operation.

The BMC serial login is not working after changing password encryption method to SHA512. The serial login is not build with PAM.

Platform/Feature: SBC 5000/7000 Series: BMC

The BMC logs do not have time stamp.

Platform/Feature: SBC 5000/7000 Series: BMC

Adding the Cpx validation for Delete operation for Variable Action Type.

Platform/Feature: SBC Core: SIP

Added the following note to the "delete" operation type on the pages listed below:

Note: The "delete" operation type is not applicable for the Action type variable.

For example, when AOR1 is already registered with port1 and the SBC receives Refresh Register for AOR1 with different port number and same IP. In such scenario, the SBC is locally responding to Refresh RGISTER before response from Registrar is received. This was causing mismatch in relayed response.

Platform/Feature: SBC Core: Application

The code has been modified to relay the Register even after receiving any error response for a REGISTER for same AOR with different contact.

To achieve the old behavior of locally responding with error messages if REGISTER is received from the same source, following enhanced DBL config can be used.

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria offendingEvent triggerEventType receiptOfMessage methodType REGISTER methodResp 403

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria occurrence countType aggrCount aggrCountValue 2 timerWindow 1000

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria scope ipAddress

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 action type blacklist effectivePeriod 60

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 state enabled

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF state enabled

set addressContext default zone INTERNAL sipTrunkGroup RHEL_1 services enhancedDblProfile TEST_ENH_DBL_PROF

In a 200 OK response to an UPDATE message, the SBC is responding with refresher=uas when the UPDATE contained refresher=uac.

Platform/Feature: SBC 7000 Series: Call Control

 In a multiple dialog scenario, the SBC is sending a 183 Session Progress with an incorrect "To" tag when there is a re-transmission of a 18x for an earlier dialog. 

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: Call Control

SBX-65094 /
SBX-61870

The SBC is changing the position of the b-line in the SDP when it sends an INVITE message.

Platform/Feature: SBC 5000 / 7000 Series: Application

The SBC does not send an ACK message in response to a 487 response or a 481 response to an outstanding UPDATE message for a canceled dialog.

Platform/Feature: SBC Core: SIP

In a SIP-T inter-working scenario, the SBC does not send a 183 response with SDP (ACM) until it receives a 200 OK with SDP (ANM).

Platform/Feature: SBC Core: Application

When large number of Tone profiles are configured, SBC plays wrong tone during local ring back.

Platform/Feature: SBC 7000 Series: Application

The code has been modified to ensure that the SBC plays correct tone.

When SBC sends early progress message while handling unsupported MIME parameter in the ingress INVITE, the SBC does not honor methods as per allowed configuration at the ingress SIP TG.

Platform/Feature: SBC 7000 Series: Application

The CAC policer applied again for same call when re-attempt (crankback) happens on the same TG and ZONE and this results in call fail.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified not to apply CAC policer again when the same call is tried on the same trunk group and ZONE due to crankback.

The SBC does not response session refresh (Refresher=uas) from the endpoint after the switchover on the TCP connection. After switchover, since the user is de-registering and registering with the new port, the TCP connection cannot be retrieved using RegId.

Platform/Feature: SBC Core: Application

set global signaling sipSigControls multipleContactsPerAor disabled

The ScmProcess coredumps in the SBC due to deadlock.

Platform/Feature: SBC 7000 Series: SIP

Platform/Feature: SBC 5000/7000 Series: Platform

The Local Ring Back Tome (LRBT) cannot be configured when the flag makeInbandToneAvailable is disabled.

Platform/Feature: SBC 5000/7000 Series: SIP

The EMA Routes search does not return any results. The SQL query which was used to retrieve Route details had an extra left parenthesis resulting in an error while executing the query and hence causing this issue"

Platform/Feature: SBC Core: Platform

After receiving corrupted RTP packets, the PrsP process coredumped which triggered an unexpected switchover.

Platform/Feature: SBC 5000/7000 Series: Application

In the following command, the multi-line mode is enabled automatically, which allows user to import certificate contents without entering multi-line mode manually.

% request system security pki certificate <cert name> importCert certContent

Platform/Feature: SBC Core: Application

The 183 is not sent to the ingress if 183 with no SDP is received with P-Early-Media as inactive.

Platform/Feature: SBC 7000 Series: SIP

The SBC does not stop TCP level re-transmission even after TCP Retransmit Timer is expired.

Platform/Feature: SBC Core: Application

The code has been modified to add a new parameter tcpUserTimeout to the Sip Signaling Port and can be configured through CLI and EMA. This parameter describes the maximum number of seconds that transmitted data remains unacknowledged before TCP forcibly closes the corresponding connection.

set addressContext default zone defaultSigZone sipSigPort 1 tcpUserTimeout 0

Note: Enter a value of 0 (use system default) or value in the range 10-3600.

Note: For more information, refer to:

• Zone - SIP Sig Port - CLI
• Signaling Ports - SIP Sig Port
  

The SBC running on OpenStack with SRIOV network, does not have the ability to strip off or add on VLAN tags when the VLANS are added on the OpenStack network.

Platform/Feature: SBC SWe/SBC SWe Cloud: Platform

The support for this feature was introduced in the software. This change enables users to administer the VLAN support either on the SBC or on the SRIOV PF (cloud network) depending on the input given in the metadata for the Cloud deployments. For non-Cloud deployments, VLANs are supported only on the SBC and the SBC must not configure VLAN on the SRIOV PF.

Platform/Feature: SBC Core: SIP

The SBC sends a Contact header in the 200 OK response to a PRACK message when one was not received in the incoming 200 OK response.

Platform/Feature: SBC 7000 Series: Application

Platform/Feature: SBC 7000 Series: Call Control

The SamProcess coredumps when there is an inconsistent behavior from SIP Peers sending OPTIONS ping- where the initial Via header is without branch parameter and the second OPTIONS is with a branch parameter.

Platform/Feature: SBC Core: SIP

The MADDR parameter is present in NOTIFY’s Contact header. The SBC does not support MADDR in NOTIFY Contact header.
When SBC sends refresh SUBSCRIBE, the ReqURI was missing.

Platform/Feature: SBC 5400: SIP

The SBC’s maddr processing is enhanced to handle “maddr” parameter present in the NOTIFY Contact and use it as target refresh. The flag honorMaddrParam must be enabled.

Also, the code has been modified to put user part in the ReqURI of the refresh SUBSCRIBE requests sent from the SBC.

Platform/Feature: SBC Core: Application

The standalone software upgrade from 4.x/5.0.x to 6.2.0R000 (offline upgrade using platform manager) failed.

Platform/Feature:SBC Core: Platform

SBX-65675 /
SBX-65888

The new user, which is created with only key based authentication, cannot login.

Platform/Feature:SBC Core: Platform

The SBC is writing incorrect "To" tag information in CDRs in downstream forking scenarios. 

Platform/Feature: SBC 7000 Series: CDR

SBX-65805 /
SBX-65075

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC Core: SIP

SBX-65846 /
SBX-65617

Platform/Feature: SBC 5000 / 7000 Series: Application

When an egress peer sends an UPDATE message with the same SDP and o-line as a previous UPDATE, the SBC repeats the same Cseq value in the re-INVITE message it sends to the ingress peer.

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: Call Control

The SBC fails to properly handle the 200 OK response to an INVITE request if it receives it before completing the PRACK-200 OK message sequence in response to a previous 18x response.

Platform/Feature: Application

The EMA SMM rules are slow to load and may throw errors.

When an SMM rule is selected, EMA in addition to loading the rule details, also generates the CLI commands required for "View CLI" functionality which takes time. Thus, SMM rule was selected slowly.  Other errors are also due to the slowness issue only.

Platform/Feature: SBC SWe Cloud: Platform

The code has been modified to avoid the slowness by avoiding a call to generate the CLI command when SMM rule is selected. Instead, the CLI commands are generated when "View CLI" option is clicked in the UI. Changes are also made to show the name of the SMM rule which is selected by the user.

SBX-65931 /
SBX-64769

The SBC does not relay the preconditions in the Require or Supported headers of UPDATE messages if the SDP and o-line values are unchanged from a previous UPDATE.

Platform/Feature: SBC 7000 Series: Application

Java exceptions in SBXLoginModule - login () module

1. The UI call that checks if the user session is valid or not was failing due to some network issue. As a result, even though the session is valid, the idle timeout notification is shown to the user.
2. In the logs, the SBC was trying to invalidate a session even though the session was already invalidated. This was resulting an exception, which was preventing cleanup of further user sessions from the device.

Platform/Feature: SBC SWe: Platform

1. In the case where call to check the user session fails a different message "Something went wrong, please click OK to refresh the page" is shown to the user.
2. The code has been modified to clean up the user session to avoid the exception.

The following GWCM error messages are visible in the system logs.

Minor .GWCM: mcsEncodeCpcOpStr: Unknown paramtype type 333:

Platform/Feature: SBC 7000 Series: Application

The SBC inserted an empty ttc-charging-params header in the P-Charging Vector header in the ACK response to a 200 OK message from the egress side.

Platform/Feature: SBC Core: SIP

With end to end re-INVITE enabled and preconditions set to transparent, the SBC re-sent a Re-INVITE (late media) to the calling party unexpectedly.

Platform/Feature: SBC Core: Application

The code has been modified to properly reset the relay flag when end to end re-INVITE is enabled with preconditions specified.

Platform/Feature: SBC SBC 5000/7000 Series: Platform

echo "PS1='~$ '" >> /home/cnxipmadmin/.bashrc

 The SBC is converting an ISUP Suspend/Resume event to a SIP INFO message even when mapSuspendResumeEventInPSvcInfoHeader is disabled.

Platform/Feature: SBC SBC 5000/7000 Series: SIP

SBX-66088 /
SBX-64471

Platform/Feature: SBC Core: SIP

In a forking scenario, the SBC is sending out an incorrect Cseq value in a RAck header.

Platform/Feature: SBC 7000 Series: SIP

Platform/Feature: SBC 7000 Series: Call Control

Platform/Feature: SBC 7000 Series: Call Control

SBX-66097 /
SBX-64243

Platform/Feature: SBC 7000 Series: Call Control

SBX-66098 /

 In a downstream forking scenario, the SBC responds with a 491 "Request pending" message if it receives UPDATE requests from different dialogs simultaneously.

Platform/Feature: SBC 7000 Series: Call Control

SBX-66103 /
SBX-64098

In a forking scenario when the SBC is processing an UPDATE message and 18x response from different dialogs simultaneously, the 200 OK response to the UPDATE is not relayed properly to the ingress leg.

Platform/Feature: SBC 7000 Series: Application

When From header transparency is enabled and Include IP ports in From and To headers flag is enabled, the SBC does not transparently pass port number.

Platform/Feature: SBC 7000 Series

The default static route with the highest precedence even though port is down makes system unreachable.

Platform/Feature: SBC 5000/7000 Series: Platform

An SBC node fails when the Address Reachability Server (ARS) limit on static blacklist entries is exceeded.

Platform/Feature: SBC SWe Cloud: Application

The code has been modified to properly apply the record limit and to return an error to prevent a memory violation.

SBX-66290 /

Platform/Feature: SBC 7000 Series: Application

SBX-66302 /
SBX-63845

The Geographical Redundancy HA Mode is disabled after upgrade.

Platform/Feature: SBC 5000/7000 series: Redundancy

Platform/Feature: SBC 5000/7000 series: FM / Traps and Alarms

The SBC does not properly handle a re-INVITE request if the SDP in the request is unchanged.

Platform/Feature: SBC 7000 series: Application

The code has been modified to handle a re-INVITE request in which the SDP is unchanged. The SBC now sends a 100 Trying message for a session refresh INVITE and sends an ACK message to the 200 OK response for a session refresh INVITE.

In a precondition interworking scenario, the SBC does not send an INVITE request to the egress side when the ingress precondition is met in a PRACK message.

Product/Feature: SBC 7000 Series: Application

SBX-66718 /
SBX-66433

With SRTP enabled and DTLS-SRTP disabled in the call leg Packet Service Profile (PSP), if both SRTP (with a=crypto line) and DTLS-SRTP (with a=fingerprint line) are offered by the peer, the call leg falls back to RTP (security disabled) instead of SRTP being enabled.

Product/Feature: SBC 5000/7000 Series: Application

The code has been modified to properly enable the SRTP on the call leg under the same call conditions.

Product/Feature: SBC SWe: SIP

The SBC is not sending originating carrier information to the PSX when an NNI profile is configured.

Platform/Feature: SBC Core: SIP

The SBC code has been modified so that the SBC now sends originating carrier information to the PSX.

In a downstream forking scenario, media cut-through occurs even if the SBC receives an 18x response without SDP.

Platform/Feature: SBC 7000 series: SIP

The Scm process core dumps when SIP-SIPI call is made with DLRBT enabled, 183 and 180 with SDP and 180 with OBCI.

Product/Feature: SBC 5000/7000 Series: SIP

The code has been modified to add NULL check for pstMsgBody > pstIsupContent as pstMsgBody is changed after retrieved from the cache.

For SIP-I to SIP-I call, when converting ISUP CON from egress to ISUP ACM on ingress, if the CON contains a connected number parameter then the resulting ACM is not populated with all required parameters e.g. Carrier info type is missed.

If CON is received with a connected number parameter, the sent ACM sent may not contain all parameters.

Product/Feature: SBC Core: Call Control

Repeated logging of a system error is causing the disk to fill up, which ultimately causes the system to switchover.

Platform/Feature: SBC 5000/7000 Series: Application

The EMA Call Diagnostics feature does not show all the trunk groups that are available for a zone.

Product/Feature: SBC 5000/7000 Series: EMA

The request URI of REFER header is globalized.

Product/Feature: SBC 5000/7000 Series: Call Control

SBX-67350 /
SBX-67076

When loopback is enabled and standard_callmix_profile is applied with >12vCPU VM configuration, SWe_NP was crashed because of the invalid core_id returned from the rte_lcore_id() function. This leads to array out of bound access in the SWe_NP and thus results in crash.

Product/Feature: SBC SWe: Application

Upstream thread in SWe is a non-DPDK thread, thus, calling rte_lcore_id() on non-DPDK thread is not allowed.

In SWe_NP, as part of enhancement, this issue is introduced and now it is fixed by not calling rte_lcore_id() in upstream thread.

The MCT recorderType option is not supported in ERE.

Product/Feature: SBC 5000/7000 Series: Platform

Prior to this release, the default CLI user name and password for AWS SWe was admin/admin. The hard coded password must not be used for the security vulnerability on the AWS SWe platform.

Product/Feature: SBC SWe Cloud: Only AWS Platform

The code has been modified to support default CLI admin password as "active role assigned instance's primary interface-id (Mgt0InterfaceIDActive)". The active role of instance in the CloudFormation Template (CFT) must be assigned and the default CLI admin password can be found on the AWS stack output.

When 30,000 routes are created, sending invalid route creation or deletion queries to the SBC causes health check failure.

Product/Feature: SBC SWe: Application

Flood of logs for the parity error messages are seen in the kernel logs.

Product/Feature: SBC 7000 Series: Platform

The SBC is allowing extra calls in local mode, more than the configured licenses. The SBC must allow sessions equal to the number of configured licenses.

Product/Feature: SBC SWe Cloud: Platform

A note has been added to resolve this issue in the documentation:

"In local license mode without installing SBC-RTU license, the SBC instance process one call, if you install N number of SBC-RTU licenses SBC instance processes N+1 calls."

The DRBD/evlog may not synchronized if one of the servers of an HA pair is re-installed or replaced.

Product/Feature: SBC 5000/7000 Series: Platform

Alarms are not generated by S-SBC under overload condition and overload rejects happening.

Product/Feature: SBC SWe Cloud: Application

The following new alarms are generated to resolve this issue. These alarms are documented under the Distributed SBC (D-SBC) Alarms.

• sonusSbxDsbcNodeCongested
• sonusSbxDsbcNodeCongestedClear
• sonusSbxDsbcNodeCongestedV6
• sonusSbxDsbcNodeCongestedV6Clear

The timestamps on media packets may differ from that of the SIP signaling packets captured in the same PKT file, and may drift over time with respect to each other.

Product/Feature: SBC 5000/7000 Series: Platform

When an SBC is configured as an HA Pair and the Standby is stopped; if a new remote syslog Server is configured on the Active and Standby is brought back up and synchronized with the Active. The configured rsyslog.conf files on the Active and the Standby are mismatched.

Product/Feature: SBC Core: Application

Any instance which has only one SCM instance, the loopback register also lands on the same SCM instance and finds PstCall which is created on outgoing Initial register thus, loopback registration fails.

Platform/Feature: SBC 5000/7000 Series: Application

During call hold, the sequence number is incremented while the timestamp is not with respect to the real time. This may be treated as a packet loss by some end-points.

Product/Feature: SBC Core: DSP

The T.30 CED IND packets does not pass over the NP layer in a pass-through call.

Product/Feature: SBC SWe: Application

During an Audio call update to video, the SBC changes video port to zero when sending reINVITE toward the Egress Endpoint.

Once the invite is challenged, the media Information was not fetched accurately. Therefore, the video stream port was set to zero.

Platform/Feature: SBC 5000/7000 Series: SIP

Inter-working calls fail when the transport parameter is sent while contact transparency is enabled (PassCompletContact/HTP or Contact header in IPSP is enabled).

Platform/Feature: SBC Core: SIP

An insufficient configuration for the VM was used by the customer. Customer suggested if a corresponding error message can be populated in the LCA logs to identify such issues.

Platform/Feature: SBC SWe Cloud: Platform

The SBC includes SDP in subsequent 18x even though the Send SDP in Subsequent 18x flag is not set.

Platform/Feature: SBC Core: SIP

The GW-GW calls with transcoding cause a memory leak.

In addition, the GW-GW calls in which the audio parameters are changed after the initial call setup will also cause a leak.

Platform/Feature: SBC 5000 Series: SIP

Product/Feature: SBC SWe

For SBC SWe, the following alarms are generated when there is a CPU congestion. The calls may be rejected during congestion to maintain system stability.

• sonusSystemNodeResourceCongestionWarningNotification
• sonusSystemNodeResourceClearCongestionWarningNotification

After executing a backup restore config, the slwresd settings are not populated in the slwresd.conf file on the standby SBC.

Product/Feature: SBC 7000 Series: Application

After executing a backup restore config, the slwresd settings are not populated in the slwresd.conf file on the standby SBC.

Product/Feature: SBC 7000 Series: Application

Platform/Feature: SBC Core: Application

When logs are sent to the remote syslog server from a Cloud SBC, the incorrect system name is displayed in the server logs.

Platform/Feature: SBC SWe Cloud: Application

The SBC drops packets generated by EMA trace route tool.

Platform/Feature: SBC Core: Platform

The P-Access-Network-Info with parameter in IPv6 format is rejected.

Platform/Feature: SBC Core: SIP

When NAT direct group is deleted, ScmProcess coredumps in SBC.

Platform/Feature: SBC Core: Application

The period execution of the AIDE file validation process does not work.

Platform/Feature: SBC Core:Security

Setting DTMF to Either in the PSP causes pass-through call to transcode.

Platform/Feature: SBC Core: Application

The named-route was not updated when route was modified.

Product/Feature: SBC Core: Platform

The newly upgraded SBC experiences DSP coredump.

A fax relay channel configured for T.38 version 0 mode but received V34 packet (such as v8ansam pkt) instead, which caused DSP to crash and detected by MP for illegal memory access.

Product/Feature: SBC 5000/7000 Series: DSP

Not possible to search routes on EMA using destination national query. Code merge Issue, as there was a repetition of the code used for destination national query.

Platform/Feature: SBC Core: EMA

The SBC is including npdi parameter in the outgoing INVITE even though doNotIncludeNpdi flags is enabled. This occurs because of changes done for the flag alwaysIncludeNpdi.

Platform/Feature: SBC Core: SIP

The SBC drops packets generated by EMA trace route tool.

Platform/Feature: SBC Core: Platform

When ARP packets are discarded at ACL policer stage, offenders are added to the aclOffendersList instead of the arpOffendersList.

Platform/Feature: SBC 5000/7000 Series: Platform

Prior to entry of FIPS mode of operation, a software integrity check is performed to verify that software has not been altered. If this check fails, FIPS mode of operation must not be entered. An error path test showed that components that fail this test are logged. However, entry into FIPS mode of operation is still permitted.

Platform/Feature: SBC Core: Security

When the first SMM rule deletes a parameter in a header, and the second rule tries to modify a different parameter on the same header, the SBC coredumps after accessing the null pointers of the deleted parameter while performing the second rule.

Platform/Feature: SBC Core: SIP

Appropriate alarm must be raised when SRS IP selection fails as current alarm requires SRS IP to be printed.

Platform/Feature: SBC Core: Application

A new alarm sonusSbxSipRecSrsSelectionFailedNotification is generated to indicate the failure to initiate SIPREC recording due to any of the following reasons:

• Failure to select SIP Recording Server
• SRTP is enabled on the leg being recorded.

In EVS codec transparency using Audio transparency Feature, the SBC does not relay EVS codec, which is received in SDP offer from ingress.

Platform/Feature: SBC 7000 Series: Media

When Audio less is enabled, fmtp params are not sent transparently. The code has been modified to use the proper CodecIndex to fill fmtp params.

Note: The Audio Transparency flag must be enabled.

IP routes remain in routing table after LDG failure.

Platform/Feature: SBC Core: Platform

Platform/Feature: SBC Core: SIP

The SBC cannot delete microflow if hash ID is 0.

Platform/Feature: SBC 7000 Series: Application

When Honor Embedded Header in 3xx is enabled and the SBC received 3xx with embedded headers in contact, the SBC sends out Invite with malformed embedded header.

Platform/Feature: SBC Core: SIP

The SBC coredumpes in SIPS Module (SipsDnsProcessNaptrResponse function) as DNS server is configured with only ENUM records and there are no NAPTR records configured for a FQDN. The SBC expects NAPTR records (replacement field in NAPTR response) from DNS server but receives only ENUM records from DNS server, as replacement field is NULL.

Platform/Feature: SBC Core: SIP

The SBC duplicates Supported header in the outgoing INVITE when ingress INVITE has history info in supported header and History Info transparency is enabled.

Platform/Feature: SBC Core: SIP

The EMA GUI does not warn about the SBC restart when enabling first NTP server.

Platform/Feature: SBC Core: EMA

The SBC does not build the NOTIFY message body properly due to transparency profile.

Platform/Feature: SBC 5000/7000 Series: SIP Access

The issue was triggered by RTCP termination, it can disrupt calls randomly when RTCP generation is enabled.

Platform/Feature: SBC SWe/SWe Cloud

The SamProcess coredumps in the SBC as a result of a NULL pointer access.

Platform/Feature: SBC Core: Application

The ScmProcess coredumps in the SBC due to call park feature segmentation issue.

Platform/Feature: SBC Core: SIP

The configuration of fileSize or fileCount under eventLog typeAdmin, and starting a load configuration immediately may cause the SBC to crash.

Platform/Feature: SBC 7000 Series: Platform

When there are two or more instances of identical user ACL rules, the SBC may not load all the user ACL rules when it starts.

Platform/Feature: SBC 7000 Series: Platform IP/Media Services

The Blink Locator LED documentation was incorrect.

Platform/Feature: SBC 5000/7000 Series: Documentation

Modified the Locator LED Settings description to describe the following parameters:

• Blink LED on
• Blink LED off

Platform/Feature: SBC SWe Cloud: Platform

Memory leaks in the SBC when SIP recorder functionality is used.

Platform/Feature: SBC Core: SIP

The SBC coredumps when a SIP message that includes a P-Charging-Vector with generic parameters is received, while the SIP-GW-GW-SIP call with SIP Transparency is enabled.

Platform/Feature: SBC Core: Platform

Platform/Feature: SBC 5000/7000: SIP

In downstream forking with dialog transparency, the SBC stops relaying 18x/200 messages to the ingress call leg and once the call is disconnected ScmProces cores.

Product/Feature: SBC 7000 Series: SIP

When PRACK with SDP is received, the subsequent 18x/200 messages are dropped. The code has been modified to set the PrackPending properly has solved the issue.

Note: The Dialog Transparency, Downstream Forking, and Audio Transparency flags must be enabled.

Multiple SMM rules or actions on the message body causes memory leak in SBC.

Platform/Feature: SBC Core: SIP

Incorrect display for integer fields in the CLI commands post switchover.

Platform/Feature: SBC Core: Application

When the flag sendSdpIn200OkIf18xReliable is enabled in the 200 OK which is sent toward the ingress, video port is not updated even though SDP version is updated.

Product/Feature: SBC Core: Application

The personalitytype.txt file was moved to a different path, which caused fileNotFound exception.

Product/Feature: SBC Core: Platform

Inter-working calls failed when the transport parameter was sent while contact transparency is enabled (PassCompletContact/HTP or Contact header in IPSP is enabled).

Product/Feature: SBC Core: SIP

In call flow, SBC --> GW-GW --> GSX --> ISDN, when ingress side sends PSTN parameters to the SBC in SIP INVITE message, the SBC does not decode PSTN parameters correctly and send incorrect bearer capability to GW-GW which results in GSX sending wrong bearer capability to ISDN side.

Platform/Feature: SBC 5000/7000 Series: Application

The issue is seen when transparency for PCV is enabled and ttc params in PCV are received from the egress side.

Product/Feature: SBC Core: SIP

The ScmProcess coredumps in the SBC due to NULL pointer access for a certain HDR.

Product/Feature: SBC 7000 Series: Application

The SBC generates PRACK with contact header, which is against RFC 3262.

Product/Feature: SBC 7000 Series: SIP

The Policy Server is stuck in the "dryup" state when it is configured as "Out of Service" on the SBC when there are outstanding requests to that Policy Server.

Product/Feature: SBC 5000/7000 Series: Platform

When Online Certificate Status Protocol (OCSP) checking was enabled and then disabled for SIP-over-TLS, the OCSP check was still triggered even though the OCSP check is disabled. In addition, the OCSP check can cause health-check timeouts.

Product/Feature: SBC Core: Security

The ipPolicingBadEtherIpHdrOffendersIntStats contains a blank addressContext and interfaceGroup name fields.

Product/Feature: SBC 5000/7000 Series:Platform

The NP stores the addressContext and interfaceGroup as an “ID” (number) and not a string name. When the IPM converts the ID to a string name, confD may have created a new ID index for the addressContext or interfaceGroup. It is also possible the user deleted the addressContext or interfaceGroup. In this scenario, the IPM does not receive the values for the addressContext and interfaceGroup names and the IPM returns the values to the above variables instead of NULL as shown below:
“addr-%-4d” ->addr-1, addr-2, addr-3, etc

“ifGrp-%-4d” -> ifGrp-1, ifGrp-2, ifGrp-3, etc

The SBC discards DTLS SRTP packets due to SRTP authentication failure. When AES-CM-128-HMAC-SHA1-32 crypto suite is used, the SRTP authentication fails. This results in calls with one-way audio or without any audio.

Product/Feature: SBC 5000/7000 Series: Media, Security, TLS

The bulk SIP registration with invalid user-agent header generated huge redundant error logs which affected the SBC performance.

Product/Feature: SBC 5000/7000 Series: Application

During upgrade of standby server, availability of upgrade packages are checked on active server, which can sometimes return errors and cause upgrade failure.

Product/Feature: SBC Core: Application

Product/Feature: SBC 5000/7000 Series: SIP Applications

In some call flows with mid-call modifications to remote IP address, if server switchover occurs, one leg may no longer receive media packets. The problem is intermittent. Root cause is that loopback state is not properly mirrored from active to standby server.

Product/Feature: SBC 5000/7000 Series: Platform

When the recording is triggered through CLI, recording will be attempted. Thus, the CLI gives the following status:

"Attemping Siprec Recording, alarm shall be raised if recording trigger fails".

The ScmProcess repeatedly coredumps on the SBC 5000 series HA systems when advanced SMM stores greater than 1000 data into a variable.

Platform/Feature: SBC Core: Application

When e2e reINVITE and relay 4xx-5xx enables, the SBC does not relay 491 to the other side.

Platform/Feature: SBCCore: SIP

Add logic based on configurations to relay 491 to the other leg. 

In this case, the SBC must not regenerate INVITE.

The PrsProcess coredumps, NP memory dump indicates ANN core took an exception. The RTCP Gen can cause announcement coredump to generate an exception.

Platform/Feature: SBC Core: Application

In the SBC 5000 series, the IP loopback is implemented in the software and not in the hardware that exists in the SBC 5000/7000 series platforms. Thus, certain call transfer from loopback to non-loopback at the NP level was affected in the SBC 5400.

Platform/Feature: SBC 5000 Series: Platform

While importing the SBC configuration from 05.00.05 to 06.02.00, users are unable to login through EMA.

Platform/Feature: SBC 5000 Series: EMA

When contact header in IPSP is enabled, transport parameter must not be sent as interworking calls fail.

When passCompleteContact in IPSP is enabled, transport parameter is sent in the contact header, which does not cause an issue as Record-Route is added where transport parameter for that particular leg is updated appropriately.

Platform/Feature: SBC Core: SIP

• Avoid sending the transport parameter transparently, when contact header transparency in IPSP is enabled.
• Send the transport parameter transparently when passCompleteContact transparency in IPSP is enabled.

However, for register messages, though passCompleteContact is enabled, transport parameter cannot be sent.

An explanation is needed on the product page “SMM (Advanced) Examples” to identify any dialog stateful variable limitations.

Platform/Feature: SBC Core: Documentation

• The SBC supported a minimum radius shared secret length of 8. However, it was discovered that some customer systems used a length of 6.
• When radius authentication was enabled on the SBC, local authentication was only performed when the radius server was down. It was discovered that some customers wanted a selection of users through radius and some to work through local authentication.
• If the SBC fails to contact the radius server it can be configured with an out of service duration and it must not contact the server again during this time. However, due to some uninitialized memory it was possible that the SBC can contact the radius server one hour earlier due to daylight savings time calculations.

Platform/Feature: SBC 5000 Series: Platform

The code has been modified to:

• Allow a new minimum length of 6.
• Try and authenticate via the radius server first but it that fails it will try local authentication, this allows for some users not be configured on the radius server.
• Correctly initialize memory for the daylight savings time flag so the radius server is not contacted prior to the out of server duration expiring.

The SBC coredumps if 18x is received with multi bodies and 200 OK is received without body, when downstream forking and transparency in the other body is enabled.

Platform/Feature: SBC Core: SIP

Platform/Feature: SBC Core: Application

Added the following note to the documentation to resolve this issue.

During an upgrade to 6.2 release, if DNS Group misconfiguration (supported in CLI but not in application) is present, it can cause 6.2 upgrade/LSWU failure. Thus, the DNS Group must be cleaned up before upgrading to 6.2 release.

Platform/Feature: SBC 5000/7000 Series: SIP

On the SBC 6.1 release and older, the following misconfigurations can be present:

1. A dnsGroup is configured with an ipInterfaceGroup outside its own addressContext, the configuration was supported at the CLI but the application does not accept it, resulting in inconsistency between the CLI and application.
2. A dnsGroup with type mgmt can be configured without an ipIntefaceGroup being specified.

The SBC 6.2 release onward, such a configuration is not supported on the CLI and thus, when performing an upgrade to 6.2, it is recommended that the DNS groups must be cleaned up by following the WBA.

Note: The WBA must be followed to clean up the DNS group misconfigurations to avoid 6.2 upgrade/LSWU failures. 

The steps to accomplish this are included in WBA "W-17-00022847". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

The setHaConfig CLI command does not work properly to configure or revert GRHA setup.

Platform/Feature: SBC Core: Application

In downstream forking scenario where multiple 18x messages are received from the egress and when 200 OK for PRACK is sent, the contact header is corrupted in case of race conditions.

Platform/Feature: SBC 7000 Series: Application

The SBC was not able to edit the configuration in the Link monitor from EMA.

When conditions added, the JSON response was not formatted properly due to the new Display.

Platform/Feature: SBC SWe: EMA

The EMA GUI does not display any warning message while changing the port number of the SIP Signaling Port.

Platform/Feature: SBC Core: EMA

The code has been modified based on the xpath, operation and port number check to pop-up warning message. If operation is updateInstance, the xpath value is /addressContext/zone/sipSigPort and changing port number value is different from the existing value, the SBC displays the following warning message:

“SIP signaling port should be outside configured mediaPortRange if transportProtocol is UDP: Do you want to continue?”.

During SMM configuration, the PRACK is generated to drop 18x message. The SBC sends PRACK without unique branch param.

Platform/Feature: SBC Core: SIP

Due to misconfiguration in VMWare (vSpehere client), the E1000 (default value) adapter is selected while creating virtual machine. Due to the selection of the E1000 adapter type, after ISO installation the np.log file will fill with the following error event:

"SWe_NP[2640]: EAL: Error reading from file descriptor 17: Input/output error (np.log)."

Platform/Feature: SBC SWe: Application

The code has been modified to check the adapter type as VMXNET 3 in VMWare (vSpehere client). Currently, E1000 Adapter type is not supported by DPDK. Thus, SWe_NP gracefully exits by throwing the following error message in the np.log file:

"ERR: Found e1000 adapter type,Update adapter to VMXNET3. exiting now"

During the upgrade from BMC version 2.x to 3.x, under some rare conditions, because of timing issues next boot-up may cause core dump on host and restart. Under such conditions, application restarts itself.

Platform/Feature: SBC 5000/7000 Series: Application

This release contains the Linux 3.16.39 kernel, which included the changes to the TCP/IP stack which affected the reuse of the local port used in CDR transfer. This causes the CDR transfer attempted within 60 seconds of the last transfer to fail.

 Platform/Feature: SBC 5000/7000 Series: Application

The LI AVP data between external PSX (with version >= 10.2.0 / Diameter Version >= 31) and SBC will be encrypted for both Legacy LI and IMS LI flavors.

Platform/Feature: SBC 5000/7000 Series: SIP

Platform/Feature: SBC Core: Documentation

Added the following note to the State flag on the SIP CAC Profile pages in EMA and CLI guides:

NOTE: Setting a SIP CAC profile state to "Disabled" does not disable SIP CAC functionality on IP Peers to which the SIP CAC profile is assigned. To disable SIP CAC functionality on a specific IP Peer, disassociate the SIP CAC profile from the IP Peer.

When Transcode if Different DTMF PT flag is enabled, the NRMA sends Wide-band as well as usual 8 KHz DTMF if honorSDPclockrate is configured.

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to always add 8 KHz DTMF PT first (if not being used by any other codec) as configured in Preferred DTMF PT.

With this approach,

• It is certain that preferredRtpPayloadTypeForDtmfRelay configuration apply to 8k, and for 16K; next available PT (most likely +1) will be used.
• No impact on customers using this flag with 8K codecs.
• The customers using 16K, can plan their configuration to get desired behavior (likely -1).

The SBC does not indicate the GSX to add the charge Area Information on the egress side. The Cai=xxxxx present in the PCV header did not egressed to the GSX.

Platform/Feature: SBC Core: Application

The SIPREC forking fails when SRS servers send 200 OK without SDP and Re-INVITE with SDP is received after the switchover.

Platform/Feature: SBC 5000/7000 Series: Media

When the SBC receives reINVITE, it adds the wrong crypto from route PSP (configuration of cryptoSuiteProfile), which is not negotiated during the call establishment to the reINVITE.

Platform/Feature: SBC 5000 Series: SIP, SIP Access

SBX-64594 /

The multiple INVITEs with replaces fail in the SBC. When the second INVITE with replaces is received, the SBC selects the wrong leg for bridging. Thus, the SBC rejects the second bridging.

Platform/Feature: SBC Core: Application

During call transfer, when the SBC receives NOTIFY with dialog-info containing only the call-ID and does not contain toTag and fromTag, the ScmProcess coredumps while relaying NOTIFY to the other leg.

Platform/Feature: SBC 5000/7000 Series: SIP

The SBC was not populating retryafter header in the 503 response that it sends to reject a call during congestion.

Platform/Feature: SBC 5000/7000 Series: SIP

Platform/Feature: SBC SWe: Application

 The following note has been added to resolve this issue:

"After the database is cleared, the active profile is retained."

From 6.2.0 release onward, the SBC determines the SRS reachability only through the SIP ARS status.

Platform/Feature: SBC SWe: Application

The following note has been added to resolve this issue:

"From 6.2.0 release onward, the SBC determines the SRS reachability only through the SIP ARS status. The pathCheckProfile must be configured to determine the reachability of the SRS peers and treat failure response like 501 as OPTIONS failure."

The SBC reINVITE uses disrupted route header when InsertPeerAddressToRouteHeader, and call required authentication is enabled.

Platform/Feature: SBC Core: Application

During an LSWU, when TLS calls are active and standby system is upgraded, the TLS session information is synchronized to Standby. The SamProcess core dumps on standby if the TLS session data length of any session being synched is more than 2048 bytes.

Platform/Feature: SBC 5000/7000 Series: Application

Standby instance is not running the 10 minute timer.

Platform/Feature: SBC Core: Application

Modification from G722 to G711 is not successful and DSP starts sending 40msec packets.

Platform/Feature: SBC Core: Media

The NAPT learning of media IP address and port does not work on Comfort Noise RTP packets received when using G711 with Silence Suppression.

Platform/Feature: SBC Core: Media

Platform/Feature: SBC 5000/7000 Series: Application

Impact: This issue is seen only with TFT flag is enabled.

Workaround: Disable TFT flag.

The Test SIP Adaptor Profile is not working in the EMA GUI.

Impact: This is a SIP Adaptor test utility that will test the SMM rules applied without making call. Based on the analysis, the issue is present in 6.2.0R000 build as well.  This issue is related to the utility and no impact on the SBC behavior. 

Workaround: Create the SMM rules and test the rules by making a call. 

Observing split brain after rebooting active and standby Instance at once.

Platform/Feature: SBC SWe Cloud: Platform

Impact: When the active are standby instances are rebooted together, they try to come up at the same time and enters into split brain (both the nodes are in ACTIVE).  The scenario is a very rare occurrence as there is less possibility of both the nodes going down simultaneously. 

Workaround: Restart the node that has been configured as STANDBY.

In SBC SWe, the transcoded loopback call fails after a switchover and revert.

Platform/Feature: SBC SWe: Platform

Impact: For transcoded calls with loopback scenarios when a double failover happens, the voice path is lost.

Workaround: Place the end points on hold and retrieve them.

RTCP Call: There are no alarms or calls tear down even when there are packet loss more than the threshold limit.

Platform/Feature: SBC Core: Application

Impact: There are no alarms or calls tear down even when there are packet loss more than the threshold limit.

Workaround: Enable inactivity for the packet loss to be reported.

SBX-42896

The SBC does not include the unknown CODEC in the SDP towards the SIP Rec even when the audio transparency is enabled.

Platform/Feature: SBC Core: SIP

Impact: Lawful Intercept, SIP REC, NICE recording may not work with unknown codec for this feature.

Workaround: If the codec is pre-determined, SMM rule can be applied to send that codec instead of G711.

The CDR pattern mismatches in fields 152 and 153 (ingress and egress Maximum Packet Outage) for pass-through and transcoded calls.

Platform/Feature: SBC SWe: CDR

Impact: CDR for transcoded calls show excessive packet outage value that does not match actual packet gap.

Workaround: The excessive value of outage occurs because of UXPAD process jitter at the beginning of the call (approx. 10 packets). The jitter settles down later during the call and does not impact voice quality.

DSP device memory dump contains Bit errors.

Platform/Feature: SBC Cor: Media

Impact: The DSP device memory dump collected is unfit for debugging as it contains bit-errors. This is the secondary coredump mechanism which kicks-in when single DSP core-dump fails.

Workaround: None

Incorrect egress codec is written to CDR at egress gateway while executing 12 codec feature over GW-GW.

Platform/Feature: SBC Core: Application

Impact: The call is successful; however, the codec information reported in the CDR is incorrect.

Workaround: None.

The SBC rejects INVITE with 414 URI too long when PCSCF + IBCF > IPX.

Platform/Feature: SBC Core: Application

Impact: This issue seen when there is double encryption by SBC.

Workaround: None

The standby instance may require second reboot to recover after the HA links are restored from the split-brain scenario.

Platform/Feature: SBC SWe Cloud: Platform

Impact: Longer redundancy protection time, but no impact on call processing.

Workaround: Requires manual reboot of standby SBC

The SBC does not send RTCP packets after a switchover when the signaling and media NAT are enabled both on the ingress and egress Trunk Groups.

Platform/Feature: SBC SWe: Media

Impact: For call flows with RTCP termination configured, and both RTP and RTCP NAPT configured, SBC may stop generating RTCP Sender report after switchover.

Workaround: None

On an SBC HA infrastructure, there are active video calls. After switchover, the active calls are switched to the newly active SBC. The quality of the existing video calls will be degraded in the newly active box.

Platform/Feature: SBC 7000 Series: SIP

Imapct: There are no known call failures. There are no issues for the new video calls attempted after the switchover.

Workaround: None

The partial config activation through Configurator fails due to Packet Service Profile config.

Platform/Feature: SBC SWe Cloud: EMA

Impact: The partial configuration update feature for the SBC SWe Cloud does not work for ERE that is, the ERE provisioning objects cannot be updated (for example, Packet Service Profile, IP Signaling Profile, and so on) using this feature.

Workaround: None

During load, the switchover can take a couple of minutes to stabilize with sporadic call acceptance, till both the boxes stabilize once the sync is completed.

Platform/Feature: SBC SWe Cloud: Application

Impact: Sporadic call acceptance once the sync or the call audit is completed.

Workaround: None

The GRHA ARP bond switch from ETH0 to ETH1 causes system restart.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: If something happens to the active slave device (eth0 or eth1), the bond device will properly switch to the backup but TIPC might notice the outage.  If TIPC notices the outage, there will be a momentary split brain causing one of the boxes to restart. The configured leadership algorithm (standard or enhanced) will determine which node remains active and which restarts to become standby upon recovery from the split brain.

Workaround: None

If T.38 protocol version 3 is enabled in the Packet Service Profile and peering endpoints are sending V.34 fax, fax may fail to negotiate or fails during page transfer.

Platform/Feature: SBC SWe: Application

Workaround:The T.38 protocol version 3 must not be enabled in the Packet Service Profile. The V.34 faxes will be negotiated as T.38 version 0 protocol and pass successfully.

Issue with the content sharing between H323 to H323 endpoints with H235 media encryption.

Platform/Feature: SBC SWe: Application

Impact: The H323 endpoint receiving H.235 encrypted content sharing will not see the shared video.

Workaround: Turn off H235 encryption.

The sftpadmin path has changed.

Platform/Feature: SBC Core: Application

Impact: The CDR collection by NetScore does not work.

Workaround: Configure NetScore to use /var/log/sonus/sbx/evlog path instead of /var/log/sonus/evlog/evlog path for CDR collection.

The SIPREC is not initiated after REFER if the recordingType is set as ingressLeg.

Platform/Feature: SBC Core: SIP

Impact: The SIPREC recording for recordingType ingressLeg does not work after a REFER.

Workaround: For SIPREC to work after REFER, set recordingType as egressLeg.

The SBC application restart may be observed if timezone change (for example, set system ntp timeZone mySBCSystem zone utc) is combined with any other commands in a single configuration commit.

Platform/Feature: SBC 5000/7000 Series: Platform

Impact: The SBC restarts.

Workaround: The ‘commit’ time zone changes independently as a single command. For example,

config

set system ntp timeZone mySBCSystem zone utc

commit

If the above workaround is not followed, the SBC application may restart and can continue normal operations once application is up.  If the configuration load was partial because of restart, reload the configuration.