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:

Adding A Modem to a CP31 CPU

The CP31 processor originally did not have a modem built in. Later revisions incorporated a modem, but for those with a CP31A, the lack of modem hampers remote support or emergency access requirements.

It is possible, however, to connect an external modem to the serial port of the CPU and use this to provide remote access into the CPU. Please note that the external modem must be programmable to setup auto answer – most serial modems have this function and can be programmed using a Null modem cable, connected to a computer with hyperterminal. Compatible modems include Mr Modem modems or US Robotics serial modems.

Equipment used:

Programming requirements:

NEC IPS Feature Codes – Programming and Usage

The feature codes for system features are already set by the easy install script installed earlier. However they can be altered in command 200.

These feature codes would normally start with a * or #. In this switch A & B represents * & # respectively when programming.

Command 200

FD Feature access code

SD Feature number as defined in the command manual.

AO1 (= dialled number *01 ) Axxx where xxx = feature number

B01 (= dialled number #01 ) Axxx where xxx = feature number

Preset Feature Codes as installed by that UK Easy Install.

Access Code Access Code Description

LCR Flowchart

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

SMDR Calling Logging Manual

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.

Right Click and “Save As” to Save The Manual Here…..

IPS Power Consumption when considering UPS requirements

The following table shows how much power is required to supply each fully loaded PIM in your NEC IPS configuration. This question often comes up as IT staff need to calculate their power consumption in the event of a power failure, so they can effectively manage their power backup strategy.

The graph shows for how many PIMS the expected power consumption in Watts Per Hour and BTU per hour.

Power Consumption for an NEC 2000 IPS

Changing CLOP – Caller Line Outbound Presentation on an NEC 2000 IPS

Changing CLOP

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.

Reset PIN on IP DTERM phone

Reset PIN on IP phone

It is a good idea to put a PIN number on IP phones for several reasons:

• Security
• Prevention of someone logging on under the wrong extension and logging out someone else
• Ability to do a ‘follow me’ and log out the previous logged in location

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.

LEN Programming / Listup on the NEC 2000 IPS

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:

• / = Start
• Space = Enter
• . = Execute
• Enter = scroll forward
• F3 = scroll back

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.

VoIP Calls Too Quiet?

Changing PAD Data Levels between devices & Trunks

In circumstances where low, distorted or generally poor transmission levels with IP to TDM are encountered then the following commands are to be added to the basic Easy Install script.
Make sure a database backup (ofd) is taken before any changes are made to system programming.
CMD 3519>TRUNK ROUTE>0 (Changes PAD control to programmable PAD0)
CMD 42>50>00 (Changes PAD Data to Europe)
CMD 42>47>26 (Changes dB level to +2dB)
CMD 42>48>21 (Changes dB level to -4dB)
CMD 42>68>07 (Side Tone Level)
All IP devices must be programmed to specific Location Groups and assigned a PAD dB level in CMD 6702 (As shown in the example below).
Example:
Location Group 01 = IP-PAD (CMD 0A09>LAN interface No> 01)
Location Group 02 = IP DTERM (CMD 1239>Station number >02)
Location Group 03 = IP DECT (CMD 1239>Station number >03)
CMD 6702>0201>0002 (TTRR – TT=Default RR= +4dB)
CMD 6702>0202>0002 (TTRR – TT=Default RR= +4dB)
CMD 6702>0203>0002 (TTRR – TT=Default RR= +4dB)
CMD 6702>0302>NONE (TTRR – TT=Default RR= Default)
CMD 6702>0102>NONE (TTRR – TT=Default RR= Default)
NOTE:
These changes require system initialisation
Make sure a backup to ROM is taken before a system reset done.

First Start A CPU

Initialising the CPU

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.

SV8000 Forums – SV8100 | SV8300 | SV8500 | Zeacom

Take a look at this sister-site of ours – dedicated to the SV8300 Systems.

OFD Restore Procedure – NEAX 2000 IPS

Procedure To Safely Restore An OFD

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!

Setup Call Pickup Groups – On the NEC NEAX 2000 IPS

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.

Zeacom TCP Registry Key 4.x

By default, your Zeacom server will use UDP to communicate with the client applications, on the various workstations within your Local Area Network (LAN). UDP is the default method, because it’s quicker and lighter than TCP and ties up less network bandwidth.

UDP uses a simple transmission model without implicit hand-shaking for assured reliability, ordering, or data integrity. As a result, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. UDP assumes that error checking and correction is either not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.

However – there is another way!

Sometimes UDP simply isn’t considered good enough for the end-user – most usually intensive telephone users, such as receptionists using Console, or agents using Desktop. You may find users such as these sometimes complain a call looks like it’s still in progress when it’s not – or a call timer is still counting up, whilst the actual call has ended. This is because UDP packets are sometimes being dropped and the Server’s announcement that things have happened haven’t reached the clients!

Secondly, UDP traffic is also not passed on by your Default Gateway, or Router – therefore if you happen to be attempting to run a Zeacom application outside of the LAN, then it won’t work. If you work from home, or outside of the office, and are lucky enough to have some way into the LAN – such as a VPN, then you may wish to run Desktop or other CTI applications from your computer, whilst outside of the office.

For both these situations, you can force your client computer to establish a TCP connection to the Zeacom server – ensuring that all packets are sent and recieved (TCP includes Error Checking), and is also able to traverse gateways and routers.

To do so, open notepad and paste in the items in this document which are in yellow. Then save the file as a .reg file. Once saved, double click and it will be imported into your registry and force your Zeacom applications to create a TCP connection to their server. Please note, before saving the file you must ammend the two IP addresses within the items in yellow with the STATIC IP of your Zeacom Server.

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces\[Default]]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces\[Default]\ClientAutodiscoverySocket]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\General]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces]
“InterfaceList”=”Main”

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main]
“IsBroadcastSocket”=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main\BroadcastSocket]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main\OutboundSocket]
“PeerAddress”=”STATIC IP”

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]]
“InterfaceList”=”"

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]\BroadcastSocket]

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]\OutboundSocket]
“PeerAddress”=”STATIC IP”

