Nortel BCM 3.7, Manual

Page: 300 / 1004

300 Configuring for remote access
N0008589 3.3
Notes about the Public and Private Received Numbers
If the received number is different than the regular DN number, enter the number in the Private
number and/or Public number field. For instance, in North America, you can enter the 10-digit
public number in the Public number field. If you leave these fields blank, the system will use the
DN of the telephone assigned with this line.
Upgrade note: If you upgraded your system from a version of Business Communications
Manager previous to BCM 3.6, the Private number field of assigned target lines will autofill with
the same value that is in the Public number field (usually the assigned DN). However, if the DN
length of the system was different from the Received number length, this field will be blank after
the upgrade. Systems running with a DPNSS keycode will also need to reenter the information in
this field after an upgrade to BCM 3.6 or newer software.
Programming note: The following trunks use one or both of these settings to route calls:
• DPNSS lines use the Private received number to route calls in the system.
• BRI ETSI-QSIG, PRI ETSI-QSIG, MCDN, DMS100, DMS250 and VoIP trunks route calls on
a per-call basis to either the public or private received digits.
Note: VoIP trunking MCDN calls
do not support Auto DN/DISA DN functionality.
• BRI (ETSI-Euro, NI-2), PRI (ETSI-Euro, NI-2, 4ESS), T1 (LoopStart, E&M, DID,
GroundStart), Analog LEC (LoopStart, E&M, DID), and DASS2 trunks route calls using the
Public received number.
Other settings to note:
• “Programming access codes” on page 321 (Public/Private DISA DNs and Auto DNs)
• “Assigning line access” on page 406 (Public/Private OLI)
Configuring for remote access
If you want callers from a different node on the network or from the public network to be able to
access system features or the system network lines, you need to set up remote access packages and
COS password
s to control outside access.
Programming note: If your system is hosting a centralized voice mail system, all calls from
non-host systems to the voice mail on your system are considered remote calls and you need to set
up the lines and remote access packages to accommodate this. If your system is using centralized
voice mail on another system, users on your system need to be advised of the appropriate voice
mail access codes.
This section provides information about:
• “Creating Direct Inward System Access (DISA)” on page 301
• “Defining remote access packages” on page 304
• “Using COS passwords” on page 305
• “External access tones” on page 308