My Oracle Support Banner

Incomplete CDR for SIP-ISUP Call (Doc ID 2420576.1)

Last updated on JANUARY 06, 2022

Applies to:

Acme Packet 6300 - Version S-Cz7.2.0 and later
Information in this document applies to any platform.


User reported incomplete CDR for specific call flows. There is only one leg CDR present for a successful call and the second leg is missing.

Call flow for bad CDR is :

A--------------SBC               SBC--------------B

---INV(sdp)------->              ---INV(mime)--->

<---183(sdp)------              <---183(sdp)-----

So now initial negotiations has happened in SDP.

Problem appears when call is forwarded and renegotiation happen:

A--------------SBC               SBC------------B

---INV(sdp)---->                 ---INV(mime)--->

<---183(sdp)----                 <---183(sdp)----

<---181(no sdp)---                <--181(mime)-----       >>>>>  (has only ISUP message body)


This renegotiation's in SDP (from SIP to ISUP) is causing bad CDR. For such calls CDR has only leg of the call and egress leg is missing completely.


Good CDR:


 1,"",5060, xx,xx,xx,xx,xx,xx "00:00:00.000 UTC Jan 01 1970","00:00:00.000 UTC Jan 01 1970","audio","audio",,,0,0,0,0,0,0,0,0,,99341350

2,"",5060, xx,xx,xx,xx,xx,xx "00:00:00.000 UTC Jan 01 1970","audio","audio",,,0,0,0,0,0,0,0,0,,99341350

Bad CDR:



If you see bad CDR starts with filename (with CDR prefix)





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.