Provisioning Examples
Secure HTTPS Resync
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters 53
4
A profile for each ATA can be identified in a general purpose parameter, with its
value referred within a common profile rule by using macro expansion.
For example, assume GPP_B is defined as Dj6Lmp23Q.
The Profile_Rule has the value:
tftp://prov.telco.com/cisco/$B/$MA.cfg
When the device resyncs and the macros are expanded, the ATA with a MAC
address of 000e08012345 requests the profile with the name that contains the
device MAC address at the following URL:
tftp://prov.telco.com/cisco/Dj6Lmp23Q/000e08012345.cfg
Secure HTTPS Resync
This section demonstrates the mechanisms available on the ATA for resyncing by
using a secure communication process. It includes the following topics:
• Basic HTTPS Resync, page 53
• HTTPS With Client Certificate Authentication, page 56
• HTTPS Client Filtering and Dynamic Content, page 57
Basic HTTPS Resync
HTTPS adds SSL to HTTP for remote provisioning so that the:
• ATA can authenticate the provisioning server
• provisioning server can authenticate the ATA
• confidentiality of information exchanged between the ATA and the
provisioning server is ensured.
SSL generates and exchanges secret (symmetric) keys for each connection
between the ATA and the server, using public/private key pairs preinstalled in the
ATA and the provisioning server.
To Next Page
Loading...
Need help?
General
