Acme Packet (MOSC)

MOSC Banner

[CDR] Disconnection Cause or SIP status

in Acme Packet (MOSC) Question

Hello all,

I would like to discuss about CDR disconnection cause field and Acme-SIP-Status fields. How the SBC decide the value for this field on each case?

In the case a SIP dialog contains encapsulated ISUP messages, should this value used later on CDRs? If not, how the SBC fill Disconnection Cause field? Will it depends on sip-isup-profile?

If we would like to monitor KPIs based on how a call ended and getting info from CDRs, which field should we use? Should we use Acme-Disconnect-Cause of Acme-SIP-Status?

From accounting documentation Acme-SIP-Status seems to cover more scenarios, although only a subset of all displayed are used in a Stop Record. But are we right?

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