296
Defining DN length
N0008589 3.3
Using the Received # length
If you change the DN length of your system, you may need to change the Received # length, which
is what the system uses, in conjunction with the dialing table coding, private and public
networking, and the access codes to determine a route for an incoming call over an auto-answer
trunk.
On systems running the DID telephony template, the Private and Public Received # length is set to
the same length as the DN length for the system. On systems running the PBX telephony template,
the Private and Public Received # length default to 3, unless the DN length is changed during the
Startup procedure.
These digits identify target lines (
“Assigning target lines” on page 297
), Auto DN
s
, and DISA
DN
s
(
“Programming access codes” on page 321
).
TIPS:
The target line number (for example, line 241) and the Received number for the target line
(for example, Received number: 123 maps to line 241) must be different numbers. (
“Target lines
and DASS2 fields” on page 259
).
However, the received number can be shorter if network or central office constraints require this.
This number cannot be greater than the system DN length on a networked system using a
coordinated dialing plan (CDP) or a universal dialing plan (UDP). On a standalone system it is
possible that the received number length would be greater than the DN length.
Changing the received # length
1
Click the keys beside Services, Telephony Services, General settings, and DN lengths.
2
Click on
Received # length
.
3
On the navigation tree, click on
Received # length
.
The Received # length screen appears in the right frame.
Figure 82
Received # length, (PBX template default)
Warning:
Decreasing the received number length clears all programmed received digits.
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...