SBC Core 07.02.02R003 Release Notes

V05.01.00F007

V07.01.00F003

V07.02.00R000

V07.02.01F001

V07.02.01F002

V07.02.01R003

V07.02.01R004

V06.01.00R009 

V05.01.02F008

Four SCMs cored after a switchover.

Impact: The SCMs have cored after a switchover.

Root Cause: There is a bug that allows the RTM to attempt to process the Call Audit fault, while still in STANDBY mode. The Call Audit fault will only be processed while in Active Mode. This causes a core.

Steps to Replicate: The steps cannot be reproduced.

Platform/Feature: SBC

The SCM fast memory increase caused a delayed switchover with an outage.

Impact: If the multilevel INVITE with Replaces is run, memory and CPU utilization by the SCM Process increases drastically and leads to core dump.

Root Cause: Each INVITE with Replaces is a new Callgroup. Each call group has their own segments. For each segment, there are associated segments.

When the Release call is invoked, it releases all segments and each call segment frees associated call segments. During the release, the flow for such a call event is posted multiple times for various orig and term GCID’s.

Steps to Replicate:

1. Test multilevel INVITE replaces (more than 15)
2. Crash should not occur

Platform/Feature: SBC

The code is modified so the event does not need to be posted multiple times for the exactly same original and term labels.

Portfix SBX-97129: After an upgrade to V08.02.00-R001, the Inbound Teams DDI call placed on hold causes a core dump.

Impact: Getting a Pes Process coredump while running registrations.

Root Cause: The CallParamMatchName function is called with a matchName, which is a 15 byte array and the strncpy is used to copy the string to the 50 byte array but with a wrong size of MATCH_NAME_SIZE, defined as 30 byte*.*.

Passing a bigger size than the actual destination string to the strncpy is resulting in padding 0’s beyond the actual 15 bytes of the matchName. This was corrupting the stack and the stack pointer, causing a segmentation fault.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The Edit route action taking a long time to complete.

Impact: The Edit Route action was taking long time and failing.

Root Cause: Use of special characters, such as # in destination National field, can cause the failure of the Edit route action.

Steps to Replicate:

1. Create Route with special character in Destination National.
2. Select the Route that is created in Special Character.
3. Edit Form must be load.

Platform/Feature: SBC

A few more special characters to support Destination National field in the Edit route are allowed.

NOTE: The following special characters are not supported: & = , \

After the LDG triggered a switch over, the SBC is rejecting all register messages with an 500 internal error.

Impact: The SCM process may coredump when the SIP signaling port being used during a SIP registration call flow is state disabled.

Root Cause: The SCM process core dumped when it attempted to display a debug warning message that contained the disabled SIP signaling port number (but encountered a NULL pointer).

Steps to Replicate: The steps cannot be reproduced.

Platform/Feature: SBC

TLS call failures were observed due to a port value set to 1 instead of 5061.

Impact: The SBC uses Port 1 for sending an INVITE out for the TLS protocol when the route header was received without a port.

Root Cause: The issue is because when the route header is received without a port in it, the SIPSG was incrementing the port for the TLS. Since the port was not received, the port received is considered as 0. For the TLS, increment by 1. When incremented, the port becomes 1 and this gets used for send an INVITE that is resulting in calls failing.

Steps to Replicate: Send the Route Header without port Route: <sip:ipaddr:;lr>. The SBC will use port 1 for sending an INVITE that is causing the issue.

Platform/Feature: SBC

The code is modified to check when the port is received in route header or not.
If port is received, then increment the port for the TLS. If it is not received, then increment and allow the SIP stack to handle it.

SBC is not sending RTCP to egress Peer for transcode only.

Impact: In customer call flow :

Ingress Peer -(ISDN)> GSX ---(GW2GW)-> SBC --(SIP)-> Egress Peer, with PSP setting as "transcode only" and RTCP enabled, SBC does not send RTCP packets towards egress.

Root Cause: Due to changes made for feature SBX-6366, SBC does not mark XRES resource as duplex and marks it as receive only. And hence SBC does not send RTCP towards egress.

Steps to Replicate:

1. Reproduce the problem in following call flow:
   Ingress Peer -- SIP -- GSX -- GW2GW -- SBC -- SIP -- Egress Peer
   This transcode only call and RTCP is enabled.
   Result: No RTCP sent by SBC to egress .
