Appendix b dial plan syntax, Appendix b, Dial plan syntax – Teo IPTelephone Network User Manual

Page 75

13-280132 Rev. Q

Page 75

The complete BNF syntax that defines the structure for the dial plan is as follows:

<dial_plan> ::= *
<component> ::=
<prefix-operation> ::= “{“ * “|” * “}”
<subst-pattern-element> ::= | |
<dial-pattern> ::= + []
<dial-pattern-element> ::= | |

<dial-pattern-terminator> ::= |
<suffix-operation> ::= “{“ * “|”* [] “}”
<meta-operation> ::=
<meta-operation-marker> ::= “`”
<meta-operation-identifiers> ::= [“,” ]
::= | |
::= “P”
::= “R”
::= (0 to 49)
::= “CF” | “CV”
<access-level> ::= (0 to 99)
<dial-character> ::= | | |
<wildcard> ::= “^”
<bracket-expression> ::= “[” { “,” < bracket-element > } “]”
<bracket-element> ::= |
<dial-range> ::= “-“
<secondary-dialtone-marker> ::= “`”
<initiate-call-marker> ::= “#”
<block-access-marker> ::= “!”

A null does not affect user dialing in any way.
Dial plan components are evaluated from left-to-right until a dial pattern within a

component is recognized or the last component is processed. Each

specifies a

, a

, and a

. Note that

character>

is limited to the following ASCII characters:

A-Z a-z 0-9 . @ _ - / \, : ; * ‘ “ ( ) < > ~ + = ? ! $ % &

(space)

The

may contain any sequence of

bracket-

expression>

, or

, and it may end with a single

marker>

. The

within the

pattern>

directs the phone to generate secondary dial tone, if the current dialed string

entry matches the

sub-string preceding the marker. An

marker>

at the end of the

directs the phone to automatically initiate a call, if