Quickly provisions a newly-installed system to a working state.
Supports provisioning of Trunk and Remote Worker flows.
Is not a replacement for the traditional UI.
This feature accepts a minimum subset of the information required to create basic trunk or remote worker flows, such as listen addresses, ports, call/trunk server addresses, and X.509 certificate/keys (if applicable). This information is used in the backend to create the relevant profiles to support these basic flows.
For trunk deployments, this information includes:
Networks & Addresses
SIP Server (Trunk)
SIP Server (Call Server)
Signaling Interface
Media Interface
Server Flows
Routing Profiles
For remote worker deployments, this information includes:
Networks & Addresses
SIP Servers (Primary Call Server + Optional Secondary Call Server)
Signaling Interface
Media Interface
Server Flows
Subscriber Flows
Routing Profiles
DAT file
Additional information, such as interworking parameters or topology hiding settings, might be required for specific service providers or remote worker deployments. This information is provided through a DAT file (YAML format) which can define options for a Service Provider (Trunk) or Client Type (Remote Worker).
A DAT file can be used to define the following:
Application Rule
Media Rule
Server Interworking Profile
Topology Hiding Profile
All the rules/profiles provided in a DAT file are optional and revert to the default profiles if not specified inside a DAT file. By default, Avaya SBC is not bundled with any DAT files. However, Avaya provides documentation on how to create your own DAT files through Avaya DevConnect.