2. Verify the issue by applying SamP with GWFE change but not change in ScmP. ( just debugging logs )
   Same setup.
   RTCP traffic was sent from SBC to egress.

Platform/Feature: SBC

The SRV query is not sent to the DNS server when porting the SBX-86420 fix to 6.2 and 7.2 code branch.

Impact: In this case, even when the FQDNPort is zero, the SIPSG/SIPS port is incremented by 1 so the FQDN port is set 1. Due to this issue, the SRV query is not sent to the DNS server.

Root Cause: When the TLS tranport is selected, the SBC is trying to increment the FQDN port by 1. In this case, even when the FQDNPort is zero, the SIPSG/SIPS port is incremented by 1 so the FQDN port is set 1. Due to this issue, the SRV query is not sent to the DNS server.

Steps to Replicate:

Procedure:

1. Send an INVITE with TGRP parameters in R-URI.
2. The SBC sends TGRP information to the PSX.
3. The PSX does TGRP based routing and sends the route.
4. The SBC will send a SRV query to the DNS to resolve port and ip details when egress peer is FQDN.

Observation: The SBC does not send SRV query to the DNS but sends 'a' query.

Expected: The SBC will send a SRV query to DNS to fetch port and ip details and establish TLS connection. with peer.

NOTE: The same scenario works fine when the egress transport preference is UDP or TCP.

Platform/Feature: SBC

The Backup/Restore file cannot be downloaded from the EMA if the file name contains a dot (.).

Impact: The Backup/Restore file cannot be downloaded from EMA if the file name contains a dot (.)

Root Cause: The issue came from the downloadSavedConfig block making an API call while running the SBC and running on the EMS at the same time.

Steps to Replicate:

1. Login into the EMA.
2. Navigate to Administration -> System Administration -> Backup/Restore.
3. Download the Backup file.

Platform/Feature: SBC: EMA

Caller eSBC cancels the call after 180: 504 to ingress, CANCEL to egress.

Impact: Late media convert call with DLRBT is not working.

Root Cause: Bad resource activation.

Steps to Replicate: Setup a late media convert call with DLRBT enabled.

Platform/Feature: SBC

The SBC IgnoreTransparency cannot be set on the EMA V6,7.2 and 8+.

Impact: The SBC IgnoreTransparency cannot be set on the EMA V6,7.2 and 8+.

Root Cause: There was no check if the "not" is applied to complete expression or not.

Steps to Replicate:

1. Log on the EMA.
2. Navigate to All-> profile-> services-> Transparency profile-> SIP Header
3. Select transparency profile.
4. Click on New Sip Header.

After that, the "Ignore Transparency " field can be seen.

Platform/Feature: SBC

Disabling the media lockdown does not suppress media lockdown re-INVITE when the SRTP is enabled.

Impact: If the SBC offers crypto, and peer does not reply with crypto in the answer, a re-INVITE is sent to lockdown the crypto attribute (no crypto ). If NAT is enabled, one second media drops while re-learning for the new re-INVITE is happening. For non-NAT cases, nothing will be observable except for a signaling change.

Root Cause: The issue was the SBC's original behavior.

Steps to Replicate:

1. Setup the SBC so that it sends crypto in offer.
2. In answer from the peer - do not send any crypto attribute.

Without fix, the SBC would send yet another re-INVITE if fallback to the unencrypted is allowed. With a fix, this extra re-INVITE will be suppressed.

Platform/Feature: SBC

A SIP to SIP call no ring back tone passed into the ingress when the PEM header is enabled on the egress endpoint.

Impact: There is no RBT when the PEM header is enabled, splitting 18x into alerting and the progress flag is enabled.

Root Cause: This flow was never tested with a flag or split 18x into alerting and progress.

Steps to Replicate: Setup a call with PEM enabled on the egress and with the split 18x flag enabled.

Platform/Feature: SBC

The SMM writeCdr was failing to write to the ATTEMPT CDR when acting upon the 300 Multiple Choice.

Impact: The SBC is failing to write the SMM fields in the ATTEMPT CDR when acting upon 300 Multiple Choice.

Root Cause: The code was missing to handle the SMM information for a Redirect Scenario in the CDR.

Steps to Replicate: Use the SMM to write in the cdrField1.

The information in the SMM will be correctly written, but will not transfer to the ATTEMPT log.

Platform/Feature: SBC: CDR, SIP

Unable to change the Source Port to any on the EMA, IPAccessControlList screen.

