Cisco 3000 User Manual

Phone Features
This chapter provides information, including feature interactions and restrictions, for the following phone features. Phone features may not be supported on all phones models that are available with Cisco Business Edition 3000, so use this information in conjunction with the documentation that is available for your phone. Be aware that your phone may support additional features that are not described in this chapter.
Ad hoc Conference, page 2
Barge, page 2
Call Back, page 3
Call Forward All, page 6
Call Forward Busy, page 6
Call Forward No Answer, page 6
Call Hold and Resume, page 6
Call History, page 7
Call Park, page 7
Call Pickup, page 8
Call Transfer (Direct and Consultative), page 8
Call Waiting, page 8
Caller ID, page 8
Cisco Extension Mobility, page 9
Cisco Web Dialer, page 9
Click to Call, page 10
Distinctive Ringing, page 10
Do Not Disturb, page 10
Meet-Me Conference, page 11
Music On Hold, page 12
Administration Guide for Cisco Business Edition 3000, Release 8.6(3)
OL-25035-01 1

Ad hoc Conference

Mute/Volume Control, page 13
Phone Applications, page 13
Reach Me Anywhere, page 13
Rollover Lines, page 14
Shared Lines, page 14
Speed Dials, page 15
Voicemail, page 16
Ad hoc Conference
Ad hoc conferences allow the conference controller to add specific participants to the conference. An Ad hoc conference is started by an initiator, and only the initiator of the conference, who is the conference controller, can add parties to the conference. Ad hoc conferences can support up to 4 participants.
Phone Features

Barge

For Ad hoc conferences to work, you must enable the conference bridge in the Sites pages.Note
When a user initiates a conference call, Cisco Business Edition 3000 places the current call on hold, flashes the conference lamp on the phone (if applicable), and provides dial tone to the user. At the dial tone, the conference controller dials the next conference participant and presses the conference softkey/button to complete the conference. Cisco Business Edition 3000 then connects all parties. Each participating phone may display that the conference is occurring.
A conference participant can view the list of conference participants and can drop the last conference participant from the conference. If a conference participant transfers the conference to another party, the transferred party becomes the last conference participant in the conference. If a conference participant parks the conference, the participant becomes the last party in the conference when the participant picks up the conference. When only two participants remain in the conference, Cisco Business Edition 3000 terminates the conference, and the two remaining participants reconnect directly as a point-to-point call.
Participants can leave a conference by simply hanging up. A conference continues even if the conference controller hangs up, although the remaining conference participants cannot add new participants to the conference.
Barge allows a user to interrupt a call without the permission of the participants that are on the call. Barge requires the use of shared lines. When a user barges into a call, the user presses the line button for the shared line or the barge softkey/button on the phone (depending on phone model). With barge, the system sets up a conference between the participants. When any participant leaves the call, the remaining participants may experience a brief interruption as the system sets up a point-to-point call.
If one participant presses the call divert softkey/button during the barged call, the system plays the outgoing greeting for the participant that pressed the softkey/button, and all participants can hear the greeting.
Administration Guide for Cisco Business Edition 3000, Release 8.6(3)
2 OL-25035-01
Phone Features

Call Back

Call Back
Call back provides users with an audio and visual alert on the phone when a busy or unavailable party becomes available. Call back works only with extensions that are in the dial plan. To receive call-back notification, the user must press the call back softkey/button while receiving a busy, ringback, or reorder tone on the phone.
Note
Call back is available automatically with Cisco Business Edition 3000, so you do not need to perform any configuration tasks to use it.
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).
If the phone of the calling party (User A) gets reset after call back has been enabled by the user, then call back gets automatically cancelled. User A does not receive an audio alert, and the call back notification does not display on the phone. If the phone of the called party (User B) gets reset, call back does not get cancelled. User A will receive an audio alert, and the call back notification displays after User B becomes available.
When a Cisco Extension Mobility user logs in or logs out of a Cisco Extension Mobility-enabled phone, any active call completion that is associated with call back automatically gets canceled.
If the user forwards all calls to voicemail, the user cannot use call back.
Example: User A calls User B, who is not available
User A calls User B. Because User B is busy or does not reply, User A activates the Call Back feature by using the call back softkey or button. 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 call back notification displays on the phone. User A goes off hook and dials the extension of User B. User B answers the call. Users A and B go on hook.
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 call back softkey or button. 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, callback notification displays on the phone. User A can interrupt the active call to contact User B in either of the following ways:
• Dial from the call back notification screen. The active call automatically gets put on hold while User A calls User B.
• Exit the call back 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 to User C before call-back activation occurs
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 the phone for User A that states that the user is available.
Administration Guide for Cisco Business Edition 3000, Release 8.6(3)
OL-25035-01 3

