Skip to main content

Call Recording.

Posted by brian on Fri, 04/15/2011

Hi All,

If I have call recording enabled for an extension all inbound and outbound calls are recorded.

If a call arrives at this extension from a hunt list it doesn't record. Is there something I need to add to the dial command from the huntlist or is this a know limitation?

Thanks
Brian


Submitted by eeman on Fri, 04/15/2011 Permalink

you can put a custom command into the huntlist at the top for the mixmonitor application much like the userextension macro uses. Just pick a clever name for it that follows the same naming format so that the webpage will parse the data out of the file name and list it correctly.

Submitted by IVSCOMM on Tue, 01/03/2012 Permalink

I have the same problem.
what would the command be?
is this the same place where we place the pickupmark command?

Submitted by eeman on Mon, 02/20/2012 Permalink

there is no 'fix' because nothing is broken. The only thing requiring a fix is your understanding of how the device gets called. If you want to extend a feature to a call that goes to a hunt list you would have to include such options in the configuration screen to allow for them. I would recommend reading Asterisk The Future of Telephony if you are wanting to do-it-yourself. Another option is to hire someone to program a huntlist for your and you can copy that example going forward.

Submitted by rfrantik on Mon, 03/12/2012 Permalink

Since this seems to be one of Erik's favorite subjects, I will continue on and ask a couple of more questions.

I understand that nothing is broken.... but it seems that the Record All and One Touch Record features were not extended to calls that arrive via a hunt-list, was this by design? Is there something else that breaks or conflicts with the hunt-list?

There is a post from moshe on Mon, 12/29/2008 - 20:36 called - Topic: feature code/hunt group not recording calls...

In that post Erik replied with this "calling from a huntlist eventually arrives in tl-userexten-rg-base which checks to see if recording is possible from your astdb settings" and then showed a config for tl-userexten-rg-base... The configs listed there seem to line up with the macro in MTE 6.1.1.12... the end of the post seems to get a bit muddled with some 1 word replies from Moshe and Ales... OK, Test

So while I understand that if I was more of an Asterisk Guru the answer would be obvious... I'm not sure where the disconnect is between being able to record and a call delivered via hunt-list.

Any help is truly appreciated.

Submitted by IVSCOMM on Mon, 03/12/2012 Permalink

Check out this forum link and see if it answers your question. I think it will. Particularly the last comment.

Submitted by rfrantik on Mon, 03/12/2012 Permalink

Looks like you added this command to get your queue recording straightened out...

Set(__MONITOR_FILENAME=queue-NameofQueue-${STRFTIME(,,55.000000-%H-%M-%S)}-${CALLERID(num)}${TL_DASH}${tenant})

I'm thinking I would need to adjust it a little to get the extension number involved...

Set(__MONITOR_FILENAME=auto-${UNIQUEID}-in-${THISEXT}-${STRFTIME(,,55.000000-%H-%M-%S)}-${CALLERID(num)}${TL_DASH}${tenant})

I will test...

Submitted by eeman on Tue, 03/13/2012 Permalink

the best place to find the format that conforms to the thirdlane naming conventions would be in the dialplan itself. Check tl-userexten-base to see which variables get set and its naming structure. Remember that the variable/function setting affects some aspects, whereas calling MixMonitor directly will mean always record without option. So when you see both examples, this will explain why its coded both ways.

Submitted by rfrantik on Tue, 05/22/2012 Permalink

Shawn, yep... I'm pretty sure that command worked to get the call recorded (or something very close to it). But in further discussion with the customer they really wanted everything recorded that went to that group. So we switch it to a queue and the queue just records everything.

Are you trying to do the same thing?

Unfortunately it was about 2 months ago and my memory isn't that great :)

Submitted by IVSCOMM on Tue, 05/22/2012 Permalink

All inbound calls to a hunt group. TL will not record all. So I am trying to find the parameters for the command to make it work.

Submitted by Skydoc on Mon, 07/16/2012 Permalink

I came across this thread when I was trying to get my hunt lists to record. MixMonitor ends the moment that the call is accepted by one of the recipients on the followme hunt group. There is not equivalent GUI asterisk command entry box in the followme screen and so I am assuming that the command would have to be added to the tl-followme script manually.
Would someone be able to confirm that this is the right approach? I have a feeling that I could easily break stuff :-)
Obviously any more comprehensive instructions as to how I could go about adding call recording to the follow me recipients would be very much appreciated.

Kind regards,

Geoff.

Submitted by Skydoc on Mon, 07/16/2012 Permalink

If you want to record the followme hunt group activity simply modify the tl-followme-huntlist script clone

Erik's was of course a good pointer - take the format from tl-useresten-base

exten => s,n(record),MixMonitor(${FNAME}-${DIALED_NUMBER}-${STRFTIME(,,%F-%H-%M-%S)}-${CALLERID(num)}${TL_DASH}${tenant}.${RECORDING_FORMAT},b)

Modify the file name parameters as required.

Hope this helps (although actually all the work was done in the previous posts!

Regards,

Geoff.