Acme Packet (MOSC)

MOSC Banner

How to force SBC to really reuse established TLS connection?

in Acme Packet (MOSC) 12 commentsAnswered

Hello.

I faced a problem in TLS: a terminal registers from its port 1.2.3.4:48630 on SBC's port 10.11.12.13:5061. This connection is stable and operational for incoming calls (INVITE from terminal towards SBC). In case of outgoing call (from SBC towards terminal) SBC tries to establish new TLS with dst.IP and port, which are already in use on terminal side. In example below you can see, that SBC has found out the existing established TCPS socket 1.2.3.4:48630 <> 10.11.12.13:5061 , but has not used it for the outgoing call.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center