3.3.13.146

What's new in 3.3.13.146

• Licenses section displayed on Tmedia devices - TB-1858
  
  

  • Tmedia devices no longer display the "License Edition" section on the Web Portal's Licenses page. This section only applies to ProSBC.

• NAPs with FQDN may become unreachable due to DNS resolution failure - TB-3509
  
  

  • Fixed an issue where DNS resolution could fail for NAPs configured with FQDN, either during normal lookups or when processing queued queries. Once triggered, the failure persisted until DNS was disabled and re-enabled.

• ProSBC firewall names are incompatible with AWS’s long management port names - TB-3554
  
  

  • Fixed an issue where firewall rule and filter names were limited to 63 characters, which caused configuration failures when using AWS-generated management interface names (e.g., ip-11-22-33-44.ap-southeast-1.compute.internal). The limit has been increased to 255 characters.

• Media thresholds bandwidth should be configurable - TB-5534
  
  

  • Various media thresholds for RTP, RTCP and T.38 can now be configured in the ProSBC Web Portal under Security / SBC / Advanced Parameters.

• Registration contacts missing in tbreport - TB-5578
  
  

  • The sip_registration_contacts.csv file is now properly included in TBReports.

• Microsoft Teams require "a=inactive" direction in SDP for call holding - TB-5669
  
  

  • Added a new parameter to control how the ProSBC forwards SDP direction attributes during call hold/resume. The SBC can now be configured to:

    • Force sendonly (default behavior)

    • Forward as-is

    • Force inactive (new option for Microsoft Teams interoperability)

    The former checkbox has been replaced with a dropdown named Forward SIP hold SDP direction mode in the SIP Profile advanced parameters section of the Web Portal.

• Improve interoperability of SRTP encryption - TB-5743
  
  

  • Improved SRTP interoperability across multiple use-cases:

    • RTP-to-SRTP handling was made more consistent, especially during SIP re-negotiation.

    • For SRTP-to-SRTP scenarios, a new SRTP relay behavior parameter was added, allowing media to either remain in pass-through mode (default) or be re-encrypted. The re-encryption key behavior is controlled by the new SRTP key policy parameter.

    Both parameters are available in the Web Portal under Profile / Media Relay and provide greater control and interoperability for SRTP media handling between call legs.

• Add support of GR-303 in tbsigtrace - TB-5834
  
  

  • Added support for GR-303 signaling trace in tbsigtrace. Logs are consolidated under their GR-303 group:

    • TMC channel signaling (EOC channel not supported yet)

    • Associated CAS signaling

     The -gr303 argument is now supported, and the -db argument is implicit whenever GR-303 tracing is activated.

• Call pickup scenario failed - TB-6133
  
  

  • Improved support for the call pickup feature in the MetaSwitch H.248 environment. TMG is now better able to join terminations required for call pickup.

• H.248 Error=430 on valid TDM terminations - TB-6239
  
  

  • Fixed an issue where valid TDM terminations could return H.248 Error 430 ("Unknown termination ID") to the MGC due to race conditions during restart or resync scenarios. The termination registration logic now queries the H.248 stack directly, eliminating state synchronization issues.

• Gateway application restarting continuously - Failed to create H.248 gateway - TB-6240
  
  

  • Specific scenarios can lead to the gateway application restarting continuously after failing to restore invalid data from the HA repository. Gateway now detects this situation and resets the HA repository before restarting.

• Crash when modifying NAP configuration under call load - TB-6295
  
  

  • Fixed a stability issue where toolpack_engine could crash when disabling or modifying NAPs while calls were active.

• Add support for filtering log_actions with relative times in the API - TB-6302
  
  

  • API requests made to /log_actions can now filter the results using a relative time instead of just absolute times with these new arguments:

    • timestamp_start: Retrieve the actions performed during the last X amount of time, and/or

    • timestamp_stop: Retrieve actions before a certain relative time.

    There are two forms of supported values available:

    • The user can specify a relative time textually (last_hour, last_day, last_week, last_month, last_year) as well as full periods relative to the current time, to get a full window. (last_full_hour, last_full_day, last_full_year last_full_month last_full year)

    • The relative time can also be specified numerically with a negative whole number followed by the wanted unit (h, d, w, m, y)

      • For example, to retrieve the actions for the previous 2 weeks, timestamp_start would be set to -2w.

• Cannot cancel configuration process during installation - TB-6311
  
  

  • Resolved an Internal Server Error generated by the Web Portal during installation when cancel button was used to restart the configuration process.

