Jump to content
KAZOOcon: hackathon signup and details here! ×

Mooseable

Members
  • Posts

    190
  • Joined

  • Days Won

    4

Everything posted by Mooseable

  1. I'm eagerly looking forward to it. It's my favorite project. I'd love to host my own cluster like I do, but just license the apps. It would then make financial sense for us being that we are so small. Biggest thing is to get off older versions of Linux :/
  2. Just because I picked "other", I've integrated real-time caller-id, account setup and automated billing with HaloPSA. Looking to grow it by adding call notes to tickets and audio recordings/transcripts and sentiment analysis.
  3. Ooma built their solution on 2600hz open source. They also acquired OnSiP On the investors call; They see 2600hz as the solution for the future. They want to invest more into development of the platform core and applications. There are significant savings in development for Ooma through the acquisition (2M/year). The recognize the revenue model of 2600hz, and list the open source market as an opportunity, though how was not discussed. They also mentioned that the GP% of 2600hz is lower than Ooma, and they hope to increase it to match Ooma's ~60% GP within 6 months (or at least EBIT positive) When asked about the developer community, its size and opportunities there, they mentioned that there "is a community" but was not really elaborated on. The acquisition is largely around the technology stack and the operational benefits it brings, control over the roadmap, new opportunities to reach large carriers, and not just the existing customer base. in closing remarks, it was said by Eric Stang that they are committed to the 2600hz community and the open source version
  4. You can try setting "ignore_early_media" on your offnet/carrier, which may solve your problem. This will send ignore_early_media to freeswitch, both 180 and 183 will trigger your fake ringing from FS to the handset.
  5. @mc_ appreciate the input. I'm personally happy to pay 2600hz, especially for apps. However, a small operation like mine tried to get a quote and it was all USA hosting for a lot considering our small customer base. I did suggest that 2600hz could host the kazoo apps nodes only, keeping the IP protected without having to run a full cluster, which seemed to garner some positive feedback from 2600hz, but I don't think it went anywhere. Its probably what the app exchange is targeted for. I'm happy to contribute to docs, for v5. But it has felt like a wasted effort to write docs for v4 since it seems the change to v5 would be drastic. I personally would love to hear what would be most helpful to contribute. I'm only one person and I'm extremely time poor, so knowing where my efforts would be most impactful would be good to know. I will add, I do try to contribute from time to time, but my PR from 3 years ago is still open (and still fixes an active issue)
  6. I also get why they don't want to release v5 as per a previous statement that people tend to "jump right to it" without testing themselves, then probably cause a bunch of complaints/support requests. But if we are anywhere near an open-source release, I would love if some of us could gain access to or sign up for the v5 open-source release for testing. But as @Chris Labonne stated, we are in that process of deciding to stick with Kazoo or not. And I'd love to do another Kazoo Community Training video with the updated v5. I've kinda held off creating anything as I don't want it to be outdated.
  7. Do we even know if we will get a new version in time so we can get off Centos7 before it hits EOL?
  8. One day, I might do a part 2, or even an updated version for more recent versions of couchDB :) If only I had more hours in the day to do all the things I wanted to do :/
  9. This is not the forums for Kazoo Pro (which I believe are knock-offs of the official 2600hz.com licensed apps). I doubt you will find any help here.
  10. Token restrictions will allow you to block "CREATE" "DELETE" operations for certain endpoints, though I've not implemented this myself yet; https://docs.2600hz.com/integrator/applications/crossbar/doc/token_restrictions/ Not sure how to handle the CLID without writing your own app at this stage (though this is something I will be looking in to myself soon)
  11. @kazte, yes, what you are after is possible. You can have pre-paid or post-paid accounts. You can apply a limit to post-paid accounts too. In the event an account exceeds its limit, it will terminate calls. You simply need to set an account to be pre-post paid and set the limit. You also need to ensure the Jonny5 app is running. By default, limits are per-month (though you could use the API to "top up" an account or change its limit on a more frequent interval). Limits apply to resellers also. When an account underneath a reseller account makes a call, the reseller account is also charged for that call. Likewise the root/superadmin account by default is also charged for the resellers calls (charges all the way up the chain). Each account may be charged a different rate (based on their ratedeck). You can choose NOT to charge a specific account (useful for the root/superadmin account) by using "flat rate trunks". Ratedecks can be at the system, reseller or account level. Hotornot is the app in charge of figuring out how much to charge for a call (it does the call rating) Jonny5 enforces the limits (it does limiting). I personally do not know how often Jonny5 checks limits/credit.
  12. So getting 404 on whitelabel doesn't mean much, it just means you haven't set up whitelabelling (which is perfectly OK). Same with the braintree. You could also fork the install guide, update it then submit a PR to get it updated. You are correct that it no longer has the line "localhost" in the configJS, as it uses the request url AFAIK if it is not defined, which works if Monster and Kazoo Apps are installed on the same server. Otherwise, you need to set it up specific to your environment as per https://docs.2600hz.com/ui/docs/configuration/
  13. What are some of the more common errors and issues you run in to?
  14. Sure, what you put in there looks fine. I'll (try) to do a new video each month. I have no idea how bits will help me out, but thanks I guess Maybe I can donate them to those that keep helping me out like @lazedo and @mc_, can I buy them beer with bits? You should also look in to offering the closed-source apps to self-hosted solutions by running ONLY the apps nodes for those closed-source apps. This would help people like me who don't really have the client base yet to pay you for the full infrastructure stack, but am certainly willing to license/pay for the extra apps!
  15. If I go to the Downloads page, when I go to contribute, the only option is to upload a file (not submit a link) unless I'm missing something obvious @Emily R
  16. Apologies for the lateness. The training stream was great, but I wanted something a bit more concise so I re-recorded an AIO setup. This covers installing and configuring the associated services for an all-in-one server. I'll work on more expanded content, including creating a clustered setup as well as deep dives in to each of the services, setting up billing plans, creating carriers, etc.
  17. I will be running another stream next week, probably more US timezone friendly. I will combine it with todays stream for the cut down version. Australian internet failed me and installation from repos were going to take ~30 mins, which wasn't happening on my test yesterday. Good practice run and I will return with the all-in-one setup probably next week.
  18. I will try to contribute the edited down videos. Not sure if it matters, but I don't have access to that area personally.
  19. Well, I should have everything I need now. I will be running a stream at 11:00 UTC this Friday. I'll be doing via youtube live which you can view/set your reminder here; https://www.youtube.com/user/mooseable/live Open to feedback, suggestions for topics. Replay should be available post stream and I'll see if I can work on an edited down version for the time-starved individuals. I'm sure the first stream will be horrible as all new things are, but we can get there I will cover, briefly, the overview/architecture/design principals of 2600hz Kazoo from my understanding, then go on to build various lab environments, starting from an All In One server, to working on getting a cluster. Finally, this will be based on Kazoo 4. If any of the 2600hz team wishes to provide any input or advice, I'd be more than happy to chat.
  20. FYI, I am still planning on doing this, but lovely COVID delayed the delivery of some equipment I needed. It's all starting to arrive now, so I should have something out soon.
  21. Posting logs helps. do a search and replace for IP addresses, usernames, realm/domain names and node names ideally. Logs should show the device being looked up and found as well as an invite to the device in freeswitch.
  22. Probably just stream to Youtube (likely with zero viewers given my timezone) then release the edited VOD a couple days later via Youtube also. I will most likely go through from the start to end. Start with planning/architecture, go on to the individual components and how they integrate/communicate, then move in to the apps based on feedback, like provisioning, billing, pivots, etc I would like it to end up being a series that I can give to my team and new employees and they can then understand Kazoo.
  23. I'm wondering if there is community interest for a weekly stream showing Kazoo 2600hz covering; Architecture Overview Planning for Deployment Deploying each service (Kamailio, Freeshwitch, RabbitMQ, CouchDB, HAProxy, etc) Configuring services (Fax to email services, pivots, api integrations) Troubleshooting (Figuring out where a fault exists, common caveats, fixes) I do not work for 2600hz and have been using the community edition in production for about 3 years. I certainly don't understand EVERYTHING about kazoo, but I know how to get it all working, fix problems, etc. The stream will be live and I will work on providing an edited version for uploading to YouTube. I'm interested to see what topics people are most interested in and what timeslots work for them. I am in Australia, so the start times I can provide could be between any of the below, with a run time of about 2 hours. 11:00 Fridays (UTC) and 14:00 Fridays (UTC) 01:00 Saturday (UTC) and 12:00 Saturday (UTC)
  24. Instead of having a ruleset for when they are open (if the open hours go over midnight), define when they are closed. Then when the temporal rule is true, route to your voicemail/ivr/whatever. Then set all other times to go to your "Business Hours" route.
×
×
  • Create New...