Note, if you’re utilising a Zeacom 2.x, or 3.x installation, the key above will not work.

Enabling Message Waiting Lamp – NEC NEAX DTERM

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 – For The NEC NEAX 2000 IPS

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

NEC 2000 IPS Course Part 1

Here is a downloadable version of an engineering course on the NEC 2000 IPS system, circa 2003. Some of the information is out of date, but overall it’s a great introduction to the standard architecture of the system.

If it’s of use to you, please post a comment.

NEC IPS Engineers Course – Basic

Changing Trunk Selection Prefix – On NEC NEAX 2000 IPS

Sometimes it’s necessary to add or change your numbering plan, so as to enable or disable users of the NEC 2000 IPS phone system to select a specific trunk when dialling a number. The most common use for this (in the UK, at least!) is using 9 to select the first preferred trunk to the PSTN. This will most likely be a trunk, such as an analogue circuit, ISDN2 or ISDN30 circuit or a SIP trunk.

Taking a step back for a moment it’s worth mentioning that in this subject arena, you have Trunks, Trunk Groups and LCR Plans.

A trunk is usually single line (or channel) – but when you have hardware like ISDN2 or ISDN30 circuits, you have to bundle lots of trunks together in one big configuration, so when you need to use it, you select anything that is available on it! This forms a Trunk Group.

Once you have built a Trunk Group you usually access them via an LCR plan – this enables you to bundle lots of trunk groups together in one big plan and decide on restrictions and specifics of how it’s used – like what numbers should be restricted, how many numbers to wait for before sending the string the trunk itself.

So, lets hop into MOC mode and take a look. You can find a quick guide on using MOC mode here, but I will try to explain all the key presses as we go….

Go into MATworX and select MOC from the menu.

Now remember, that you start a command with a forward-slash (/), you submit each item of data using the <spacebar> and you only execute a command when using the full stop (.)

We want to look into the number plan, so press / and you’ll see “COMMAND>” return on the screen. Then type 200 (CM200 is Number Plan Zero) followed by the number the user would dial for the trunk you’re interested in. To see an overall view, you could start with zero (followed by space bar) and use the enter key to scroll through all 10 of the numeric 1-digit number plan entries to see what data is already in your system.

Your screen will look something like this.

The image shows the number plan numbers from 0 to 9 and, keeping this brief the replies are as follows:

0: 801 = 0 goes to a 1 digit internal destination

1: 804 = 1 goes to a 4 digit internal destination

2: 804 = 2 goes to a 4 digit internal destination

7: A129 = 7 goes to LCR plan A129

9: A129 = 9 goes to LCR plan A129

The bits we’re interested in for Trunk selection is anything that has a second data of 1xx (a specific trunk) or anything that has a second data of Axxx (an LCR group which could contain the specific trunks).

Now, in the UK, 99% of systems ever built in the UK would have A129 pointing to any available ISDN or Analogue PSTN trunk. Thats how it is – I can go into further detail about how to determine what is inside an LCR plan, but that’s another story – just trust me on this one!

So you can be pretty sure that if a number in your number plan goes to A129, that’s going to hit any PSTN trunks you have. If you want to MAKE a number in the number plan access that LCR plan, then simply do the following:

