SBC Core 07.02.01R010 Release Notes

Portfix SBX-95710: Development to allow early RTP ICE learning for MS teams in the DLRBT media bypass scenarios.

Impact: In a media bypass call flow with the DLRBT enabled, if the MS Teams client takes a long time to answer the call, then the ICE processing does not complete as the MS Teams client never sends STUN with the useCandidate = 1 because it did not get responses to previous STUN messages in the first ten seconds for the call.

Root Cause: For an outgoing call, the SBC was not enabling ICE learning and was not responding to STUNs until an answer SDP is received.

Steps to Replicate: With MS Teams media bypass and the DLRBT configuration on the SBC, make a call from PSTN to the MS Teams and delay answering the call for 30 seconds.

Platform/Feature: SBC

When the SBC receives the first 18x response for the outgoing call, as well as starting the ring back tone based on the DLRBT, ICE learning is enabled and responds to STUNs on the RTP port.

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

The SBC was unable to handle emergency calls (E911) when ICE is enable.

Impact: When the call limit for ordinary calls is already consumed on a trunk group. A new 911 emergency call on that trunk group does not complete using the emergency call bandwidth if ICE is also configured on the trunk group.

Root Cause: Issue in software was not processing ICE data correctly when call was transitioning from using ordinary bandwidth to using emergency bandwidth.

Steps to Replicate:

With the SBC, the trunk group was configured with ordinary call limit and additional emergency call limit and ICE enabled.
1. Establish as many calls as required routed through the trunk group to consume the ordinary call limit on that trunk group.
2. While the previous calls are active, initiate a new 911 emergency call to be routed through the trunk group and verify the call succeeds.

Platform/Feature: SBC: Media, SIP

Portfix SBX-94580: Missing a svcGrp entry for the TG while a few duplicate entries in the srvcGrpTbl.

Impact: Duplicate entries in the GWSG service group table.

Root Cause: The root problem is that on the create GWSG does not validate the TG name. It only goes through the srvcGrpTbl[] and finds the first empty slot’s index. If the new index != original entry’s index, the NamedInsert() will insert SUCCESS and set the duplicate entry at the new location in the table, otherwise the NamedInsert() will return FAILURE and the duplicated entry will be freed.

On the standby node, when it is coming up, the GWSG restores all GWSG_SRVC_GRP_STR from the CDB. Once the configuration restore is done, the active node will start to sync over all the GWSG_SRVC_GRP_STR, which caused the standby node to have duplicate entries.

Steps to Replicate: Refer to /sonus/sw/Specs/TSBX-94580.txt

Platform/Feature: SBC: GW-GW

Portfix SBX-94389: There was a call transfer to the PSTN, the SBC was sending the RTP/AVP instead of the RTP/SAVP towards Teams in the ReINVITE.

Impact: When the 'Announcement based tones' flag is enabled. Make a call from PSTN - Teams n/w.

After the call connects, an Teams user transfers the call to another Teams user. The SBC sending a Re-INVITE towards MS Teams with the m= line protocol as the RTP/AVP instead of the RTP/SAVP. Due to this issue, Teams is sending 488 call is failed.

Root Cause: After an abort_ann_tone event, the CC not moving to cutthru mode.

Steps to Replicate:

1. 'Announcement based tones' flag is enabled.
2. Make call from PSTN - Teams n/w.
3. After the call connects, Teams user transfers the call to another Teams user.
4. The call will succeed.

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

A call from the MS Teams, and the audio loss for 30 seconds and the switchover.

Impact: The MS Teams to the PSTN call flow with the DLRBT enabled on the SBC. If there is an SBC switch-over after the call is established, there can be a delay (e.g. 30 seconds) in the re-established media from the PSTN to the MS Teams direction.

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

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

Platform/Feature: SBC

Portfix SBX-94539: Calls disconnected with the 132 after a switchover.

Impact: When the XRES uses the altMediaIpAddress was freed unexpectedly in a standby XRM when the LIF is created.

Root Cause: When the standby XRM is notified with the LIF allocate request from NRS, it only receives the LIF's IP address. Any altMediaIpAddress will not be populated until the XRM has replied back to NRS. So when XRM is activating any XRES in the deferred activate list, the activation of XRES using altMediaIpAddress will fail and be freed.

Steps to Replicate: Refer to /sonus/sw/Specs/TSBX-94539.txt

Platform/Feature: SBC: CDR, Redundancy

Portfix SBX-93360: The SBC was sending the INVITE with the SRTP instead of the RTP.

Impact: The SBC is sending SRTP instead of RTP

Root Cause: The intersection of the working PSP and the peer PSP does not take place when the Stream was absent. The SRTP values are never updated.

Steps to Replicate:

1. Create a UAC with RTP.
2. Create two UAS with SRTP param.
3. Send port =0 for hold response.
4. Check if the SBC is misbehaving while sending invite to release hold from far end.

Platform/Feature: SBC: MS Teams

Portfix SBX-87615: The 200 Ok (connect) was never sent to the ingress or the ACK to the egress.

Impact: The call will fail with the customer new script to play tone and the ann after connected.

Root Cause: The issue is that the CC is confused, this is a multiparty call transfer and not telling the ingress to connect the call (send 200OK).

Steps to Replicate: Only at customer site with specific script and setup. The steps cannot be replicated.

Platform/Feature: SBC

When a transfer call to the PSTN is rejected around 9-10 times, the initial call with MS TEAMS gets disconnected.

Impact: The call segment created was not cleared after a REFER-INVITE, even on non-2xx response. The segment is moved to deleted state.

Root Cause: The call segment created was not cleared after a REFER-INVITE, even on non-2xx response. The segment is moved to deleted state, but does not clear it by design.

Steps to Replicate:

1. Make a call from A to B.
2. Transfer from B to C.
3. Reject the transferred call at C.
4. Repeat that for 10 times.
5. Initial call will not fail.

Platform/Feature: SBC: MS Teams

Portfix SBX-92580: The SIP Domain was missing in the FROM header after an upgrade.

Impact: The DM rule for a FROM Uri is not working.

Root Cause: It was introduced by SBX-85711 to treat the FROM Uri specifically for the RewriteIdentity only.

Steps to Replicate: Configure the PSX for the FROM Uri, and use a SIP-SIP call. Verify the FROM header is picking up the DM rule of the FROM Uri.

Platform/Feature: SBC

Portfix SBX-96992: The TLS Call failures observed on the ATL1-CUSBC-05 due to port value set to the 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 route header is received without port in it, the SIPSG was incrementing the port for the TLS. Since there was no port received, the port received is considered as 0. The TLS was incremented to 1. So when incremented, the port becomes 1 and this gets used for sending an INVITE that resulted in calls getting failed.

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

Platform/Feature: SBC

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

The CAC handling is not working with the REFER and INVITE with replaces.

Impact: In the MS Teams call flows, they support the music on hold service by default. MS Teams have implemented “on hold” by sending a REFER to the SBC that the SBC then generates an INVITE out to the MS Teams music server and the B-leg is then released. MS Teams have implemented the “off hold” by sending an INVITE to have the MS Teams phone replace the music on hold server call leg. Run with the CAC enabled in the lab and have call limit set to 10. Every time the SBC gets an INVITE with replaces it reduces the CAC count on the ingress trunk group and then eventually fails.

Root Cause: The root cause is that the Trunk Group and Zone CAC are being performed for call pickup. Since the CAC has already been performed for a call that is being picked up, a double count occurs that causes incorrect CAC failures.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The SBC was not releasing the other leg when the call is disconnected during hold( MOH enabled).

Impact: The SBC is not releasing the other leg when the call is disconnected during hold( MOH enabled).

Root Cause: This is a race condition in CC where the handler for the event ASG_DISC_CMD is not present for the CC state CC_VIRT_ESCR_VDREQ because the call is hung.

Steps to Replicate:

1. Make TEAMS to PSTN call.
2. TEAMS holds the call (MOH).
3. TEAMS disconnect call during MOH.

Platform/Feature: SBC

Portfix SBX-96129: Observed a PesProcess coredump during the TLS reg/call load execution.

Impact: A coredump generated for PesProcess and was observed once the call load started.

Root Cause: The root cause was a strncpy with an incorrect size argument.

