SBC Core 07.02.02R000 Release Notes

V05.01.00F007

V07.01.00F003

V07.02.00R000

V07.02.01F001

V07.02.01F002

V06.01.00R009 

V05.01.02F008

The D-SBC DFE module, which controls connections to the MSBC/TSBC, continues to read memory after being freed.

This issue was found from ASAN testing in the lab.

Root Cause: This issue was due to not stopping a timer correctly after a link to MSBC/TSBC went down whereby the timer later expired it causing the timer handler to read the freed memory. Although the memory was being read, it was first being used to check that the memory block was associated with the timer by looking at the timerID field in the memory block. If the block did not match then nothing more was read. If the block did match, then the code should have stopped doing any further processing as all the associated calls would have already been cleared up. This issue is only seen for an edge case scenario where the timerID part of memory is not updated, but other fields are updated.

Impact: The D-SBC DFE module continues to read memory after being freed.

Steps to Replicate: Run the NWDL SVT automation suite on ASAN images.

Platform/Feature: SBC

The SCM Process cores when making a REFER call where more than two SCMs are present in an I-SBC configuration. When the scenario occurs, the SBC does not recognize the N:1 Slot and will not pick the changes.

Impact: SCM Process cores 

Root Cause: When N:1 changes came, Refer code is not modified to pick the changes of N:1 slot ID.

Steps to Replicate: Execute a Refer call and ensure that call lands on SCM greater than 2 (because coredump will not occur if call lands on SCM0 or SCM1).

Platform/Feature: SBC

The SCM may core due to memory corruption caused by processing Global PCDR Info received from the Policy Server.

Impact: Repeated SCM cores.

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

During the write process to create a new policy status reporting file, the correct read privileges were not present to allow the successful completion of the status reporting session.

Impact: The status reporting process wrongly reports a sync in progress.

Root Cause: /home/oraadmin/SSDB/PolicyDBSyncStatus is getting removed by logrotate. When the new file was created by write process, it did not have the correct privs to be read by status reporting session, so the status reporting process wrongly reported sync in progress.

Steps to Replicate: N/A

Platform/Feature: SBC: Application

Portfix SBX-86468: When the "Registration Expires in Expire Header" flag is enabled in the surrogate registration on Ingress TG IPSP, the de-registration is sent before the registration can refresh, which results in a call failure. (Originated in release 6.2.3F2)

Impact: The SBC is not picking the correct expiration value resulting in a long refresh timer (more than expired value); de-registration is sent before the registration refresh.

Root Cause: The SBC is not picking the correct expiration value that results in along refresh timer (more than the expire value), and de-registration is sent before registration refresh.

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC added a REFER method in the Allow header when the condIncMethInAllowHdr was enabled, though REFER is set to Reject in TG methods instead of Allow Only.

Impact: N/A

Root Cause: N/A

Steps to Replicate:

1. Run a SIP->SIP call with default settings. REFER was included in the Allow header in the outbound INVITE.
2. Set the refer to "reject" under the egress trunk group->signaling -> methods -> refer. Now in the Allow header of the outbound INVITE, REFER was not included. This works as expected.
3. Set flag condIncMethInAllowHdr under the egress trunk group->signaling to "enabled". Now in the Allow header of the outbound INVITE, REFER was included. This shows that this flag changed the behavior.

Platform/Feature: SBC

PortFix SBX 72693: FPGA failures are observed on DSP cards. (Originated in release 8.0.0)

Impact: Communication lost between the CPU on the SBC and FPGA on the DSP card.

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: DSP

SBC adds "Max-Forwards: 71" header into SIP responses in violation of RFC3261 section 20

Impact: After receiving the error message with Max-Forwards header, End User may report for Invalid message as it deviate from RFC3261 response message header inclusion.

Root Cause: When the SBC does not find the route information when adding the Max-Forwards header for an incoming call, the SBC rejects the call.

Steps to Replicate: N/A

Platform/Feature: SBC

When the PCRF is enabled, a SCM may core on switchover.

Impact: N/A

Root Cause: The function SipSgReconstructParentRcb() allocates a structure (pcrfInfo), but leaves it empty if sbyRdbPtr->diamRxHandle is 0. One of the fields in this structure is a list pcrfGCIDList, and this list is left uninitialized if sbyRdbPtr->diamRxHandle is 0. Later, SipSgIncomingCallNfy() attempts to insert something in this uninitialized list causing a core.

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC reads the end of a memory block while processing DTLS signaling.This issue was found while running ASAN regression in the SVT lab.

Impact: This can result in invalid accessing of memory. This can potentially lead to coredumps if the memory block is at the end of the process memory as it will then try to access invalid memory.

Root Cause: The code was processing the fingerPrint information associated with DTLS calls and was reading of the end of the memory block because it was not correctly null terminated.

Steps to Replicate: Execute the SVT STIR/SHAKEN-related test suite to reproduce this issue.

Platform/Feature: SBC

The SBC CDR 'GMT' timestamps are skipping forward and backward in some call scenarios.

Impact: This issues causes incorrect call start/stop/duration timestamps in the CDRs.

Root Cause: N/A

Steps to Replicate:

1. Execute command: set system ntp timeZone pjk zone gmtPlus02-Athens
2. Execute: sbxstop
3. Set time on the NTP server to before the daylight saving time: date -s "2018-03-25 UTC 00:40:00".
4. Execute: sbxstart, and make sure the SBC gets in sync with the NTP server.
5. Start some call load to monitor the timestamps in the CDRs.
6. Wait until 7:00 local time to see both CDR timestamp jump.

Platform/Feature: SBC: CDR

CRLF in 7K mime causes fGenband SST to send extra hex data at bottom of ACM

A TDM customer places a call that is routed via CS2k/C20 Genband switch through a Sonus SBC.

Impact: If the call hits an SBC 7000, the SIP-T ACM passed back to the CS2K/SST has a length indicator in the SDP that is not present when the call hits a SBC 9000.

Root Cause: Extra CR, LF (0x0d, 0x0a) characters are added at the end of an ISUP MIME body immediately before the correct CR, LF is associated with the boundary line.

Steps to Replicate: N/A

Platform/Feature: SBC: SIP

"Call/Registration Data" stays in syncInProgress after the B node performs a LSWU.

Impact: The Active SBC may fail to synchronize ("Call/Registration Data" remains in syncInProgress) after an LSWU upgrade of the Standby SBC when using an IpPeer pathCheck profile.

Root Cause: N/A

Steps to Replicate: Test setup: LSWU from v5.1.2R0 to v5.1.2R2

1. Create a pathCheck profile
2. Create 100+ ipPeers with IPv4 ipAddress and ipPort
   1. Make sure the ipAddress / ipPort does NOT respond to the OPTIONS ping
3. Assign pathCheck profile to the 100+ ipPeers
4. State enable the 100+ ipPeers pathCheck profile
5. Verify that the 100+ ipPeers have been blacklisted.
6. Assign the 100+ ipPeers pathCheck profile hostName and hostPort
7. Start LSWU of the Standby CE to v5.1.2R2
8. Wait for LSWU of Standby CE to complete.
9. Verify that the Synchronization Status for 'Call/Registration Data' remains in 'SyncInProgress' forever.
10. Verify the following error message exists in the SYS log:
    "MAJOR .RTM: .RTM .PsObjectFactoryManager: Failed to find object's prototype while operating on object ID 154415 (0x25b2f)"

Platform/Feature: SBC: Application

The DNS NAPTR transport is not used during surrogate Authentication REGISTRATION attempt. The Transport is not correctly set while the SBC is sending an Authorization request.

Impact: The subsequent Registration attempt fails as the SBC is changing the TCP port from a normal TCP port 47xxx to 5060 after it got challenged.

Root Cause: The SBC sends no NAPTR only SRV followed by A query and Surrogate registration successful.

Steps to Replicate:

1. Set FQDN port to "0".
2. Set Transport type in IPSP to "none"
3. Enable noPortNumber5060 flag in IPSP.

Platform/Feature: SBC

The code is modified to set a correct transport type while sending an Authorization request.

Portfix SBX-86748: The fragment timeout logic is decrementing the wrong interface's current in-use count. This problem only impacts hardware SBCs. (Originated in release 7.2.1)

Impact: If the PSX responses are large and the IP packets are fragmented, the SBC may retry multiple times due to reassembly failures resulting in packet drops.

Root Cause: The SBC's ability to handle defragmented packets will deteriorate. The NO DEFRAG MATCH count in "show table system networkProcessorStatistics defragStatistics" increments rapidly.