Call Divert

Call Divert
Phone Features
Example: User A calls User B, who configures call forwarding to User C after User A activates call back
User A calls User B. 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.
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 dials User B first connects to User B.
Call divert allows a user to transfer a ringing, connected, or held call directly to voicemail. After a call is diverted, the line becomes available to place or receive new calls. For call divert to work, the user must press the call divert softkey/button on the phone.
When a caller calls a user, the assistant attends the call through shared line and divert the call directly to the user's voice mailbox. The Call Divert softkey appears in the connected state.
When a conference participant presses the call divert softkey/button on the phone, the remaining conference participants receive the voice mailbox greeting of the party that pressed the softkey/button.
Members of a hunt list can invoke call divert if the call is direct. They cannot invoke call divert if they are reached as a member of a hunt list, and a message ‘Feature is unavailable’ displays on the phone.
In some cases, call divert can detect a busy condition on the voice-messaging ports. (The call cannot divert to a busy voice-messaging system, but the original call gets maintained. Busy will display on the phone on which call divert was invoked to indicate that the call was not diverted.)
The calling and called parties may divert the call to their voice mailboxes if both simultaneously press the divert softkey/button. The voice mailbox of the calling party would contain a portion of the outgoing greeting of the called party. Similarly, the voice mailbox of the called party would contain a portion of the outgoing greeting of the calling party.
Example: Called Party Presses Divert Softkey
1
Party A calls Manager A.
2
Manager A presses the call divert softkey.
3
The call gets diverted to the voice mailbox of Manager A.
4
Party A receives the voice mailbox greeting of Manager A.
Example: Forwarded call on shared line (manager-assistant scenario) gets diverted to the voice mailbox of the manager
1
Caller calls manager.
2
The assistant attends the call through a shared line and presses the Call Divert softkey.
3
Immediate Divert diverts the call to the manager's voice mailbox.
4
The caller receives the voice mail greeting of the manager.
Administration Guide for Cisco Business Edition 3000, Release 8.6(3)
4 OL-25035-01
Phone Features
The Call Divert softkey appears in the connected state.Note
Example: Forwarded Call Gets Diverted to the Voicemail of Another Party
1
Party A calls Party B.
2
The call gets forwarded to the personal line of Assistant B.
3
Assistant B presses the Divert softkey.
4
The call gets diverted to the voice mailbox for Assistant B.
5
Party A receives the voice mailbox greeting of Assistant B.
Example: Manager A Forwards a Call to Manager B
1
Party A calls Manager A.
2
Manager A has line forwarded to Manager B.
Call Divert
3
Manager B presses the Divert softkey.
4
Immediate divert diverts the call to Manager B voice mailbox.
5
Party A receives the voice mailbox greeting of Manager B.
Example: Voicemail is Busy
1
Party A calls Party B.
2
Party B presses the Divert softkey.
3
The call cannot be diverted to the voice mailbox because the voice-messaging port is busy.
4
Party B sees the message Busy on the IP phone.
5
The original call remains in the call-offering state.
Example: Calling Party Calls a Hunt Pilot Number
1
Party A calls Hunt List B.
2
Hunt List B member presses the Divert softkey, which is disabled.
3
Call divert cannot divert the call to the voice mailbox to Hunt List B because Party A is not allowed to use voicemail. The following message displays on the Hunt List B member phone:
Feature is unavailable.
Note
If the calling party directly calls the phone number/extension of the member, the member can divert the call to voicemail if call divert and voicemail are enabled in the usage profile that is assigned to the member.
Administration Guide for Cisco Business Edition 3000, Release 8.6(3)
OL-25035-01 5
Loading...
+ 11 hidden pages