Creating Direct Inward System Access (DISA)
301
Programming Operations Guide
Creating Direct Inward System Access (DISA)
To control access from the public or private network, you can configure auto-answer trunks to
answer with DISA. Remote callers hear a stuttered dial tone and must then enter a COS password
that determines what they are allowed to do in the system.
•
Auto-answer T1 loop start and T1 E&M trunks are configured to answer with DISA by
default.
•
T1 DID trunks: You cannot configure T1 DID trunks to answer with DISA. If you want
incoming T1 DID calls to be answered with DISA, configure the system with a DISA DN.
Incoming T1 DID calls that map onto the DISA DN are then routed to a line that has DISA.
•
You cannot program a DISA DN or Auto DN to VoIP trunks, because they act as auto-answer
lines for private networks. However, you still need to assign remote access packages
s
to the
VoIP trunks, to ensure that remote access restrictions are properly applied to incoming calls
trying to access the system or the system network.
This section also includes information about:
•
“Remote access line settings”
•
“Remote access on loop start trunks” on page 302
•
“Remote access on T1 DID trunks” on page 302
•
“Remote access on PRI” on page 302
•
“Remote access on DPNSS lines” on page 303
•
“Remote access on a private network” on page 303
Remote access line settings
The remote access feature allows callers elsewhere on the private or the public network to access
your Business Communications Manager by dialing directly and not going through the attendant.
After the remote user is in the system, they can use some of the system resources. You must enable
remote access in programming before callers can use it.
Business Communications Manager supports remote system access on a number of trunk types
which may require the remote caller to enter a password for DISA.
The system resources, such as dialing capabilities, line pool access and feature access, that a
remote user may access depends on the COS password assigned to them. See
“Using COS
passwords” on page 305
.
Note:
Callers remotely accessing the Business Communications Manager press
*
followed by the
feature code to use the system features. Even if you are calling from another Business
Communications Manager system, press
*
instead of the Feature key.
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...