Ysean: did you enable auth creds in couch but not tell kazoo about it?

otherwise, not seen 401s

Not that I recall. _users doesn't show any users in it. I even went through and manually set to allow anon requests

on the couchdb servers themselves

oh, and I'm tring to build kazoo 4.3 on centos 7 with absolutely horrible results... erland crash dumps for most of the modules it seems.

Considering centos 7 is a ghost is there going to be an update to the open source release that will permit it to compile without major pain in another distro?

i mean, you have the source for 4.3 and can build RPMs or DEBs targeting any distro you please

I'll get back to that pain later. I dont mess with git much. I may have pulled the main/master and it not compile. I'll have to check.

master won't, 4.3 branch will

But, as for the database issue... any suggestions on where I should check in couchdb or in kazoo configs? I really don't want to try to migrate data to a newly built cluster if the issue is within the databases themselves.

I'm going to guess there's no news on 5.x or updated 4.x releases going open-source during kazoocon?

marketplace is opening up to partners to list apps and purchase apps

Q2 for general availability was on one slide

which would trigger open source access to repos

cool

in couchdb 10-admins.ini there is 1 admins user the couchdb uuid and chttpd_auth secret. So, I take that as only the admin user exists

mc_ So, I just attempted to recall one of hte system internal audio files (one related to VMs) and I see a 404 in the log of 2 couchdb servers but, 200 from the 3rd. However, I still hear no audio actually being played. Would seeing 404s in all but 1 of the nodes be normal for a couchdb cluster?

If not how would I go about merging all the records on the cluster so each member node has a full copy?

Or, am I looking at having to rebuild the couchdb cluster from scratch and rebuild kazoo configs from scratch?

Ysean: silly question, but are you sure you actually have your nodes added and clustered? curl "localhost:5984/_membership" --user admin_username should have a list of nodes and then cluster nodes, if you're missing cluster nodes, something is wrong

mc_ will the marketplace be setup to allow the OS guys to purchase apps as well? What I think would be really neat would be the ability to buy hybrid-cloud capacity from 2600hz on top of whatever cluster environment we may deploy in-house.

fink, all couchdb nodes are listed.

and your cookie is configured across the nodes? (etc/vm.args)... firewall configured?

Ysean: yes, GA of marketplace means open source can purchase any apps listed there

no firewall issue and the cookie is across all nodes.

and the _admin role is still present in the permissions of your system_media db?

That it is

oh well... I may be a dummy. After doing some better log file filtering I see the 404 is while trying to access the document under the account. The successful requests come after when trying to access the document under the system_media database.

So, it may be working properly there? However, I'm not hearing anything other than static when the audio file should be playing. Incompatible/unsupported audio type (wav of all things)? Where could I check and fix that if that is indeed the issue?

Or, is the issue that kazoo is not falling back from the account database to the system_media database

Well, that's curious... I don't recall changing my admin account credentials... I don't see a document of type "user" in the master realm database but, when I try to re-create my account via cli create_account I receive an error the account already exists. I'm not able to reset the PW via the web UI.

In the kazoo.log file I see a message "unable to parse jwt: undefined" and "faile dto find a user with MD5 creds"

how could I go about fixing this via the couchdb UI?

oor sup tool

mc_ or anyone else. Would I be able to create a new top level acount (from the looks of it it will require a new realm), use that to 1) login to the UI and see if I can fix the original top level account from the Kazoo UI or 2) compare the newly created top-level account with the one that I can no longer login with and create any missing documents impacting login of the top level account or determine the password had been altered and fix it?

Ysean: there is only 1 top level account

So, what are my options when I can't log in via the account's credentials any longer?

Ysean: you could look up the account doc and get the pvt_api_key and use that via /v2/api_auth ?

Can I use the API to change the login creds of the top level account?

Ysean: yeah, use api_key to get auth token, then change password of admin user

ok sweet.

I ask dumb questions because assuming things bites me in the butt!

Thank you.

all good!

mc_ would I reference the api_key in the x-auth-token header?

Disregard, I just found the answer in another page.

Is the user password stored as the credentials hash? And, is that stored in the account document or in a "user" document?

user doc has pvt_md5 or similar key

oh ok. awesome. thank you.

Interesting... I found the user document. pvt_deleted is set to true. Shouldn't that be false?

or that key removed entirely?

Well, setting it to false allowed me log back in. Should I remove the key altogether?

alright... after doing a DB migrate and a cache flush (which probably caused my issue with my admin account) my test shows the system_sounds document requests are returning 200 now instead of any 4xx variant. However I am still just hearing white noise. The freeswitch nodes are reporting curl errors trying to curl to localhost using the port that is used by haproxy on the kazoo nodes.

Should I have installed haproxy on the freeswitch nodes as well?

I don't remember doing this before but, based upon what it's doing I may have.

i would suggest you do

Yup. That fixed it.

So, f me... I really need to update my notes.

I had 2 separate issues and my work to fix the db one may have caused the 3rd.

Anyway, thanks for all the patience mc_ and others :)

sure thing! glad its closer to good

Oh, yes... I think this one is good now. prompts are playing, the DB issue appears to be resolved and I had faxing working a while back.

BTW, I like that api key "hack" it's more convenient than going through the normal process.

What audio format(s) is supported for things like music-on-hold?

I'm trying to upload an MP3 that is just under 5MB and it's giving me a non-descript error message.

all the messages are undefined and there's a code of 0

Also, does anyone have any idea why doing recordings of greetings and such via the phone all require you to have right around 9 seconds of dead time in the beginning. Anything said during those 9 seconds are not recorded.

Also has anyone tried OPUS on the Poly CCX line with Kazoo? They seem to not play well together.

Is it possible to configure 4.3 to to post a webhook to a 3rd party with an Oauth key?

Or, would I need to put in a middle man web app to take the information from the Kazoo webhook and do the necessart Oauth stuff and hourly key turning necessary for the 3rd party system?

correct, just basic HTTP requests supported

you can embed basic auth into the URL

but otherwise, you'll need to be in the middle

ok. Thanks!