mc_
-
Posts
1,796 -
Joined
-
Days Won
4
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by mc_
-
-
Is the system_configs endpoint enabled? Its off by default
-
@huwsc90 Hi!
One guess is that the auth-by-ip information has left the cache and has to be pulled from your database. This process is delayed long enough that the reorder app's response of Nope Nope Nope is received first. Subsequent calls then work as expected as the cache is primed.
Compare logs of the first call that fails against the subsequent call that succeeds to see where the slowdown might be (thinking stepswitch_inbound and related processing to resolve IP to account).
-
I'm trying to get an "official" doc on this but my understanding is 2600Hz and Signalwire have agreements to let 2600Hz distribute the newer versions of FreeSWITCH with KAZOO but that Signalwire releases the source on a delayed basis. Something to that effect, anyway. So yes, packages from us will reflect more recent work in FreeSWITCH than is available via their github.
When I have an "official" doc, I'll get it posted here for everyone.
-
Yeah, there are a number of ways to do it. Most use the e164 converters; see https://docs.2600hz.com/dev/doc/internationalization/numbers/#converters
-
In KAZOO, a "dialplan" allows configuring ways to adjust the dialed number. For instance, in the US of A, you could dial a local number without the area code; with dialplans, KAZOO can adjust that 7-digit dialed number to the full 10-digit (or full E164) version before Callflows processes it. But dialplans are not a "typical" feature folks tend to use.
-
404 on your link so just in case: https://docs.2600hz.com/dev/doc/internationalization/numbers/
I think your sentence-ending period got linked as well, throwing off the URL.
If you have used FreeSWITCH before, KAZOO doesn't use the dialplan XML - every call is handled in real-time by KAZOO. The primary call processing app is named 'Callflows'.
From an API perspective: https://docs.2600hz.com/sysadmin/doc/install/configure_kazoo/
You should get a device, number, callflow, and resource setup and make calls using that.
If there are specific parts of the docs that don't work for you, you can use the Edit (pencil icon) which should bring you to the github repo that backs these doc sites if you have suggestions. If a command fails, please include the command tried and the output; we can help see if the docs are wrong or your invocation.
-
Resources do not register to upstream carriers, as this would break the resiliency of the platform for that carrier. Most carriers allow you to specify a list of IP addresses to deliver calls to (should be your Kamailio IPs). If the carrier you are using requires registration, there are some old old instructions floating around to setup a FreeSWITCH config to force the registration to proxy through one of your Kamailio servers. Or you can setup a vanilla Kamailio to register to the carrier and setup your vanilla Kamailio as a "resource" in KAZOO.
You'll find the "resources" API here: https://docs.2600hz.com/dev/applications/crossbar/doc/resources/
Suggestion that you don't manipulate the CouchDB databases directly; the API server code (Crossbar) does a lot of things in addition to accepting API requests and putting them into the database. The handful of things that do require db access are typically one-offs, set it and forget it type things.
And welcome! We're always open to improved docs if you have suggestions and PRs! Let me know when you want to start learning Erlang too ;)
Oh, and if an API doesn't seem to work, make sure it is running on the API servers: `sup crossbar_maintenance start_module cb_resource_selectors` for instance. Just prepend "cb_" to the API endpoint's name for the Erlang module to initialize. This should add it to the list of modules to start as well.
-
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/
-
-
Something is amiss, then, as the channel bindings are put on the 'webhooks_shared_listener' which uses a named queue, shared by all instances of the webhooks app.
The bindings are not federated so other zones should not be receiving copies either.
So my guess at this point is you have two webhooks configured and enabled for the same HTTP server, causing the duplication.
-
PRs to https://github.com/2600hz/kazoo-sounds/tree/master/kazoo-core
Would be great to improve the prompts available to all KAZOO users!
-
Not seeing the crash in kz_hooks_util though, so that's good! But yeah it does appear that konami decides to exit after the bridge occurs. Hopefully the community can patch the behaviour to correct this!
-
@Marcin Muzylo the patch was applied 4 months ago: https://github.com/2600hz/kazoo/blob/4.3/core/kazoo_events/src/kz_hooks_util.erl#L144
Can you get the new crash / stacktrace?
-
"direction" will be relative to FreeSWITCH so "inbound" means a user agent started the SIP dialog (aka FreeSWITCH received the initial INVITE) while "outbound" means FreeSWITCH is initiating the comms (aka FreeSWITCH sending the initial INVITE).
I believe the CDRs API will return user-specific CDRs using /v2/accounts/{ACCOUNT_ID}/users/{USER_ID}/cdrs: https://docs.2600hz.com/dev/applications/crossbar/doc/cdrs/#variations
Call recording has its own API: https://docs.2600hz.com/dev/applications/crossbar/doc/recordings/
Voicemails are under the vmboxes/{BOX_ID}/messages: https://docs.2600hz.com/dev/applications/crossbar/doc/voicemail/
No grand unified APIs; each API is focused on the collection or entity described, generally speaking.
-
"direction" tells you, relative the FreeSWITCH, how the call started. So "inbound" says the call started from the UA - the UA sent an INVITE "inbound" to FreeSWITCH. "outbound" would be FreeSWITCH sending the INVITE to the UA (device, carrier, whatever).
Not sure on your recordings question other than look for the recording and storage related logs ("kz_att_s3" would be a good key in the log lines, for instance).
-
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.
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.
-
Whitelabel 404 errors are expected and fine, you haven't configured any yet.
If you want to run some APIs youself: https://docs.2600hz.com/sysadmin/doc/install/configure_kazoo/
Otherwise use SmartPBX to create a device, then register your phone to your account and try a test call.
-
@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?
-
Check the startup logs in /var/log/kamailio/kamailio.log and see if it suggests anything? Could be that vanilla Kamailio started and bound for the IP/port already. Try stopping kamailio (not kazoo-kamailio) if so.
-
You may want to expand the log lines returned by the status command there to see what exactly caused the main process to exit.
Kazoo Version 5 open source
in General OS Kazoo Questions
Posted
Not currently. We've rolled 5.0 out to our hosted platform and select customers to iron out the technical challenges with 4.3->5.0 upgrades. The app exchange is in active development, which I believe is the last component to the release of the open-source components of KAZOO.