static char * CallProcessingElementName(unsigned int elementType, char elementName[])
{
switch (elementType)
{
case CallProcElemType_None:
ACE_OS::strncpy(elementName, "None",ELEMENT_NAME_SIZE);
Break;
…………..
}

This function is called with an elementName that is a 50 byte array and strncpy is used to copy the string “None” to the 50 byte array. With a wrong size of ELEMENT_NAME_SIZE, it is defined as 128.

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

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

When a direct-dial call moves to the call queue, and is subsequently transferred to an agent, the call gets disconnected automatically after 20 seconds as Teams releases the call.

Impact: The call gets disconnected.

Root Cause: A disconnection occurs because the SBC does not acknowledge a message on the egress side. The root cause is due to stuck states in the SBC call control.

Steps to Replicate:

1. PSTN dials CallQ number.

2. TEAMS1 is configured in call queue.

3. TEAMS1 transfers call to TEAMS2.

Platform/Feature: SBC

When a direct dial is put on a call queue, the transfer to the agent fails.

Impact: For PSTN to Teams calls, when Teams is triggering an INVITE with replacements and then performing a subsequent REFER, the SBC is not relaying the REFER-TO information from the REFER message to the subsequent INVITE. This results in the incorrect information being sent back to MS Teams and the call failed.

Root Cause: The SBC was not relaying the REFER-TO information from the REFER message to the subsequent INVITE.

Steps to Replicate: In a MS Teams setup, run a call Q and transfer the scenario where the call originates from the PSTN side.

Platform/Feature: SBC: MS Teams

The code is modified to pass the REFER-TO information from the REFER to the INVITE in this scenario for MS Teams setup.

Portfix SBX-74615: Increase the hardcoded OAFSM timer from the current value of 10 seconds. (Originated in release 8.0.0)

Impact: The SBC has a hardcoded timer of 10 seconds to allow the SIP offer/answer exchanges to be completed. If the offer/answer exchange is not completed in this time then the call is released.

Root Cause: The timer may not allow enough time for some end points to complete their offer/answer processing.

Steps to Replicate: In a late media offer call flow where the INVITE does not contain any SDP, the SBC was sending a SDP in the 200 OK and waiting on ACK from the remote end. The ACK did not arrive back quickly enough and the call was released.

Platform/Feature: SBC

The edit route action is slow to complete.

Impact: The edit route action is slow to complete and fails frequently.

Root Cause: The use of special characters such as # in a destination National field caused the failure in the edit route action.

Steps to Replicate:

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

Platform/Feature: SBC

The code is modified to allow additional special characters to support the Destination National field in Edit route.

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

The SBC generates a RTCP goodbye to ingress after the 200 OK.

Impact: When Downstream forking is enabled and the Early Media Response is set to "last received SDP" - when the call gets answered the resource chain will be re-built and the RTCP BYE will be generated.

Root Cause: Root cause lies in feature completed in a previous release. The feature required that if the ingress peer does not have 100 rel support, and egress gets multiple 18xs, then the transcode is forced even though pass through is possible to support codec change.

Steps to Replicate: Enable Downstream Forking and forking response as anything except the first prov response.

Keep PSP's are setup to perform a transcode only.

Platform/Feature: SBC

The code is modified to address the exact scenario that was presented to us in a previous release.
1. Downstream forking is enabled.
2. Early media behavior - non FIRST PROV RESP.
3. One forking dialogue.
4. No SDP is sent in 2xx if the 18x reliable.

Portfix SBX-86180: PolicyDBSyncStatus data is being removed by the logrotate.

Impact: Policy Data shows a sync in progress.

Root Cause: File paths were being removed by the logrotate. When the new file was created in the writing process, it did not have the correct privileges to be read by a status reporting session, so the status reporting process wrongly reported sync in progress.

Steps to Replicate: On SBC ERE, after nightly logrotate job finishes, the file must not be removed.

Platform/Feature: SBC: Application

Call Transfer call to PSTN gets failed second time, when a MOH is played in the initial call.

Impact: After multiple times on hold and resume, if the first call transfer fails due to reject by transfer target, then the transferee and transferor are reconnected successfully. For any subsequent call transfer, the SBC rejects the call transfer request.

Root Cause: When the first call transfer got failed, the SBC tries to reconnect the original call. Due to this re-connection, the original call is not moving to the stable state. Any call transfer request in such state is rejected by the SBC.

Steps to Replicate:

1.TEAMS to PSTN1 call.
2.TEAMS hold and resume the call.
3.TEAMS transfer call to PSTN2.
4.PSTN2 rejects the call.
5.TEAMS resume the call and transfer again to PSTN2.

Platform/Feature: SBC: MS Teams

No relay of UPDATE with a SDP when the media mode changed and the DRBT is configured.

Impact: When the Downstream Forking and DLRBT is enabled, an UPDATE is received from the ingress are not going out to egress (UPDATE received after the media cut-thru has happened because of receipt of RTP from egress).

Root Cause: The code had been modified in a previous release that when an 18x with the SDP is received from a particular dialog, it is marked as OA_COMPLETE. If it is marked as OA_COMPLETE, the UPDATEs received are sent to the other leg if that other leg is 100rel/PRACK supported. This issue was caused due to some legs not being marked as OA_COMPLETE due to an incomplete implementation.

Steps to Replicate: Set Downstream Forking and DLRBT as enabled.

Platform/Feature: SBC

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

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

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

Steps to Replicate:

1. Log on to the EMA application.
2. Select 'ALL' -> 'Address Context' -> 'IP Access ControlList' -> 'Rule' -> 'default'.
3. Ensure that SourcePort number is changing from integer to 'any' and 'any' to integer.

Platform/Feature: SBC

MS Teams Call Park has an intermittent failure.

Impact: In a Microsoft Teams environment, Microsoft has a bug in the client code that can randomly cause messages to be sent out of sequence. For example, when trying to transfer calls, Microsoft can send REFER and then INVITE with a=inactive afterwards. The out of sequence message processing was causing processing issues on the SBC and the call did not complete.

Root Cause: Microsoft agrees that there message sending is broken and are working on a fix.

Steps to Replicate: Repeatedly run Microsoft Teams Call Park scenarios. The problem is not always reproducible and is possibly dependent on the Microsoft server and location of the associated client.

Platform/Feature: SBC: MS Teams

The code is modified to be more defensive against the out of sequence messaging, such as:
1) Reject the INVITE with 491 if REFER is being processed on a call leg.
2) Reject the REFER if the SBC has an outstanding INVITE waiting to be sent.

When a transfer call is not answered from the PSTN, MS TEAMS client is not able to resume the existing call.

Impact: In a Microsoft Teams call flow where the call gets transferred, the C-party sends back a 180 with no SDP that triggers the SBC to play RBT and then C-party sends a 183 with SDP and finally rejects with 6xx. This results in the SBC internally getting into a bad state. This results in the SBC being unable to resume the call and the call getting released.

Root Cause: The resource management in the SBC was getting confused on the packet service profile for the various call legs, which lead to the call being released.

Steps to Replicate:

1.TEAMS to PSTN1 call.
2.TEAMS transfer call to PSTN2.
3. PSTN2 does not answer the call.
4.TEAMS resume the call and transfer again to PSTN2.

Platform/Feature: SBC: MS Teams

Call failure due to FQDN in request URI.

Impact: When the SBC sends a query for the SRV record to external server and the Peer Domain in reqURI is disabled, the SBC intermittently sends a FQDN in the reqURI of egress INVITE. The correct behavior is to send an IP and address in the reqURI of egress INVITE. Without a fix, the SBC will send a FQDN in reqURI even when a Peer Domain in reqURI is disabled.

Root Cause: The SBC does not use formatted SIP messages when an external query is made for finding an SRV record and when a record is found in cache. The SBC cannot apply setting of "Peer Domain in ReqURI" flag in an egress SIP message.

Steps to Replicate:

Reproduce the issue.

1. Follow the configurations on PSX.
   
   1. Set IP PEER as FQDN abc.com instead of IP address.
   2. Enable "noPortNumber5060" on IPSP [ This is for done for NAPTR, SRV query ].
   3. Disable "Peer Domain in ReqURI " on IPSP.
