Q: How do you assign an IP address to the M606 NIC?

A: From MATWorX select menu item System and then LAN Interface

The following window will appear:

Click on the Lookup button

Insert the relevant IP Address, Subnet Mask and Default Gateway (if a Default Gateway is required).

Click on the Update button to write the changes to the CPU.

You will then be prompted to backup the customer data and restart the system. This is required and will stop call processing while the system restarts.

You can also set the IP Address information using the following commands:

CM 0B00 > 00 : IP Address ( e.g. 192168001005 )

CM 0B00 > 01 : Subnet Mask ( e.g. 255255255000 )

CM 0B00 > 02 : Default Gateway ( e.g. 192169001001 )

To define a dial plan you use Command 200 to define each number range as shown below:

Thanks for visiting and hope you find this information helpful. I’ll try to update with more stuff at least once a week. Any questions or if you’re in the UK and need support, you can get in touch via the contact tab at the bottom of this screen.

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:

Mr Modem model number: – MRI-1456 EVS –serial external modem

CP-31 Main processor wit 6.2 ver. 3.00 software load RS NORM- 4S CA-A NR-553924-107

Programming requirements:

1) On the Modem you need to put the following Modem string ATS0=2 this is an auto answer string. This is a Auto Answer string that answer after 2 Rings

2) On the NEAX CP-31 main processor the comm. Port needs to be set to 9600 bps .This is achieved by the following command
CMD 40 Y=08 FD= 0 SD = CCC OR 4 (By setting CCC this sets the default setting which is 9600 bps)

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

*66 A160 10-Party Conference Trunk Access

*68 A162 6/10-Party Conference Trunk Control (Release)

*67 A161 6/10-Party Conference Trunk Control (Set up)

*65 A159 6-Party Conference Trunk Access

*20 A085 Account Code

#06 A045 ACD/UCD Station Busy-Out Reset

*06 A044 ACD/UCD Station Busy-Out Set

*38 A164 All Zone Internal Paging

#969 A109 Announcement Service Delete

*970 A104 Announcement Service Group 0 Replay

*971 A105 Announcement Service Group 1 Replay

*972 A106 Announcement Service Group 2 Replay

*973 A107 Announcement Service Group 3 Replay

*974 A108 Announcement Service Group 4 Replay

*969 A103 Announcement Service Record

*21 A086 Authorization Code

*980 A039 BGM on Dterm Set/Reset

#00 A003 Call Back Cancel

*00 A002 Call Back Set

#*6 A190 Call Forwarding Not Available Cancel

#*7 A191 Call Forwarding Not Available Replay

#*5 A189 Call Forwarding Not Available Set

#01 A011 Call Forwarding-All Calls Cancel

*01 A010 Call Forwarding-All Calls Entry

#03 A015 Call Forwarding-Busy Line Cancel

*03 A014 Call Forwarding-Busy Line Entry

#02 A017 Call Forwarding-Don’t Answer (-No Answer) Cancel

*02 A016 Call Forwarding-Don’t Answer (-No Answer) Entry

#04 A019 Call Forwarding-I’m here (-Destination) Cancel

*04 A018 Call Forwarding-I’m here (-Destination) Entry

#05 A013 Call Forwarding-Don’t Answer/Busy Line Cancel

*05 A012 Call Don’t-Don’t Answer/Busy Line Entry

*12 A046 Call Hold

#08 A009 Call Park-System Retrieve

*08 A008 Call Park-System Set

*24 A062 Call Park-Tenant Set/Retrieve

*22 A037 Call Pickup-Designated Group

#2 A021 Call Pickup-Direct

#8 A020 Call Pickup-Group

*13 A125 Call Waiting (Camp-on by Station)

*29 A007 Camp-on by Station (Transfer method)

*23 A042 Choice of Night Service from Attendant

*27 A156 Data programming for DISA Speed Calling-System, Data/Time Change and Tone Ringer Change from SMARTCON

*25 A043 Day Night Mode Change by Station Dialling

*26 A155 Day/Night Mode change, ATTCON Lockout from SMARTCON

#*2 A102 Digital Announcement Trunk Access Delete

#*0 A100 Digital Announcement Trunk Access Record

#*1 A101 Digital Announcement Trunk Access Replay

*960 A022 Do Not Disturb Set