Impact: Unable to change the Source Port to any on the EMA, IPAccessControlList screen.

Root Cause: The source port attribute is validated as an integer instead of an alphanumeric.

Steps to Replicate:

1. Bring up the SBC in 7.2.2R0.
2. Log on to EMA.
3. Select 'ALL' -> 'Address Context' -> 'IP Access ControlList' -> 'Rule' -> 'default'
4. SourcePort is not changing from integer to 'any' in EMA.
5. It working fine in CLI, SourcePort number is changing from integer to 'any' and 'any' to integer.

Platform/Feature: SBC

The ImPr cored when the SBC was running a call load.

Impact: The SBC ImProcess cored when the LI server became unavailable.

Root Cause: When the LI server becomes unavailable and a large number of packets are queued up for that server, the ImProcess takes more than 10 seconds to clean up all those packets, and the process core dumps.

Steps to Replicate:

1. Establish a large number of LI calls.
2. Bring the LI server down.
3. Ensure that the ImProcess does not core dump.

Platform/Feature: SBC

Portfix SBX-96834: Asymmetric PRACK Interworking was not working as described.

Impact: Whenever any codec entry is deleted from codec list in the PSP and in the PSX, it rearranges the codec list immediately. There will not be any empty codec entry in the list.

The same issue is in the ERE, so it can be treated as a bug in the ERE.

Root Cause: When any CodecEntry is deleted, it is not rearranging the CodecEntry, which causes a NULL value in that place.

Steps to Replicate:

1. Configure the CodecEntry1 ,CodecEntry2 to CodecEntry12
2. Delete any CodecEntry.

Result: The call will be successful.

Platform/Feature: SBC: ERE

Portfix SBX-96706: Multiple switch overs causes non 5060 sipSigPorts to become inactive.

Impact: When user configured >= 2 SIP SIG ports are configured with same IP address but different port numbers, they are using the same LIF group that contained 1 LIF.

Pkt down triggered a switchover and it stayed down for an extended time. After the pkt up, a second switchover occurred, then only one SIG port became inactive. The other SIG ports were stuck in OOS.

Root Cause: Since the pkt port was down when new standby node came back online, the SIP SIG ports were restored while the LIF was OOS. The address registrations failed as a result. After the SIPCM has reached max number of retries, the LADDRs of the SIG ports, except the first one, were deleted in the NRS context.

Later when pkt port came back up, the NRS brought LIF back in service and registered the only one signaling address saved in the NRS context.

Steps to Replicate:

1. Configure the 2 VLANs on YF or BF pkt2.
2. Configure the 4 SSPs on the first VLAN interface; 4 SSPs on the second VLAN interface. 4 SSPs use udp/tcp port numbers 5060, 5160, 5260, and 5360 with the same IP address.
3. Run the sbxstop command.
4. Unplug the packet ports - YF pkt2.
5. Run the sbxstart command
6. Display the SSPs on VLAN interfaces.

Platform/Feature: SBC

The code is modified to only delete the LADDR before reaching the max number of retries. And restored the pendingNrsReq flag properly when the address registration failed.

The SBC Memory shows High alerts.

Impact: When Local Ring back tone is configured on the SBC and egress endpoint sends 183 Session Progress with SDP followed by 180 Ringing, SCM Process does not free up memory allocated even after call is completed. Without a fix, SCM Process will leak memory.

Root Cause: When Local Ring back tone is configured and egress endpoint sends 183 Session Progress with an SDP followed by 180 Ringing, SCM Process does not free up the media session descriptor structure.

Steps to Replicate: Run call load with a Local Ring back tone configured and monitor the virtual memory usage of ScmProcess. With a fix, virtual memory of SCM Process must not be high after all the calls have been disconnected.

Platform/Feature: SBC

The SBC releasing the call with 504 when the DLRB and Downstream Forking are enabled.

Impact: The SBC releasing the call with 504 when the DLRB and Downstream Forking are enabled.

Root Cause: The Race condition was not handled properly. When the first 180 without SDP is received, the forking list was updated and the message stored. When the 18x with SDP is received a second time, the forking list must be updated and store the new received 18x.

Steps to Replicate:

Send RTP before sending 180 Ringing.

Without fix - call is not successful and with fix call is successful.

Platform/Feature: SBC

MS Teams call flow for hold/resume then transfer causes a SCM crash.

Impact: When the music on hold is used in the deployment and a call is put on hold/resumed and then transferred, causing the SBC to coredump in the SCM process.

