3.3.14.100

What's new in 3.3.14.100

• Missing Ringback Tone on caller side in IMS call flows - TB-5469
  
  

  • The "Remap 180 with SDP to 183 with SDP" profile parameter was converting all 180 responses to 183, regardless of whether the 180 carried SDP. The parameter now only converts 180 responses that actually contain SDP.

• Audio prompt file list in Test Call does not show files from subdirectories - TB-5591
  
  

  • Fixed an issue in the Web Portal where the audio file selector in the Gateway Test Call page did not show audio files stored in subdirectories. The selector has been replaced with an autocomplete search field. The Audio Prompts page now lists files from subdirectories with pagination.

• New option to disable H.248 MGC watchdog restart - TB-5821
  
  

  • Added a new MGC Watchdog Enabled option in the H.248 configuration (Web Portal > Timers section). When enabled (default), the gateway automatically restarts if no MGC communication is received for 60 seconds. When disabled, the gateway remains running regardless of MGC connectivity.

• 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.

• Web Portal log files lack automatic log rotation - TB-6325
  
  

  • Web Portal log files are now automatically rotated daily when they exceed 10 MB, with up to 31 days of compressed history retained. Previously, log files could grow unbounded and consume all available disk space.

• Routing scripts fail when NAP names contain lowercase characters - TB-6348
  
  

  • Fixed an issue where NAP names containing lowercase characters could cause routing scripts to fail. NAP names are now restricted to uppercase letters, numbers, and underscores. Existing NAP names containing lowercase characters are automatically converted to uppercase upon upgrade.

• ISUP CIC group always displays CICs 1-30 regardless of "Skip timeslot 16 CIC" setting - TB-6361
  
  

  • The ISUP CIC range in the Web Portal now correctly reflects the "Skip timeslot 16 CIC" setting on E1 lines: 1-31 when unchecked (gap numbering) and 1-30 when checked (compact numbering).

• SIP stack does not properly handle multiple Supported headers - TB-6431
  
  

  • Fixed an issue where SIP messages containing multiple Supported headers were not fully parsed, causing only the first header to be recognized. This could affect, for example, SIP session timer negotiation and lead to unexpected call disconnections.

    Additionally, the SIP/Session Timers interop parameter “Support reinvite no role change” was renamed to “Allow call role change on re-INVITE”. The default value is now “enabled” to align with RFC 4028 session timer behavior.

• 100rel present in Supported header when PRACK is disabled in profile - TB-6455
  
  

  • Disabling PRACK via the profile's Allowed SIP Methods now correctly removes 100rel from the Supported header.

• SIP service disruption during 1+1 switchover - TB-6597
  
  

  • Fixed an issue where the SIP stack could fail to activate properly during a 1+1 switchover, disrupting call service until the process recovered.

• SIP registration not retried on failure during system startup - TB-6625
  
  

  • Fixed an issue where SIP REGISTER requests could fail during system startup or when the call control engine was temporarily unavailable, with no automatic retry. Subscribers could remain unregistered until the next refresh cycle. Failed registrations are now automatically retried.

• False "host is not fully synced" warning when validating TMG configuration - TB-6638
  
  

  • Fixed an incorrect warning that appeared when validating a TMG configuration. The warning was a regression introduced in 3.3.13.

• AMR Parameters dropped by engine - TB-6650
  
  

  • Targeted AMR parameters are now supported, meaning the SBC can successfully regenerate SDP transmissions that are sent with these AMR parameters.

• False "Invalid GR303 license" warning at startup before configuration activation - TB-6654
  
  

  • Resolved an incorrect license warning that appeared after a reboot, before the configuration was activated. License validation now correctly reports the status at startup.

• Call drops in late-offer scenarios with "Active codec only" codec selection mode - TB-6760
  
  

  • Fixed an issue where calls using late-offer SDP negotiation could drop when the profile had "Active codec only" codec selection mode enabled. The ProSBC attempted to send a RE-INVITE before completing the initial call setup, causing the call to fail.

• 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.

• 200 OK to INVITE not forwarded to the caller - TB-6776
  
  

  • Fixed an issue where the 200 OK response to an INVITE could be dropped when a RE-INVITE was received before the initial call setup completed. The early RE-INVITE is now rejected with 491 Request Pending until the call is fully established.

• PRACK Request-URI does not reflect Contact header of 183 response during NAT traversal scenario - TB-6790
  
  

  • PRACK now correctly derives its Request-URI from the Contact header in received 18x responses. Previously, it could incorrectly use the Request-URI from the initial INVITE.

• Repeated FQDN resolution loop when building firewall exception rules after startup - TB-6837
  
  

  • Fixed an issue where tboam_app could enter an infinite DNS resolution loop when prefilling firewall entries during the first 60 minutes after startup, causing high resource usage and call processing failures.

• Network packet capture may fail after running consecutive sessions - TB-6847
  
  

  • Fixed an internal buffer management issue that could cause the second network capture to fail when the buffer had been fully utilized during a prior session. Symptoms included the capture file failing to save or the system becoming unresponsive. Also fixed an edge case where certain captured packets could be truncated. Corrected the capture buffer usage percentage and warning indicators displayed in the tbrouter CLI status page, which could show higher usage than actual.

• Unnecessary system reboot warning on fresh install during configuration validation - TB-6862
  
  

  • Fixed a false reboot warning that appeared during the first configuration validation after a fresh install. The system incorrectly detected a configuration change requiring a reboot, even though no prior configuration existed.

• ISDN PRI rejects Progress Indicator #4 in NET5 mode - TB-6872
  
  

  • Fixed an issue where the Tmedia ISDN PRI stack in NET5 mode rejected Progress Indicator value "Call has returned to the ISDN" (0x04) received in PROGRESS messages. The rejection caused a STATUS message, which could lead the remote equipment to clear the call.

• ProSBC does not start on systems with an unusual number of CPU cores - TB-6873
  
  

  • Fixed an issue where tbrouter could fail to initialize network ports on systems with certain CPU core counts (e.g., 3, 5, or 6 cores). Systems with 2, 4, 8, or 16 cores were not affected. Some NIC drivers (e.g., vmxnet3) require a power-of-2 number of rx queues. The network port configuration now correctly adapts to this constraint.

• Excessive "Overlapping Subnets" warnings during activation - TB-6911
  
  

  • The IP interface subnet overlap warning now shows only the first overlap in detail, with a summary count of any additional overlaps. Full details remain available in the logs.

• tbsigtrace incorrectly displays Q.931 signaling data for ISDN - TB-6927
  
  

  • Fixed an issue where the Q.931 hex dump in tbsigtrace showed invalid data instead of the actual signaling content, preventing proper analysis of ISDN captures.

• Unnecessary error messages in logs related to Metaswitch announcement files on systems without the SAS license - TB-6933
  
  

  • Corrected the log level so that missing Metaswitch announcement file messages are logged at informational level when the SAS license is not active. Error-level messages are now only generated when the SAS license is active and files are genuinely missing.

• Packet capture fills up too quickly on busy multi-interface systems - TB-6943
  
  

  • The capture buffer is now redistributed among only the selected interfaces instead of being spread across all of them. A new interface filter option accepts a comma-separated list of interface names (-1 for all).

• tbrouter may fail to start on specific systems - TB-6947
  
  

  • Fixed an issue where tbrouter could fail on systems using 2M hugepages.

• TBSip may fail when an error occurs with REFER, NOTIFY, or SUBSCRIBE - TB-6971
  
  

  • Fixed an issue where TBSip could fail due to an error when processing failed REFER, NOTIFY, or SUBSCRIBE requests under certain timing conditions.