#09 A023 Do Not Disturb/Return Message Schedule Cancel

#960 A023 Do Not Disturb/Return Message Schedule Cancel

*999 A094 Emergency Call

*28 A006 Executive Right of Way (Executive Override)

*951 A095 Individual Attendant Access/ Inter Position Transfer

*950 A081 Individual Trunk Access

#30 A138 Internal Zone Paging Group Answering 0-7

#31 A139 Internal Zone Paging Group Answering 0-7

#32 A140 Internal Zone Paging Group Answering 0-7

#33 A141 Internal Zone Paging Group Answering 0-7

#34 A142 Internal Zone Paging Group Answering 0-7

#35 A143 Internal Zone Paging Group Answering 0-7

#36 A144 Internal Zone Paging Group Answering 0-7

#37 A145 Internal Zone Paging Group Answering 0-7

*30 A130 Internal Zone Paging Group Calling 0-7

*31 A131 Internal Zone Paging Group Calling 0-7

*32 A132 Internal Zone Paging Group Calling 0-7

*33 A133 Internal Zone Paging Group Calling 0-7

*34 A134 Internal Zone Paging Group Calling 0-7

*35 A135 Internal Zone Paging Group Calling 0-7

*36 A136 Internal Zone Paging Group Calling 0-7

*37 A137 Internal Zone Paging Group Calling 0-7

*952 A034 Intra-Office termination on Tandem Connection

*953 A035 Intra-Office termination on Tandem Connection (Send DT)

*14 A069 Last Number Call (Redial)

9 A126 LCR Group 0

*930 A029 Maid Status

#928 A149 Message Reminder Cancel

*927 A148 Message Reminder Set

#926 A147 Message Waiting/Message Reminder Retrieve

*926 A146 Message Waiting/Message Reminder Search

*39 A033 Monitor

#*9 A041 MW Lamp Control Reset

#*8 A040 MW Lamp Control Set

*11 A110 Name Display

#51 A195 Number Sharing Cancel from main station

#50 A193 Number Sharing Cancel from sub station

*51 A194 Number Sharing Set from main station

*50 A192 Number Sharing Set from sub station

*925 A084 OAI Terminal Mode Set Facility (MSF)

#921 A001 Outgoing Trunk Queuing Cancel

*921 A000 Outgoing Trunk Queuing Set

#922 A005 Outgoing Trunk Call/Call Back Cancel

*922 A004 Outgoing Trunk Queueing/Call Back Set

*40 A070 Paging Answer Zone

*41 A071 Paging Answer Zone

*42 A072 Paging Answer Zone

*43 A073 Paging Answer Zone

*44 A074 Paging Answer Zone

*45 A075 Paging Answer Zone

*46 A076 Paging Answer Zone

*47 A077 Paging Answer Zone

*48 A078 Paging Answer Zone

*49 A079 Paging Answer Zone

*52 A088 Priority Call 0

*53 A089 Priority Call 1

#70 A210 Re-participation Group Call-2Way Calling (Group 0-7)

#71 A211 Re-participation Group Call-2Way Calling (Group 0-7)

#72 A212 Re-participation Group Call-2Way Calling (Group 0-7)

#73 A213 Re-participation Group Call-2Way Calling (Group 0-7)

#74 A214 Re-participation Group Call-2Way Calling (Group 0-7)

#75 A215 Re-participation Group Call-2Way Calling (Group 0-7)

#76 A216 Re-participation Group Call-2Way Calling (Group 0-7)

#77 A217 Re-participation Group Call-2Way Calling (Group 0-7)

*09 A154 Return Message Schedule Set

*920 A158 Sending of Hooking Signal to C.O. line from PB telephone

*58 A196 Set Relocation

*910 A220 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*911 A221 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*912 A222 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*913 A223 Simultaneous Paging Group Call-2Way Calling (Group 0)

*914 A224 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*915 A225 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*916 A226 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*917 A227 Simultaneous Paging Group Call-2Way Calling (Group 0-7)

*70 A200 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*71 A201 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*72 A202 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*73 A203 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*74 A204 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*75 A205 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*76 A206 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

*77 A207 Simultaneous Paging Group Call-6/10 Party (Group 0-7)

#40 A080 Speaker/Radio Paging Cancel (Delay Operation)

