Acme Packet (MOSC)

MOSC Banner

How to protect a non-TLS connection

edited Apr 5, 2013 2:39PM in Acme Packet (MOSC) 3 commentsAnswered

Hello,

for some special scenarios we want to connect customers via non-TLS using a Layer-2 connection towards our SBC cluster (so unique IP address for IP-PBX and SIP interface on SBC per customer). For each enterprise a Session Agent and dedicated realm wil be configured.

 

  1. Is there a way to protect non-TLS connections for a man-in-the-middle attack?
  2. How can we verify the credentials of the IP-PBX (username/password on soft switch or IP address of IP-PBX) on the ACME SBC when someone else tries to authenticate with these credentials on the core soft switch?
  3. Can we limit this in the realm/session agent configuration?
Tagged:

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