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_
-
-
Single-server installs are proofs of concept, for testing/instructive purposes, do not use in production, here be dragons!
There are two common "minimal" installations:
- 2 zones, 4 servers per zone - in each zone, 2 bigcouch servers, 1 kazoo/kamailio/rabbit, 1 FreeSWITCH
- 1 zone, 7 servers - 3 bigcouch servers, 2 kazoo/kamailio/rabbit, 2 FreeSWITCH
But the big one is to have 3+ servers for bigcouch from the start.
-
There's a page from a while ago: https://docs.2600hz.com/dev/applications/crossbar/doc/securing_crossbar/
It shows setting up a self-signed certificate but you can just skip to where the guide configures Crossbar. Should work as expected once you restart Crossbar.
Another option is to use HAProxy or similar in front of Crossbar to handle SSL termination.
-
Hi @Syed Hasan!
Most of the docs around the APIs (such as devices) include example cURL commands to get you started. Most languages have HTTP clients so you should be able to start playing with the APIs using your client of choice in your language of choice.
I'm not aware of any pre-existing Java SDKs for Kazoo's APIs though. We're obviously happy to help answer your questions if you want to provide one to the community though!
-
Certainly we need to know these use cases that are failing for you so Kazoo can be more robust in the face of the errors. Mind filing tickets for each of these so we can investigate and get some fixes in?
I don't think there's a limit on URL-based files; just that you will see a delay on calls that hit a FreeSWITCH server with a cold cache. Shoutcast streams are a nice alternative as I believe FreeSWITCH will just stream bytes as needed during the call vs fetching the file in full before playing, but providing the stream is a different experience vs providing a file.
This is good feedback and I hope we'll see some tickets come in where we can coordinate this work! Thanks
-
If you change the MP3 at mydomain.com/file.mp3, there is nothing to tell Kazoo that the media changed. I don't think FreeSWITCH will do HEAD requests or use HTTP headers to determine whether to download again.
You can upload the media file to Kazoo instead; if you replace the attached MP3 it should cause the media to be flushed from the underlying systems.
I can't think of a programmatic way to flush the URL though...
-
@Bartimaeus try again!
-
Sponsor-able by anyone. I believe the development rate is affected by whether the work will go into the open source Kazoo project or be a closed source project specifically for you.
Contact sales@2600hz.com to get more information on sponsorship and your options there.
-
Thanks for the alert. Looks like the cert expired. Forwarded to operations.
-
You can setup a device to auth by IP address by setting the device's "sip.ip" and "sip.method" = "ip".
-
Your best bet is to start here: https://docs.2600hz.com/dev/applications/pusher/doc/pusher/
-
Each documentation page should have a Pencil icon in the top-right corner. Clicking that will bring you to the Github, to the repo and markdown file that backs the doc site. If you are signed into Github, it should be a page with Github's WYSIWYG editor to make your changes and submit a pull request.
Look forward to your suggestions!
-
Appears that RFC 4662 is on the roadmap but no timeline afaict. It is sponsor-able though, so if its the only thing holding you back, that could be an option too.
-
Hooray! A win for the day :)
-
You could create a menu that has the password as one branch, going to the page group and a default branch going to a recording. You may have to use the API to set that up as I don't think you can configure menus in the UI with multi-digit branches.
-
AFAICT Kamailio supports RFC 4662 (https://www.kamailio.org/w/interoperability/)
So Kazoo should support it or adding support should be straightforward. Can't speak authoritatively on that though; have you tried it?
-
Perfect! Thanks
-
OK, mind filing a feature request in JIRA?
-
If on your own system, you can configure the minimum and maximum recording time in system_config, see https://docs.2600hz.com/dev/core/kazoo_voicemail/doc/README/#system-config-settings
I'm not sure what the hosted system's setting is; you could file a support ticket to find out.
-
Sweet, glad it is working!
-
Did you try the play callflow like this?
{"module":"play" ,"data":{"id":"/{ACCOUNT_ID}/{MEDIA_ID}"} ,"children":{...} }
-
If you upload media to Kazoo via the API, you can reference it in the "play" callflow with "/{ACCOUNT-ID}/{MEDIA-ID}" I believe
-
There is a simplistic quickstart guide that will show you some basic API commands.
Endpoints dial numbers, some endpoints carry around a caller ID so you "know" who is calling. Numbers are assigned to callflows which determine what to do with the caller - put them in a conference, connect them other endpoints, play a recording, put the caller in a conference, etc.
Triggering calls from a website typically requires using Click-To-Call. You can also front the request with your own server and call the conference dial command from your server.
-
Community-supported call queue app is acdc - open source, free to use on your own installation.
Qubicle is our paid call center application. There is talk of a "lite" version being free to use / open source but nothing available yet. When the app store is ready, there will be a way to purchase Qubicle for self-managed installations.
-
Please open a new thread and include logs related to the registration attempt, how you created the device and callflow, and anything else that might be relevant.
Scaling from single server
in 2600Hz Mobile
Posted
The clustering guide will get you started.