Wrong TCP/SYN Messages Sent In SIP Over TCP Call
Last updated on MAY 26, 2017
Applies to:Net-Net OS - Version S-Cz7.1.2 to S-Cz7.4.0 [Release S-Cz7.0]
Information in this document applies to any platform.
In a number of calls, it was observed that after a standard call setup, from one side of the Session Border Controller (SBC), a SIP/BYE is received. On the other side (where TCP transport is used), the SBC sends a TCP/SYN on a wrong port (it attempts to create a new socket towards the endpoint using as destination port the TCP port used is previous messages). This, of course fails as this new TCP/SYN is not accepted. The effect is that BYE is not forwarded.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms