Joseph Watson

When i try to pull /accounts/{account_id}/service_plans I get a 404. So I need to start something in order to use service plans?

Hey everyone, I am running into this as well. I built a "hack" we call the UC Proxy which allows this. But if we wanted to be able to allow multiple registrations on some device types, how hard would it be to modify kazoo to allow for this?

I am support interested in helping to test. Let me know what we can do to be of assistance.

So I have an update. After doing some debugging, I found that the customer just deleted the AWS Access Key. I attempted to update the storage plan with a new key, but it appears that kazoo is still looking for the old key. What can I do now? kz_att_s3:271(<0.17218.4495>) S3 error: {aws_error,{http_error,403,"Forbidden",<<"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>AKIAJXP6D4AAZFZOJ2YA</AWS

any idea what a script like that would look like. Honestly I am not support wonderful with couchdb. So any help would be fantastic

The permissions are set fine. New recordings are going into the bucket, and we can access them via the API. Its any recordings we transferred from the old bucket over to the new bucket we have an issue with. I need to somehow update those records so they reflect the right bucket or something. There has to be a sup command to do this.

bump!

Hey there, I have a storage plan configured which points to an AWS bucket we configured for a customer. That customer now wants to host their own bucket which is fine. We transferred any recordings or files to the customer's bucket, but now when you try to access the files via the kazoo api, it fails. Do we need to "update" something somewhere since we change the bucket? Thanks, Joe

that commit for master was MAy 14th. I know stuff has been committed since

Well that's good to hear, but what about us that are doing active development in 5.0 and trying to get PRs pushed and stuff. What happens now?

I regularly watch the github repo for kazoo, and I just noticed that all of the 5.0 branches are now gone. A friend told me that he got an email from Patrick saying kazoo 5.0 will now be closed source. Is this true?

Hey @SIPGuy what app are you using for setup your queues? As for managing your callflows, there is a open source version of the callflows app which contains all of the ACDC actions you will need, you can find it at https://github.com/OpenTelecom/monster-ui-callflows-ng. Good luck

I was just going to tell you, This looks like it could be an issue making quorum. In order for new DBs to be written to the cluster you need to have a quorum. If you have a node that's not responding correctly it can cause issues with the data handlers waiting for a response. Also if you are doing cluster replication over the WAN, that could be an issue as well if the nodes are to far apart and have high RTT. If that the case you may want to think about configuring your node into zones, which is a short term solution. Really doing cluster replication over WAN/Internet is not a "great" idea.

Is there away to run this App with Monster UI, or do you have to manage everything in Kazoo UI?

Hey, Does anyone know if there is a Monster-UI App for ACDC?