atcomsystems.ca/forum Forums TDM Business Telephone Systems NEC Telephones & Systems LCR - Digit Addition/Deletion

Hello All,
We recently changed providers, and our new provider requires 10 digit dialing for our local "expanded calling area".

I'm taking this opportunity to reprogram our LCR table, and seem to have a good understanding of the basics.

What I want to know, is how should I proceed with Digit addition/deletion?

After reading through the manual, it seems that I can set the order to go through the LCR Routes...does this mean if the PBX doesn't encounter a match in the first LCR, it will move on to the next?

If this is the case, can I use the max digits to match the data?

I.E. 7 digits max, with an "area code" of 201 which is really an exchange, then I can route it and perform the digit addition and route it over our Local PRI

If theres 10 digits with a true area code of 201, then it doesn't match, so it goes on to the next route, where it will match as a true area code and route it over our LD T-1?

Which system? 2400...2000....IPKII....IPK...192...
DSX....Aspire...EPro....????? If you expect some help, you gotta provide a little more info.

Whoops...completely forgot about that.

Its an NEC 2000 IPS.

After reviewing our existing LCR, I think I have it figured out now...if anyone wants to provide any feedback I have an excel file that I will be using sometime this week to complete the programming:
https://lovemyitguy.com/Files/Least Cost Routing - 091707.xls

Overall, its 375 entries, and accounts for current/planned toll free #'s, current/planned feature codes (211, 311, 411...), regular long distance.

The LCR entries also account for Area Codes that are dialed with a leading 1, and will strip the leading 1. Additionally it accounts for all known NXX combinations that can be dialed as 7 digits, and will add the area code (772) to the #

Hopefully it all works out as planned =D

Okay, two ways to do it...

1.):
in 8A4005>201xxx>yyyy program every possible dialing combination (where xxx is an office code or portion of an office code, and yyyy is a route plan)

in 8Ayyyy>1> zzzww where yyyy is the route plan from 8A4005, 1=1st choice, zzz is a handle for future reference, and ww is a trunk group.

8Ayyyy>2>zyzwx (2nd choice, reference zyz, trunk gp wx)

Omit "blocked" entries from the table, or assign an invalid route (one without any entries in 8Ayyyy)

2.):
Leave 8A4005 with entries beginning with the office code. Note the route plan.

8A4005>5551212>yyyy (yyyy=route plan)

8Ayyyy>1>xxxzz (xxx=reference #, zz = trunk group)

8A5xxx>100>9xxx (where xxx is reference # from 8Ayyyy, above)

8A9xxx>0>201 (where xxx is from 8A5xxx, and 201 is the digit string to be inserted - max 32 digits)

As with the first method, you can have multiple trunk group choices (8Ayyyy>2>xxxcc, 8Ayyyy>3>xxxdd) but as long as the reference number (xxx) remains the same, 201 will be inserted at the beginning of the string.

Now, obviously, you need to plan this out and consider 1+areacode+7digit (clue: don't put 201 in front -- use a different route plan and reference number), 1 800+, 1 900+, 976+, 011+, 911, 9+911, etc. when planning your routes. Test each one, even the 911s. Especially the 911s.

You'd be a lot better off to hire a professional, I'll tell you that right now. He'll charge even more to straighten it out if you tangle it up.

I also strongly recommend a database backup before you start.

Well the LCR was a breeze...I programmed and tested my new LCR setup on Thursday morning, and put it into production that afternoon.

The only issue I had was with the digit addition, Matworx didn't make a programming change that was required, so I had to use the MOC to complete the setup (Command 100 on 8A5XXX as mentioned in telephoneguys post).

Granted, I put some thought into my setup as can be seen in my Excel layout.

Setting up the restrictions was also a breeze, and are definetly welcome as we had users making international calls, 411, personal long distance calls and etc with no way for us to block them until Thursday =D

Thanks for everyones input!

Always do a backup before any major changes...

But no need to hire a professional...then I will never learn this system!

Besides, I did all of my programming on non-conflicting items. I.E. We were using LCR Groups 5 & 7 so I used Group 0. We were using Route Patterns 000 & one other so I used 010-019

I setup a LCR Access code (instead of 9, I used 80) to test, and when I was comfortable with the changes I put them into production. Now if something major goes wrong I can just revert to the previous setup while I review my config.