mc_

I can't say definitively but I believe this cause can be added to ignored hangup causes. I know Kazoo has plumbing in ecallmgr the explicitly handles the case where the hangup cause is REDIRECTION_TO_NEW_DESTINATION. I can't imagine why a system operator would want alerts about this (but I'm not a typical system operator so hopefully someone else can chime in with a good reason to keep the alerts for this hangup cause). Regarding Erlang, I would welcome you to pick it up just for general learning as well as being able to hack on Kazoo itself. Probably the best way to help the community is looking at the different doc sites and improve the docs. Each page should have an edit link taking you to the git repo backing the content. PRs welcome! Feel free to ask Erlang questions here as well, if you decide to pursue that avenue. Love to help folks get up to speed there!

Hi! and welcome! If you want to remove this hangup cause from the ones that generate alerts, I think you need to edit the "hangups" document in the "system_config" database. There should be a key "ignore_hangup_causes" that will contain a list of hangup causes that Kazoo considers "normal" or expected. You can add this redirection cause to that list, flush the cache "sup kapps_config flush" on the VM, and see if that does the trick. See here for more about monitoring hangup causes.

Hi Lance, There is a commercial offering called Qubicle. You'd have to talk to the sales team to find out more, get a demo, etc. ACDc is community-supported and has several companies using it and occasionally submitting pull requests with updates.

Hard to know what "does not work" means in this case? What errors do you see? Does using 'curl' on the command line work? Maybe its an issue with Fauxton? Can you supply some more details around what you're experiencing?

Where are you putting this media? Most places that take a media_id of some sort will also accept the "shout://" URL as well. FreeSWITCH will need mod_shout enabled as well, by the by.

I don't think there's anything restricting the URL from being "shout://...". ecallmgr explicitly checks for shout:// and passes it direct to FreeSWITCH. Give it a shot and let us know!

To add, this will be on the latest and 3.20 builds when those jobs are run.

Hi Alex, I've patched the relevant code to support multi-nested keys in the querystring filters. The relevant commit if you care is here