Meridian 1 Security

Check out Gene's "BARS 101" and details on how to stop "Transfer me to an
outside Operator" and the "90# scam" including more information about the
"extension 9000 scam" ©GHTROUT

An audit of the Meridian 1 telephone system will ensure that every possible "system"
precaution has been made to prevent fraud. The first step involves querying data
from the system in the form of printouts (or "capturing" the data to a file in a PC).
The next step is to analyze the data and confirm the reason for each entry. Please be
advised that this procedure is not designed for all "networked" Meridian 1 systems,
however, most of the items apply to all systems. Use at your own risk. ©GHTROUT

PRINTOUTS REQUIRED FOR SECURITY AUDIT: It is suggested that you "capture" all
of the data from these printouts to separate files. This can be accomplished with a PC
and communications program. For the BARS LD90 NET printout, look here
©GHTROUT

LD22 CFN LD22 PWD LD21 CDB LD21 RDB

LD21 LTM LD23 ACD LD24 DISA LD20 SCL
LD86 ESN (Detail) LD86 RLB (Detail) LD86 DMI (Detail) LD87 NCTL (Detail)
LD87 FCAS (Detail) LD87 CDP (Detail) LD90 NET (Detail) LD90 SUM (Detail)
LD20 TNB LD22 DNB LD88 AUB

GATHERING DATA FROM LD81 ©GHTROUT

List (LST) the following FEAT entries to form an information base on the telephones.
©GHTROUT

NCOS 00 99 CFXA UNR TLD SRE

FRE FR1 FR2 CUN CTD

DATA BLOCK REVIEW ITEMS ©GHTROUT

From the printouts, a review of the following areas must be made. Some of the items
may or may not be appropriate depending on the applications of the telephone
system. ©GHTROUT

CFN - • Verify that History File is in use. ©GHTROUT

Configuration
PWD - • Verify that FLTH (failed login attempt threshold) is low
Passwords enough.
• Verify that PWD1 and PWD2 (passwords) use both alpha and
numeric characters and are eight or more characters long.
 • Note any LAPW's (limited access passwords) assigned.

• Enable audit trails. ©GHTROUT

CDB - Customer • Verify that CFTA (call forward to trunk access code) is set to
Data Block NO.
• Verify NCOS level of console. ©GHTROUT
• Verify that NIT1 through NIT4 (or other night numbers) are
pointing to valid numbers. ©GHTROUT

• EXTT prompt should be NO to work in conjunction with trunk

route disconnect controls (See RDB) ©GHTROUT
RDB - Trunk • Verify that every route has a TARG assigned. ©GHTROUT
Route Data • Confirm that FEDC and NEDC are set correctly. ETH is typical,
Block however for maximum security in blocking trunk to trunk
connections, set NEDC to ORG and FEDC to JNT ©GHTROUT
• Confirm that ACCD's are a minimum of four digits long
(unless for paging). ©GHTROUT
• If ESN signaling is active on trunk routes, verify that it needs
to be. ESN signaling, if not required, should be avoided.
©GHTROUT

• NOTES ON TGAR: For demonstration purposes, this document

suggests that sets be a "TGAR 1". The only requirement for
TGAR is that it match one of the TARG numbers assigned in
the Route Data Block ©GHTROUT
ACD - • Verify ACD queues and associated NCFW numbers. Verify all
Automatic Call referenced extensions. ©GHTROUT
Distribution
DISA - Direct • Remove DISA if not required. If required, verify that security
Inward System codes are in use. ©GHTROUT
Access
ESN - Electronic • AC1 is typically "9". If there is an AC2 assigned, verify its
Switched use.
Network • If TOD or ETOD is used - verify what NCOS levels are
changed, when they are changed and why they are changed.
©GHTROUT
• Apply FLEN to your SPNs to insure nobody is ever allowed to
be transferred to a partially dialed number, like "Transfer me
to 91800" ©GHTROUT

• Study EQAR (Equal Access Restriction) to insure that users

can only follow a "Carrier Access Code" with a zero rather
than a one: (1010321-1-414-555-1212 is blocked but
1010321-0-414-555-1212 is allowed with EQAR)
©GHTROUT
NCTL - Network • Use LD81 FEAT PRINT to verify all NCOS being used.
Control • Does NCOS 0 = FRL 0? Does NCOS X always equal FRL X in
 the NCTL? ©GHTROUT

• Does FRL 0 have any capabilities? - It should not be able to

