0% found this document useful (0 votes)
48 views15 pages

Call History

The document discusses call history features that record incoming calls with caller ID or ANI information into a rolling list for each station. It describes how call information is stored for different call scenarios like answered, abandoned, transferred or forwarded calls. The summary also provides details on how call history is stored for shared lines.

Uploaded by

Cristhian Haro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
48 views15 pages

Call History

The document discusses call history features that record incoming calls with caller ID or ANI information into a rolling list for each station. It describes how call information is stored for different call scenarios like answered, abandoned, transferred or forwarded calls. The summary also provides details on how call history is stored for shared lines.

Uploaded by

Cristhian Haro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

OVERVIEW

Call History Incoming calls with Caller ID or ANI information may be optionally
recorded into a rolling list for the station where the call is ringing. The call
is placed in the list along with the number, name (if provided), time and
date of the call, and status of the call (answered, abandoned, or
redirected). This list is accessible by the user from the telephone LCD and
any call may be selected and redialed using the flexible Caller ID or
History button.

When a trunk line call having originator information is terminated to an


extension station and answered, not answered, not completed, or it is
transferred to another extension station or external line by Call Forward,
the originator information can be stored for each extension station at the
destination and the extension station can sequentially search, display and
call back the original incoming call.

When a call having originator information is terminated to a trunk line, the


system appropriately recognizes the originator’s name and number.
(Refer to Call Identification.) When a call is terminated to an extension
station and answered, not answered by the busy extension station and
abandoned, or the call is transferred to other extension station by Call
Forward, the system stores the originator information in the memory
provided for each extension station. The memory is limited for each
extension station and when the memory becomes full, the oldest data
stored is overwritten. The call history memory is non-volatile, and the
contents are held even if the power switch is turned off.

This feature is applicable when the calling party's information is presented


to the system regardless what mechanism is used, SIP or ISDN trunk,
ANI, or CLASS connected to 3rd party gateway. A call from a trunk
without such capability or a call whose calling party's information is
omitted or classified as "presentation restricted" is not stored in the
station's memory. An outgoing call is not recorded in the memory.

Information to be stored in the memory contains the originator’s name,


the originator’s number (if provided by the network), abandoned or
answered time (month/ day/ time) and result (answered/ abandoned/
redirected). This information is stored for the destination station when the
call is terminated from a public network by Direct Inward Dialing or Direct
Inward Termination.

If the destination is the "dialed station" i.e., if the call has not been
transferred or forwarded, the system stores the record regardless of
whether the call actually rings the station or not. For example, even if the
dialed destination forwards a call unconditionally using Call Forward All
Call, or Call Forward Busy, or even if the dialed destination denies a call
using Do Not Disturb, the system stores the record for that station.

However, if the destination is a transferred or forwarded destination, the


system stores the record only when the destination station accepts or
answers the call. If the destination forwards the call using Call Forward All

IPedge Feature Desc. 5/6/11 1-1


Call, or Call Forward Busy or denies the call by Do Not Disturb, the record
is not stored.

Call Forward All Call

Call Forward All Call



2 3

4 5 6

7 8 9

# 0 *

203

1 2 3 1 2 3

4 5 6 4 5 6

7 8 9 7 8 9

# 0 * # 0 *

201 202

Dialed Station

In the illustration above, an incoming call is presented to station 201,


which is forwarded to 202. Station 202 has also activated Call Forward All
Call, thus, the call is terminated to 203. In this situation, the call arrival is
recorded at 201 and 203 if those stations have memory for it. The result is
"Redirected" for 201 while it is "Answered" or "Abandoned" depending on
the result for 202. But, the call is not recorded for 202 because it is neither
the dialed station nor the physically-rung station.

Where the record is stored in the station's memory, it is done when the
termination stops at the station. If the termination stops because the
originator abandoned the call, the result is "Abandoned." If the termination
stops because the call is transferred/forwarded to another station or
because another station picks up the call, the result is "Redirected" for the
station. If the terminating stops because the station answers it, the result
is "Answered."

If the line where the call is terminated is shared by other station through
Multiple Appearance, the information is stored at a particular station as
follows.

