In this section:
The Configuration Workflows and Templates object:
A configuration template workflow is a sample configuration that guides you through the process of data entry for a particular scenario. The sample configuration includes default values for some of the settings - you can accept or override these settings before loading the workflow onto the SBC.
On the SBC main screen, navigate to Configuration > Configuration Wizards. The Configuration Workflows and Templates window is displayed.
The EMA workflow is sourced into two different types. This is indicated by the Source column in Configuration Template Workflows.
To launch the workflow, click in the Launch column.
To delete the workflow, click in the Delete column.
You can delete only user-added workflows.
This section describes the navigation of workflow and commands associated with it. After launching the workflow, the workflow home page opens.
After launching the template workflow, a new screen opens with the workflow title and the steps associated with it.
Navigation is sequential - you can navigate to the next step or previous step. You cannot skip a step.
These steps are provided to give an overview of the current workflow process and to inform you about any prerequisite required for the workflow. (Your interaction is required to proceed to next step.)
The static workflow step displays only text, images, and hyperlinks.
The template workflow steps are linked to CLI commands. For simplicity and ease of use, these commands are not visible to you in the UI (although you can still use the CLI if you wish). You will instead see text, images, hyperlinks, and forms in which to enter tokenized values.
Once you click the Submit button in that particular step, the EMA loads the CLI commands to the SBC. The CLI commands for a template step are categorized into:
Tokenized CLI – You must input the value for the tokenized CLIs before submitting the configuration step. The workflow template identifies fields that can be customized through "tokens" in the CLI. The tokens in the CLI are replaced with the values you enter. You must complete all input fields before the tokens in tokenized CLIs can be updated. For example, if a CLI command includes a token for an IP address, the IP address input field is presented to you, and the value entered in this field replaces the corresponding token in the CLI command before submitting it to the SBC.
Non-Tokenized CLI Steps – Steps with CLI commands that do not require any input from you.
Templates are included in the Configuration Template Workflow sections. For example, the Sonus template named Skype for Business is included in the SBC. This template helps you configure inbound and outbound call flows between the SBC Core and Microsoft Skype for Business using TCP and SRTP.
This workflow does not include TLS configuration.
The concept of tokenized CLI starts from the Global Configuration. The tokenized CLIs (marked in red) are user-defined parameters, which are customized based on the requirements. Click View Config Details tab to view the configuration.