Skip to main content

cdr incorrect

Posted by fropa on Mon, 03/27/2017

Hi. I'm testing thirdlane MT. I viewed cdr module and it shows incorrect info. While inbound call goes to an extension it writes that destination was an extension, but when inbound goes to queue or voice menu it writes that destination was 't', 's', or sometimes DID number. no matter that calls answered or not. And case 2, when I'm testing inbound and the test phone answers the music on hold continues for 2-3 seconds. Also in cdr, the 'caller ID' shows "the real caller number" format.


Submitted by eeman on Tue, 04/11/2017 Permalink

thats not incorrect. This is how asterisk writes CDR. Its the extension inside asterisk dialplan

[someivr]
exten => s,1,Answer
exten => s,n,Playback(greeting)
exten => 1,1,Voicemail(120@default,u)
exten => 2,1,Goto(from-inside-redir,121,1)

exten => t,1,Goto(s,1)

in this case if you call in and get sent to [someivr] and end the call while still processing the Playback of the greeting, the extension in cdr is 's'. If you press option 1 and hang up then the extension written to CDR is '1'. If you press 2 then you get sent to extension 121 and 121 is written to CDR.

This is how asterisk works universally. This transcends all front-end management applications as it is part of the engine core itself.