Root Cause: The SCM process was de-referencing a null pointer.

Steps to Replicate: The music on hold is used in the deployment and a call is put on hold/resumed and then transferred.

Platform/Feature: SBC: MS Teams

Losing a call from MS Teams, and audio loss for 30 seconds during a switchover.

Impact: If there is an SBC switch-over after the call is established, there can be a delay (e.g. 30 seconds) when re-establishing the media from PSTN to the MS Teams direction.

Root Cause: The stored SSN value does not get updated before the SBC switch-over occurs, and it causes the SSN jump backwards after switch-over, which causes the one way audio issue for sometime until the SSN value increments pass the previously sent value.

Steps to Replicate: MS Teams to PSTN call flow with the DLRBT enabled on a software SBC. Perform a switch-over after the LRBT is played and check there is no one way audio issue.

Platform/Feature: SBC: MS Teams

The DFW1-CASBC-02 Box A had a SCMP coredump.

Impact: The SBC cored when accessing Box A, switching over to Box B instead.

Root Cause: Enabling the SDP transparency and the directMediaAllow to show a simple 18x response from the peer may cause core due to access from an invalid address.

Steps to Replicate: Disable either the SDP transparency or the directMediaAllow.

Platform/Feature: SBC

There is a possible slow memory leak in SAM process while running GW-GW calls.

Impact: A possible slow memory leak in the SAM process.

Root Cause: The GWFE is leaking a copy of incoming PDU that was queued internally.

Steps to Replicate: This problem is not reproducible.

Platform/Feature: SBC

Portfix SBX-92580: The SIP Domain is missing in FROM header after an upgrade. (Originated in release 7.2.3).

Impact: The DM rule for the FROM URI is not working.

Root Cause: It was introduced in a previous bug fix to treat FROM URI for a specific RewriteIdentity.

Steps to Replicate: Configure PSX for the FROM URI, and on a SIP-SIP call. Verify FROM header is picking up the DM rule from the FROM URI.

Platform/Feature: SBC

The SBC introduces a static in the custom Announcement.

Impact: If the issue is not fixed, the quality of the announcement will be insufficient.

Root Cause: A software bug in the DSP was resetting the first sample of every announcement frame to zero.

Steps to Replicate:

Note: Any call flow that involves using TPAD to play announcement can work correctly.

1. The set-up requires SBC and PSX. A PSX script is implemented which has information about what announcement to play and DTMF digits that need to be entered to switch to the second stage of the call.
2. Client makes a call to SBC. In the first dip SBC plays the announcement configured in the script and waits for DTMF digits to be entered.
3. A route is present in PSX for DTMF digits entered.
4. After entering digits, PSX now goes for second dip for the new digits entered and returns a route to SBC.
5. With this route, SBC calls Egress end point.
6. Monitor the announcement quality played at step #2..

Platform/Feature: SBC

In I-SBC, PKT Port redundancy support is not present in 7.2.2 release.

Impact: SBC Release 7.2.2 is missing PKT Port redundancy support, when it is listed as available.

Root Cause: In I-SBC, PKT Port redundancy support is added in 8.x releases, but not present in the 7.2.2 release.

Steps to Replicate: Configure pkt port redundancy, do port switchover to see the service continuity on PKT ports with redundancy enabled.

Platform/Feature: SBC

Sending an a=inactive to the late media re-INVITE, after a peer put the SBC on hold, does not comply with RFC.

Impact: The SBC running 721R2 is responding with 'a=inactive' instead of 'a=sendrecv' in the 200ok SDP to late media re-invite causing no audio.

Root Cause: Requirement to send a=sendrecv in this scenario was missed.

Steps to Replicate:

Step 1: From logs, generate sipp scripts using the dbgDecode.pl utility provided by Ribbon TAC.
Step 2: Setup 7.2.1 system without fix.
Step 3: Run the call flow to see that the problem is observed.

To Verify:
Step 4: Change ScmProcess with release having the fix.
Step 5: Make call to observe that SBX is sending a=sendrecv in 200 OK.

Platform/Feature: SBC

Portfix SBX-91332: Getting the IP peer current statistics for individual IP peer was not working. The issue is reproduced when multiple IP peers are configured under same zone. (Originated in release 8.1.0).

Impact: Getting the IP peer current statistics for individual IP peer was not working.