CM200 > 8 : A129

thats

Press Forward Slash to get “COMMAND>”, followed by 8 and the <spacebar>, then type A129 and press “.” (full stop)

If you want to DELETE a number in the number plan which accesses that LCR plan, then simply do the following:

CM200 > 7 : A129: CCC

thats

Press Forward Slash to get “COMMAND>”, followed by 8 and the <spacebar>, then type CCC and press “.” (full stop)

In this instance, you’ve made 8 select LCR group A129 and removed 7 from selecting LCR group A129.

Any questions, feel free to ask in the comments box below!

Commands, MOC and CAT Mode on the NEC NEAX 2000 IPS

How do I enter commands in MOC?

The commands and variables used to program the NEAX 2000 IPS are in Hexadecimal (Machine Code) and will not accept alpha-numeric entries. Don’t let this scare you though because most commands remain very simple and don’t require any understanding of hex to do!

The programming entries are made up of a COMMAND, followed by a FIRST DATA VARIABLE which defines a variable to be set and then a SECOND DATA VARIABLE which will enable, disable or set a features or functions.

Command + First Data Variable + Second Data Variable

Entering A Command

The Command Manual lists the above structure in the following syntax:

ST + CM + DE + First Data Variable + DE + Second Data + EXE

ST is Start Command
DE is Data Entry
EXE is Execute Command

So, for an example from the Command Manual, using this syntax the command will be entered as folows:

CM 11 > 000 : 100

“CM” is Start Command, “>” is Data Entry and “:” is Data Entry

Extending Commands and Multiple First Data Values

Commands can also be extended beyond two Hexadecimal characters which is shown in the Feature Programming and Command Manuals as a y integer. For example, command EC has a  y data of “6″

e.g. CM EC6 > 0 : 0

The First Data Variable field may use a comma , to separate multiple values when shown in the Feature Programming and Command Manuals. For example, command: 9000 (90 y = 00) has a first data with a comma seperating the First Data from the extra value: First Data: 2000 Extra Value: 00.

e.g. CM 9000 > 2000,00 : 2046

Programming Interfaces

There are 2 programming interfaces available:

1. Customer Administration Terminal (CAT) – Programming from an NEC DTERM phone

2. Maintenance Administration Terminal (MAT)

• GUI – MATWorX Menu Items
• Command Prompt – MOC (Maintenance Operation Console)
• Batch / Script Files – MACH (MOC Accelerated Command Heap) Script Editor

Entering the Commands in MOC

The commands are entered into MOC using the keyboard Function Keys (F1 to F12) as listed below:

ST is Start Command = F9 (or / )
DE is Data Entry = F8 (or space bar)
EXE is Execute Command = F2 (or . )
CE is Clear Entry = F3
S is Step Forward through Entries = F4
, is Data Seperator = F5
- is Step Backwards through Entries = F6
Backspace to erase a typed character = Backspace or F7

So to enter the commands above in MOC, the following sequece would be required:

CM 11 > 000 : 100 could be literally interpreted as “F9 11 F8 000 F8 100 F2″

CM EC6 > 0 : 0 could be literally interpreted as “F9 EC6 F8 0 F8 0 F2″

CM 9000 > 2000,00 : 2046 could literally be interpreted as “F9 9000 F8 2000,00 F8 2046 F2″

How To Lookup DDI Programming 2000 IPS

Quite a few people have asked us why there isn’t a simple GUI tool to do this. The most imporant word of the last sentence was “simple” – because there is a GUI tool for looking up DDI translations (as we call it!), but we’ll stick to MOC mode programming in this post.

For those who don’t know – DDIs (Direct Dial Inbound) is a single or range of phone numbers which are all on your ISDN circuit. An ISDN2 or ISDN30 circuit can have between 1 and unlimited telephone numbers attributed to it – and when someone dials one of these numbers, BT (or whoever your carrier is) will present the last few digits down the wire to your phone system. It’s then up to the phone system to decide what to do with it.

The NEC 2000 IPS supports between 3 and 4 digits at the end of any DDI for programming. You use a seperate command to tell the system whether it needs to look at the last 3 or 4 digits.

Usage – Part 1

The first command for DDI programming is 76xx. The xx part of the command is the DDI plan you’re looking at – which is 99% of the time DDI plan zero. So let’s assume this and use the full command 7600.

The FD (first data) for command 7600 is the last few digits of the DDI you wish to look up – lets say for example the DDI 0207 111 1234 is the number we wish to scrutinise. If you had setup the IPS to look at the last four digits, then you’d type 1234 as your FD, if you setup the IPS to look at the last three digits, then you’d type 234 as your FD.

