Please provide the link for download !
What’s new in 3.3.7.81
-
Unsupported network interfaces might block SBC network links configuration - TB-4486
- Tbrouter now gracefully handles network interfaces with no available driver. Previously, it would exit on startup and retry indefinitely, even when the unsupported interface(s) were not managed by tbrouter.
-
Legacy files from previous major versions are never cleaned up - TB-5270
- A new rule, “Inactive Setup files”, has been added to the host folder cleanup table to remove old log files and dumps from previous major versions. By default, these files are automatically deleted if they are more than 30 days old.
-
Creating a new IUA link is reverting back from Network to User - TB-5280
- Fixed an issue where the “Side” field would revert to User when Network was chosen on Creating New IUA Link or Creating Multiple IUA Links.
-
Increase the list of supported SIP Reason Cause codes - TB-5366
- Added support for the following Reason Codes:
- 428 (Use Identity Header)
- 436 (Bad Identity-Info)
- 437 (Unsupported Certificate)
- 438 (Invalid Identity Header)
- 607 (Unwanted)
- 608 (Rejected)As referenced by RFC 4474, RFC 8197, and RFC 8688.
- Added support for the following Reason Codes:
-
Script dpdk_get_port_config.py fails after reboot - TB-5462
- Removed an outdated system command from a TBRouter script to prevent a rare edge case where IP interfaces could fail after a reboot.
-
TBRouter sporadically produces dump files upon application shutdown - TB-5468
- Improved TBRouter’s memory management to ensure the allocation and deallocation are always compatible.
-
Timeout when bringing up network may block tbrouter on KVM - TB-5515
- Fixed a deadlock when bringing up network interfaces on KVM that was causing tbrouter to restart by itself.
-
Reboot loop after migrating the ProSBC VM to another system - TB-5589
- Removed automatic reboot after the initial recovery web portal, to prevent a reboot loop.Also improved tbrouter reliability.