Jump to content

mc_

2600Hz Employees
  • Content count

    602
  • Joined

  • Last visited

  • Days Won

    4

mc_ last won the day on January 6

mc_ had the most liked content!

Community Reputation

44 Node Leader

6 Followers

About mc_

  • Rank
    Advanced Member
  1. Kazoo in IMS

    Kazoo is API driven so I suppose if the IMS environment has a way to write adapters to talk to Kazoo it should be possible. Do you have a system in mind?
  2. Open Source Dev Community Call

    until

    Every two weeks is correct.
  3. Open Source Dev Community Call

    until

    @Te Matau 9:30 Pacific, so yeah, 16:30-17:00 now with the time change. One day the forum will have proper timezone support!
  4. KAZOO 4.2 Upgrade Highlights

    @Mike Montgomery From reading the list, everything not Qubicle-related is in the open source project.
  5. Open Source Dev Community Call

    until

    @Dhruv yes, please type "community" as instructed in the event description
  6. Unable to get the kazoo atlassian wiki page

    Probably though I find the docs site comes up using duckduckgo. I don't think we've tuned it much and should probably add redirects from the wiki somehow. The big push is getting content moved over; making it discoverable to the search engines hasn't been prioritized yet.
  7. Unable to get the kazoo atlassian wiki page

    The wiki is in the process of being deprecated. Some of the pages were "auto-imported" into the docs site but require refreshing and updating to render properly. For instance, the SUP page can be found here. It needs love though; want to make the updates and issue a pull request? There's an edit link on the page if you're signed into Github.
  8. until
    This is a make-up call for Dec 19th with James, Karl, and 2600Hz engineers to talk all things 2600Hz with developers from around our community. Join us on Townhall: https://townhall.2600hz.com/ room is "community" 9:30-10:00 PT (17:30-18:00 UTC)
  9. Open Source Dev Community Call

    until

    @CBV David Sorry! There was a need to update the certs used which was supposed to be a quick update/restart but things spiraled out of control fast. OPS had to rebuild a bunch of stuff (including compiling FreeSWITCH which is never fast). Looks like this one flopped hard. I'll see if we can do a makeup later in the week.
  10. Open Source Dev Community Call

    until

    @CBV David the call is in 30 minutes. Don't use the keypad to enter; just type in on your keyboard the room name. https://townhall.2600hz.com/
  11. SaaS Support

    Hi @Luigi and welcome! You will want to check out our Global Infrastructure program. You can also reach out to the sales team to talk through your requirements, hopes, and dreams. They'll walk you through your options, give you a demo of what the platform looks like, etc.
  12. Basic SIPp scripting: https://github.com/2600hz/community-scripts/tree/master/sipp And make-busy: https://github.com/2600hz/make-busy Though make-busy is getting an overhaul to be more friendly to test writers!
  13. To add more, will your devices be doing HD audio? Video? Lots of transcoding between WebRTC (using OPUS) and PSTN (using PCMU)? Conferencing? If so, how many participants? Support for SIP over TCP/TLS/VPN/etc (basically non-UDP)? SRTP? Fax? Expected CPS and concurrent calls? Lots of presence/BLF/other features? As mentioned, you can create more zones to isolate load based on geography (typically). You can throw bigger hardware at the problem. You can buy bigger and bigger pipes. You can host and get cross-connects in the same data-centers with your upstream providers. But there's no magic formula for inputting X devices and getting Y infrastructure costs. There are best practices that get you pretty far but eventually something will crack and you'll need good monitoring to detect those cracks. So, yes, Kazoo can be (and is) deployed to support 250K+ devices. As you grow, different parts of the infrastructure will fall down and need improvement, and where those spots are tend to be unique values for each installation (esp since usage patterns tend to vary greatly). We can be your partner in that journey to 250K and anticipate a lot of the growing pains
  14. schema user_auth not found

    Sounds like the schemas haven't been loaded into the database. Try 'sup kapps_maintenance refresh system_schemas` to force a reload of schemas, then try your create command again. You probably want to remove the account db (and modb), and the account doc from the 'accounts' db.
  15. You can test it out by setting "sip.custom_sip_headers.in.X-Geolocation" on the device doc. This will set the header on outbound calls from the device (Kazoo typically uses in[bound] to mean coming to Kazoo from the endpoint). But it doesn't address the room/floor question.
×