Fletch

Thats a tall question and an audit of your current programming would be required in order to answer it.

Nothing is really 'standard' in NARS/BARS. Think of it as a kit of tools used to design a dialing plan that suits YOU. That's why it is so powerful.

__________________
Fletch
Nortel Emergency Services PLM

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts

Chas2002

Fletch - Can you post (in this message) all of your assistance in this issue? I'm still trying to get my mind wrapped around the entire Nars/Bars kit...

Thanks,
Chas2002

Fletch

NARS/BARS is a deep subject and everyone has their own 'spin' to it. There are some great references out there on it. Not sure a message board is the best place ti disect the issue.

NARS/BARS was a grueling 2 week class, and I understood a good deal before I took it. Back that up with at least 15 years of practical application after the class, and here I am today. You can't teach it in a few days, and it is more conceptual than anything else.

I can take 5 guys and say "Do this in NARS/BARS" and I will get 5 different ways of doing it. Each one of them is correct, and the end result is the same. SO I guess what I am saying is that you need to design a basic NARS/BARS functionality framework for your site, and them build on that will the features you want.

Many folks like to trash Nortel for their NARS/BARS complexity, but it is that very same complexity that allows it's extreme flexibility. Now when some one asks, "I want to do this, what do I change in my NARS/BARS to do it?", it's a hard question to answer. There are dozens of things that could be done, but without a full understanding of the NARS/BARS design for that switch, you could fix the problem at hand, but break quite a bit in the background. PRI and dialplans for a private voice network make it even more complex.

The customer site I was at just prior to returning to Nortel had a HUGE complex dialplan. The NARS/BARS were designed over a period of about 6 months, by several engineers. Strict change control was applied for ANY changes, and they were reviewed prior to implementation. Now this was the backbone of a global voice network, had probably some 1800 ESN entries, provided encrypted and unencrypted routing controls, and a guarantee of call completion everytime. Sure that is the extreme, but I wanted to give you an example of the power in it.

Back to the original question at hand: They want to restirct a phone, but allow some calls.

What is the NCOS to FRL mapping
What is the RLI / Route structure
How are NPA and NXX, SPN codes treated today
What is the overal design of the existing plan

Now you can determine what to do to handle it, without affecting the rest of the users.

__________________
Fletch
Nortel Emergency Services PLM

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts

HCJes

Binary,
Your quickest solution may be to see what NCOS are mapped to what FRLs. Once you have that you can change the MFRL and FRL on your routes that do local calling and long distance.

For example, say that NCOS 0 is mapped to FRL0.
If you change the MFRL to 1 and the FRL on your ROUTE ENTR to 1, people with NCOS 0 will not be able to get on that route.

As Chas and Fletch have said, there is a lot to learn and many methods of custom configuring the NARS/BARS. I took me about three months, however, I documented and created a 2 inch binder of my site's Electronic Switch Network and how to change settings like these.

Good luck and happy studying.

Jes

imported_BinaryDragon

Is it bad that when I print this NCOS to FRL list all my NCOS are FRL0?