-
Posts
1,768 -
Joined
-
Days Won
4
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by mc_
-
-
Hi @Andres Gomez!
So a couple things:
1. How is your callflow for *25 configured? Did you set that in "patterns" with a regex to match? Or "numbers":["*25"]? If "numbers", that will only match the explicit *25. If patterns, make sure the regex used will match what you're dialing.
2. To return JSON from php, typically you set the header('content-type', 'application/json') and echo the JSON. Some basic PHP scripts exist that may help.
-
The server config shows you how to prefer querying database nodes in the same kazoo zone and using the other zone as a failover (hopefully minimizing WAN latency). Since couch is multi-master, even if the data isn't on a given node, the handling node knows how to retrieve it from its peers.
Each db server will have its own hostname; any on the same LAN (typically) should be in the primary list and any that live across a WAN would include the 'backup' signifier.
-
You can check out the repo to get started: https://github.com/2600hz/monster-ui-csv-onboarding
-
If there are no FreeSWITCH servers yet, you are correct that the destination sets should be empty.
When you setup FreeSWITCH and ecallmgr, there's a heartbeat that Kamailio will receive and auto-add FreeSWITCH to the proper destination set.
-
Well, I would say don't use anything until you have a firm handle on installing/managing Kazoo itself. You don't want weird Docker networking or other unrelated issues clouding your mind while learning about Kazoo.
Then you can check out orchestration tooling and containers and the like, so you at least know if an issue is Kazoo-related or otherwise.
-
The "releases" tab on the Github repo is probably your best bet. For instance: https://github.com/2600hz/monster-ui-voip/releases
-
You add extensions to the callflow root (where your DID is). You can assign as many DIDs/extensions as you like to the callflow.
-
You have the idea that a member can affect their own settings while a moderator can affect others. You can also set up conferences to start/end when the moderator joins/leaves.
-
I've passed the lack of us-central onto OPS to see if they can get something setup. Thanks for the update!
-
I would point you to the "official" docs:
https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/
https://docs.2600hz.com/sysadmin/doc/kazoo/cluster-guide/
But they should get you on the right path, yes
-
What version are you using? If 4.2, make sure you're running the latest (4.2.24 I think?).
-
Well yes, Kazoo is flexible.
If you have 0 customers, it doesn't make sense to get the beefiest hardware before you prove that you can sell your service.
So start with what's easy for you to provision and get working. So maybe that's a couple VPS servers. Then you get enough traffic that your FreeSWITCH servers are having trouble keeping up. Now you can replace the VPS running FreeSWITCH with bare metal instances on the provider. Or you can build out a datacenter rack with your stuff, get better circuits, co-locate with your upstream carriers, whatever.
So the architecture definitely grows with you as you grow the business.
-
We ran the hosted platform on small Rackspace VMs for two years at the beginning. You can certainly start small and scale up as you go.
If you plan on supporting smallish conferences only, then having lots of Pis or whatever to spread them out is fine. If you plan to support large conferences (for some value of large), beefier hardware will be needed.
You need to define the load levels you wish to support and build the architecture to support those levels.
-
Conferencing will be impacted most by the hardware you give FreeSWITCH. Run bare metal and with plenty of CPU/memory since conferences does a lot of audio muxing and transcoding. Everything else is pretty lightweight in comparison. Of course, you'll need to load test to be sure your setup is adequate. Testing max participants in a conference and max concurrent conferences to see where things go funky. Will you allow video conferencing?
-
FreeSWITCH and Kamailio are two open source telephony projects upon which Kazoo sits. They log their processing of the calls in addition to Kazoo's logging.
-
Typically there's a call-id associated with the call that can be used to grep the logs of Kazoo, FreeSWITCH, and Kamailio. Those logs are helpful in seeing what might have gone wrong.
-
I believe 4.2 is in the "stable" repo now as an upgrade option so its up to you. Running 'sup kapps_maintenance refresh' should be all you need to do to update to 4.2. Let us know if something doesn't go as expected.
-
PRs are always welcome to fix this, of course. I would venture that its not a common configuration nor should it be encouraged but if its a real need, please issue the appropriate PRs to make it happen!
-
Kazoo is API driven so I suppose if the IMS environment has a way to write adapters to talk to Kazoo it should be possible. Do you have a system in mind?
-
You'll want to take a look at the logs for Kamailio and FreeSWITCH; I bet something will pop in the logs for what's going on.
-
On 3/17/2018 at 10:58 AM, Josh Robbins said:
it doesn't work - I get a system message saying "no channels" and then she hangs up on me. This must be disabled on the hosted platform. Booooooo
If you are hearing a recording it is enabled but didn't find any matching channels.
-
@Mike Montgomery From reading the list, everything not Qubicle-related is in the open source project.
-
@FASTDEVICE this won't be possible since you won't be able to create the "internal" number properly. If you create it on the hosted platform, it gets tagged as a "local" number; as such, it would be forced outbound to the carrier, even though it exists on Account B's callflow. This prevents accounts from stealing numbers that don't belong to them and receiving calls for those numbers.
Is there a reason why account B's callflow can't have a proper DID that account A can call? As mentioned previously, that DID will not go to the carrier if it has been properly purchased and configured.
-
So when a call goes to the "Resources" callflow action, stepswitch (the app) figures out what carrier(s) to send the call to, right? But first it checks that the dialed number is not already existent on the system; if the number is found and it isn't forced offnet, stepswitch will hairpin the call back into the system for processing. So any numbers known to the Kazoo system will stay local unless forced to go out.
So you could define an "internal" prefix of "+abc" and when you create your callflows, you create an "internal-to-kazoo" DID for that callflow as well. Now your Pivot app returns {"module":"resources", "data":{"to_did":"+abc1001"}}. Since you setup Account B's callflow to include "numbers" :["1001", "+abc1001"], and "+abc1001" is in the number database, stepswitch will hairpin the call to Account B.
This is a hack! But if you accept the headache of managing this, it could be a way to accomplish your goal.
caveat emptor
Using X-Lite Softphone with Kazoo
in PSTN, Software, and Services
Posted
Hmm, not sure where the problem is.
I would debug your PHP code as your JSON works fine for me using cURL.
If you are getting a response back from the server, use the request_id to grep the server logs and see what it says (in debug mode).