Provisioning Tutorial; Preparation; Version - Linksys SPA2102-AU Provisioning Manual

Provisioning Tutorial

This chapter describes the procedures for transferring configuration profiles between the SPA and the
provisioning server and includes the following sections:
•
•
•
•
For information about creating configuration profiles, refer to
Scripts."

Preparation

The examples presented in this chapter require the availability of one or more servers. For the purposes
of this tutorial, these can be installed and run on a local PC. To troubleshoot server configuration, it is
helpful to install clients for each type of server on a separate server machine. That establishes proper
server operation independent of the interaction with Linksys VoIP devices.
The pertinent servers include: Syslog (UDP port 514), TFTP (UDP port 69), HTTP (TCP port 80),
HTTPS (TCP port 443). For generating configuration profiles, it is useful to install the open source gzip
compression utility. For profile encryption and HTTPS operations, you can install the open source
OpenSSL software package. In addition, to test dynamic generation of profiles and one-step remote
provisioning using HTTPS, a scripting language with CGI scripting support, such as the open source Perl
language tools, is recommended.
Finally, to verify secure exchanges between provisioning servers and Linksys voice devices, it is useful
to install an Ethernet packet sniffer (such as the freely downloadable Ethereal/Wireshark). For HTTPS
transactions, you can use the ssldump utility.
A Linksys VoIP device (SPA) can retrieve a configuration profile from a provisioning server and update
its internal configuration accordingly. SPAs accept two different profile formats, one based on an open
published syntax, and one based on an unpublished binary definition. The open configuration profile
format uses a simple XML-like syntax. The binary format is generated by converting a plain text file
using the SPA Profile Compiler (SPC).
The examples in this tutorial use configuration profiles with XML-style syntax. To use the proprietary
plain-text format, you need to convert the files using SPC before they can be used. This procedure is
described in the

Version 3.0

Preparation, page 3-1
Basic Resync, page 3-2
Secure Resync, page 3-7
Profile Formats, page 3-10
"Proprietary Profile Format" section on page
C H A P T E R
Chapter 2, "Creating Provisioning
3-13.
Linksys SPA Provisioning Guide
3
3-1