mc_

By "funny money" I mean when you want to issue a service credit to your customer, say give them $20 for whatever reason, there's no credit card to charge or otherwise. It's just you updating their ledger with some "money". "real money" is when a CC is processed and those funds are added to the account to pay for services.

Could be a ulimit issue? Check those settings, make sure you have enough file descriptors...

Possibly permissions on the database files themselves (I think they're under /srv/dbs ?). Try accessing a single bigcouch node and see what its logging. Also, n=4 (or any even number) is problematic in a network split. It is generally good to have n be odd to make it more likely to have a majority on one side of the split.

As the SSO stuff is still a work-in-progress, the docs are evolving as we go. We have an internal doc for setting it up but there are still a lot of details to work out before it is ready for release to the broader community. Of course, if you are familiar with the SSO flow of OAuth you can probably figure it out but a comprehensive guide is not currently ready for release.

jonny5 is a reference to the movie Short Circuit; the kazoo app tracks limits and balances for accounts and does authorization for resource-consuming calls. In other words, it short-circuits calls that are not authorized :p For numbers, check out https://docs.2600hz.com/dev/doc/internationalization/numbers/ You'll probably want alternative prompt languages too: https://docs.2600hz.com/dev/doc/internationalization/prompts/ While most of the 2600Hz team is US-based we do have a number of devs outside the US as well as a group of community members outside the US too. We all want KAZOO to be a proper platform for any region of the world. That said, we also know we have blind spots of how telecom is done everywhere so any feedback you have which can be incorporated into the project for everyone to take advantage of, is greatly appreciated. Also, when you feel you need to look at code or the docs aren't sufficient, ask here in the forums - that's usually a good trigger for someone to take a stab at improving the documentation. You are always welcome to submit PRs for improved docs as well.

For support, free options include this forum and IRC; you can email sales@2600hz.com to see about dedicated support plans. For open-source builds you are probably best served with the 'dev' docs site: https://docs.2600hz.com/dev/ Also the 'sysadmin' docs site: https://docs.2600hz.com/sysadmin/ Both are great places to contribute to the project if Erlang code isn't something you want to take on at the moment.

You "use" DIDs by assigning them to an account and creating a callflow in the account to run when receiving calls for the DID. There are no zone restrictions on that.

I believe rating will debit via ledgers but things like auto top-up and such use transactions

Check /opt/kazoo/lib for a jonny5 folder. If it doesn't exist, see if 'yum install kazoo-application-jonny5' works

I think you need to use `ledgers` for "funny money" and transactions for "real money" stuff.

Kazoo sets the Content-Type header in the response to the mime type of the binary data. Typically it will be "audio/wav" or "audio/mp3" but will depend on how the audio was uploaded.

Crossbar will use the 'Content-Type' header you provide when uploading the media binary data.

Hi @Avneet Singh The files should exist as attachments on the media doc ({MEDIA_ID}) in the account database.

Number states can be read about more here: https://docs.2600hz.com/dev/core/kazoo_number_manager/doc/number_states/ I'm not sure what monster-ui uses to determine "spare" vs "in-use"; @azefiel ?

@Josh Robbins Ladder diagrams and MOS scoring are still on the roadmap; I don't have specifics though.