dial anything. ©GHTROUT
FCAS - Free Call • Confirm the need to use FCAS and remove it if possible. FCAS
Area Screening is usually a waste of system memory and complicates the
system without saving money. ©GHTROUT
DGT (DMI) - • Confirm all numbers referenced in the "insert" section of each
Digit DMI table. ©GHTROUT
Manipulation
RLB - BARS • Are any RLB ENTR'S assigned FRL 0 - typically, only the RLB
Route List Block that handles 911 calls should have an FRL 0. ©GHTROUT

• If DMI is in use, confirm all "inserted" numbers. ©GHTROUT

CDP - BARS • Are all CDP numbers valid? Check the RLBs they point to and
Coordinated see what the DMI value is. Confirm insertions. ©GHTROUT
Dialing Plan
NET - ALL - • Add 000,001,002,003,004,005,006,007,008,009 as SPNs
BARS Network pointing to a route list block that is set to LTER YES. These
Numbers entries block transfers to "ext. 9000" and similar numbers.
©GHTROUT
• Point SPN "0" to a RLI with a high FRL, then consider adding
new SPNs of 02, 03, 04, 05, 06, 07, 08, 09 to point to a RLI
with a lower FRL so that users cannot dial "0", but can dial
"0+NPA credit card calls. ©GHTROUT
• Check FRL of 0, 00, 011 and confirm that each is pointed to
separate NET entry requiring a high FRL. ©GHTROUT
• Remove all of shore NPAs (Like 1-809 Dominican Republic) if
possible. Regulations are almost non-existent in some of
those areas and they are hot fraud targets. ©GHTROUT
• Verify blocking 900 and 976 access. Also consider blocking
the NXX of your local radio station contest lines. Users will
go nuts calling a radio station to win a free toaster, taking
over all the trunks in your phone system. ©GHTROUT

• Restrict the main numbers and DID range within the BARS
system. There is no need to call from an outgoing to an
incoming line at the same location. ©GHTROUT
TRUNKS • Confirm that all trunks have TGAR assigned. ©GHTROUT
• Confirm that all incoming and TIE trunks have class of service
SRE assigned. (caution on networked systems) ©GHTROUT
• Confirm that all trunks have an NCOS of zero. ©GHTROUT

• NOTES ON TGAR: For demonstration purposes, this document

suggests that sets be a "TGAR 1". The only requirement for
TGAR is that it match one of the TARG numbers assigned in
the Route Data Block ©GHTROUT
SETS-PHONES • Does every phone have a TGAR of 1 assigned? (This must be
checked set by set, TN by TN). ©GHTROUT
• Can you change every phone that is UNR to CTD? Review
LD81 FEAT PRINT to find out the UNR sets. CTD class of
service is explained below. ©GHTROUT
• Confirm that all sets are assigned CLS CFXD? ©GHTROUT
• Confirm that the NCOS is appropriate on each set.
©GHTROUT
• In Release 20 or above, removing transfer feature may be
appropriate. ©GHTROUT
• Confirm that all sets CFW digit length is set to the system DN
length. ©GHTROUT
• NOTES ON TGAR: For demonstration purposes, this document
suggests that sets be a "TGAR 1". The only requirement for
TGAR is that it match one of the TARG numbers assigned in
the Route Data Block ©GHTROUT

• Apply Flexible Trunk to Trunk Connections on the set (Such as

CLS=FTTR), and FTOP in the CDB if deemed appropriate.
These restrictions are done on a set by set basis and allow or
deny the ability to transfer incoming calls out of the facility.
©GHTROUT
VOICE MAIL • Each port should be CLS of SRE ©GHTROUT
PORTS • Apply Flexible Trunk to Trunk Connections on the TNs
(CLS=FTTR), and verify FTOP in the CDB ©GHTROUT
• Each port should be NCOS 0 - NCOS 0 must be known to be
too low to pass any call ©GHTROUT
• Each port should be TGAR 1 (all trunk routes must be TARG 1
also) ©GHTROUT
• NOTES ON TGAR: For demonstration purposes, this document
suggests that sets be a "TGAR 1". The only requirement for
TGAR is that it match one of the TARG numbers assigned in
the Route Data Block ©GHTROUT

• NOTE: If you are used to your Mail system doing outcalling,

you can forget about that working after applying these
restrictions. An alternative that will allow Outcalling but
restrict thru-dialing to external numbers is to keep the NCOS
and CLS restrictions high enough to place outcalls, but "Apply
Flexible Trunk to Trunk Connections on the TNs (CLS=FTTR),
and verify FTOP in the CDB" as indicated in point 1 above.
©GHTROUT

