Logicwrath Posted December 10, 2016 Report Posted December 10, 2016 Hello,Prior to the most recent upgrades and changes we had call recording objects set to 3600 as the time limit. Now when I edit call flows or groups and the like I get an error that says the time limit cannot exceed 600. This is only ten minutes. I think it is reasonable that a call will last longer than 10 minutes.Is this a bug? I already had to change 2 objects today to 3600 to 600. Can we get the time limit removed or increased?
Karl Stallknecht Posted December 10, 2016 Report Posted December 10, 2016 Uh oh, this is really important to us too! Are you noticing that accounts you used to set to 3600 are now going back to the default, or you just can't change newly created call recording objects?
Logicwrath Posted December 10, 2016 Author Report Posted December 10, 2016 I just noticed that when I needed to edit an object with inbound call recording enabled I could not save it because my 3600 was failing the 600 max limit. I suspect/assume that already saved objects still have the 3600 configured but I have not dug into it more yet.
Administrators Darren Schreiber Posted December 10, 2016 Administrators Report Posted December 10, 2016 No, nothing has reverted. It's only when you edit.
Administrators Darren Schreiber Posted December 10, 2016 Administrators Report Posted December 10, 2016 There has, for a long time apparently, been an erroneous time flag saved in the STOP call recording objects, which the schemas have now actually been fixed for. BUT when we fixed the schema (properly ironically) it made it so the old elements are failing. At least this is what we believe the issue to be.In the call flow you are editing, is there a start AND a stop element? If so, can you try deleting the stop element and then re-adding it?
Administrators Darren Schreiber Posted December 10, 2016 Administrators Report Posted December 10, 2016 Well the issue ironically is that the old callflows have invalid data in them. We fixed the validation for that, but now the hidden values in the old callflows won't save (which is technically correct). If you rebuild the callflow, it will work.We are looking into some JS that will "cover up" the invalid data if you try to re-save it and just "clean" it "as you go" basically. But for now, rebuilding the callflow SHOULD work. Let me know if that matches your findings.To be clear, the callflows still work fine, so no need to re-save them if you're not actually working on them.
Logicwrath Posted December 10, 2016 Author Report Posted December 10, 2016 I noticed this with groups in SmartPBX where I configured "Inbound Call Recording". When I try to edit the group and save changes, it will fail saying the call recording options have a time limit set too high.I also have a single call flow item with "Start Call Recording" configured prior to calling another call flow. There is no stop configured.I have not tried recreating the call flow object yet. Are you suggesting that we re-creating the call flow might solve the problem?I hope "re-creating" groups and call flows is not the solution. That will require some effort.
Administrators Darren Schreiber Posted December 10, 2016 Administrators Report Posted December 10, 2016 Let me take a look. Email a support ticket in with the account and group you're editing and how I can recreate it.
Administrators Darren Schreiber Posted December 10, 2016 Administrators Report Posted December 10, 2016 To be clear, the recreating was a workaround if you just needed to do this now, before a permanent fix is figured out.
Karl Stallknecht Posted February 21, 2017 Report Posted February 21, 2017 Looks like 3600 is the limit. Any chance we can get it bumped up to 7200?
Administrators Darren Schreiber Posted February 21, 2017 Administrators Report Posted February 21, 2017 Please file this on tickets.2600hz.com and I'll see what we can do.
Administrators Darren Schreiber Posted March 6, 2017 Administrators Report Posted March 6, 2017 This was changed to 7200, where are you seeing 600?
Logicwrath Posted March 6, 2017 Author Report Posted March 6, 2017 Try deleting your temporary internet files etc..
Karl Stallknecht Posted March 6, 2017 Report Posted March 6, 2017 I tried creating a new call recording element on a call flow and got this error.
Karl Stallknecht Posted March 6, 2017 Report Posted March 6, 2017 @Logicwrath: I almost always use Monster in Incognito mode
Administrators Darren Schreiber Posted March 6, 2017 Administrators Report Posted March 6, 2017 What other items are in the callflow? I bet it's a different item which has the >600 issue.
Karl Stallknecht Posted March 6, 2017 Report Posted March 6, 2017 Nope, literally nothing else in it:
Logicwrath Posted March 7, 2017 Author Report Posted March 7, 2017 We are seeing the same issue. I tried to add a caller id pre-pend on a monster group and it is telling me "The value for the field "children._.time_limit" must not be more than 600."I would still like to add the pre-pend if this gets fixed can you update the thread so I know to check?
Administrators Darren Schreiber Posted March 7, 2017 Administrators Report Posted March 7, 2017 Can you guys try it now?
Recommended Posts