The
following examples describe how Call Back works after an unavailable phone
becomes available.
Note |
The calling phone
only supports one active call back request. The called phone can support
multiple call back requests.
Call Back only
supports spaces and digits 0 through 9 for the name or number of the calling or
called party. To work with Call Back, the name or number of the calling or
called party cannot contain # or * (pound sign or asterisk).
|
Note |
If the originating
side (User A) gets reset after Call Back has been activated, then Call Back
gets automatically cancelled. User A does not receive an audio alert, and the
Callback notification screen does not display. If the terminating side (User B)
gets reset, Call Back does not get cancelled. User A will receive an audio
alert, and the Callback notification screen displays after User B becomes
available.
|
Example: User A
Calls User B, Who Is Not Available
User A
calls User B, who exists either in the same
Cisco Unified Communications
Manager cluster as User A or in a different cluster.
Because User B is busy or does not reply, User A activates the Call
Back feature by using the CallBack softkey. The following call back activation
message displays on the phone of User A:
CallBack is activated on <DN of User B>Press Cancel to deactivate
Press Exit to quit this screen
User A
presses the Exit softkey.
After User
B becomes available (phone becomes on hook after busy or completes an off-hook
and on-hook cycle from idle), User A receives an audio alert, and the following
message displays on the phone of User A:
<DN of User B> has become availableTime HH:MM MM/DD/YYYY
Press Dial to call
Press Cancel to deactivate
Press Exit to quit this screen
User A
presses the Exit softkey and then goes off hook and dials the DN of User B.
User B answers the call. Users A and B go on hook.
When User
A presses the CallBack softkey, the following message displays on the phone of
User A:
<DN of User B> has become availableTime HH:MM MM/DD/YYYY
Press Dial to call
Press Cancel to deactivate
Press Exit to quit this screen
Note |
Manually dialing a
DN that has been activated with Call Back notification does not affect the Call
Back status.
|
Example: User A
Activates the Call Back Feature for User B but Is Busy When User B Becomes
Available
User A
calls User B. User B does not answer. User A activates the Call Back feature by
using the CallBack softkey. The following call back activation message displays
on the phone of User A:
CallBack is activated on <DN of User B>Press Cancel to deactivate
Press Exit to quit this screen
User A
presses the Exit softkey.
User C
then calls User A, and users A and C go on hook in an active call. User B
becomes available (phone becomes on hook after busy or completes an off-hook
and on-hook cycle from idle) while User A is still on an active call. User A
receives an audio alert, and the following message displays on the phone of
User A:
<DN of User B> has become availableTime HH:MM MM/DD/YYYY
Press Dial to call
Press Cancel to deactivate
Press Exit to quit this screen
User A can
interrupt the active call to contact User B in either of two ways:
-
Select Dial from
the notification screen. The active call automatically gets put on hold while
User A calls User B.
-
Press the Exit
softkey to exit the notification screen and then park (or otherwise handle) the
active call. After the active call is handled, User A can press the CallBack
softkey and select Dial to call User B).
Example: User A
Calls User B, Who Configured Call Forward No Answer (CFNA) to User C Before
Call-Back Activation Occurs
The
following scenario applies to Call Forward No Answer.
The call
from User A gets forwarded to User C because Call Forward No Answer is
configured for User B. User A uses call back to contact User C if User C is not
busy; if User C is busy, User A contacts User B.
When User
B or User C becomes available (on hook), User A receives an audio alert, and a
message displays on User A phone that states that the user is available.
Example: User A
Calls User B, Who Configures Call Forwarding to User C After User A Activates
Call Back
The
following scenarios support Call Forward All, Call Forward Busy, and Call
Forward No Answer.
-
User A calls
User B, who exists in the same
Cisco Unified Communications
Manager cluster as User A. User A activates call back because User B
is not available. Before User B becomes available to User A, User B sets up
call forwarding to User C. User A may call back User B or User C, depending on
the call-forwarding settings for User B.
-
User A calls
User B, who exists in a different cluster. The call connects by using a QSIG
trunk. User A activates call back because User B is not available. Before User
B becomes available to User A, User B sets up call-forwarding to User C. One of
the following events occurs:
-
If the
Callback Recall Timer (T3) has not expired, User A always calls back User B.
-
After the
Callback Recall Timer (T3) expires, User A may call back User B or User C,
depending on the call-forwarding settings of User B.
Tip |
The timer starts
when the system notifies User A that User B is available. If User A does not
complete the call back call during the allotted time, the system cancels call
back. On the phone of User A, a message states that User B is available, even
after the call back cancellation. User A can dial User B.
|
Example: User A
and User C Call User B at the Same Time
User A and
User C call User B at the same time, and User A and User C activate call back
because User B is unavailable. A call-back activation message displays on the
phones of User A and User C.
When User
B becomes available, both User A and User C receive an audio alert, and a
message displays on both phones that states that User B is available. The User,
that is, User A or User C, that presses the Dial softkey first connects to User
B.
Feedback