2. Use External DNS server.
   1. Configure SRV record and A record on external DNS server with different Time To Live values.
3. Run high number of calls.

With a fix, the SBC is sending an IP and Port for all the calls since the Peer Domain in ReqURI is disabled.

Platform/Feature: SBC

SBX-93320 / SBX-89414

Multiple Refer calls are failing in both the ISBC and DSBC.

Impact: When the music on hold is deployed with MS Teams environment and call is put on hold/resumed multiple times, it results in the call being released by the SBX.

Root Cause: The music on hold service requires multiple REFER / INVITE with replace attempts and leads to a race condition where the call control state machine did not get back to a stable state after the call was put on hold. This unstable call led to an internal failure when trying to take the call off hold.

Steps to Replicate: Attempt to put a call on hold and resume; the call may fail after 3 attempts or up to 6 attempts.

Platform/Feature: SBC: MS Teams

The code is modified to allow call control to correctly transition back to a stable state and that the resume handling is processed correctly.

A slow SAM Process memory leak when running GW-GW calls.

Impact: Possible slow memory leak in the SAM process when running GW-GW calls.

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

Steps to Replicate: The steps are not reproducible because the trigger is a race condition that cannot be forced.

Platform/Feature: SBC

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

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

Root Cause: The SCM process was dereferencing a null pointer.

Steps to Replicate: Music on hold is used in the deployment and a call is put on hold/resume and then transferred.

Platform/Feature: SBC: MS Teams

Possible Memory leak in the Sam process.

Impact: The SAM process will leak memory in the case where a De-REGISTER is received and then within less than 30 seconds, another REGISTER in the same AOR is received.

This will only happen if Multiple contacts in the AOR flag is disabled.

Root Cause: The code does not free certain memory blocks.

Steps to Replicate:

1. Multiple contacts per AOR flag will be disabled
2. Do a Register for particular AOR and do a de-register.
3. Within less than 30 secs, re-send the registration for same AOR so that SIPFE selects the same preferred slot which was used for registering the same AOR earlier. By registering multiple users with same time period, leak will be reproduced.

Platform/Feature: SBC

The SBC is releasing the Call with 504 when the DLRBT and Downstream Forking are enabled.

Impact: The SBC releasing the Call with 504 the when DLRBT and Downstream Forking are enabled.

Root Cause: Race condition is not handled properly. When first 180 without the SDP is received, there is an updated forking list and stored the message. On a second time when the 180 without the SDP is received, update the forking list and store the new 180 received.

Steps to Replicate: Send RTP before sending 180 Ringing ( CSeq: 961529 INVITE RSeq: 629928).

Platform/Feature: SBC

SBX-91273

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.

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 doesn't load and after some time results in Proxy error

Platform/Feature: SBC

Instead of CDB, the EMA reads the data for a DM PM Rule, DM PM Sub Rule and DM PM Criteria directly from the Oracle Database, reducing the delay to a larger extent in rendering the UI.

If there is an SBC switch-over after a call is established, there may be a delay (for example, 30 seconds) when re-establishing the media from PSTN to MS Teams direction.

Impact: The stored SSN value does not update before the SBC switch-over occurs.

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

Step of 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

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

Impact: The PKT Port redundancy support is not present in 7.2.2 release.

Root Cause: In the I-SBC, PKT Port redundancy support added in 8.x releases.

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

Platform/Feature: SBC

SBX-91726 / SBX-87861

PortFix SBX-87861: The SWe_NP thread hang was observed on a packet port pull out. (Originated in Release 8.1.0).

Platform/Feature: SBC

The thread health check mechanism is fixed on the port reset.

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.

Platform/Feature: SBC

Portfix SBX-91493: On a CLI port switch over, a packet interface with random connectivity loss is observed for few seconds on other interfaces. (Originated in Release 8.1.0).

Platform/Feature: SBC

In scenarios where MS Teams referred the call to another user, the SBC started to play an RBT (ring back tone) and if the REFER failed due to the C-party not answering, the media is not established again between the A and B party.

Platform/Feature: SBC: MS Teams

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

Platform/Feature: SBC: MS Teams

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

Platform/Feature: SBC

PortFix SBX-90308: When the LRBT is enabled for an ICE call, the egress endpoint responds to initial INVITE with a 183 progress message with SDP parameters followed by a 180 without an SDP and a 200 OK with SDP. Following the local ring back tone, the SBC instigates a re-INVITE to the egress endpoint, which is missing ICE ufrag, password and RTCP candidate line in the SDP. (Originated in Release 7.2.2).

Platform/Feature: SBC: SIP, MS Teams

SBX-91098 / SBX-90673

PortFix SBX-90673: When multiple users registered from the same source IP and if the SBC receives SUBSCRIBE from second user, incorrectly fetches the RCB of first user (The pilot number) and forwards the SIP pdu to the wrong SIPSG slot. The SIPSG is not able to locate the RCB and rejects the SIP message with an 403 error response. (Originated in Release 6.2.5)

Platform/Feature: SBC

SIPFE uses the user name or pilot number (pilot number selected based on user name) while fetching the RCB. If the RCB is found at the SIPFE level, then it forwards the SIP pdu to the correct SIPSG slot.

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

Platform/Feature: SBC

When an SRS does not respond to the SBC's request, and if no redundant SRS is configured, the SBC sends a BYE response towards an SRS without XML. Also, the SBC terminates all the SIPREC calls towards the SRS by sending BYE responses.

Platform/Feature: SBC

The code is modified to invoke the API responsible for building XML body.

The code is modified so that when there is no response from SRS for the Re-Invite, the SBC terminates only the specific SIPREC call that did not receive the response.

SBX-91386 / SBX-88070

Portfix SBX-88070: If a call to the sonusPeerUpload.expect is made and the peer goes down, the user may get stuck waiting for the scp connection, resulting in the application healthcheck timing out after 10 seconds. The timeout causes the application to crash. (Originated in Release 7.2.2)

Platform/Feature: SBC

A timeout for the scp is used in sonusPeerUpload.expect script to ensure that a user does not wait longer than 2 seconds for the scp connection to establish.

SRTP enabled calls in the SWe SBC, causing sporadic NP worker crashes.

Platform/Feature: SBC

The audio becomes one way after there is a call transfer on the SWe when Ring Back is enabled with SRTP towards a MS TEAM. The enabled Ringback with SRTP relays the one way call transfer back to the PSTN behind the SBC. 

Platform/Feature: SBC

Portfix SBX-89877: If the server sends multiple notifications without a record-route before the subscribe is stable, the SBC may core because the free memory being duplicated. (Originated in Release 7.2.2)

Platform/Feature: SBC

Unable to upload a configuration in the SBC Provision Management.

Platform/Feature: SBC: EMA/EMS

Portfix SBX-86427: When large SIP PDU's(4096 B) are sent towards a monitoring server, the SBC cores because of buffer overflow. (Originated in Release 7.2.2)

Platform/Feature: SBC

In the Configuration Script and Template Import page, when you select 'Create Configuration from Template', you choose a Configuration from the table, and select Next. This template form is not getting displayed due to some failure.

Platform/Feature: SBC

SBX-91257 / SBX-90664

Portfix SBX-90664: 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.1R2)

Platform/Feature: SBC/MS Teams

The SBC was unable to retrieve a parked call. The call did not working correctly due to the NRMA process incorrectly swapping PSP information on the call legs. (Originated in Release 7.2.1R2)

Platform/Feature: SBC/MS Teams: SIP

Scm Process cores on receiving notifications from PCRF, which Registration Control Block does not exists. (Originated in Release 5.1.5R0)

Platform/Feature: SBC

NRS task failed healthcheck when there was over 3000 status requests per minute.(Originated in Release 7.2.1R2) 

Platform/Feature: SBC: Application, confd

Portfix SBX-90061: When the SIP trunk group->signaling->s8hrSupport flag is enabled, the SBC requests the PCRF for PLMN ID and waits for response. On getting PLMN ID response (or timeout), the SBC continues the call processing but did not free up all the internal resources causing a memory leak. (Originated in Release 7.2.1R0) 

Platform/Feature: SBC

Portfix SBX-90085: When special character inputs are used for called 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.0R0) 

Platform/Feature: SBC

