/
3.3.6.68

3.3.6.68

Feb 14, 2025

What's new in 3.3.6.68

  • SSH connection issues with some recent clients - TB-3619
    • The SSH server has been upgraded to enhance security and ensure compatibility with recent SSH clients.
  • Support RFC 5761 - TB-3692
    • Added support for rtcp-mux (RFC 5761), configurable per profile.
  • Session Version not increasing although SDP has changed - TB-4143
    • The profile parameter “Send 200 with same SDP session version” is now effective only for the initial 200 OK. All further transactions in the SIP dialog (e.g. re-INVITE or UPDATE) are properly incrementing the session version when there is a change in the SDP.
  • "Host reboot is required" may not disappear after a reboot - TB-4474
    • Fixed an issue on UEFI systems that was not properly dismissing the “Host reboot is required to fully activate the firewall" message, even after a reboot.
  • Enhanced SIP re-INVITE forwarding with Replaces header - TB-4995
    • The ProSBC now supports receiving re-INVITE requests containing a Replaces header with inverted from-tag and to-tag. It no longer responds with a 481 Call/Transaction Does Not Exist error in such cases.The ProSBC will forward the re-INVITE with the tags inversion preserved.Please note that some SIP endpoints may not properly handle a request containing a Replaces header.
  • Memory leak detected by internal tools - TB-5249
    • A small memory leak has been addressed in the H.248 stack.
  • The ProSBC cannot detect the IP interfaces after upgrade in some situations - TB-5275
    • The NICs configuration cache (dynamic_nic.json) is now refreshed on every system startup.
  • "Check Linux Packages" returns an error. - TB-5298
    • The “Check Linux Packages” host action now properly list the packages that can be updated.
  • Tracking 26236 - Stability issues in tbsip when under heavy DNS resolution load. - TB-5302
    • Heavy usage of the DNS resolver within the tbsip application could lead to memory corruption and stability issues. This issue was more apparent when the DNS Cache was disabled or with very short expiry.tbsip is now able to handle the described scenario without experiencing stability issues.
  • Tracking 26235 - SIP INFO responses may not be forwarded by the ProSBC - TB-5313
    • Error codes following a SIP INFO request are now properly forwarded to the other peer.
  • No Transport Server Found - TB-5325
    • In some cases, a “No Transport Server Found” error trace could be seen when the SIP requests did not include any transport parameter in its Contact and/or Record-Route headers.The ProSBC now correctly selects the appropriate transport server in these situations.
  • "No Nap Found" error after failed DNS resolution during reconfiguration - TB-5339
    • ProSBC is now more resilient to DNS resolution failures that occur at reconfiguration (HA switchover, configuration modification, etc). If a “No NAP Found” ever arrives, ProSBC will trigger again the DNS resolutions, allowing future SIP messages to be matched to the appropriate “incoming” NAP.
  • Unexpected NAP congestion - TB-5445
    • Resolved an issue where the total number of SIP calls was miscalculated when NAP call limiting was used.