Jump to content

Darren Schreiber

Administrators
  • Posts

    1,202
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by Darren Schreiber

  1. Also, I've re-confirmed that this appears to be only traffic to NY so far that I've been able to simulate this with. Very strange. I think a peer somewhere is saturated. I wonder if Level3 is having peering disputes again with Verizon and/or Comcast or their backhaul providers.
  2. I don't think this is throttling. BlueTel has been working with me on this with some traces. What is super weird is Level3 (or Verizon?) is sending traffic to our gateway IP (.1) via one peering point, but traffic to our other nodes is going through an alternate peering point. I think something is still wrong, and am working on it. We did confirm that if you're impacted by this, you can reroute to us-central.p.zswitch.net for now and the problem is resolved. I may even do that for the remainder of the day for all traffic until I understand this issue more.
  3. Yes but most people expect it to also not open the bridge until a moderator arrives, drop callers at the end when a moderator leaves, and give DTMF control, too basically. None of that works (yet).
  4. 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.
  5. ALG should be off, Consistent NAT should be on.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. Unfortunately, I still have no idea what you're asking :-/
  12. You can use PRIs with Kazoo. But I don't know what you mean by "linking" two PRIs?
  13. Found the setting and changed it! You should now be able to edit.
  14. 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.
  15. 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!
  16. 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.
  17. 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.
  18. Yes, this was actually a community contribution. Someone wanted a simple ability to ring groups of people repeatedly, up to a limited number of times. It's kind of a poor-man's call center.
  19. Miss the old Google Groups "email only" format of communicating? With the help of ninja engineer @Bret Truchan, we're bringing it back! You can now reply by email to notifications you receive from the forum. Read https://forums.2600hz.com/forums/announcement/5-post-to-forums-via-email-now-available/ for more details. (We're working on a simple way to email all posts to you as well. Stay tuned for that)
  20. Rules and Guidelines For the 2600Hz Community: Discussions, Reviews, and User Generated Content These guidelines apply to all places in the 2600Hz Community Forums and Documentation areas where users can post content. This includes, but is not limited to: discussions, comments, guides, product reviews, screenshots, artwork, videos, tags, etc. When providing feedback, posting information, or discussing a product in the 2600Hz Community, whether it’s negative or positive, please make sure you are being relevant, constructive and polite. Developers take feedback from all kinds of sources into account, even though they may not have the time to respond to every post or question. Please note that Administrators/Moderators reserve the right to change/edit/delete/move/merge any content at any time if they feel it is inappropriate, abusive, or incorrectly categorized. General Rules Do NOT do any of the following: Flame or insult other members Post personally identifiable information (i.e. name, address, email, phone number, etc.) Post advertisements or add advertisements to your signature, or attempt to solicit other members via the forum in any way Post links or attempt to covertly promote outside services Bump threads Derail a thread's topic Post spam or links to phishing sites or Re-post Closed, Modified, Deleted Content Repetitively post in the incorrect forum (example: VoIP device provisioning settings in the product feedback section) Openly argue with a moderator Artificially manipulate the User Review system or voting/rating systems Content Rules Do not post any content on the 2600Hz Community containing the following: Porn, inappropriate or offensive content, leaked content or anything else not safe for work (NSFW) Any discussion of piracy will result in a permanent ban from the 2600Hz Community including, but not limited to: Cracks Key generators Console emulators Cheating, hacking, game exploits Threats of violence or harassment, even as a joke Posted copyright materials Soliciting, auctioning, raffling, selling, advertising, referrals Racism, discrimination or slander Abusive language, including swearing Drugs and alcohol Religious, political, and other “prone to major arguments” threads No Backseat Moderating Let the moderators, moderate. Backseat moderating is when people who are not moderators try to enforce the forum rules. If you see a person breaking the rules, take advantage of the Report button or simply ignore the offensive content Report Posts to Moderators Should you observe a fellow Community member breaking these rules please report the post or item by clicking the Report button located on every item, post, and review. Repeated Offenders Repeated offenders of the above rules and guidelines will be banned from the 2600Hz Community. A moderator has the ability to ban a user for violating the rules at their discretion. Enforcing the Rules We have a variety of methods we use to enforce our rules, including, but not limited to Asking nicely to stop the negative contributions Asking you less nicely the next time Suspension of accounts (temporary or permanent) Removal of privileges, or added restrictions to account Adding restrictions to the 2600Hz communities, such as adding NSFW tags Removal of content Banishment from 2600Hz Community
  21. This is GREAT, thank you, hold onto this, we're gathering a list now that we finally have a damn tool that allows peer reviews (that is what has taken so long).
  22. @Ivan Tazelaar We're putting together a group of folks to help with docs, would you consider joining? It's just a small commitment to touchbase once a week. We'll divy up the biggest needs and split the work but also coach people on it. You get the added benefit that you can interact with our staff directly and get answers to, well, whatever you want!
  23. That's what the option requiring pressing 1 on answer is for. Nobody likes it, of course, but that's why it exists.
×
×
  • Create New...