3.1.144.11

What's new in 3.1.144.11

• tbsip unable to use TCP or TLS transport servers when SIP strict routing is enabled - TB-2253

  • Since V3.1.129, both TCP and TLS transport had issues when the “Use SIP strict routing” parameter was enabled in the Profile. This is now resolved.

• A non-responding DNS server may cause the SIP service to re-initialize - TB-2975

  • The SIP service on TMG is now more resilient to external DNS server outage. In other words, the toolpack_engine won’t restart anymore because a DNS response takes too long to be received.

• Tracking 26050 - Lawful interception - Call should not terminate when HI3 interface is unavailable - TB-3384

  • Intercepted calls will no longer fail if the NAP for the intercepting agency is down.

• Wrong contact header in the 200 OK of UPDATE message - TB-3453

  • A SIP UPDATE message is no longer replied with the same Contact header as the one received in the request. Its 200 OK response now has the right Contact URI.

• Tracking 24007 - Empty internal file is causing system instability - TB-3476

  • In rare cases, an unprotected write in an internal file was causing system instability. This file is now written atomically.

• Tracking 26072 - TMG 1+1 warning on V.152 VBD enabled - TB-3497

  • The config validation process now properly recognizes the license features on 1+1 standby units.

• A resource leak may cause unexpected restarts of the H.248 service - TB-3525

  • Two small memory leaks have been addressed:When a call audio connection is changed between full duplex and half duplex (SendReceive / ReceiveOnly).

    • We now ensure to modify existing objects rather than adding new ones.

    When an ephemeral termination is given an empty signal list.

    • We now ensure inserted objects are removed afterwards.

• IP conflicts in a 1+1 SBC with Ethernet bonding - TB-3655

  • Fix possible IP conflict when using Ethernet bonding on a 1+1 SBC.