more topics
|
Remote Access Feature
Description
Lines and Trunks
Remote Access calls are treated differently, depending on the type of line/trunk
and how it is routed.
- Line. Loop-start, ground-start, emulated loop-start, emulated ground-start,
BRI, and PRI B-channels programmed for line-appearance routing can be set
for Remote Access use, dedicated or shared. A Remote Access caller does not
dial the Remote Access code when Remote Access is in effect on these lines/trunks.
- Dial-In Tie. This type of line/trunk requires the caller to enter
the Remote Access code when dial tone is received. The code is not part of
the telephone number.
- Local Dial Plan. If a Remote Access caller dials the system on a
DID, E&M, PRI B-channel with dial plan routing, T1-emulated tie line,
or T1-emulated DID trunk, the caller can be connected without entering the
Remote Access code separately. Instead, the Remote Access code is part of
the telephone number dialed by the caller and is routed automatically by the
system as a Remote Access call. If the dialed telephone number does not include
the Remote Access number or the line/trunk is not programmed for routing by
dial plan, the call is treated as a normal incoming call and Remote Access
is not available.
- Non-Local Dial Plan (Hybrid/PBX mode). Intersystem calls between
extensions on networked systems are not Remote Access calls. The Remote Access
code for a non-local system, however, can be included in the non-local dial
plan, so that users from one system can reach another networked system more
economically via Remote Access for changing forwarding or for system maintenance.
The Remote Access codes of networked systems must be unique and unambiguous
with respect to the other numbers in the local and non-local plans. The receiving
system applies restrictions, and barrier codes should be required.
When a call is received for an unassigned number on a dial plan-routed PRI
facility, a DID trunk, a dial-in tie trunk, or a line/trunk programmed for shared
Remote Access and Night Service is activated, the call is redirected to the
QCC queue, a Calling Group, or an extension, depending on how the destination
of calls to unassigned numbers is programmed. The factory setting specifies
the primary operator as the destination.
When a call is received for an unassigned number on a private network facility,
the caller hears a fast busy or warble tone, depending on the type of facility,
on which the call arrived.
 |
In Hybrid/PBX mode, a Remote Access user from one system can reach Remote
Access on a networked remote system by using a DID trunk, tandem trunk,
a PRI B-channel with dial plan routing, T1-emulated DID trunk, or dial-in
tie trunk. The remote system applies any restrictions. The Remote Access
codes for each system must be unique and unambiguous. The default COR
settings that control this access should require barrier codes.
|
The table on the following page, Remote Access Routing,
summarizes the ways that Remote Access is made available to callers, depending
upon the type of line/trunk and the routing used on that line/trunk.
