Acme Packet (MOSC)

MOSC Banner

Wrong routing inside SAG

in Acme Packet (MOSC) 2 commentsAnswered

Hello fellows.

Have you ever seen a routing problem where the SBC routes a call to SA2 from a SIP interface in the realm where SA1 resides? SA2 ignores the INVITE.

It looks like the problem appeared somewhere between SCZ9.2 and SCZ10.0. There were "to-addr" prefixes in the local policy toward that SAG before the upgrade from 9.2 to 10.0, and this misbehavior had never occurred.

After the upgrade, a new prefix was added to the "to-addr" list, and the SBC routes incorrectly only that particular prefix. All others are still routed correclty: either to SA1 or SA2.

The strategy inside the SAG is set to "roundRobin". When sipd selects SA1 for routing, everything works normally. The problem occurs only when SA2 is chosen for routing. Is there a limitation for SAG, that requires all "dest" session-agents to be in the same realm?

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