2000IPS number plan addition

[rfcomm2k]

I have a 2000IPS networked with a 2400IPX via CCIS. On the 2000IPS side there are extension numbers in the 29xx, 40xx, 41xx, 57xx ranges. Believe it or not, on the 2400 side there are ALSO extensions in those ranges.

I tried to add a new IP phone on x4053 on the 2000IPS. I used matworks32 to add the phone on that ext. Then plugged the phone I, accessed the phone menu and set up the DNS, Gateway, etc and saved. Phone rebooted and prompted me with LOGIN prompt. I entered 4053 and the phone came up OK, I thought. I could dial outside, or call internally, or call the 2400 side via CCIS. BUT, I cannot call 4053 from inside or outside.

When I checked the numbering plan 4 digit station assignment, I found 2945, 4077, 4101 thru 4112, 5725, 5733 thru 5749, and 5784 (all existing extensions). I clicked the blue + button at the bottom of window and tried to add 4053. When I tried to update, got an error message "Access code exceeds digits already in use".

How do I get 4053 added to the 2000IPS number plan?

 

[belevedere]

The error means that the number plan for 4053 was not expanded to 4 digits. Look for 4, 40, 403. Typically in a CCIS network we use LCR table 8A4007 to set up local or distant number plans.
EX: 4053 lives in the IPS side, 4054 lives on the 2400 side
200>4>A129 = LCR table for networking
8A4007>4053>8004 = 4 digit extension on IPS side
8A4007>4054>0043 = route table to send digits dialed to 2400 side.
You possible have 8A4007>4, 0r 40, or 403 set to a routing table. It needs to be broken out to accommodate a split number plan.
I prefer to use the MOC mode and hex code for programming the IPS. The GUI tends to be more cumbersome.

 

[OzzieGeorge]

There is a similar requirement on the 2400 side but it has been over 10 years since I did this, Belvedere should be able to help but if you don't program both ends, you will have problems in the future!

 

[belevedere]

On the 2400 ANPD is either LCR, or STN for 4 digits. List out LNPD, LSPA, LFRS for all routes. Look for a station on the 2400 side and one on the 2000 side and match them. Again, it has to be broken out to the number of digits needed.

 

[rfcomm2k]

Belvedere, thank you for that info.

I am trying to do this remotely by connecting via VPN to the customer PC and using his copy of Matworks32 to program it. That actually works very well, especially considering that the customer is about 90 minutes away on a GOOD day.

When I looked at the LCR in numbering plan, I was in Group 0 at the top of the window, and in LCR Group 0 there was only one entry, for the access code 0. In LCR groups 1 and 2 there was nothing. In LCR group 3 was where I found the majority of the data. In that table, I noted that for every valid extension access code that currently existed in the 2000, the corresponding Feature code was 804. I found extension 2496, 4077, 4101, 4102, 4103, etc. Each of these was an individual entry in LCR, with 804 as the Feature code.

I wanted to Add 4053 to this, so I tried clicking on the + button in Matworks. It would not allow me to add. However, if I clicked on an existing extension, the - button lit up, so I could conceivably delete an extension if I wished.

Is there a limitation to how many entries can be placed in an LCR table? If not, how do I insert a new extension into LCR with feature code 804? (Using Matworks).

 

[belevedere]

There is no limitation. I use the MOC mode for programming. MOC mode is programming through hex code. For things like LCR it is actually easier than using the GUI.
Click on "tool" at the top. Click on MOC mode.
When the screen opens, press F9 to start (command)
type 8A4007 - space bar
type 4053 - space bar, if you get an error, press F3 clear entry) then try 405 - space bar. Keep trying less digits until you see either 8004 (804 for older software) or 00XX (4 digit route table number)
What you need to get to is the option that looks like this; 8A4007>4053>8004. If you see 8A4007>405>00XX, then you need to break it out to 4 digits. EX:8A4007>405>00XX:CCC F2 to delete it. (write down the table number first).
8A4007>4050>00XX ~ 4052>00XX, 4053>8004, 4054 ~ 4059>00XX. This sets up 4053 as an extension on the 2000 and the remaining digits as extensions on the 2400.
F2 writes data
CCC + F2 erases data
If you see 8A4007>40>error, then it is broken out to more digits. Try 8A4007>400 space bar (DE key is also F8).

 

[rfcomm2k]

Great answer Belvedere. Tried it today and got the following error message:

Command=8A4007
8A4007>4053
8A4007>4053:WRONG
8A4007>


Attached is a PDF of the LCR part of the numbering plan, as extracted from Matworks.

 

[rfcomm2k]

My bad Belvedere. I think it was supposed to be 804, not 8004 on that system. Am going to try again & post the result here

 

[belevedere]

Whoever programmed this LCR and number plan did it wrong. In CMD 200 (number plan) digits used for extension numbering should not be longer than 2 digits in length.
EX:200>40>804, or A129, not 200>405>804 Digits longer than 2 in command 200 create problems especially with call forwarding. A proper program should be; 200>40>A129, 8A4007>400>00XX, 8A403>8004. In your example, 200>40>A129, 8A4007>4050>00XX, 4051, 4052, 4054, 4055, 4056, 4057, 4058, 4059>00XX, 8A4007>4053>8004
NOTE: in CMD 200 804 = 4 digit extension numbers, in CMD 8A4007, 8004 = extension numbers.

 

[rfcomm2k]

I think I am beginning to understand the problem finally. In LCR, the original programmer pointed ALL 405x numbers to A129, which I presume is sending the caller via CCIS over to the 2400 PBX. Also, 407x numbers are broken down individually so that 4077 stays on the 2000 as a local extension and all other 407x numbers point to the 2400.

If my assumptions above are correct, then I should be able to go to LCR, delete 405=A129, and re-enter 4050, 4051, 4052, 4054, 4056, 4057, 4058, 4059 all as A129 and 4053 as 804.

Am I correct here?

Specifically, in MOC mode:

8A4007>405>A129:CCC F2 to delete it
8A4007>4050>A129 F2 to write it
8A4007>4051>A129 F2 to write it
8A4007>4052>A129 F2 to write it
8A4007>4053>804 F2 to write it
8A4007>4054>A129 F2 to write it
8A4007>4055>A129 F2 to write it
8A4007>4056>A129 F2 to write it
8A4007>4057>A129 F2 to write it
8A4007>4058>A129 F2 to write it
8A4007>4059>A129 F2 to write it

 

[belevedere]

You got it. However, in 8A4007 it's 8004 not 804.

 

[rfcomm2k]

But when I look in the printout of LCR it shows 804, not 8004.

 

[rfcomm2k]

OK, now I am beginning to get peeved. Why NEC had to make LCR on the 2000 so difficult I will never understand. I can do it in a snap on the 2400.

When I enter 8A4007 space 405 space, I get error message "WRONG"

Please look again at the file I uploaded and tell me what I am doing wrong.

 

[belevedere]

Your list out is for number plan not for LCR, however see below;
The data stored in the memory is wrong. This message is displayed when too many digits are entered. For example, when assigning “123” for a service access code when “12” has been already used for another service access code.
Enter 8A4007 space 40 space, one less digit. If you get the error again, try one less digit 8A4007 space 4 space.
Yes, LCR is difficult. That is why trained experienced NEC engineers have a job. Sorry if that sounds cold, but it took me years to master it. You can make the same case for microsoft trained engineers, and any other software program. Don't get peeved about it. LCR and LCR with toll restriction is the single most difficult thing on this system. I have worked with techs and engineers that have years of experience with this system and still do not get LCR.
Try looking at some documents at

http://www.nectekhelp.com

under the 2000 tab.

 

[rfcomm2k]

Belvedere, you have been a great help so far. I hope you do not get discouraged with my apparent lack of understanding.

I checked as you stated 8A4007 4. It has data 0010, which according to my manual is a route pattern table.

I then tried to display the route pattern table via 8A4007 (DE) 0010 (DE). It came up blank. Empty. NADA.

While in Matworks I then clicked on numbering plan and retrieved the data. I browsed to LCR, but the first entry I saw was for 400, not the single digit 4. I see nowhere else that I can list the LCR data.

So, once again I will try to think this on paper and see if you agree.

1. 8A4007(DE)4(DE). Display reads 8A4007>4:0010
2. Type CCC and press (F2)
3. next type 8A4007(DE)4050(DE)0010 (F2)
4. 8A4007(DE)4051(DE)0010 (F2)
5. 8A4007(DE)4052(DE)0010 (F2)
6. 8A4007(DE)4053(DE)804 (F2)
7. 8A4007(DE)4054(DE)0010 (F2)
8. 8A4007(DE)4055(DE)0010 (F2)
9. 8A4007(DE)4056(DE)0010 (F2)
10. 8A4007(DE)4057(DE)0010 (F2)
11. 8A4007(DE)4058(DE)0010 (F2)
12. 8A4007(DE)4059(DE)0010 (F2)