*54 A090 Special Operator Call 0

*55 A091 Special Operator Call 1

*56 A092 Special Operator Call 2

*57 A093 Special Operator Call 3

#07 A066 Speed Calling-Station (Station Speed Dialling) Cancel

*07 A065 Speed Calling-Station (Station Speed Dialling) Entry

** A064 Speed Calling-Station (Station Speed Dialling) Origination

*15 A152 Speed Calling-System (1000 Memory BK0)

*16 A151 Speed Calling-System (1000 Memory BK1)

*18 A150 Speed Calling-System (1000 Memory BK3)

*17 A068 Speed Calling-System Origination (1000 Memory BK2)

## A067 Speed Calling-System Origination (300 Memories)

#60 A181 Split Call Forwarding-All Calls (Cancel)

*60 A180 Split Call Forwarding-All Calls (Entry)

#61 A183 Split Call Forwarding-Busy Line/Don’t Answer (Cancel)

*61 A182 Split Call Forwarding-Busy Line/Don’t Answer (Entry)

*80 A047 TAS Answer A

*81 A048 TAS Answer B

*82 A049 TAS Answer C

*83 A050 TAS Answer D

*84 A051 TAS Answer E

*85 A058 Trunk Hold

*78 A163 Voice Call/Ring Tone Programming

*901 A114 Voice Message Waiting Service-Individual

*907 A165 Voice Message Waiting Service-Individual

*900 A113 Voice Message Waiting Service-System

*904 A118 Voice Message Waiting Service-System Delete

*902 A115 Voice Message Waiting Service-System Record

*903 A116 Voice Message Waiting Service-System Replay

*905 A119 Voice Message Waiting Service-System/Individual (Reset)

*906 A120 Voice Message Waiting Service-System/Individual (Retrieve)

*909 A028 Wake Up Call Set from Predetermined Station (MWU)

*908 A027 Wake Up Call Set from Predetermined Station (SWU)

#10 A025 Wake Up Call/Timed Reminder Cancel

*10 A024 Wake Up Call/Timed Reminder Set

*19 A188 Whisper Page

Connecting To The Voice Messaging System

With the BRU utility, you can use either a null modem (serial) cable or a modem to connect the BRU Remote on the support computer to the BRU Host on the voice messaging system. Once you have used the BRU utility to connect to the voice messaging system, the connection status and baud rate are displayed at the bottom of the screen.

Note Although you can use CoSession to establish a remote maintenance connection, you cannot maintain this connection and connect the BRU Remote to the BRU Host at the same time.

Reconfiguring the serial port

The serial port on the support computer is used to make a null modem cable or modem connection. By default, the BRU Remote is configured to use COM1. If the support computer is already using COM1 for another connection or a device such as a mouse, you can select a different serial port. The BRU Host is configured to run at 19,200 baud on NEAXMail AD-8 voice messaging systems. Before you attempt to connect the BRU Remote to the BRU Host, be sure that the BRU Remote is set for the same baud rate by following the procedure below.

To reconfigure the serial port settings

1 Start the BRU Remote.

2 From the BRU Connection menu, type 3 and press ENTER to select “Configure serial ports.”

3 From the Serial Port Configuration menu, select one of the following:

· 1 and press ENTER to select “Select serial port.

· 2 and press ENTER to select “Change baud rate.

4 To save the new serial port settings for future BRU sessions, type 3 and press ENTER to select “Save current settings.” Otherwise, the serial port settings are valid for this session only.

5 Type 4 and press ENTER to return to the BRU Connection menu.

6 Follow the on-screen instructions to exit the BRU Remote.

To connect the BRU Remote to the BRU Host

1 Establish a remote maintenance connection by using CoSession.

2 Exit the voice messaging system.

3 From the Utility menu, type 2 and press ENTER to select “Voice Mail Utilities.”

4 From the Voice Mail Utility menu, type 5 and press ENTER to select “Backup, Restore, and Update—BRU utility.”

5 When prompted, hang up the CoSession connection and close the CoSession window to end the remote maintenance connection.