Steps to Replicate: N/A

Platform/Feature: SBC 5xx0, 7000

The CDR connection timeouts greater than 127 seconds are not honored, as the TCP sessions times out after 127 seconds.

Impact: N/A

Root Cause: The TCP session times out in 127 seconds.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-87448: In the AWS SBC, SSH keys stored in CONFD database are lost during the upgrade to 07.xx.xx. (Originated in release 7.2.0)

Impact:  Any SSH key stored in the CONFD database is lost during the upgrade.

Root Cause: In AWS deployment where the volume replacement-based upgrades are used, the standby undergoing upgrade is not requesting CONFD.conf keys from older active SBCs.

Steps to Replicate:

1. Perform LSWU from 7.0S407 to 7.2S400
2. Call load of 700 sessions @7cps is running
3. Trigger a switchover

Observation:

1. Calls are running fine.
2. Switchover is successful but observing errors in DBG file.

Platform/Feature: SBC

SBC is not processing the 200 OK.

Impact: N/A

Root Cause: Blind transfer call fails due to DLRBT. The internal tone flag on leg B was not reset properly, as a result of leg C failing to the cancel tone.

Steps to Replicate: N/A

Platform/Feature: SBC

When the End to End PRACK is enabled and if call fails after sending 18x to Ingress before receiving PRACK or if any PRACK drops happens; there may be a memory leak.

Impact: N/A

Root Cause: When End to End PRACK is enabled, just after receiving 18x; memory will be allocated for storing reliable data. And this will be cleared when PRACK is sent out. But If there is PRACK drop (It happened as Call is simulated with SIPP scripts and it is closed abruptly) there is chance of memory leak.

Steps to Replicate: Run Call with reliable 18x messages and Enable End-To-End PRACK flag in IPSP. Close scripts just after sending 18x out or don't send PRACK from INGRESS.

Platform/Feature: SBC: SIP

IPTABLES rules are incorrect on the SBC SWe after an upgrade where non-default addresses are configured for HA ports.

Impact: This may prevent the HA peers from communicating when one of the configured HA IP addresses is the same as the default address, but the other peer is not.

Root Cause: IPTABLES rules are incorrect on the SBC SWe after an upgrade in the case where non-default addresses were configured for HA ports.

Steps to Replicate: N/A

Platform/Feature: SBC SWe

Portfix SBX-87404: When the SBC compare SDP online only and the peer answers with a 200 OK with SDP (where sessId and sessVer are zero), the SBC incorrectly sends a reInvite out before sending the acknowledgement. (Originated in release 6.2.4)

Impact: This issue may trigger an unnecessary reInvite.

Root Cause: SIPS fails to save the peer SDP when online validation only and both online and offline validation sessId and verId are zero in 200 OK.

Steps to Replicate:

Platform/Feature: SBC

Portfix SBX-87615: After the announcement script is completed, the CC validates this as a multiparty call and transfer script and notifies ingress to connect the call.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-86930: e2e prack is not working if require header is present and no 100rel. (Originated in release 6.2.4)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-86099: Minimize the logic suppressing the Update. (Originated in release 6.2.4)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When multiple DM Nat tables are configured, calls which should have been sent to Direct Media are being media anchored through the SBC.

Impact: N/A

Root Cause: DM Nat table entries are not getting properly created and entries are getting added to wrong tables - this is leading to Direct Media not working for entries configured in DM NAT table.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-86068: reInvite after an authentication call is missing logic to copy the SMM scope variable data into a new message. (Originated in release 6.2.4)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

In case a call to sonusPeerUpload.expect is made and if the peer goes down then, there may be a waittime for the SCP connection, resulting in the application healthcheck timing out after 10 seconds, which causes the application to crash.

Impact: N/A

Root Cause: The scp operation may get stalled if standby goes down while scp was in progress resulting in health check timeout in application in turn causing a crash suspecting deadlock.

Steps to Replicate: N/A

Platform/Feature: SBC

Because of the Anonymize flag, the host name will get updated with Egress SIP Sig port in an outgoing PAI header. When the Source host name size (SIP Sig IP) is bigger than destination, the host name size (an existing host name in PAI received on INGRESS) issue will appear.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Porfix SBX-86236: The SWe TPAD channel modify code had a bug that had a response sent to a different entity on the host (SWEA instead of DDH) and that resulted in DDH major log event. (Originated in release 8.0.0)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: DSP

Shadow file copy is available to admin user after an upgrade.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC ignored the ACK and failed to relay it to the INGRESS peer. As a result, after 10 seconds, the OA-FSM timer expired on the egress call leg and the call was torn down. 

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The Scm Process may core dump while trying to double free the memory associated with the username of registration of the AOR.

Impact: N/A

Root Cause: The previous register AOR block was freed, however the username field was not set to NULL and subsequent re-registration or refresh comes in and reuses the heap memory that was freed for the previous registration. When we try to free our current registration block, double free is detected and hence we core.

Steps to Replicate: The problem is not reproducible.

Platform/Feature: SBC

Possible memory leak when the parameter rewriteIdentities is enabled on a SIP trunk group.

Impact: N/A

Root Cause: If a SIP trunk group has the feature "rewriteIdentities" enabled, there is an edge case in which memory which was allocated for temporary storage of a toHeader is never freed.  

Steps to Replicate: N/A

Platform/Feature: SBC

When a E2E PRACK is disabled and PRACK is received from the caller with preconditions, the SBC does not relay the precondition changes to the callee.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

NAPT learning is broken if the following events occur:

RTP and RTCP NAPT learning are enabled when call comes up 
No packets are received within 1.5 seconds 
RTCP packet is received 
RTP packet is received 

In this scenario, the source IP address and RTCP port learn from the received RTCP packet, but any subsequent RTP packets (from same source IP address) are not learned. So, the RTP port is never learned.

Impact: N/A

Root Cause:

This problem occurs because we checked in some NP code changes that basically added NATL support to learn source IP address from RTCP packet (which we never supported before), but we didn’t check in the necessary XRM changes to support this feature. Our thinking at the time was that the NP changes were backward-compatible with the existing XRM code, and thus the new NP RTCP NATL learning functionality would not be executed; the NP would continue to operate as before (RTCP packets received before NATL learning from RTP packet had occurred would be discarded).

In 8.0 we implemented the XRM/application changes that, coupled with the previously checked in NP changes, fully support RTCP NATL learning.

Steps to Replicate: N/A

Platform/Feature: SBC

When an Audio transcode is possible and below the line index is zero, all non-core streams are being removed even when multipleAudioStreamsSupport is enabled.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: Media Resource Management

The SBC was reading the end of a memory block while trying to play an announcement, due to pre-conditions interworking happening on the ingress call leg.

Impact: N/A

Root Cause:

The code was passed in a memory block which contained the name of an announcement and was copying the name into a fixed size memory buffer. The code was always copying a fixed amount of memory. However the name of the announcement was less than the fixed amount being copied so the code was reading more than the allocated space.

If the memory block passed in was right at the edge of process memory then its possible this might cause a memory exception and coredump.

Steps to Replicate: This was found while running SVT pre-conditions test suite.

Platform/Feature: SBC

Portfix SBX-85335: The SBC replaces custom EMA SSL certificate with a self-signed certificate during an upgrade. (Originated in release 8.1.0).

Impact: N/A

Root Cause: User installed certificates were not being restored after upgrade and were getting replaced by default EMA certificates. Also, SSLVerifyClient was not being restored to its configured value after upgrade.

Steps to Replicate:

To verify restoration of SSLVerifyClient:
1. Setup and verify mutual authentication for EMA
2. Verify value of SSLVerifyClient ("required" when clientAuthMethod set to pkiCertOnly; "optional" when clientAuthMethod set to usernamePassworkOrPkiCert)
3. Perform upgrade and verify that the value of SSLVerifyClient remains the same as configured

Platform/Feature: SBC: EMA

A second REFER comes in too fast when the previous referer has not completed the teardown. It sets the teardown in an invalid state.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The logical implementation for the flag CondIncMethInAllow is incorrect. 

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Standby logs (/var/log/messages and syslog and user.log) are flooded with CpsShmAttach event log messages.

Impact: N/A

Root Cause:

CpsShmAttach() is being incorrectly being call by the standby for every SIP Registration.
The only negative consequence of this is that a log message with the following text is logged for every registration:
"CpsShmAttach: Attached to shared memory"

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-72165: The mandatory users (admin, guest, operator) in the SNMP users table are user removable. If removed, the SNMP commands may fail. (Originated in release 6.2.4).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: CLI, EMA

