Expert Mode Changing Line Keys 2

[nick1977]

Does anyone know how to change the line keys for a station on an optipoint 500? For example I have a rollover line that goes to 2135. I would like to make that a line key that points to 5252. If anyone has any guidance, it would be appreciated.

Nick

 

[Iamnothere]

You should be able to use this AMO to see the current Key System Configuration:

DIS-KCSU:<station number>;

To change the config, use CHA-KCSU

But What comes next relies on whether you are changing the Primary Line or a Secondary Line appearance.
I think you'll be able to figure it out once you see it.

One suggestion: perform EXE-UPDAT:BP,ALL; twice before and ONLY before you begin to experiment.
That way, if you make a horrible mistake, the SWU database can be reloaded minus the critical mistakes.

 

[nick1977]

Any pointers on this message:

CHA-KCSU:5135,SEC,10,4935,YES,NO,DI,NO,,,SLKNAME;
H500: AMO KCSU STARTED
F22: KYNO 10 IS NOT ASSIGNED TO A STNOSEC.

4935 is the primary line for my coworker.

Thanks
Nick

 

[Iamnothere]

What are you trying to do? Your AMO command tells me that you have selected the phone with Prime Line = 5135, and you are trying to REVISE the configuration of the Secondary Line "4935" which is currently button # 10 on that same phone. The message is trying to advise you that "4935" is not already configured on that Line Key.

If you are trying to ADD that station "4935" to the phone with Prime Line "5135", then you would perform ADD-KCSU.
This type of configuration requires some previous knowledge and skill, as the Line Key must first exist in AMO TAPRO.

If you are using ComWin/Expert Access to perform these AMO commands, I suggest that you use the Com-Edit function. This function can be "called" by pressing CTRL + TAB keys.
When the ComWin-Edit window appears, select AMO KCSU in the "Command" field, then use your mouse and click the GREEN "Command" Link. Here you will see handy information about how to use AMO KCSU.
If the information is in German, click "Options -> Settings", then change the Language to English, and try again.

 

[nick1977]

Yes, I am trying to add 4935 as a line key on kyno 10. I am currently unable to add key layouts through the gui until we can get a service call placed; in the meantime I am braving expert mode. :]. So amo tapro is where I actually can define different line keys on standard layouts. Currently most of our phones use layout 63.

Best Regards,
Nick

 

[nick1977]

Got it Thank you for the Tapro hint

Nick

 

[donb01]

Don't modify template 63 though unless you want to make that change to all of the phones currently on template 63.

It won't happen immediately, but what you will have done in essence is make all current phones that were assigned to template 63 "ba$tard children" as their station record will say they are in that faceplate, but the actual phone layout will not match it anymore (it used to be called "custom buttons"), and when I went through training they were generally frowned upon.

The better solution would be to find an empty 12-button table and set it up the way you want it for your new type of phone - maybe all the buttons will be the same but it has 2 line keys. Then assign that to the phone that needs to have the second line with cha-tapro. Now you can assign the line per the above instructions without affecting any other phones, and you will have a button table saved in case you want to assign it to more phones later.

 

[nick1977]

Let me make sure I understand, I used cha-tapro to add line keys to a specific station. It asks what key layout is being used. I entered 63, and then went through the keynos and edited that specific station. After I said 9-12 were LINE layout, I then used add-kcsu to add the appropriate lines I wanted. Is this incorrect?

Thanks,
Nick

 

[sbcsu]

If you are using a lot of phones with the same key layout you normally create a separate TAPRO for them.

Also if you are using for example 12 button phones you could create TAPRO 12 for them but that is just to make it easier to remember.

You can change TAPRO for individual phones and when you do that DO NOT specify the Keymap layout for that phone as you will end up changing the keymap for all phones that have that keymap.

DIS-TAPRO:STN;

will give you the key layout for all phones.

 

[nick1977]

5045 | 63 | OPTISET | |
| | | | |


5071 | 63 | OPTISET | 1 MB 2 MBLINE |
| | | | 7 DND 10 DSS |
| | | | 11 DSS |
| | | |

5135 | 63 | OPTISET | 2 MBLINE |
| | | | |

5135 was the station I was attempting to change.
9,10,11,12 were defined as LINES.

I do not see any changes to 63, other than what was intended at this point. I am on v4 if that makes a difference. I will yank the backup MO drive tonight.

Thank you all for the warning.
Best Regards,
Nick

 

[sbcsu]

Just to clarify:

You setup the TAPRO key standards initially.
Then these are used as 'standard' layouts.

You 'move' the phone into that TAPRO.

You can change the phone's individual key layout and it will remain in that TAPRO but when you display it, it will show the differences.
Easiest way if you are just changing a few phones is to change their OWN keylayout by CHA-TAPRO:STNO=5701,KEY01=MB;

However if you change the TAPRO Standard by CHA-TAPRO:STD=63,KEY01=MB;
then all the phones in that standard WILL KEEP THEIR ORIGINAL LAYOUT and will show the different KEY01
but if you add a new phone and put it into STD 63 it will have KEY01=MB

Hope that helps, not easy to explain !
Play around with a vacant TAPRO and a spare phone.

 

[nick1977]

Thank you for the warning and explanation. It is making much more sense now. Key 11 which is one I changed would have been a line key, so there should be no adverse effects. Key 9 may have been a MUTE key on some phones.

If I do a DIS-TAPRO:STN; as suggested above and sort all of the key layout 63's I should be able to tell what the original KEY09 is. If it was a mute key I would use cha-tapro on key layout 63 and change it back to a mute key before any phones get added?

So key point, don't enter the key layout number when making button changes to the phones.

====================================================================================================================
I have compared it to an unaltered keylayout 63 and changed tapro back to match. Thank you all for causing me a lot less hassle and frustration in the future. I appreciate the guidance, and hopefully, in the next couple weeks we have have a company that specializes in the Hipath to manage the PBX. In the meantime, thank you for answering all of my questions.

Best Regards,
Nick

 

[sbcsu]

No problem Nick, glad you got it sorted.
It's an easy one to mess up !

Not sure if you use it already but you could try using ComWin Edit

Log On
Click on 'macro' and 'retrieve system variant'

Then click in the input area, either on a blank area or on an AMO then CTRL + TAB will bring up the comwin edit box.