Can some explain Cap Keys to me I understand that you need to make calls as well as recive calls - how many do you usally need and it would appear that they are for incomming only .
I also understand that they have to be unique to each phone (how do you program this and keep track of this )*08 ... .
I am just starting to work on the SV 8100 .I am certified on the Aspire and UX 5000

Thanks

JD

I would love a good explanation of CAP key too because they are stupid. I also some from the UX,Aspire i-series side as well. Trust me, I send letters monthly to NEC regarding their "choice" over the traditional UX/Aspire built in CALL (loop) keys. Please, feel free to keep greasing the wheels and let them know.


You can assign them easily through PCPro when you are programming the system. Actually you need at LEAST 2 CAP keys per phone AND and intercom key if you are not using key system functionality IMHO. So, when you quoted 12 button or 6 button phones before just know you are going to burn 3 keys for the phone to work correctly in a non-key system config.

When I was involved with the original evaluation of the SV8100 back in January 2008 NEC Japan wanted to remove CAP keys and use loop keys or nothing. The KTS people at NECAM and NEC AU jumped up and down saying it wouldn't be a keyphone system anymore and they wouldn't support the move. That was in the days wehn the PBX and KTS channels were separated Hence we are still stuck with this archaic concept. They did in the European version of the SL1100 give you the option (20.02.23) but in the AU release we get here there is no option to have either CAP or Loop keys only loop keys. Loop keys are fine if they would fix them for call supervision as on small SL1100 we have to put on trunk keys for the operator to control calls. This is the only benefit of CAP keys on the SV8100 for call supervision for the operators.

Paul can you elaborate on an example of the call supervision limitations? In the US we have Loops on the 1100 too.

Coral Tech

Can you explain why I need an Intercom Key as well

Thanks!

JD

Visual indication of held internal calls. On the UX/Aspire/i-Series these were also handled by the built in loop appearances (call keys) CAP keys will not do this as they are for external.

Using loop keys only and no trunk keys.
Call is answered by the operator. Call appears on loop key. Call is transfered to local station. Call is still visable on loop key. Call is completed as a blind transfer. Call drops off loop key and there is no way to supervise this call other than wait for it to recall..

This is how it works on our SL1100s of is there something in our programming that I'm missing??

I really don't see the difference. We have always had CAP keys on 'NEC key telephone' days(CAP came from call appearance as apposed to CAR call arrival) hence the abbreviation.

I do agree that there is a problem with held internal calls (they show on a CONF key which they removed from the DT300/700 handsets (you think NEC could have moved this to the feature key)

This is why you need an ICM key (also for the crap 'red pheonix' desktop suite)

but in saying this not many users put internal calls on hold (wouldn't you just ring them back?)

(this is how it works on AUS version anyway)

Delsar:
to say that we have always used CAP in the past doesn;t make it right.

I recommend using a i-series, Aspire, UX phone with out the CAP key or Int key.

there were 2 hard keys that would support all of that. And just because there were 2, that didn;t limit the amount of calls to 2.

Like CT said, you now have to upsell the number of buttons on a phone to accomplish the same thing that we always did.