Skip to content

KAZOO Support Channels

This documentation is curated by 2600Hz as part of the KAZOO open source project. Join our community forums here for peer support. Only features in the docs.2600hz.com/supported space are included as part of our 2600Hz Support Services plan.

Maintenance

Callflow Maintenance#

About The Maintenance Commands#

The maintenance module defines a set of functions useful to sysadmins for adjusting how the callflow app operates.

lookup_endpoint/{1, 2}#

blocking_refresh/0]).#

refresh/{0, 1}#

migrate_menus/{0, 1}#

migrate_recorded_names/{0,1}#

show_calls/0#

call_count/0#

flush/0#

account_set_classifier_inherit/2#

account_set_classifier_deny/2#

all_accounts_set_classifier_inherit/1#

all_accounts_set_classifier_deny/1#

device_classifier_inherit/2#

device_classifier_deny/2#

list_account_restrictions/1#

update_feature_codes/{0,1}#

allow_authz_context/{1,2}#

When processing route requests, the default context of the call does not permit unauthorized calls to make use of the no_match callflow. Some Kazoo applications will set the context used (say during a blind transfer) to note that this particular route request should be authorized to use the no_match callflow.

sup callflow_maintenance allow_authz_context {APP_NAME} [{AUTHZ_CONTEXT}]

If {AUTHZ_CONTEXT} is omitted, the value will be read from {APP_NAME}'s system_config document (using the authz_context key). If the key is missing from that document, a default random hex string will be set in the app's config and used in the callflow doc.

deny_authz_context/1#

Remove an app's authz_context from the allowed authz contexts

sup callflow_maintenance deny_authz_context {APP_NAME}

{enable,disable}_authz_context/0#

Toggle whether to allow callflows to check the route request's context and compare to allowed authz_contexts for no_match access.

sup callflow_maintenance enable_authz_context
sup callflow_maintenance disable_authz_context