Acme Packet (MOSC)

MOSC Banner

Multi-Realm Configuration with Common IP (but different port) + ACL causing issues

in Acme Packet (MOSC) 6 commentsAnswered

Dealing with an interesting problem. I have three internet-facing realms with separate SIP interfaces. These SIP Interfaces, use the same IP address, but have separate TLS ports incremented. Example using a faking public IP: So Realm 1 = 100.100.100.1:5061, Realm 2 = 100.100.100.1:5063, and Realm 3 = 100.100.100.1:5065

I also have a range of session agents that are assigned to each of the realms. The session agents communicate to each of the realms on the specific ports.

All of this works well. Until I start applying Access Control Lists. Assuming none exist, unfettered access to the Oracle SBC is anticipated. However, once I start applying ACLs to the specific realms, it has impacts on session agents on the other. So, agent for realm 2 goes out of service when I applied an ACL to Realm 1. It appears to me that the SIP interface for realm2 locked it on realm 1 ingress path. As soon as realm 1 ACL was applied, and it didnt include realm 2 session agent, it dies.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center