Mapping Zero Touch Templates
Before implementing Zero Touch, you must map Zero Touch Templates.
|
➢
|
To prepare the network: |
|
1.
|
Prepare a template per tenant / device model-type in the deployment. The template informs the server how to generate the .cfg configuration file when the devices are plugged in to the network. When the devices are plugged in, the .cfg configuration file is downloaded to them from the server. |
|
a.
|
Open the 'Add new template' screen (Setup > Configuration > Templates). |
|
b.
|
Click theAdd New Template button. |
|
c.
|
Enter a name for the template. Make the name intuitive. Include tenant and model aspects in it. |
|
d.
|
Provide a description of the template to enhance intuitive maintenance. |
|
e.
|
From the 'Tenant' dropdown list, select the tenant. |
|
f.
|
From the 'Type' dropdown list, select the device model-type. |
|
g.
|
Select the Default Tenant option for the template to be the default for this tenant. More than one model-type can be in a tenant. All can have a common template. But only one template can be configured for a tenant. If a second template is configured for the tenant, it overrides the first. After a template is added, it's displayed as shown below in the Devices Configuration Template page (Setup > Configuration > Templates). When a phone is then connected to the network, if the device is of this model-type and located in this tenant, it will automatically be provisioned via the DHCP server from the OVOC provisioning server (Zero Touch). |
|
h.
|
From the 'Clone From Template' dropdown list, select a template to clone from. If the template is for devices in a tenant that are Microsoft Skype for Business phones, choose a Skype for Business template. |
|
i.
|
Do this for all tenants and device models-types in the network. |
|
j.
|
If necessary, click the here link in 'Click here to Download Shared Templates'; your browser opens displaying the share file in which all templates are located. |
|
2.
|
Upload the firmware .img file to the the OVOC provisioning server after getting it from AudioCodes. When devices are later connected to the network, they're automatically provisioned with firmware from the server. |
|
a.
|
Access the Firmware Files page (Setup > Firmware > Firmware Files). |
|
b.
|
Click the + Add New Device Firmware button. |
|
c.
|
Navigate to the .img file and upload to server. |
|
3.
|
Configure the DHCP server's Option 160 to allocate the phone to the tenant/site URL. Point DHCP Option 160 to a tenant URL so that the devices will automatically be provisioned with their .img firmware file and cfg configuration file when they're plugged in to the network for the first time (Zero Touch provisioning). |
|
a.
|
In the DHCP Options Configuration page (Setup > Settings > DHCP Options Configuration), click the link Advanced: DHCP option 160 with Tenant Configuration. |
|
b.
|
Under the Tenant URLs section, select from the 'Tenant' dropdown a tenant with which to associate a new device. |
|
c.
|
From the 'Group' dropdown list, select a group with which to associate a new device. |
|
◆
|
Live Platform has direct access to the phones. The DHCP server will connect the phones directly to the OVOC server IP address. Copy (Ctrl+C) the following URL and paste it into DHCP Option 160 in the enterprise's DHCP server: HTTP://<OVOC_IP_Address>/firmwarefiles;ipp/tenant/<tenant selected in Step 1>/group/<group selected in step 1> |
|
◆
|
Live Platform access the IPP's through the SBC HTTP proxy. The DHCP server directs the phones firstly to an SBC HTTP proxy server, which then redirects to the OVOC server. If the phones communicate with an SBC HTTP proxy rather than directly with the OVOC server, copy (Ctrl+C) the following URL into DHCP Option 160 in the enterprise's DHCP server: http://SBC_PROXY_IP:SBC_PROXY_PORT/firmwarefiles;ipp/tenant/Tenant |
|
◆
|
Direct URL for the IPP (No DHCP Available) – typically used for debugging purposes when no DHCP is available. |
|
●
|
Configure DHCP Option 160 to point to the OVOC provisioning server's URL if the phones are not behind a NAT. DHCP Option 66/67 can also be used. |
|
●
|
If the phones reside behind a NAT and an SBC HTTP proxy is available, configure DHCP Option 160 to point to the SBC HTTP proxy; device-OVOC communications will then be via the SBC HTTP proxy rather than direct. |
After copying the tenant URL (Ctrl+C) and pasting it into the enterprise's DHCP server's DHCP Option 160, select the device model from the 'IPP Model' dropdown and then click the button IPP with this model will get from the DHCP; an output of the configuration file that you have configured to provision is displayed. Verify it before committing to provision multiple devices.
When a deployment covers multiple tenants, the tenants definition can be in two main hierarchies:
For Zero Touch provisioning to function, tenant granularity must correspond with the number of DHCP servers/subnets already located within the enterprise network.
|
1.
|
Open the 'Zero Touch Templates Mapping' page (Setup > Settings > Zero Touch Mapping). |
|
●
|
After installation, the Zero Touch Templates Mapping page will be empty. |
|
●
|
Zero Touch mapping enables you to control which device model to include and which to exclude, and how to associate a specific template with a specific model. |
|
●
|
The templates are part of Device Manager's database and are supplied with the module. Though the module provides every device model with a ready-to-use template, each can be edited if necessary (Setup > Configuration > Templates). |
|
✔
|
Native Teams devices are supported (with the exception of the RX50 Meeting Room device peripheral)
|
|
✔
|
Jabra headsets and speakers are supported |
|
✔
|
Microsoft Teams SIP Gateway is supported |
|
✔
|
Poly devices and EPOS headsets and speakers will be supported in the future |
|
2.
|
Select the devices to include in the deployment and click Save after each selection. |