1. When the destination line is PDN, PhDN, and GCO button and the
owner exists, the information is stored in the owner’s station memory.
2. When the destination line is PDN, PhDN, and GCO button and owner
does not exist, or the destination is Pooled Line button, the
information is stored in the memory of the station specified per line
basis. If an owner exists and the station to store the call history is
specified, the information is stored in the memory of both stations.
If the owner station answers the terminating call, the result is "Answered"
for the owner record. If another station than the owner answers the call,
the result is "Redirected" for the owner record and "Answered" for the

IPedge Feature Desc. 5/6/11 1-2


station who answers the call. In case that there is another station
specified to store the call history, the same rule is applied as to an owner.

An Extension station can search the call history of its own station using
the feature button. To indicate the call history, press the CLID button while
the station is idle. The CLID button lights in green, and the station goes
into Call History Viewer Mode. The LCD displays the originator name and
information of the latest record. When the VOLDOWN button is pressed,
the previous record displays. When the VOLUP button is pressed, the
next later record displays. When the page key is pressed, the terminating
date and status display. When the page key is pressed again, the display
returns to the originator name and the number.

When the VOLUP button is pressed while the latest record is being
displayed, the oldest record displays. Contrarily, when the VOLDOWN
button is pressed while the oldest record is being displayed, the latest
record is displayed. The record is cyclically displayed.

When the CLID button is pressed while the station is neither idle nor
terminating, it is ignored.

PAGE
JON SMITH JON SMITH
2122345678 01/21 13:58 ABN

VOLDOWN
VOLDOWN VOLUP
VOLUP

MARY JONES MARY JONES


4374567890 01/21 11:24 ANS
PAGE

This operation is common to the stations regardless of the lines of the


LCD display.

During this operation, the inter-digit timer does not work.

The information stored for each station should be capable of restoring the
previous operation for upgrades.

While the call history is being displayed in Call History Viewer Mode, the
originator can be called back. To make a callback, display the destination
on the LCD and do any one of the following:

1. Press the GCO button, Pooled Line button and the CLID button.
Depending on the programming option, the system may or may not
add “1” for the long distance call. See “1.1 Concept of Callback
Operation” section below for the details.

IPedge Feature Desc. 5/6/11 1-3


2. Press the PDN button and PhDN button, then dial the necessary
access code, and press the CLID button.
3. Press the SPKR button or hook off, select an appropriate line button
by Automatic Line Selection, then dial the necessary access code,
and press the CLID button.
4. Dial the necessary access code without pressing the line button,
select an appropriate line button by Hot Dialing, and press the CLID
button.
When the CLID button is pressed, the system goes into the ordinary call
processing mode and the CLID button LED disappears. The system
continues call processing by inserting the originator’s number in the
position where the CLID button is pressed. The system processes an
outgoing call according to the feature selected by the pressed button and
dial. Class Of Service, Toll Restriction, and Account Code are applied the
same as for an ordinary call.

When the CLID button is pressed without selecting the line button by
watching the LCD display in Call History Viewer Mode, the system goes
into ordinary call processing mode and the CLID button LED disappears.
Callback is not made because the line button is not selected.

When a feature button, other than dial pad and CLID button, is pressed in
Call History Viewer Mode after the line button is selected and the station
goes out of dialing phase, then Call History Viewer Mode is finished and
the CLID button LED goes out. The system continues the ordinary call
processing service according to the pressed line button and feature
button. However, if the pressed function is the SPEED DIAL or One
Touch Button, and the station is still in the dialing phase even after the
feature button is pressed, the CLID button is valid.

When dial number is sequentially dialed and the dial digits reach the
necessary number to make an outgoing call after the line button is
selected (the dialing phase is finished), Call History Viewer Mode is
finished and the CLID button LED goes out.

When a call comes in to a station during Call History Viewer Mode, the
incoming call is processed as usual, but the call history is still displayed
on the LCD. When the Call History Viewer Mode is finished, the incoming
calls display on the LCD according to the order of their priority. When the
terminated line button is pressed to answer to the incoming call during
Call History Viewer Mode or when the line button indicated as In-Use is
pressed to join a conversation, then Call History Viewer Mode is finished.

Concept of Callback There are various callback operations using the CLID button. These
Operation operations are based on the following concepts.

