Setting up the Dial Plan on the NEC 2000 IPS
To define a dial plan you use Command 200 to define each number range as shown below:
ProAction Networks is the United Kingdom's leading support vendor for the NEC 2000 IPS business telephone system, the NEC IPS DM branch telephone system, the NEC SV8100 business telephone system and the accompanying Zeacom Communications Centre application server. Based in Milton Keynes, Buckinghamshire and supporting, maintaining and serving 2000 IPS and SV8100 owners, administrators and users worldwide, ProAction Networks provide both ad-hoc support services and 24 hour, 365-day contractual support, warranty and maintenance. ProAction Networks, as a Cisco Certified Organisation with over a decade hands-on experience with the NEC 2000 IPS and SV8100 can also perform complete rebuild, restore and clean installation services for the NEC 2000 IPS, DM, SV8100 and Zeacom Server.
We are a fully accredited Cisco and Microsoft Partner - fully able to help with your Network, Server, Computer, Phone System and Web Presence. We partner with various other business to combine the complete range of business technology services. This includes datacentres for everything cloud-based, service providers for physical connectivity and hardware distributors to bring down costs.
ProAction Networks offer 2 types of NEC & Zeacom support contract.
Our 'traditional' contract is similar to that of most telephone companies. It is based on 12% of the original cost of the hardware. This contract is sold in 6-month segments with no minimum term to limit your exposure and assure you, the customer that we are serious about keeping you happy. If we do not perform, you do not have to remain a customer!
Within that 12% annual cost, you get a full warranty on all audited equipment. Should you experience a malfunction or some equipment fails, we will deliver, replace and reprogram - free of charge. We carry all equipment in stock and available immediately.
Alongside the warranty, we provide 24 hour, 365 day-a-year support. Your account manager is your engineer and you will have constant direct access to him or her via email, mobile and support desk.
Alternatively, we offer a Per Seat maintenance contract.
Many NEC 2000 IPS and Zeacom owners invested heavily in their systems many years ago, and in many cases their staff and premises have changed along the way. We do not insist you pay to maintain the 50% of a system which is not in use! You may have a system that is architectually over-powered but is still worth utilising and maintaining. For this reason, we offer this per-seat maintenance contact.
You get to choose which contract is right for you - which may simply be whichever is cheapest
Most NEC NEAX 2000 IPS or IVS telephone systems will also have an accompanying application server in some shape or form to add lots of bells and whistles to the entire telephony system. At it's most basic, it may provide a voicemail system or operator console. However, an accompanying application server can scale upwards to include a huge array of services.
The NEC 2000 IPS is regarded by many as a fairly old-school enterprise phone system - and as a result, rather than try to utilise any of the NEC functions for Voicemail, Uniform Call Distribution (UCD) or Computer Integration (CTI), most customers in the UK, and indeed throughout New Zealand, Australia and the USA aquired a Zeacom Communications Center as well.
In the UK there were only really three options if you wanted voicemail for the NEC IPS - that was to either by an AD8 voicemail card, which was essentially a linux-based PC on a card, with a 2.5" hard drive - very unreliable (spinning hard drive without any form of redundancy) and not very management-friendly. Secondly there was the option of NEC or Philips' own voicemail and CTI applications, and lastly you could use the Zeacom.
Zeacom products were originally called Corus (for voicemail) and Q-Master (for call/contact centre) - and somewhere in the middle was CTI and it's associated applications. More recently, Zeacom rebranded their extensive product portfolio as the Zeacom Communication Center (sic) - which encompasses everything they provide in one neat portfolio. The most popular parts that make up any Zeacom installation include Console, Desktop, Voicemail, Reports and Wallboard.
Zeacom applications reside on a seperate Windows-based server and controlled the PBX using an NEC feature called OAI (Open Application Interface) - essentially a closed developer protocol to control the phone system. This OAI protocol could either be sent via RS232 or more commonly via a TCP/IP network. There would also sometimes be analogue connections between the Zeacom server and the PBX to send and recieve voice recordings, although more recently this is done via VoIP.
A Call Center is possibly the 2nd most likely component of an appication server - many providing full multimedia, networked call center solution with comprehensive management, reporting, live statistics, IVR, Auto Attendants, Callback, Web and Chat modules - the list is almost endless.
The OAI interface is probably Zeacom's greatest weapon, as it allows full control and oversight of the phone system - the server can report everything that is going on back to the end user, control devices and fully manage the NEC 2000 IPS live. This enables certain software programs, like Desktop for the standard user and Console for the operator to show a huge array of live information - such as who is at their desks, who is out of the office, who is on the phone, what calls are in the queue, how many people are on hold and so on.
If you have any specific problems with your Zeacom solve which you simply cannot resolve, then please get in touch.
Most NEC NEAX 2000 IPS or IVS telephone systems will also have an accompanying application server in some shape or form to add lots of bells and whistles to the entire telephony system. At it's most basic, it may provide a voicemail system or operator console. However, an accompanying application server can scale upwards to include a huge array of services.
The NEC 2000 IPS is regarded by many as a fairly old-school enterprise phone system - and as a result, rather than try to utilise any of the NEC functions for Voicemail, Uniform Call Distribution (UCD) or Computer Integration (CTI), most customers in the UK, and indeed throughout New Zealand, Australia and the USA aquired a Zeacom Communications Center as well.
In the UK there were only really three options if you wanted voicemail for the NEC IPS - that was to either by an AD8 voicemail card, which was essentially a linux-based PC on a card, with a 2.5" hard drive - very unreliable (spinning hard drive without any form of redundancy) and not very management-friendly. Secondly there was the option of NEC or Philips' own voicemail and CTI applications, and lastly you could use the Zeacom.
Zeacom products were originally called Corus (for voicemail) and Q-Master (for call/contact centre) - and somewhere in the middle was CTI and it's associated applications. More recently, Zeacom rebranded their extensive product portfolio as the Zeacom Communication Center (sic) - which encompasses everything they provide in one neat portfolio. The most popular parts that make up any Zeacom installation include Console, Desktop, Voicemail, Reports and Wallboard.
Zeacom applications reside on a seperate Windows-based server and controlled the PBX using an NEC feature called OAI (Open Application Interface) - essentially a closed developer protocol to control the phone system. This OAI protocol could either be sent via RS232 or more commonly via a TCP/IP network. There would also sometimes be analogue connections between the Zeacom server and the PBX to send and recieve voice recordings, although more recently this is done via VoIP.
A Call Center is possibly the 2nd most likely component of an appication server - many providing full multimedia, networked call center solution with comprehensive management, reporting, live statistics, IVR, Auto Attendants, Callback, Web and Chat modules - the list is almost endless.
The OAI interface is probably Zeacom's greatest weapon, as it allows full control and oversight of the phone system - the server can report everything that is going on back to the end user, control devices and fully manage the NEC 2000 IPS live. This enables certain software programs, like Desktop for the standard user and Console for the operator to show a huge array of live information - such as who is at their desks, who is out of the office, who is on the phone, what calls are in the queue, how many people are on hold and so on.
If you have any specific problems with your Zeacom solve which you simply cannot resolve, then please get in touch.
The Rich Presence functionality in Zeacom Communications Center (ZCC) provides employees with a bird's eye view of the whereabouts of their colleagues providing real-time information on staff availability, regardless of their location. Rich Presence is one of five key functionality sets that are part of the ZCC Unified Communications solution. ZCC will enable your organization to become more efficient and productive, by improving communications with customers, colleagues, suppliers and business partners.
Make First-Call Resolution a Reality It's frustrating for your customers if their calls can't be resolved straight away, and they need to leave a message or are informed that somebody will be in touch shortly. But delayed responses affect your organization even more in terms of double-handling, additional costs and possibly even lost business. So wouldn't it be handy if when a call comes in and it requires a transfer it is always re-directed to staff who are actually available, at their desk or on their mobile? Your ability to quickly link a customer to the company 'expert', to close a sales call or resolve an inquiry, can make all the difference between a satisfied customer and a disgruntled one. ZCC Rich Presence makes first-call resolution a reality, not only for external interactions but also for internal calls. It will enable your employees to make direct contact when they call one of their colleagues, every time. Introduce Rich Presence and you'll eliminate voice mail jail, reduce frustrations, and save time across the entire enterprise whenever a phone call successfully connects to a real person.
With Rich Presence, you have instant access to information about your colleagues' availability, allowing you to make contact the first time you call. Need to find someone urgently? Presence can tell you where they are, what meeting they are in and when they are due back. If somebody walks away from their desk, their icon will show that they are no longer there. In that case you can be notified immediately upon their return, making voice mail jail a thing of the past.
You'll also find that Presence is an integral part of other key Unified Communications functionality. For example, your console operator or receptionist needs to easily and quickly transfer calls, and will appreciate the fact that their intuitive application is combined with the visibility of everybody's whereabouts.
If knowledge workers wish to organize an ad hoc conference call with colleagues in other parts of the world, they will only click on icons of co-workers who are actually at their desk.
Executives will only need a single phone number to always be contactable. ZCC will transfer calls to the office phone automatically to their mobile, as soon as they're away from their desk. And when they're traveling, they can use Presence to see on the mobile which of their 'buddies' is active at their desk, before they call the office.
Check whether colleagues are at their desk, and see when they are due back.
To define a dial plan you use Command 200 to define each number range as shown below:
Each system cabinet with the NEC 2000 IPS is called a “PIM” – Programming Interface Module. You can generally have up to 8 PIMs on the NEC 2000 IPS (depending on the age of the system and how much IP telephony you have). Within a physical PIM, you have slots to mount system cards which are labelled LT/AP00 to LT/AP11. These slots are universal and can house LT (Line / Trunk) or AP (Application Processor) cards.
Slot 12 is used for either the Main Processor (MP) if this is PIM 0, or Firmware Processors (FP) if this is PIM 2, 4 or 6. PIM numbering begins at 0 (zero) for the first PIM and goes up to 63.
You’ll notice at the bottom of this diagram you can see the LTC 0-2 cables, which carry 3 x 8 pairs of wires attached to each of the card slots between LT0 and LT11. Please note also that LTC3, despite carrying 24 pairs of wires for 3 cards, the backpane of the NEC PIM will only allow 4 port cards within these slots to be wired out to patch panel or wiring frame.
One Firmware processor is required for every 2 PIMS in your system – with the exception of the first two PIMs. This is because the main processor (MP) for the 2000 IPS has an firmware processor ‘built in’.
The maximum number of physical PIMs would have 3 FPs and 1 MP.
A bus cable must be used when connecting more than one PIM – which connects all the PIMs together, but in a very specific nature (covered in another post!).
You must ensure that power control cable D is used on the PIMs 1-7 and that Power Control cable E is used on PIM0. Power control cable E has a single wire cut, to make it different, which you can do manually if you do not have the right cable.

