Panasonic Kx Ta824 Feature Guide

							1.14 Optional Device Features
Feature Guide 101
Conditions
Hardware Requirement: An optional voice message card.
 The optional voice message card has 2 voice message resources (BV resource 1 and BV resource 2), 
and every extension must belong to one of these resources based on system programming (
 BV 
Resource [621]). When an extension that belongs to either resource is reassigned to the other 
resource, the voice messages that were recorded prior to reassignment are erased, but the personal/
common OGMs are not erased.
 Each resource can only be accessed by one extension at a time. When the resource an extension is 
assigned to is being used by another extension, the extension cannot use that resource, even if the 
other resource is available.
 The optional voice message card functions differently from an OGM card used by the DISA and 3-level 
Automated Attendant (AA) features (
 1.14.5 Outgoing Message (OGM)).
 The PBX can record a maximum of 128 voice messages per resource. The maximum recording time 
of each voice message (
 BV Recording Time [214]) and the total recording time of the PBX ( BV 
Total Recording Time [807]) are programmable. The maximum recording time of each personal/
common OGM ( Common/Personal OGM Recording Time [215]) is also programmable.
 System programming determines the extension users that can use this feature ( BV for Extension 
[622]).
 If a voice message channel (resource) is in use when an outside caller tries to leave a voice message, 
he or she will hear a ringback tone. The caller will hear an OGM as soon as a channel becomes 
available. Up to 8 outside (CO) line calls can be placed in a queue as they arrive.
 If a user performs System Data Clear through system programming ( System Data Clear [999]), all 
voice messages except for personal/common OGMs are erased. To erase all voice messages and 
personal/common OGMs at once, initialize the voice message card through system programming (
 
BV Card Initialization [808]). 
 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.
 When the remaining recording time for the PBX is less than 5 minutes, the display informs both the 
extension users within the same resource and the manager that the voice message resource is full, and 
the users will hear a special dial tone (dial tone 5) when going off-hook. If the remaining recording time 
goes back to being 5 minutes or more, for example, when messages are erased, the display returns to 
the idle status display and the users will hear a normal dial tone (dial tone 1) instead of dial tone 5 when 
going off-hook.
 If Call Forwarding (FWD) is enabled for an extension whose FWD destination is a BV ( Call 
Forwarding Selection [963]), outside (CO) line calls to the extension will not be forwarded and the 
extension will not ring, even if the user has set the FWD feature. If FWD is disabled, outside (CO) line 
calls to the extension will not be forwarded and the extension will ring.
 Only the operator or the manager can access the common message area (including common OGM). 
The operator has higher priority than the manager as follows:
– When the operator extension is reassigned, the common BVs (except for the personal OGM of the 
operator) that were recorded prior to reassignment are erased. The new operator can record, play 
back, and erase the common OGM.
– When the operator, who does not share an extension number with the manager, is newly assigned, 
the common BVs (except for the personal OGM of the manager) that were recorded prior to 
reassignment are erased. The operator can record, play back, and erase the common OGM.
– When the operator, who does not share an extension number with the manager, is deleted, the 
common BVs (except for the personal OGM of the operator) that were recorded prior to 
reassignment are erased. In this case, the manager can record, play back, and erase the common 
OGM. 
						

							1.14 Optional Device Features
102 Feature Guide
 A voice message area cannot be included as a member of a conference call.
Installation Manual References
2.3.8 2-Channel Voice Message Card (KX-TE82492)
Feature Guide References
1.14.6 Direct Inward System Access (DISA)
4.2.1 Tones/Ring Tones
User Manual References
1.5.5 Using Voice Messaging (Built-in Voice Message [BV]) 
						

							1.15 Caller ID Features
Feature Guide 103
1.15 Caller ID Features
1.15.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 callers 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 companys Caller ID service 
and enable Caller ID for the appropriate outside (CO) lines through system programming (
 Caller 
ID [900]).
 
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
2.Automatic Caller ID Number Modification 
When Caller ID information is checked, the PBX can automatically modify the callers 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. 
FeatureDescriptionDetails in
Incoming Call LogCaller 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.15.2 Incoming 
Call Log 
						

							1.15 Caller ID Features
