Unable to record an inbound call once a call has been parked or sent to a ring group

I have the same problem which i just noticed today. After a call is parked, recording does not restart, even though the extension that picked up the call is set to always record.

Any thoughts?

I cant believe only 2 of us are having this problem.

I would really like to get this handled before it becomes a huge issue. I've tried everything I can think of.

Anyone have a solution? Please help.

*BUMP*

I'm curious what the intended behavior is...

If I pick up a parked call, is it still considered incoming? I would actually like to hear ALL legs of incoming calls for diagnostic purposes after-the-fact.

George

Recording can be specified by each user when they login to the web interface, they can choose whether or not to record their calls. If you transferred the call to another agent, it is considered incoming, and runs through the same part of the dialplan (you can verify this in /etc/asterisk/extensions.conf, and more specifically, under the [macro-record-enable] section of /etc/asterisk/extensions_additional.conf). So, as long as the agent who is receiving the call has record incoming calls turned on, it *should* be recorded. Can you verify that this was the case? If those conditions are true, then I'll look further into the subject, and get you some answers you can work with. Also, you can write a custom script to do a BEEP BEEP when recording is enabled at the start of each call if you like, it would only require slight modification to extensions.conf.

All of the users had incoming call recording enabled. I just did a test to my extension that has all incoming (& outgoing) calls recorded.

- Dialed my extention directly via IVR
A Talked to myself for a few seconds.
- Parked call.
B Talked to myself for a few seconds.

It didn't matter if it was a blind transfer or assisted transfer on my Polycom 550 to the parking lot--Part "A" is recorded, but part "B" is NOT.

George

So at least there are several of us with this problem.

Can anyone record a call once its been parked?

George

I was able to test the workaround. It is a bit of a hack, and may cause other problems, but I was able to record my parked call.

Any Thoughts? I've copy and pasted the text from the second link:
---------------------------------------------------------------------------------------------------
On February 6th, 2009 NSSL (tadpole) said:

I have some further information that may be of interest . The problem with retrived parked calls not being recorded is a ASTERISK issue , there is a problem in res_features.c ( parked calls handler) park_exec - ast_set_flag(&(config.features_callee), AST_FEATURE_REDIRECT); - This seems to not set the *1 feature code - I know a little "C" however not enought to solve the issue !

Also to get around this problem I wanted in FREEBPX to be able to take control of the process of picking up parked calls i.e when 701 is dialled I want to do some stuff ( like record the call!) so I added this to extensions_custom.conf

- [from-internal-custom]

exten => _70Z,1,NOOP(HERE--------------------710-----------------------GOT-IT AND RECORD)
exten => _70Z,2,Macro(record-enable,${CALLERID(number)},OUT)
exten => _70Z,3,parkedCall(${EXTEN})

However this code is only executed if you dial say 701 and there is not call parked on 701 - If there is a call parked on 701 the FREEPBX take over and my custom code is not executed -

I then discoverd that this is because in extensions.conf ( from-internal-xfer)
the include "parkedcalls" is before the include "from-internal-custom" .

It you swap these around my custom code works ( eg. 701) get executed !)

[from-internal-xfer]
; applications are now mostly all found in from-internal-additional in _custom.conf
include => parkedcalls
include => from-internal-custom

change to be
include => from-internal-custom
include => parkedcalls

I know you are not susposed to change extensions.conf - however it looks like this file does not change with a reload etc ?

regards
-----------------------------------------------

So it is apparent that this is a bug in the system. Not a configuration issue.

I have given up on waiting for someone from trixbox to step up to the plate. I am also tired of the "have you turned your pc on" people. If I was that stupid I wouldn't have found this amazing forum.

Now that I have got that off my chest. I being a lowly stupid person unwise in the ways of the pbx world apparently found my own workaround until the gods of the trixbox world wake up and notice they missed something.

If you are not using hudlite, install it.

if you use it to pick up a parked call you keep your caller id information and you can record the calls. We have tested it thoroughly. The receptionist answers the call. parks the call. Normally I would hit 701 to pick it up and then I have lost the caller id and ability to record. Now I use hudlite and drag the parked call to my extension and poof all is well.

The bug appears to be in the actual pickup of the call. When trixbox picks up a parked call it loses its information. But using hudlite does not have the same issue.

So for those of us who actually have to get work done. Its not the best solution but it works.
And for any trixbox person who cares enough to actually pay attention. FIX IT.

I will not recommend the pro version of this to anyone until the ce version works.