Portfix SBX-90088: NOTIFY is rejected with 489 Bad Event after a double switchover. (Originated in Release 7.2.0R0)

Platform/Feature: SBC

Portfix SBX-88996: The single character search is an exhaustive search operation and the browser witnesses Timeout Exception and renders a the blank screen to the user. (Originated in Release 6.2.4R0)

Platform/Feature: SBC: EMA

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

Platform/Feature: SBC: EMA, Security

All filters do not display for the tables like Call Detail Status, Call Media Status, Call Resource Detail Status, etc. (Originated in Release 7.2.0R1)

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. (Originated in Release 7.2.0R0)

Platform/Feature: SBC

Portfix SBX-89586: Token load option is not loading values into a template. No action is triggered even after a user clicks on Token load. (Originated in Release 8.0.0R0)

Platform/Feature: SBC

SBX-88882

200 OK of INVITE received immediately after UPDATE/200 OK gets stuck and the call fails. 

Platform/Feature: SBC

SBX-88326

PRACK for locally generated 18x is relayed to other leg. This is because of bNw18xRcvd flag not reset when CallProgressCmd is called.

Platform/Feature: SBC

SBX-87795 / SBX-87053

PortFix SBX-87053 (Originated in Release 8.0.0): Failed to apply ARS procedure on getting 503 (when FQDN and uriPreference configured on Egress side).

Platform/Feature: SBC

SBX-89651 / SBX-87342

PortFix SBX-87342: SIP 503 error occasionally occurs in a test.

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

Platform/Feature: SBC

SBX-89333 / SBX-87140

PortFix SBX-87140 (Originated in Release 7.2.2): First, DNS query was getting initiated through management even if IP was configured.  As default static routes are configured and management gets the preference, the DNS query was initiated through the management interface. 

Secondly, the Patchcheck process core dumped when a truncated DNS response was received from DNS server. The Patchcheck process core dump was happening because of its inability to handle a truncated DNS response. 

Platform/Feature: SBC

SBX-89383 / SBX-86553

PortFix SBX-86553 (Originated in Release 7.2.2): The SBC is not responding for ping request of higher bytes of 2000 using x710 NIC's.

SBX-89383: IP Fragmented Packets on X710 NIC will have issues and will get dropped. Due to this large packets with or without VLAN will be dropped and not handled by the SBC.

Platform/Feature: SBC

SBX-89110

The SCM deadlock core dumps.

Platform/Feature: SBC: Application

SBX-89567

Platform/Feature: SBC

BMC Serial Port skips character of input data, causing command failure.

Platform/Feature: SBC: BMC

When a high number of endpoints are registering and un-registering frequently, the ScmProcess core dumps while deleting the registration control block for registration where the SIP redirecting server sent multiple contacts in a SIP 3xx response.

The SBC system starts and stops a very high number of timers for call and registration functionality to work correctly and assigns a timer ID as an incremented integer value. When the number of timers the SBC has started since startup is more than 4 billion (unsigned int32 bit max value), the next timer ID the SBC assigns is a wrapped value of 1. At this time, if there are any timers in use using a low timer ID, the SBC will fail to start the timer. If the start timer fails for a registration with the redirecting server sending multiple contacts to the SBC, the ScmProcess may core dump while deleting the registration control block.

Platform/Feature: SBC Core: Platform

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

The previous register AOR block was freed. However, the username field was not set to NULL and a subsequent re-registration or refresh reuses the heap memory that was freed for the previous registration. When trying to free the current registration block, double free is detected and core dump occurs.

Platform/Feature: SBC

SBX-88482/SBX-87601/SBX-88477/SBX-85988

PortFix SBX-87601: The SBC is dropping the userpart in the RURI of the outgoing INVITE.

Platform/Feature: SBC

PortFix SBX-88254 (Originated in Release 6.2.3F3): The SBC rejects SUBSCRIBE requests with 403.

Platform/Feature: SBC

PortFix SBX-87944: A blind transfer call occurs due to DLRBT. The internal tone flag on leg B was not reset properly. As a result, leg C fails to cancel the tone. 

Platform/Feature: SBC

PortFix SBX-86593 (Originated in Release 6.2.4): The EMA Template fails to import the configuration when Special Characters are present.

Platform/Feature: SBC

A memory leak occurs when rewriteIdentities is enabled on a SIP trunk group. If a SIP trunk group has rewriteIdentities enabled, there is a case in which memory that was allocated for temporary storage of a toHeader is never freed.

Platform/Feature: SBC

SBX-86783 / SBX-73424

Platform/Feature: SBC: CDR

SBX-86608

Platform/Feature: SBC

Wrt key-salt generation validation is added.

SBX-86790 / SBX-86589

PortFix SBX-86589 (Originated in Release 7.2.2R0): Sip sig port is not responding to ARP if the ARP request comes on an interface which the sip sig port is not bound to.

Platform/Feature: SBC Core: Platform IP/Media Services

SBX-85675

Random Java code writing from Rest interface as the json dependency was not loaded.

Platform/Feature: SBC

SBX-86735 / SBX-86694

PortFix SBX-86694 (Originated in Release 8.0.0R0): Transfer cases failing as E2E PRACK needs to be disabled on transfer Leg, as provisional responses will not be relayed to other leg.

Platform/Feature: SBC

SBX-85676

Reading any file from un-privilege Rest User from REST GET Request is not validated as the curl command was not sanitized.

Platform/Feature: SBC

SBX-85742

Support for In dialogue REFER request when Response is present.

Platform/Feature: SBC

The code is modified in the SIP stack. If the Message type is REFER and PSX Response profile is configured before a response is sent to network, add the Custom Reason Text from the PSX Response Profile and not the default one.

If in the IPSP "Include Reason Header" is enabled, the SBC will Add Q.850 Reason header with the cause code, Reason text of Q.850 Reason Header configured into Response Profile.

When the SBC does not find the route information for incoming call, it rejects it with Error response. In the error response message, Max-Forwards header was being added. 

Platform/Feature: SBC

Issue 1: A 488 was sent because of Nrma Modify Failure when UPDATE followed by 18x without SDP was received. This is caused by Prack pending.

Issue 2: A 491 is issued when UPDATE is received immediately after 18x without SDP. This is again caused by Prack pending.

Platform/Feature: SBC

Issue 1: Added a flag check and OfferAnswer check to avoid this issue.

Issue 2: Added a flag check to avoid this issue.

REFER Relay is not working in S-SBC.

The SBC allows REFER to be Relayed to the egress side in a D-SBC environment. It would reject REFER that should be acted upon if REFER Relay is not enabled.

Platform/Feature: SBC

The SBC does not handle IP fragment timeout properly. When IP fragment timeout occurs, the fragment context is deleted and the per-nif in use count is decremented. There is a problem in the code where it decrements the incorrect nif.

The SBC's ability to handle de-fragmented packets will deteriorate. The NO DEFRAG MATCH count in "show table system networkProcessorStatistics defragStatistics" increments rapidly. If 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

When pcrf is enabled, SCM may core on switchover. 

Platform/Feature: SBC

PortFix SBX-68858: The SBC CDR 'GMT' timestamps jumped forward and backward.

Platform/Feature: SBC: CDR

PortFix SBX-86992 (Originated in Release 6.2.4R0): SCM may core due to memory corruption caused by processing of Global PCDR Info received from Policy Server.

Platform/Feature: SBC

While triggering a recording call towards SRS for a SIPREC Redundancy scenario, the SBC fails to build the XML Metadata Information which failed to trigger the Recording call.

Platform/Feature: SBC

PortFix SBX-63571 (Originated in Release 5.1.6R0): The Active CE may fail to synchronize ("Call/Registration Data" stays in syncInProgress) after LSWU upgrade of Standby CE, when ipPeer pathCheck is used. The RTM process was not able to handle pathCheck messages that may occur during LSWU.

Platform/Feature: SBC: Application

CallFlow is captured properly but the sequence of the packet is out of order.

Platform/Feature: SBC

Non-default addressContext ACLs are not working.

Platform/Feature: SBC

Log packets before and after SMM translations.

Platform/Feature: SBC

NRMA fails to select the AMR codec when restricted mode set is present in Offer and Route PSP during tone play.

Platform/Feature: SBC

