TMG SIP stack congestion on inbound legs - TB-1662
Fixed a SIP session leak related to SIP MESSAGE and SIP INFO methods. The leak was affecting only SIP over TCP and TLS transport.
Gateway failed to activate configuration with "Too many open files" - TB-2022
Fixed a race condition when multiple External Routing HTTP requests were performed simultaneously.
This anomaly caused the gateway app to restart unexpectedly.
One way RTP after Re-INVITE when using SRTP - TB-2023
SRTP keys are now updated after every 200 or ACK message containing a crypto change during an invite or re-invite.
CDR has incorrect Local SIP IP/Port attributes when a call is retried on another route - TB-2295
CDR attributes LocalSIPIP, RemoteSIPIP, LocalSIPPort, and RemoteSIPPort have now proper values even if the first route fails to connect.
Convert the CIN format from decimal to hexadecimal - TB-2326
The CIN in the exported IRI record for Lawful Interception is now limited to 8 ASCII digits as required by the ETSI specification (ETSI ES 201 671 V3.2.1 – annex D.5)
When there is an SSRC change, it is normal for the SBC to receive overlapping RTP for some time. We increased the consecutive SSRC change threshold on an overlapping RTP stream from 4 to 20 changes in one second.
Unexpected message on TMG-7800: Received Port BW for unknown physical Ethernet port [all ports] - TB-2515
Corrected an anomaly preventing adapters from re-syncing their physical ports during a configuration reload.
Use 5 characters instead of 8 characters in the IRI record's Operator Identifier - TB-2518
For Lawful Interception, the "Network Operator Identifier" in the exported IRI record is now limited to 5 ASCII characters, as defined by the ETSI ES 201 671 specification.The web portal now enforces a maximum of 5 characters for the "Network Operator" field.NOTE: Any existing Lawful Intercept configuration containing a "Network Operator" name longer than 5 characters will be truncated to the rightmost 5 characters in the exported IRI records.
tboamapp application unexpectedly closes when accessing the vlan interface statistics of certain adapters - TB-2526
Added protection in certain scenarios to prevent the tboamapp application from closing unexpectedly.
Delayed offer re-INVITE in No Anchoring scenario. - TB-2596
When in “No Anchoring” mode and the SIP profile option “Send 200 with SDP after invite without SDP” is checked, the ProSBC will now forward any SIP INVITE without SDP to the peer and relay the answer to the originator of the INVITE.When “Send 200 with SDP after invite without SDP” is unchecked, the behavior remains the same: the SIP INVITE without SDP is immediately replied with a 200 OK without being forwarded to the peer.