Viewing station module information
157
Programming Operations Guide
You can enable or disable any port. Refer to
“Disabling/enabling a port channel setting” on page
160
.
Station module line deployment
The MSC presents 32 physical ports for each bus number assigned to a station or analog station
module. The DIP switch settings on the module determine which ports support telephone
connections. The first 16 ports are based on the B1 channel; the second 16 ports are based on the
B2 channel. Therefore, if a single-density DSM 16 module is used, only the first 16 DNs are
available for system telephones. Any module that was installed on a BCM version 2.5 or earlier
system is single density, which means it would support some of the first 16 ports, depending on the
type of module.
On systems running BCM version 3.0 and newer software, if you install DSM 16+ or DSM32+
modules, you can set them to be either single density or double density. An GASM installed on a
double density bus can populate all four offsets. If a DSM16+ or DSM32+ are set to double
density 32 ports are available, depending on the module and the dip switch settings. Example: A
DSM16+ set to double density accesses either the first 16 ports or the second 16 ports, depending
on the offset setting. A DSM32+ set to double density accesses the first 16 ports on the lower
connector and the second 16 ports on the upper connector.
Partial Double Density systems (PDD), which is the default system setting for BCM version 3.0
and newer software, retain a single-density identity for buses 06 and 07, to allow support for
legacy Companion installations which support two handsets for each B1/B2 port. Each port in
single density configurations are assigned a B1 and a B2 channel. If you set your system to
fully-deployed double density (FDD), both bus 06 and 07 are configured as double density and are
no longer available for applications that require both B1 and B2 ports.
You can change your system density from PDD to FDD under the Configuration menu in the MSC
programming. (
Services
,
Diagnostics
,
MSC
)
Upgraded systems:
BCM version 2.5 systems upgraded to BCM version 3.0 or newer systems
have a different DN deployment than newly-deployed BCM version 3.0 systems. In upgraded
systems, the first 16 DNs are assigned to DS30 02, the next 16 are assigned to DS30 03, and so on,
down to DS30 07. Then the first 16 DNs following this list is assigned to the second 16 lines (B2)
on DS30 02, and so on down the list again.
New BCM version 3.0 and newer systems:
The DN deployment in these systems is sequential.
That is, the first 32 DN numbers are assigned to DS30 02, the second 32 DN numbers are assigned
to DS30 03, and so on.
DN numbering for each type of system is displayed in tables in
“DN mapping for digital
telephones” on page 367
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...