CLASS OF SERVICE AND TRUNK GROUP ACCESS RESTRICTIONS: ©GHTROUT

EXPLANATION OF CLASS OF SERVICE SRE: ©GHTROUT

• NTP DEFINITION: Allowed to receive calls from the exchange network.

Restricted from all dial access to the exchange network. Allowed to access the
 exchange network through an attendant or an unrestricted telephone only.
©GHTROUT
• Essentially, an SRE set can do nothing on it's own except dial internal and TIE
line extensions. If a trunk is SRE - it will work normally and allow conference
calls and transfers. ©GHTROUT

EXAMPLES OF 'SRE' IN USE: ©GHTROUT

• Voice Mail cannot connect to an outgoing line, but can receive incoming calls.
©GHTROUT
• Callers on the far end of a TIE line cannot call out through your end (for their
sake, both ends should be SRE). ©GHTROUT

EXPLANATION OF CLASS OF SERVICE CTD: ©GHTROUT

• If a route access code is accessed (if there was no match between the TGAR
and TARG), the caller cannot dial 1 or 0 as the leading digits. ©GHTROUT
• If the caller makes a "dial 9" BARS call, the NCOS will control the call.
©GHTROUT

EXPLANATION OF TGAR AND TARG: ©GHTROUT

• The best restriction is to have all trunk routes TARG'd to 1 and all TNs
(including actual trunk TNs) TGAR'd to 1. This will block all access to direct
trunk route selection. ©GHTROUT

BENEFITS OF IMPLEMENTING THESE SECURITY RESTRICTIONS ©GHTROUT

• No incoming caller will have access to an outside line unless physically

transferred or conferenced by an internal party. If voice mail ports are SRE
and NCOS 0 and have a TGAR matching the TARG - they will not be able to
transfer a call out of the system, regardless of the voice mail system's
resident restrictions assigned. ©GHTROUT
• No phone will be able to dial a trunk route access code. Consider allowing
telecom staff this ability for testing. ©GHTROUT
• Layered security: ©GHTROUT
• If in phone programming, TGAR was overlooked on a phone, the CTD
class of service would block the user from dialing a 0 or 1 if they
stumble upon a route access code.
• If in programming, the CTD class of service was overlooked, both
TGAR and NCOS would maintain the restrictions. ©GHTROUT
• If in programming, the NCOS is overlooked, it will defaults to zero,
which is totally restricted if NCTL and RLBs are set up correctly.
©GHTROUT
 BARS
What BARS Does RLI - ROUTE LIST INDEX (Look Below)

Example: You have a dedicated long The RLI is the List of Trunk Routes an
distance route at your company. You NPA, NXX or SPN can call out on.
also have a local Telco trunk route.
The cost to call Area Code 312 is In the example below, you can also refer to
cheaper over the Long Distance THIS
route. If that long distance trunk
route fails or becomes busy, you RLI 4 - The LIST in the example
would like some callers to fail over to
the local Telco route. ENTR 0 The first entry in the LIST
LTER NO
With BARS, you can program the ROUT 15 The Long Distance route in
system so the long distance route is the example
preferred for all calls to NPA 312, but TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
during a failure or all trunks busy
CNV NO
condition, the most important users
EXP NO
(or any users you specify) will FRL 3
automatically route over the local DMI 0
Telco lines. You assign NPAs to Route FCI 0
Lists. Route Lists contain the trunk FSNI 0
routes OHQ YES
CBQ YES
The column to you your left (no, the
other left...on the right) is a route list
printed out. ENTR 1 The second entry in the LIST
LTER NO
ROUT 10 The local Telco route in
the example
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES
FRL 3
DMI 12
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 2

Back to TOP
BARS 101 - Quick Tour of a Meridian 1 BARS Call
Click the underlined links to take you to the details and/or explanation of that
prompt.

Basic Automatic Route Selection. If you dial "9", you are accessing BARS. "9" is the
"BARS Access Code"

1. A telephone dials "9" - BARS activates.

2. The telephone dials a number - Example: 1312-XXX-XXXX
3. The PBX holds the digits while it looks up "1312" to figure out what Route List
to use for processing the call.
4. The Route List determines the possible trunk routes that can be used.
5. The Route List checks the facility restriction level of the telephone and
compares it to its own required facility restriction level.
6. The Route List checks to see if any special digit manipulation should be
performed.

LD90 NET Back to TOP

The LD90 Network overlay is where area codes and exchanges

