![background image](http://html.mh-extra.com/html/nec/univerge-sv9100/univerge-sv9100_features-and-specifications_248323127.webp)
127
Call Appearance (CAP) Keys
Description
This feature automatically places an outside call on a Call Appearance key when the system is operated
as a hybrid (Multifunction) system. These keys can be assigned on any multiline terminal or the same
key can appear on multiple terminals. This feature allows efficient call handling when numerous CO calls
are received and a limited number of CO line key appearances are available.
Once a Call Appearance (CAP) Key call is set up, the user can handle it like any other trunk call. For
example, the user can place the call on hold, transfer it to a co-worker or send it to a park orbit. An
incoming call is answered on the first available CAP key, beginning with the lowest numbered key. If
keys 1~3 are Call Appearance (CAP) Keys, for example, the first incoming call is answered on key 1. If
key 1 is busy, the next call is answered on key 2. If keys 1 and 2 are busy, the next call is answered on
key 3. If all three keys are busy, additional incoming calls queue for the first available key.
Conditions
A trunk call that is originated or answered at a multiline terminal must appear on a line key.
The line key can be assigned as the Trunk Key, or as a Call Appearance Key. A CAP is
dynamic because it is used for any trunk call. An 8-button multiline terminal can have eight
CAP keys that allow the telephone to process all trunks, eight trunks at a time.
Multiline terminals can be assigned to the same CAP Key. Trunk calls that appear on the
same CAP Key at multiple stations have the same visual appearance of the call (Busy or
Hold).
Any held call left on a CAP key for more than the programmed time recalls to the multiline
terminal where the call was originally put on hold.
When a multiline terminal (other than the one that originally initiated or received a call) is
used to retrieve a held call, the SMDR records a transfer to the multiline terminal where the
call was retrieved.
Only outside lines use a CAP key.
A multiline terminal can have multiple CAP keys assigned to it.
Outside lines reside on the CAP key in the order of lowest to highest line key number on the
station. For instance, when line keys 1, 2 and 3 are CAP keys, the first call resides on line
key 1, the second call resides on line key 2 and third call resides on line key 3.
All Flexible Line keys on a multiline terminal can be assigned as CAP keys in System
Programming.
A conference call involving two outside lines cannot reside on one Call Appearance key.
For Call Appearance (CAP) Keys, trunks must be assigned to trunk group 1 or higher
(Program 14-05-01). Trunk Group 0 means KF (Key Function) mode.
CAP Keys can be programmed from 0001~9999. 0000 assigns the next available CAP
Key.
Trunk Group (
*
02), Virtual Extension (
*
03) and Call Appearance (CAP) Key (
*
08), codes
cannot be programmed on a DSS Console as the system does not allow entry of the
additional data required.
If you have both trunk line keys and Call Appearance (CAP) Keys, the line key has priority. An
Summary of Contents for Univerge SV9100
Page 1: ... SV9100 Features and Specifications Manual Rev 1 2 March 2016 ...
Page 64: ...64 Required Component s None ...
Page 238: ...238 Walking Code Restriction 663 ...
Page 239: ...239 Temporary Code Restriction Override service code be changed 775 ...
Page 285: ...285 Single Line Telephone 1 Lift the handset A fast busy is heard 2 Dial 759 3 Hang up ...
Page 332: ...332 Circular Routing Department Calling Circular Routing CALL 1 CALL 2 CALL 3 CALL 4 ...
Page 406: ...406 Trunk Distinctive Ringing Flow Chart ...
Page 407: ...407 ICM Distinctive Ringing Flow Chart ...
Page 442: ...442 CCIS Standard Calls ...
Page 447: ...447 CCIS VE Standard Calls ...
Page 456: ...456 CPN sent when making a 911 call across CCIS trunks from a terminal ...
Page 461: ...461 CCIS VE 911 Calls ...
Page 637: ...637 Cascade Message Notification Flow Chart 1 ...
Page 638: ...638 Cascade Message Notification Flow Chart 2 ...
Page 639: ...639 Cascade Message Notification Flow Chart 3 ...
Page 655: ...655 Cascade Message Flow Chart 1 ...
Page 808: ...808 DTI U40 ETU Programming Flowchart for ISDN PRI Answering Calls the GCD PRTA Overlap ...
Page 813: ...813 ...
Page 844: ...844 None Related Features None Guide to Feature Programming None Operation None ...
Page 915: ...915 Communications Interface feature for more ...
Page 916: ...916 ...
Page 917: ...917 Operation None ...
Page 948: ...948 Operation Normal call handling procedures for single line telephones apply ...
Page 1015: ...1015 Related Features None Guide to Feature Programming None Operation None ...
Page 1026: ...1026 Operation Refer to Central Office Calls Answering ...
Page 1030: ...1030 Multiline Room Monitoring ...
Page 1031: ...1031 Single Line Telephone Room Monitoring ...
Page 1146: ...1146 SMDR Flowchart Continued ...
Page 1147: ...1147 SMDR Flowchart Continued ...
Page 1371: ...1371 ...
Page 1400: ...1400 To answer off hook signaling 2nd call and 2nd caller disconnect the call NOTE ...
Page 1402: ...1402 SV9100 Features and Specifications Manual NEC Enterprise Solutions ...