[CDR] Asterisk 13. Not showing CDR for Transfers as expected

Asterisk Asterisk Support
1

Hey,

I’ve just upgraded from Asterisk 11 to 13, in hopes of getting more wholesome CDR records for calls that are transferred, as shown here https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification#. The scenario is the Attended Transfer to Channel.

My scenario here is:

  1. 682 dials 850 and talks for a while
  2. 850 transfers to 851 (by holding the call, dialing 851, then transferring)
  3. 682 talks to 851 for a while and hangs up.

What I get in my CDR records is:

	seq	src	dst	dcontext	 uniqueid	      linkedid
	141	682	850	act-22575	1424894097.687	1424894097.687
	143	850	851	act-22575	1424894105.695	1424894105.695 <- notice linkedid different
	145	682	850	act-22575	1424894097.687	1424894097.687

What I would expect (according to the Asterisk 12 CDR Spec), is something like this:

	seq	src	dst	dcontext	 uniqueid	      linkedid
	141	682	850	act-22575	1424894097.687	1424894097.687
	143	850	851	act-22575	1424894105.695	1424894097.687
	145	682	851	act-22575	1424894097.687	1424894097.687

This is actually what I saw in asterisk 11 too, so I’m wondering if something else can cause this behavior? When testing this, I’ve got three phones (A(682), B(850) and C(851)) on my desk, one for each extension. I test is like this:

  1. A, dial B
  2. Pickup B, press Transfer, dial 851#
  3. Pickip C, hangup B. C and A are connected.
  4. Hangup A.
2

Howdy,

I think you’re correct about that. Could you follow the Issue Reporting Guidelines here:
wiki.asterisk.org/wiki/display/ … Guidelines

Cheers

3

Hey Malcolm, thanks for your reply.

I’ve created issue ASTERISK-24839 on Jira.

4

Awesome. And I see correspondence going back and forth on the issue tracker there. Thank you. :smile: