17:45:28 I've got Kazoo5 installed on Rocky9 - all seems good except freeswitch only stays up for 15seconds and crashes/restarts 17:50:21 barney: not sure off hand :) 17:50:28 FreeSWITCH 20.23.6-2600hz.22.el9 17:50:28 mod_kazoo v1.5.0-1 community 17:50:28 mod_kazoo.so -> fetch_config_exec() 17:50:28 switch_xml_free() 17:50:28 free() 17:50:29 SIGABRT 17:50:45 also, open source community call in 10 if you didn't see the announcement on the forums 17:50:55 seems if i stop fetch_sup it stays up 17:51:08 https://events.teams.microsoft.com/event/ac9673ea-f90a-40ef-9f5c-17542151429c@2d44ad66-e31e-435e-aaf4-fc407c81e93b i think is the link 17:51:32 barney: yeah, i think lazedo mentioned mod_kazoo will need some updating 17:51:57 we're debating whether to bring it into 2600hz github org or put it in kazoo-community org to coordinate the updates needed 17:52:11 yeh that would help :) 17:52:40 fs also says: 17:52:40 switch_xml.c:01797 Error[[error near line 1]: root tag missing] 17:53:03 I guess the xml has changed? 17:53:13 or. no long compatible? 17:53:47 likely yup 17:58:41 wip: https://gist.github.com/bputtick/f9f565a4c0a6226aafab84ca5fec63bf 18:01:38 link 404s 18:02:20 yeh.. just redacting lol 18:02:21 https://gist.github.com/bputtick/b72f28ea5af0f7509020968d70e1a0bf 19:02:10 barney: check out mod_kazoo at https://github.com/openkazoo/mod_kazoo 19:03:06 I thought mod_kazoo was closed source - or is this a complete rewrite? 19:07:44 2600hz uses a closed source version (actually I think it has a different name than mod_kazoo but anyway same purpose). This is a modified version of mod_kazoo community version. 19:11:04 ahh ok.. where is the community version ooi? 19:20:54 stupid question - it's a git fork of it :) 19:41:08 barney: are you bputtick? 19:41:27 yes 19:42:49 ah ok. I had seen your open/closed PR a while back with a bunch of changes and was going to try to get ahold of you to join us with the OpenKazoo v4.4 work. But I guess most of the efforts are going to be around v5 now (hopefully things progress enough in that direction anyway). 19:44:22 ahh what PRs were you interested in? 19:50:13 barney: we developed mod_com_kazoo to integrate some closed source features between FS/kazoo 20:02:14 located the bug in mod_kazoo - or at least where it's blowing up for me - OpenKazoo version does the same 20:02:48 i just assumed there was no pulic source for it - didn't occur to me to look on freeswitch 20:04:27 I suspect that the XML ecallmgr is sending over the api is broken/incomplete which is causing mod_kazoo (kazoo_node.c) to die - it's to do with UNPROTECT_INTERFACE(api) 20:05:03 just digging in to that macro to understand what it's doing 20:17:51 mc_: until you clarified today, I was under the impression that you also had a closed Ecallmanager version that was higher performance, but from what you said, it's just the Freeswitch module that's different, right? 20:18:47 Alan Evans did some early stage work on modifying Freeswitch's mod_amqp for bidirectional communication. If I remember correctly he got it to work for basic calling. 20:19:10 barney: nothing in particular---I just noticed a rather large PR being opened by you on 2600Hz Kazoo 4.3 repo. Just trying to make sure all us guys working on Kazoo are working together more and not reinventing the wheel like we've all been doing for the last 7 years or so lol 20:30:07 ruhnet: ecallmgr + FS/mod_kazoo is the open source release 20:30:25 ecallmgr + ecallmgr_extension(closed) + FS/mod_com_kazoo is what we run internally 20:31:06 Oh ok, so that "extension" is what you mentioned as the "overlay" in the call I guess. 20:31:12 exactly 20:31:42 i am trying to convince powers that be that mod_com_kazoo + ecallmgr_extension don't impede our ability to sell ooma services 20:31:50 and we should open source them so we all can benefit 20:31:57 that's a slower conversation :) 20:33:15 Hehe that would be great. So (without getting you in trouble) what exactly [at a high level] is that extension? Is it like a translation/connection layer of some sort, or does it add Ooma custom functionality, or what? 20:33:36 (if you can't answer that without danger that's ok) 20:35:13 mostly it does the konami integration in FS using bind_meta_app stuff, then morphed into the AMQP connector 20:35:20 so we send/recv over amqp to/from FS now 20:36:16 nice 20:36:20 ah, so combo of both translation (to AMQP layer) and features (Konami). 20:37:29 and I guess having Konami work closer to FS like that improves performance considerably over our Konami that we have now. 20:37:41 yeah, mod_com_kazoo also shapes the events, so they go straight to other apps, ecallmgr doesn't shape them and republish 20:40:02 cool 22:35:35 barney: have you updated ecallmgr at all? there are some changes that need to be made to ecallmgr to make it play nice with mod_kazoo, even with mod_kazoo being "fixed" to work with v5