Acme Packet (MOSC)

MOSC Banner

routing using nested realms (AP1100)

in Acme Packet (MOSC) 3 commentsAnswered

Hi,

We are testing a new service and we have several routing problems, i'll try to explain the design that the provider implement.

We have a father realm = A, and several nested realms, B and C (configuring in both of them the field parent realm as A)

Only exists a SIP-interface in A, and two session agents (one in B and the other one in C), the provider configure the sip-i (with allow-anonymous as "all", instead "agents-only") when we reconfigure this field as agents-only we receive a 403, and if we change this field to "all" the call proceed (incoming realm A), and in the logs seems that the incoming SA it's the same (because the routing is by local-policy, always route the call using the local-policy of B, the lp is more or less: from * to * source realm B next-hop 1.1.1.1; we have a

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