Portfix SBX-88548: For a non-SIP to SIP call, the transparency/relay flags are still in effect. (Originated in release 6.2.4)

Impact: N/A

Root Cause: Resolved: Change the logic to disable/ignore all transparancy/relay flags if it is not end to end SIP call.

Steps to Replicate: N/A

Platform/Feature: SBC: SIP Applications

If a user enables/disables the audit system (auditd + kernel's audit system), the existing CLI command "set oam eventLog platformAuditLogs state <enabled/disabled>" will be used.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The code is modified to:

• change the default state of the platformAuditLogs to enabled Stop audit system (auditd + Kernel audit system) for stopping auditd,
• disable the audit system when platformAuditLogs's state is disabled and persists on restart.

Software editions of the SBC use uninitialized values during the SmProcess startup.

Impact: N/A

Root Cause: Coding error.

Steps to Replicate: Use valgrind on SmProcess at startup to find use of uninitialised values.

Platform/Feature: SBC

The SBC is not able to send 200OK to the Ingress due to tone playing and a "Send Update SDP in 200OK" flag.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

e2e PRACK is not working if the required header is present and 100rel is not.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-88882: A 200 OK INVITE received immediately after a UPDATE/200 OK gets stuck and the call fails. (Originated in release 7.2.1)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-88220: SBC system configuration: sysctl variables, hardening. (Originated in release 8.1.0)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

NAPT not learning due to a delay in media being received. NAPT is learning for 1sec for a re-INVITE and after the learning, the previously learned address is returned to NRMA (which does not work for end changes).

Impact: N/A

Root Cause: NAPT not being learnt due to delay in media being received. NAPT is learnt for 1sec only for a re-INVITE and after that the previously learned address is returned to NRMA ( which doesn't work in this case as far end changes it's IP:PORT ).

Steps to Replicate: For re-INVITE send media after 1/2 seconds and see that napt learning is restarted after timer expiry.

Platform/Feature: SBC

Portfix SBX-89202: When ISUP/QSIG message body is present in the OOD requests, the SCM coredump occurs since the hSipCallHandle will not be present. (Originated in release 8.1.0)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-88221: High auditd activity is causing disk issues and registration failures on the SWe. (Originated in release 6.2.4)

Impact: N/A

Root Cause: High activity of auditd was mainly caused due to flooding of MAC_IPSEC_EVENT messages in /var/log/audit/audit.log

Steps to Replicate:

1. run ipsec.sh script
2. Simultaneously, on another session, try "mpstat -P ALL 1", verify that high values of %iowait are not found
3. If high activity of auditd is still causing issues, auditing can be stopped using "set oam eventLog platformAuditLogs state disabled"
4. After disabling auditd, verify that auditd has been disabled, using "auditctl -s" and "systemctl status auditd"
5. Also verify that audit messages are not being logged in /var/log/audit/audit.log and /var/log/messages

Platform/Feature: SBC

R-URI userpart is incorrect when the ToHeader Transparency is on and with registration. 

Impact: N/A

Root Cause: Logical error.

Steps to Replicate: N/A

Platform/Feature: SBC

Application can fail to start if the name chosen for the SBC ends with "net". 

Impact: N/A

Root Cause:

In implicit registration case, SBC fails to unsubscribes with PCRF during De-Registration and that results in PCRF keep on sending notifications to SBC
even after De-registration and that result in coredump(Because SBC tried to access Registration Control Block which is given by callback function which does not exist)

Steps to Replicate: N/A

Platform/Feature: SBC

The SCM Process cores when receiving notifications from the PCRF, which does not exist on the Registration Control Block.

Impact: N/A

Root Cause:

In implicit registration case, SBC fails to unsubscribes with PCRF during De-Registration and that results in PCRF keep on sending notifications to SBC
even after De-registration and that result in coredump(Because SBC tried to access Registration Control Block which is given by callback function which does not exist)

Steps to Replicate:

1. Enable Rx feature and signallingPath flag on access TG
2. Run implicit Registration
3. Send De-Register request

Platform/Feature: SBC

Portfix SBX-74470: SIP (LM) -> GW call (x-fer on this side) - call is torn down. (Originated in release 6.2.4)

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: Gw-Gw, Media Resource Management

Portfix SBX-89981: Contact Transparency issue(HTP) for a Late Media Invite is not working as expected when excluded methods are configured. (Originated in release 8.1.0)

Impact: N/A

Root Cause:

When Excluded methods is configured and Late Media INVITE is received, we are checking the transparancy bits for Contact before
actually calling the CopyTransparancyContent where transparancy bits are actually set.

Steps to Replicate: Enable Contact transparency with HTP and exclude methods as below and execute call flow as mentioned in description.

Platform/Feature: SBC

Portfix SBX-87984: RCA: web server leaks a private IP address through its HTTP headers. The web server will expose internal IP addresses that are usually hidden or masked behind a Network Address Translation (NAT) Firewall or proxy server. (Originated in release 8.0.0). 

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: EMA, Security

A change in the return code for Platform REST API calls for passwords mismatch.

Impact: N/A

Root Cause: In case of password mismatch, Platform REST API was returning status code 200 with error message. Which is not correct for authentication.

Steps to Replicate: Login into platform manager with wrong password, response should come with 401 status code and error message.

Platform/Feature: SBC

SIPSG_GET_DMINFO_RPY_MSG is not sent when the DM Info is not sent. The SCM lookup times out after 1 second and the 200 OK is released after 1 second.

Impact: N/A

Root Cause: It is the day one behavior of Direct Media Anti-trombone feature.

Steps to Replicate: N/A

Platform/Feature: SBC

When the Enhanced Dynamic black list feature is configured for a Receipt of message event type, the ScmProcess leaks memory.

Impact: N/A

Root Cause: When Enhanced Dynamic black list feature is configured for Receipt of message, ScmProcess allocates memory for ICM message but do not free the memory.

Steps to Replicate: Execute the DM Anti-trombone call flow so that two calls hits different SCM's.

Platform/Feature: SBC

Subscription information is lost on an SBC switchover in a particular direction.

The NOTIFY request is rejected with a 489 Bad Event message after a double switchover.

Impact: N/A

Root Cause: Ingress and Egress transparancy profile *present* bits was not set in Relay CB because of which they are not getting mirrored during second switchover.

Steps to Replicate:

1. Register and Subscribe from Active Machine.
2. Do a switchover so that Standby machine becomes active.
3. Do a switchover again so that Active machine becomes active again.
4. Now send Notify from core.

Platform/Feature: SBC

Portfix SBX-88996: As, the single character search is an exhaustive search operation which would in turn consume more time and space , the browser witnesses Timeout Exception due to which the blank screen is rendered to the user. (Originated in release 6.2.4).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: EMA

Portfix SBX-90195: A transport parameter is transparently sent when the Request-URI transparency is enabled for all messages. (Originated in release 8.1.0).

Impact: N/A

Root Cause: As prat of transparency support for Request URI, this parameter was transparently sent which shouldn't be sent.

Steps to Replicate:

1. Enable transparency for Request URI.
2. Make a TLS-UDP or TCP-UDP call with transport parameter in Request URI.
3. Transport parameter will sent transparently though the call is UDP in egress leg.

Platform/Feature: SBC

Portfix SBX-76393: The CPX process was timing out when requests were made for specific rows in an interval statistics table, only used to populate the statistics tar file. (Originated in release 6.2.4).

Impact: N/A

Root Cause:  Interval statistics tables that are used only to populate the statistics tar file do not support requests for individual rows, and those requests time out.

Steps to Replicate: N/A

Platform/Feature: SBC: confd

For registration, the 200OK has the service-route, and the flag Stored service route enabled. If the Server sends multiple notifications without a record-route before the Subscribe is stable, the SBC may core due to duplicated freed memory.

Impact: N/A

Root Cause: SBC may core due to duplicated memory free.

Steps to Replicate: Test: ~stran/sipp/sippc_89788.xml and sipps_89788.xml

Platform/Feature: SBC

Portfix SBX-87321: Sip Parser has predefined method length restriction set to 128 and a negative test case in Codenomicon test suite with a method including more than 128 characters is resulting in a coredump. (Originated in release 8.0.0).

Impact: N/A

Root Cause:

1)When ever CSEQ method name comes beyond 127 character size and SMM profile is applied, SBC taking box down as it is missing boundary condition

