Darren Schreiber

There was a JS error that is preventing the list from loading. There is a patch rolling for that tonight.
 

This was already reverted in the latest build - please check it.

This should be resolved. Sorry for the delay.
 

Hi there!
Thanks for trying out Kazoo! Lots of questions indeed. Let me try to answer each, below...
We are looking for assistance on the documentation side, if you are interested in helping out, please let us know!
 
 
So actually the rating stuff is kind of generic and you can use any currency you like, but we hardcoded US in the UI for now. So you would just have to change that. We don't deal with tax right now, and the billing engine is kind of archaic and is due a re-write. I would recommend using only the limits and per-minute rate tracking features and overriding the UI to put in your own currency. We would welcome contributions to make the currency dynamic, we just haven't had the time to do it.
 
Like a single install? Just remove accounts manager from the apps list and it's a standalone PBX if that's what you mean.
 
We have some more open-source apps coming out soon but not yet. The provisioner / carrier manager / dialplan apps are currently closed source. Please contact sales@2600hz.com for those.
 
There is a blacklist application that I believe is released open-source. You can use that.
 
Thanks!
 
Go into the Futon database and go into the accounts DB. Delete the bogus account. Also, drop the databases for the bogus account as well. Then you should be good to go.
 
 

Yup, soooo we host this outside of 2600Hz datacenters and apparently the provider rebooted the box. I thought we restarted all services but postfix did not auto-start. The mail has been queueing though.
So all the emails should have just been delivered that were queued.
Sorry bout that.
 

To be clear the ISO was actually an auto-installer that would download the latest version from the web. That said, it was for 3.x. Hasn't been updated for 4.x.
But the date is not so relevant. The configs changed from 3.x to 4.x though.
 

Hi there,
     As far as I know, every number gets a unique address (even room number) so I am not aware of a way you can transmit the specifics of the room or location number with granularity at this time. If someone is working on that, it is news to me - right now they make money off each of those numbers so there's no motivation, to my knowledge, to fix that.
     We played with an idea at one point to change the APIs in realtime - person dials 911, we update the API with the latest address, pause for 2 seconds, then connect the call, but decided it was a terrible idea to have someone wait on the line, even for 2 seconds, when calling 911, so abandoned that (without the pause the databases didn't seem to update reliably enough / rapidly enough).
      So I am unaware of a solution to this besides paying per number.
 

Thanks for writing. I'll try to answer your questions as best I can!
 
You wrote:
"1) I would like to know how many registrations/calls Kazoo can manage for each Kazoo/kamailio node (for registrations) and for each FreeSwitch node (for calls). How can I estimate these values? Do I have to evalutate for each node or for the entire cluster?"
Currently we have a number of people hitting between 10,000 and 30,000 on a single proxy. There are some optimizations we're working on which should raise that limit, but that's the norm, on mediocre hardware.
 
You wrote:
"2) I would like to start with 2 nodes. How can I setup them? 1 FS + 1 DB/Kazoo? 1FS+1DB + 1Kazoo? All-in-one? Next they will be scaled as the registered devices increase."
Yes, we support this now. All-in-one nodes are fine. You can split the components out later. But use at least 2 servers so you have some redundancy.
 
You wrote:
"3) I know Kazoo 4.0 pretty good (applications and source code). Is it a good idea to start with 4.1 instead?"
Up to you, 4.1 is stable now. There was a memory leak in Kamailio 5.0.3a but I believe that is patched also, so should be good to go. We are running 4.1 publicly on many clusters now.
 

You can use PRIs with Kazoo. But I don't know what you mean by "linking" two PRIs?
 

That's what the option requiring pressing 1 on answer is for. Nobody likes it, of course, but that's why it exists.