1. When the CLID button is pressed while the station is idle, call history
displays. If the feature button and line button other than the keys to
control the display are pressed, then the display control mode is
finished. If the line button is selected when the mode is finished, the
originator’s information displayed last is associated with the CLID

IPedge Feature Desc. 5/6/11 1-4


button. When the CLID button is pressed during dialing, the
associated calling party number information is used.
2. The information associated above is valid only when the station is in
the dialing phase and disappears when the service is determined, the
station becomes idle again, or the dialing phase is finished (Call
History Viewer Mode is finished).
3. In the United States, the central office notifies AC+OC+SN as the
calling party information all the time no matter if it is local or long
distance. In Canada, the central office notifies 1+AC+OC+SN for long
distance and OC+SN for local call. The IPedge system takes the
programming option whether “1” is added in front of the calling party
or not, when the call back occurs, to support both of the regions. In
the US, for the local call, 1+AC has to be stripped off using the LCR
digit modification table. As for the 10-digit local number, just “1” must
be stripped off. This method works only if the LCR is used to call
back. For other trunk access methods, even though the method
doesn’t work, it is regarded as a feature limitation.
4. When a calling party's information is stored, the feature defined in the
Numbering plan on CLI is applied.

IPedge Feature Desc. 5/6/11 1-5


Call History Incoming calls with Caller ID or ANI information may be optionally
recorded into a rolling list for the station where the call is ringing. The call
is placed in the list along with the number, name (if provided), time and
date of the call, and status of the call (answered, abandoned, or
redirected). This list is accessible by the user from the telephone LCD and
any call may be selected and redialed using the flexible Caller ID or Hist
button.

When calls ring a button (Line or DN) that appears on multiple stations,
the number is stored on the telephone that is designated as the owner of
the Line or DN and on the telephone that answers the call. If an incoming
call is directed to a telephone, but the call is not answered by that
telephone because it hunts or forwards to another destination, the call
record is still stored on that telephone as “redirected” and on the
telephone that answers the call as “answered.” If a call is not answered, it
is stored on the line or DN owner’s telephone as “abandoned.”

To store call records, a telephone must be allocated Call History memory


by the System Administrator.

IPedge Feature Desc. 4/13/11 1-6


Call History Incoming calls with Caller ID or ANI information can be optionally
recorded into a rolling list for the station where the call is ringing. The call
is placed in the list along with the number, name (if provided), time and
date of the call, and status of the call (answered, abandoned, or
redirected). You can access this list from an LCD telephone with a flexible
Caller ID button.

View Call History • When your station is idle, press the Caller ID button. The Caller ID
LED lights green and the latest record displays.
• Press Vol + ▲for the next record; press Vol + ▼ for the previous
record.
• To view the call date, time, and status, press SK2 (press again to
toggle to call name/number).

IPedge Feature Desc. 4/13/11 1-7


PROGRAMMING

System Data 1. Click on System > System Data.


2. Enable/Disable: Call History Prefix Enable inserts a 1 in front of
returned calls.
3. Reset to Default sets all values to factory defaults.
4. Click on Save icon.

Call History Store Station 1. Click on Station > Call History Store Station.
2. Check the IPedge Server to modify.
3. Click on Edit icon.
4. Enter the station DN for which to store call history data.
5. Click on Save icon.

Station Assignment 1. Click on Station > Station Assignment.


2. Check the Station to be programmed.
3. Click on Edit icon.
4. Select the Preference tab.
5. Click Show Advance Configuration.
6. Select the Call History amount of Memory to be assigned to the
station.
7. Click on Save icon.

IPedge Feature Desc. 4/13/11 1-8


CAPACITY The number of stored call history = 2000 in the whole system (maximum
capacity).

AVAILABILITY
Station/Line Descriptions
IPT Applied for IPT with LCD
Soft IPT Applied

RESTRICTIONS The Call History feature is applied only for incoming calls from a public
trunk which provides caller information and a call providing valid caller
information. This is regardless of whether it is a SIP or ISDN trunk.

IPedge Feature Desc. 4/13/11 1-9


HARDWARE No additional hardware is necessary for this feature.

IPedge Feature Desc. 4/13/11 1-10


