The
following examples describe how hold reversion works in
Cisco Unified Communications
Manager.
In these
examples, the hold reversion duration timer, which defines when to activate
hold reversion, is set to 30, and the hold reversion interval timer, which
defines when to send reminder alerts, is set to 20.
Example: Hold
Reversion Feature Disabled
User A
calls user B, who exists on the same system as user A. User B answers the call
and puts the call on hold. If MOH is configured for held calls, user A receives
music.
Because
hold reversion is not enabled for the DN, user B does not receive alerts to
indicate that the call remains on hold. The clusterwide Maximum Hold Duration
Timer system setting expires, and
Cisco Unified Communications
Manager clears the call.
Example:
Reverted Call and New Outgoing Call
User A
calls user B, who exists in the same
Cisco Unified Communications
Manager system as user A. User B answers the call and puts the call
on hold. If MOH is configured for held calls, user A receives music.
Cisco Unified Communications Manager notifies user B
when the held call assumes the reverted state - after 30 seconds,
Cisco Unified Communications
Manager sends the message
"Hold Reversion"
to the phone and rings the phone once (or beeps or flashes once) on the holding
DN. (Your phone may support additional alerting mechanisms.)
User B
goes off hook to make an outgoing call when the held call is in the reverted
state.
Cisco Unified Communications
Manager resumes the held call. User B cannot make a new outgoing
call.
Example: Shared
Line
User A and
user B exist in the same system. User A calls a shared line on user B phone.
User B puts the call on hold. If MOH is configured for held calls, user A
receives music.
Cisco Unified Communications Manager notifies user B
when hold reversion activates for the call - after 30 seconds,
Cisco Unified Communications
Manager sends the message
"Hold Reversion"
to the phone and rings the phone once (or beeps or flashes once) on the holding
DN. (Your phone may support additional alerting mechanisms.) Other users on the
shared line do not receive reverted call alert.
Until user
B retrieves the reverted call,
Cisco Unified Communications
Manager sends periodic reminder alerts every 20 seconds to the
holding phone for the DN -
Cisco Unified Communications
Manager sends the message
"Hold Reversion"
to the phone and rings the phone once (or beeps or flashes once) on the holding
DN at the configured intervals. (Your phone may support additional alerting
mechanisms.) No other users on the shared line receive reminder alerts.
User B
receives no other calls on the phone. The reverted call has focus, and user B
goes off hook. User B retrieves the reverted call.
 Note |
When the held
party is a shared line, other line appearances show normal indicators for a
remote-in-use call. When the holding party is a shared line, the remote-in-use
indicator does not display on other line appearances after the user puts the
call on hold; the remote-in-use indicator redisplays on the other line
appearances when the user reconnects with the call. If another user on the
shared line picks up the reverted call, the phone of the holding party displays
the remote-in-use indicator and no longer displays hold reversion alerts. If
the holding party drops off the call, for example, gets released by an
application, the Hold Reversion timers deactivate.
|
Example:
Multiple Reverted Calls on the Same Line
User A and
user C call user B on the same DN; user B has Hold Reversion enabled, and call
A is a reverted call.
User B
answers the call from User C and puts the call on hold. If MOH is configured
for held calls, user C receives music.
Cisco Unified Communications Manager notifies user B
when call C assumes the reverted state - after 30 seconds,
Cisco Unified Communications
Manager sends the message
"Hold Reversion"
to the phone and rings the phone once (or beeps or flashes once) on the holding
DN. (Your phone may support additional alerting mechanisms.) User B gets
reminder alerts for both calls every 20 seconds.
Call A has
focus, and user B retrieves the reverted call from user A.
Example:
Multiple Reverted Calls on Different Lines with Incoming Call
User A
calls on line B1 for user B, who has hold reversion configured on both B1 and
B2. User B puts user A on hold. If MOH is configured for held calls, user A
receives music.
User C
calls on line B2 for user B. User B puts user C on hold. If MOH is configured
for held calls, user C receives music.
Both held
calls enter the reverted state when they exceed the preconfigured time limit of
30 seconds. User B gets hold reversion alerts for both held calls.
An
incoming call comes in on line B3. Incoming calls have focus priority. User B
goes off hook and answers the incoming call. User B ends the B3 call.
User B
goes off hook and resumes the B1 call. User B still receives reminder alerts
every 20 seconds for call B2. User B presses the
Resume softkey. Call B1 gets put on hold, and
call B2 gets connected.
Cisco Unified Communications Manager restarts the
timer for activating the hold reversion feature on call B1.