[mc_]

Hi Otto,

I'll try to list the reference docs that probably address your points:

- If you plan to have devices/users in Kazoo, you can use the quickcall functionality[0] to connect them to a phone number. Includes setting custom caller ID. Some folks build queues using conferences and you can dial out[1] from them as well

- With the channels[2] API you can query active channels per account/user/device.

- With the CDRs[3] API you can fetch CDRs over a range of time

- You can setup call recordings automatically for devices/users/accounts (see [4] for example). You can also enable them on-demand in the callflow (JSON tree that determines how to process a call).

- Depends on whether you bridge two callers together or put them in a conference how you implement these features but definitely do-able.

From what you've described, your use case fits in our sweet spot of providing the infrastructure for you to build on. You get the scaling of your app for free by using Kazoo, in that Kazoo presents one logical soft-switch while taking care of the bookkeeping of which media server calls and conferences actually exist on. You can setup Kazoo yourself to play with it (currently recommendation is to use CentOS[5] but Debian is coming), knowing that we have professional services and SaaS/PaaS/Iaas offerings to get you going faster as well.

Hope that helps!

[0] https://docs.2600hz.com/dev/applications/crossbar/doc/quickc...

[1] https://docs.2600hz.com/dev/applications/crossbar/doc/confer...

[2] https://docs.2600hz.com/dev/applications/crossbar/doc/channe...

[3] https://docs.2600hz.com/dev/applications/crossbar/doc/cdrs/

[4] https://docs.2600hz.com/dev/applications/crossbar/doc/device...

[5] https://docs.2600hz.com/sysadmin/doc/install/install_via_cen...

[otto_ortega]

Thanks for such a detailed answer, I will be checking 2600hz for sure, the only downside I see so far is that we will still need to use a SIP Trunk provider to connect to the telephonic network and register DIDs.

But it seems like a good option for sure, thank you for taking the time to point me to the specific parts of documentation related to the functionality we need to implement.

I will be checking the viability of using this service and contacting sales for a demo if it seems like a good fit.

[mc_]

Well, it depends. You can signup for the hosted platform and use our provided carriers (transparent to you), purchase numbers via API, manage their lifecycle, assign them to sub-accounts, etc. So if you want a proof of concept, that is definitely the fastest way to get up and running.

If/when you go full throttle and need more power, we offer custom boards that will run the infrastructure for you versus the hosted offering which you share with other tenants. And if you have your own hardware, we can install/maintain the software in your datacenters (and transitioning off hosted to one of these is done with 0 down time and transparent to your users).

And of course you can build it all yourself from the RPMs.

One thing to note is that a properly configured Kazoo cluster is redundant across data-centers so outages in one geographical area won't impact customers in other areas, and customers pinned to the down data center will fail over to the next closest during the outage.

Anyway, things to consider as you plan what your infrastructure will need to handle. These are mostly independent of Kazoo and things you'll want to think about regardless of the solution/provider you move forward with!

[otto_ortega]

Purchasing numbers via API it is something that would be very useful for us. And if you can provide us with carriers too that will be awesome (if the price is reasonable)

[e-mail] is the best way to reach you or someone in there to discuss pricing and some other details?

[mc_]

Sales will get you all the info you need and can setup further calls with engineering/operations/whomever as necessary to get you going.