FEATURE INTERACTION

Account Codes This is applied the same as an ordinary call.

ACD Overflow to Voice Mail An overflow call is handled as a ring transfer call and recorded as a dialed
station in the call history at the overflow destination.

After-Shift Service Call History feature is applied at the Aftershift destination.

Automatic Busy Redial If the destination is busy when a call is originated using Call History, the
(ABR) Automatic Busy Redial feature can be invoked.

The Call History feature is not applied to Call Back to ABR Invoker. (Call
History is not stored.)

Automatic Callback (ACB) When all trunks are busy and callback fails, it is possible to activate
Automatic Callback but it is not possible to use the CLID button for
originating a call thereafter because the CLID button goes out in this
state. However, if the call is originated in Senderized mode and Automatic
Call Back is activated after the callback destination is entered with the
CLID button, the extension station registered for Automatic Call back is
automatically called immediately when the trunk becomes idle the same
as in an ordinary call.

Because an incoming call from the trunk cannot invoke Automatic


Callback, the call history does not have the feature interaction.

Automatic Camp On/Off- When all trunks are busy and callback fails, it is possible to activate Off-
hook Camp On hook Camp On but the user cannot use the CLID button for originating a
call thereafter because the CLID button goes out in this state. However, if
the call originates in Senderized mode and Off-hook Camp On is
activated after the callback destination is entered with the CLID button,
the destination is automatically called immediately when the trunk
becomes idle the same as in an ordinary call.

An incoming call, which automatically camps onto the station with the call
history option, is recorded in the station's memory if it is the "Dialed
Destination." The timing for recording is when the call is abandoned. If the
camp on is retrieved and the call is terminated to the destination, the
recording takes place just like other ordinal calls.

If the destination of camp on is not the dialed destination, the call is not
stored in the memory when the camp on is abandoned. However, even in
this case, if the camp on is retrieved and the call is terminated to the
destination, the recording takes place just like other ordinal calls.

IPedge Feature Desc. 4/13/11 1-11


Automatic Line Selection When two or more calls come in to a certain station, the lowest priority call
cannot actually ring the station. Call history is recorded even in this case
(call history is recorded for the owner station regardless of whether the
call actually rings the station).

When the SPKR button is pressed or the line is hooked off in Call History
Reviewer Mode, the line button is selected by Automatic Line Selection. If
there is a ringing button and the system is set to preferably select the
ringing button, the system answers the ringing line button. Call History
Reviewer Mode ends, and the CLID button turns off.

Back Light In Call History Mode, Backlight turns on and does not turn off.

Basic Survivability Call histories in the primary server are not succeeded to a secondary
server.

Call histories in the secondary server during switchover are not


succeeded to the primary server.

Call Forward/System Call When an internal call is forwarded unconditionally to another destination
Forward by Call Forward or System Call Forward, the call is recorded as the
forwarding station’s call history only when the extension is a Dialed
Station. When the forwarded destination accepts the call, it is recorded as
call history of the forwarded destination as well.

If a call is forwarded by Call Forward No Answer, the call is recorded


when it is forwarded with the result as "Redirected."

Call Monitor No Call History record is saved on either the called or Voice Mail device
when the Call Monitor feature invokes.

Call Pickup When the incoming call is answered by the Call Pick Up feature, it is
recorded as incoming call history.

Call Transfer With Call Transfer, when an external incoming call is transferred, the call
history is recorded as "Answered."

Call Transfer Immediate/ With Ring Transfer and Call Transfer With Camp On, when an external
Call Transfer With Camp incoming call from CO is transferred, call history is recorded at events of
On/Ring Transfer abandon, answer, or redirection. Considering the attendant, the
destination of Ring Transfer, Call Transfer with Camp On, and Call
Transfer Immediate are treated as Dialed Destination.

Caller Identification This feature is not applied for SIP station. Call history is not saved.

IPedge Feature Desc. 4/13/11 1-12


The Call History feature may be provided by the station to save call
history and use history to originate, if the station is SLT that can display
caller information or SIP station. Thus, it depends on the spec of the
station how to use call history feature.

Class Of Service Override This is applied the same as an ordinary call.