2)When From Tag is missing in Dialog scope variable data, SBC taking box down as it is missing NULL check

Steps to Replicate: N/A

Platform/Feature: SBC

Added software checks to enforce upper limit as well as NULL termination

Portfix SBX-75715: The SCM reports a deadlock when multiple set operations are committed. The feature previously worked in earlier releases and does not work in 7.x releases. (Originated in release 8.0.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: CLI

Registrations with a syntax error cause an incorrect REG counter.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-89220: The 200 OK is not being sent for call HOLD when the sdpAttributeRelay is enabled on the Trunk Group. (Originated in release 8.1.0).

Impact: N/A

Root Cause: Setting this flag SIP_SDP_CTRL_IS_CHANGED_SDP and properly not resetting it is causing the issue

Steps to Replicate: Run a Audio Video call and UAS sends the answer with Audio and Video(Stream disabled). Send the hold invite with change in datapath mode, 200 OK for this is not being sent.

Platform/Feature: SBC

The PSX Name field is not being populated in CDR's.

Impact: N/A

Root Cause: Code was missing to handle the PSX name and copy to CDR's

Steps to Replicate: N/A

Platform/Feature: SBC

When "show status addressContext <addressContext_name> ipsec ipsecSaStatistics" and "show status addressContext <addressContext_name> ipsec ipsecSaStatus" commands are run and the IPSec is configured, the IKE Process will leak memory.

Impact: N/A

Root Cause: Memory leak occurs because of double allocation of key and value buffers which hold IKE statistics.

Steps to Replicate:

Configure IP SEC AKA on SBC.
Run valgrind.
show status addressContext <addressContext_name> ipsec ipsecSaStatistics.

show status addressContext <addressContext_name> ipsec ipsecSaStatus
Make sure AKA is configured and working correctly.
Check valgrind output.
Certain blocks of size 664 and 16 will be shown.

Platform/Feature: SBC: IPSec, SIP

[SMM] The Scm process core dumped while modifying the URI scheme.

Since the stHdrString is not MemZero and when we try to free the memory which is junk, coredump occurs.

Impact: N/A

Root Cause: The core dump was observed as memory of few structures were not memzero.

Steps to Replicate: N/A

Platform/Feature: SBC: Application

The call setup time under the currentCallStatistics output was not calculated correctly.

Impact: N/A

Root Cause: The code was incorrectly managing the cumulative total for this field and dividing it by 100.

Steps to Replicate: Make multiple calls with a delay between sending INVITE and receiving 18x message and check the call setup time is correct.

Platform/Feature: SBC

In old scenario, using ':' for separation between attribute name and value.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When the saveCallFlows is enabled, and only Out of Dialog Messages are received, a memory leak occurs.

Impact: N/A

Root Cause: Packets without a GCID associated with them are stored in a queue until a packet is sent or received with a GCID

Steps to Replicate: N/A

Platform/Feature: SBC

When the SIPT library was returning a DISCARD_MSG event to SIPSG while trying to send out a message, it results in the call being released if the MIME disposition was required.

Impact: N/A

Root Cause: If the SIPT library returns DISCARD_MSG there is no need to release the call.

Steps to Replicate: Make a SIPT to SIPT call where the ingress revision is spirou and the egress revision is itut92+ and send a CPG message with the event indicator of 5 in the backward direction.

Platform/Feature: SBC

During the long load run, a few 503 responses are seen from the SBC.

Impact: N/A

Root Cause: The issue is seen because of SBC wrongly identified INVITE PDU type as OTHER and not INVITE only in the case when first partial PDU received over TCP as fractional INVITE word.

Steps to Replicate: In long load run over TCP on ingress side.

Platform/Feature: SBC

Portfix SBX-90379: Pathcheck process currently supports 32 DNS records, whereas the DNS client supports 100 so there was a mismatch and this pathcheck process crash was seen when there are more than 32 records. (Originated in release 8.1.0).

Impact: N/A

Root Cause: PathCheck process crash was seen due mishandling of the records when the number is more than 32.

Steps to Replicate:

1. Configure patch check profile to IP peer to send OPTION sip message as ping.
2. Patch check host name peer as FQDN.
3. TCP fallback enabled for DNS server configuration.
4. TC flag set coming from DNS server, which basically indicates that DNS response is truncated.
5. DNS reply has more than 32 SRV records.

Platform/Feature: SBC

During registration failures, and peer tries to register again, the SIPFE and SIPSG may become out of sync.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

SIPS is no longer responsible to answer the re-transmissions and the application directly handles the answer to avoid an out of sync registration.

The SCM may core while processing SIP INVITE headers.

Impact: N/A

Root Cause: The received INVITE message is not as per RFC 5626 that requires +sip.instance to be followed by a value.

Steps to Replicate: N/A

Platform/Feature: SBC

When invoking an API with an input param, the input params were not getting validated because the validation code was not present for the rest of the API input params.

Impact: N/A

Root Cause: When we were invoking any rest API with some input param. Input params were not getting validate because validation code was not present for rest API input params.

Steps to Replicate: Call rest API using curl command with invalid input params value.

Platform/Feature: SBC

The mgmtRedundancyRole is displaying Unknown instead of active/standby.

Impact: N/A

Root Cause: SmaGetMgmtRedundancyRole() which returns the mgmtRedundancyRole is returning rgmRedundancyRole instead of redundancyRole

Steps to Replicate:

Run cli command: show table system serverStatus <system name> mgmtRedundancyRole

admin@CEGVM3> show table system serverStatus CEGVM3 mgmtRedundancyRole
mgmtRedundancyRole active;

Platform/Feature: SBC

When there are multiple ipInterfaces in different subnets in an ipInterfaceGroup, the sipSigPort address can remain bound to an ipInterface with an unmatching subnet. The sipSigPort address does not move to an ipInterface with the matching subnet when the ipInterface with the matching subnet becomes enabled and in-service.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When the packets are logged as part of the SBC Packet Collector for Core Dump Analysis functionality, if there are SMM rules applied to those packets, the packets are not stored after the SMM rules have been applied.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The user was able to read any file from the under-privilege REST user through a GET request.

Impact: N/A

Root Cause: In old scenario, input sanitization for rest call parameters not present.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-70808: It is not possible to use the EMA "Test SIP Adaptor Profile" or a CLI command "request profiles signaling sipAdaptorProfile getDigits testProfile" to test an SMM rule that manipulates an ISUP MIME body, because these mechanisms only support ASCII characters and the MIME body is binary. (Originated in release 8.0.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The packets are captured out of order. Though all packet data is present in memory, the packets are not stored in the proper order.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

/home/log/session directory has a record of the terminal session logs for all the users and the directory is world-writable without being set. 

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

A user is not able to create a group starting with '.'

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The OS user linuxadmin was not getting the shortened lockout time of 10 seconds, when the OSAccountAging goes from being disabled to enabled.

Impact: N/A

Root Cause: Misspeliing in command to update the PAM config files.

Steps to Replicate: N/A

Platform/Feature: SBC

The Packet Loss Threshold is not set properly in the NP, so the NP will report a packet loss incorrectly.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When the To header transparency and call route by TN is on, the R-URI is uncorrected.

Impact: N/A

Root Cause: Incorrect logic to treat RURI as transparency.

Steps to Replicate: N/A

Platform/Feature: SBC

When the DRM (Application) is not receiving the response from the UXPAD for the health check messages, the DRM sends SIGABRT signal to the unresponsive UXPAD (using the UXPAD process number) to generate a coredump. 

Impact: N/A

Root Cause:

While we get the PID of the Process using the UXPAD process number, we were not searching for the exact match.
If the UXPAD number is 1, it matches all the UXPADs/TPADs that have 1 in their process number ex: 1, 10, 11, 12, 21 etc, and the SIGABRT signal was sent to all those processes.

Steps to Replicate:

This issue can be produced with instance having more than 10 UXPADs.
We don't need to run calls to reproduce this.

Kill UXPAD with process number 0 or 1.

Get the PID of the desired UXPAD
> ps -elf | grep UXPAD
(/opt/sonus/bin/swe/SWe_UXPAD -c 0x8 -n 1 --proc-type=secondary --no-pci -- -c4 -t1)
choose the PID with process number 0 to 1 (process number is the last field "-t<process number>" in the output when the above command is executed).

Kill the UXPAD.
> kill -9 <PID>

Since the UXPAD was killed, the DRM does not get the response for the health check messages and it issues the SIGABRT Signal.

Without this fix the coredump gets generated for the wrong UXPAD that matched the process number (not exact match)
With this fix it does not generate the core as the desired UXPAD was not live.

We can monitor these logs in "/var/log/syslog", search the relevant messages with the keyword "coredumpSweDsp"
Also we can check cores dumps in "/var/log/sonus/sbx/coredump"

Platform/Feature: SBC

Privilege Escalation by www-data on the SBC (Runtime Diagnostics Test).

Impact: N/A

Root Cause: runDiagField.sh has sonusadmin ownership and can be modified by sonusadmin to escalate to root.

Steps to Replicate: N/A

Platform/Feature: SBC

When the configuration for the connected realm (Address Context > Realm > Connected Realm) is created and the realm name used already exists, the code was reading off the end of a memory buffer.

Impact: N/A

Root Cause: The code was using a memory copy routine which always copied a fixed amount of memory regardless of the string size that existed in the source memory location. This lead to reading off the end of the memory buffer.

Steps to Replicate: This issue is only seen when using special ASAN images

Platform/Feature: SBC

First, a DNS query was getting initiated through the mgmt even if the IP was configured. The Patchchk process core dumps when the truncated DNS response is received from DNS server.

Impact: N/A

Root Cause:

As default static routes are configured and mgmt. get the preference, that's the reason DNS query was initiated via mgmt. interface.
Ptachcheck process core dump was happening because of its inability to handle truncated DNS response.

Steps to Replicate:

1. configure patch check profile to IP peer to send OPTION sip message as ping.
2. Patch check host name peer as FQDN.
3. TCP fallback enabled for DNS server configuration.
4. TC flag set coming from DNS server, which basically indicates that DNS response is truncated.

Platform/Feature: SBC

The SecureNAT does not learn the remote IP address.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

SIPS/SIPSG: The 200 Ok (connect) is not sent to the ingress, and ACK is not sent to the egress, when a call is handled using a custom call script.

After the announcement script run is completed, the CC confuses the script as a multiparty call transfer script and not telling the ingress to connect the call (send 200OK).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC allowed a user to use the same IP address for a route next hop that caused a loss of traffic to all off-net peers across the SBC interface.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

For sRTP call, the SBC does not reset the ROC while doing an sRTP encryption, even if the SSRC changes. This may cause the remote decryption operation to fail on some 3rd party equipment.

Impact: N/A

Root Cause: The fast path design wasn't paying attention to the SSRC changes while doing sRTP encryption operation.

Steps to Replicate:

This specific fix has been tested/verified in unit-test environment. The following is not required, but just for the sake of completeness:

Set up an sRTP call, run it for 25 minutes, make sure there is two-way audio.
Without signaling it, force a change to the SSRC on one side
check if there is one-way audio.
Repeat the above step with 6.2.0R0 and 6.2.3A16.

Platform/Feature: SBC

An internal module's passphrase generation method was not strong.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC, while trying to create DM NAPT table (after retrieving the details from the Database), was trying to read the end of a memory block for some of the parameters in the table (such as table name, etc).

Impact: N/A

Root Cause: While copying the different parameters from the database to DM NAPT table, the code was copying fixed size table name string. This might result in reading off the end of a memory block and if the memory block is at the top of the heap then it can cause invalid memory access and result in crash.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-75943: When an video+audio directmedia call with m=audio after m=video in the SDP is made (audio becomes the last stream), the LIF bandwidth is allocated though it is a DM call.(Originated in release 8.0.0).

Impact: N/A

Root Cause: In nrmaResAlloc.c, the code to set the session BW to 0 (xrmBwChangeCmd.sessionBwBps = 0) is never processed for audio since it is inside a block meant for non-audio streams.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-89089: If a name change operation is performed to swap any of the two system names (CE name or peer CE name), the SBC application may fail to start. (Originated in release 8.1.0).

Impact: N/A

Root Cause: There are some config files where there is no distinction between the key used for specifying the system name and CE names. A swap in such a file cannot be done correctly.

Steps to Replicate: N/A

Platform/Feature: SBC

The I-SBC does not span across multiple vNUMA nodes, causing a SWe_NP failure to launch.

Impact: N/A

Root Cause: The failure happens due to improper allocation of hugepages for SWe_NP in case it is dual NUMA ,failing SWe_NP to come up.

Steps to Replicate: Follow the guidance to restrict ISBC to be confined within same NUMA in which packet port is connected.

Platform/Feature: SBC

The SWe SBC software is updated to enforce I-SBC instances to run only with single vNUMA node in order to achieve deterministic performance.

Portfix SBX-89586: Loading the TEAMS Template token from the EMA is not working. The Token load option does not load values into the template. No action is triggered even after clicking the Token load. (Originated in release 8.1.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The radiusSharedSecret may appear in plain text in the logs.

Impact: N/A

Root Cause: Debug print statements caused the passphrase to be written to the logs.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-90289: The SBC cored after swapping a name (CE and System) and performing a clearDb action. (Originated in release 8.1.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Currently, all filters are not displayed for tables such as Call Detail Status, Call Media Status, and Call Resource Detail Status.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

In case of SUBSCRIBE Relay refresh, the the R-URI must be based on the last Contact received if the first route set has the lr parameter.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-90085: When special character inputs are used for the call number filter in the CDR viewer table, the input validation fails and the page keeps showing the table as 'Loading...'. (Originated in release 6.2.4 ).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The code is modified so the user can filter the called number data in CDR Viewer table, with numbers and few special characters such as #, *, +, -

When history info header is received and International Nature of Address (NOA) Plus flag is enabled, the NOA printed in CDR log is incorrect. The NOA for the original called and redirecting number must be set to International.

Impact: N/A

Root Cause: When history info header is processed , International Noa Plus flag is not considered.

Steps to Replicate:

Reproduce the issue by
Enabling following 2 flags :
History Info on Ingress SIP TG.
International Noa Plus

Send INVITE with
History-Info: <sip:+442071899987@telekom.de;user=phone?privacy=history>;index=1
History-Info: <sip:+442071900059@telekom.de;user=phone;cause=302>;index=1.1

Actual Result in CDR ACT logs :
REDI,20,442071899987,442071899987,3,3,1,1,1,2,,,,,,,,,,,0,2

Expected Result:
REDI,20,442071899987,442071899987,3,3,1,1,1,3,,,,,,,,,,,0,3 --> two HI

Difference is NOA parameter for redirecting original called number. It should be 3.

Platform/Feature: SBC

When LRBT is enabled for an ICE call and egress, the endpoint responds to initial INVITE with an 183 progress message with the SDP parameters followed by an 180 without the SDP and a 200 OK with the SDP. Following the local ring back tone, the SBC initiates re-INVITE to the egress endpoint that is missing ICE ufrag, password and RTCP candidate line in the SDP.

Impact: N/A

Root Cause: Error in the software that was causing the ICE information for the call to be incorrectly cleared in this particular scenario.

Steps to Replicate:

Create sbx configuration to allow ICE sip to sip call to be routed between ingress and egress TG's.
Create a toneAndAnnouncementProfile for LRBT with dynamicLRBT disabled and associate the profile to the ingress and egress TG's.
Enable rtcpMux on the PSP associated with the ingress and egress TG's

Method
----------
1. Send INVITE to SBX ingress with valid ICE SDP including rtp and rtcp candidates and a=rtcp-mux.

2. From egress endpoint, respond to INVITE with with following sequence
183 Session progress including valid SDP with ICE
180 Ringing without an SDP
200 OK including valid SDP with ICE

3. At ingress endpoint,
Respond to 200 Ok with ACK
At egress endpoint,
Respond to re-INVITE with valid 200 OK

Complete call signaling and stun exchange at ingress and egress

Platform/Feature: SBC

CDR records are broken into multiple syslog messages.

Impact: N/A

Root Cause: There was a limit to the message size of ~1.8K and CDR messages beyond that would be split into multiple syslog messages.

Steps to Replicate: N/A

Platform/Feature: SBC

During SMM testing, the code for handling message scope variables could read off the end of a memory block while printing a debug statement.

Impact: N/A

Root Cause: There was a limit to the message size of ~1.8K and CDR messages beyond that would be split into multiple syslog messages.

Steps to Replicate: N/A

Platform/Feature: SBC

If a domain license is installed on the head end node, but the license is pushed out to another node more than an hour later, the push of the license is not successful.

Impact: N/A

Root Cause: N/A 

Steps to Replicate: N/A

Platform/Feature: SBC

The call setup time under the currentCallStatistics output was not calculated correctly.

Impact: N/A

Root Cause: The code was incorrectly managing the cumulative total for this field and dividing it by 100. 

Steps to Replicate: Make multiple calls with a delay between sending INVITE and receiving 18x message and check the call setup time is correct.

Platform/Feature: SBC

Software Update fails if an snmp trapTarget with a name containing white-space characters is configured.

Impact: N/A

Root Cause: A change was added to remove prefixes on trapTarget names during software update. This change does not work with names containing spaces, which is possible when manually creating a trapTarget from CLI only.

Steps to Replicate: On old software, manually create a trapTarget from CLI with a name containing at least one white-space character - to do this, the name must be quoted.
Then perform LSWU - this fails.

Platform/Feature: SBC

The function SipSgContinueCallProcessing() acquires pstCall using SipCallFromHandleAndLockCCBCmd() and after use, the function was not releasing pstCall, causing memory leaks.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When the HA peer is upgraded, the upgrade screen shows an error pop up with "Internal Operation error session_start" content.

Impact: N/A

Root Cause: It was happening because of cnxipm directory was deleted and not able to create again, meantime system was trying to session under cnxipm director.

Steps to Replicate: To reproduce this issue, we have to upgrade the system in HA peer mode.

Platform/Feature: SBC

SNMP v3 doesn't work after the upgrade/restore.

Impact: N/A

Root Cause: SNMP version is not applied after upgrade/restore

Steps to Replicate: N/A

Platform/Feature: SBC: confd, Install/Upgrade Platform

There is One way audio after call transfer is made on the SWe when Ring Back is enabled with SRTP towards the MS TEAM to relay it back to PSTN behind the SBC. 

Impact: N/A

Root Cause: With this call transfer BRES is deactivated, activated again, while reusing BRES associated SRTP ENC context it should retain the old required values in contexts, which is missing in SBC SWe

Steps to Replicate: N/A

Platform/Feature: SBC

An Application on active may crash when the HA connection is frequently bouncing.

Impact: N/A

Root Cause: If the HA connection bounces while an scp operation is in progress then the copying gets stalled resulting in health check timeout in application in turn causing a crash suspecting deadlock.

Steps to Replicate: N/A

Platform/Feature: SBC

The SBC is using the surrogate Registration hostPart as the target FQDN. 

Impact: N/A

Root Cause: surrogate hostPart is over-write egress IpPeer fqdn (target route)

Steps to Replicate:

1. configure surrogate registration with hostPart.
2. configure Egress route as fqdn (Egress IpPeer is fqdn).
3. enable surrogate registration.

Platform/Feature: SBC

Portfix SBX-89491: If a split-brain occurs prior to the standby being up and being fully synced, selecting the former standby as the leader when coming out of a split-brain will result in a complete outage. (Originated in 8.1.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

 Platform/Feature: SBC

The template form on the Configuration Script and Template Import page is not getting displayed due to some failure. 

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Unable to upload configuration in the SBC in the Provision Management.

Impact: N/A

Root Cause: unable to create export directory to store configuration file.

Steps to Replicate:

1. Logged in to ems gui as admin user
2. Switch to Networks tab
3. Go to provisioning
4. Clicked on SBC Core under provisioning
5. Clicked on upload configuration
6. Provided the required configurations.
7. Clicked on upload.
8. Before fixing the issue --
9. Configuration did not got uploaded.
10. After fixing the issue ---
11. Configuration uploaded successfully.

Platform/Feature: SBC

DSP card present status is not updated if the card is administratively disabled.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

When using EMA and accessing the Call Trace/Logs/Monitors > Log Management > TShark, the screen does not list the files if there are more than 130 files in the directory.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Serialization errors are logged in the SYS log for type 137603, which points to CPC_OP_TYPE_AC_ZONE_INFO, that in-turn caused the coredump.

Impact: N/A

Root Cause: Serialization errors are because of CPC_OP_TYPE_AC_ZONE_INFO (137603) not getting registered and trying to send it to standby SBC.

Steps to Replicate: Execute LSWU from any version above 7.2.1 R1 to any other above versions.

Platform/Feature: SBC

The NRS task failed healthcheck when there was over 3000 status requests per minute.

Impact: N/A

Root Cause: NRS task was calling out to CONFD for each packet LIF status request.

Steps to Replicate: N/A

Platform/Feature: SBC: Application, confd

Portfix SBX-89957: In TR87 service (CSTA) call flow, INVITE transaction in SIP stack on ingress is not killed, the timer G expires and continues re-sending 200 OK to ingress. (Originated in release 6.2.4)

Impact: N/A

Root Cause: SBC is not killing INVITE transaction in SIP stack on ingress once we receive ingress ACK (to complete INVITE-200).

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-90846: Memory leak due to the use of the delete operator. (Originated in release 8.1.0).

Impact: N/A

Root Cause: Memory leak due to use of delete operator

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-91594: When SBC-7000 is under high call load with RTCP termination and unstable traffic (reaching 10Gb traffic instantaneously), the Network Processors cores stall. Media traffic stops and PRS coredump is generated. (Originated in release 6.2.4).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: Firmware

A bug in GW Signaling code can cause a core when the GW Signaling Links are bouncing.

Impact: N/A

Root Cause: A bug in GW Signaling code can cause a core when GW Signaling Links are bouncing.

Steps to Replicate: N/A

Platform/Feature: SBC

Apache server is not running.

Impact: N/A

Root Cause: Missing library.

Steps to Replicate: Start apache server.

Platform/Feature: SBC: Platform

When a logicalMgmtIpInterface is configured, and the useIpAddrAsSnmpSource is set to true. The source for snmp traps are the specified address in the logicalMgmtIpInterface ipAddress field. However, the source of the traps is not the correct address, and instead the address is of one of the management IP ports.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC: confd, Management, Platform

AppContextId within NRMA_CALL_PTR is not being synced to standby after a switchover. As a result, Wile bridging calls NRMA identifies the Id as zero and crashes.

Impact: N/A

Root Cause: AppContextId within NRMA_CALL_PTR was not being synced to standby after switchover.

Steps to Replicate:

1) Make a call between A and B
2) Switchover
3) REFER C
4) Swithover
5) REFER to wrong IP

