Acme Packet (MOSC)

MOSC Banner

Precedence of "tgrp" over Contact data

edited Oct 4, 2019 8:32AM in Acme Packet (MOSC) 6 commentsAnswered ✓

Hello community,

Has anybody ever met following problem: there are two session-agents connected to the softswitch via SBC in peering scenario with "tgrp" based routing.  SA1 sends INVITE with address of SA2 in Contact field. SBC forwards this INVITE to the core and adds trunk-group;trunk-context configured for SA1, so from softswitch (10.20.30.40) perspective, this incoming INVITE belongs to trunk-group 100. If softswitch sends any request within the session, for example, BYE, it adds trunk-group 100 into this BYE. When SBC makes a routing decision - to which of two SAs to forward this request, it looks only to the "tgrp" user-uri-param received

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