are defined. If a prefix is not entered into LD90, it
cannot be dialed through BARS. Each area code or exchange
refers to a "Route List" or RLI which contains the
instructions for routing the call.

>ld 90
ESN000
REQ prt
CUST 0
FEAT net
TRAN ac1
TYPE npa
NPA 1312
NPA 1312 <-- This is the network number (prefix)
RLI 11 <-- This is the Route List that the prefix gets
instruction from
DENY 976 <-- This is an exchange in NPA 312 that is
blocked. Optional, but common
SDRR DENY CODES = 1
DMI 0
ITEI NONE
REQ end

LD86 RLB (or RLI) Back to TOP

The RLB is a "list" of possible trunk routes that an area

code or exchange (NPA, NXX, SPN) can be selected for the
call. Each "ENTR" or list entry contains a trunk route.
Each entry also has a "minimum Facility Restriction Level"
or "FRL" that must be met or exceeded before a phone can
access that entry.

In the following example, the first ENTR can be accessed by

phones whose NCOS equals an FRL of 3 or above. The second
entry can only be accessed by phones whose NCOS equals an
FRL of 6 or above. For example, less important phones
might be NCOS 3 and very important phones might be NCOS 6.
If all trunks in the first route choice were busy, only
important phones would have access to the trunks in the
second route choice.

Along with the trunk route and the FRL, you can apply
specific "digit manipulation" with the DMI entry. The DMI
entries are explained here.

>ld 86
ESN000
REQ prt
CUST 0
FEAT rlb
RLI 11
RLI 11
ENTR 0 <-- This is the list's first "Entry Number"
LTER NO
ROUT 15 <-- This is the first choice Trunk Route Number
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 3 <-- This is the Facility Restriction Level
DMI 10 <-- This is the Digit Manipulation Index Number
FCI 0
FSNI 0
OHQ YES
CBQ YES
ENTR 1 <-- This is the list's second "Entry Number"
LTER NO
ROUT 9 <-- This is the second choice Trunk Route Number
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES <-- This is considered the "expensive" choice
FRL 6 <-- Note that the Facility Restriction Level is higher
DMI 0 <-- Note no digit manipulation is required for this
trunk route
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 3

REQ end

LD87 NCTL Back to TOP

The FRL to NCOS "relationship" is built in the NCTL data

block. The FRL and the NCOS do not necessarily have the
equal one another, however they usually do. A higher
FRL/NCOS has more capability than a lower FRL/NCOS. For an
NCOS number to have any capability, it must first be
defined in the NCTL data block.

>ld 87
ESN000
REQ prt
CUST 0
FEAT nctl
NRNG 0 7 <-- Range from NCOS 0 through 7 was requested
SOHQ NO
SCBQ YES
CBTL 10
---------------
NCOS 0
EQA NO
FRL 0
RWTA NO
NSC NO
OHQ NO
CBQ NO
MPRI 0
PROM 0
---------------
NCOS 1
EQA NO
FRL 1
RWTA NO
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT I
RADT 0
SPRI 0
MPRI 0
PROM 0
---------------
NCOS 2
EQA NO
FRL 0
RWTA NO
NSC NO
OHQ NO
CBQ NO
MPRI 0
PROM 0
---------------
NCOS 3
EQA NO
FRL 3 <-- NCOS 3 equals FRL 3.
RWTA YES
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT I
RADT 10
SPRI 0
MPRI 0
PROM 0
---------------
NCOS 4
EQA NO
FRL 4
RWTA YES
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT A
RADT 10
SPRI 0
MPRI 0
PROM 0
---------------
NCOS 5
EQA NO
FRL 5
RWTA NO
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT A
RADT 10
SPRI 0
MPRI 0
PROM 0
---------------
NCOS 6
EQA NO
FRL 6 <-- NCOS 6 equals FRL 6.
RWTA NO
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT A
RADT 0
SPRI 0
MPRI 0
PROM 0
---------------
NCOS 7
EQA NO
FRL 7
RWTA NO
NSC NO
OHQ NO
CBQ YES
RETT 10
RETC 5
ROUT A
RADT 0
SPRI 0
MPRI 0
PROM 0
TOHQ NONE

LD86 Digit Manipulation Back to TOP

The Digit Manipulation data blocks are where special

prefixes are entered before numbers are sent out over
trunks. An example of digit manipulation is where a
1010XXX carrier access code must be inserted before a
number is processed over a trunk.

