Assigning Trunk/line data
271
Programming Operations Guide
Note:
The Auto privacy setting does not apply to target lines, PRI lines or VoIP trunking lines.
Received #
Target lines provide an additional record under
Trunk/Line Data
, and that is the
Received
number
. You can specify received numbers for both private (VoIP and MCDN) and public
network connections. This allows the system to identify the source of the call on a per-call basis.
1
Click on
Received Number
.
The Line XXX Received Number screen appears.
Figure 57
Target line Private and Public received numbers
2
Public number: The Network DN supplied by your service provider.
Private number: The DN number of the telephone or Hunt group.
3
Go to the DN record for that telephone and ensure that the target line number is specified in
the Line Assignment section.
Line pool tips
Read these tips before you assign your line pools.
•
Line pools must never contain a mixture of lines. All lines in a given line pool should go to the
same location.
•
Avoid putting unsupervised loop start lines in a line pool. These lines can become unusable,
especially when a remote user uses the line pool to make an external call.
•
Assign line pool access to telephones in
Line access
programming.
•
Assign system-wide line pool access codes in
General settings
(not applicable to PRI pools).
Caution: Changing the received # length:
If you change the received number length for your system, the
Public number
entry for
the target lines will clear if the new received # length is less than the number entered in this
field.
If the new received # length has more digits than the number entered in this field, you need
to change the entry manually, if changes are required. Refer to
“Changing the received #
length” on page 296
.
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...