Table of Contents
Advertisement
Provisioning Tutorial
Basic Resync
Basic Resync
Cisco Small Business IP Telephony Devices Provisioning Guide
•
For profile encryption and HTTPS operations, install the open source
OpenSSL software package.
•
To test dynamic generation of profiles and one-step remote provisioning
using HTTPS, a scripting language with CGI scripting support, such as open
source Perl language tools, is recommended.
•
To verify secure exchanges between provisioning servers and Cisco Small
Business voice devices, install an Ethernet packet sniffer (such as the freely
downloadable Ethereal/Wireshark). For HTTPS transactions, you can use
the ssldump utility.
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 must convert the files using the SPC
before they can be uploaded to the device. This procedure is described in the
"Proprietary Profile Format" section on page
This section demonstrates the basic resync functionality of Cisco Small Business
VoIP devices. It includes the following topics:
•
TFTP Resync, page 63
•
Logging with syslog, page 64
•
Automatic Resync, page 65
•
Unique Profiles and Macro Expansion, page 67
•
URL Resolution, page 68
•
HTTP GET Resync, page 69
79.
3
62
Advertisement
Table of Contents