The SBC is not printing ingress details in callDetailStatus/callMediaStatus after switchover for REFER flow.

Platform/Feature: SBC

The SBC is not intercepting media packets of one stream post REFER.

Platform/Feature: SBC

This issue occurred as routers respond to the ARP probe request sent by the SBC with a GARP request, and the target MAC in that ARP request is set to a broadcast MAC. The SBC expects the target MAC in the ARP response sent by router to contain the MAC address of the SBC port from which the request was sent. The SBC was not treating this as a valid response, which resulted in reporting standby links as DOWN.

Platform/Feature: SBC

The SBC is not able to send local ACK after REFER when E2E ACK is enabled.

Platform/Feature: SBC

E2E ACK functionality should not kick in after call is transferred as 200 OK response does not need to be relayed to other leg. Code changes are made.

XRM deadlock. Standby keeps restarting.

Platform/Feature: SBC

The issue is fixed by the XRM inserting the xres into the encryption hashtable after state becomes active, and by processing the modify (deactive-reactive) scenario, the hash entry in map should be updated, otherwise it causes the duplicate issue.

The SBC does not honor the expires value from the registrar.

Platform/Feature: SBC

SBX-75934

PortFix SBX-76121: The SBC core dumps if P-Com.Session-info with SIP URI of the format sip:host is received. 

Platform/Feature: SBC CE: SIP

SBX-76571 / SBX-74056

PortFix SBX-74056: Call scenario is inconsistent in the case of a SIP-I/SIP call with Hold on 180.

Platform/Feature: SBC 5000/7000 Series: SIP

Validation code is added to ensure that the SBC does not send out a generic notification with hold in the backward direction until after the call is answered. It is only sent out in the forward direction after the call has routed. Retrieve is also not sent out unless hold has previously been sent out.

SBX-76013 / SBX-75378

PortFix SBX-75378: Code to free a structure is missing from camRecordDestroyOptionalFields. 

Platform/Feature: SBC 5000 Series: Call Control

SBX-76041 / SBX-74899

PortFix SBX-74899: The SBC disconnects calls intermittently. After that, the UAC sends Re-INVITE without any change in SDP, so the SBC responds locally.

Platform/Feature: SBC Core: Application

SBX-76017 / SBX-75618

PortFix SBX-75618: SIPFE found the wrong Reg AOR and route Options to the wrong SG (slot).

Platform/Feature: SBC Core: SIP Access

SBX-76052 / SBX-74160

Platform/Feature: SBC 5000/7000 Series: DSP

SBX-76016 / SBX-75864

The code is modified so that memory is properly freed.

SBX-76012

Platform/Feature: SBC Core: Application

SBX-76062 / SBX-75057

PortFix SBX-75057: SMM Dialog Statefull Variables with Dialog Transparency is not working. 200 OK for Re-INVITE sent, Bye Received and 200 OK is re-transmitted.

Platform/Feature: SBC Core: SIP

SBX-76494 / SBX-76310

PortFix SBX-76310: In downstream forking and 18x without PRACK, the SBC does not relay a 180 response.

Platform/Feature: SBC Core: SIP

The code is modified so that the 180 response is not dropped.

SBX-76492 / SBX-76059

PortFix SBX-76059: NTP security improvements needed.

Platform/Feature: SBC 5000/7000 Series: Security

SBX-72863

TPAD crashed when it was setup for internal (IDP) format but received a mix of RTP and IDP packets. This caused TPAD to delete the buffer pool, and inconsistency resulted in illegal memory access resulting in a crash. 

Platform/Feature: SBC 5000/7000 Series: DSP

The code is modified to not delete the buffer pool because IDP channel is expected to receive only fixed size IDP packets. If it receives RTP packets, it will drop RTP packets but not re-carve buffer pool. 

SBX-76453 / SBX-75458

PortFix SBX-75458: When 180 Ringing is received before completion of UPDATE-200OK during an egress precondition inter-working scenario, an issue is seen.

Platform/Feature: SBC 5000/7000 Series: SIP

SBX-76456

PortFix SBX-76182: Issues occur after SBC7K receives 181 on Egress.

Platform/Feature: SBC 5000/7000 Series: SIP

The Preconditions Update needs to be sent for 18x with SDP, and Ignore 18x needs to be sent without SDP.

SBX-75249

The error "Unable to login to peer shell, IP: 169.254.88.1" was observed after LSWU.

Platform/Feature: SBC SWe: Application

SBX-76097

The new MAC address in the received Gratuitous ARP sent by the next-hop router will update the media packet headers of the existing calls.

The previous SBC behavior was to use the new MAC address from Gratuitous ARP (G-ARP) only if the IP address in G-ARP belonged to the peer. If the peers are reachable via the next-hop router, the existing calls can experience one-way audio when the next hop router’s MAC address changes.

Platform/Feature: SBC Core: Common Sonus Platform Services, Platform IP/Media Services

The code is modified to include processing G-ARP from the next-hop router when the media peers of existing calls are reachable via the next-hop router.

SBX-76851 / SBX-62682

PortFix SBX-62682: Deleting the IP interface while in dryUp action does not work correctly.

Platform/Feature: SBC 5000/7000 Series: CLI, EMA

SBX-76844 / SBX-74460 

PortFix SBX-74460: The SBC releases ACK based on Stack State, while unaware of delayed ACK and Faking from Stack.

Platform/Feature: SBC 5000/7000 Series: Application

SBX-76857 / SBX-76611

PortFix SBX-76611: Standby Subscribe with registration accessed an invalid address, causing a core dump.

Platform/Feature: SBC Core: SIP Applications

SBX-76856 / SBX-74725

PortFix SBX-74725: "Minimize relaying of media changes from other Call Leg All" is suppressing Re-INVITE to pass through codec in REFER scenario.

Platform/Feature: SBC Core: SIP

SBX-76794 / SBX-76119

PortFix SBX-76119: For a SIP to SIP call using GW protocol between 2 SBCs with "Include OTG" selected, the OTG parameter in Egress Invite will contain GW trunk name instead of name of ingress SIP trunk group from ingress GW. 

Platform/Feature: SBC Core: Gw-Gw

SBX-76845 / SBX-71646

PortFix SBX-71646: While sending input data for certificate content, content is encoded and not read by netconf properly.

Platform/Feature: SBC Core: EMA

SBX-76876 / SBX-74280

PortFix SBX-74280: After a user logs out of EMA, some of the http sessions are not cleared, which results in stale http sessions in the heap, causing an out of memory error. 

Platform/Feature: SBC 5000/7000 Series: EMA

SBX-76971 / SBX-75802

PortFix SBX-75802: A Radius account timeout occurs.

Platform/Feature: SBC SWe: Application

PortFix SBX-75086: SCM core dumped due to an attempt to de-reference a NULL pointer. 

Platform/Feature: SBC 5000/7000 Series: Application

SBX-76972 / SBX-67707

PortFix SBX-67707: A swagger interface was exposed.

Platform/Feature: SBC: EMA, Platform, Security

SBX-77014

Servers1 is not created in memusage log during upgrade from 5.1 to 7.1.

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

The SBC adds duplicate Via headers.

Platform/Feature: SBC Core: SIP Applications

PortFix SBX-74608: When the minimize flag is off, and after egress resume on a call on hold takes place, the SBC sends an unnecessary INVITE.

Platform/Feature: SBC Core: SIP

The code is modified to suppress re-INVITE while the call is on hold.

PortFix SBX-74611: When multiple switch over occurs, includeQ850Reason and unrecAction flags configured on custom cpcToSipCauseMapProfile are not honored and instead default values from baseProfile is used. Consequently, mapping between CPC to SIP cause code is incorrect. 

Platform/Feature: SBC Core: SIP

The platformManager has broken logic.

Platform/Feature: SBC Core: ConnexIP OS, Platform

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

PortFix SBX-75076: If the SBC is re-ISOed and then loadConfig is performed, it results in the loss of confd.conf encryption keys. The encrypted fields in CDB then become non-decryptable. If an upgrade is performed in such a scenario from 4xx/5xx to 7.2.x, then it will fail as confd will fail to decrypt the mandatory encrypted fields and so the fields will remain blank in CDB. During startup post upgrade, confd will exit during validation phase as it will find blank for mandatory field.

