ZyXEL APS 1.0 User Guide - Page 24

Common File

Get ZyXEL APS 1.0 PDF manuals and user guides View all ZyXEL APS 1.0 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

Auto Provisioning Administrator's Guide The following example is named "Field.txt". Figure 6 Account Field File Example 980101014 = SIP #1 Phone Number 980101012 = SIP #1 UserId 980101013 = SIP #1 Password 980102014 = SIP #2 Phone Number 980102012 = SIP #2 UserId 980102013 = SIP #2 Password 3.4 Common 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. , where is your input conforming to . 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. 24 Chapter 3 Provisioning Utility

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Auto Provisioning Administrator’s Guide
24
Chapter 3 Provisioning Utility
The following example is named “Field.txt”.
Figure 6
Account Field File Example
3.4
Common 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.
980101014 = SIP #1 Phone Number
980101012 = SIP #1 UserId
980101013 = SIP #1 Password
980102014 = SIP #2 Phone Number
980102012 = SIP #2 UserId
980102013 = SIP #2 Password