mc_

Please verify what version you installed. The last time "whapps_controller" was a thing was...years ago. https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/

https://freeswitch.org/confluence/display/FREESWITCH/Hangup+Cause+Code+Table

e3ca0806-54a5-4edc-9b4a-1935151964cb|j5_hard_limit:65(<0.2907.0>) inbound_channels_per_did_limit AccountId: <<"2d54787d167f74af8ef1055e8cd4998b">> ToDid: <<"6601">> Used: 1 Limit: -1 Limit: -1 suggests unlimited trunks. The account appears misconfigured.

I just see calls to extensions 6601 and 6602? What am I missing here? Limits only apply to call legs that involve a "resource" which is an upstream carrier for most folks' use cases. You'll need to dial DIDs to exercise the account limits

@huwsc90 your best bet is to look at FreeSWITCH's supported endpoints as all the audio muxing will be done there. Verto is an option for sure. Or you can do pure WebRTC+SIP using Kamailio as the wss server.

@louyingge there is not a way to track channels going to a particular carrier and use a different carrier if some threshold is reached. You can limit an account's channel count going to/from carriers. Could be an interesting feature if you wanted to sponsor it though!

@huwsc90 Its mostly in the form of JSON schemas for the payload formats. Most of the info will be in the source (which hopefully is readable for what you're wanting, even not knowing Erlang). For instance, a route request to setup a call involves the 'req' payload published to all bound queues, each of which will respond with a 'resp' payload if able. One 'resp' payload will "win" and receive a 'win' payload back on a direct queue. https://github.com/2600hz/kazoo/blob/master/core/kazoo_amqp/src/api/kapi_route.erl In there you'll see the 'req_definition' which will list the JSON keys (named headers) of the payload, the routing (and binding) keys used for publishing/binding, etc. https://github.com/2600hz/kazoo/blob/master/applications/crossbar/priv/couchdb/schemas/kapi.route.req.json In this directory, you'll see auto-generated schemas. "kapi.route" maps to "kapi_route.erl" for instance, and the 'req' payload. Should at least get you started, get a queue bound to AMQP for messages, and you can start inspecting things.

@Gagan KAZOO has no control over the format of the INVITE's RURI; that is generated by the sending side. Can you clarify why you need E164 format? What are you trying to do with the call?

If you built this from source, make sure all the deps/ built properly (should be listed in make/deps.mk). You can stop the release, do `make sparkly-clean compile build-dev-release` to clean everything out, fetch all deps, recompile everything, and build a development release. Then `make release` will start the dev release. Other things to check are that you're compiling with the correct version of Erlang (see make/erlang_version).

If this is a new system, yes, KAZOO should initialize relevant databases and configure the default list of apps to start automatically. You'll want to bump log level (typically syslog) in /etc/kazoo/core/config.ini to debug, then restart the VM and see what happens, why the default apps weren't started. Could be a temporary issue too (though I routinely reset my database cluster for dev and don't have issues with the default apps starting).

https://docs.2600hz.com/dev/applications/crossbar/doc/filters/

Hard to say why the other apps aren't starting offhand. Consult the logs from startup. You can manually start with 'sup kapps_controller start_app {APP_NAME}'

Hi @Beka Gelashvili When I'm testing alternative FreeSWITCH instances, I use: sudo FS_BIN=/usr/local/freeswitch/bin/freeswitch /usr/sbin/kazoo-freeswitch start -nonat This starts FreeSWITCH in the foreground so if you exit the console, FreeSWITCH will stop. You can use the -nc flag to put FreeSWITCH in the background and use fs_cli to connect that works better for you.

Hi Alex, First, I would recommend https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/ I'm not sure if the powerpbx guide is still updated or not, but our guide covers similar ground and is updated as folks encounter issues. It is backed by a public Github repo as well for all to contribute. As for your issue, KAZOO (and most SIP setups) use the domain portion to figure out what account to associate with the caller. In your case, it is unlikely you created an account with a SIP realm of Kamailio's IP address. You will need to configure zoiper to use the SIP realm of the account and, if the domain doesn't resolve to Kamailio's IP address, you will need to configure zoiper to use an outbound proxy (or zoiper's equivalent) to point to Kamailio's IP. You can read https://docs.2600hz.com/user_guides/doc/manual_phone_config/zoiper/ Might help; adjust realm and outbound proxy to your setup

HI @vageesh welcome! It is hard to say but it appears that you've misconfigured the API url. Your API responds with an appropriate error with 'curl -v -X PUT http://143.110.176.191:8000/v2/user_auth' So check your monster config.js and ensure the URL is similar to this ^