Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won



Recent Profile Visitors

1,898 profile views
  1. Ok thanks for the clarification @mc_ I will make sure to install the open source white label app instead on clusters I build.
  2. I don't know where it was obtained from---the last one I looked at did not have any git files, so it didn't show a git remote entry. There is a community app called "Whitelabel" that offers similar functionality. But the Branding app looks a bit more polished as far as the UI, so if it's OK to use it I would prefer to install and use it. But I don't want to use it if it's not open source or free/legal to use and was obtained through unapproved means. I know there was a company a while back selling bootlegged copies of some MonsterUI apps and there are probably some of those floating around still, so I just didn't want to inadvertently use something that wasn't allowed.
  3. No, I'm talking about the Branding MonsterUI app that has the fingerprint icon:
  4. Recently, I've seen the Branding app installed on some open source clusters that I have worked on for various clients, but I do not see it on GitHub. What is the licensing status of the Branding app? Is it open source, or available for purchase, or ??
  5. Yum supports using a SOCKS5 proxy, so what I've done in cases like this is to SSH to another machine (that isn't blocked) and add the -D5000 option to SSH, which will give a SOCKS5 proxy on port 5000 that yum can connect to. Then you can use an environment variable to tell yum to use the proxy on socks5://localhost:5000. You could also use some publicly available HTTP proxy.
  6. The main problem I have encountered with Cisco phones of this vintage are that they absolutely refuse to register to a realm---they will resolve hostnames, but will always put the resolved IP address as the realm in the SIP messages. So to work with Kazoo, it requires either a local Kamailio (or similar) to do some SIP message manipulation, or to modify your Kazoo Kamailio config to detect phones from a particular IP address and make the realm changes, to allow Kazoo to identify the device as belonging to a particular account.
  7. Yes, HAProxy only supports a combined certificate/key file in one. I normally use the bash script GetSSL to do cert renewals, and it will output a single file which removes the need to cat them together.
  8. Hehe I didn’t really mean to target you with that lol—it was only the handiest example (of many out there) to illustrate my point. 😁 And like I said, I’m just as frustrated and anxious as everyone else but at the same time I do feel respect for 2600Hz’s position. (Except for on Konami/Konami Pro and kazoo_db which I can’t make sense of why those are closed source. 😆)
  9. Umm 2600Hz has been clear that they do intend to release v5 open source. They have never said anything to the contrary. Now technically they could change their mind or have been lying about it, but I don’t see any indication of either of those. The time delay factor is of course frustrating, but that in itself I don’t believe is a solid sign of them backing out, and they have continued to maintain that v5 will indeed be released.
  10. To be honest I think these nitpicky complaints are exactly [part of] the reason v5 has been delayed --- it's impossible to please everyone, and all these statements like "YOU (2600Hz) should have latest Freeswitch", "YOU should fix this XYZ bug...", "YOU should support ABC, XYZ because I want it to make money for myself...", "YOU should have released v5 two years ago when it wasn't ready so you could put up with me complaining about it for the past two years" probably don't really give 2600Hz a warm feeling about the OSS community. So why should 2600Hz release something when they know it's not ready, and it will only unleash a barrage of [free] help requests, criticism, and general bad feelings toward 2600Hz? Especially when the amount of help given back to 2600Hz by the community is somewhat limited. To be clear---I use Open Source Kazoo, I want new features, I want fixes, I want all of it to be open source (Konami hehe). I've been chomping at the bit to have v5 as long as anyone else. But at the same time, I do understand their position, and I understand why the app store has been delayed so long---it's hard to make software not pirate-able, but at the same time not a nightmare to install and use and maintain. I do wish they would go ahead and release everything else, so we could begin to work with it, but I don't know all the ins and outs of v5 to know if that's doable without a great deal of effort. So, everybody, just relax. :) Unless of course you are willing to put your money where your mouth is and actually offer to pay for certain things to be fixed, or offer to fix (and contribute) certain things yourself. :-D I don't think a fork is warranted at this time---forks are sometimes good things, but most people grossly underestimate the amount of work involved in maintaining a medium-large codebase. And unless something changes I really don't think our OS Kazoo community has enough high power developer talent to make a fork a real success, so any benefits I think would be minimal. I'm hoping we'll hear good news concerning OS v5 around Kazoocon this year. If not, then I may begin to reconsider my position. But until then I'm just going to be patient and do the best I can with what we have now.
  11. You can manually install the latest Freeswitch can't you? Keeping latest FS in sync with Kazoo repo adds another layer of management complexity, so to be honest I'd rather have the default repo be the older (it's not all that old) version of Freeswitch that is guaranteed to work fine with the other Kazoo RPMs, rather than having breakages happen every so often and then having to wait on a fix or revert or whatever. in the mean time there's nothing stopping anyone from using the official Freeswitch repo. It's just a matter of setting your yum config for it. 🤷‍♂️
  12. Ok yes that's very interesting. I'll have to add this to my notes.
  • Create New...