Platform/Feature: SBC Core: Install/Upgrade(Platform), IPSec

To prevent upgrade failure, upgrade code is introduced, which fills in a dummy value if an empty value fund for mandatory encrypted fields.

SBX-85446

Apache Commons FileUpload package requires security upgrade.

Platform/Feature: SBC

Commons FileUpload package file to the latest version is updated to the latest version.

SBX-85110

The SBC is rejecting EVS Passthrough call for an invalid attribute added in fmtp line.

Platform/Feature: SBC

LSWU failure. Synchronization Failed For DNSC.

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

PortFix SBX-85273: SMMs are not properly displayed in EMA.

Platform/Feature: SBC : EMA

SBX-85455

PortFix SBX-85455:

When the SBC receives an INFO message with content type as media_control + XML and XML body does not contain any tags, ScmProcess core dumps.

Example of an INFO message:

INFO sip:8906661212@10.7.5.110:5060 SIP/2.0 
Via: SIP/2.0/UDP 10.7.20.75:5061;branch=z9hG4bK-7225-1-5 
From: sipp <sip:sipp@10.7.20.75:5061>;tag=1 
To: sut <sip:8906661212@10.7.5.110:5060>;tag=gK00800082 
Call-ID: 1-7225@10.7.20.75 
Cseq: 2 INFO 
Contact: <sip:sipp@10.7.20.75:5061> 
Max-Forwards: 70 
Content-Type: application/media_control+xml 
User-Agent: ENSR3.0.67.5-IS1-RMRG348-RG930-CPI1-CPO777 
Content-Length: 20

X-Header=trying.

Platform/Feature: SBC Core: Memory Management

PortFix SBX-76408: When Lawful Intercept is configured, the SCM process may leak memory. 

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

PortFix SBX-67966: ssreq launched from EMA was blank and was not loading. 

Platform/Feature: SBC 5000/7000 Series: EMA

A platform type check for the SBC is added.

An EMA issue where Subscriber Numbers are in the Surrogate Registration Profile occurs when validation is missing for the Subscriber Numbers field.

Platform/Feature: SBC

PortFix SBX-76903: SMM headerInfo requirement different in EMA and CLI. The SMM entered in CLI will give an error in EMA.

Platform/Feature: SBC Core: EMA

Platform/Feature: SBC 5000/7000 Series: Common Sonus Platform Services

SBX-74066

Platform/Feature: SBC Core: Media

SBX-76915 / SBX-66015

PortFix SBX-66015: G.711 playout buffer sizes were increased in release 6.0 as part of SBX-57507 so that the initial playout delay and jitter minimum occupancy threshold could be set at values up to 200 ms. However, the TPAD playout buffer was not increased in size, so this large setting of initial playout delay can result in a core dump.

Platform/Feature: SBC Core: DSP

An issue occurs when DB backup was restored when backup was taken from the unsupported version.

Platform/Feature: SBC: Common Sonus Platform Services

PortFix SBX-85312:  After call transfer, the media loss detection feature turned OFF as the logic hit the MGSG feature, which accidentally turned the feature OFF.

Platform/Feature: SBC: Media

The code is modified so that if not MGSG, then the feature does not turn OFF.

When HTP all header transparency is set with ignoring some headers related to Privacy, though IPSP Privacy transparency is disabled, we still send those ignored headers transparently. 

Platform/Feature: SBC: SIP, SIP Access

When sipHeader all transparency is enabled in HTP, and Privacy related headers transparency needs to be ignored, then all following headers should be ignored in HTP.

Refer to SBC SIP Transparency Implementation Guide for more information.

PortFix SBX-67707: Swagger interface exposed.

Platform/Feature: SBC: EMA, Platform, Security

PortFix SBX-76611: Standby Subscribe with a registration access invalid address caused a core dump.

Platform/Feature: SBC Core: SIP Applications

The code is modified to validate the address before accessing it.

PortFix SBX-76310: Downstream forking and 18x w/o PRACK, cause the SBC to drop subsequent 180.

Platform/Feature: SBC Core: SIP

The SBC was unable to reach the benchmarking count of 150000 on bluefin setup.

Platform/Feature: SBC Core: Performance

A New configuration flag, sipTcpConnectionAgingState, is introduced to control the Aging timer. 

If sipTcpConnectionAgingState is disabled, then TCP connections are maintained even if they are Idle for more than an hour. 

If sipTcpConnectionAgingState is enabled, then TCP connections are guarded by the Aging Timer and connections are removed if they are found Idle for more than an hour.

PortFix SBX-76978: When the SBC has /var/log mounted on the external cinder volume, /home/sftproot/evlog is missing. This causes EMS statistics collection to fail.

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

PortFix SBX-76861: AIDE service is disabled initially, but can be enabled by user. False positives are reported by AIDE.

Platform/Feature: SBC: Common Sonus Platform Services

Temporarily disable AIDE to avoid false positives. Full implementation to provide user controls will undo this change.

AIDE can be enable by following these steps:

1. Copy /opt/sonus/sbx/scripts/aide.sh to /etc/cron.daily/aide 
Command: 
    cp /opt/sonus/sbx/scripts/aide.sh /etc/cron.daily/aide 
2. Run the aideinit to create baseline 
Command: 
   /usr/sbin/aideinit -c /etc/aide/aide.conf -f -y > /var/log/sonus/hids/aide_init.log

Max-Forwards value is not getting decremented when the rfc7332ValidateMaxForwards flag is enabled for end to end ACK scenario.

Platform/Feature: SBC Core: SIP Applications

PortFix SBX-86003: The SBC includes SDP in subsequent 18x while Update offer is pending. 

Platform/Feature: SBC Core: SIP Applications

PortFix SBX-86094: Late answer Onhold caused mismatch codecs.

Platform/Feature: SBC Core: SIP Applications

Ignore the response from Onhold while there is a pending Offhold about to send out. 

In the case of a DNS crankback, TCB is getting replaced in pstCall and we do not have access to it. In the case of an MRF call application, CCB can be deleted because of an error event.

Platform/Feature: SBC

SBX-85187 / SBX-76066

PortFix SBX-76066: When the RTP monitoring profile is configured for a non-zero monitoring period, NP does not send any notification to the application for IPV6 RTP packets.

Platform/Feature: SBC CE: Application

SBX-76501

Platform/Feature: SBC Core: SIP Access

With the embeddedRegInfoInUserPart flag enabled, the SBC now sends the same Contact's userpart in the request/responses towards the application server which is sent earlier in the REGISTER message.

SBX-85190

The UserPart received in Request URI of INVITE was truncated in the SBC, leading to call failures. 

Platform/Feature: SBC Core: Application

Verstat parameter is sent in the egress INVITE in the PAI header when privacy transparency is enabled in PSX and 'Do not Sent Received value' for verstat param is enabled in the STI Profile.

 Platform/Feature: SBC SWe: SIP

The code is modified to give precedence to the STI profile control and allow modification to the PAI header according to that profile setting. This change in precedence allows the "verstat" parameter to be removed from the PAI header if configured within the STI profile.

NWDL License activation failed and core dumped was observed on standby node.

Platform/Feature: SBC CE: EMS

PortFix SBX-76448: The SBC core dumped if P-Com.Session-info with SIP URI of the format sip:host is received.

The SBC does not handle sip:host URI in P-Com.Session-info.

Platform/Feature: SBC CE: SIP

PortFix SBX-76497: M-SBC #3 in cluster 1 does not report in sync in the rgStatus. It is stuck in a sync state until rebooted.

Platform/Feature: SBC CE: Redundancy

Changes were made to clear node parameters for the node on which a member-failed event is received. Changes were also made to update the current role and service ID for the standby node in case member-failed is received for any other node, in order to avoid the race condition where member-failed and custom event may be received in quick succession due to a very short duration network glitch (< 1second).

After setting the new CLI aggregate policer to unlimited, the bucket size and fill rate are set to 0pkt/s and block all packets.

Platform/Feature: SBC 5000/7000 Series: Security

PortFix SBX-76500: Dead air occurs on the node after network maintenance because the same IP address is assigned to different SBCs.

Platform/Feature: SBC CE: Redundancy

PortFix SBX-76861: AIDE service is temporarily disabled as false alarms are generated.

