| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | n00b needs virtual help Greetings to all, and thanks to the creator/host of this forum! I can see that I will probably be spending a lot of time here in the coming months. Upon taking a new job, my first day in the office and I'm [surprisingly] told that I will be managing an NEC NEAX 2000 IPS+IVS (they have both) system. I've never managed a PBX in my life. I know very little about them. I know that we do have MATWorX installed and functional. The previous admin has a folder full of notes; unfortunately she wrote them specifically for herself so that only she would understand them. They have "commands" and such, but they really are Greek to me. I know that probably most of them are related to the MOC utility in MATWorX but she did a very poor job (in fact, nonexistent) of documenting anything. One thing I have already been asked to do is to setup a job hotline for the company using two "virtual" extensions. The HR people want one line, 7100, to be a listing of open jobs with the company, and a second line, 7600, to be a voicemail line where callers can leave a message regarding the open jobs. I don't even know where to start, but I'm more than willing to learn and read. Unfortunately I cannot find any manuals for the NEC's nor for MATWorX anywhere in this data center or in digital form on our fileserver. I know this is a total n00b question, but...could someone link me some threads on how to setup these virtual hotlines, or provide a link to a manual which would help me, please? Pretty please? With sugar on top? I really don't want to have to call a consultant and spend a bunch of money on my first day here. (Even though they never discussed the PBX in the interview process!) TIA | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Senior Member ![]()
Rep Power: 0 ![]() | I'm a noob too, but picked up a few things along the way in the last several months. You can the manuals here: NEC Unified Solutions The 3 most important manuals you will find is the Command Manual, the Feature Programming Manual, and the Business/Hotel/Data Feature & Specifications Manual. I have an IVS2 which is a step down from the IPS, but they share alot of the same commands. The names of these manuals may be slightly different for the IPS, but here is the breakdown. The command manual shows you what commands do what, and how to program them into the PBX. If you look at the notes left behind by the previous admin, you can look in the command manual to see what those commands are for. So if she has Command 14 or CM14 written down, open the Command Manual and look for CM14. CM14 assigns station/trunk/card numbers to the ports on the LEN in the PIM. The Feature Programming manual is just that. It gives you the command neccessary to program Features in the PBX. The Business/Hotel/Data Feature & Specs manual shows you how to work those features once they are programmed. The trick in programming with the NEC is understanding the manuals. You will find alot of y=something. Y's are like sub commands of the main command. Take a command like 17. 17 is the command code for ACD/UCD Groups. The Y data can be 0,1,2,3,4,etc. Command 170 is a subcommand of Command 17. Command 171 is the same and etc. So if Y=0, or Y=1, you add it onto the Command. To create virtuals, you need to look at command 11. To enter commands, you can either open a MOC terminal and hit F9, or you can program from any display phone by pressing in order: Feature Conf * Feature Conf #. Press the Redial key to get COMMAND=. You will need to find an available Virtual LEN to assign the Virtual Number. You can use MatWorx to do alot of the functions instead of MOC, but it's not always reliable. MOC is generally perfered, but I have found MatWorx to be particularly useful in generating reports that show me what LEN's are in use, what hunt groups are setup, and etc. There is alot you will need to know before tackling what your company wants here. I know your pain, as I was put in a very similar situation 6 months ago. I had little to no documentation whatsoever. They want 7100, and 7600, but you need to make sure those numbers are setup in the Numbering Plan. The Numbering Plan is important, because it dictates how the PBX will react to what numbers are dialed onto the phone keypad. Do you already have extensions that start with 71 or 76? If so, then you'll be okay, if not you will need to add them, and you will need to make sure no Feature Access Codes are programmed with 71 or 76. You will also need to know how to get into your voicemail system and manage that as well. Unfortunately, I do not have the expertise to tell you exactly how to do it, but fortunately others will chime in with alot more experience. I hope this is enough to at least get you started. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Thanks a ton! That gives me enough to get me started. I'm going to be breaking some things along the way, but that will give me the opportunity to learn by fixing them, too. I really appreciate your guidance. I know what I'll be doing this weekend | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Senior Member ![]()
Rep Power: 4 ![]() | Might I suggest you take a look here..... NEC: PBX solutions FAQ Index - Tek-Tips Also you will need to let us know the make and model of the Voicemail system. Regards R4 AKA OzzieGeorge | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Another n00b i'm afraid | gandalf800 | Introductions | 10 | 11-20-2006 08:36 AM |
| Virtual Office with ACD | Cflynt | Meridian Systems | 2 | 11-17-2006 12:18 PM |
| Complete and utter n00b | potato | Introductions | 3 | 11-15-2006 07:20 AM |
| Virtual Office ? | Meridian Systems | 1 | 05-02-2005 03:10 PM | |
| Virtual Office | esemay | Meridian Systems | 6 | 10-10-2003 04:57 PM |