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 - Configuration

Verify that History File is in use. ©GHTROUT

PWD - Passwords

Verify that FLTH (failed login attempt threshold) is low 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 Data Block

Verify that CFTA (call forward to trunk access code) is set to 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 Route Data Block

Verify that every route has a TARG assigned. ©GHTROUT Confirm that FEDC and NEDC are set correctly. ETH is

typical, 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 - Automatic Call Distribution

Verify ACD queues and associated NCFW numbers. Verify all referenced extensions. ©GHTROUT

DISA - Direct Inward System Access

Remove DISA if not required. If required, verify that security codes are in use. ©GHTROUT

ESN - Electronic Switched Network

AC1 is typically "9". If there is an AC2 assigned, verify its use.

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 Control

Use LD81 FEAT PRINT to verify all NCOS being used. 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 Area Screening

Confirm the need to use FCAS and remove it if possible. FCAS is usually a waste of system memory and complicates the system without saving money. ©GHTROUT

DGT (DMI) - Digit Manipulation

Confirm all numbers referenced in the "insert" section of each DMI table. ©GHTROUT

RLB - BARS Route List Block

Are any RLB ENTR'S assigned FRL 0 - typically, only the RLB that handles 911 calls should have an FRL 0. ©GHTROUT

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

CDP - BARS Coordinated Dialing Plan

Are all CDP numbers valid? Check the RLBs they point to and see what the DMI value is. Confirm insertions. ©GHTROUT

NET - ALL - BARS Network Numbers

Add 000,001,002,003,004,005,006,007,008,009 as SPNs pointing to a route list block that is set to LTER YES. These 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 PORTS

Each port should be CLS of SRE ©GHTROUT 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 distance route at your company.  You also have a local Telco trunk route.  The cost to call Area Code 312 is cheaper over the Long Distance route.  If that long distance trunk route fails or becomes busy, you would like some callers to fail over to the local Telco route.

With BARS, you can program the system so the long distance route is preferred for all calls to NPA 312, but during a failure or all trunks busy condition, the most important users (or any users you specify) will automatically route over the local Telco lines.  You assign NPAs to Route Lists.  Route Lists contain the trunk routes

The column to you your left (no, the other left...on the right) is a route list printed out.

 

 

 

The RLI is the List of Trunk Routes an NPA, NXX or SPN can call out on.

In the example below, you can also refer to THIS

RLI 4 - The LIST in the example

ENTR 0 The first entry in the LISTLTER NOROUT 15  The Long Distance route in the exampleTOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 3 DMI 0FCI 0FSNI 0OHQ YESCBQ YES

ENTR 1 The second entry in the LISTLTER NOROUT 10  The local Telco route in the exampleTOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 3DMI 12FCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 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 90ESN000REQ prtCUST 0FEAT net

TRAN ac1TYPE npaNPA 1312NPA 1312 <-- This is the network number (prefix)RLI 11  <-- This is the Route List that the prefix gets instruction fromDENY 976 <-- This is an exchange in NPA 312 that is blocked.  Optional, but commonSDRR DENY CODES = 1DMI 0ITEI NONEREQ 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 ESN000REQ prtCUST 0FEAT rlbRLI 11RLI 11ENTR 0 <-- This is the list's first "Entry Number"LTER NOROUT 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 ONCNV NOEXP NOFRL 3 <-- This is the Facility Restriction LevelDMI 10 <-- This is the Digit Manipulation Index NumberFCI 0FSNI 0OHQ YESCBQ YESENTR 1 <-- This is the list's second "Entry Number"LTER NOROUT 9 <-- This is the second choice Trunk Route NumberTOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES <-- This is considered the "expensive" choiceFRL 6 <-- Note that the Facility Restriction Level is higherDMI 0 <-- Note no digit manipulation is required for this trunk routeFCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 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 ESN000REQ prtCUST 0FEAT nctlNRNG 0 7 <-- Range from NCOS 0 through 7 was requestedSOHQ NO

SCBQ YESCBTL 10---------------NCOS 0EQA NOFRL 0RWTA NONSC NOOHQ NOCBQ NOMPRI 0PROM 0---------------NCOS 1EQA NOFRL 1RWTA NONSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT IRADT 0SPRI 0MPRI 0PROM 0---------------NCOS 2 EQA NOFRL 0RWTA NONSC NOOHQ NOCBQ NOMPRI 0PROM 0---------------NCOS 3EQA NOFRL 3 <-- NCOS 3 equals FRL 3.RWTA YESNSC NOOHQ NOCBQ YESRETT 10RETC 5

ROUT IRADT 10SPRI 0MPRI 0PROM 0---------------NCOS 4EQA NOFRL 4RWTA YESNSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT ARADT 10SPRI 0MPRI 0PROM 0---------------NCOS 5EQA NOFRL 5RWTA NONSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT ARADT 10 SPRI 0MPRI 0PROM 0---------------NCOS 6EQA NOFRL 6 <-- NCOS 6 equals FRL 6.RWTA NONSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT ARADT 0

SPRI 0MPRI 0PROM 0---------------NCOS 7EQA NOFRL 7RWTA NONSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT ARADT 0SPRI 0MPRI 0PROM 0TOHQ 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 prtCUST 0FEAT dgt DMI 10DMI 10 <-- This is simply the index number.DEL 1 <-- This says "delete the first digit after "9"CTYP NCHGREQ prtCUST 0FEAT dgtDMI 3DMI 3DEL 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 NCHGREQ end

Telephone Back to TOP

This is simply a telephone's data block

