/
3.3.9.31

3.3.9.31

Jun 23, 2025

What's new in 3.3.9.31

  • Support a digitmap with more than 20 different patterns - TB-1665
    • The number of patterns in a single digit map has been increased from 20 to 40.
  • Tracking 26215 - ISUP does not handle COT indications in some situations - TB-5223
    • A new advanced parameter has been added to the ISUP interface, allowing COT messages received in the IDLE state to be delayed so that the related IAM can be treated in the meantime.→ Please describe which new parameter is in the web portal
  • H.248 Digit Map - Gateway may miss the first DTMF received during announcements - TB-5277
    • Fixed an issue in gateway where DTMF tones sent during an announcement (barge-in) could stop digit capture and notify MGC that a stream completion occurred, rather than capturing the digit and aborting the stream.
  • Improved SIP UPDATE support - TB-5461
    • SIP UPDATE requests containing SDP are now correctly handled by the ProSBC. These UPDATEs are properly forwarded to the peer leg during both the early dialog and active call states, and are fully integrated into the ongoing offer/answer negotiation flow. This ensures more reliable mid-dialog media renegotiation and improves interoperability with SIP endpoints that use UPDATE for session modifications.Furthermore, when the SIP stack parameter “Provisional Response Type” is set to “supported”, reliable 1xx responses are now correctly forwarded with the required 100rel and RSeq headers. This enables proper handling of UPDATE requests during the early dialog phase.
  • 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.
  • H.248 announcement files may not load properly (metaswann) - TB-5533
    • Due to a timing issue during H.248 initialization, metaswann announcement files could sometimes fail to load properly.This has been resolved, as the validation of the SAS license feature now occur before the announcements are played.
  • H.248 audio gain not applied on TMG - TB-5568
    • The volume control gain configured on a H.248 TDM Termination through metaswtdmc is now applied properly to the Ephemeral Termination (RTP).
  • Large files in "File Db" could cause database backup failures - TB-5592
    • The internal database and its associated tools now support larger database sizes, allowing successful backup operations even with large files under the “File Db”.
  • The "Require: 100rel" header is not always relayed for PRACK - TB-5600
    • Improved handling and propagation of reliable provisional (1xx) SIP responses to ensure proper inclusion of Require: 100rel and RAck headers during forwarding, specifically in scenarios where the SIP parameter “Provisional Response Type” is set to “Supported”.
  • Encryption issues when translating between SRTCP and RTCP - TB-5608
    • Added support for ProSBC to translate packets between encrypted SRTCP and plain RTCP, i.e. when one call leg expects RTCP to be encrypted while the other does not.Note that SRTCP in pass-through mode was not affected by this issue.
  • Failed to create database due to "Validation failed" error - TB-5609
    • Fixed an issue with the database port range query that caused database creation to fail in certain scenarios.This issue affected only ProSBC systems already linked to a Hardware Transcoding unit.
  • Inappropriate SDP may be present in 200 OK responses to BYE - TB-5624
    • The ProSBC no longer include SDP in BYE responses in certain scenarios.
  • New parameters for the SIP Allow header - TB-5628
    • The following SIP methods can now be individually excluded from the Allow header: INFO, NOTIFY, PRACK, REFER, REGISTER, SUBSCRIBE, and UPDATE.These new per-profile parameters have been added under Profile > VOIP > SIP > Allowed SIP methods.
  • Race condition may cause tbrouter to generate crash dumps on shutdown - TB-5631
    • Resolved a situation where dumps could be generated during TBRouter shutdown.
  • Prevent H.248 call failures due to timeouts while waiting for join completion - TB-5662
    • In certain scenarios, the timing between handling H.248 parallel transactions and allocating the required resources for them could cause timeouts while waiting for those allocations to complete.
  • A “No Transport Server Found” error may be seen in some situations - TB-5699
    • In some cases, a “No Transport Server Found” error trace could be seen when the SIP response 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.
  • Better handling of errors encountered during tbrouter initialization - TB-5706
    • A new error banner is now displayed in the Web Portal when a critical error occurs during tbrouter initialization – for example, when the system requires more memory.
  • Upgrading a ProSBC from version 2.x to 3.3 may fail - TB-5713
    • Importing or upgrading a database from an older ProSBC 2.x system configured with hardware transcoding now works correctly.
  • One-way audio with early-media SRTP - TB-5716
    • SRTP crypto keys are now correctly advertized during early-media negotiation.
  • toolpack_engine may crash during CallBridgingGetFilteredPeerSdp - TB-5738
    • Improved behavior when the Profile SDP description doesn’t have any media codecs in its list and the profile requires to combine and reorder the Profile SDP with a received SDP.
  • "Failed to find NAP" log messages may affect performance - TB-5742
    • The log level of the "Failed to find NAP" messages has been adjusted to prevent them from affecting system performance.
  • Missing documentation on invalid SDP configurations without audio codecs - TB-5772
    • A new warning has been added on configuration validation to flag conflicting SDP combinations.Tooltips for “allow other codecs” and “use sender codec order” have also been updated.
  • IP Interface Status displays wrong "Avail bandwidth mbps" unit - TB-5801
    • Fixed the “Avail bandwidth” field under IP Interface Status, where 1 Gbps interfaces were incorrectly shown as 1 Kbps. 
  • "Too many terminations" error may occur during H.248 configuration - TB-5826
    • The “Maximum Number of TDM Terminations” configuration parameter for H.248 has been removed. The value is now calculated dynamically.In the rare case where the calculated maximum exceeds the Tmedia supported limit, an error message will be displayed during configuration validation or activation.
  • Add support for bulk addition of CAS NAPs in the H.248 configuration - TB-5896
    • Multiple CAS NAPs can now be added at once in the H.248 configuration, enabling a more efficient configuration for GR-303 groups.