Campaign Rec Filename & ALLFORCE

[Go4Payne]

I'm having an issue with the filename of recordings. I have filled in Campaign Rec Filename = VENDORLEADCODE_FULLDATE_CUSTPHONE_AGENT

When I set Campaign Recording = ONDEMAND the recordings get named correctly without issue every time. However, when I set it to ALLCALLS or ALLFORCE it drops the vendor_lead_code off the front of the recording name. I've tried testing on a newly created (not copied) campaign and every time it works fine with ONDEMAND but nothing else. I'm not hitting the character limit because I'm testing with the same vendor_lead_code each time.

I have another completely separate cluster where this is working fine and I've compared line by line the campaigns and they match completely. The only difference being the dial method and my other environment is SVN 3057 DB Schema 1561, same version and build though.

Has anyone else ran into this or have any advice on what to try from here?

[Go4Payne]

Small update. I attempted changing the template and moving VENDORLEADCODE to the end of the filename and that still did not resolve the issue additionally if the template has ONLY VENDORLEADCODE then it makes the recording using the Asterisk call id and then writes nothing back to the recording_log table for the filename so the recording is not accessible from the admin site.

[Go4Payne]

One more update: I had route Routing Initiated Recording set to "Y", changing only this to "N" resolved this issue.

Follow up questions:
1. What am I missing by not having Routing Initiated Recording?
2. I still don't really understand why this is happening in this manner, my other environment has Routing Initiated Recording set to Y without issue. (I guess that's less of a question...)

[williamconley]

If you read the details for RIR, you'll find that it's a technical question and is necessary in certain, very technical, situations and prohibited in others. If not sure, test it. Relates mostly to manual dial vs autodial. does the call get initiated by the agent javascript/AJAX interaction or by the agi scripting in the "route" of the call.