1.16 Caller ID Features

1.16.1 Caller ID

Description

The PBX can receive Caller ID information (telephone numbers and callers' names) from calls received on outside (CO) lines. This information can be shown on the displays of proprietary telephones (PTs) as well as some single line telephones (SLTs) when receiving calls. Additionally, Caller ID information is logged in the Incoming Call Log of the extension that received the call, allowing the caller to view a record of incoming calls or make a call to a person in the call log later.
The PBX can be programmed to modify a caller's telephone number when it is received by, for example, adding an Outside (CO) Line Access number or adding/deleting certain digits of incoming telephone numbers automatically. This allows an extension user to make a call later to a telephone number logged in his or her call log without worrying about Outside (CO) Line Access numbers, area codes, etc.
Notes
• The term "Caller ID" used in this Feature Guide refers to features that can receive caller information sent from the telephone company and received on outside (CO) lines. Your network provider may use a different name for this type of service.
• To receive Caller ID information, you must subscribe to the telephone company's Caller ID service and enable Caller ID for the appropriate outside (CO) lines through system programming (rarrow.gif Caller ID [900]).
• Caller ID signalling type, FSK (Bell 202 or V.23) or DTMF, can be selected to match the type used by your telephone company through system programming (rarrow.gif Caller ID Type [910]).

Caller ID Display on SLT
This feature is available only for SLTs compatible with either FSK-type Caller ID or DTMF (Dual Tone Multi-Frequency)-type Caller ID.
Notes
• This feature complies with ETSI (European Telecommunications Standards Institute)-type FSK and Bellcore-type FSK.
• This feature does not comply with methods using DT-AS signal or line reversal signal.
1. Caller ID-Related Feature

Feature

Description

Details in

Incoming Call Log
Caller ID information is automatically recorded in the call log of the extension that received the call. This information can be used to view a record of incoming calls or make calls to any number in the call log.
• 1.16.2 Incoming Call Log
2. Caller ID Automatic 0 Addition
When a call containing Caller ID information is received, the PBX can add "0" to the caller's telephone number as a leading number if it does not begin with "0", through system programming (rarrow.gif Caller ID Automatic 0 Addition [905]).
3. Automatic Caller ID Number Modification
When Caller ID information is checked, the PBX can automatically modify the caller's telephone number according to a preprogrammed set of rules (Caller ID Modification Table). This modified number allows the extension user to make a call to this number later without worrying about Outside (CO) Line Access numbers, area codes, etc.

[Programming Example: Caller ID Modification Table]

Call Type

Code No.

Area Code*1

Removed No. of Digits

Added No.

Local Call*2
1
212
3
Not Stored
2
011
3
001
:
:
:
:
5
Long-distance Call*3
[Not programmable]
0
1
*1
rarrow.gif Caller ID Area Code [901]
*2
rarrow.gif Caller ID Modification for Local Calls [902]
*3
rarrow.gif Caller ID Modification for Long-distance Calls [903]
<Modification Flowchart>
imf1229a.gif
4. Displaying the Caller's Name
When a call containing Caller ID information is received, the PBX will search for the caller's name in the following order, then show that name on the display.
1) The System Speed Dialling Table
2) The Caller ID information received from the telephone company
If a caller's name is not stored in the PBX or sent from the telephone company, it will not be displayed.

Conditions

[General]

• Hardware Requirement: An optional Caller ID card.

[Caller ID Display on SLT]