REQ prt
CUST 0
FEAT dgt
DMI 10
DMI 10 <-- This is simply the index number.
DEL 1 <-- This says "delete the first digit after "9"
CTYP NCHG
REQ prt
CUST 0
FEAT dgt
DMI 3
DMI 3
DEL 0 <-- This says "delete nothing after 9"
INST 1010288 <-- This says "Insert 1010288 after 9 and
before the actual number dialed". 1010288 is a way to
select ATT for a call.
CTYP NCHG
REQ end

Telephone Back to TOP

This is simply a telephone's data block

DES 5135
TN 004 0 14 00
TYPE 500
CDEN 4D
CUST 0
DN 5135 MARP
CPND
NAME Typical User
XPLN 9
 DISPLAY_FMT FIRST,LAST
AST NO
IAPG 0
HUNT
TGAR 1
LDN NO
NCOS 5 <-- What FRL does this equal?
SGRP 0
RNPG 0
LNRS 16
XLST
SCI 0
CLS CTD DTN FBD XFA WTA THFD FND HTD ONS
LPR XRA CWD SWD MWA LPD XHD CCSD LNA TVD
CFTD SFD C6D PDN CNID CLBD AUTU
ICDD CDMD EHTD MCTD
GPUD DPUD CFXD ARHD OVDD AGTD CLTD LDTA ASCD
MBXD CPFA CPTA DDGA NAMA
SHL ABDD CFHD
USRD BNRD OCBD
RCO 0
PLEV 02
FTR CFW 4
DATE 28 NOV 1978

LD86 ESN - the Start of BARS Back to TOP

The ESN data block is the root of BARS. Before BARS can
be set up, the ESN data block must be defined.

>ld 86
ESN000
REQ prt
CUST 0
FEAT esn
MXLC 0
MXSD 30
MXIX 0
MXDM 100
MXRL 80
MXFC 60
MXFS 0
MXSC 120
NCDP 4
AC1 9 <-- This is where "9" is defined
AC2
DLTN YES
ERWT YES
ERDT 0
TODS 0 00 00 23 59 <-- This section refers only to time of
day routing controls
RTCL DIS
NCOS 0 - 0 <-- This section refers only to time of day
routing controls
NCOS 1 - 1
NCOS 2 - 2
NCOS 3 - 3
NCOS 4 - 4
NCOS 5 - 5
NCOS 6 - 6
NCOS 7 - 7
<continued to 99...>
NCOS 99 - 99
ETOD
TGAR NO
REQ end
ENTR = ENTRY IN RLI. An ENTR is just one of the entries in a a Route List
Index. Each Trunk Route specified in a Route List is defined in it's own
ENTR

EXAMPLE

ENTR 0
LTER NO
ROUT 15
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0
FCI 0
FSNI 0
OHQ YES
CBQ YES

ENTR 1
LTER NO
ROUT 7
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES
FRL 5
DMI 12
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 2
ROUT = The TRUNK ROUTE one of the ENTR's in a RLI will use for calls

RLI with ROUT Highlighted

ENTR 0
LTER NO
ROUT 15
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0
FCI 0
FSNI 0
OHQ YES
CBQ YES

ENTR 1
LTER NO
ROUT 7
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES
FRL 5
DMI 12
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 2
FRL = FACILITY RESTRICTION LEVEL OF ENTRY IN RLI
The basic restriction philosophy is this: Each ENTR of a Route List has an
FRL that must be met or exceeded by the telephone attempting to dial. The
telephone is assigned it's "FRL value" at the NCOS prompt. The NCOS and
the FRL are linked in the LD87 NCTL datablock

EXAMPLE OF FRL IN AN RLI

ENTR 0
LTER NO
ROUT 15
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0
FCI 0
FSNI 0
OHQ YES
CBQ YES

ENTR 1
LTER NO
ROUT 7
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES
FRL 5
DMI 12
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 2
DMI = DIGIT MANIPULATION INDEX
Create an instruction to delete or insert digits and apply it to all calls using a
RLI's Entry

DMI 12 - See Below

DEL 0 (none)
INST 1010288
CTYP NCHG

Example. If a call is sent out the second ENTR below, it will go out Trunk
Route 7. Before the call is outpulsed, the digits "1010288" are inserted. An
example of someone who wants to pick ATT for the long line carrier.

DMI IN RLI

ENTR 0
LTER NO
ROUT 15
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0 (Not here - assume Trunk Route did not need it. Look below)
FCI 0
FSNI 0
OHQ YES
CBQ YES