No crash should happen

Platform/Feature: SBC

Gencom client sends a 481 for call park retrieval INVITE. When an incorrect tag in Replaces header, it is sent through the SBC.

Impact: N/A

Root Cause: Also, When we do egress lookup when replaces call isn't connected yet, we are not finding CCB because of incorrect tag setting during lookup.

Steps to Replicate: Execute call park and retrieve case where parked call is not established yet.

Platform/Feature: SBC

If the LinkDetection interfaces are configured to use addresses specified in the systemMetaVariable dynamic table, those addresses are not properly read and LinkDetection is not activated.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The Broadsoft AS returns the 403 for a REFER Request due to From and To tags are swapped.

Impact: N/A

Root Cause: "To tag" and "from Tag" were being swapped twice, resulting to their original respective values in outgoing REFER's Replaces header section.

Steps to Replicate: N/A

Platform/Feature: SBC

ARM calculates the amount of memory that needs to be freed from the NP (Y has a multiple of certain number of fixed sized PNPS_ANN buffers) to fit in a new announcement the size of a WavFile_X. Due to design size, Y is not equal to size of WavFile_X.

Impact: N/A

Root Cause: Customer hit this issue because they touched the max amount of announcements cached in the system. Probably no other customer did that and that’s why it never came out.

Steps to Replicate: Run customer flow with customer's announcements all dumped into system.

