Acme Packet (MOSC)

MOSC Banner

mid call resiliency feature in ESBC

edited Apr 12, 2019 5:02AM in Acme Packet (MOSC) 1 commentAnswered

Hello,

How should I implement the mid call resiliency feature?

Details:

There are two equivalent SIP peers but only peer#1 is involved in the signaling. But peer#1 is down and the SBC does not use peer#2 as secondary path toward the destination.

The peers cannot operate in HA, they are two distinct SIP proxies with equal feature set.

So what to do?

Is it a missing feature in the ESBC?

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