ENTR 1
LTER NO
ROUT 7
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP YES
FRL 5
DMI 12 <-----------------H E R E
FCI 0
FSNI 0
OHQ YES
CBQ YES
ISET 2
MFRL 2
EACH NCOS = AN FRL - DEFINED IN FRL = FACILITY RESTRICTION LEVEL
LD87 NCTL OF ENTR IN RLI
The basic restriction philosophy is this:
NCTL DATABLOCK Each ENTR of a Route List has an FRL that
must be met or exceeded by the
>LD 87 telephone. The telephone is assigned it's
ESN000 FRL value in the NCOS prompt. The NCOS
REQ PRT and the FRL are linked in the LD87 NCTL
CUST 0 datablock
FEAT NCTL
-------------- RLI ROUTE LIST
NCOS 1
EQA NO
ENTR 0
FRL 1 = VALUE OF NCOS 1
LTER NO
RWTA NO
ROUT 15
NSC NO
TOD 0 ON 1 ON 2 ON 3 ON
OHQ NO
4 ON 5 ON 6 ON 7 ON
CBQ NO
CNV NO
MPRI 0
EXP NO
PROM 0
FRL 2
--------------
DMI 0
NCOS 2
FCI 0
EQA NO
FSNI 0
FRL 2 = VALUE OF NCOS 2
OHQ YES
RWTA NO
CBQ YES
NSC NO
OHQ NO
CBQ NO
ENTR 1
MPRI 0
LTER NO
PROM 0
ROUT 7
--------------
TOD 0 ON 1 ON 2 ON 3 ON
NCOS 5
4 ON 5 ON 6 ON 7 ON
EQA NO
CNV NO
FRL 5 = VALUE OF NCOS 5
EXP YES
RWTA NO
FRL 5
NSC NO
DMI 12
OHQ NO
FCI 0
CBQ YES
FSNI 0
RETT 10
OHQ YES
RETC 5
CBQ YES
ROUT A
ISET 2
RADT 10
MFRL 2
SPRI 0
MPRI 0
PROM 0

NCOS Meeting or Exceeding the FRL to Proceed | Return to Top of Page

BARS Cars represents a Route List and it's components.

• The cars are the calls

• The guards are verifying the FRL is met before cars enter the "ENTR".
• The "dead" looking cars before the first sign did not meet the required NCOS-
FRL
• The turnoffs are the Trunk Routes leading to the carrier
• The DMI guy near the "red DMI pump", places the digits on the car before it is
released to the carrier.
 Figuring Out What You Have - Printing Your BARS Configuration
Back to BARS101

If you want to organize records for easy reading, download this simple Excel file
that has a worksheet for each report. Also included is a "line number" column so you
can perform sorting. Not rocket science, but Excel is nice for Meridian printouts
when you create a separate sort column.

Report Overlay Load How to Print. Enter

LD then see the
Listed in the same order you would use if LD Number PROMPT and your
you were building BARS from scratch.. RESPONSE below.
You may print the reports in any order as
long as you can keep track of what report [CR] means "just hit
starts where. enter"
LD86 ESN: ESN Data Block - Controls REQ PRT
some global BARS settings and limits. LD 86 CUST 0
FEAT ESN
LD87 NCTL: Network Control (Relationship REQ PRT
Between FRL and NCOS). See LD87 NCTL CUST 0
LD 87 FEAT NCTL
in diagram below
NRNG 0 7
LD86 DGT: Digit Manipulation - The digits REQ PRT
that may be inserted or deleted for specific CUST 0
LD 86 FEAT DGT
dialed numbers. See LD86 DMI/DGT in
diagram below DMI [CR]
LD87 FCAS: Free Call Area Screening REQ PRT
CUST 0
LD 87 FEAT FCAS
FCI [CR]
LD86 RLB: Route Lists - The order that the REQ PRT
system selects trunks for specific dialed CUST 0
LD 86 FEAT RLB
numbers. See LD86 RLB/RLI in diagram
below RLI [CR]
LD87 CDP: Coordinated Dialing Plan and REQ PRT
Steering Codes and what Route List they CUST 0
LD 87 FEAT CDP
use.
TYPE ALL
LD90 NET: Network Numbers - Area Codes REQ PRT
and Exchanges and what Route Lists they CUST 0
use. See LD90 NET in diagram below LD 90 FEAT NET
TRAN AC1
TYPE ALL
LD90 SUM: ESN Network Summary. Just a REQ PRT
trivial report. Note there is a delay before CUST 0
LD 90 FEAT NET
the printout starts.
TRAN SUM
LD88 AUTH - if you administer it, you know better
then to not have a backup.