Platform/Feature: SBC

The ACL rules in a non-default address context were not getting added back to the NP after a sbxrestart/reboot. Without this fix, the ACL rules configured in non-default address context do not work.

Impact: N/A

Root Cause: Root cause for this issue was iteration of rules list wasn't proper resulting in non-default address context rules not being added back after sbxrestart/reboot.

Steps to Replicate: This issue can be reproduced by adding some ACL rules in default address context and some in non-default address context, After a sbxrestart/reboot, only the rules in default address context work.

Platform/Feature: SBC

Portfix SBX-88766: The improper value for RFactor was displayed under the CLI command: trunkGroupQoeStatus. (Originated in release 7.2.1)

Impact: N/A

Root Cause: This became broken as part of N:1 feature done in release 6.1

Steps to Replicate: N/A

Platform/Feature: SBC

In the case of status commands executed from the CLI, a request is sent to both active and standby nodes. An LVM running on active and standby nodes compares the CE name configured in the LDG with a server name and returns stats only for LDGs that are configured on that CE. However, there is no similar check in the case of a PF stat. Without the check for a PF stat,the statistics displayed for LDGs configured on standby node was not correct.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The cluster configuration for saveConfigStoreFile fails on the head end node due to a change of permission by keyKeeper.py. The sbcRegistration was not readable by the admin as a result of the configuration failure.

