Manager: Telephone Features
|
|
Centralized Call Log |
For IP Office 5.0+, the IP Office can store a centralized call log for users.
Each users' centralized call log can contain up to 30 call records for user calls (10 on IP412 and IP406 V2 systems). When this limit is reached, new call records replace the oldest record.
That call log is can be displayed on the phone, by pressing Call Log, when the user is using a 1608 or 1616 Series phone. The user can use the call log to make calls or to store as a personal speed dial. They can also edit the call log to remove records.
The centralized call log moves with the user if they log on and off from different phones, including if they hot desk within a Small Community Network.
Call Log Information
The following information is included in each centralized call log record:
Information |
Description |
||||||||||||
Name |
The name, of the caller or the party called, if available. Up to 31 characters. This text is similar to that shown on the phone display of 1600 Series phones. For example, on forwarded call details of the original target and the caller name are included, eg. Bob > Sue. |
||||||||||||
Number |
The number associated with the call. Up to 31 digits. |
||||||||||||
Tag |
A text tag can be associated with calls by several different methods. See Call Tagging. Up to 31 characters. The tag is not shown within the call log display on phones. |
||||||||||||
Time and Date |
The time and date of the call using the IP Office system time. |
||||||||||||
Duration |
The call duration. For outgoing and answered calls this is the call connection time. For missed calls this is the call ringing time. |
||||||||||||
Record Type |
Call log records can be Incoming, Outgoing or Missed. Note that these are calls to or from the user, not the phone, so it can include IP Office calls handled through a twinned device, mobile call control, one-X Mobile Client or Phone Manager Telecommuter mode.
|
||||||||||||
Count |
The number of times a matching call has been logged. A matching call is one with the same name, number and type. Only one record is kept for matching calls, with the count increased by 1 and using the time and date of the most recent matching call. |
If missed hunt group calls are also being logged, the IP Office stores up to 10 call records for each hunt group. When this limit is reached, new call records replace the oldest record.
Controlling Centralized Call Logging
The following controls exist for which users have their calls included in the centralized call log and which calls are included.
User Setting
The user centralized call log settings can be set through the user configuration (User | Telephony | Call Log) or through their associated user rights (User Rights | Telephony | Call Log).
| • | Centralized Call Log: Default = System Default (On) This setting allows the use of centralized call logging to be enabled or disabled on a per user basis. The default is to match the system setting Default Centralized Call Log On (System | Telephony | Call Log). The other options are On or Off for the individual user. If off is selected, the call log shown on the users phone is the local call log stored by the phone. |
System Settings (System | Telephony | Call Log)
| • | Default Centralized Call Log On: Default = On. When selected, each IP Office user is defaulted to have the IP Office store a call log of their calls. This call log will be displayed on the phone when the user is using a 1600 Series phone. The use of centralized call logging can be enabled/disabled on a per user basis using the Centralized Call Log user setting (User | Telephony | Call Log). |
| • | Logged Missed Calls Answered at Coverage: Default = Off. This setting controls how calls to a user, that are answered by a covering user should be logged in the centralized call log. This option applies for calls answered elsewhere (covered) by pickup, call coverage (call coverage buttons or coverage group), bridged appearance button, user BLF, voicemail, etc. |
Setting |
Targeted User |
Covering User |
Off (Default) |
Nothing |
Answered Call |
On |
Missed Call |
Answered Call |
| • | Log Missed Hunt Group Calls: Default = Off. By default, hunt group calls are not included in any user's centralized call log unless answered by the user. If this option is selected, a separate call log is kept for each hunt group of calls that are not answered by anyone. It includes hunt group calls that go to voicemail. |
| • | If missed hunt group calls are also being logged, the IP Office stores up to 10 call records for each hunt group. When this limit is reached, new call records replace the oldest record. |
| • | Within the user call log setting (User | Telephony | Call Log) the list of hunt groups allows selection of which hunt groups' missed call records should be displayed as part of the centralized call log when a user is using a 1608 or 1616 phone. |
Call Scenarios
This is not a comprehensive list. However it summarizes how the user call log is used in some common call scenarios.
Scenarios |
User Call Log Notes |
Authorization / Account Codes |
Account and authorization codes used as part of a call are not included in user call logs. |
Automatic Callback |
If answered, they will show as an outgoing call to the target. |
Application Calls |
Calls made and answered using IP Office applications (including CTI interfaces) are logged as if the user made or answered the call using an extension. |
Conference Calls |
Conference calls are not included in the user call log. |
Hold |
When a user holds and then un-holds a call, the call duration includes the time the call was on hold. |
Follow-Me |
Calls to the user still appear in their user call log. The follow me calls do not appear in the user call log of the user who was the follow me destination. |
Forward on Busy |
If the forwarded call is answered, the forwarding user will have a Missed - Answered by Other call log record. If the forwarded call times out to voicemail, the user will have a Missed - Answered by Voicemail call log record. |
Forward on No Answer |
|
Forward Unconditional |
When forwarding to another number, there will be no record of forwarded calls in the forwarding users call log. When using the To Voicemail option, the forwarded call will by logged as a Missed - Answered by Voicemail call record. |
Page Calls |
Page calls are not included in any user call logs unless the page is answered (by pressing Conference). When answered the page is logged as a normal call between the two users involved. |
Park |
Retrieving a call from Park (even if the user is the one who parked the call) is logged as a incoming call. |
Short Codes |
Calls are only logged if they result in a call being made or a call being answered. Calls made using Break Out are not included. |
Small Community Network |
The user's call log records are stored by the IP Office system that is their home system, ie. the one on which they are configured. When the user is logged in on another system, new call log records are sent to the user's home system, but using the time and date on the system where the user is logged in. Hunt group call log records are stored on the IP Office system on which the hunt group is configured. |
Suppressed Digits |
Calls made with digit suppression enabled (AD Suppress button) are not included in the users call log. |
Transfers |
If the user answers and accepts a supervised transfer, they will have a incoming calls records. One for the transfer enquiry call and one for the transferred call. If the user is the target of an unsupervised transfer, they will have an Incoming or Missed call log. Note that even if the call being transferred was originally an outgoing call, for the user answering the transfer it is logged as a incoming call. |
Twinning and Mobility |
When a user has a twinned device (either internal twinning or mobile twinning), the user's call log operates regardless of which device the user uses to make or answer calls. Calls between the twinned devices, ie. the user transferring a call between devices, are not included in their call log. This includes calls made using mobile call control or a one-X Mobile client. |
|
© 2009 AVAYA 15-601011 Issue 23.p.- 07:07, 30 October 2009 (centralized_call_log.htm) Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners. Last Modified: 30/06/2009 |