Consultation Hold Call history is recorded the same as the ordinal termination from a station
when a Consultation hold invoker puts a 2 way call or conference on
consultation hold and calls the station.

Delayed Ringing Even if the owner station or the station specified to store the call history is
set to ring for the incoming call with delay by Delayed Ringing feature, the
incoming call is recorded when the termination stops at DN if those
stations are the dialed destination. If those stations are not the Dialed
Station and the call is abandoned, answered, or redirected before the
delay timer expires for those stations, the call is not recorded for those
stations. Once the ringing starts at those stations, the call is recorded at
the events of abandon, answer, and redirection.

Do Not Disturb (DND) The Call History feature is applied and saved as usual for the call after Do
Override/DND/ Busy Not Disturb Override is activated.
Override

Do Not Disturb (DND) Even if the destination station activates Do Not Disturb, call history is
recorded if it is the Dialed Station. It is possible to call back with the CLID
button while activating Do Not Disturb.

Executive Override The barged into party by Executive Override does not record the
information from the barged-into party as terminating history.

External ACD Applied regardless of the agent state, logged in or out.

Group CO Button The Call History feature is applied only for the owner station when the call
is terminated on a Group CO button.

Hot-dialing The Hot Dialing feature is applied by pressing the dial pad in Call History
Reviewer Mode. When the CLID button is pressed as the first button in
Call History Reviewer Mode, the system finishes Call History Reviewer
Mode without selecting the line button.

IP Phone User Mobility The DN is treated as busy when the terminating DN is logged out. Thus,
caller information is stored to the memory that is kept for each station.

LCD Shift Key Each feature button can be set on both the fore side and the hidden side.

IPedge Feature Desc. 4/13/11 1-13


The service using LED continues even though it is not indicated while on
the hidden side.

Least Cost Routing (LCR)/ After the line button is selected in Call History Reviewer Mode, the trunk
Outgoing Call call method is selected according to the entered access code.

Local Date and Time The information of the terminating time in Call History record by Call
History feature is the IPedge server time where the station belongs.

Make Busy Call History is saved at the station in make busy mode.

Multiple Calling When a station answers a call, the record is stored in that station. The
records are not stored in other stations as abandoned.

When a station doesn't answer a call, the record is stored only in the
primary destination as an owner of that Multiple Calling group.

Numbering plan on CLI When originator number is referred, the feature defined in Numbering
plan on CLI is applied.

Overflow Call overflow is handled as a Ring Transfer call and is recorded in the
incoming call list as a Dialed Station in the Overflow destination.

PC Attendant Attendant can store the same information as IPT, however, the operation
depends on the spec of the PC application.

Pop Speed Dial A Speed Dial Name is stored to the memory that is kept for each station,
when the incoming call is answered, the incoming call is abandoned
because of no answer, busy, or the incoming call is forwarded by the Call
Forward feature.

Private Networking Over IP In IPedge, when an incoming call is from a trunk line, it is recorded as the
Call History of a terminating extension. If the incoming call is not from a
trunk or it comes from non-IPedge, it is not recorded as Call History.

When calling back a call by searching Call History, take the appropriate
outgoing call originating operation. A callback is not always made in the
same route as the incoming call.

Recall Treatment/Lost Call An Incoming call of Recall or Lost Call is not recorded as call history.
Treatment

Ringing Assignment Even if the station is set not to ring by Ringing Assignment, call history is
recorded if the station is an owner station.

IPedge Feature Desc. 4/13/11 1-14


SIP Extension It is possible to store Call History information, but there is no way to
display it.

The station may provide the Call History feature.

SIP Trunking Provided.

Specified Caller Call History is not stored if MAS (FF PCH) or Varaha makes a call to a
Identification station in the IPedge system because the call from MAS or Varaha is an
internal call.

Station Hunting The Call History feature is applied for the station including secondary
appearances and Call History is recorded when the call is diverted from
the pilot DN.

The Call History feature is applied only for a Dialed Station, including
secondary appearances, and Call History is recorded when the incoming
call is diverted from a Dialed Station to another member because of busy
or other reasons.

Station To Station Call History is applied only to the external call from CO.
Connection

Toll Restriction This is applied the same as an ordinary call.

IPedge Feature Desc. 4/13/11 1-15

You might also like