Impact: N/A

Root Cause: N/A 

Steps to Replicate: N/A

Platform/Feature: SBC

Failure stats are not being printed in the SBC stats file while it is showing in "show table addressContext default linkDetectionGroupStatistics". The LDGs are configured on both active and standby nodes. An LVM running on active and standby nodes compares the CE name configured in the LDG with server name, and returns stats only for the LDGs that are configured on that CE. However, there is not a similar check in case of PF stat. In response, the statistics displayed for the LDGs configured on standby node are not correct.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

The code is modified to compare the CE name and return stats associated with the LDGs configured on the respective nodes.

The SRTP enables calls in the SWe SBC and causes the NP_Work_2 to sporadically crash and core.

Impact:

Root Cause: In SWe SBC, NP API updates are asynchronous w.r.t packet processing, If packet processing is accessing the API cleared pointer it result in crash.

Steps to Replicate: This is sporadic, running SRTP calls load can trigger this crash sometimes.

Platform/Feature: SBC

The SBC was not sending the ACK to the 200OK for an INVITE after the 4th switchover.

Impact: N/A

Root Cause: Syncing of transferred calls to standby was not proper

Steps to Replicate:

1) Make a call form A to B
2) Switcover
3) Transfer from B to C
4) Switchover
5) Refer from C to D
6) Switcover
7) Refer from D to E
8) Call should be connected between A and E

Platform/Feature: SBC

Portfix SBX-87053: The SBC fails to apply an ARS procedure on collecting a 503, with or without a Retry-After header when the FQDN is configured on the IP Peer. (Originated in release 8.0.0).

Impact: N/A

Root Cause: When FQDN configured on IP Peer, on getting 503 SBC should look for DNS resolved IP address, instead SBC looking at FQDN configured in IP peer and hence it fails to apply ARS.

Steps to Replicate:

1. Configure FQDN in IP peer
2. Enable uriPreference flag
3. Simulate UAS to reject INVITE with 503
4. SBC should apply ARS procedure on getting 503

Platform/Feature: SBC

The System Diagnostics throws an error in Custom-> View Custom Perspectives through the xpath, which is incorrect.

Impact: N/A

Root Cause: Xpath was old must have been changed. Old xpath was not part of model.

Steps to Replicate: N/A

Platform/Feature: SBC

The status of the Routing Label Route in a table shows as out of service, even if it is In service when created. The out of service status shows when the code picks the wrong data for validating the status.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-85902: Whenever there is any SMM rule for a SDP body, the SMM will remove all linear white space before and after the “=” character from each SDP line.The removal of the white space before and after the "=" character results in a SIP parse error when valid lines "s= " or "l= ". (Originated in release 8.1.0).

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

Remove the plainText EMS Passwords from the userData/MetaData files in cloud. EMS plain text password cannot be present in the SBC, it must be replaced with hashes.

Impact: N/A

Root Cause: N/A

Steps to Replicate: N/A

Platform/Feature: SBC

A call is torn down if the SendOnlyPreferred enabled.

Impact: N/A

Root Cause: The receive and transmit payload type for ULAW and ALAW are not correctly set.

Steps to Replicate:

sipp -sf /sonus/support/SBX-87883/scenario_0x00408a30_UAC.xml -s 890 172.23.243.230 -m 1 -i 10.7.20.75
sipp -sf /sonus/support/SBX-87883/scenario_0x00408a30_UAS.xml -p 16284 -i 10.7.20.75

Enable SendOnlyPreferredCodec and HOP and HRP.

Platform/Feature: SBC

Portfix SBX-87242: When the DNS packets are received over a TCP, during the failure case (primarily when the length is less than 0 after a reading from the socket), there is no validation of the DNS TCB (Transaction Control Block) pointer while processing. (Originated in release 8.1.0).

Impact: N/A

Root Cause:

This issue was reported as part of ASAN testing in SBC lab.
When SBC is receiving packets/PDUs from DNS server via TCP, it does the following
1. Process the PDU (valid data received from TCP socket). Once the PDU is processed, the Transaction Control Block (TCB) maintained is freed.
2. For the same transaction, if some data is received with the length < 0, we check if the TCB exist to process the connection failure. Here we are not checking whether the TCB pointer is already freed (i.e. NULL) or not.

Steps to Replicate: N/A

Platform/Feature: SBC

The Nessus scan found multiple vulnerabilities (1 critical, 3 high, 2 medium).

Impact: N/A

Root Cause: Many packages are out of date.

Steps to Replicate: Run Nessus scan.

Platform/Feature: SBC: Application

Portfix SBX-87182: There is an error while importing a perspective having " - " in the perspective name. (Originated in release 6.2.4).

Impact: N/A

Root Cause: Missing Validation for checking unwanted and illegal characters in the file names.

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-86593: An EMA Template fails to import the Config when Special Characters are present. (Originated in release 6.2.4).

Impact: N/A

Root Cause: Logic to escape the HTML Characters was used while reading the request parameters . (Java Escape HTML Logic was in place).

Steps to Replicate: N/A

Platform/Feature: SBC

Impact: Interception of LI calls fail during upgrade (for instance, when the setup has S-SBC and the M-SBC running on different versions). The impact is only for in-service upgrade. No impact with respect to LI calls, when the VNF is brought down and re-created for upgrade..

Workaround: No workaround available.

Impact: In the rare case where a PRACK for 18x is dropped and the call eventually fails, a small leak of SCM memory can occur.

Workaround: No workaround available.

When a headend cluster configuration is pushed, the Standby SBC reboots and hangs without getting the Configuration.

When a Standby SBC is rebooted, it transitions to registered online then later unregistered offline. This also happens in #1, Standby reboot after Configuration is pushed.

Platform/Feature: SBC Core: EMA

Impact: When a headend cluster configuration is pushed, Standby SBC fails to download the configuration and so fails to come up properly.

Workaround: To resolve the above issue, the fill rate and bucket size needs to be increased in lca.py script and the Standby SBC system needs to be rebooted so that it can download the configuration again.

CallMedia and CallDetailstatus do not show in the EMA during the load run.

Platform/Feature: SBC Core: EMA

Impact: Call details Status and Call Media Status are intermittently not visible in the EMA.

Workaround: Call details status and Call Media status can be viewed from CLI.

Impact: Under load with 30,000 simultaneous NP tones playing M-SBC switches over. M-SBC system confirmed to perform fine up to 28,000 simultaneous NP tones.

Workaround: No workaround available.

Impact: A PDU of a size less than 6K is rejected with 400 Bad Request, when maxPduSizeValue is set to 6K.

Workaround: Increase the maxPduSizeValue to 15k.

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: While upgrading from pre-7.1 releases to 7.1 and 7.2 releases, if the SNMP trap targets are setup with <space> in the name field then the upgrade fails. This affects all the platforms (SBC 5xxx/7xxx/SWe).

Workaround: Prior to the upgrade, the user must check and delete/replace any trap targets that are setup with <space> in the name.

SBX-86003

Impact: The peer may reject the call.

Workaround: No workaround available.

Impact: A call onhold/offhold before being connected by Update may fail.

Workaround: Enable E2E Update.

A race condition occurs under a 3x load scenario where MRF is configured as FQDN and none of the MRF server responds.

Platform/Feature: SBC: DSBC

Impact: The SCM process may core dump.

Workaround: No workaround available.

Impact:

The RTP monitoring feature will not work for IPv6 terminated peers, and therefore the following behavior will be observed.

1. If The SBC is in tone playing state and expecting media cut through after successful monitoring, the SBC will continue the tone play even though the expected RTP packet count is received, which is discarded by the SBC because of this issue.
2. If the SBC does not have conditions for delayed tone play, is not in tone playing state and is expecting media cut through after successful monitoring, the SBC will discard media packets because of this issue.
3. If the SBC has conditions for delayed tone play, is not in tone playing state, and is expecting media cut through after successful monitoring, the SBC will discard media packets because of this issue and therefore the delayed tone play starts because of the monitoring failure.

Workaround: no workaround for IPv6, but the same feature works for IPv4.

Impact: A PDU of a size less than 6K is rejected with 400 Bad Request, when maxPduSizeValue is set to 6K.

