mc_

@simonp22 all tests work in my environment. What version of KAZOO are you running? I recommend updating to the latest 4.3 and trying again.

@simonp22 no haven't had a chance to try it myself. Let me see how my day goes; I may have a couple minutes this afternoon to setup a test. Thanks for the reminder.

No, 5.0 hasn't been tagged yet. The master branch represents 5.0 at the moment but is not considered "stable"; 4.3 remains the suggested install version. Hopefully by the end of the summer we'll tag 5.0, do the breakening, and all that jazz.

Umm, kazoo-mk is not the new build method (it explicitly states a temporary repo to explore ideas for a new build system). The breakening has not officially happened; much more fanfare and announcements will precede the actual event! For now, master/5.x is being developed in the regular kazoo repo. More to come!

I just checked and I'm pretty sure `/{ACCOUNT_ID}/{MEDIA_ID}` will work (at least in my tests of the underlying code paths). Add the preceding slash and you should be good to go.

@Jack Noe ah, I see. Entering the PIN on the voicemail callflow restricts the length to 6 digits. But this is out of sync with the schema, hence the confusion. The reasoning for the restricted length was to keep people from using their phone numbers as their pin but that restriction was encoded as a system_config value instead of updating the schema. Talking internally about path forward here to fix the issue. File a support ticket if you'd like to lobby for a higher limit.

The schema allows for 4-15 length pins: curl https://api.zswitch.net:8443/v2/schemas/vmboxes | python -mjson.tool ... "pin": { "description": "The pin number for the voicemail box", "maxLength": 15, "minLength": 4, "support_level": "supported", "type": "string" }, ... Where are you seeing the error?

Looking at https://docs.2600hz.com/dev/applications/crossbar/doc/voicemail/ Appears "pin" must be a string of length between 4 and 15. What version of KAZOO are you trying this on?

Can you pull debug kazoo logs of a call attempt? Would be helpful to see what was tried.

The system_media prompts are intended for the pre-built callflow actions, such as the voicemail prompts, and aren't generally meant for account-level usage. Does that make sense? Instead, you would upload a media file to the account (or a reseller/master account) and reference it with `{ACCOUNT_ID}/{MEDIA_ID}`. You can also try `"greeting":"/system_media/{PROMPT_ID}"` in the JSON if you really want to use a system prompt in a menu callflow action. I think it might work but buyer beware!

@Rick Guyton the change occurred in KAZOO, in how the data was sent to the provisioner service. The PRs have been issued and merged. Hotpatches to hosted will be scheduled when OPS can do it; not sure on the timing.

PR - pull request on the git repo. Once the PRs are opened and merged into the 4.3 and master (5.0) branches, new RPMs will be created containing the fix. We'll also likely hot-patch the platforms we manage to alleviate the issue. Timing for the updates/hot-patches is unknown until the PRs are accepted and we see what the OPS workload is. But we'll update here when things are live on the various systems we manage.

Consensus is to revert back to the pre-existing functionality and let you guys continue to operate as you did before this change. Look for PRs for 4.3 and master in the next day or two.

We're meeting about this today. Should have an idea of what next steps are then. Sorry for the disruption; hopefully things will be sorted out and a proper announcement can be sent around all this.

You can also accomplish this via API: https://docs.2600hz.com/dev/applications/crossbar/doc/voicemail/#change-a-message

I think you will want to check out our architecture page: https://2600hz.com/architecture If you can ask questions using more general terminology instead of AVAYA-specific, that would probably help us find you the answers you're looking for!

@wolfru68 Thanks for the translation I'm not entirely sure but I think the AVAYA concepts map to KAZOO as such: SES(SIP Enablement Services): KAZOO provides SIP connectivity via Kamailio and FreeSWITCH, with KAZOO providing the high level routing logic to those components. So if you stand up a KAZOO instance with all the components (via the install guide as mentioned earlier in the thread) you will be able to provide SIP connectivity (trunking, PBX, etc). ACM (G650) (Aura Communication Manager): Again, appears to be providing SIP services (like PBX functionality). This is built into KAZOO. Typically you will create SIP devices, create numbers and callflows for what to do when the numbers are dialed. The callflow actions are things like IVR menus, routing to devices, users (all devices owned by that user), upstream carriers, playing prompts, directory services, etc. AIC (Interaction Center): As far as I can tell, this is contact center functionality which 2600Hz provides to partners via Call Center Basic and Call Center Pro (the KAZOO app is called Qubicle in case you've seen that name floating around). There is a community-maintained call queues app called ACDc as well. VP(IVR): IVRs are definitely build-able via callflows. You can also use Pivot to make an HTTP request to your server on each call to dynamically build the IVR. Call Center Basic/Pro provide specific prompts for wait time and other announcements when waiting in queue. AES (Application Enablement Services): Basically APIs to control stuff. Yes to all that. KAZOO is built from day-one to be API driven. See https://docs.2600hz.com/dev/ Hope this helps a little?

@Kirill Sysoev can you help @wolfru68 translate this to English? I assume he wants help with KAZOO vs Avaya PBXes (based on Google Translate).

@Noah Mehl has the patch to FreeSWITCH been backported to the version installed alongside KAZOO 4.3? AFAIR the uuid_fileman stuff wasn't working prior to the fix in FS master, no?

@Rick Guyton are you thinking there should be a menu option during playback to read back the caller id number?

@It_panda welcome! You'll want to get a single-server install up first: https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/ Once you are comfortable playing around with it, check out setting up a cluster: https://docs.2600hz.com/sysadmin/doc/kazoo/cluster-guide/ And of course, if you like, you can contact sales@2600hz.com to see about paid support in setting up and maintaining a cluster too. Feel free to ask questions here in the forum as you encounter things!

Hi @Jim_PGi you might need to make manual calls to the presence API. I'm not sure if this is exposed in the UI though. See https://docs.2600hz.com/dev/applications/crossbar/doc/presence/#reset-presence-state

Take a look at the clustering guide: https://docs.2600hz.com/sysadmin/doc/kazoo/cluster-guide/ I would recommend upgrading to 4.3 and see if these issues persist. If they do, then we can dig into the nitty gritty and figure out if its kazoo, environment, combo, or just gremlins!

As the SSO stuff is still a work-in-progress, the docs are evolving as we go. We have an internal doc for setting it up but there are still a lot of details to work out before it is ready for release to the broader community. Of course, if you are familiar with the SSO flow of OAuth you can probably figure it out but a comprehensive guide is not currently ready for release.

jonny5 is a reference to the movie Short Circuit; the kazoo app tracks limits and balances for accounts and does authorization for resource-consuming calls. In other words, it short-circuits calls that are not authorized :p For numbers, check out https://docs.2600hz.com/dev/doc/internationalization/numbers/ You'll probably want alternative prompt languages too: https://docs.2600hz.com/dev/doc/internationalization/prompts/ While most of the 2600Hz team is US-based we do have a number of devs outside the US as well as a group of community members outside the US too. We all want KAZOO to be a proper platform for any region of the world. That said, we also know we have blind spots of how telecom is done everywhere so any feedback you have which can be incorporated into the project for everyone to take advantage of, is greatly appreciated. Also, when you feel you need to look at code or the docs aren't sufficient, ask here in the forums - that's usually a good trigger for someone to take a stab at improving the documentation. You are always welcome to submit PRs for improved docs as well.