As much as it pains me to sideline the old forum that had plenty of information in it, we have introduced a far cleaner and improved Forum courtesy of vBulletin. Â It wasn’t possible to migrate the old phorum database, so you’ll all have to start chatting to get the information going!
It only takes a few moments to register, and when you do you get full access to the forums – which are actively monitored by NEC telephone system engineers.
You can view the forums by clicking on the FORUM tab along the top menu, or clicking here.

Okay, I’ll admit it. I haven’t spent as much time here as I should have. For this, please accept my humble apologies. I’d originally developed this site over a year ago when I was really just a beginner in HTML and PHP. I am now slightly less a beginner and understand far better how to make this site work now.
So, I’ve cleaned it up a bit, opened up commenting (which I had to shut due to a massive amount of SPAM!) and in the next few days I am going to integrate a new Forum, which will be much more powerful. Please, if you appreciatate this site, then please add a comment somewhere and let me know. You do have to register (takes 2 minutes), but I really appreciate feedback, which meaks me feel it’s worthwhile spending the time.
Thanks
Alex
You can download a link below to a PDF document which goes through the process of tracing the LCR programming for the NEC 2000IPS. When we refer to “LCR” in the NEC PBX programming, we’re not just talking about ways to make cheaper calls. It does indeed cause route preference choices depending on the location, extension, tenancy and more – but also is responsible for barring, time scheduling, volume control and so much more.
This flowchart takes it down to the very basics and should be noted that it’s based on traditional UK programming of the NEC IPS. Therefore it may bear no resemblance to your standard programming, but if you study closely, you’ll soon figure out what does what and where.
http://www.necphonesystem.co.uk/files/www.necpbx.co.uk_LCR_flowchart.pdf
Hi Everyone. I know, I know – updates have been thin on the ground and for which please may you accept my humble apologies!!! I just added the SMDR manual for the NEC 2000IPS and am going to add a few more useful articles now. Be Well!
Some users have enquired about the SMDR manual. Attached below is the SMDR manual for R14 release NEC IPS CPUs. Please bear in mind that before R10, there was only one format of SMDR output (called Former Format) and then from R10 onwards, you have the option to select an Extended Format.
The main difference is a few extra fields of data – most imporantly an abandonment field and abandonment time.
Happy Christmas everyone and a merry new year. I’ve added a load more articles in the previous weeks with many more to come. Don’t forget, if you get stuck over christmas, you can call our 24 hour emergency number at 09050 990 010 to speak to an NEC and Zeacom Engineer, if you’re stuck up the river without a paddle!
Quick special thanks to all the help we’ve received from our USA and Austrlian counterparts – the engineers out there in the thick of things! Thanks for all your positive comments and glad we’re all able to help each other!
Have a good one!, one and all!
We use several commands to control what CLOP is sent out by any given extension, be it analogue, Digital, IP or Virtual. There are 4 widely used parts to this command.
The use of this command relies on the network âallowingâ the PBX to predetermine what CLI is sent out on each call. Generally this is a feature you have to have enabled with the circuit provider and they will only let you send out numbers proven to belong to your company.
The attachment of a CLI to an extension is formed of two parts â the first part of the string and the second part of the string. The first part is held within a table of up to 15 different variations (CM>1213). The second part is attached directly to the extension using CM>1212.
CM>1325 â Permits or Denies the sending of CLI to the network
CM>5005 â Builds a table of up to 15 different National area codes
CM> 1212 â Attaches the last 4 digits of the CLI to an extension
CM>1213 â Attaches the rest of the digits as determined in CM>5005 to the extension.
Below we break down examples of each command:
Example:
CM> 1325: 1001 = 1
This means that extension 1001 is permitted to send out a CLI to the network as itâs own âCLOPâ. If the Second Data had been a Zero then the extension will be denied sending a CLOP (circuit vendor permitting).
CM> 5005: 01 = 0190833
This means that we have within table number 01, the first part of a number which is 0190833. You can have different types of number in table number 00-14. The last four digits are assigned directly to the extensions in the final command;
The following two commands are made up of the Command, followed by the Extension, followed by the type of number to be sent:
CM> 1212: 1001 = 1001
This means that extension 1001 is going to attach the digits â1001â to the CLI string it sends out to the network when making an outside call.
CM> 1213: 1001 = 01
This means that extension 1001 will use whatever number has been configured within table 01, using CM>5005 as the first part of the string.
It is a good idea to put a PIN number on IP phones for several reasons:
However sometimes it is necessary to either reset or setup a PIN number.
Example:
CM> 2B00 : 1001 = 1234
This means that extension 1001 is setup with the PIN number of 1234.
Note: This guide assumes you know how to input commands into MOC.
MOC mode is a command line interface to the phone system. It is made up of a few simple keyboard commands:
Command 14 allows you to listup anything that resides on possible programmed LENs (or wirable ports on the phone system). The programming is defined as follows:
Command > 14
First Data: XXYYY
XX is the module number. Main Site PIMS 0 & 1 = Module 00, PIMS 2 & 3 = Module 01, PIMS 4 & 5 = Module 02 and PIMS 6 & 7 = Module 03
Remote Sites are generally known as Module 33 for Remote Site 01 and Module 44 for Remote Site 02.
Second Data: Z-ZZZZZZ
This data will be what is programmed on the port. A number such as 100 will generally be an analogue station. A number prefixed with an F is a digital station. A number prefixed with a D is a trunk (such as ISDN2 or Analogue Trunk), and a number prefixed with a DD is an IP-TDM conversion channel.
Set Rotary Switch 3 to position 2.
Press reset button on CPU (Off Line Mode no call processing)
Connect your computetr’s serial port to you PBX processor’s RS0 port
Using MATWorX go into MOC mode.
Connect to PBX
Execute Command 00 FD 1 SD CCC .
Red light on CPU flashes fast.
OK appears on the screen.
NOTE: If there are, or likely to be IP stations you need to customise the Switch for this. Virtual PIMs are required for IP stations. (1 Virtual PIM allows 64 IP stations )There is a trade off between IP and TDM stations as seen in the manual. The command 00 can be used to achieve the correct number. see examples shown below.
Execute Command 00 FD 11 SD CCC ( To create 7 virtual and one physical PIMs)
Or Command 00 FD 12 SD CCC ( To create 6 virtual and two physical PIMs )
Or Command 00 FD 13 SD CCC ( To create 5 virtual and 3 physical PIMs )
Or Command 00 FD 14 SD CCC(To create 4 virtual and 4 Physical PIMS.
Set Rotary Switch 3 to position 0.
Press reset button on CPU.
What is an OFD?
It’s a file, which MATWorX can generate, which is essentially a listup of all the command data in your 2000 IPS. You can generate an OFD by going into MATWorX and selecting the Save/Load/Verify from the Menus.
When Can I Generate An OFD?
You’re supposed to do it offiline (rotary switch in position 2, system reset) and via a Serial connection. If you switch it to 19200 baud, it should take less than 20 minutes, depending on how much data is on the system. MATWorX will let you generate an OFD whilst in ONLINE mode, but it’s not recommended because certain parts of the programming may be in use, or be changed whilst the generation is occuring, thus providing you with corrupt data. You can also generate an OFD over serial or modem cable – however for some reason it suggests it will often take hours, and I wouldn’t trust the outcome!
Why Would I Generate An OFD?
You may simply want a routine backup of all your PBX programming. You may be making lots of changes, which will require a save to ROM and therefore not be un-do-able, and want a get-out-of-jail-free card. If you’re performing an MP firmware upgrade, then you WANT to take an OFD incase it all goes pear shaped.
Things To Know
Once you have taken your OFD (which will usually be a few hundred kilobytes), you can then use it to restore to another, or the same processor. It’s also generally accepted that you clear down all the data on the system (also rotary 2, reset, serial connection, CM00, 1, CCC).
You apply the OFD in the same place you generated it, except under the LOAD section. You can also verify an OFD to see if it’s all good using…….verify!! Again, only load an OFD when in offline mode.
Once loaded here are some pointers:
Do an EC6/backup to ROM BEFORE you reset the PBX. I think the system automatically backs the new data up to ROM when the OFD restore finishes, but do it again to be sure.
Then, still in offline mode, do an Office Data Conversion using command CM00>90:0. If you have upgraded the firmware on the CPU, this will ensure that any commands which have been replaced or superceded will be migrated to the new ones.
ROM again
Check and Change the time(it’ll reset).
Test both an IP and TDM phone – the Dial tone/Hold/Ring etc maybe different, if so, you will need to go over and check your tone commands, and possibly, upload specific tone firmware onto your MP. I know in the UK we sometimes mistakenly (those silly boys!) were given Dutch firmware with different tones, which we had to manually over-write. DTG files must be loaded using an MP download with rotary switch on 8.
You can also run in MACH editor a dial tone conversion script (if you have one) – changes won’t occur til you ROM and reset).
IP phones tone may need to be changed manually. On modern firmware IP phones, you have a hidden menu where you have to set the Region to the local country tone. There also were some commands, I think to set it system wide – but I don’t know for sure.
To change to UK dial tone do doing the following (on an IP phone):
Hold, Transfer, *, #
Hold, #, 0
look for menu 3 Area ID
when in Area ID, enter 8# until Uk is displayed.
Save change and wait until phone boots up
Check dial of IP phone.
If everything checks out the create another OFD as a backup. Well done!
How To Setup Call Pickup Groups In Matworx!
Intro
Okay, like a linux bore at a computer market in the sports hall of a school outside Dartford, I’m going to lay it down here that if you really could be bothered, you won’t go wrong adding, deleting and modifying a Call Pickup Group in MOC mode. The reason I say this is that the MATworX GUIs sometimes can’t work out what’s going on and will give you mis-information. A perfect example is when you have an extension in a pickup group – then some nonse deletes the extension and recreates it again.
If that extension has not been removed from the pickup group first then it is technically referred to as FUBAR (it won’t work).
That’s because like most ‘groups’ in the NEC IPS – they’re built in what can only be described as a chain – a chain which, when a link is removed falls apart and is neither use to man nor beast.
So, what I am getting at in a convoluted way is that if one day you sit down, and you transform from a smiling, whistling, happy-go-lucky human being to a chainsaw-wielding maniac – all because MATworX makes no sense whatsoever, then you’ll need to go into MOC to fix it. That, alas is another day, another story. Shall we begin?
To setup call pickup groups, you need to go into MaTWorX and click on Station, then click on Call Pickup Group:
The Call Pickup window will open…
Yes, it’s empty. You need to click on Listup in Create Group. MATWorX will now take 3 of your Earth days to download the current data that’s already on the PBX.
To Create Pickup Groups:
The list underneath the Available column are the extension numbers that have not been assigned in a pickup group. To assign them in a group you need to highlight one of the extension numbers and then click on the button with the arrow facing right, this will move the extension number to the Members column. Carry on highlighting the other extension numbers and moving them to the right column until all the required extensions are on the right hand column.
Click on Build Group to create the pickup group. MATWorx will then go away and DESTROY any existing group you modified and REBUILD a new one!
Bear in mind that each extension number can only belong to 1 pickup group only.
To setup the pickup button for each extension you will need to click on Station and then click on Station Assignment
If you click on Key Data Assignment
If you look at the example on Key 8, the pickup code is F0020, this code is used to pickup all the other extension numbers that is in the same pickup group as the extension number you are on now. Bonus Ball: F0021 is pickup station (not a group – just pickup the phone, press this button and the extension which is ringing and t’will be answered!)
To check and/or modify the pickup groups, go to the Modify Group section:
For Example, The pickup group for x7126 has x7149, x7120 and x7124
x7126 is capable of picking up x7149, x7120 and x7124 by pressing the 8th button (F0020).
If you need to modify the pickup group then use the button with the right hand to include more extensions and the button with the left arrow to delete out of the group.
Click on Update Group to update the pickup group.
We’ve introduced a mini-forum section, to simplify the concept of asking and answering questions. Anyone can post – you can reply to posts without registering, and create, edit etc posts if you just register.
Registration takes seconds. Any questions posted should have answers within a few hours.
Hi All! It’s a little rough-and-ready, but we’ve implimented a new Forum Section to this site. You can now really easily ask and answer questions about three main topics – NEC 2000 IPS & SV 8300, NEC 2400 IPX, and the Zeacom Server. Go on, sign up and show your support!
Message Waiting Notification Lamp
The following command needs to be set on the extension. CM 1303 > extension number (e.g. 2000) : 0 (this allows message waiting notification to be set).
To test the message waiting on an extension do the following, from a phone dial #*8 and then an extension number e.g. 2000, you should see the message waiting light come on that phone, in this case extension 2000.
If you have a service feature code setup to determine switch on or off the lamp, it will likely be #*9. To turn it off dial #*9 and the extension number again.
Setting Call Forwards on Dterms and Analogue stations.
Call Forwards can be set on both Physical and Virtual extensions. Before setting Call Forwarding please use CM 15 to check if call forwarding is allowed for the class that the station belongs to. By default, call forwarding externally is barred. Follow the link below for further details:
Call forwarding Class of Service
To enable Call forwarding to external numbers you need to check if Trunk to Trunk transfer is enabled. Follow the link below for further details:
Trunk to Trunk Transfer
Using the Handset to Set Call forwards:
To Set:
1. Press the Speaker button
2. Press the Call Forward button (Call Forward All /Call Forward Busy /Call Forward No Answer)
3. Dial the number of the required destination
4. Press the Speaker Button
To Cancel:
1. Press the Speaker button
2. Press the Call Forward button (Call Forward All /Call Forward Busy /Call Forward No Answer)
3. Press the Star key
4. Press the Speaker Button
Using Access Codes:
To Set:
1. Lift the handset
2. Dial the required access code to set the Call Forward (i.e. *01 for Call Forward All, *02 for Call Forward No Answer and *03 for Call Forward Busy )
3. Dial the number of the required destination
4. Replace the handset
To Cancel
1. Lift the handset
2. Dial the required access code to cancel the Call Forward (i.e. #01 for Call Forward All, #02 for Call Forward No Answer and #03 for Call Forward Busy )
3. Replace the handset
Using the Command Interface MOC:
To Set:
CM E600 (to set Call Forward All) > Extension Number : Destination Number (if to an external number, the access code must be used e.g. 9,123)
CM E601 (to set Call Forward Busy) > Extension Number : Destination Number
CM E602 (to set Call Forward No Answer) > Extension Number : Destination Number
To Cancel:
CM E600 (to set Call Forward All) > Extension Number : CCC
CM E601 (to set Call Forward Busy) > Extension Number : CCC
CM E602 (to set Call Forward No Answer) > Extension Number : CCC
Hi – quick word from the author of this site. I’m intending on using this site to build up a resource, or at least a link to the resources available on the internet for the NEC 2000 IPS. I’ve always found the NEC IPS PBX is one of the hardest things to support because the information hasn’t moved with the times.
Most technologies nowadays, you can google search and find sites dedicated to those subjects and usually many forum subjects where people have discussed the problem you have and (hopefully) if you read on long enough you can see how they fixed it. This simply isn’t the case with the NEC IPS.
So i’m going to link to the few places on the internet that are useful resource, along with adding lots of my own information and personal responses to questions, and hopefully this site will become a resource in itself!