Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

32 Button Series i Phone 1

Status
Not open for further replies.

wayne50

Technical User
Jan 28, 2004
147
Hello, I have a nec 2000ivs2 switch that I am trying to program a 32 button series i phone,can this be done.Thanks
 
Set command 1224 >ext>0 ececute. Then unplug the phone and plug back in.
 
Thanks for all the help,my problem after doing the change is my key data will not stay after I assign each location.When I check it my prime line is on button 8 not 24 and other numbers are not where they were programmed for.Thanks
 
This may be a silly question but are you in fact programming the right extension. Just because a phone has a number as it's prime line doesn't mean it is actually that number. For example you can program up an extension F300 but then put another extension (say 301) on it as a line appearance in the same place as you would normally put the prime line, then make it the prime line in Cmd 93. This will then confuse the heck out of anyone who comes to program it later as they would be trying to program 301 when in actual fact they should be programming 300. I have used this trick on occasion when someone wanted a cordless and a dterm you give them a dterm and an analogue cordless then make the analogue the prime of the dterm. What you could have here is one dterm appearing on another dterm.
 
Wayne

when you say the key data will not stay do you mean the keys are not the way you programmed them or the data shown when you step through Cmd 9000 is wrong? Or are you using the matworks feature to program this?
 
The keys that I program,button 1 thru 24 do not show up the way I programed them in cmd 9000.We use 8,16,and 32 button nec series e phones but we are getting a few series i phones to see if they hold up better,we have found that they do so far and our cost is a little lower. Also we use a 2000ivs2 switch not a 2000isp.We use matworx studio moc mode for most of our programming,we are getting good results and enjoy using it.Thanks for any and all help,this is a great place to get wonderful info.I have found so many fixes here.Thanks
 
So if you change the data for say key 01 which key if any on the phone changes?
 
IT SHOWS UP ON ANOTHER BUTTON OTHER THAN THE ONE I PROGRAMMED IT TO.
 
Sorry to be pedantic but if you change key one, which key appears to change. Sorry if this seems so basic but this seems quite unusual and I am just trying to understand what is happening. If anyone else can help I'll shut up I'll Even shut up if you say so. No need to shout by the way.
 
Sorry about the upper case,was not paying attention.We have alot of crazy things happen here but we seem to get them worked out sooner or later. The ext. numbers I program for certain buttons do not show up on the proper button locations on the phone I assign them too. ?
 
You don’t seem to want to answer specific questions so I can only offer general advice.
Key data is one of the hardest things to get back to default. You can delete an extension, do multiple resets, leave it a year or all of the above and when you next put a dterm on that port the old data will reappear. I have even had old key data cause a problem with an analogue extension when a card was fitted to a slot that had previously been used for dterms
Try CCCing everything out in both 90xx and 12xx, then delete the extension then reset the system (making sure you have backed it up first to be on the safe side) then try assigning it again. If this doesn’t work move to a new card slot and try again. If you haven’t got a spare card slot swap it with a different card type. A pain I know, the easiest to swap with would be the register card (8RSTA)
I have assumed you tried swapping the handset with a known good one first and that the fault stayed with the len position
 
Wayne,

This is a known issue with the IVS2 and Series I phones.
The button map is below. Look at this as you would 1 - 8 9 - 16 and so on.

[1] [2] [3] [4] [7] [8] [9] [10]
[13] [14] [15] [16] [19] [20] [21] [22]
[5] [11] [17] [23]
[6] [12] [18] [24]

Ozzie - get a grip!
 
Thanks for all the info guys.
 
Yes this is a known problem that NTAC never issued a fix for. It only effects dtr-32d phones. You will need to leave the phones set in 16 button mode or use the button map that mextera gave you. I presume that is correct. I have never put a series I 32d on an IVS2 in 24 button mode.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top