Darren Schreiber
-
Posts
1,202 -
Joined
-
Days Won
27
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Darren Schreiber
-
-
The moderator pin doesn't really do anything yet. Also, you either use a moderator pin or an attendee pin.
We're still working on moderator functionality.
-
ALG should be off, Consistent NAT should be on.
-
Not yet, we are working on an installer that allows for this. But we're not quite there, the delivery mechanism is being built for them.
-
This is not a great idea. While it's been discussed, we generally only support extension dialing within the same account. As you pointed out, there are many threads discussing this, and while most people SAY they only want to call extensions between accounts, the conversation always devolves into additional requirements (all of which vary) like BLF across accounts, conference bridges across accounts, parking slots across accounts, and so on. It gets super messy.
We are instead working on a solution so that, in a single account, you can have multiple delegations (for location or franchise and so on). This should solve this, but is not ready yet.
-
We'll see for sure on Monday but we have just completed some routing changes that should put this issue to rest. Sorry for any headaches this has caused.
-
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.
-
We now have three FiOS folks complaining about this. I have opened a ticket with Level3 to see if we can get some traces and figure out what is going on here.
-
Unfortunately, I still have no idea what you're asking :-/
-
You can use PRIs with Kazoo. But I don't know what you mean by "linking" two PRIs?
-
Found the setting and changed it! You should now be able to edit.
-
I might be able to fix that.
-
There should be an edit button, no?
-
Yes, there is a Caller ID option for specifying which Caller ID to send when using a trunk. Its' specific for this purpose. Set it to "Internal" when configuring your carriers/resources.
-
I'm confused, you can already select the firmwares. Are you saying when a new one becomes available, you want to manually set it beforehand?
-
That makes sense. What if we add a special newsletter you can sign up for that is solely for sandbox updates?
-
I agree with that completely. We'd LOVE to have the public feedback. Frankly we've also been struggling with how to get people to actually test. I know ya'all are busy, but honestly we can't think of everything to test and it drives the costs way up if 100% of the testing is on us. I am debating whether people get "bug hunter" credits that they can cash in as incentives or something for participating in the testing.
We've been pretty religious at this point about pushing ALL updates to sandbox WEEKS before pushing to production, and that includes provisioner. But we're only seeing two or three people actually use sandbox to pre-test regularly.
-
Thanks, feel free to add some feedback on what topics you'd love covered this year! We're trying very hard to ensure it's engaging and there are demos you can try - from your computer during the conference!
-
The call recording app and features are now in beta on sandbox. We are still working out some kinks on it. We are also deploying it to the folks who sponsored part of the feature first. Once they approve it and testing is complete, we'll roll to production.
I think it will roll out for testing this weekend and next weekend. After that, I can post another update and ETA here.
-
Well the beta strategy I listed above would likely give enough time to find any huge bugs. To roll-back I suspect we could just remove the bad firmware which would change the default/Current one.
However frankly the problems have been amplified not by a need to roll back (the manufacturers have been pretty good with fixing actual bugs quickly) but more with an inability to quickly release & move forward without being disruptive. So I feel a bit of this nervousness is from being burned in the past in ways that may not happen in the future.
-
I don't think we'll do that, that's kind of "black magic" that gets us in trouble. Though creative :-)
I can imagine our poor support staff trying to tell some super picky client to point their firmware server to their own server (they'll freak) and then tell them to manage and host their own firmware files and if they don't like a firmware to just not host it. They will not like it.
-
Also, yes, the current firmware should be listed in addition to the "Current" option, I'll note that with @Peter Lau
-
Perhaps then we simply add an "Beta (vXXX)" category. Then you can set some phones to Beta, watch for the announcements, and test. We'll leave a week in between before we promote a firmware after announcing it (minimum).
-
We do not allow email signatures or profile signatures. The resources you are using here are paid for by 2600Hz and 2600Hz customers and too many people try to use email signatures, in my opinion from past forums, to advertise their services who don't contribute to the project. So they should be getting stripped or will be removed manually by moderators.
-
We basically don't add anything special to FreeSWITCH's native transcoding subsystem. You may wish to post your questions about codecs on the FreeSWITCH forum, they may have more suggestions for you.
Call Park RingBack time change
in Tips and Feedback
Posted
If someone could file a JIRA requesting this enhancement, I can see about getting it on the schedule.