• Caller ID Display on SLT feature applies to:
Intercom calls and outside (CO) line calls.
Intercom calls include forwarded calls, calls from Transfer Recall and Hold Recall.
Outside (CO) line calls include calls directed to Uniform Call Distribution (UCD) or Direct Inward System Access (DISA) ring groups, forwarded calls, intercepted calls, or calls from extensions that placed outside (CO) line calls on consultation hold.
• SLT Caller ID signalling type can be selected through system programming (rarrow.gif SLT Caller ID Signalling Type [150]).
• Each SLT (including an SLT connected in parallel with a PT) can be programmed to receive Caller ID information through system programming (rarrow.gif SLT Caller ID [628]).
• When the caller's telephone number is sent to an SLT, an Outside (CO) Line Access number can be automatically added to the telephone number through system programming (rarrow.gif SLT Caller ID Line Access Number [151]), to be used when calling the caller back.
• If a call is transferred, forwarded, or intercepted via Intercept Routing to an SLT, the original caller's information will be shown on the SLT.
• During a conversation, Caller ID information will not be shown on the SLT.
• When FSK-type Caller ID information is received, the caller's telephone number (max. 20 digits), name (max. 16 characters), date and time, or the reason for nondisplay of Caller ID information such as "Private", "Out of Area", or "Long Distance" will be shown on the SLT. If the caller's telephone number exceeds 20 digits, the SLT receives only the first 20 digits. If the caller's name exceeds 16 characters, the SLT receives only the first 16 characters.
• When DTMF-type Caller ID information is received, the caller's telephone number (max. 16 digits) or the reason for nondisplay of Caller ID information will be shown on the SLT. If the caller's telephone number exceeds 16 digits, the SLT receives only the first 16 digits. However, when a value less than "1500 ms" is set through system programming (rarrow.gif SLT Ring Bell-on Time [143]), the SLT receives only the first 10 digits.
• Depending on the type of SLT being used, caller names and the dates and times that calls were received may not be able to be shown on the SLT.
• If an outside caller disconnects a call to an SLT on which the call's Caller ID information is displayed, and the SLT receives another outside (CO) line call directly after, the SLT will wait until a preprogrammed time has passed (rarrow.gif SLT Ring Wait Time for New Call [627]) before it starts to ring, and the new caller's Caller ID information will be shown on the SLT. A certain amount of time may be required between calls for an SLT to receive Caller ID information correctly.
• To enable the Caller ID feature, it may be necessary to set the same ring tone pattern (rarrow.gif SLT Fixed Bell Pattern [629]) as used by the telephone company.
• When an SLT is programmed to receive Caller ID information, the ringing of calls with Caller ID on that SLT is delayed for a few seconds. Therefore, the length of time before calls are forwarded or intercepted, and the length of time that intercepted calls ring at the destination SLT, may be slightly shorter than the duration specified through system programming.

Installation Manual References

• 2.3.5 3-Port Caller ID Card (KX-TE82493)

Feature Guide References

• 1.6.1.5 Speed Dialling—Personal/System
• 1.20.1 Station Message Detail Recording (SMDR)
• 4.2.1 Tones/Ring Tones

1.16.2 Incoming Call Log

Description

When a call containing Caller ID information is received by an extension, the information is shown on the telephone display, notifying the extension user of the caller's identity.
This information is also automatically logged in the Incoming Call Log of the extension, and can be viewed later or used to call that caller back.
There are 2 types of call log areas available in the PBX. One is the personal area, which stores logs of calls received by each extension when a call arrives at a certain proprietary telephone (PT).
The other is the common area, which stores a log of calls arriving at multiple PTs or via the Direct Inward System Access (DISA) Intercept Routing feature. Caller ID information can be logged by the following methods:
• Logged automatically when no one answers calls.
• Logged automatically if an extension user presets logging of the caller's information when answering calls.
• Logged manually by pressing the Caller ID Indication button during a conversation.
• Logged automatically when a caller leaves a voice message (rarrow.gif 1.15.7 Built-in Voice Message (BV))

[Example]
imf1238a.gif

Conditions

• Caller ID Indication—Personal/Common Button
A flexible CO button can be customised as a Caller ID Indication—Personal/Common button, and will indicate the status of the Incoming Call Log for the extension, as shown below.

Light pattern

Status of the corresponding call log