• SNMP IF-MIB not fully compliant, causing issues with SNMP clients - TB-6313
  
  

  • Fixed the SNMP interface table indexing to comply with RFC 2863. The IF-MIB ifIndex values now use a single integer index instead of the previous two-level hierarchy (board.interface). This change ensures compatibility with standard SNMP clients.

    Applies only to Tmedia gateways.

• T.38 re-INVITE is not always forwarded - TB-6351
  
  

  • Fixed an issue where a T.38 re-INVITE was not forwarded when the initially negotiated audio codec differed between the two call legs.

• Support distinctive ringing on H.248 calls with GR-303/CAS - TB-6382
  
  

  • Add support for distinctive ring patterns received from Metaswitch CFS for GR-303/CAS calls.

    Note that distinctive ringing is not supported for call waiting.

• DTMF through SRTP Event packets fails due to incorrect Ethernet padding - TB-6393
  
  

  • Fixed an issue where Ethernet padding bytes in small RTP Event packets were incorrectly included in SRTP authentication, causing Out-of-Band DTMF to fail. The system now trims padding before SRTP processing.

• The SBC page in Web Portal does not always highlight non-default parameters - TB-6402
  
  

  • The Security / SBC page in ProSBC now correctly displays parameters in orange when they differ from their default values.

• Unable to collect stats from SRTCP during SRTP calls - TB-6403
  
  

  • Statistics from SRTCP packets are now collected under different SRTP interworking situations.

• NAP may not properly register to SIP trunk after configuration changes - TB-6414
  
  

  • Fixed an issue where the ProSBC failed to send REGISTER messages to the SIP trunk after modifying a Transport Server configuration. Internal registration state is now properly cleaned up during reconfiguration, ensuring that new REGISTER transactions use the correct call leg.

• TBRouter out-of-memory messages are not clear enough - TB-6426
  
  

  • Improved the Web Portal out-of-memory banner to distinguish between two situations:

    • The host does not have enough memory, or

    • The host just need a system reboot.

• Increase maximum GR-303 groups to 84 with H.248 - TB-6440
  
  

  • Fixed limitations in H.248 to allow configuration of up to 84 GR-303 groups.

• Gateway crashes during some H.248 call pickup scenarios - TB-6450
  
  

  • Fixed an issue where the gateway application crashed during some H.248 call pickup scenarios due to incorrect thread handling when destroying call resources.

• The Refer-To header should not be altered by the ProSBC - TB-6459
  
  

  • Relayed SIP call transfers has now the correct Refer-To URI from incoming REFER requests. To relay a call transfer, the Call Transfer mode parameter under Profile/Call Transfer Options must be set to Relay.

• Microsoft Teams consultative transfer rejected with a 420 Bad Extension - TB-6463
  
  

  • SIP re-INVITEs for call transfer scenarios are no longer rejected with a 420 Bad Extension due to the Required:Replaces header.

• System instability when handling H.248 subtract messages with specific timing - TB-6474
  
  

  • H.248 subtract messages received for terminations that are already being subtracted due to other messages no longer cause the gateway app to close unexpectedly. Defensive modifications were made to prevent future occurrences.

• Crash when call timeout and reliable provisional response occur simultaneously - TB-6481
  
  

  • Fixed an issue that caused tbsip to crash when one call leg ended with a 500 Internal Server Error and the other leg sent a reliable 183 response at nearly the same time.

• Warning about no Teams license displayed even if license is valid - TB-6485
  
  

  • The warning about Microsoft Teams usage without a license no longer appears at system startup, unless the license is actually missing.

• Manually created network interface configuration files prevent toolpack from managing interfaces - TB-6487
  
  

  • Fixed an issue where manually created ifcfg files (e.g., ifcfg-voip0) for VoIP or control interfaces caused toolpack to mark them as read-only and prevented proper network management. Toolpack now detects externally created configuration files, backs them up to /var/backup/toolpack/ifcfg/, and takes ownership to ensure proper interface management. This applies to voip and ctrl interfaces on ProSBC and Tmedia platforms.

• Configuration validation does not warn about overlapping subnets on different ports - TB-6491
  
  

  • Added detection of overlapping subnets across IP interfaces on different VLANs. The configuration validation/activation now displays a warning when overlapping subnets are detected.

• Inaccurate RTP packet statistics in call reports - TB-6493
  
  

  • Fixed an issue where RTP packet statistics (Rx/Tx counts) were underreported compared to actual traffic. Statistics now accurately reflect captured traffic.

• Wrong CPU usage may be displayed - TB-6496
  
  

  • Fixed an issue where the CPU usage displayed incorrect values (e.g., 42949672%) when configurations mixed voip interfaces with and without Dedicated CPUs.

