programming softkeys in NEAX 2000 and remote log ons 1

[mookiemoo]

Hello everyone,
I have two questions:

1. I just finished programming the soft keys for a NEAX 2000. They used to blink when you pressed the key to let you know that the key was pressed, but now the do not. How do I make them do that?

2. I don't have matworx at my job. I can connect to the modem on the switch by using hyperterminal, but I do not know how to enter any command once I connect. Do you need matworx to do remote programming or does someone know how to program by just connecting to the switch

Thanks

 

[neax]

Question 1 - I don't know the Softkeys blinked - mine don't?

Question 2 - Use Procomm or Hyperterminal in VT100 Terminal Emulation. Default, an IVS is set to 1200bps (as shown by Command 4008>0>NONE) NONE = 1200bps. If you make it a "4", the pport speed will be 9600. Make your Procomm or Hyperterminal match the baud rate (Command 4008).

Use the following key strokes:

/ (forward slash) = Command=
. (Period) = Writes the data
Enter key = Steps to the next level
, (comma)= Separator mark (used with commands 72, 74, 90, 97)
- (minus) = allows you to Back Up in a given Command
Space bar = Data Enter key

 

[neax]

One more thing....

For 2000IVS:
The Internal Modem can do speeds of 1200bps or 2400bps.
Local connection can do 1200, 2400, 4800, 9600. Default setting is 1200 and it is located on Port 1.

For IVS2 or IPS:
The Internal Modem can do speeds of 1200, 2400, 480, 9600, 19200. Default setting is 9600 and it is locatd on Port 1.

Port 0 is for local connection.

 

[mookiemoo]

Thanks for the help the remote logon works fine...

After re-reading my post, it sounds like the softkey itself blinks. I meant to say that the display above the softkey blinks. For example if one of the softkeys is programmed to mute then the display "mute" blinks when the user is on mute.

Thanks for all the help

 

[austech]

Hi, I hope I can help on the softkey question, the softkey feature doesn't blink when the feature is activated on the IVS2/IPS/2000 pbx's only on the large IMX PBX. The Dterm handsets are the same, but work slightly different. I hope I have used the correct names for the PBX's as i'm an installer from Australia and that's what we know them as. Thanx

 

[neax]

You are correct Sir. 2400 softkeys blink, 2000 don't. Not sure how the Elite treats the keys though....

 

[austech]

The softkeys in the Elite also don't blink, but I don't know about the IPK, I haven't worked on one yet as the IPK was just released in Australia last week.
Thanx

Jesse
PABX Sales and Service

 

[mookiemoo]

I have dterm series e telephones. I did the programming for the softkeys, but not all of the telephones pick it up. I put them into the same group using command 1223 and I also made sure that programming was turned on using command 1222. Any telephone that has the blinking softkey display will not take the programming, so I guess my question is: "Is all of the programming done through the PBX or can I program the telephone locally"

I am a computer guy that they decided to give the telephones too. I am a total novice.

Thanks

 

[neax]

SoftKeys can be programmed through the Phone (CAT Mode) or with MATWorX Studio or MATWorX IPS. I highly recommend using MAT WorX when making the SoftKeys.

Command 1222 is set to "0" at default allowing softkey functionality. Command 1223 allows you to set a Dterm to the desired Pattern (0,1,2,3). Tipically, all phones are set to reference the same pattern, but it's up to you. Pattern 3 cannot be changed, leaving you Patterns 0,1,2 to change as you see fit.

The programming for this is very tricky. If you use the phone to program, it's all done in Command 9A

If you know what softkeys you want based on the state of the phone (Idle, On a trunk call, During dialing, etc) I can give you some suggestions.

I used 9A00 because I'm using Pattern 0. The "00" represents Pattern 0 and the "10" in 9A10 represents the name programming for pattern 0 (example - MIC for microphone is, per HEX assignment, 4D4943). 9A00 & 9A10 go hand in hand. Command 77 in the Command manual has a chart that tells you what character is what in HEX.

You program the key assignment then you MUST program a name for it. If you only program the key but not the name, the LCD for that key will be blank but it will have functionality if pressed. This is why I recommend using MATWorX for all SoftKey programming.

Below is what I have for all my Dterms (Command 1223=0 (using pattern 0) and Command 1222=0)

Idle state
9A00-0000-F1017 9A10-0000-4D4943(MIC)
9A00-0001-F5014 9A10-0001-535953(SYS)
9A00-0002-F5010 9A10-0002-434944(CID)

During Dialing - (Holding no call)
9A00-0100-F1017 9A10-0100-4D4943(MIC)
9A00-0101-F1014 9A10-0101-535953(SYS)
9A00-0102-F5010 9A10-0102-434944(CID)
9A00-0103-F0010 9A10-0103-464341(FDA)

During Speaking (Holding no call)
9A00-1000-F1017 9A10-1000-4D4943(MIC)
9A00-1001-F1091 9A10-1001-524543(REC)
9A00-1002-F5010 9A10-1002-434944(CID)

The MIC and CID are in several softkey states so I can kill the Microphone if I want, CID (Caller ID) is to display and re-display the Call ID info. SYS is System Speed dial, FDA is Forward All, REC is Live Record to AD-8 Voice Mail.

I'm only concerned with three of the 15 or so states a Dterm can be in. But, you can make it any way you want.

Good luck....

 

[OMBD]

Hey Neax,

Excellent tip for soft keys. We usually throw in a headset key too on the soft keys to save a button later on but you then have to have a release key for your other active states. We also use the CID key but I do like the Record key, Thanks.

Jerry Pannell

http://www.SCLB.com

techs@sclb.com