Red on
There are new call records since the last time the call log was viewed.
Off
There are no new call records in the call log, or the call log has been already viewed.
The Caller ID Indication—Personal/Common button will alert an extension user to any missed (unanswered) calls.
The Caller ID Indication—Personal/Common button is also used to store the information of an incoming call during a conversation, and to view caller information while on-hook and then call back a caller.
If a Caller ID Indication—Common button is not assigned to any PT, the calls will be logged in the personal area of the PT that is connected to the lowest-numbered jack, and its Caller ID Indication—Personal button light will turn red.
• Caller ID Selection—Personal/Common Button
A flexible CO button can be customised as a Caller ID Selection—Personal/Common button. The Caller ID Selection—Personal/Common button is used to display the number of logged calls while on-hook, to display and cycle through the information of an incoming call during a conversation, while receiving a call, or while viewing caller information, and to inform an extension user that the personal or common area call log is full. The user may also change the displayed information by pressing the "#" key instead of the Caller ID Selection—Personal/Common button while receiving a call, or while viewing caller information.
• It is programmable whether the user can view call logs stored in the common area or not (rarrow.gif Common Area Call Log Check [909]). If this programme is enabled, the Caller ID Indication—Common button and Caller ID Selection—Common button can be assigned.
• Incoming Call Log Memory
The total number of incoming calls that can be logged by the PBX is limited (rarrow.gif 4.1.1 Capacity of System Resources). When a call log is full (personal area: 20 calls, common area: 300 calls), the Caller ID Selection—Personal/Common button light will turn red. When a caller leaves a voice message, it is automatically linked to the Caller ID information in the Incoming Call Log. Up to 125 voice messages per BV resource are stored separately from the Incoming Call Logs mentioned above.
It is possible for an extension user (or the operator/manager) to select whether the oldest call in the personal area (or common area) will be replaced each time a call is received, or whether the new call information will be discarded, by entering the 21st Incoming Call Logged in the Personal Area (or 301st Incoming Call Logged in the Common Area) feature number.
Caller records for all call logs of an extension are numbered sequentially as they are received, regardless of which call log the information is stored in. For example, information on the first call received will be stored as record "001" (e.g., 001, logged in the personal area) and information on the second call received will be stored as record "002" (e.g., 002, logged in the common area), whether it is logged in the personal area, common area, or BV.
If the call log in the personal area becomes full when the 21st call (e.g., 110, logged in the personal area) has been set to overwrite the oldest call (001, logged in the personal area),
– The oldest call will be deleted and subsequent records will be moved one number down, if the 21st call is unanswered or if it is answered but has different information from the 20th call.
– The 21st call will be discarded and the previous call information will stay as it is, if the 21st call is answered and has the same information as the 20th call.
Common area call logs function in the same way.
• If a transferred call (unscreened) is not answered, the information is logged in the personal area of the final destination.
• Regardless of the telephone type being used, the recorded voice message is associated with the caller's information.
• Even if no flexible CO button is assigned as a Caller ID Indication—Personal button or a Caller ID Indication—Common button, a caller can leave a voice message in that personal/common message area and the Caller ID information, including associated voice messages will be logged.
• Incoming Call Log Display Lock
An extension user can lock the Incoming Call Log (including associated voice messages) stored in his or her personal area, preventing other users from viewing its contents (rarrow.gif 1.8.3 Extension Lock). The operator or manager can cancel the lock in the case that the extension user forgets the lock code.
The Incoming Call Log for the common area can only be locked or unlocked by the operator and manager.
• Automatic Caller ID Number Modification
If the PBX is programmed to automatically modify incoming telephone numbers, the modified numbers will be displayed when Caller ID information is checked. Extension users can also modify the incoming telephone numbers manually.
• Initial Display Selection
If the Caller ID service provides both the number and name, the user can select which is shown first on the display of the PT through system programming (rarrow.gif Caller ID Log Priority [904]).
• While a user is viewing his or her extension's Incoming Call Log, if the caller whose information is being viewed also left a voice message, the Message/Ringer Lamp or the MESSAGE button light will turn on. The associated voice messages in that personal/common message area can be played or erased with the MESSAGE button or the TRANSFER button respectively.
• Even if there are message waiting indications left at a user's extension, the Message/Ringer Lamp or the MESSAGE button light that displays notifications from the Message Waiting feature (rarrow.gif 1.17.1 Message Waiting) turns off while the user is viewing his or her extension's Incoming Call Log with the Caller ID Indication—Personal/Common button.
• If a user erases voice messages by any method (for example, by using BV or performing System Data Clear), the caller's information is erased from the extension's Incoming Call Log simultaneously.
• Even if a caller does not leave a voice message, for example, by going on-hook while hearing a personal/common BV outgoing message (OGM), the information is logged in the corresponding Incoming Call Log (common or personal area).
• During a conversation with an extension or outside party, an extension user can transfer the call to another extension that has set incoming calls to be forwarded to that extension's personal message area, or can transfer the call to the personal message area using the Direct Message feature of BV. If the transferring user performs Call Transfer with Announcement, there is a chance that both parties may be recorded in the same message. In this case, the information of the last extension or outside party that recorded the message is logged in the corresponding Incoming Call Log (personal area).

Feature Guide References

• 1.16.1 Caller ID
• 1.18.2 Flexible Buttons

User Manual References

• 1.9.1 Calling with the Incoming Call Log
• 2.1.4 Erasing All Caller Information in the Common Area (Incoming Call Log in the Common Area—CLEAR ALL)
• 2.1.5 Disregarding the Newest Call or Overwriting the Oldest Call in the Common Area Call Log (301st Incoming Call Logged in the Common Area)

For New Zealand, "0" can be added to the received telephone number when the maximum length of a telephone number is 8 or 9 digits, and "00" can be added to the received telephone number when the maximum length is 10 digits or more.