Root Cause: The comparison of IP Peer specified in the CLI with the IP Peer statistics list was missing. Due to this issue, more than one IP Peer is configured under same zone, and the statistics for first IP Peer in the list are always used to get selected.

Steps to Replicate: Multiple IP Peers need to be configured under the same zone to reproduce this issue.

Platform/Feature: SBC

Portfix SBX-90654: A parked call was not working correctly because the NRMA process had incorrectly swapped PSP information on the call legs. (Originated in release 7.2.1).

Impact: The SBC was unable to retrieve a parked call.

Root Cause: This is a new call scenario being implemented for MS Teams interop.

Steps to Replicate: Run a test call in MS teams for call park and retrieve.

Platform/Feature: SBC: MS Teams

Portfix SBX-88122: In scenarios where MS Teams referred the call to another, the SBC started to play a RBT (ring back tone) and if the REFER failed due to the C-party not answering, the media could not be established again between the A and B party. (Originated in release 7.2.1).

Impact: Media is not re-established on A-B call when REFER to C fails.

Root Cause: The media resource used to play the RBT did not get freed up correctly when the REFER failed and this blocked the media flow from A to B being re-established.

Steps to Replicate: Make a call from PSTN to MS Teams, have MS Teams REFER the call to another user. Let the phone ring as C-party but do not answer it.

Platform/Feature: SBC: MS Teams

Portfix SBX-87861: While performing a port switch-over, observed that the SBC active went for reboot and Standby did not takeover the calls. (Originated in release 8.1.0).

Impact: The SBC does not properly put calls on Standby when a switch-over occurs.

Root Cause: A cable pull was resetting calls on the interface, which took more than 5 seconds and exceeded the health check threshold, causing the thread to lock on reset.

Steps to Replicate:

• Bring up setup in port redundancy setup.
• Cable pull packet interface to trigger port switch over.

Platform/Feature: SBC

If there is an SBC switch-over after the call is established, there can be a delay (e.g. 30 seconds) to re-establish the media from the PSTN to MS Teams direction.

Impact: The media may have a delay (e.g 30 seconds) when re-establishing.

Root Cause: The stored SSN value does not get updated before an SBC switch-over occurs, and it causes the SSN to jump backwards after a switch-over and causes the one way audio issue for sometime until the SSN value increments past the previously sent value.

Steps to Replicate: MS Teams to PSTN call flow with DLRBT enabled on a software SBC. Perform a switch-over after the LRBT is played and check there is no one way audio issue.

Platform/Feature: SBC: MS Teams

Portfix SBX-91257: The SBC was playing ring back tone while processing REFER and transferring the call. However, the tone was not heard on the original call leg because MS Teams had put the original call on hold. (Originated in release 7.2.1).

Impact: Calls on hold do not hear the ring back tone, while original calls do.

Root Cause: The code was intentionally not sending re-INVITE messages in this scenario before.

Steps to Replicate: Run any MS Teams transfer call scenario.

Platform/Feature: SBC: MS Teams

The Call Graphs are showing more calls after upgrade.

Impact: Stale calls may be found on the newly upgraded SBC when upgrading from a version older then 6.1.0 to something higher.

Root Cause: As a result of changes that were made to the call ID in 6.1 code, during LSWU any calls that existed prior to the upgrade and were then modified or terminated after the upgrade started will be left in a hung state. The only way to clean up these calls is to use the following commands:

 unhide debug
 request sbx rtm debug command “cleanup <gcid>

Steps to Replicate: N/A

Platform/Feature: SBC

Portfix SBX-91820: The SBC was immediately disconnecting the SRS call after establishing the SIP Rec session with the next available SRS when the initial SRS has responded with a failure 4xx response. (Originated in release 7.2.1).

Impact: The SBC was disconnecting the SRS call.

Root Cause: The SBC, after finding next reachable SRS when the initial one has failed with 4xx, created a new SIP Rec Call Block data matching to new SRS. For the old SIP Rec Call Block, the state machine was invoked with a wrong event and this wrong event in the state machine was deleting the old SIP Rec Call Block along with new one.

Steps to Replicate:

1. Create a SRS Group with three SRS Servers
2. Configure num streams to 2.
3. SBC Tries to send SRS Invite to first two SRS
4. Send 4xx from the first SRS and 2xx from the Second SRS
6. After the 4xx SBC tries to send new INVITE to 3rd SRS
7. Send 2xx From 3rd SRS
8. At this step after ACK towards 3rd SRS, SBC Immediately sends BYE to third SRS