• Web users cannot change their own password without admin access - TB-6503
  
  

  • Added a new "User Password" page that allows users to change their own password without requiring admin access.

• Repetitive 1+1 system switchovers may cause instability - TB-6526
  
  

  • Fixed an issue where, during multiple switchovers in a short period of time, the standby system could become active while still transitioning to standby, causing the gateway app to reinitialize after 45 seconds.

• Calls with huge SIP INVITE messages are not always handled in ProSBC - TB-6531
  
  

  • Fixed an issue where incoming calls with long SIP content (such as those received from 3GPP networks) were often ignored. These messages are now processed correctly.

• H.248 gateway may crash when subtracting all terminations at once from a context - TB-6536
  
  

  • Fixed a crash that could occur when using wildcard subtract (Subtract=*) on an H.248 context containing multiple terminations (conferencing). The context is now properly released only after all terminations are fully removed.

• TBSIP may crash when processing chained CNAME DNS answers with identical hostname prefixes - TB-6540
  
  

  • Improved handling of chained CNAME DNS responses, including FQDN(s) based on sip.api.openai.com.

• ProSBC failed to boot after an upgrade on systems with multiple NUMA nodes - TB-6543
  
  

  • Fixed an incorrect estimation of the required hugepage memory on systems with multiple NUMA nodes, which could previously consume all available memory. The ProSBC can now boot properly on such systems.

• Toolpack_engine may not exit cleanly when internal DNS resolver is not present - TB-6564
  
  

  • Toolpack_engine would attempt to perform a DNS resolution while it was in the process of closing. In certain situations this would lead to toolpack_engine crashing instead of closing cleanly.

• TBSip may close unexpectedly when aborting DNS resolutions - TB-6566
  
  

  • Fixed a timing issue that could cause TBSip to unexpectedly close while cancelling ongoing DNS requests. This was more likely to occur on systems running with the DNS cache disabled, using short TTL values, or with many unique FQDNs to be resolved.

• SIP domain ignored when routing calls to multi-domain registered extensions - TB-6569
  
  

  • Fixed an issue where incoming calls to an extension registered on multiple SIP domains were routed without considering the target domain. The system now prioritizes the domain specified in the request when selecting the destination.

• VoIP network interfaces may be missing after a system upgrade - TB-6602
  
  

  • Fixed an issue in the SBC boot process that could abort network interface initialization after a system upgrade. The SBC can now complete hugepages memory setup for tbrouter even if a “No MAC found” message is seen in the logs.

• Upgrade may get stuck after minor upgrades due to outdated tbtoolpack_service - TB-6618
  
  

  • The toolpack_installer now includes tbtoolpack_service in all upgrades (minor and major). Previously, this could cause upgrades to get stuck at "package validation". For upgrades from 3.1 or 3.2 to 3.3: upload the package, reboot, and then proceed with validation and package activation as usual.

• Hole-punch firewall entries can become stale due to incorrect ACL rule matching - TB-6671
  
  

  • Fixed an issue where hole-punch firewall entries were incorrectly matched against ACL rules due to reversed source and destination field comparison. Matched entries had their cleanup timer set to zero instead of the normal timeout, causing them to remain indefinitely. Over time, these stale entries could accumulate, saturate the firewall table, and block new connections.

• Outgoing P-Asserted-Identity incorrectly includes ext parameter from tel URI in sip URI - TB-6728
  
  

  • Fixed an issue where the ext parameter from an incoming tel URI in the P-Asserted-Identity header was incorrectly copied to the outgoing sip URI. When both sip and tel URIs are present in the incoming P-Asserted-Identity, each URI type now preserves its own parameters correctly. Additionally, the display name from the sip URI is now properly forwarded when the tel URI appears first in the header.

• SDP parsing failure when fields contain time-like patterns - TB-6744
  
  

  • Fixed an SDP parsing issue where values ending with time suffixes (e.g., "s" for seconds) were misinterpreted as durations.

• Web users with read-only rights cannot use "Filter" function, route pagination disappears after some time - TB-6764
  
  

  • Read-only users in ProSBC can now use filters to manipulate the contents of the tables in the NAPs and Routes pages.

• ProSBC fails to start on systems with limited RAM and multiple network interfaces - TB-6766
  
  

  • Fixed an issue where tbrouter, following an upgrade, could fail to start on systems with limited RAM (around 8 GB) and multiple network interfaces. The maximum allowed sessions is now calculated more conservatively to allow smaller setups to have more network interfaces.