Live Support - Click To Chat

ProAction Partners

Breaking UK Telephony News

Latest Support Articles Added
MACH Script Editor Easter Egg


How do I get the video on MACH Script Editor to play?


To play the Easter Egg in MACH Script Editor:

Hold down the SHIFT + CTRL + ALT keys and then Left mouse click on the NEC Car. The video will play as shown below:





Message Waiting Notification on Analogue or DTERM



How do I enable message waiting notification on an analogue or Dterm Phone?





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.

To turn it off dial #*9 and the extension number again.

Number Temporarily Out Of Order Message


When calling the main number I receive a message saying “This number is temporarily out of order”.



This is normally a problem with the network provider, make sure they provide an ETSI standard circuit. There are however a few things to check to be sure.

Have a look at the PRT card (Primary Rate card) and see whether the D-channel light is on, this is the top most green light below the dip switches. If this is off then it’s definitely a network problem.

You can also put a loop back cable on the switch to prove that the PRT card is working ok. This can be done by taking a normal CAT5 patch lead and plugging one end into where the white lead of the PRI connector is plugged in and the other end into where the grey lead is connected, you should now see the D-channel on the PRT card lit up. This proves the PRT card is functioning correctly.



Running Zeacom PABX View on Client PC


How do you run PABXview from a client PC to clear phantom calls?



From the Client PC do the following:-

1. from the CTI Shared Folder  (for example: \\Qmaster\cti\application)

Copy the following files:

1. vcl50.bpl

2. vclx50.bpl

3. SchComp.bpl

4. borlndmm.dll

5. cc3250mt.dll

6. IPCmessaging.dll

and paste into a folder on the client PC that listed in the Windows path (for example %System Folder%\System32)

2. Edit the registry (Regedit.exe) and go to:


and if the entry does not exist, create a new String Value with a Value Name of Host and in the Value Data enter the IP Address of the smartconnect (Qmaster Server).

3. Create a shortcut to PABXview.exe

4. Run PABXview to test.

Prevent CO Trunk Disconnecting with Tannoy System


How do I stop a CO Trunk line release when connecting to a Tannoy System?



To stop the CO Trunk from doing a release set the following:


CM 3505 > CO Trunk Route number : 0

Setup PIN Authentication for IP DTERM logon


By default, as a security measure the IPS2000 authenticates whether an IP phone is allowed to log on by ‘tagging’ the MAC address of the device (softphone nic or IP phone) and then this remains attached unless the phone is logged out using the dterm logout feature.

This causes problems because if a phone that is logged in is simply ubplugged, switched off, or the user tries to login on another phone, it will not allow another mac address to be assigned to that extension.

There is another way though.

You can tell the PBX to use PIN numbers to authenticate the user as the ‘owner’ of that IP extension and this will then allow you to use the protected login feature, which allows you to login anywhere, whether you logged off the original phone or not and it will ‘follow me’.


You have to allow protected login on SRC15 or put the phone into a class that allows it.






/put phone into SRC13 class 1 and 2







/put phone into SRC13 class 3





/put 1234 as the PIN number





/turn on pin authentication over MAC for all phones.



All phones must have a PIN to authenticate the logon.



Setup Divert Button for Ringing Phone


How do I program a feature key button on a Dterm to forward an inbound call to voicemail?



The command below sets the Voicemail Pilot as the VMS (done per tenant):

CM 5118 > Tenant Number (usually 00) : Voicemail Pilot


On the relevant station, program a Feature Key to Call Redirect to the VMS:

CM 9000 > Station Number , Feature Key Number : F5012


For example, running Corus Voicemail,  station 300 needs the second jelly key to be programmed:

CM 5118 > 00 : 1111

CM 9000 > 300,02 : F5012

Setting Call Forwards on Analogue or Virtual Extensions


How do I set a Call Forwarding on a Digital or Analogue station?




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


Setting Call Forwarding Timers


We have a station in the warehouse that requires a much longer ring time before diverting to voicemail than the rest of the handsets in the offices. How do I do this?



For a detailed programming and explaination please refer to the Feature Programming Manual, the chapter on Call Forwarding-Don't Answer.


There are two ways of setting the Call Forward - Don't Answer (No Answer) timers, the first being set per station and the second set for the whole system.


1. Timer Set Per Station:


The following command sets the station not to use the default timer:

CM 1346 > Station Number : 0


The following command sets the alternate system timers for incoming trunk calls in 4 second increments:

CM 410 > 100 : x

where x = 01 to 30

01 = 4 second delay

02 = 8 second delay

03 = 12 second delay

04 = 16 second delay


30 = 120 second delay


The following command sets the alternate system timers for internal or assisted calls in 4 second increments:

CM 410 > 101 : x

where x = 01 to 30

01 = 4 second delay

02 = 8 second delay

03 = 12 second delay

04 = 16 second delay


30 = 120 second delay


The following command sets the unique STATION timers for incoming trunk calls in 4 second increments:

CM E607 > Station Number : y

where y = 001 to 120


The following command sets the unique STATION timers for internal or assisted calls in 4 second increments:

CM E608 > Station Number : y

where y = 001 to 120



2. Timer Set Only For System:


The following command sets the station to use the default system timer:

CM 1346 > Station Number : 1


The following command sets the default timers for incoming trunk calls in 4 second increments:

CM 410 > 01 : x

where x = 01 to 30

01 = 4 second delay

02 = 8 second delay

03 = 12 second delay

04 = 16 second delay


30 = 120 second delay


The following command sets the default timers for internal or assisted calls in 4 second increments:

CM 410 > 15 : x

where x = 01 to 30

01 = 4 second delay

02 = 8 second delay

03 = 12 second delay

04 = 16 second delay


30 = 120 second delay

Setting Date and Time


How do I set the time and date on a NEAX IPS or IVS?



The time and date can be set in two ways, via the MATWorX GUI or in MOC mode.

1. Using the MATWorX GUI

The time and date can be changed using the MATWorX GUI by selecting the System Drop down and selecting the set clock option.

You will then be presented with the time and date screen as below:

This program will change the time and date to the same setting as the time and date on the MATWorX PC if the tick boxes highlighted above are set, alternatively you can un-check the boxes and manually set the time and date in this program. To send the updated time and date to the system simply click on the Write data button highlighted above.

2. Using MOC Mode

To set the time and date via MOC mode you should use the following commands:

CM 02 > 0 : Year (e.g. 2004)

CM 02 > 1 : MMDDWW Date

Note: Month, Date and Day are set by 2 digits each in the order named. Days are set as follows:

SUN: 00 MON: 01 TUE: 02 WED: 03 THU: 04 FRI: 05 SAT: 06

CM 02 > 2 > HHMMSS Time

How To Setup an IP PAD without Compression


Calls cannot be made between two sites using either an IP trunk or Remote PIM.



The following commands need to be taken in to account when using an IP-PAD without VCT cards:


CM0A09 > LAN Interface Number e.g. 01 : IP Location Number e.g. 01 (This command puts the IP-PAD into an IP location)


CM6719 > IP Location Number e.g. 01 : 02 (This command sets the IP loaction to not use any VCT cards)


Once you have set these commands you will need to reset the IP-PAD by switching the toggle switch on the IP-PAD.

Setting Up Remote Access on a 2000 IPS

How do I set up remote access on an IPS 2000 in order to dial in remotely?


First of all the following commands need to be set in the switch for remote access.


CM4010 > 1 : enter an extension number for the modem, in this case 599.


CM7600 > DDI number to be used for the modem, e.g. 3999 : DDI block number e.g. 399


CM7601 > DDI block number, in this case 399 : extension number of modem e.g. 599


Once you have set these commands Switch 2 2/4 needs to be set to the ON position


To connect to this system remotely using MATWorX please view "Configuring Remote Dial-in from MATWorX" (Answer 4469)

Configuring Remote Dial-in from MATWorX




How do I setup a remote dial in connection?


I need to remotely administrate a system, how do I do so?




To connect to a remote site, you use MATWorX as you would to connect via a serial cable (RS-232) or the LAN (TCP/IP).


Step 1:

Click on PBX menu item on the MATWorX toolbar, and then select Setting as shown in the (NEC4911a.bmp) attachment below.


Step 2:

Click on the New icon to create the remote dial-in connection


Step 3:

Click on the Connection Type drop down box and select Modem. Now type in the site's name in the PBX Alias Name box.


Step 4:

You will now need to select the COM Port that your Modem Uses (to check, go to Start -> Settings -> Control Panel -> Phone and Modem Options -> Modem tab).

Choose your Dial Type, Tone or Pulse.

And then remember to type in the DDI for the modem on the system that you wish to connect to under Phone Number. This is covered in "Setting Up Remote Access on the NEAX 2000 IPS" (Answer 4469).

About Silent Monitoring


How is Silent Monitoring switched on or off?



CM 15103 > class number : 0 (Restrict) / 1 (Allow) - Allows users to monitor other users.

CM 15104 > class number : 0 (Restrict) / 1 (Allow) - Allows users to be monitored.

CM 08 > 259 : 0 (Off) / 1 (On) - Switches warning tone on or off


IMPORTANT: Read the note in the command manual that goes alongside CM 08 >259 and make sure the end user knows the implications of silent monitoring.

System Speed Dials Not Adhering to Trunk Restriction


Why do the System Speed Dials ignore the Trunk Restrictions and how do I change this?



When using the Easy Install Script the Toll Resriction for System Speed Dials is not set.  To get System Speed Dials to follow Stations Toll restriction use the following command:-


CM 08 > 044 : 1

Understanding Multi-Site Clustering

How does multi-site clustering work?

NEC Clustering

Understanding and Selling the ClusterConcept

Sales Guide v1.1


Clustering Diagram

NOTE: To view, you will need Microsoft Visio 2003 installed on your computer. If you do not have this, download the Visio Viewer at the bottom of this page.




The purpose of this document is to explain in detail, the technical and sales implications of NEC clusters in a multi site environment. This document is targeted at a sales and pre-sales audience.




When tackling a multi-site environment the traditional way of deploying voice, was to use a platform of the appropriate size at each location.  These platforms would then all communicate with each other via a legacy protocol, such as DPNSS or Q sig.  Using these protocols, or often a bespoke protocol designed by a specific manufacturer, the systems were able to communicate with a limited range of features.


Today with the advent of IP and the proliferation of reliable IP WAN services, the architecture for multi site scenarios, is changing both in the voice and data worlds.   Where sites can be reliably and cost effectively linked, the concept of centralisation is becoming key, to any modern communications network.  Where hardware can be centralised costs are dramatically reduced, administration becomes simple and future deployment becomes faster.


This type of architecture, of centralised hardware, has been a facet of the data world for many years.  Now with the proliferation of VOIP the logical conclusion is that voice will follow the same architecture.  This architecture has been termed by NEC and other manufacturers as “Clustering.”


Other Adopters of the Technology


Like NEC, other large communications companies such as Cisco have followed the same strategy.  When Cisco launched its own voice product nearly five years ago, it naturally adopted the centralised architecture.


AVAYA, took a dramatic u-turn in 2001, to release its new range of Multivantage products.  This product range was to adopt the centralised architecture and move the company from years of developing networked PBX technology.


The Key to Clustering


Within a multi-site environment, the key to clustering is to centralise hardware and thus reduce cost.  However with centralised hardware, the risk of failure at local site becomes a real threat. This is overcome with the use of local redundant processing.


In simple terms this means all the users within the cluster use the processing power of the centralised hardware.  Then if the connection to this hardware is lost, a local processing is provided by a local-redundant processor, keeping the local site alive.

The key benefit to this architecture, is that each site can be evaluated in terms of function and risk.  Then local redundancy can be provided only at sites, where it is deemed essential the site survive in the event of a WAN failure.  Sites not deemed to be essential, will be lost in the event of a failed connection to the central hardware.


Key Benefits to Clustering


-          Allows expensive hardware only to be deployed to the sites where it is required.

-          With all the clients using the centralised hardware, the platform acts as one single system across multiple sites

-          Local redundant processing to provide survivability in the event of WAN failure or hardware failure at the central site

-          Redundant centralised processing in the event of centralised hardware failure

-          Administration is centralised with automatic updates to the outside nodes

-          Growth of the platform is centralised allowing the roll out to integrate into the data network growth

-          Deployment of application is centralised, negating the need for hardware at each site

-          Overall system growth becomes more flexible as multiple clusters are linked




NEC’s number one USP is the migration story, which in a clustered environment is essential in making the architecture cost effective.  At each site in the cluster, the NEC solution offer the customer total flexibility between the type of endpoint deployed, IP or traditional.  Further to this the NEC offers full migration from a traditional digital endpoint to a full IP endpoint, with full retention of investment.  All of this is achieved at a market leading price.


