TCP Bearer Conditions
The following conditions are applicable to the Oracle® Enterprise Session Border Controller’s support of RFC 4145.
- The Oracle® Enterprise Session Border Controller can not provide media-over-TCP for HNT scenarios (endpoints behind a NAT).
- When media is released into the network, the TCP packets do not traverse the Oracle® Enterprise Session Border Controller because nNo TCP bearer connection is created.
- The Oracle® Enterprise Session Border Controller does not inspect the setup and connection attributes in the SDP message since the TCP packets transparently pass through the Oracle® Enterprise Session Border Controller. These SDP attributes are forwarded to the other endpoint. It is the other endpoint's responsibility to act accordingly.
-
After the
Oracle® Enterprise Session Border Controllerreceives a SYN packet, it acts as a pure pass through for that TCP connection and ignores all further TCP handshake messages including FIN and RST. The flow will only be torn down in the following instances:
-
The TCP initial guard timer, TCP subsequent guard timer, or the TCP flow time limit timer expire for that flow.
-
The whole SIP session is torn down.
-