Workaround: Increase the maxPduSizeValue to 15k.

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: While upgrading from pre-7.1 releases to 7.1 and 7.2 releases, if the SNMP trap targets are setup with <space> in the name field then the upgrade fails. This affects all the platforms (SBC 5xxx/7xxx/SWe).

Workaround: Prior to the upgrade, the user must check and delete/replace any trap targets that are setup with <space> in the name.

SBX-74179

1

Impact: IPv6 with X710 NIC cards in SRIOV mode will not work as multicast packets will be dropped by the PF.

Workaround:

Set the trust mode to "on" for all the VFs on the computes.

ip link set dev <PF name> VF <vf id> trust on

This needs to be done for all computes and all created VFs (this change is not persistent across reboots). This will allow Multicast promiscous mode to work.

Otherwise, add a static neighbor table entry on the remote servers connecting to the SBC using the following command:

ip -6 neigh add <IPv6 address> lladdr <link-layer address> dev <device>

SBX-73218

Platform/Feature: SBC CE: Application

Impact: Virtual ports intermittently stop responding on compute node running on RHOSP 13 (Queens) under certain conditions. Specifically, at 1000 RPS with refresh registration interval at 180 seconds, virtual ports stop responding after reaching 500K registrations. This issue is not seen when the refresh registration interval is configured as 200 seconds and above

Workaround: Use SR-IOV ports only when using RHOSP 13 (Queens) release.

SBX-73943

Platform/Feature: SBC Core: Application

Impact: The call signaling and media work properly, but media clipping can occur if the final cut-thru codec received from UAS is different from the codec that is being used for playing tone. 

Workaround: No workaround available.

SBX-74945

Impact: Commit cannot be issued in for all set commands until the ipInterfacegroup is committed.

Workaround: Commit should be issued for ipInterfacegroup first and then commit for the remaining set commands can be executed.

SBX-73660

Platform/Feature: SBC CE: Application, EMA/EMS

Workaround: Add a static route to EMS from the SBC through management interface.

Memory congestion was observed when executing around 64K calls in the 32GB SWe system.

Platform/Feature: SBC SWe: SIP-Peering

Impact: On a SWe system with 32GB 32vCPU, the SBC is only able to scale up to 60K calls instead of 64K, due to per call memory increase.

Workaround: No workaround available.

Observing 503 response for more time post port SWO in S-SBC.

Platform/Feature: SBC CE: Application

Impact: The load is 1000cps/120K calls. After doing port SWO on S-SBC, SBX rejects calls with a 503 response for 86 seconds. Later SBX again responds with 503 responses for approx 36 seconds. After that, it stabilizes.

Workaround: No workaround available.

The SBC is not able to handle 150 Sa/Sec IPsec load on the Yellowfin Platform.

Platform/Feature: SBC 5000/7000 Series: SIP

Impact: If the rate for IPsec SA setup using IKE is increased beyond 60 SA/s, errors are seen.

Workaround: No workaround available.

SBX-72652

The PSBC observing system is in continuous iRTT congestion during the overload test.

Platform/Feature: SBC CE: Application

Impact: IRTT congestion is observed continuously for the 15 mins duration of 3x overload. There is no congestion during normal 1x load. This is 1000cps/120K in DSBC (PSBC).

Workaround: No workaround available.

The SBC failed to generate Enum lookup after updating the dynamic metaVariable.

Platform/Feature: SBC CE: Application

Impact: Enum lookup fails to generate if the meta variable related to sipSigPort (used for the Enum lookup) is dynamically updated.

Example:

Before updating sipSigPort with new dynamic metaVariable:

admin@vsbc1% show global servers lwresdProfile

lwresdProfile DEFAULT {

    description          DEFAULT;

    enumDomainNameLabel  DEFAULT_ZONE_LABEL;

    enableLwresdLog      disable;

    type                 signalingIp;

    addressContext       default;

    eDnsGlobalBufferSize 4096;

    eDnsMonitorInterval  120;

    zone                 ZONE_ING_V6;

    sipSigPort           3;

    ipInterfaceGroupName LIG_ING_V6;

}

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   IF2.IPV6;

}

[root@VSBCSYSTEM-vsbc1 linuxadmin]# lsof -ni:5060

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

CE_2N_Com 32059 sonusadmin  110u  IPv6 3716854      0t0  UDP [fd00:10:6b50:5d20::c9]:sip

CE_2N_Com 32059 sonusadmin  111u  IPv6 3716855      0t0  TCP [fd00:10:6b50:5d20::c9]:sip (LISTEN)

CE_2N_Com 32059 sonusadmin  112u  IPv6 3716856      0t0  UDP [fd00:10:6b50:5d20::a9]:sip

CE_2N_Com 32059 sonusadmin  113u  IPv6 3716857      0t0  TCP [fd00:10:6b50:5d20::a9]:sip (LISTEN) 

ENUM query is successful from sipSigport (fd00:10:6b50:5d20::a9)

After updating sipSigport to new dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME     VALUE                 

-----------------------------------------------------

vsbc1-10.34.195.109  lpl_egg  fd00:10:6b50:5d20::c9 

vsbc1-10.34.195.109  lpl_ing  fd00:10:6b50:5d20::c7 

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   lpl_ing;

}

[root@VSBCSYSTEM-vsbc1 linuxadmin]# lsof -ni:5060

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

CE_2N_Com 32059 sonusadmin  110u  IPv6 3716854      0t0  UDP [fd00:10:6b50:5d20::c9]:sip

CE_2N_Com 32059 sonusadmin  111u  IPv6 3716855      0t0  TCP [fd00:10:6b50:5d20::c9]:sip (LISTEN)

CE_2N_Com 32059 sonusadmin  112u  IPv6 3716856      0t0  UDP [fd00:10:6b50:5d20::c7]:sip

CE_2N_Com 32059 sonusadmin  113u  IPv6 3716857      0t0  TCP [fd00:10:6b50:5d20::c7]:sip (LISTEN)

ENUM query is not picking new sipSigport (fd00:10:6b50:5d20::c7) updated with dynamic metaVariable

Workaround: Do not update the metavvariable associated with a sipSigPort if Enum is being used.

Example:

Don't update the sipSigport to new metaVariable

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipsigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp

    ipVarV6                   IF2.IPV6;

}

Platform/Feature: SBC CE: Install/Upgrade(Platform)

Workaround: There is no workaround that is not service impacting.  Do not execute the Recreate_destroy option on a VM that has DHCP enabled.

Platform/Feature: SBC CE: Application

Impact: The old IP address is not getting deleted when the ipInterfaceGroup is updated with new dynamic meta variable.

Example:

Before updating ipInterfaceGroup with dynamic metaVariable:

admin@vsbc1> show table system metaVariable | match IF2.IPV6

vsbc1-10.34.195.109  IF2.IPV6      fd00:10:6b50:5d20::a9 

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     IF2.IPV6;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::a9/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8954 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9060 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:780288 (762.0 KiB)  TX bytes:902476 (881.3 KiB)                                                          

Creating dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME  VALUE                 

--------------------------------------------------

vsbc1-10.34.195.109  lpl   fd00:10:6b50:5d20::cf 

vsbc1-10.34.195.110  lpl   fd00:10:6b50:5d20::ff 

[ok][2018-11-13 07:11:41]

After updating ipInterfaceGroup with dynamic metaVariable (lpl) old IP (IF2.IPV6) is not deleted from interface

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::a9/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          inet6 addr: fd00:10:6b50:5d20::cf/128 Scope:Global

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9093 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9209 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:792396 (773.8 KiB)  TX bytes:917382 (895.8 KiB)

Workaround: To change an addressContext ipInterfaceGroup to use a different ipVarV6 you must delete the ipInterfaceGroup and recreate it.

Example:

Delete the interface group:

 delete addressContext default ipInterfaceGroup LIG_ING_V6

Create interface group with new dynamic metaVariable:

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::cf/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9093 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9209 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:792396 (773.8 KiB)  TX bytes:917382 (895.8 KiB)

 Note: Similar procedure for IPV4.

The RTCP port is not transparently passed in Direct Media.

Platform/Feature: SBC Core: Application

Impact: In case of a Direct Media call, the SBC will add an RTCP port in the outgoing INVITE SDP, when RTCP is enabled on Egress PSP and the RTCP port was not received in the incoming INVITE SDP.

Workaround: Disable RTCP flag on Egress PSP.

set profiles media packetServiceProfile PSP_DM_DTLS rtcpOptions rtcp disabled