SBC : Session-Agent Choosing For Incoming Calls With Same IP (Doc ID 2878131.1)

Last updated on NOVEMBER 03, 2023

Applies to:

Symptoms

There are 2 session-agents which using same IP. These session-agents have different child-realms and these child-realms working under same parent-realm. According to documentation below ACME SBC should accept that call according to alphanumeric order if the precedence parameter not configured. But when I tested that scenario at our LAB SBC, it gaves 403 Forbidden cause of not choosing a session-agent and our sip-interface allow only session-agent IP.

Changes

The Oracle Communications Session Border Controller associate an incoming call with a Session Agent by using alphanumeric order to determine sorting. If customer have configured multiple Session-Agent with same ip-address and port then they can use the feature parameter called precedence under Session-Agent to over-ride this default behaviour. The attribute precedence provides a user-controlled mechanism to determine order for Session Agents.

However, this precedence feature is only applicable when Session-Agents belong to same realm.

There can be scenarios where customer may have configured several Session-Agent with same ip and different ports belonging to multiple child realms.

Please refer the Cause Section for more detailed explanation where we have used specific examples and an additional option parameter which can be used to provide additional flexibility.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.