Acme Packet (MOSC)

MOSC Banner

How to force sipd to check local-policy additionally to reg-cache

in Acme Packet (MOSC) 6 commentsAnswered

Hello community.

A customer wants to configure an alternative routing rule for a surrogate-agent: surrogate-agent is registered with number +0123456 . A session-agent "SA" is configured as "customer-next-hop". By default logic, when SBC receives incoming INVITE from the Core, it performs the reg-cache lookup, finds the called number +0123456 and forwards the INVITE to the customer-next-hop "SA". In cases when "SA" becomes out-of-service, Customer wants SBC to forward the INVITE to alternative session-group1 and session-group2 (if SAG1 also fails). The only solution that comes into my mind is an additional local-policy rule

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