104 Feature Guide
 
[Programming Example: Caller ID Modification Table]

Call TypeCode No.Area Code*1Removed No. of 
DigitsAdded No.
Local Call*2 12123Not Stored
20113001
::::
5
Long-distance Call*3[Not programmable]01
*1 Caller ID Area Code [901] 
*2 Caller ID Modification for Local Calls [902]
*3 Caller ID Modification for Long-distance Calls [903] 
An outside (CO) line call containing
Caller ID information is received.
Yes NoIs the callers area code stored in 
the Caller ID Modification Table?
Modifies the number according to the 
method programmed in the corresponding 
Local Call field.
Example:
Removed number of digits: 3
Added number: blank
Example:
Received number:
Modified number:201 555 1234
       555 1234
Modification is complete.
Modified number is logged.Modification is complete.
Modified number is logged.
Modifies the number according to the 
method programmed in the Long-distance 
Call field.
Example:
Removed number of digits: 0
Added number: 1
Example:
Received number:
Modified number:313 555 1234
  1  313 555 1234 
						

							1.15 Caller ID Features
Feature Guide 105
3.Displaying the Callers Name 
When a call containing Caller ID information is received, the PBX will search for the callers name in the 
following order, then show that name on the display.
1)The System Speed Dialing Table
2)The Caller ID information received from the telephone company
If a callers 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 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 signaling type can be selected through system programming ( SLT Caller ID Signaling 
Type [150]).
 Each SLT (including an SLT connected in parallel with a PT) can be programmed to receive Caller ID 
information through system programming (
 SLT Caller ID [628]).
 When the callers telephone number is sent to an SLT, an Outside (CO) Line Access number can be 