If this is correct my next question is, what about routing 4077 or 4101-4110 to a local extension, or 4070-4076 to the 2400?

It seems it would be more appropriate to go to the route pattern table and make changes. If the single digit 4 in LCR is pointing to route pattern table 0010, then somewhere in table 0010 there needs to be some data to break out that single digit 4 to 2, 3, or 4 digits as needed, and point those 2, 3, or 4 digits to either CCIS or to a local station.

How can I get a listup of route pattern table 0010?

BTW, were you ever an NEC engineer or instructor? Because if not you sure should have been. My former Director at another company was Victor Foia, former Director of NTAC, and I am good friends with a former NEC engineer George Radu. Unfortunately, George is not familiar with the 2000.

 

[belevedere]

Yes, and yes, and I know both of them.
0010 is a route pattern table. It equates to command 8A0010>1>xxxyy, where xxx is another table used to add/delete digits or toll restrict and yy is the CCIS trunk route.
Routing 4077 or 4101-4110 as local extensions is done the same way as 4053.
8A4007>4077>8004 = local extension
8A4007>4101-4110>8004 = local extensions
8A4007>4070-4076>0010 = extensions on the 2400
In short, an entry of 0010 in 8A4007>xxxx will route to the 2400 and an entry of 8004 will be a local extension.
8A4007(DE)4(DE). Display reads 8A4007>4:0010
This process is correct.
1. 8A4007(DE)4(DE). Display reads 8A4007>4:0010
2. Type CCC and press (F2)
3. next type 8A4007(DE)4050(DE)0010 (F2)
4. 8A4007(DE)4051(DE)0010 (F2)
5. 8A4007(DE)4052(DE)0010 (F2)
6. 8A4007(DE)4053(DE)804 (F2)
7. 8A4007(DE)4054(DE)0010 (F2)
8. 8A4007(DE)4055(DE)0010 (F2)
9. 8A4007(DE)4056(DE)0010 (F2)
10. 8A4007(DE)4057(DE)0010 (F2)
11. 8A4007(DE)4058(DE)0010 (F2)
12. 8A4007(DE)4059(DE)0010 (F2)

 

[belevedere]

Moving forward, under the maintenance tab at the bottom you will find a LEN list option. Run a LEN list, then export it to an excel spreadsheet. Once it is in excel you can manipulate the columns. It will list all multilines, single lines, analog trunks and any register cards and announcement cards. Add some columns, for example I always add columns for CMD 73 (speed dial memory), 94 (one touch memory), names, locations, cable numbers, riser numbers, etc. Maintain this as you move things around so you do not have to re-learn your system 6 months from now.
Extensions listed as FXXXX are multilines, XXXX are single lines and DXXX are analog trunks. The list will also give you an idea as to where cards are located in the PIM. Memory data cloumns (73 + 94) ensure that you do not overlap memory to more than one extension. This will take a little time but down the road save time. LCR list outs are not so user friendly, but you can press F10 in the MOC mode and send the data selected to a file, or cut and past to a spreadsheet for future reference.

 

[rfcomm2k]

Thanx again belvedere. Confirmation that my programming for the 405x numbers was correct is step 1.
Am I correct though that after deleting the entry for 4 (line 1 in my list) that I will now need to provide the following routing also:
400, 401, 402, 403, 404, 406, 408, 409 all to A129
4070, 4071, 4072, 4073, 4074, 4075, 4076, 4078, 4079 all to A129
4077 to 804
4100, 4111, 4112, 4114, 4115, 4116, 4117, 4119 all to A129
4101, 4102, 4103, 4104, 4105, 4106, 4107, 4108, 4109, 4110, 4113, 4118 all to 804
412, 413, 414, 415, 416, 417, 418, 419, 420, 421 all to A129
4220, 4221, 4222 all to A129
4223, 4224, 4228 all to 804

And so on, breaking out to 4 digits as needed to accommodate scattered numbers.

Is this all correct?

 

[belevedere]

Yes.

 

[rfcomm2k]

Glad you were watching!
OK, this is going to sound really dumb but here goes. If I have to break down the 8A4007>4>0010: into the myriad of new entries needed to accommodate a single additional extension in the 405x range, how was it possible for the original programmer able to accommodate 4077 without having to do the same thing?