Platform/Feature: SBC

SSREQ server has memory leak, which could soon eat up virtual memory when there is call load via SSREQ client.

Impact: The SSREQserver memory will leak, when there is call load via SSREQ client.

Root Cause: The memory allocated for call data and call trace not being deleted properly, leaving those memory blocks idle forever.

Steps to Replicate:

Without the fix, memory growth can be seen every minute. Ribbon test observed 1 call per 5 second SSREQ traffic, the memory used by SSREQ grew from 0.5% to 10% in less than 30 minutes.

Platform/Feature: SBC

When the SBC sends out re-INVITE messages on a call leg supporting ICE, it can still include a=rtcp:<rtp port + 1> value in SDP that is different to the previously agreed RTP/RTCP mux setup agreed with the remote end.

Impact: MS Team scenario with ICE causes RTCP port with X when RTP is Y and when mux is supported. 

Root Cause: The SBC was not considering the SDP answer from the peer when setting the RTCP port value.

Steps to Replicate:

1. SBX routes the INVITE to egress endpoint via egress TG. INVITE should have valid SDP including -

In SDP audio stream -
RTP and RTCP ICE candidates
a=rtcp-mux
a=rtcp: which has port number of audio rtp+1

2. SBX must send 180 and 200 OK to ingress endpoint and include valid SDP for audio stream.

3. Valid ACK received.

4. SBX routes the re-INVITE to egress endpoint via egress TG. re-INVITE should have valid SDP including -
In SDP audio stream -
RTP ICE candidates (no RTCP as egress has already agreed rtcp-mux)
a=rtcp-mux
a=rtcp: which has same port number as audio rtp (as this is not initial offer for this stream and rtcp-mux has already been agreed)

In SDP video stream -
RTP and RTCP ICE candidates (as this is initial offer for the video stream)
a=rtcp-mux
a=rtcp: which has port number of video rtp+1 (as this is initial offer for the video stream)

5. Call signaling completed and then call cleared.

Platform/Feature: SBC

When a user navigates to a SIP trunk group or DM PM rule creation screen, there is no response from the UI and after some interval of time, "Proxy error" is shown to the user.

Impact: The browser is timed out, resulting in "Proxy error" to the user.

Root Cause: The EMA reads the DM PM Rule, DM PM Sub Rule and DM PM Criteria data from CDB via Netconf interface. With large amount of data, there is a significant delay in rendering the UI. Due to the request, the browser is timed out resulting in "Proxy error" to the user. Copying the TG will take approximately 3 minutes.

Steps to Replicate:

1. Configure more than 25000+ DM PM Criterias and 25000+ DM PM Rules.
2. Navigate to SiP Trunk Group Creation Screen or DM PM Rule creation screen.
3. The create screen does not load and after some time results in Proxy error.

Platform/Feature: SBC

Portfix SBX-91750: Observed a "SamProcess" core dump on an active box while running SIP-GW calls.

Impact: SBX may core if the GW Signaling Port configuration is disabled while the GW Signaling Link is up.

Root Cause: The core is caused by an attempted NULL pointer access.

Steps to Replicate: Disable the GW Signaling Port while the GW Signaling Link is up.

Platform/Feature: SBC

Multiple nodes switched over and caused outage.

Impact: Under certain conditions, the SBX sends out a duplicate OPEN_ACK, causing the receiving GW to crash.

Root Cause: Not reproducible.

Steps to Replicate: Steps are not reproducible.

Platform/Feature: SBC

The service instant messages for "Call_Hold" and "Call_Retrieve" are not generated in some GW-GW scenarios.

Impact: When SIP-SBX-GW-GW-GSX-ISUP call is intercepted, if hold/retrieve is received from either side, the SBC is not sending service instant messages to the LI server.

Root Cause: The SBC is not sending service instant messages to the LI server.

Steps to Replicate:

Setup
SIP---GW(SBX)-----GW(GSX)-------ISUP
Description:
When call HOLD comes from called (egress), GSX does not send service instance to the intercept server.

Steps to Verify:
Ensure the setup above is active.
1. Start the LI server
2. Initiate SIP-ISUP call with HOLD from egress
3. Check LI server logs for service instance msg for hold and retrieve.

Platform/Feature: SBC

Portfix SBX-87727: There was a SNMP-USER-BASED-SM-MIB Namespace Change.