Platform/Feature: SBC Core: Common Sonus Platform Services

PortFix SBX-74244: ScmP core dumped due to a NULL pointer accessing a service group table entry.

Platform/Feature: SBC SWe: SIP

PortFix SBX-62682: Deleting the IP interface while in dryUp action causes an error.

Platform/Feature: SBC 5000/7000 Series: CLI, EMA, Platform IP/Media Services

The CLI warning is updated to inform the user about possible issues when deleting ipInterface in dryUp mode while active calls are taking place.

PortFix SBX-62917: Configuration restore brings mgmtIntf4 interface to mgmtGroup.

Platform/Feature: SBC 5000/7000 Series: confd

Platform/Feature: SBC Core: Application, SIP

SBX-76495

The IKE process core dumped.

Platform/Feature: SBC CE: Application

SBX-76978

When the SBC has /var/log mounted on the external cinder volume, /home/sftproot/evlog is missing due to EMS stats collection failing.

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

The code is modified to replicate evlog dir on /home/sftproot/evlog, since /home/sftproot is the chroot directory for sftp access. 

SBX-76587

The S-SBC disconnects TCP connection after 60 minutes.

Platform/Feature: SBC Core: SIP-Peering

Update of attributes through the CLI and EMA do not reflect in Visual First Call Setup.

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

The Cloud T-SBC allocates resources for Xcode calls even if the compression ratio is set to 0.

Platform/Feature: SBC SWe, CE: Platform IP/Media Services

2

Some "STOP" records are missing in the CDR viewer.

Platform/Feature: SBC 5000/7000 Series: EMA

SBX-66254

Platform/Feature: SBC CE: Application

A light weight policy dip for RE-INVITE with P-Com.Session-info header to be relayed is triggered (when End to END Re-Invite flag is enabled). 

If the Refer TG is different than the original Egress TG then a PSX DIP is performed if skipRerouteQuerytoPsx is disabled.

If Refer TG is different than the original Egress TG then a PSX DIP is not performed if skipRerouteQuerytoPsx is enabled.

skipRerouteQuerytoPsx can be enabled only on Egress TG.

SBX-67191 / SBX-67938 / SBX-67939

With 1000 CPS and 120K sessions, a 99.999% success rate in the RHOSP setup is not achieved.

Platform/Feature: SBC 5000/7000 Series: Application

SBX-69024

Two cipher suites were added to tlsProfile's supported ciphers.

Platform/Feature: SBC Core: Security, TLS

Two cipher suites were added to tlsProfile:

• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384

The changes were documented in the appropraite guide.

Certain SIP Access call flows fail due to an ARP lookup failure after an upgrade to 6.2.1R1.

Platform/Feature: SBC Core: SIP Access

ICMP Echo Request is used to resolve the ARP failure.

SBX-71637

PortFixSBX-68300: IP fragmented signaling packets received on a signaling port within the media port range are dropped as rogueMedia. Calls utilizing signaling packets that are large enough to be fragmented fail.

Platform/Feature: SBC Core SIP

SBX-71964 / GSX-57791

PortFix SBX-57791: Nature of Address (115) support is missing from ITU SIPROU variant for SIP-I calls.

Platform/Feature: SBC Core: Call Control, SIP

DSCP marking for T.140 Text media - new flag t140Dscp needs to be documented.

Platform/Feature: SBC 5000/7000 Series: SIP

SBX-72359

In the EMA Dashboard PSX Status, Standby needs to be added in a different color.

Platform/Feature: SBC 5000/7000 Series: EMA

A new color is added for Policy Server standby mode.

A figure and note are added to the documentation.

Platform/Feature: SBC SWe: CDR

The code is modified so that the correct egress TG name is logged.

The AMR and AMRWB improved the capacity code. Code is added, but channel density is not increased.

The feature control flag is at IP peer level. Because of this, SIPFE goes for hash lookup to access Advance peer details for every call and the flag sits inside the peer.

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

PortFix SBX-62083: If an incoming call has contact in the FQDN, then ipPeer is missing in the trace for the incoming Invite.

Platform/Feature: SBC Core: SIP

The Cloud I-SBC does not come up with Multiqueue enabled on RHEL 7.5 when multi-queue is enabled on RHEL 7.5. As soon as the instance was spawned with multi-queue in RHEL 7.5, the instance will disconnect automatically.

Platform/Feature: SBC CE: Application

The code is modified so that the instance does not disconnect automatically.

PortFix SBX-73025: The sonusEma stop/start script does not return to prompt as an exit command is missing if the user stops EMA.

Platform/Feature: SBC Core: ConnexIP OS

PortFix SBX-67954: While evaluating a displayWhen condition that involves an instance attribute, if the instance attribute is not set in CDB then the displayWhen condition evaluates as false. As a result, the EMA does not show the Exclude methods value.

Platform/Feature: SBC 7000 Series: EMA

PortFix SBX-69614: In the SIP Adaptor (SMM) Profile, the View CLI script outputs rules in the reverse order.

Platform/Feature: SBC 5000/7000 Series: Platform

Call trace cannot be disabled from EMA as the values entered for the attribute state were not saved properly. 

Platform/Feature: SBC SWe: EMA

PortFix SBX-72973: "Do not include SS in re-Invite" IPSP flag Config on egress but affect on ingress.

Platform/Feature: SBC Core: SIP

The code is modified to check the flag based on Ingress or Egress leg.

SBX-73174

Platform/Feature: SBC Core: CLI

PortFix SBX-73149: SIP-SIP call flow works, but the SBC is still sending PEM to Ingress once it sends INVITE to Egress instead of waiting until Egress media cutthrough is done.

Platform/Feature: SBC Core: SIP

SBX-73360

CDR version for 7.2 needs to be captured in the relevant documents. CAM header fields need to be updated.

Platform/Feature: SBC Core: CDR

PortFix SBX-73040: For a SIP-GW-GW-SIP call flow, when the PSX sends a translated number to Ingress SBC1, the Egress SBC2 sends a translated number to Egress SIP endpoint. This behavior was altered starting with SBC 6.0.

Platform/Feature: SBC Core: Gw-Gw, SIP

The code is modified to ensure that the Egress SBC sends the original called number to the Egress SIP endpoint in the outgoing INVITE.

PortFix SBX-73417: A queued reINVITE, race 491 conditions, and ACK with a different branch parameter value causes call failure. 

Platform/Feature: SBC Core: SIP

PortFix SBX-72776: Based on a coredump analysis, the openSSL stack was automatically clearing sessions resulting in corruption, triggering a coredump. 

Platform/Feature: SBC 7000 Series: Application

SBX-73477 / SBX-73327

PortFix SBX-73327: A small window of race condition for a rare case of digit insertion causes NP to crash.

Platform/Feature: SBC 5000/7000 Series: Platform

PortFix SBX-73573: A dummy sessionDescriptionPtr was created in SIPSG and then passed to NRMA. NRMA uses the dummy sessionDescriptionPtr passed from SIPSG where sRTPAdminState is disabled, causing the SRTP late media call to fail.

Platform/Feature: SBC SWe: Media

PortFix SBX-68591: The SBC reports "Policy Data syncInProgress".

Platform/Feature: SBC 5000/7000 Series: Install/Upgrade (Platform)

The change done by SBX-59731 is reverted as policyDBSyncStatus can have 600 permissions when generated by Oracle.

PortFix SBX-73488: The SBC coredumps when free memory is duplicated for transparency headers.

Platform/Feature: SBC Core: SIP

PortFix SBX-73955: SipFe is not able to find registration, when the From header is missing the userpart, resulting in SipFe being unable to find the correct slot for routing the call.

Platform/Feature: SBC Core: SIP

PortFix SBX-73162: Privacy is handled incorrectly in the outbound INVITE as the SBC sends a restricted userpart in the From header.

Platform/Feature: SBC Core: SIP

PortFixSBX-74073: The SBC gives a response error when itrecievesa generic parameter with IPv6reference value.

Platform/Feature: SBC Core: SIP

PortFix SBX-74234: During split brain recovery, the becoming-standby SBC may send packets out of pkt interfaces after GARPs are sent by the active SBC.

Platform/Feature: SBC 5000/7000 Series: HA

