4 posts / 0 new
Last post
mcampbell@1pointcom.com's picture
Joined: 2015/05/20
Points: 10

I have an Asterisk command to record hunt list calls that works fine (uses MixMonitor, places the correctly formatted filename in the correct subfolder, etc...)

Issue: the recording never shows up in the Recorded Calls screen. I believe there is another command I must use to notify the database the recording exists. Any ideas as to the syntax of this command to use in conjunction with MixMonitor?

I am currently running TL-MTE

Thanks in advance for any assistance.

volodya's picture
Joined: 2017/01/05
Points: 250


You need to call ODBC function TL_RECORDING from your dialplan.

cleartalk's picture
Joined: 2010/05/25
Points: 10

Hi Valodya,

We have the same issue using a hunt list device based. When using extention based it works.

How can we make this work with device based using the Thirdlane GUI?

eeman's picture
Joined: 2007/11/06
Points: 290

As 'root' you have the ability to 'add custom command' in your huntlist. This is where you can call that function. here is an example from existing code that used the function TL_RECORDING. It appears as it is just making an entry into the database, you would still need to use MixMonitor to get asterisk to record the file.

exten => s,n,Set(__MIXMONITOR_FILENAME=queues/${ARG1}/${YEAR}/${MONTH}/${DAY}/queue-${ARG1}-${STRFTIME(,,%F-%H-%M-%S)}-${CALLERID(num)}${TL_DASH}${tenant}-${CALL_ID})
exten => s,n,Set(__FULL_NAME=${MONITOR_FILENAME}.${HASH(Q,monitor_format)})
exten => s,n,NoOp(result=${TL_RECORDING(${CALL_ID},${FULL_NAME},${RECORD_CALLER},${RECORD_CALLEE},queue,${TOUCH},${CALLERID(num)},${ARG1})})

Runs the following query, as defined in func_odbc.conf, performing
substitution of the arguments into the query as specified by ${ARG1},
${ARG2}, ... ${ARGn}. This function may only be read, not set.

call set_recording('${ARG1}', '${ARG2}', '${ARG3}', '${ARG4}', '${ARG5}', '${ARG6}', '${ARG7}', '${ARG8}', '${ARG9}', '${ARG10}', '${ARG11}' ,'${ARG12}', '${ARG13}')


Not available

[See Also]
Not available

Ideally what I would do is use MixMonitor and set a filename but make the destination extension static so it will get parsed by the application that lists recordings. Ideally I would make a feature code for a huntlist so that it has an internal extension. So lets say that all your sales agents are 521 - 529, I would make a feature code 520 that runs the tl-huntlist macro. Then my MIXMONITOR_FORMAT would look similar to the recording format of an extension, but instead of using the extension of whomever answered the call (wont know that until after you've already defined the filename), simply make it 520.

Erik Smith
Thirdlane/Asterisk Support available