Acme Packet (MOSC)

MOSC Banner

Source Based routing in the SBC

edited Sep 10, 2013 7:15PM in Acme Packet (MOSC) 5 commentsAnswered

Hello everybody,

 

I'd like to know if any of you guys have encountered something like I am working on right now:

 

The scenario is the following:

 

Session Agent (Ingress side) -->SBC--> Several possible next hop session Agents (egress side)

 

I'm applying session constraints (max-inbound-sessions) on the ingress side session agent, so it only can stablish a certain number of calls with the first configured egress side session agent (there a are several egress side SAs configured in a local-policy) before it reaches the constraints defined in the SBC.

 

When the constrains are met in the ingress side session agent, the intended behavior is that, from all the configured egress side session agents, traffic is now sent to another configured egress session agent (another next hop configured in a local policy)

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