trying to record outbound calls on an outbound route statement

Status
Not open for further replies.

wa4zlw

Member
Jun 7, 2019
131
2
18
70
Blandon, PA
www.myinternetsupport.com
hi folks!

we're running a call center and inbound calls are working fine. We're trying to record outbound calls when our agents dial a prefix which sets the caller specifc did and then goes out a specific trunk. We searched the forum and found to add action | set | record_session=true and that is right before we go out the trunk below. Dialing out this trunk does NOT record the call. What am I missing? Thanks leon
We are on 4.4.6 and switch 1.8.5 (64 bit) running on Debian 9.9.

1561572169682.png
 

JamesBorne

Active Member
Jan 24, 2019
294
57
28
Australia
action | set | record_session=true
This would record all calls.
You would need to check the /var/log/freeswitch/freeswitch.log for your test calls and see if there is an error or an attempt at recording. Probably a file permission error.

If you wanted to:
dial a prefix
Most modern SIP phones can record with SIP signalling. Yealink have a button type that is "Record" which can initiate and stop recording on a press with no modification to any routes.

Otherwise, you could do this to record when you press *2:
action - digit_bind_action - local,*2,exec:record_session,$${recordings_dir}/${domain_name}/archive/${strftime(%Y)}/${strftime(%b)}/${strftime(%d)}/${uuid}.${record_ext},${bind_target}

Haven't used/tested this in a long time but it should do the trick.
 

wa4zlw

Member
Jun 7, 2019
131
2
18
70
Blandon, PA
www.myinternetsupport.com
Hi James...thanks for getting back to me.

I just tried it again and I only see this in the log relating to recording (sorted descending)

Code:
3b0e47fb-7c5c-4690-a465-21645192e850 2019-06-27 01:48:57.711673 [DEBUG] mod_dptools.c:1598 SET sofia/internal/1522@myis.xxxx.com [record_session]=[true]
3b0e47fb-7c5c-4690-a465-21645192e850 EXECUTE sofia/internal/1522@myis.xxxx.comset(record_session=true)

I'd prefer not to use a key code like *2 becuz our agents would most likely forget to do it. :) Like to keep things automatic.

seems like we're missing something here. Can't put my finger on it.

Thanks leon
 

JamesBorne

Active Member
Jan 24, 2019
294
57
28
Australia
I reread your question.
Your agents dial a prefix to reach a specific outbound route, not they dial a prefix to record. My apologies.

You could try this answer?

<action application="export" data="execute_on_answer=record_session $${base_dir}/recordings/${strftime(%Y%m%d%H%M%S)}_${caller_id_number}.wav"/>

String looks right from what I can tell.
 

wa4zlw

Member
Jun 7, 2019
131
2
18
70
Blandon, PA
www.myinternetsupport.com
GM John...no problem but this didnt work. oddly it also affected other outbound routes as well. when I put that in when I dialed I got a Not Found (code: 404) on the 81 or non 81 dialing. when I removed it all works again.

I also kept in the previous action session=true as well. I had it as follows:

Code:
action | Application export | data="execute_on_answer=record_session $${base_dir}/recordings/${strtime(%Y%m%d%H%M%S)}"

I stuck it after the record_session=true and before the last entry
CDR shows No Route Destination when tryiing to dial with or without the 81 prefix.

Thanks leon
 
Status
Not open for further replies.