Why Is CDR(recordingfile) Not Being Written To The Database Despite Being Set In The Dialplan?

Home » Asterisk Users » Why Is CDR(recordingfile) Not Being Written To The Database Despite Being Set In The Dialplan?
Asterisk Users No Comments

I am using Asterisk 11.17.1 with my program that uses AMI Originate calls to generate a bunch of calls for a callcenter. The PBX configuration is handled by FreePBX 2.11. I want to understand the dialplan behavior in order to figure out why the CDR(recordingfile) is blank on the CDR records despite the dialplan setting it.

My program generates the calls by setting Channel=Local/NUMBERTODIAL@from-internal and by setting Exten=QUEUENUM, Context=from-internal, Priority=1 . The FreePBX-generated dialplan results in the following trace as seen in the Asterisk console. In particular, please note that CDR(recordingfile) is being set in Local/9991416445@from-internal-0000017b;1 :

— Executing [9991416445@from-internal:1] Macro(“Local/9991416445@from-internal-0000017b;2”, “user-callerid,LIMIT,EXTERNAL,”) in new stack
— Executing [s@macro-user-callerid:1] Set(“Local/9991416445@from-internal-0000017b;2”, “TOUCH_MONITOR29224932.21697”) in new stack
— Executing [s@macro-user-callerid:2] Set(“Local/9991416445@from-internal-0000017b;2”, “AMPUSER