Acme Packet (MOSC)

MOSC Banner

Terminating Trunk Group value in CDR does not match that of egress session agent after re-direct

edited Apr 3, 2013 3:59PM in Acme Packet (MOSC) 3 commentsAnswered

Hi,

 

Our SD receives a SIP 302 with multiple values within the contact header to recurse through. Each contact is a configured session agent. Additionally each session agent is configured with a unique trunk group value.

 

If the SD ultimately uses an option within the contact header other than the primary,  the CDR still shows the egress trunk group value to be that of the first option.

 

For instance, a SIP 302 to the SD contains the following contact header:

 

Contact: sip:15857500000@1.1.1.1, sip:15857500000@2.2.2.2

 

Each host is a configured session agent on the SD with the following trunk group values:

 

SA 1.1.1.1 - TG 11111

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