Impact: The EMS cannot configure the SNMP-USER-BASED-SM-MIB through NETCONF.

Root Cause: The SNMP-USER-BASED-SM-MIB is not exposed to NETCONF.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The BRM redundancy messages were filling up the DBG logs.

Impact: The BRM redundancy messages were filling up the DBG logs.

Root Cause: The redundancy messages were debug messages to help debug a resource leaking issue. The messages must be moved to lower level.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

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

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.

Platform/Feature: SBC

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

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.

As a result, the status reporting process wrongly reported a sync in progress.

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)

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.

Platform/Feature: SBC

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

Platform/Feature: SBC: DSP

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

Platform/Feature: SBC

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

Platform/Feature: SBC

The SBC reads the end of a memory block while processing DTLS signaling. This can result in invalid accessing of memory.

Platform/Feature: SBC

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

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

Platform/Feature: SBC: CDR

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.

Platform/Feature: SBC: SIP

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.

Platform/Feature: SBC: Application

Transport is not correctly set while the SBC is sending an Authorization request.

Platform/Feature: SBC

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

The SBC's ability to handle defragmented packets will deteriorate. The NO DEFRAG MATCH count in "show table system networkProcessorStatistics defragStatistics" increments rapidly. If the PSX responses are large and the IP packets are fragmented, you may see the SBC retry multiple times due to reassembly failures resulting in packet drops. 

Platform/Feature: SBC

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

Platform/Feature: SBC

In the AWS SBC, ssh keys stored in confd database are lost during the upgrade to 07.xx.xx.

Platform/Feature: SBC

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

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.

Platform/Feature: SBC: SIP

IPTABLES rules are incorrect on the SWE after an upgrade in the case where non-default addresses were configured for HA ports. If one of the configured HA addresses is the same as the default address, but the other is not, this may prevent the HA peers from communicating.

Platform/Feature: SBC

When online validation only and both online and offline validation sessId and verId are zero in 200OK, SIPS fail to save the peer SDP.

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.

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)

Platform/Feature: SBC

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

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.

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)

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.

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.

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)

Platform/Feature: SBC: DSP

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

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. 

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.

Platform/Feature: SBC

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

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.

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.

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.

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.

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

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.

Platform/Feature: SBC

The logical implementation for the flag CondIncMethInAllow is incorrect. 

Platform/Feature: SBC

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

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

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)

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.

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.

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.

Platform/Feature: SBC

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

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)

Platform/Feature: SBC

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

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

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)

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)

Platform/Feature: SBC

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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)

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)

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

Platform/Feature: SBC: EMA, Security

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

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.

Platform/Feature: SBC

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

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.

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

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

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

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. 

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

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

Platform/Feature: SBC: CLI

Registrations with a syntax error cause an incorrect REG counter.

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

Platform/Feature: SBC

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

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.

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.

Platform/Feature: SBC: Application

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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.

Platform/Feature: SBC

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

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

Platform/Feature: SBC

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

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.

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.

Platform/Feature: SBC

The mgmtRedundancyRole is displaying Unknown instead of active/standby.

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.

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.

Platform/Feature: SBC

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

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

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.

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. 

Platform/Feature: SBC

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

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.

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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. 

Platform/Feature: SBC

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

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.

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.

Platform/Feature: SBC

The SecureNAT does not learn the remote IP address.

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

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.

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.

Platform/Feature: SBC

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

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

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

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

Platform/Feature: SBC

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

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

Platform/Feature: SBC

The radiusSharedSecret may appear in plain text in the logs.

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

Platform/Feature: SBC

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

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.

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

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.

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.

Platform/Feature: SBC

CDR records are broken into multiple syslog messages.

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.

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.

Platform/Feature: SBC

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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.

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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)

 Platform/Feature: SBC

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

Platform/Feature: SBC

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

Platform/Feature: SBC

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

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.

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.

Platform/Feature: SBC

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

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)

Platform/Feature: SBC

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

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

Platform/Feature: SBC: Firmware

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

Platform/Feature: SBC

Apache server is not running.

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.

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.

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.

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.

Platform/Feature: SBC

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

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.

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.

Platform/Feature: SBC

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

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.

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.

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.

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.

Platform/Feature: SBC

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

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

Platform/Feature: SBC

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

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.

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

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.

Platform/Feature: SBC

A call is torn down if the SendOnlyPreferred enabled.

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

Platform/Feature: SBC

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

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

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

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