FASTDEVICE Posted November 20, 2018 Report Share Posted November 20, 2018 Any thoughts on adding a failback field to the Advanced Call Flow Pivot element? Maybe a pulldown to select extension, user, device, media, TTS, or enter another Voice URL? Link to comment Share on other sites More sharing options...
CCP Posted November 23, 2018 Report Share Posted November 23, 2018 Having this would be wonderful. Ideally, in advanced callflows, you should just be able to add/chain something on to the bottom of a pivot, like any other normal callflow element. Right now, this has to be done via the API or direct in the docs. Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted November 27, 2018 2600Hz Employees Report Share Posted November 27, 2018 Pivot expects to be in control of the call once the pivot callflow action is executed. This may mean sending the response callflow JSON back to the callflow executor, but the intent was never to let the response "inject" callflow but to "be" the callflow going forward. Kazoo UI was thus coded to have the pivot action be a terminal action and not allow children. Some time after Advanced Callflows was ported from Kazoo UI to Monster, the ability to have a "failure" child on the pivot callflow was introduced in case the HTTP request failed or the response was invalid. I think Darren mentioned that Advanced Callflows is close or on the roadmap for a refresh so I would wager this failure child will be doable via the UI once that's complete. Link to comment Share on other sites More sharing options...
esoare Posted December 23, 2018 Report Share Posted December 23, 2018 On 11/27/2018 at 1:47 PM, mc_ said: Pivot expects to be in control of the call once the pivot callflow action is executed. This may mean sending the response callflow JSON back to the callflow executor, but the intent was never to let the response "inject" callflow but to "be" the callflow going forward. Kazoo UI was thus coded to have the pivot action be a terminal action and not allow children. Some time after Advanced Callflows was ported from Kazoo UI to Monster, the ability to have a "failure" child on the pivot callflow was introduced in case the HTTP request failed or the response was invalid. I think Darren mentioned that Advanced Callflows is close or on the roadmap for a refresh so I would wager this failure child will be doable via the UI once that's complete. That would be fantastic @mc_ esoare Link to comment Share on other sites More sharing options...
FASTDEVICE Posted August 17, 2019 Author Report Share Posted August 17, 2019 On 11/27/2018 at 4:47 PM, mc_ said: Some time after Advanced Callflows was ported from Kazoo UI to Monster, the ability to have a "failure" child on the pivot callflow was introduced in case the HTTP request failed or the response was invalid. Hey @mc_ I remember you pointing out the usage for the failure child but I seem to have lost my notes. Would you please refresh my memory and I'm sure others want to know as well, the JSON usage for the Pivot callflow failure? Big Thanks! Link to comment Share on other sites More sharing options...
Rick Guyton Posted August 17, 2019 Report Share Posted August 17, 2019 +1 just because I can't figure out how to follow a thread on my mobile phone without replying Link to comment Share on other sites More sharing options...
FASTDEVICE Posted August 19, 2019 Author Report Share Posted August 19, 2019 Think I found the documentation. https://github.com/2600hz/kazoo/blob/91ca9c277aa0af6019b210e1d7124736fe4ec068/applications/pivot/doc/README.md Look for the section header Failback. Link to comment Share on other sites More sharing options...
esoare Posted August 20, 2019 Report Share Posted August 20, 2019 On 8/17/2019 at 11:03 AM, Rick Guyton said: +1 just because I can't figure out how to follow a thread on my mobile phone without replying @Rick Guyton On mobile it's at the bottom. Just had to find it for another thread, and I thought I'd share. Link to comment Share on other sites More sharing options...
Recommended Posts