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_
-
-
Check /etc/kazoo/bigcouch/local.ini the database_dir config: https://github.com/2600hz/kazoo-configs-bigcouch/blob/master/bigcouch/local.ini#L16
-
The API is the callflows API. These are actions within the "flow" of a callflow.: https://docs.2600hz.com/dev/applications/crossbar/doc/callflows/
About callflow structure: https://docs.2600hz.com/dev/applications/callflow/doc/
-
Your best bet for a system reset is, on each couch server, delete everything in /srv/db then restart kazoo-bigcouch. Then restart kazoo-applications to re-initialize system databases.
-
Also, is the network between the zones experiencing issues? Could be a failure to communicate and sync with the other zone.
-
I can't answer an ETA as its outside my purview; I can only say that I'm very annoyingly asking the same questions internally. I have assurances that code/applications in 4.3 will resume their open status in 5.x when we're given the go-ahead.
-
On 4/4/2022 at 4:28 PM, Bitrate said:
Greetings and thank you for making such a great open source project!
We're also using the open source version and are interested in purchasing apps from you guys. Whats going on with this and the open source 5.0 release? Also, whats the timeframe on the 4.3 re-release with all the apps?
4.3 remains open. Aside from high priority bug fixes and such, that branch is "done". So the latest 4.3 RPMs represent the end of the line for that development.
For 5.0 + purchasing private apps, there should be annoucements at this year's virtual KAZOOCon. We're anxious to get 5.0 back into public repos but want to make sure as many issues are ironed out before doing so.
-
@jeroen what version of KAZOO are you running? Your log line numbers don't match up to recent 4.3 so its hard to say if your crash has been fixed already.
-
The virtual KAZOOCon this year should have some announcements in that regard.
-
Have you compared the call logs of the working and non-working calls? I'm surprised the a-leg's CAVs have your value in the answered call, and don't have the CAV in the unanswered. I would expect the CAV to be set on the a-leg even before the PIVOT request is made. Of course, click2call might be messing that up since it does use loopbacks.
-
Any in particular? A few are exported across the bridge but most pertain to the leg itself and shouldn't be exported. You can see the bridge strings have the exported CCVs on them when creating b-legs.
-
-
use_local_resources:true will check the account for carrier docs; use only if the account itself has carriers defined.
DIDs on the system are forced outbound by either carrier module = knm_local OR "force_outbound" set to true (I think just those two).
Try `sup stepswitch process_number {DID}` and see if the output includes forcing the DID offnet. If using local resources, I think you can add the account ID as an argument after {DID}.
-
When the endpoint with "push" settings is being built, the code doesn't know yet if the SIP device itself is registered or reachable yet. So the "push" options are delayed 5s to allow the SIP device a chance to be contacted. If there's no registration or the network doesn't work to deliver the call to the SIP device, the "push" device is called (meaning push notification sent and Kamailio is ready and waiting for the SIP device to register its new location on the network.
-
When you have push configs on a device, KAZOO will create two endpoint configs for FreeSWITCH/Kamailio - the "real" device and the "push" device. KAZOO gives the "real" device 5s to answer the call before initiating the push notification to allow for network shenanigans.
-
These are MODBs: https://docs.2600hz.com/dev/core/kazoo_modb/doc/
They are critical to KAZOO usage, so there's no disabling of them. If the MODB doesn't exist when a document (like a CDR) needs to be saved, the MODB will be created. If you have a lot of activity, they'll all stack up waiting for the MODB to be created.
What you can do is configure the MODB task (https://docs.2600hz.com/dev/applications/tasks/doc/modb_creation/)
Set that to pre-create the next month's MODB for all accounts and give it enough lead time (say 3-5 days depending on how many accounts you have); the task will automatically spread out the MODB creations across that time period to hopefully minimize impact on the DB cluster.
-
Don't think so, offhand. There's a 'set_audio_level' FS command that could be useful? If you want to try it out and let us know, we can look into incorporating it
-
As far as I recall, KAZOO has some facility for coverting wav<->mp3 but that is rudimentary and I think only for uploading media through the API. Your best bet is to fetch the recording and convert it on your server.
-
You'll likely need to tinker with FreeSWITCH settings; I'm not sure if alternatives are supported though. Probably post-recording format conversion will be needed.
-
A basic intro to the API and setting up devices and carriers: https://docs.2600hz.com/sysadmin/doc/install/configure_kazoo/
From there, check out the bigger collection of Voice APIs: https://docs.2600hz.com/dev/
KAZOO does not have LCR capabilities, just basic ratedeck support. Most folks setup LCR servers as a carrier for KAZOO to route through when needing that functionality.
-
KAZOO does not do outbound registrations, meaning it will not register to your peerless account.
One way would be to create a "device" in KAZOO to represent the peerless system and have peerless register to KAZOO (if possible). That would allow extension dialing.
You can also create peerless as a carrier in KAZOO and accept inbound calls from it (peerless IP(s) need to be in the ACLs); but you would need to setup E164 numbers on your callflow. So a little more complicated but would set you up to accept traffic from other carriers as well.
-
You'll need to investigate the db side (maybe check HAProxy logs too). Is couch on a public IP? Maybe someone is messing with you?
Check kazoo logs, make sure you aren't inadvertently deleting the account through some automation gone wrong.
-
Yeah we currently have to deploy those apps to trusted environments to prevent piracy. The app exchange will include a distribution mechanism to handle this better.
-
You can also find out more here: https://forums.2600hz.com/forums/home/
-
The plan is to re-open-source all the applications and core that 4.3 currently has (so apps like Crossbar, Teletype, Ecallmgr, etc).
One lesson from the 3.22->4.0 upgrade we learned was people will try the new stuff before its officially ready, encounter issues and complain, and revert back to 3.22.
The other complaint is that we want to address is from open-source folks wanting to purchase our closed-source apps (like our call center app qubicle). Due to the nature of how the Erlang VM works, this isn't really do-able via "rpm install" methods.
So we've taken more time to develop 5.0 behind the scenes so folks don't start using it and lose confidence before it even has a chance. We've been upgrading our clusters with it to iron out upgrade-related bugs, accidental backwards incompatibilities, and the like. Concurrent with all this is the app exchange and a mechanism to deliver closed-source apps like qubicle to open-source clusters.
copy of couchdb every first of the month
in Product Discussion
Posted
What is KAZOO doing at this time? There are routines that run monthly for updating account balances and things like that; could also be that your server is underpowered