Cisco SPA1001 Administration Guide - Page 57

Configuring a Dial Plan

Page 57 highlights

Chapter 3 Configuring Linksys ATAs Configuring a Dial Plan Yes Binary format profiles contain Linksys ATA parameter values and user access permissions for the parameters. By convention, the profile uses the extension .cfg (for example, spa2102.cfg). The Linksys Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs into a properly formatted and encrypted .cfg file. The SPC tool is available from Linksys for the Win32 environment and Linux-i386-elf environment. Requests for SPC tools compiled on other platforms are evaluated on a case-by-case basis. Please contact your Linksys sales representative for further information about obtaining the SPC tool. The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value pairs, with the value in double quotes. Each parameter-value pair is followed by a semicolon. Here is an example of a valid text source profile for input to the SPC tool: Admin_Passwd "some secret"; Upgrade_Enable "Yes"; Refer to the Linksys SPA Provisioning Guide for further details. The names of parameters in XML profiles can generally be inferred from the Linksys ATA configuration Web pages, by substituting underscores (_) for spaces and other control characters. Further, to distinguish between Lines 1, 2, 3, and 4, corresponding parameter names are augmented by the strings _1_, _2_, _3_, and _4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles. Parameters in the case of source text files for the SPC tool are similarly named, except that to differentiate Line 1, 2, 3, and 4, the appended strings ([1], [2], [3], or [4]) are used. For example, the Line 1 Proxy is named Proxy[1] in source text profiles for input to the SPC. Configuring a Dial Plan The Linksys ATA allows each line to be configured with a distinct dial plan. The dial plan specifies how to interpret digit sequences dialed by the user, and how to convert those sequences into an outbound dial string. The Linksys ATA syntax for the dial plan closely resembles the corresponding syntax specified by MGCP and MEGACO. Some extensions are added that are useful in an end-point. Note When using the SPA3102 or AG310 as a PSTN gateway, gateway calls can be restricted on a per-caller basis using dial plans. Up to eight dial plans can be configured to restrict gateway calls in either direction. Dial Plan Digit Sequences The plans contain a series of digit sequences, separated by a vertical bar ( | ). The collection of sequences is enclosed in parentheses. When a user dials a series of digits, each sequence in the dial plan is tested as a possible match. The matching sequences form a set of candidate digit sequences. As more digits are entered by the user, the set of candidates diminishes until only one or none are valid. Any one of a set of terminating events triggers the Linksys ATA to either accept the user-dialed sequence and transmit it to initiate a call, or else to reject it as invalid. The terminating events are as follows: • No candidate sequences remain-The number is rejected. Document Version 3.1 Linksys ATA Administrator Guide 3-5

  • 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
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186

3-5
Linksys ATA
Administrator Guide
Document Version 3.1
Chapter 3
Configuring Linksys ATAs
Configuring a Dial Plan
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
Binary format profiles contain Linksys ATA parameter values and user access permissions for the
parameters. By convention, the profile uses the extension .cfg (for example, spa2102.cfg). The Linksys
Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs into a properly
formatted and encrypted .cfg file. The SPC tool is available from Linksys for the Win32 environment
and Linux-i386-elf environment. Requests for SPC tools compiled on other platforms are evaluated on
a case-by-case basis. Please contact your Linksys sales representative for further information about
obtaining the SPC tool.
The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value pairs,
with the value in double quotes. Each parameter-value pair is followed by a semicolon. Here is an
example of a valid text source profile for input to the SPC tool:
Admin_Passwd
“some secret”;
Upgrade_Enable “Yes”;
Refer to the
Linksys SPA Provisioning Guide
for further details.
The names of parameters in XML profiles can generally be inferred from the Linksys ATA configuration
Web pages, by substituting underscores (_) for spaces and other control characters. Further, to
distinguish between Lines 1, 2, 3, and 4, corresponding parameter names are augmented by the strings
_1_, _2_, _3_, and _4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles.
Parameters in the case of source text files for the SPC tool are similarly named, except that to
differentiate Line 1, 2, 3, and 4, the appended strings ([1], [2], [3], or [4]) are used. For example, the
Line 1 Proxy is named Proxy[1] in source text profiles for input to the SPC.
Configuring a Dial Plan
The Linksys ATA allows each line to be configured with a distinct dial plan. The dial plan specifies how
to interpret digit sequences dialed by the user, and how to convert those sequences into an outbound dial
string.
The Linksys ATA syntax for the dial plan closely resembles the corresponding syntax specified by
MGCP and MEGACO. Some extensions are added that are useful in an end-point.
Note
When using the SPA3102 or AG310 as a PSTN gateway, gateway calls can be restricted on a per-caller
basis using dial plans. Up to eight dial plans can be configured to restrict gateway calls in either
direction.
Dial Plan Digit Sequences
The plans contain a series of digit sequences, separated by a vertical bar ( | ). The collection of sequences
is enclosed in parentheses.
When a user dials a series of digits, each sequence in the dial plan is tested as a possible match. The
matching sequences form a set of candidate digit sequences. As more digits are entered by the user, the
set of candidates diminishes until only one or none are valid.
Any one of a set of terminating events triggers the Linksys ATA to either accept the user-dialed sequence
and transmit it to initiate a call, or else to reject it as invalid. The terminating events are as follows:
No candidate sequences remain—The number is rejected.