The SD (second data) for command 7600 This will read back to you either “NONE” or a 3 digit number. This number is essentially a table reference in between 000 and 999. The table is there inbetween the last bit of programming to give you the flexibility of pointing a DDI to one of four destinations, depending on whether the NEC 2000 IPS phone system is in Day, Night, Mode 1 or Mode 2. I digress!

You can change this SD to anything you desire, between 000 and 999 – just be aware that in the next section of this tutorial, we may find the number you chose is already being used. We’ll set this to 100.

Usage – Part 2

The second command for DDI programming is one of four settings – 7601 for when the PBX is in day mode, 7602 for night, 7603 for Mode 1 and 7604 for Mode 2. You will almost always only use Day and Night (if that!).

So let’s have a look at the Day mode for 100 (set in command 7600).

The command is 7601, followed by the FD of 100, which will return a second data of “None” or a number. This final number is the terminating destination of this DDI – it could be an extension, a virtual number, a queue or most things ‘internal’. You cannot point a DDI directly to an outside number.

Problems & Solutions

Probably the biggest complaint with DDI programming in MOC is that there isn’t a command to display the information in reverse. Example, if I have an extension 100 and want to know it’s DDI, I can’t simply look this up quickly. I have to trawl through all the whole table (in 7601,2,3,4 – 1000 numbers, potentially) looking to see if there are any matches.

If you’re familar with the MACH Script Editor – then you can run a command in to lookup all DDIs which have been assigned. It takes a while but is useful in cutting away all the chaff.

There is a GUI for DDI translations in MATworX version 11 or higher.

NEC DTERM Telephones

The NEC IPS had a variety of handset ranges, each with loads of different terminals, some specific to certain territories, and some making their way across borders mysteriously! All terminals are generally considered very ‘american’ for some reason – chunky but strong and rarely had any inherant design flaws.

Nearly all handsets had a 2-way full-duplex speakerphone, a range of useful feature keys and a headset jack port. Most terminals sold in the UK were display models, with a set of programmable buttons which lit up when used for certain features. Some people referred to these buttons as ‘jelly keys’ because they looked a bit like clear Jelly!

Most people in the early days had an E Series handset, which came in white or grey, and was very sturdy – but very square!

Later, along came the I Series handset, which came in black and silver only. An extra MIC key was added, along with Directory and Phonebook buttons, which rarely were made to do anything useful.

For more information on the NEC handset ranges, click here!

NEC NEAX 2000 IPS 10u

The NEC 2000 IPS 10u has been around for nearly 15 years now. Originally available in wall-mounted or floor-standing configuration, it was later rack-mountable, which most people chose to do despite the expense of the brackets!

Although the chassis has 12+ slots inside, you could only mount line/trunk cards in slots 00 to 07 – as these really were the only cabled-out slots. You could sometimes get away with certain cards in slots 08+ but that’s another story!

The chassis was always very reliable, with a strong PSU (Power Supply Unit), had no moving parts and generated very little heat. All these points are reasons a lot of people refer to the 2000 IPS as ‘bulletproof’!

The 10u chassis for the 2000 IPS has gone through a number of name & aesthetic changes – originally called the NEAX 7400 2000 IVS (Integrated Voice System), and with grey front covers, the system was later changed into the NEAX 7400 2000 IPS (Internet Protocol Server) with blue covers. Lastly in the UK, at least, when the system was licensed to Philips (and completely ran by Philips for a short while), the system was renamed again to the SOPHO IPS and came in horrible white covers.

You can read more about the systems architecture of the 10u 2000 IPS here!

NEAX IPS DM (Remote Site)

The IPS DM (Distributed Module) was introduced in 2003 to solve two problems with the NEC architecture at the time. NEC wanted to add a chassis to their portfolio which brought down the price to invest in an NEC 2000 IPS so as to make it attractive to the SME (Small to Medium Enterprise). It didn’t really work, because there wasn’t the marketing energy behind the excercise, however it did get a few more systems out there, and allowed organisations who love the Zeacom applications a cheaper entry into the club.

Secondly, the IPS DM had a second name – the DMR (Distributed Module Remote). This was aimed as a way of distributing the NEC telephone system over completely different geographic locations and then connecting them together as a single unified PBX (each DMR became a ‘Remote Site’). This provided traditional and VoIP telephone services across tens of sites, all converged and managed from one location. It also meant you only needed one Zeacom server, to run voicemail, CTI and call centre at all locations. Finally it provided redundent failovers to the remote sites, in the form of local breakout and backup programming.

Click here to visit our main section on the system architecture of the NEC 2000 IPS and DMR