automatically added to the telephone number through system programming (
 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 callers 
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 callers 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 callers telephone number 
exceeds 20 digits, the SLT receives only the first 20 digits. If the callers name exceeds 16 characters, 
the SLT receives only the first 16 characters. 
 When DTMF-type Caller ID information is received, the callers telephone number (max. 16 digits) or 
the reason for nondisplay of Caller ID information will be shown on the SLT. If the callers 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 (
 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 calls 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 (
 SLT Ring Wait Time for New Call [627]) before it starts to ring, 
and the new callers Caller ID information will be shown on the SLT. A received call can be answered 
even if it is not yet ringing, but Caller ID information will not 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 ( SLT Fixed 
Bell Pattern [629]) as used by the telephone company.  
						

							1.15 Caller ID Features
106 Feature Guide
 This feature will not function when the SLT uses the call waiting tone supplied by the telephone 
company (Call Waiting Caller ID).
Installation Manual References
2.3.5 3-Por t Caller ID Card (KX-TE82493)
Feature Guide References
1.6.1.5 Speed Dialing—Personal/System
1.19.1 Station Message Detail Recording (SMDR)
4.2.1 Tones/Ring Tones 
						

							1.15 Caller ID Features
Feature Guide 107
1.15.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 callers 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 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 callers 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 ( 1.14.7 Built-in Voice Message 
(BV))
 
[Example]
Conditions
Caller ID Indication—Personal/Common button 
A flexible CO button can be customized as a Caller ID Indication—Personal/Common button, and will 
indicate the status of the Incoming Call Log for the extension, as shown below.
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 call 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. 
Light patternStatus of the corresponding call log
Red onThere are new call records since the last time the call log was viewed.
OffThere are no new call records in the call log, or the call log has been 
already viewed.
Personal
Common
Caller ID Indication buttons
May15 10:00AM   --- Date and time of call
John White
--- Callers name 
123456789
--- Callers number 
Personal
Common
Caller ID Selection buttons
New:002 Old:001--- Status 
						

							1.15 Caller ID Features
108 Feature Guide
Caller ID Selection—Personal/Common button 
A flexible CO button can be customized as a Caller ID Selection—Personal/Common button, and will 
indicate the status of call records, as shown below.
The Caller ID Selection—Personal/Common button is also 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 ( Common 
Area Call Log Check [909]). If this program 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 ( 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.  
It is possible for an extension user to select whether the oldest call in the personal 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 feature number. 
 
It is possible for the operator or manager to select whether the oldest call in the common area will be 
replaced each time a call is received, or whether the new call information will be discarded, by entering 
the 301st Incoming Call Logged in the Common Area feature number.
 If a transferred call (unscreened) is not answered, the information is logged in the personal area of the 
final destination.
 When a caller leaves a voice message, it is automatically linked to the Caller ID information. Up to 128 
voice messages with a total recording time of 60 minutes can be logged per BV resource. Each BV 
resource shares the total space of personal/common message areas. For example, in BV resource 1, 
if the common message area currently has 10 messages, totaling 10 minutes, the personal and 
common message areas can jointly store up to 118 messages or 50 minutes.
 Regardless of the telephone type being used, the recorded voice message is associated with the 
callers 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 (
 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. 
DisplayStatus of the corresponding call log
NewThere are unanswered call records that have not previously been 
viewed, answered call records that were logged using the Caller ID 
Indication—Personal/Common button during a conversation, or call 
records with associated voice messages that have not been played 
back yet.
OldThere are unanswered call records that have previously been viewed, 
records of calls that were answered (if set to log automatically), or call 
records with associated voice messages that have previously been 
played back. 
						

							1.15 Caller ID Features
Feature Guide 109
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 (
 Caller ID Log Priority [904]).
 While a user is viewing his or her extensions 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 users extension, the Message/Ringer Lamp or 
the MESSAGE button light that displays notifications from the Message Waiting feature (
 1.16.1 
Message Waiting) turns off while the user is viewing his or her extensions 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 callers information is erased from the extensions Incoming Call Log simultaneously.
 If a caller does not leave a voice message, for example, by going on-hook while hearing an 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 the personal message area, or can 
transfer the call to the personal message area using the Direct Message feature of BV. In this case, the 
information of the extension or outside party that recorded the message (not the extension that 
transferred the call) is logged in the corresponding Incoming Call Log (common or personal area). 
Feature Guide References
1.15.1 Caller ID
1.17.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) 
						

							1.16 Message Features
110 Feature Guide
1.16 Message Features
1.16.1 Message Waiting
Description
When an extension user calls another extension user who does not answer the call, he or she can leave a 
message waiting indication. The appropriate button or lamp on the called extension users telephone will 
light, indicating that a call was missed, or a message recorded by the Voice Processing System (VPS) or 
Built-in Voice Message (BV) feature is waiting. A MESSAGE button can be used to call the caller back or 
listen to the message. 
 
When a message is left for a proprietary telephone (PT), the MESSAGE button on it lights, or the Message/
Ringer Lamp turns red. Pressing the lit MESSAGE button while on-hook shows the callers information as 
shown below:
 
[Example]
Conditions
 System programming determines the single line telephones (SLTs) that can receive the message 
waiting notifications left by another extension (
 SLT Message Waiting [619]). 
 If a user goes off-hook with an SLT that has messages waiting, a special dial tone (dial tone 3) will be 
heard. The user can call a caller back or listen to the message by entering the Message Waiting Answer 
feature number.
Message for another extension Button 
A flexible CO/Direct Station Selection (DSS) button can be customized as a Message for another 
extension button. This button can be used on a PT that is allowed through system programming (
 
Message Waiting for Another Extension [618]) to access messages left for another extension.
Message Waiting for Another Extension Lock 
An extension user can lock or unlock message waiting indications to prevent others from viewing, 
calling back or clearing message waiting indications left at his or her extension. The operator and 
manager can override this lock to unlock it (Extension Lock—CANCEL ALL). 
 
Even while this lock is on, the user can view, call back, or clear message waiting indications left at his 
or her own extension.
 Both the calling extension and the called extension can cancel a notification after it has been left.
 Message waiting indications are always left on the originally called extension. Message waiting 
indications cannot be sent to an FWD destination (
 1.3.1.2 Call Forwarding (FWD)) or an idle 
extension hunting destination ( 1.2.1 Idle Extension Hunting).
*This button is useful when, for example, the manager checks messages left for another 
extension.
--- Extension no. and name of the person who left the message
This extension
Message/Message for another 
extension buttons
Other extension*
105:Tom Smith