BARS programming course
- Programming -
General
Programming can be broken into three arbitrary sections: Planning and information gathering, Preliminary setup, and Functional programming. The planning stage is the most critical because no matter what follows, if the first stage was not done properly, the resulting behavior will not be the expected functionally. The preliminary programming set a group of memory sizes. This must be done before any other BARS related programming, but can be changed later if conditions change. The final stage consists of several overlays or loads and functions that actually define BARS operation.
Detailed Sequence of Programming
Planning
See the Planning & Programming Guide.
For each station, determine the following:
- Call locations: Local, In-country long distance, International long distance. In the US, interlata and intralata calls will also have to be considered.
- Allowed call types: Direct Distance Dialed (DDD), Operator assisted, Toll free long distance, and special service codes.
- Allowed calling times: Both the time of day (TOD) and day of the week (ETOD) should be considered and recorded. BARS can split the day into eight parts, and the week into three. Any period or group of periods can be used to turn a facility (a group of trunks called a route) off. Period seven can be used to change a station user's Network Class Of Service (NCOS) number and thus change the user's ability to make different types of calls. A user might be allowed to make international calls only during normal business hours, but can only make local calls at other times. Account or authorization codes can be used to override this or to allow certain users to "unlock" any phone at any time if needed for a call.
- Allowed facilities: Which of the equipped facilities will the user be allowed to use? Local trunks, International Voice Gateway trunks (IVG), private lines that are reserved for a particular agency or work group, and others are all possible facilities that might be present and available.
- Allowed features: On Hook Queuing (OHQ) and Call back Queuing (CBQ) are two possible features that will have to be considered. The station's assigned Trunk Group Access Restriction (TGAR) and NCOS should be noted for future reference. Normal practice will not use TARG/TGAR restrictions, but it could be required if there are private trunk in general use for outgoing calls.
For each trunk route, determine the following:
- Dialing Patterns: You will need to know what has to be dialed on each trunk route to complete each type of call that is to be allowed on that route. How many digits will be required for each type of call? Will a country code be required? What about sending a city code on a local call? Will a toll access digit need to be sent?
- Preferred usage sequence: Determine which routes are most desirable for each
type of call, the second most desirable, the third
etc. for each dialing pattern. Also, determine how far down the list a user may progress before being given Expensive Route Warning Tone (ERWT) or being denied access. - Permissions: Tie trunks have a TGAR and NCOS as well as a TARG. Determine what type of calls the tie trunks will be allowed to originate as well as there assigned TARG values.
Select system wide parameters:
Use the above information to determine the minimum value for each of these parameters. It is suggested that you increase the determined value by 10% to allow for easy growth. This is only a suggestion because any of these values can be increased at any time. Nortel does not state a memory conflict in this area so you could actually set every one of these parameters to its maximum without causing a problem.
- Maximum number of location codes (ISDN networking). This is a NARS function andwill not be addressed by this course.
- Maximum number of Supplemental Digit Restriction Blocks.
- Maximum number of incoming trunk group exclusion tables.
- Maximum number of digit manipulation tables.
- Maximum number of route lists. These are the lists of trunk routes in the desiredorder of usage.
- Maximum number of free calling area screening tables. These tables only work whenthe dialed number type has been flagged as NPA in load 90. If the local dialingpattern can not be made to fit the North American Plan Area (NAPA) pattern, they can notbe used.
- Maximum number of free special number screening tables.
- Maximum number of special common carrier entries. Nortel BARS instructors will notaddress this area and there is little chance that it will ever be needed by a non-US system, therefore it will not be addressed in this class either.
- BARS access code. This will usually be "9", but it may have to be takenfrom a trunk route before it can be used here.
- Will second dial tone be provided?
- Will ERWT be provided to anyone? If it is not enabled in the system parameters, itcannot be used by anyone in the route lists.
- Will trunk route access restrictions be checked? In most cases, it is notdesirable to have this enabled, but there are conditions which can only be met by usingthis capability.
- What intercept treatment is desired for calls that fail to complete? Options ofReorder tone (Nortel calls it "Overflow Tone"), Recorded announcement(Pronouncement Reorder or PRO for short), and Attendant intercept are the availablechoices. You may select one choice for each call originator type (Station or DISA,Attendant, Central Office Trunk, or Direct Inward Dial trunk). In every case that Ican think of, DID and DISA trunks should not have any access to BARS. For each ofthe originator types you have a choice of intercept depending upon the point in the BARSprocessing the call was denied. These points are: if programming is not completed atthe time of the call, Network Translations, Supplemental Digit Restriction andRecognition, and at the trunk selection phase.
Preliminaries:
The following changes in load 15 can be done at any time, or even skipped if the default values are acceptable. The load 86 ESN programming, however, must be done before any other BARS programming is attempted.
Adjust intercept treatments if required.
| LD 15 | ||
| REQ: | CHG | |
| TYPE: | INT_DATA | Gate opener |
| CUST | 0 - 99 | Select a customer, typically 0 |
| ACCD | OVF OVF OVF ATN | Access denied (Stn | Atnd | CO Trunk | DID) |
| CTVN | OVF OVF OVF ATN | Vacent number |
| MBNR | OVF OVF OVF ATN | Maintenance busy |
| CTRC | OVF NAP OVF NAP | Restricted call |
| CLDN | NAP OVF NAP NAP | Calls to listed directory number |
| NINV | OVF OVF OVF ATN | Invalid NARS/BARS call |
| NITR | OVF OVF OVF ATN | Invalid NARS/BARS translation |
| NRES | OVF OVF OVF ATN | Restricted NARS/BARS call |
| NBLK | OVF OVF OVF ATN | Blocked NARS/BARS call (no usable trunk available) |
| : | Remaining fields do not affect NARS/BARS calls.
<CR> to accept the default values. |
Establish buffer sizes since no default exists for any of the following "MX - -".
| LD 86 | ||
| REQ | NEW | Can't change something that doesn't exist. |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | ESN | Electronic Switched Network |
| MXLC | Maximum number of location codes for NARS use | |
| MXSD | Maximum number of SDRR blocks | |
| MXIX | Maximum number of incoming trunk group exclusion tables | |
| MXDM | Maximum number of digit manipulation tables | |
| MXRL | Maximum number of route lists | |
| MXFC | Maximum number of free calling area screening tables | |
| MXFS | Maximum number of free special number screening tables | |
| CDP | (YES) NO | Coordinated Dialing Plan feature for this customer? |
| MSCC | Global Knowledge won't admit anything about this feature. | |
| AC1 | 9 | Typical BARS access code |
| AC2 | Only used by NARS | |
| DLTN | (YES) NO | Second dial tone provided after dialing the access code |
| ERWT | (YES) NO | Expensive Route Warning Tone customer wide enable |
| TODS | Define time of day schedules. All 24 hours default to schedule 0 | |
| RTCL | (DIS) YES | Routing controls enabled? |
| NMAP | xx yy | NCOS map NCOS xx becomes NCOS yy when RTCL= YES, and either TOD 7 is active or when the attendant's <RTC> key is pressed. |
| ETOD | Routing control for days of the week 1 = Sun ... 7 = Sat | |
| TGAR | (NO) YES | Checks for trunk group access restrictions on BARS calls. |
For example:
Set anything 'MX' to 255!
| LD 86 | ||
| REQ | new | |
| CUST | 0 | |
| FEAT | esn | Feature = ESN (Electronic switched network) |
| MXLC | 255 | Max.# of location codes for NARS use |
| MXSD | 255 | Max.# of SDRR blocks |
| MXIX | 255 | Max.# of incoming trunk group exclusion tables |
| MXDM | 255 | Max.# of digit manipulation tables |
| MXRL | 255 | Max.# of route lists |
| MXCM | 255 | Max.# of CLID manipulation lists (1-256) |
| MXFC | 255 | Max.# Free Calling area screening tables |
| MXFS | 255 | Max.# of free special number screening tables |
| CDP | yes | Coordinated Dialing Plan feature for this customer? |
| MXSC | 255 | Max.# of Steering Codes (if CDP=yes) |
| NCDP | 4 | Max.# Number of digits in CDP DN (DSC + DN or LSC + DN) (if CDP=yes) |
| AC1 | 9 | Typical BARS access code |
| AC2 | 8 | Only used by NARS |
| DLTN | yes | Second dial tone provided after dialing the access code |
| ERWT | yes | Expensive Route Warning Tone customer wide enable |
| ERDT | Expensive Route Delay Time: 0-(6)-10 | |
| TODS | Define time of day schedules. All 24 hours default to schedule 0 | |
| RTCL | Routing Controls (DIS) YES | |
| TGAR | Checks for trunk group access restrictions on BARS calls. |
Functional Programming:
The following has a direct affect on the functioning of BARS. In some cases the suggested order just keeps the jumping from one load to another at a minimum, in other cases it sets up data blocks that are indexed into by subsequent items.
Digit Manipulation
| LD 86 | ||
| REQ | NEW | Select a customer, typically 0 |
| CUST | 0 - 99 | |
| FEAT | DGT | Digit manipulation |
| DMI | Can't be more than MXDM - 1 | |
| DEL | Number of leading digits to delete | |
| INST | Actual digit string to prefix to what the user dialed. | |
| SCCI | Special Common Carrier index. Ignore this, Global Knowledge does. | |
| CTYP | Changes the call type flag on an ISDN call. It has no effect onother facilities. |
Network restrictions for station NCOS
| LD 87 | ||
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | NTCL | Only NCOS FRL has to be defined in this block, all else is optional. |
| SOHQ | (NO) YES | Off-hook queuing option? |
| SCBQ | (NO) YES | Call-back queuing option? |
| NRNG | NCOS range or | |
| NCOS | NCOS number to be modified | |
| ADRL | ||
| MPL | ||
| EQA | (NO) YES | Equal access associated with this NCOS group? |
| FRL | (0) - 7 | Facility Restriction Level (the higher, the less restricted) |
| RWTA | (NO) YES | expensive route warning tone for the users of this NCOS? |
| NSC | ||
| OHQ | (YES) NO | Off-hook queuing eligibility? |
| CBQ | (NO) YES | Call Back queuing eligibility? |
| RETT | ||
| RETC | ||
| SPRI | Starting priority in CBQ | |
| MPRI | Maximum Priority attainable in CBQ | |
| PROM | Priority Promotion timer | |
| TOHQ | TCOS OHQ eligibility? |
Free calling area screening of NPA numbers
| LD 87 | ||
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | FCAS | This only works on Area Codes (NPA in ENPA format). |
| FCI | An index into this table. | |
| NPA | 3-digit area code to be screened | |
| NXX | DENY or ALOW | Will this table list all denied or allowed numbers? |
| DENY or ALOW | 3-digit office code or range to be screened. This table defines all 800 possible office codes. Any number not listed in a DENY table is allowed, and anynumber not listed in an ALOW table is denied. |
Free special number screening for additional digits
| LD 87 | ||
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | FSN | Use this to screen for additional digits after a service code or non-ENPA formatted code. |
| FSNI | An index into this table. | |
| SPN | 3-digit special number code to be screened | |
| XXX | DENY or ALOW | Will this table list all denied or allowed numbers? |
| DENY or ALOW | 3-digit code or range to be screened. This table defines all 1,000 possible codes. Any number not listed in a DENY table is allowed, and any number not listed in an ALOW table is denied. |
Build each required route list.
All load 86 and 87 programming listed above must be completed before starting this. This and the translation check table below are the actual working part of BARS. The Route List Block defines each group of trunks, (or Route), who can use it, and when it can be used.
| LD 86 | ||
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | RLB | Define a Route List Block. |
| RLI | Index number that will be referenced in the Translation Check Table. | |
| ENTR | 0 | Entry point or position in the list. 0 is always the first. |
| LTER | (NO) YES | NARS stuff (take the default) |
| ROUT | 0 - 511 | Actual Route Data Block number that was defined in LD 16 before starting BARS programming. |
| SCNV | (NO) YES | Skip conventional signaling (take the default) |
| TDET | (NO) YES | Tone detector used (take the default) |
| TOD | 0 - 7 | Time of day periods this entry can be used. |
| VNS | (NO) YES | (take the default) |
| CNV | (NO)YES | (take the default) |
| EXP | (NO) YES | Expensive Route Warning Tone to be provided (see ISET note) |
| FRL | (0) - 7 | Primary restriction tool. The higher the number, the more restrictive. |
| DMI | (0) - 999 | Digit Manipulation Index |
| ISDM | (0) - 255 | ISDN D-channel down Digit Manipulation index |
| FCI | (0) - 255 | Free Calling Area Screening index |
| FSNI | (0) - 255 | Free Special Number Screening index |
| BNE | (NO) YES | Business Network Extension Route NARS stuff (take the default) |
| SBOC | (take the default) | |
| IDBB | (take the default) | |
| IOHQ | (NO) YES | ISDN Off-hook queuing option |
| OHQ | (NO) YES | Off-Hook Queuing allowed |
| CBQ | (NO) YES | Call Back Queuing allowed |
| ISET | Number of entries in the Initial set (minimum of 1). The ESET orextended set begins just below this point. An entry must be in the ESET to give ERWT. |
Finally, build the Network Translation Check Table.
This table defines calls, or digit patterns, that can use each Route List Block. Since there are no "wild card" characters, it's suggested that you define all 800 possible ENPA codes when you build the table and point them at the IVG route list. It will save you from having to update the table every time a new area code is commissioned.
| LD 90 | ||
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | NET | For BARS it is always table 1 |
| TRAN | AC1 | |
| TYPE | HNPA | |
| HNPA | define your local Area Code. This is really an aspect of private networking. Outside of North America, you need not be concerned |
| LD 90 | ||
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | NET | |
| TRAN | AC1 | For BARS it is always table 1 |
| TYPE | NPA | |
| NPA | [1] xxx [yyy zzzz] | everything in [brackets] is optional |
| RLI | A route list you defined in LD 86 FEAT RLB | |
| SDRR | SDRR invoked for this call: ALOW, DDD, DENY, DID, ITED, LDDD, LDID, orSTRK | |
| selected type repeats and expects a response of digits to be tested. |
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | NET | |
| TRAN | AC1 | For BARS it is always table 1 |
| TYPE | NXX | |
| NXX | [1] yyy [zzzz] | [1] and [zzz] are optional elements, only 3 digits are required. |
| RLI | A route list you defined in LD 86 FEAT RLB. | |
| SDRR | SDRR invoked for this call: ALOW, DDD, DENY, DID, ITED, LDDD, LDID, orSTRK | |
| selected type repeats and expects a response of digits to be tested. |
| LD 90 | ||
| REQ | NEW | |
| CUST | 0 - 99 | Select a customer, typically 0 |
| FEAT | NET | |
| TRAN | AC1 | For BARS it is always table 1 |
| TYPE | SPN | |
| SPN | Special number digit sequence to be identified | |
| FLEN | (0) - 24 | Flexible length maximum. |
| INPL | (NO) YES | International dialing plan? |
| ITOH | (NO) YES | inhibit timeout handler? |
| RLI | A route list you defined in LD 86 FEAT RLB. | |
| CLTP | ||
| SDRR | SDRR invoked for this call: ALOW, ARRN, DDD, DENY, DID, ITED, LDDD, LDID, or STRK | |
| selected type repeats and expects a response of digits to be tested. |
SDRR Explained:
SDRR prevents a call from using a trunk without necessarily blocking the call. DENY will kill a call in its tracks. LDDD will divert a call to the local attendant. LDID will send a call directly to an internal extension without using an outgoing and incoming trunk (a trombone connection). In part this is accomplished by using a Digit Manipulation Table that was defined in LD 86 FEAT DGT. This table will tell the system how many digits to delete (not counting the access code which is always removed automatically on any BARS call) and insert if required to match the internal dialing pattern. ALOW (Nortel's spelling, not my mistake) is an exception to one of the previous conditions. Although there are no wild characters, a short digit string includes all possible longer strings unless excluded (in this case excluded from being blocked) by a longer digit sequence in an ALOW list. The remaining types are for networking applications and will not be addressed this side of NARS.