PortFix SBX-73913: Split brain recovery may lead to blacklisted IP peers. In a split-brain scenario when the SBC application is brought down, the cleanup script invoked toggles the pkt ports. When the pkt port goes up, ICMPV6 packets are sent out to the pkt ports. The switch may map the wrong port with the active MAC address and start sending packets to the standby SBC. The packets should not be sent.

Platform/Feature: SBC Core: Application, Platform

PortFix SBX-69137: During IMS-AKA registration, IPSec policy and SA are configured in kernel and during de-registration, they are removed from kernel.

An issue in kernel IPSec code causes memory allocated for IPSec policy to not be freed even though IPSec policy was removed from kernel by application. This causes a memory leak in kernel module for each registration and the memory leak gradually increases as the number of registrations increases. 

Platform/Feature: SBC SWe: IPSec, SIP

PortFix SBX-74127: MemUsage logs are not displayed in EMA.

Platform/Feature: SBC 5000/7000 Series: EMA

The code is modified to add support for Memory Logs.

PortFix SBX-72774:  SBC was not able to convert when a state where ICE learning was completed to a state where ICE was not required on the call flow due to call forking. This lead to no audio after the call was set up. 

Platform/Feature: SBC Core: SIP

PortFix SBX-74387: E2E reINVITE caused the application offer to timeout. If a new offer is the same as a previous SDP, SIPS fails to send out a reINVITE.

Platform/Feature: SBC Core: SIP

PortFix SBX-73433: Call failures occur due to Lif with no available ports.

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

SBX-74375: SCM cored as a result of an attempt to copy from unmapped memory. 
This problem is not predictable - but will only happen if sipSigSrvcGrpRewriteIdentities is configured. 

Platform/Feature: SBC 5000/7000 Series: SIP

The code is modified to prevent copying from unmapped memory.

PortFix SBX-73636: The SBC did not auto-recover after double failure.

In a case where both active and standby SBC processes go down in succession, it can lead to a state where active SBC node may continue to run as standby even if there is no node running in active mode in the redundancy group.

Platform/Feature: SBC CE: Platform

Platform/Feature: SBC Core: Application

PortFix SBX-74514: The SBC (which later becomes standby) sends GARPs after GARPs are sent by the SBC (which stays active) after split brain recovery.

Platform/Feature: SBC 5000/7000 Series: HA

Platform/Feature: SBC 5000/7000 Series: Platform

PortFix SBX-65396: EMS (SBC-Manager) and EMA are out of sync due to missing code for handling and accessing custom perspectives in the SBC. 

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

T38 stack v3.35 from Commetrex has broken v0 fax calls and should be reverted to the previous version.

Platform/Feature: SBC 5000/7000 Series: DSP

PortFix SBX-73374: PRS cored when SBX received a STUN message with a bad UDP header (UDP length field contained an invalid value). 

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

The SBC EMA does not allow uploading token files with the file upload as the token file extension is not supported in the file upload.

Platform/Feature: SBC Core: EMA

The code is modified to allow token files to upload successfully and to load the values from the token file into the Configuration script form.

PortFix SBX-74051: Under a heavy load, while using IPSec AKA TCP feature, the SAM process may coredump due to the code not handling an error condition correctly.

Platform/Feature: SBC SWe: IPSec, SIP

PortFix SBX-67713: When sendRouteUriToPsx is enabled, useRouteSet is set as received, and the SBC receives NOTIFY before 200OK for SUBSCRIBE is received, the SBC sends NOTIFY received from the core side back to the core side instead of relaying it to the access side. 

Platform/Feature: SBC Core: SIP

The M-SBC cannot establish IPSec connections after reboot/respawn during LSWU initiated switchover due to a pre-shared key getting re-encrypted. Encryption keys are not installed to the upgraded instances, due to which the instances are not able to decrypt the pre-shared key.

Platform/Feature: SBC CE: Application

PortFixSBX-72547: GW-GW call fails when a LM Re-INVITE is received with passthrough configuration as the PAM message is not sent to egress gateway.

Platform/Feature: SBC 5000/7000 Series: SIP

The code is modified so that GW-GW calls do not fail. GW1 now sends MCS PAM to GW2 on receiving a Re-INVITE without SDP.

PortFix SBX-75463: After TG delete, the SBC accesses an invalid TG address, causing SCM to coredump.

Platform/Feature: SBC Core: SIP Applications

PortFix SBX-75052: After a switchover, SBC will randomly pick a media IP address on sipTrunkGroups that has mediaIpAddress configured. 

Platform/Feature: SBC SWe: SIP

Platform/Feature: SBC Core: SIP

PortFix SBX-64175: In SIP call forking, there is dead air after 200 OK.

Platform/Feature: SBC 5000/7000 Series: Media Resource Management, Platform IP/Media Service

PortFixSBX-72945: Short Spikes in CPU Utilization of Management Processes triggers resource DRM Congestion Level 3 Alarms.

Platform/Feature: SBC SWe: Platform

PortFix SBX-75073: SIP Recording of a call using SRTP to a SIP Recording Server (SRS) does not work. The SBC generates malformed SRTP packets which do not reach the SRS.

Platform/Feature: SBC SWe, CE: SIP

PortFix SBX-59422: PassThrough call converted to DM after HOLD/UNHOLD resulting in packets getting discarded after unhold.

Platform/Feature: SBC Core: SIP

The SBC EMA does not allow uploading Tokens file with the Fileupload.

Platform/Feature: SBC Core: EMA

The Cloud I-SBC does not come up with Multiqueue enabled on RHEL 7.5.

Platform/Feature: SBC CE: Application

Multi-queue virtio instances support on OpenStack requires below command to be executed on the compute node:

1. audit2allow -a -M attach_queue. 
2. semodule -i attach_queue.pp 
3. Try spawning SWe instance again.

Impact: When using the Microsoft Teams client through the Microsoft Edge browser, there is a compatibly issue in the SIP signaling between the SBC and the Microsoft Edge browser resulting in calls not being successful.

Workaround: Use the Microsoft Teams client in a different browser.

Impact: The timing of messages received from MS Teams can be occasionally different leading to out of sequence handling on the SBC, which causes the call to fail.

Workaround: No workaround available.

MS Teams call flows that try to use call queue capability can fail to complete. 

Platform/Feature: SBC

Impact: The SBC does not include the transport=tls attribute in the contact header of the 200 OK message, sent back in response to the INVITE with replaces from the MS Teams.

Workaround:

Apply the SMM to the output adapter on the Microsoft Teams trunk group similar to the following:

set profiles signaling sipAdaptorProfile TEAMSOUT profileType messageManipulation
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 applyMatchHeader one
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 type message
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message messageTypes response
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message statusCode 200
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header name Contact
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header condition exist
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header hdrInstance all
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 operation regsub
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 headerInfo headerValue
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from type value
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from value "5061;transport=tls>"
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to value Contact
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp string "5061\>"
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp matchInstance all

Impact: Interception of 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 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.

Egress peer sends back two UPDATES messages during call setup. The second UPDATE is rejected with a 488. During the processing of the second UPDATE a 183 without SDP is also sent and forwarded to the ingress with 100rel.

Platform/Feature: SBC Core: Application

Impact 1: 488 because of Nrma Modify Failure when UPDATTE followed by 18x w/o SDP received. This is because of PRACK is pending.

Impact 2: 491 is issued when Update is received immediately after 18x without SDP with E2E Prack. This is again because of PRACK pending.

Workaround 1: Enable E2E Update so that update will be queued when PRACK is pending.

Workaround 2: No workaround available.

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.

Issue 1: 488 occurs because of Nrma Modify Failure when UPDATE followed by 18x w/o SDP received. This is because we try to fake when Prack is pending.

Issue 2: A 491 issue occurs when UPDATE is received immediately after 18x w/o SDP with E2E Prack. This is again because of prack pending.

Platform/Feature: SBC Core: Application

Impact: UPDATES are rejected.

Workaround:

For issue 1: Enable E2E Update so that update will be queued when Prack is pending.

For issue 2: 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 is not received in the incoming INVITE SDP.

Workaround: Disable RTCP flag on Egress PSP.

set profiles media packetServiceProfile PSP_DM_DTLS rtcpOptions rtcp disabled