The contents of this publication may not be reproduced in any part or as a whole, transcribed,
stored in a retrieval system, translated into any language, or transmitted in any form or by any
means, electronic, mechanical, magnetic, optical, chemical, photocopying, manual, or
otherwise, without the prior written permission of ZyXEL Communications Corporation.
Published by ZyXEL Communications Corporation. All rights reserved.
Disclaimer
ZyXEL does not assume any liability arising out of the application or use of any products, or
software described herein. Neither does it convey any license under its patent rights nor the
patent rights of others. ZyXEL further reserves the right to make changes in any products
described herein without notice. This publication is subject to change without notice.
Trademarks
ZyNOS (ZyXEL Network Operating System) is a registered trademark of ZyXEL
Communications, Inc. Other trademarks mentioned in this publication are used for
identification purposes only and may be properties of their respective owners.
Copyright3
Auto Provisioning Administrator’s Guide
Please have the following information ready when you contact customer support.
• Product model and serial number.
• Warranty Information.
• Date that you received your device.
• Brief description of the problem and the steps you took to solve it.
This document is for administrators who need to configure a large number of ZyXEL’s VoIP
ATAs and IADs. Auto provisioning has the VoIP devices periodically download a
configuration text file from a server that you set up and maintain. The VoIP device changes its
configuration to match the configuration file (if they are different). At the time of writing, you
can use TFTP, HTTP or HTTPS
The following sections introduce two scenarios for using auto provisioning with ZyXEL’s
VoIP ATAs and IADs. The first uses a provisioning utility and the second uses an auto
provisioning server.
1
protocol for auto provisioning.
Auto Provisioning Administrator’s Guide
CHAPTER1
1.2 Provisioning Utility Scenario
For smaller-scale deployments, you can manually use the ZyXEL configuration generator
provisioning utility to generate and encrypt a batch of configuration files. Then store the
configuration files on a server for the ZyXEL Customer Premises Equipment (CPE) VoIP
devices to automatically download and use.
1.HTTPS support is optional and is not supported in the standard release.
Chapter 1 Auto Provisioning15
Auto Provisioning Administrator’s Guide
Figure 1 Provisioning Utility Scenario
1.2.1 Provisioning Utility System Usage
Use the following steps to set up auto provisioning using the provisioning utility.
Note: You must use the Command Line Interface (CLI)
configure the ZyXEL VoIP devices to get the configuration files from the server
(see Chapter 2 on page 21).
Figure 2 Provisioning Utility Set Up
1 Create an account file containing settings such as the username, password and SIP
number (see Section 3.2 on page 23 for details). You can export data from your Customer
Relationship Management (CRM) database to use in the account file.
autopro command to pre-
2 Create a common file with general SIP settings such as the SIP server’s IP address, port
number, codec and timeout (see Section 3.4 on page 24).
16Chapter 1 Auto Provisioning
3 Use the provisioning utility to generate and encrypt a batch of configuration files (see
Chapter 3 on page 23). Each includes subscriber specific SIP settings (username,
password and SIP number).
4 Store the configuration files on a TFTP or HTTP server. Subscribers do not need to
configure any SIP settings. After the VoIP device starts and connects to the Internet, it
automatically downloads its unique configuration text file from the provisioning server.
1.3 Auto Provisioning Server Scenario
For large-scale deployments, you can use ZyXEL’s auto provisioning server software for a
automated, end-to-end solution. The auto provisioning server provides the following key
benefits and features.
• Efficient management. The database-centric approach automatically generates and
manages VoIP subscriber device profiles. The auto provisioning server’s database uses
MySQL.
• It is easy to update settings for individual VoIP subscriber devices when you change SIP
parameters.
• PIN code based authentication for enhanced security. The auto provisioning server uses
Hypertext Preprocessor (PHP) to communicate with the VoIP subscriber devices.
• The web-based management interface is easy-to-use.
• ZyXEL’s auto provisioning server software supports the XML and Simple Object Access
Protocol (SOAP) to ease integration with your existing CRM database.
Auto Provisioning Administrator’s Guide
Figure 3 Auto Provisioning Server Scenario
Chapter 1 Auto Provisioning17
Auto Provisioning Administrator’s Guide
1.3.1 Requirements for Using the Auto Provisioning Server
You need to do the following.
• Provide and maintain a CRM system (database) that:
Stores a record of VoIP subscriber device MAC addresses.
Generates a unique PIN code to map to each VoIP subscriber device MAC address.
Stores each subscriber’s SIP number, user ID, password PIN code and MAC address.
Note: The auto provisioning server software package includes sample CRM server
software called the VoIP Subscribing System (VSS). See Appendix D on page
87 for its database structure.
• Install the auto provisioning server software on a server (see Chapter 4 on page 43).
• Integrate the auto provisioning server with the CRM system. See Appendix E on page 89
for how the auto provisioning server uses SOAP to communicate with the CRM system.
• Provide SIP numbers and PIN codes to the subscribers either through a card, information
sheet or other method.
• Use the
ZyXEL VoIP devices to get the configuration files from the server (see Chapter 2 on page
21).
autopro command in the Command Line Interface (CLI) to pre-configure the
1.3.2 Auto Provisioning Server System Usage
The following figure and steps describe how auto provisioning works with the auto
provisioning server.
18Chapter 1 Auto Provisioning
Figure 4 Auto Provisioning Server Operation
Auto Provisioning Administrator’s Guide
1 Register a VoIP subscriber device and create a subscriber profile in the CRM database.
The device’s type and MAC address have to be stored in the CRM database. You could
set it up so that a subscriber uses a credit card on-line to register for VoIP service and the
CRM database creates the subscriber profile and maps it to a device MAC address.
2 The subscriber connects the VoIP device to the Internet and uses the telephone keypad to
enter the assigned SIP number and PIN code. The subscriber must press *99** SIP
number * PIN code #. For example, *99** 10000002 * 1234 #. After the subscriber
enters this information once, the device uses it to get the latest configuration file every
time the device starts and connects to the Internet.
3 The VoIP device uses the SIP number, PIN code and its MAC address and model name to
authenticate with the auto provisioning server.
4 For a new subscriber, the auto provisioning server requests subscriber specific settings
from the CRM database.
5 The CRM server sends the subscriber specific settings to the auto provisioning server.
6 The provisioning server combines the subscriber specific settings with general SIP setting
to make a configuration file.
7 The subscriber’s VoIP device downloads and uses the configuration file.
1.3.3 Auto Provisioning Server System - Important Notes
The default address for accessing the sample CRM server is http://192.168.1.200/ZyXEL/.
Sample VoIP SIP Express Router (SER) software is also included on the auto provisioning
CD. You can use http://192.168.1.200 to access it. See iptel.org for more information on SER
servers.
Chapter 1 Auto Provisioning19
Auto Provisioning Administrator’s Guide
By default the sample SER server does not enforce any security so a SIP device does not have
to be registered to use it. When you implement the auto provisioning server system, you will
want to have the CRM server and SIP server interact to make sure that only registered SIP
devices can use the SIP server.
20Chapter 1 Auto Provisioning
Auto Provisioning Administrator’s Guide
CHAPTER2
Auto Provisioning Commands
Before you deploy the VoIP devices, you need to configure them with your provisioning
server’s IP address and enable the auto provisioning feature.
Use the Command Line Interface (CLI) to configure the VoIP device’s auto provisioning
settings. The VoIP device’s auto provisioning settings are not configurable via the web
configurator. This prevents end users from accidentally changing them.
Do the following to enter the CLI.
1 Log into the device by telnet or the console port.
2 Enter SMT Menu 24.8, the CLI mode.
2.1 Auto Provisioning Commands
Use the following commands to configure the VoIP device’s auto provisioning settings.
Table 1 Auto Provisioning Commands
COMMANDDESCRIPTION
voice configautoproindex<index>Starts an auto provisioning configuration session.
active<index>
<0:off|1:on>
servaddr <index> <ip
address>
timeout<index>
<second>
retry<index>
<second>
method<index>
<0:common|2:
http_pincode
>
protocol <index>
<0:TFTP|1:HT
TP|2:HTTPS>
save<index>Saves the auto provisioning configuration.
Turns auto provisioning on or off.
Sets the IP address of the server.
Sets how long the VoIP device waits after
successfully downloading the configuration file from
the server before downloading it again.
Sets how long the VoIP device waits after a failed
attempt to download the configuration file from the
server before making another download attempt.
This period is usually shorter than the timeout
period.
Use 0 if you are using the provisioning utility. Use 2
if you are using the auto provisioning server.
Sets which protocol to use for auto provisioning.
Chapter 2 Auto Provisioning Commands21
Auto Provisioning Administrator’s Guide
Table 1 Auto Provisioning Commands (continued)
COMMANDDESCRIPTION
display<index>Displays the auto provisioning configuration
settings.
dumpCfg<index>Displays the auto provisioning settings in the
temporary buffer.
22Chapter 2 Auto Provisioning Commands
Provisioning Utility
3.1 Provisioning Utility Overview
Use the provisioning utility to create encrypted configuration text files. The utility uses triple
DES encryption for strong security.
Use the correct utility for your operating system (ZyConfigGen_Win32 for Windows or
ZyConfigGen_Linux for Linux).
3.2 Account File
Auto Provisioning Administrator’s Guide
CHAPTER3
You must create an account file before you use the utility. The account file lists subscriber
specific account information according to the following format. The MAC address must be
listed first.
Syntax
<MAC Address>,<SIP1 Phonenumber>,<SIP1 User ID>,<SIP1 Password>,[SIP2
Phonenumber],[SIP2 User ID],[SIP2 Password]
The account file may be generated from a database. The following example is named
“Account.txt”.
You must also create an account field file that identifies the fields in the account file. The
fields must be in the same order in the account file and the account field file. The MAC
address is not included in the account field file.
You can also include a common file of general settings if you want to change them from the
defaults. A common file is optional.
Use the
voice autopro itemdisplay command with a device to see which fields can be
configured through auto provisioning. It is recommended that you use communications
software (such as a terminal emulation program) that allows you to capture the results.
3.4.1 The Common File Format
This is the format of the configuration text files.
<field identification number = field name = parameter values allowed =
input>,
where <input> is your input conforming to <parameter values allowed>.
It is also the same format that Internal SPTGEN configuration files use. See Section 3.5 on
page 25 for how to get a device’s SPTGEN file.
Note: Make sure you use the
voice autopro itemdisplay command to get the
fields that are configurable via auto provisioning. Even if you use a full Internal
SPTGEN file, auto provisioning only changes the settings that are configurable
via auto provisioning.
3.4.2 File Modification - Important Points to Remember
Each parameter must be preceded by one “=”sign and one space.
Some parameters are dependent on others.
24Chapter 3 Provisioning Utility
3.5 Getting an SPTGEN File
You can use an internal SPTGEN file to create a common file. Use the following procedure to
get a SPTGEN file from a VoIP device via FTP.
1 Launch the FTP client on your computer.
2 Enter “open”, followed by a space and the IP address of your VoIP device.
3 Press [ENTER] when prompted for a username.
4 Enter your password as requested (the default is “1234”).
5 Enter “bin” to set transfer mode to binary.
6 Use “get” to transfer files from the device to the computer, for example, “get rom-t
SPTGEN.txt” transfers the internal SPTGEN file on the device to your computer and
renames it “SPTGEN.txt”.
7 Enter “quit” to exit the ftp prompt.
The following figure shows an example.
Auto Provisioning Administrator’s Guide
Figure 7 FTP Session Example
C:\>ftp 192.168.1.1
Connected to 192.168.1.1.
220 P2302R FTP version 1.0 ready at Sat Jan 01
00:01:52 2000
User (192.168.1.1:(none)):
331 Enter PASS command
Password:
230 Logged in
ftp> bin
200 Type I OK
ftp> get rom-t P-2302R.txt
200 Port command okay
150 Opening data connection for RETR rom-t
226 File sent OK
ftp: 36107 bytes received in 3.75Seconds
9.63Kbytes/sec.
ftp> quit
221 Goodbye!
3.6 Auto Provisioning Text Files
Auto provisioning uses configuration text files that include subscriber specific SIP settings
(username, password and SIP number). Subscribers do not need to configure any SIP settings.
They only need to connect the VoIP device to the Internet.
Chapter 3 Provisioning Utility25
Auto Provisioning Administrator’s Guide
Your server must include a database with a different configuration file for each subscriber. The
filename of each configuration file must include the VoIP device’s MAC address, for example:
sip<MAC ADDRESS>.txt. This allows each VoIP device to download its unique
configuration file.
3.6.1 Auto Provisioning Text File Menus Example
The following table explains the labels that have been added to the example auto provisioning
menu tables for identification purposes. These labels do not appear in an actual auto
provisioning configuration file.
Table 2 Example Auto Provisioning Menus Abbreviations
ABBREVIATIONMEANING
FINField Identification Number (not seen in SMT screens)
FNField Name
PVAParameter Values Allowed
INPUTAn example of what you may enter
Here are examples of configuration text file menus that auto provisioning uses. This is a
general example, the exact fields vary by product.
Note: You can add comments in a configuration file by adding a a /* before them and
a */ after them.
26Chapter 3 Provisioning Utility
Auto Provisioning Administrator’s Guide
Note: DO NOT alter or delete any field except parameters in the INPUT column.