3.3.12.53

What's new in 3.3.12.53

RTP port range with maximum value of 65535 causes call failures - TB-3212
- Fixed an issue where RTP ports could be assigned outside the configured port range. The system now correctly enforces the configured RTP port range limits.

Calls are routed to NAPs with 0% availability - TB-4910
- The routing logic now excludes Network Access Points (NAPs) with 0% availability from route selection. This prevents the system from attempting to send calls to unavailable NAPs and avoids unnecessary call failures.

SNMP ifOperStatus does not reflect FAILURE alarms on T1/E1 and DS3 interfaces - TB-5248
- Fixed an issue where the SNMP agent reported T1/E1 and DS3 interfaces as operational (up) even when certain FAILURE alarms were present. The ifOperStatus now correctly returns down(2) for all FAILURE-level alarms, including FAILURE_RAI and FAILURE_TS16xxx (E1 only) which previously had no effect on the operational status.

Add "Microsoft Teams Direct Routing" parameter in Web Portal - TB-5491
- Added a “Microsoft Teams Direct Routing” parameter under NAP / Proxy Environment. A license is required to enable this feature. This feature is available as early access for customers evaluating Microsoft Teams Direct Routing integration. It may be subject to changes before full certification.

H.248 CAS configuration should ignore GR-303 signaling channels (TMC and EOC) - TB-5897
- Fixed an issue where GR-303 groups incorrectly included the TMC and EOC signaling channels in H.248 CAS configurations. Users can now specify an H.248 CAS mask of 0xfffffff, and the system will automatically exclude timeslot 12 (TMC) and timeslot 24 (EOC) when required.

Explicit H.248 media descriptors required for Metaswitch CFS interoperability - TB-6042
- The configuration of certain MGCs requires the explicit inclusion of media descriptors for proper function. H.248 transaction replies will now contain both the Local and Remote media descriptors (if the information is present), even when only one has been modified.

Modified configurations do not always have the asterisk (*) prefix - TB-6110
- The configurations dropdown in the Web Portal now consistently displays an asterisk prefix when a config is modified and saved successfully. Note that for background operations, like the "<<" buttons, the asterisk indicator will appear after the next page refresh.

mtp3_linksets missing on Status page with large numbers of MTP3 routes - TB-6161
- Statistic fields are no longer limited to 256 entries, allowing mtp3_linksets to appear correctly in configurations exceeding this limit.

Network capture size should be configurable from the Web Portal - TB-6221
- The total file size for tbrouter network captures can now be configured in Web Portal under Security / SBC.Note that a system reboot is required for a new capture size setting to take effect.

Modification of SBC firewall list sizes should ask for a reboot - TB-6222
- ProSBC now asks for a reboot after modifying firewall list sizes under Security/SBC/Advanced Parameters in the Web Portal.

Unused memory remains allocated after tbrouter initialization - TB-6225
- Fixed an issue where unused hugepages remained allocated after system initialization. The system now releases unused pages after startup, reducing overall memory usage while maintaining performance for high call volumes. Initial memory allocation during startup has been increased from 35% to 50% of available RAM to accommodate this optimization.

Unintuitive negative logic in RTP no-anchoring parameter - TB-6248
- Renamed the "Use RTP no-anchoring" parameter to "Use RTP anchoring" in the ProSBC Web Portal under Profile > VOIP > Media Relay. The logic has been inverted to eliminate the confusing double-negative phrasing of "disabling no-anchoring".

Repeated "UCT transaction request size" warnings may appear in logs - TB-6262
- Increased the default request size to an appropriate value, making the warning less likely to occur. In any case, the warning message has been improved to reduce log verbosity by logging once every 30 minutes instead of continuously.

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).
  - 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 pages slow to load with many routes or call traces - TB-6307
- Fixed a performance issue introduced in v3.3.9.31, where Web Portal pages would load slowly when displaying large lists.

Toolpack applications are not optimized for modern CPUs - TB-6309
- Toolpack applications are now built for the x86-64-v2 micro-architecture baseline, enabling SSE4.2 optimizations supported by virtually all CPUs from the past 15 years.

Lost of connectivity on voip interfaces after initial network configuration - TB-6337
- Fixed an issue in the initial network configuration wizard where connectivity could be lost if no dedicated management interface was present. The voip interfaces are now accessible without requiring a manual reboot.

Error detected in the routing table for <IP>, deleting it - TB-6346
- Fixed an issue where, after rebooting the system following a firmware update or host role reset, some interfaces could repeatedly fail to be destroyed. This resulted in a loss of connectivity on the affected interfaces and continuous tboam_app log messages such as "Error detected in the routing table for <IP>, deleting it".

Add new SIP response codes for early-media stream errors - TB-6352
- Added new SIP response codes for specific early-media stream errors. The following conditions are no longer reported under the generic “201 - Toolpack resource error” but now have distinct profile cause mappings:
  - 227 - Toolpack excessive payload type changes
  - 228 - Toolpack excessive IP port changes
  - 229 - Toolpack excessive SSRC changes
  These errors can now be mapped to different SIP response codes when the call is in the early-media state.

ProSBC creates invalid PAI header from two valid PAI headers - TB-6372
- Fixed an issue where the ProSBC created an invalid PAI header when both SIP and TEL URIs were present. The ProSBC no longer assumes the first PAI header is a SIP URI, and now correctly supports a TEL URI as the first value.

GR-303 terminations fail to create properly on H.248 gateways - TB-6381
- Fixed an issue where GR-303 terminations could not be created reliably on H.248 gateways. The system now properly handles GR-303 termination creation during system starts and configuration changes, including scenarios with multiple GR-303 groups.