DES 5135TN 004 0 14 00TYPE 500CDEN 4DCUST 0DN 5135 MARP     CPND     NAME Typical User      XPLN 9     DISPLAY_FMT FIRST,LASTAST NOIAPG 0HUNT TGAR 1LDN NONCOS 5  <-- What FRL does this equal?SGRP 0RNPG 0LNRS 16XLSTSCI 0CLS 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 OCBDRCO 0PLEV 02FTR CFW 4DATE 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 86ESN000REQ prtCUST 0FEAT esnMXLC 0MXSD 30MXIX 0 MXDM 100MXRL 80MXFC 60MXFS 0MXSC 120NCDP 4AC1 9 <-- This is where "9" is definedAC2DLTN YESERWT YESERDT 0TODS 0 00 00 23 59  <-- This section refers only to time of day routing controlsRTCL DISNCOS 0 - 0  <-- This section refers only to time of day routing controlsNCOS 1 - 1NCOS 2 - 2NCOS 3 - 3NCOS 4 - 4NCOS 5 - 5NCOS 6 - 6NCOS 7 - 7<continued to 99...>NCOS 99 - 99ETODTGAR NOREQ 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 0LTER NOROUT 15 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 2 DMI 0FCI 0FSNI 0OHQ YESCBQ YES

ENTR 1LTER NOROUT 7 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 5DMI 12FCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 2

ROUT = The TRUNK ROUTE one of the ENTR's in a RLI will use for calls

RLI with ROUT Highlighted

ENTR 0LTER NOROUT 15 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 2 DMI 0FCI 0FSNI 0OHQ YESCBQ YES

ENTR 1LTER NO

ROUT 7 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 5DMI 12FCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 2

FRL = FACILITY RESTRICTION LEVEL OF ENTRY IN RLIThe 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 0LTER NOROUT 15 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 2 DMI 0FCI 0

FSNI 0OHQ YESCBQ YES

ENTR 1LTER NOROUT 7 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 5DMI 12FCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 2

 

DMI = DIGIT MANIPULATION INDEXCreate an instruction to delete or insert digits and apply it to all calls using a RLI's Entry

DMI 12 - See BelowDEL 0 (none)INST 1010288CTYP 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 0LTER NOROUT 15 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 2 DMI 0 (Not here - assume Trunk Route did not need it.  Look below)FCI 0FSNI 0OHQ YESCBQ YES

ENTR 1LTER NOROUT 7 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 5DMI 12  <-----------------H E R EFCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 2

EACH NCOS = AN FRL - DEFINED IN LD87 NCTL

NCTL DATABLOCK

>LD 87ESN000REQ PRTCUST 0FEAT NCTL--------------NCOS 1EQA NOFRL 1 = VALUE OF NCOS 1RWTA NONSC NOOHQ NOCBQ NOMPRI 0PROM 0

FRL = FACILITY RESTRICTION LEVEL OF ENTR IN RLIThe basic restriction philosophy is this:  Each ENTR of a Route List has an FRL that must be met or exceeded by the telephone.  The telephone is assigned it's FRL value in the NCOS prompt.  The NCOS and the FRL are linked in the LD87 NCTL datablock

RLI ROUTE LIST

ENTR 0LTER NOROUT 15 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP NOFRL 2

--------------NCOS 2EQA NOFRL 2 = VALUE OF NCOS 2RWTA NONSC NOOHQ NOCBQ NOMPRI 0PROM 0--------------NCOS 5EQA NOFRL 5 = VALUE OF NCOS 5RWTA NONSC NOOHQ NOCBQ YESRETT 10RETC 5ROUT ARADT 10SPRI 0MPRI 0PROM 0

DMI 0FCI 0FSNI 0OHQ YESCBQ YES

ENTR 1LTER NOROUT 7 TOD 0 ON 1 ON 2 ON 3 ON    4 ON 5 ON 6 ON 7 ONCNV NOEXP YES FRL 5DMI 12FCI 0FSNI 0OHQ YESCBQ YESISET 2MFRL 2

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 ConfigurationBack 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

Listed in the same order you would use if you were building BARS from scratch..  You may print the reports in any order as long as you can keep track of what report starts where.

Overlay Load

LD Number

How to Print.  Enter LD then see the PROMPT and your RESPONSE below.

[CR] means "just hit enter"

LD86 ESN: ESN Data Block - Controls some global BARS settings and limits. LD 86

REQ  PRTCUST 0FEAT ESN

LD87 NCTL: Network Control (Relationship Between FRL and NCOS).  See LD87 NCTL in diagram below

LD 87

REQ  PRTCUST 0FEAT NCTLNRNG 0 7

LD86 DGT: Digit Manipulation - The digits that may be inserted or deleted for specific dialed numbers.  See LD86 DMI/DGT in diagram below

LD 86

REQ  PRTCUST 0FEAT DGTDMI  [CR]

LD87 FCAS: Free Call Area Screening

LD 87

REQ  PRTCUST 0FEAT FCASFCI  [CR]

LD86 RLB: Route Lists - The order that the system selects trunks for specific dialed numbers.  See LD86 RLB/RLI in diagram below

LD 86

REQ  PRTCUST 0FEAT RLBRLI  [CR]

LD87 CDP: Coordinated Dialing Plan and Steering Codes and what Route List they use.

LD 87

REQ  PRTCUST 0FEAT CDPTYPE ALL

LD90 NET: Network Numbers - Area Codes and Exchanges and what Route Lists they use.  See LD90 NET in diagram below LD 90

REQ  PRTCUST 0FEAT NETTRAN AC1TYPE ALL

LD90 SUM: ESN Network Summary.  Just a trivial report.  Note there is a delay before the printout starts.

LD 90

REQ  PRTCUST 0FEAT NETTRAN SUM

LD88 AUTH - if you administer it, you know better then to not have a backup.