I HAVE A DREAM BLF for Call Recording

[gordon]

So I asked on the FreePBX forum and it isn't possible to have a BLF for call recording.

Would this be something that an add on could implement? Visual feedback that a call is being recorded would be very helpful. I have had a couple of calls in the past that I wish were recorded, but nothing to warrant recording all calls. However, in my testing, it is kind of awkward to enable call recording and since *1 is called a "toggle", I am fairly certain I will eventually disable call recording instead of enabling it when I need it.

A visual indicator that the call is being recorded when I press the button would be very nice.

 

[krzykat]

I like it ... can't think off-hand how to accomplish is though. The GXP2200 has this feature set though - while in a call - you can press options and record - and it will record to your SD card. I know not exactly what you're looking for, but better than nothing.

 

[krzykat]

You know ... I've done call flow control with a BLF hint with *280 - Green indicates normal mode, and Red indicating toggle on. ... wondering if this could be used in conjunction with Misc Application to do what you want.

 

[gordon]

No idea if this is a viable solution, but if I was attempting to code this, I might try to splice into the record macro [macro-systemrecording] and define a custom hint in the format *1<ext_num> (probably *1${AMPUSER}) set it to "INUSE" when recording then set back to "IDLE" when recording finishes. Then extension 100 would have a BLF set to monitor *1100. You wouldn't be able to use the BLF button to toggle recording, but with some work you might get it to visually indicate recording status.

Then could the dial plan be set so that *1<ext_num> only dials *1 but the BLF reads *1<ext_num> correctly?

 

[phoneguy]

It is not that easy. When we designed Call Recording for 2.10 we tried to get a button working. The problem was to many race conditions where it would never be right. Its better to show no data then in correct data.

 

[gordon]

It is not that easy. When we designed Call Recording for 2.10 we tried to get a button working. The problem was to many race conditions where it would never be right. Its better to show no data then in correct data.

Hello Tony,

That is too bad. I didn't know that the implementation had been attempted. It sounds like you are saying it would basically take a redesign in call recording to make this work?

 

[phoneguy]

No as we already re-designed it. It would take more then a re-design more of some core changes in Asterisk for this to work. We did add in 2.10 that it will beep when it starts the recording for on-demand.

 

[ou812]

Yealink has a Record button that lights up when you press to record and turns off when you press to stop or hangup, This uses a sip header to tell Asterisk to record and USED to work but for some time now Asterisk doesn't like the sip header command and it"s WAAAY over my head to figure out how to get Asterisk to accept the command, I will show what I captured maybe someone smarter than me can shed some light.

INFO sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.122.58:5062;branch=z9hG4bK42824453

From: <sip:[email protected]:5062>;tag=1725010718

To: "Polycom" <sip:[email protected]>;tag=as5c631b46

Call-ID: [email protected]:5060

CSeq: 103 INFO

Contact: <sip:[email protected]:5062>

Max-Forwards: 70

User-Agent: Yealink SIP-T28P 2.70.0.140

Record: on

Content-Length: 0



SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.122.58:5062;branch=z9hG4bK42824453;received=192.168.122.58

From: <sip:[email protected]:5062>;tag=1725010718

To: "Polycom" <sip:[email protected]>;tag=as5c631b46

Call-ID: [email protected]:5060

CSeq: 103 INFO

Server: FPBX-2.11.0(11.1.2)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Content-Length: 0



OPTIONS sip:[email protected]:5062 SIP/2.0

Via: SIP/2.0/UDP 192.168.122.150:5060;branch=z9hG4bK170180ff

Max-Forwards: 70

From: "Unknown" <sip:[email protected]>;tag=as0bbaa71e

To: <sip:[email protected]:5062>

Contact: <sip:[email protected]:5060>

Call-ID: [email protected]:5060

CSeq: 102 OPTIONS

User-Agent: FPBX-2.11.0(11.1.2)

Date: Fri, 28 Jun 2013 21:29:10 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Content-Length: 0



SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.122.150:5060;branch=z9hG4bK170180ff

From: "Unknown" <sip:[email protected]>;tag=as0bbaa71e

To: <sip:[email protected]:5062>;tag=193001677

Call-ID: [email protected]:5060

CSeq: 102 OPTIONS

User-Agent: Yealink SIP-T28P 2.70.0.140

Content-Length: 0



INFO sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.122.58:5062;branch=z9hG4bK501974758

From: <sip:[email protected]:5062>;tag=1725010718

To: "Polycom" <sip:[email protected]>;tag=as5c631b46

Call-ID: [email protected]:5060

CSeq: 104 INFO

Contact: <sip:[email protected]:5062>

Max-Forwards: 70

User-Agent: Yealink SIP-T28P 2.70.0.140

Record: off

Content-Length: 0



SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.122.58:5062;branch=z9hG4bK501974758;received=192.168.122.58

From: <sip:[email protected]:5062>;tag=1725010718

To: "Polycom" <sip:[email protected]>;tag=as5c631b46

Call-ID: [email protected]:5060

CSeq: 104 INFO

Server: FPBX-2.11.0(11.1.2)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Content-Length: 0


Gary.