Table 50 Destination codes schedules
Attribute
Schedule
First Route
Absorbed Length
Second Route
Absorbed Length
Third Route
Absorbed Length
Second Dial Tone
This feature provides dial tone for outgoing calls on any PRI line, based on the digits dialed. Digits
dialed must match an entry in the second dial tone table to enable a second dial tone. Dial tone
occurs on the line until another digit is dialed, a timeout occurs, or the user hangs up.
Up to 10 separate entries can be stored in the second dial tone table. The maximum digit length for
each entry is four. Each entry must be unique and cannot conflict with:
•
Internal DNs
•
Hunt Group DNs
•
DISA DNs
•
Auto DNs
•
Target Line DNs
Tips: Entries can match destination or access codes for outgoing lines.
The following paths indicate where to configure the Second Dial Tone in Element Manager and
through Telset Administration:
Chapter 26 Dialing plan: Routing and destination codes
Value
Defaults: Night,
Evening, Lunch,
Weekend, Sched. 5,
Sched. 6
<configured route #>
All, None, 1-X
<configured route #>
All, None, 1-X
<configured route #>
All, None, 1-X
Description
If you use a different carrier at different times of the day or
week, you can set the destination code to use that route
and provide two more backup routes. The user does not
experience any difference in dialing sequence.
This is the route that the system will use, during the
indicated schedule, when the destination code is added to
the dial string.
This indicates how much of the destination code gets
removed before the system sends the dial string to the
network.
This is the route the system will use if the first route is
unavailable.
This indicates how much of the destination code gets
removed before the system sends the dial string to the
network.
This is the route the system will use if the first and second
route are unavailable.
This indicates how much of the destination code gets
removed before the system sends the dial string to the
network.
Networking Configuration Guide
265