Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 66

Provisioning Tutorial Basic Resync 3 An IP Telephony Device can retrieve a configuration profile from a provisioning server and update its internal configuration accordingly. IP Telephony Devices 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 SIP Profiler 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 "Proprietary Profile Format" section on page 81. Basic Resync This section demonstrates the basic resync functionality of Cisco Small Business VoIP devices. It includes the following topics: • TFTP Resync, page 64 • Logging with syslog, page 66 • Automatic Resync, page 67 • Unique Profiles and Macro Expansion, page 68 • URL Resolution, page 70 • HTTP GET Resync, page 71 TFTP Resync The IP Telephony Device supports multiple network protocols for retrieving configuration profiles. The most basic profile transfer protocol is TFTP (RFC1350). TFTP is widely used for the provisioning of network devices within private LAN networks. Although not recommended for deployments of endpoints across the Internet, it can be convenient for deployment within small organizations, for inhouse preprovisioning, and for development and testing. The following configuration profile format uses the XML-style syntax: 12345678 Cisco Small Business IP Telephony Devices Provisioning Guide 64