NEC Hardware


The NEC hardware is simple to design, configure and deploy.  All cards are common at each site as are the handsets and licenses.  The only item that changes is the type of CPU, an IPS always forms the central node of the cluster, with DMR’s where redundancy is required at the outside nodes.


Cluster Capacity


CPU Type Traditional Users IP Users

IPS Central CPU

500 Users at the central site* 500 Users at the central site*

DMR Local Redundant CPU 60 Traditional users at local site** 120 IP Users at local site**


*  Numbers of users will vary depending on trunk configuration and number of IP/traditional users

** Number of users will vary depending on trunk configuration.  The number of traditional users is available in conjunction with the 120 IP users.


Selling Clusters over Traditional Networking


With clustering it important to understand, which areas of the concept are going to appeal to the various parties within a perspective customer.


IT Manager/Director


-          Ease of administration

-          Ease of roll-out

-          Control of the voice network in a format they can understand

-          In the case of IP, the possibility of getting their network upgraded


Finance Director


-          Reduced cost of ownership, in terms of admin and growth

-          Reduced implementation cost through totally flexible migration (Unique to NEC)


Company Director


-          Cost if of course the major concern

-          Comfort factor buying the latest technology as support by other major vendor adoption


Cost of Ownership


Clustering often comes about through the need or interest for IP telephony, which is growing through most sectors of the market.  Through this, comes the immediate need to upgrade data infrastructure to handle voice and data.  This need to upgrade the data network, plays on the key NEC USP, flexibility and migration.




Customer sold on IP, centralisation and clustering can still achieve this architecture but with a mix of traditional and IP endpoints.  Therefore, allowing the data infrastructure to be upgraded in line with its existing life cycle costing.  By eliminating the need to remove and replace massive data infrastructures overnight, the customer is given the solution they require tomorrow at a cost they can afford today.




Flexibility is just one half of cost story, without migration the flexibility from day one is lost as the system grows.  Through the retention of the handsets and their ability to become IP handsets, a large percentage of the initial investment is retained.




The NEC cluster offers the customer the latest architecture, whilst still growing with their data network, at the most competitive price in its market sector.



View Pre-Existing Settings in MOC


How can I view what settings has been set on the PBX?


To view data entries, type in the command, press the spacebar, type in the second data, press the spacebar key and the second data value is displayed. By pressing enter /return key, the first data values are stepped through.


Pitfalls Between Remote Site and Managed Ethernet Networks

When connecting MP card, IP-PAD cards or IP telephones to Ethernet switches that support STP, Spanning Tree Protocol (IEEE 802.1d)and LACP, Link Aggregation Control Protocol (IEEE 802.3ad), there is a strong possibility that communications will be disrupted. Ensure that both of these features are deactivated on Ethernet switches.


The following are examples of conflict with these features:

IP telephones fail to connect to the PBX.

Calls between IP telephones cannot be made.

Calls between IP telephones and legacy telephones or trunk cannot be made.

With Remote PIM over IP the Remote site does not operate in Normal mode.

2000 IPS Remote Site (DM)

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.

NEC 2000 IPS and DM System Cards

Both the 10u and 2u chassis accepted the same circuit cards - the DM chassis takes either 5 or 7 cards (sepending on the age of the unit) and the full size system took up to 12 cards. Only certain slots could contain cards which needed wiring out (like extension/line cards) and other cards like Main or Firmware Processors had to site in single unique slots only. If you got it wrong, you could be very liable to destroy the card or the backpane....


Most cards are hot swappable and can be done live, taking only a few seconds to come back online. Some cards are considered more 'smart' than others with various systems on-board, like make-busy switches, firmware, and ranges of information LEDs and switches.

Direct Dial Inward (DDI) Programming for 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, but it's only real use we have found is to look up every possible programmed DDI in the system. It also only appears in some chosen later versions of Matworx.


So 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. In the USA, it's often called DID (direct inward dialling).


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.


Command Line, MOC and CAT Mode

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)  A GUI called MATWorX which is available for most Windows-based operating systems.


MATWorX offers the following features:

  • 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"

« StartPrev123NextEnd »

Page 1 of 3