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

mc_

2600Hz Employees
  • Posts

    1,760
  • Joined

  • Days Won

    4

Posts posted by mc_

  1. The situation was that marketing was done with Kazoocon and we didn't have official word that there'd be a 2024 Kazoocon, so they decommissioned the site.

    Word is, there will be a 2024 Kazoocon, so the site should be re-instated in the next day or two (whenever our ops team can turn it back up).

  2. You're correct that Kamailio interacts with KAZOO via AMQP, does not contact CouchDB, and does use sqlite for local storage stuff. Kamailio is part of the "cluster" because of the AMQP connection.

    I can't speak to the packaging issues though. The process to open sourcing Kazoo5 work continues to wind through the appropriate channels; should resolve so many of these issues. Apologies for the frustrations in the mean time.

  3. @RuhNet definitely a private app that appears to have been exfiltrated. We know of someone (or someones) who had sandbox access that appear to have taken several private UI apps this way.

    The APIs are open for what the branding app does, but the UI code is not. I don't know what we can do about it but if you want to share any information privately, feel free to contact me and we can look into it.

  4. To be clear, it doesn't exist because this is quite possibly the first time in 13 years someone has actually wanted to use this in KAZOO.

    So, while your request might be widely accepted, in practice it does not seem to be widely desired within the KAZOO userbase (or folks just don't mention the lack of this feature as important).

    If this is a typical thing Teams will be doing, however, it could end up on our roadmap, as we do have the Teams integration now. Will pass along to our team managing that, thanks!

  5. That is not a supported way to dial, no. You could see about using the sleep and send_dtmf callflow actions via the channels API.

    In general, there aren't many ways to interact with an established b-leg via the callflow itself (most actions like user/device/resources will block in the action while the bridge is up, and only continue processing the callflow on SIP error).

  6. When the Erlang VM starts up, it catalogues what code is present. It sounds like you added Konami to the file system after the VM was started, so the VM has no way of knowing about Konami.

    You can add the file path to Konami in the VM or you can restart the VM and Konami should be included in the file paths searched by the VM when a module is used.

  7. If you want to have an existing PBX route through KAZOO, create it either using the "connectivity" API or as a "device". "Connectivity" configs use a backend service call trunkstore, most suitable for pure SIP trunking. If you want callflow features available before routing to/from your PBX, creating it as a "device" makes sense.

    The "ips" API is probably not what you want, in this case.

  8. All indications are that marketplace means open sourced 5.x from discussions I've had. On the technical side, we've demo'd working marketplace integration with clusters. The CPaaS team presented at Kazoocon and the roadmap sounds like a rollout of select partners listing their existing apps on the marketplace and select partners participating in purchasing/delivering apps via marketplace to their clusters is next.

    Q2 2024 was listed as possible general availability of marketplace to the broader community which should trigger opening access back up to KAZOO repos related to open source KAZOO apps.

    Its obviously been a whirlwind as much of the company found out about the acquisition at Kazoocon and we're just returning home to process, get onboarded into Ooma, etc. But I am encouraged by discussions that open source does remain on the roadmap and, with the bigger resources of Ooma coming to bear on all aspects of KAZOO and 2600Hz's goals, I'm personally excited to continue building KAZOO and the open-source community around it.

  9. 1> UTC = calendar:datetime_to_gregorian_seconds({{2023,8,31}, {2,43,00}}). 
    63860668980
    2> Mel = kz_time:adjust_utc_timestamp(UTC, <<"Australia/Melbourne">>).
    63860704980
    3> calendar:gregorian_seconds_to_datetime(Mel).
    {{2023,8,31},{12,43,0}}

    It appears KAZOO at least knows what time it is in Melbourne. KAZOO typically gives the API response in UTC seconds so I would investigate the UI conversion.

×
×
  • Create New...