6 Start the BRU Remote. After the Connection Menu appears, wait approximately one minute before proceeding. If you are connecting by modem, wait two minutes. (When the BRU Host is ready to connect to the BRU Remote, the #1 and #4 LEDs will light up.)

7 From the BRU Connection menu, select one of the following:

· 1 and press ENTER to select “Connect to BRU Host via null modem cable.”

· 2 and press ENTER to select “Connect to BRU Host via modem.” Type the phone number or extension for the public phone network (analog) line connected to the modem and press ENTER.

8 After the connection has been made, press any key to proceed to the BRU Main menu.

Tips

If you are not connected to the voice messaging system by a remote maintenance connection, you can use the make busy (MB) switch and the #4 DIP switch to start the BRU Host. First, move the MB switch to the up position.

Then change the #4 DIP switch on the voice messaging system interface to the ON position. Finally, return theMB switch to the down position, and push the Reset button on the voice messaging system interface. To connect the BRU Host with the BRU Remote, continue with step 6 in the above procedure.

If you do not establish a modem connection within 10 minutes, start the procedure again beginning with step 1.
Backing up system files.

It is a good idea to back up your voice messaging system files regular basis. You may also want to back up system files after installation, before major software updates, and after software changes or updates. Because you must exit the voice messaging system, plan to perform backups during off-hours.

The backup process requires that you select the type of backup you want and indicate the directory path on the hard drive where you want to store the backup files. This information, along with the date, time, and an optional comment line, is used to generate a description of the backup files.

Note Using the BRU utility, the voice messaging system files are directly backed up to the support computer’s hard drive. You can also use the voice messaging system’s archive procedure to save voice messaging system files to a separate location on the voice messaging system hard drive.

Types of Backups

Use the BRU utility to back up the voice messaging system database files, outgoing messages (OGMs), and incoming messages. The backup process takes between five minutes and about three hours, depending on the type of backup you choose and the number of subcribers and messages on your system.

Tips

After backing up the files to the hard drive, copy them to diskettes for offsite storage.

Back up your files on a regular schedule, such as every month.

Keep a written log of the directory path where your backup files are stored.

To backup system files

1 Use the BRU utility to connect the support computer to the voice messaging system (see “To connect the BRU Remote to the BRU Host” on page 6 )

2 From the BRU Main menu, type 1 and press ENTER to select “Backup.”

3 From the Backup menu, select one of the following:

· 1 and press ENTER to select “Database only.

· 2 and press ENTER to select “Database and OGMs.

· 3 and press ENTER to select “Database, OGMs, and messages.

4 Type the directory path where you want to store the backup files on your support computer. If the directory you indicated does not exist, the BRU utility will create it.

5 Follow the on-screen instructions to complete the backup procedure.

5. Restoring system files

If the voice messaging system’s database becomes corrupt and unusable, you can restore system files from a recent backup using the BRU utility.

WARNING! Restoring the voice messaging system files will overwrite existing files.

To restore system files

1 If you are restoring system files from diskettes, copy the backup files to the support computer’s hard drive.

2 Use the BRU utility to connect the support computer to the voice messaging system.

3 From the BRU Main menu, type 2 and press ENTER to select “Restore.”

4 Type the directory path where the backup files you want to restore are stored.

5 Follow the on-screen instructions to complete the restore process.

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.

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

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.

Switching between former and extended SMDR formats!

There are two types of SMDR output (the data stream that comes out of your serial or ethernet port on the NEC 2000 IPS that usually goes into a call logging / management system to tell you what calls have been made or recieved and for how long etc. The former is the ‘usual’ format, but the extended gives some additional information, like inbound call abandonment time.

To switch between the two (and you must have Series 3400 firmware on the CPU to do this), you use command 04, and First Data 07 for SMDR over RS-232 and 08 for over IP. The structure is CM04> 07 (or 08 if you’re doing call logging over IP) : then 00 for Extended Format and 15 for Former Format.

Hi Everyone! Sorry it’s been quiet here the last few weeks. It’s been a busy Christmas season, and there has been a bit of the old lurgy drifting around NECPBX Towers, meaning people have been desperately trying to breathe, cough and get better. New updates coming soon. Any questions – give the forums a post!

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!

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 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.

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.

Upgrading Licences the New way!

This guide decribes the procedure for upgrading the new style NEC licenses on an NEC 2000 IPS or Philips Sopho IPS. This was written in the UK, where the licence model changed upon the release of the R10 processor. In other countries this may be different.

The older style used KeyFD – floppy disks which were written with the serial of the NEC CPU when applied to a the processor, meaning they can only ever be re-applied to the original processor. This was replaced, as I’ve said with a new method where the licences either came in a ZIP file, or on floppy disk.

License Loading Procedure

This first step in the procedure will guide you through the relevant steps to import your new licences onto the CPU. The file that will be delivered may be sent to you by email, or may come on floppy disk. If you’re using the licence install program which comes with MATWorX R10, then the IVS2_opt.exe files must be loaded into the root of the floppy drive . If you manage to get MATWorX R11+ then you can simply navigate the program to the directories on your computer which contains the licence files.

You will also have received a text file with what licenses will be added. An example below indicates that the file will add an 8 IP port license and a 4 port SP30 license.

NATION:GB

CARDTYPE:

SYSTEM_ID:

MP_BARCODE:

CPU_NO:

JOB_NO:065857

STOCK_NO:960052150497 960052150641 960052150680

IPS_LIC:8

SP20_LIC:0

RPIM_LIC:1

SP30_LIC:4

LT64_LIC:0

GEN_KEY:

OPT_KEY:0909953779140

PO:419590065857

CUST_NAME:200 IPS TEST

To display the licenses in the CPU using the MOC in MatWorX, type the following command:

CM>F88:01:

This will display the first license. Press return to display each license in turn as below. Note: in this example below, there are no SP30 or IP Port licenses.

Applying The Licences

1. Run the program ‘IPS Registration wizard’. This can be found under program files / MatWorx (dependant on which version of MatWorx you are using) IPS Registration Wizard.
2. Begin the IPS Registration Wizard and when you reach the installation/Activation screen below, select install software.

3. After you press the Next button, the Keykeeper load screen will appear as below. Please insert your License disks. Once the disk has been loaded it should look like the picture below. (note this image is from MATWorX V10, so it doesn’t offer you to browse to a folder on your machine).

4. The next screen will have a start button on it to load the option disks please press the start button.

5. Once the option disks are loaded press the next button and a screen will appear that will ask if you want to activate now or later. Please select activate later and check the box as below:

6. After clicking next the wizard will ask you for a location and name to save the device activation profile. Once the folder has been chosen, press the Create button. This will create you a file in your chosen location called ‘Name ( the name you called this file ).dpf’.
7. Once the file is created, click next. You will be asked to finish the Wizard .

This is the first step completed. You have loaded new MP software and loaded Keykeeper disks and created a profile that can be authenticated with an NEC server via an analogue modem.

Creating an activation profile

1. Run the program IPS Registration. This can be found under program files MatWorx IPS Registration Wizard.
2. Begin the IPS Registration wizard and when you reach the installation/Activation screen below, select Activate Software as below:

3. Click the next button and this will take you to a screen that ask ‘s if you would like permanent activation or Temporary activation. Please select permanent activation. If there are no PSTN lines available on site, temporary activation will activate the processor for 5 day’s .You need to activate the processor permanently before this 5-day period expires.
4. After you select permanent activation the next 2 screens will ask you to fill in customer and engineer details. The fields denoted by an asterisk are mandatory but we recommend you fill in all the fields . Please see the examples below:

5. After filling in the details, click the next button a screen will appear with 3 options please select “Register from device profile” then press the next button.
6. The next screen will confirm the modem on your laptop/PC and the number that needs to be dialed.
7. After selecting next a screen will appear that will ask you for the location of you’re your .dpf file you created earlier. It will also ask you for a name and location for the Activation profile file (.apf). This is the file that is created by the registration server in Holland and needs to be registered in the CPU.
8. Once you have entered the names and locations above you have to press the Activate button and this will then dial our registration server in Holland. When finished, the wizard will display a screen that will say that the device was successfully activated and create you a file that will look like this
9. Once completed press the next button and finish the wizard.
You have now successfully created a activation profile to register on the CPU.

Activating CPU from a profile.

1. Please follow steps 1 – 4 in creating an activation profile. The site info will already be completed when you run it this time.

N.B. you have to have the port on the CPU set at 9600 and there must be NO password enabled on the system.
2. After completing above a screen will appear with 3 options will appear please select “Activate device from Activation profile file (.apf)” then press the next button.

3. After clicking next a screen will appear that will ask for the location of the Activation profile file.
4. Once you have found the location of the file, please press the Activate button. Once the system has been activated a screen will appear saying that it has been successfully activated.
5. After pressing the next button the following screen will appear reminding you to reset the CPU.

6. Click next to finish the Wizard. You should then connect via MatWorx and check if the licenses have been registered as below.

You have now successfully upgraded your licenses on the CPU and will now have and additional 8 x IP ports and 4 x SP30 licenses.

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.

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.

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

Zeacom Phantom Calls

In versions 2 and 3 of the Zeacom Server, you may need to delete a phantom call? What is a phantom call, I hear you ask? Well, the Zeacom Server is constantly monitoring and controlling calls from the NEC 2000 IPS (or whichever PBX, really!), and so sometimes the Zeacom Server isn’t able to determine a call has ended – or was able to connect it in the first place. This sometimes causes Zeacom applications to show a call is in progress, when infact the Zeacom should have cleared the call down.

You can delete phantom calls in Zeacom Q-Master queues, or seen via a CTI app using the PABXview tool that is supplied with the server software. This tool is designed to allow removal of such calls without interfering with the operation of other live calls and the system as a whole.

Killing phantom calls is not a routine function that should be performed by a Call Centre Supervisor.

1. Open Zeacom Q-Desktop. (This can be done on the Zeacom server).

2. Place the mouse cursor over the phantom call. The phantom is normally the first in the
queue as it would have spent the most time there. A reference number appears under the
cursor as indicated in Figure 1. Note that the computer running Zeacom Q-Desktop must have
Internet Explorer 5.0 or higher installed to show this reference.

3. Record the reference number. This number is in decimal. Using a calculator, convert this
number to HEX. A scientific calculator can be accessed on the server in the following way:
− Click Start Programs Accessories Calculator
− On the Calculator toolbar, click “View” and “enable Scientific”.

4. Run the file: C:\Program files\Zeacom\System\PABXview.exe

5. Click on the icon indicated in Figure 2. Look for the reference number that you have
recorded in the “seq” column. It is very important that you confirm that you have the correct
number for that call when on a live site. Otherwise you could easily delete a queued
customer call.

6. Right-click on it. Under the cursor, a phantom window appears as indicated in Figure 3.
Left-click on it.

7. Your phantom should now be cleared. Check the queue.

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!

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!

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.

SMDR Overview

The Station Message Detail Recording (SMDR) feature allows the system to send a raw data of the trunk outgoing/incoming call information. The SMDR data can be received by a personal computer (PC) which is running RS-232C terminal emulation software. ( This is referred to in the rest of this TIB as simply “SMDR terminal”) The NEAX 2000 IVS provides two sources of SMDR output – one is via the Main Processor (MP) built-in SMDR, and the other is the SMDR via the Application Processor (AP00).

Call information is sent out from the MP or AP00 to the SMDR terminal when each call is completed. If the SMDR terminal is not connected to the system or if the SMDR terminal is not ready for receiving information, the call information is temporarily stored in the MP or AP00. As soon as the SMDR terminal becomes ready to receive information, the call information temporarily stored in the MP or AP00 is sent out to the SMDR terminal.

MP Built-in SMDR

The Built-in SMDR consists of the MP and the external SMDR terminal.

• MP card:The MP stores various kinds of information on an event basis. When a call is completed, the MP sends out the call information for that specific call to the SMDR terminal. Two RS-232C ports can be used for the SMDR terminal interface. The MP keeps supervising the status of the SMDR terminal. If the SMDR terminal is not ready to receive information (Busy Status), the MP temporarily stores the call information into its internal memory. When the number of the call records stored in the MP reaches the maximum, new call records will be lost. Note: the call record memory will be cleared by MP reset.

• SMDR Terminal: An Asynchronous Personal Computer is used as the SMDR terminal for receiving and processing the call information. The maximum number of SMDR terminal is two.

SYSTEM CAPACITY

(1) MP Built-in SMDR:

# The maximum number of trunk calls simultaneously: No EXPMEM card on MP provided: 64 trunk calls, EXPMEM card on MP provided: 255 trunk calls.
# The maximum of call recorded: No EXPMEM card on MP provided: 256 call recorded, EXPMEM card on MP provided: 1024 call recorded.

SMDR terminal Programming

Command FD SD

4000 0 or 1 14 (This sets port 0 or 1 to output SMDR, note: if you set port 1 to SMDR inbuilt modem cannot be used!!!!!)
4001 *0 or 1 1 (Default) – Data length 8 bits
4002 *0 or 1 1 (Default) – Parity check ineffective
4003 *0 or 1 1 (Default) – Parity odd
4004 *0 or 1 0 – 1 Stop bit
4008 *0 or 1 4 – 9600 Data speed

Additonal commands:

1306 – Provide SMDR for station
3514 – Provide SMDR for trunk route
1305 – Provide incoming SMDR per extn
3549 – Provide incoming SMDR per Trunk Route
CM08, FD:426 SD:0 Effective for all incoming calls
CM08 FD:463 DS:0 Send CLI to SMDR terminal

To test the output from the main processor after the above programming connect the SMDR cable between the comm. Port on your PC and the Main Processor. Run Hyper Terminal or a similar application set the comm. Port as : 9600 8 none 1 and you should get the following output after several successful calls:

0!KE030027001810 10311157421031115815 000030 00000 0!KE030026001811 10311157561031115824 00003000001908690888 0 0!KA03003400120210311157421031115824 0000300301620292047744000000 0!KA030055001216 1031114940103111583800003003016201753822921 0000 00!KE030026001402 10311158241031115900 10003000001908690888 0 0!KE030025001810 10311155131031115921 000030 000012528202550 0!KA061250001810 10311155381031115921 000061061711 0000 0 0!KE0300
26001811 10311159121031115929 00003000001512366600 0

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 Everyone

I’m hoping to introduce a small forum section soon, where open discussion can occur purely regarding the NEC 2000 IPS, the NEC 2400 IPX or the Zeacom Server suite of applications. I’m just working out the code – don’t expect it to be that pretty! But it should work!

Don’t forget. If you have any 2000 IPS or Zeacom questions, please ask them here

Cheers! Alex

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

Here are some manuals for the NEC NEAX 2000 IPS. We’ve included here R14 manuals, which are pretty much backwards compatible – they list up which series release of MP firmware is required for commands which were introduced along the way.

• General Description Manual – A Philips Manual describing the features, capacity and so on of the NEAX 2000 IPS (or Sopho IPS as they call it)
• 2000 IPS Reference Guide – Talks about the history of NEC, the architecture of the NEAX 2000 IPS, and again it’s capacity and features.
• R14 Business & Hotel Feature Programming Manual – discusses how to program all the features of the system and associates commands together so you know all the commands related to one another to make something work
• R14 Command Manual – The Holy Bible! Contains all the general-release engineering commands for programming on the system
• R14 ISDN System Manual – Manual specifically about implimenting ISDN connections
• R14 Maintenance Manual – Manual for troubleshooting, alarm codes, problem solving etc
• SIP Trunk Manual - Programming the SIP Trunk Card

I’ll be posting up more in the near future – but if anyone has any problems downloading these, or need something specific, then please let me know.

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!

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″

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.

The NEC 2000 IPS can utilise VoIP (Voice Over Internet Protocol) in many different ways. Here are many ways in which you can usefully utilise VoIP on your NEC 2000 IPS:

1. If you have limited cable infrastructure in your premises, IP DTERMs are useful because they can use the same cable connection as your wire-networked computer. The IP DTERM sits inline between the PC and the wall socket and allows you to provide a phone point where normally you could need an entire new cable run.
2. If you work from home, or remotely outside the office, installing an IP Softphone on your computer can provide you with an internal extension where-ever you have VPN access back into your office. The IP Softphone uses a USB handset or headset, and software on screen to simulate all the functions of your NEC DTERM. You can also use this in conjunction with a Zeacom CTI installation, such as Desktop for a feature rich voice solution.
3. If you have a hardware VPN connection to your office location (usually using a DSL router or firewall), you can plug in an IP DTERM at home and have it run as if it were sat in your office.
4. Using VOIP you can interconnect NEC IPS systems in a variety of ways. This means you can make calls between offices for nothing, using an existing WAN (wide area network).

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!

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.

Visit our main section on the PBX to find out more about the NEC 2000 IPS system architecture.

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!

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!

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