IP Phones 6900 8900 9900

(1)

(2)

BRKUCC-2050 Cisco Public

Cisco Unified IP Phones: Best Practices

and Collaboration Enablement

(3)

Session Objectives

At the end of the session, you should be able to:

 Understand the Cisco Unified IP Phone Portfolio offering

 Identify, understand, and configure feature updates on 6900, 8900, and 9900 series phones

 Understand the feature support for E20, EX, MX, SX and C-Series

(4)

Agenda

4

IP Phone Portfolio Overview

Release 9.2(2) Release 9.2(3) Release 9.3(1) Q&A Release 9.2(4) Telepresence Endpoints

(5)

(6)

Cisco Unified IP Phone Portfolio At a Glance…

6 SPA 500 Series SPA 900 Series SPA 500 Series 9900 Series 8900 Series 7900 Series 6900 Series 3900 Series 9900 Series 8900 Series 7900 Series 6900 Series 3900 Series 9900 Series 8900 Series 7900 Series 6900 Series 3900 Series

SPA 9000 UC500 Unified CME on ISR Unified CMBE Unified CM

Higher POR TFOLIO A V G LI ST PRICE ($USD) Lower Voice IP PHONE APPLI CA TI ONS Voice/Video Apps 7900 Series

(7)

Cisco Unified IP Phone Portfolio

8900 Series

9900 Series Advanced Collaborative Media Endpoints

• HQ video, voice, graphical color displays

• Desktop consolidation and business apps with VXI • USB, Bluetooth, Wi-Fi & Gigabit Ethernet

• Energy-friendly for cost savings

Advanced Professional Media Endpoints

• HQ video, voice, graphical color displays

• Desktop consolidation and business apps with VXI • USB, Bluetooth and Gigabit Ethernet

• Energy-friendly for cost savings

6900 Series Business Voice Endpoints

• Traditional telephony-like experience

Advanced Business Endpoints

• Deskphone, conference and VoWLAN endpoints • HQ voice , video, large graphical displays

• Desktop consolidation and business apps with VXI • Energy-friendly for cost savings

(8)

(9)

Features: Release 9.2(2)

 All Calls on Primary Line

 All Calls, Shared Line, Collapsed Call Bubble

(10)

All Calls on Primary Line

 A frequent customer feedback was that the All Calls key, when configured, uses up one of the available line keys on the 8961/99x1 phones, reducing the number of speed dials or other function keys that can be placed on the device

 In 9.2(2) firmware, administrators can

configure the Primary line to act like the All Calls key.

 This is configured on a per device basis

10 10

(11)

All Calls, Shared Line

 Original Request:

‒ All Calls showed wrong session bubble for two shared lines in one phone

 Background:

‒ Confusing Shared Line Caller ID ‒ Unclear Caller and Callee display

(12)

All Calls, Shared Line

 Scenario configuration:

 Phone A (David), B (Chuck), C (Ruth). Privacy set to off on all phones

 Phone A‟s 2nd line shared with B, 3rd line shared with C

 Select All Calls filter

Collapsed Call Bubbles – cont‟d

12

Phone A

(13)

All Calls, Shared Line

 From phone A, Call phone B: Shows the outgoing session

Collapsed Call Bubbles – cont‟d

(14)

All Calls, Shared Line

 Phone B calls phone C: On phone A, the following shows:

Collapsed Call Bubbles

14

Before:

(15)

All Calls, Shared Line

 Phone B calls phone C: On phone A, shows alerting call as it has higher priority than another session.

 Answer on phone A: On phone A, shows incoming session as it has higher priority than another session.

Collapsed Call Bubbles

Before:

(16)

Features: Release 9.2(2)

 Configurable Call Features: Call Forwarding, Call Pickup, and Group Pickup

 Additional Locale Support

16

(17)

Release 9.2(2) - IP Phone 3905

 Configurable Call Features: Call Forwarding, Call Pickup, and Group Pickup

‒ Previously, Call Forwarding, Call Pickup, and Group Pickup were hard-coded features

‒ In Release 9.2(2), you can enable or disable these features on the 3905 phone using the softkey template

 Note: Softkeys are not supported on IP Phone 3905. However, the phone downloads the softkey

template from Cisco Unified Communications Manager and uses the settings contained in the template to enable or disable these features. The three features are enabled by default. The softkey template settings affect only the three features listed here and phone ignores any other feature settings in the softkey template.

 Adding Locale Support

(18)

Features: Release 9.2(2)

 Multiple Calls Per Line

18

(19)

Multiple Calls Per Line (8941/8945)

 Releases prior to 9.2(2), Maximum Number of Calls/Busy Trigger is fixed to 3/2 per line

 From 9.2(2), Maximum Number of Calls/Busy Trigger is

configurable and maximum up to 24/24 for 8941/8945. Each call can be an outgoing call, incoming call or consultant call

 The default settings for Maximum Number of Calls/Busy Trigger is 4/2

 Maximum Calls Per Line feature on the 894x models is supported on CUCM 7.1.5 or higher release

(20)

Hold connected call Initiate 2nd call

Multiple Lines Per Call – cont’d

20 20

(21)

Features: Release 9.2(2)

 PLKs as Soft Keys

 FAC/CMC

 Enhanced Version Negotiation for CME (SIP)

 Disable Single Button Barge

 “phone not registered” display turned off

 Calling Party Normalization

 Maximum CTL file size

 SRST Notification

 Incoming Call Toast Timer

6900 Series IP Phones (November 2011)

(22)

Disable Single Button Barge

 6900 series IP Phones support Line Key Barge since 9.2(2) release. Now, it has capability to disable Single Button Barge for customer privacy

concern

 On CUCM phone configuration page, new configure item Line Key Barge is added

 This parameter specifies the capability to conference into remote-in-use call, it can be configured as below:

1. Default: phone can conference(cBarge) into the call

2. Off: Disable Single Button cBarge

3. Turn on softkey: Press line key will turn on softkeys configured in call state remote-in-use of softkey template, then user can choose to cBarge into the call (if configured) or start a new call

22 22

(23)

(24)

Features: Release 9.2(3)

 Default Back to All Calls

 One Touch Private Line Automatic Ringdown (PLAR)

 Alerting Calls Filter

 Busy Lamp Field for Call Lists

 Enable Video On/Off

 Call History for Shared Line

 VPN for Cisco Virtualization Client (VXC 211X)

 Additional USB Headset Support including hold function

 Headset Sidetone Control

 Enhanced Version Negotiation for CME

IP Phones 8961, 9951, and 9971 (Dec. 2011)

(25)

Default Back to All Calls

 Main purpose: Users want the All Calls view as default even after ending

a call on another line

 Old Behavior: Selecting a secondary line drives one of two configurable

behaviors:

1. The phone remains on that secondary line for the next call with the secondary line‟s filter view

2. The phone defaults back to primary line for the next call with the primary line filter view

In either case, returning to All Calls requires a button press

 New Behavior: The phone defaults back to All Calls filter for the next call

(26)

Default Back to All Calls

 A multi-level configuration in CUCM administration page to enable/disable this feature

26 26

(27)

User Experience: Default to All Calls

(28)

User Experience: Default to All Calls

 When the call ends and the second line is idle, the phone reverts to All Calls as shown below

28 28

(29)

Default to All Calls - Scenarios

 The IP Phone reverts to All Calls when a call has ended on the secondary line and the phone is in idle state

 Before reverting to All Calls, the phone checks to see if the All Calls or the Primary Line or the Alerting Calls filter is already selected. If it is, then it stays at the current line

 The phone also checks to see if it‟s a group pickup session, in which case, it stays at the current line

 Finally, it checks to see if “All Calls on Primary Line” in enabled. If so, the phone reverts to primary line

 If the “All Calls on Primary Line” is not enabled, then the phone will revert to the “All Calls”

(30)

One Touch PLAR

This feature changes the line behavior if the line is configured as PLAR (Private Line Automatic Ringdown)

 Old Behavior: Using PLAR requires two key presses to activate the call

1. Select the PLAR line

2. Select a session key to process the call

 New Behavior: Using PLAR requires one key press to activate the call

1.Select the PLAR line

2.The call session automatically appears and processes the call

Note:

 The phone should only issue a new call from a PLAR line when that line is idle

 There is no additional user or admin configuration required other than the PLAR

configuration

30 30

(31)

Alerting Calls Filter

 The Alerting Calls feature allows users to view a list of all Alerting Calls in chronological order; oldest to most recent

 Users interact with this feature using a programmable line key; easier to interact with Alerting Calls received across multiple phone lines

 The Alerting Calls filter is configured as a Programmable Feature Key via the CUCM administration web page

 This feature applies to 9971, 9951, and 8961 IP Phones

(32)

Alerting Calls Filter

 Step 1. Create a Phone Button Template

Configuration

32 32

(33)

Alerting Calls Filter

 Step 2. Select the template on the Phone Configuration page

(34)

Alerting Calls Filter

 Step 3. Modify the button items in the template

Configuration (Contd.)

34 34

(35)

(36)

Busy Lamp Field for Call Lists

 The Presence feature allows a user to monitor the real-time status of a directory number from the device of the user

 This feature will allow the watcher to monitor the status from the Call History list

 When the BLF for Call Lists parameter is set to Enabled, the phone line numbers in the Call History register BLF notifications and an icon

appears next to each Call History item in the Call History list

 The following states are monitored using this feature:

 Unknown  Idle  Busy  DND 36 36

(37)

Busy Lamp Field for Call Lists

 In Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters)

(38)

Busy Lamp Field for Call Lists

User Experience

38 38

(39)

Enable Video On/Off

 Video On/Off is added as video capabilities setting on the phone side. When video is disabled, user can make audio call only

 When the video capabilities option has been enabled by the administrator from CUCM, the “Video” item is added in the Preferences menu to allow users to turn on/off user video capabilities on the phone. When the video capabilities option has been disabled by the administrator, the “Video”

menu item does not show.

 This setting will not change the existing behavior of “Camera Settings: Auto Transmit Video”.

(40)

Enable Video On/Off

 When “Video Capabilities” is enabled, user can find a toggle under Preferences menu.

User Experience

40 40

(41)

Enable Video On/Off

 When “Video Capabilities” is disabled, the toggle for “Video enable” under Preferences menu will be removed.

(42)

Call History for Shared Line

 The feature is designed to provide an entry for user to track the calls happened on the other shared line phones

 Phone‟s remote call log remains the same as its shared line peer‟s local call log, except that a label “remote” is added in call detail

42 42

(43)

Call History for Shared Line User Experience

(Placed Call)

(44)

Call History for Shared Line User Experience

(Received Call)

Figure 1. Local log for received call _Figure _{2. Remote log for received call}

44 44

(45)

Call History for Shared Line

(46)

Call with Privacy

 If a phone has set privacy on, the remote log on its shared line peer

should hide the actual call information and display an empty number as well as a “Private” label

 Privacy setting may vary during a call, once the call gets connected, privacy change will not affect log contents

46 46

(47)

(48)

VPN for Virtualization Client (VXC 211X)

 This feature enables VPN tunneling for the Cisco VXC 2111 and Cisco

VXC 2112 clients when attached to a Cisco Unified IP Phone 8961, 9951 or 9971

 The phone can establish a separate VPN tunnel for VXC device plugged in its PC port

 All data traffic to and from the VXC is passed through that VPN tunnel

48 48

(49)

VPN for Virtualization Client (Contd.)

 VPN must be enabled

 VXC VPN relies on phone VPN feature; make sure that a VPN profile is applied to the phone before hand

 VXC VPN can be powered up when phone is using a power brick

 With Power over Ethernet Plus(PoE+) deployed on the network, the phone + Backpack can be powered solely via the network cable

 9971, 9951, and 8961 phones support VXC VPN. However, only when the phone is connected to the network via an Ethernet cable – VXC clients

(50)

VXC VPN

Typical Topology and Data Traffic

50 50

(51)

VXC VPN

 Configure Phone VPN before enabling VXC VPN

Phone Configuration

(52)

VXC VPN

 VXC is powered by the phone. In the Accessories menu, VXC should be indicated once it is recognized by the IP phone

User Experience

52 52

(53)

VXC VPN

 VXC VPN Enabled or Disabled is indicated on the phone VPN menu

(54)

VXC VPN

 When PC Port Link is down, VXC VPN tunnel is disconnected

User Experience (Contd.)

54 54

(55)

VXC VPN

 When PC Port link is up, the phone prompts the user to enter credentials before setting up the VXC VPN tunnel

(56)

VXC VPN

 VXC VPN is not allowed when the phone is on the wireless network

(9971). In this use case, the VPN menu on the phone indicates that the VXC VPN is tunnel is disconnected (even if the PC port is up)

User Experience (Contd.)

56 56

(57)

VXC VPN

 Both phone native tunnel and VXC tunnel are disconnected when user selects OFF from the phone menu

(58)

Headset Sidetone Control

 The Headset Sidetone Controls feature lets the user adjust the headset sidetone levels from the phone preferences menu

 Four levels of sidetone settings are provided: High, Normal (default), Low and Off. The Normal (default) level is the existing side tone level

 This feature is for analog wired headsets only. It does not apply to BT headsets or wireless headset that control sidetone levels by their own DSP

58 58

(59)

Headset Sidetone Control

(60)

Features: Release 9.2(3)

 PLKs as Soft Keys

 FAC/CMC (SIP)

 Enhanced Version Negotiation for CME

 SSH Configurable

 Enhanced Call Forward Notification

 Calling Party Normalization

 Maximum CTL File Size

 SRST Notification

 Incoming Call Toast Timer

 HTTP Download – Image and Configuration

 Customized Wallpaper

 Assisted Directed Call Park (SIP)

 Classic Ring tones

 BT Handsfree profile (8945)

IP Phones 8941 and 8945 (Dec. 2011)

(61)

PLK as Softkey

 This feature allows following Programmable Line Keys as Softkeys from release 9.2(3) on both SCCP and SIP load:

‒ MCID ‒ Mobility ‒ QRT

‒ cBarge ‒ DND

(62)

FAC/CMC (SIP Only)

 8945 and 8941 IP Phones support FAC/CMC starting release 9.2(3) on SIP loads as it does on SCCP loads

‒ Forced Authorization Code (FAC) is used to determine if a user is authorized to make a particular class of calls (such as, intrastate, interstate, international, etc.). FAC can be triggered by a FAC enabled route pattern.

‒ Client Matter Code (CMC) is used to associate a call with a client so that a client can be billed. Clients are assigned Client Matter Codes. CMC can be triggered by a CMC enabled route pattern.

 A route pattern can have both FAC and CMC restrictions. In that

scenario, the user is prompted for FAC and then the CMC in sequence.

62 62

(63)

Enhanced Version Negotiation with CME

(SIP Only)

 The Enhanced Version Negotiation with Unified CME feature allows the phone to identify the version of Unified CME with which it is operating so that the phone can enable the correct set of supported features

(64)

Configurable SSH

 The SSH Access option allows the administrator to enable or disable the SSH Access setting on the phone using Cisco Unified CM Administration

 When you enable SSH access, the phone can accept SSH connections.

 When you disable SSH access, SSH connections to the phone are blocked.

 By default, SSH access is disabled.

64 64

(65)

Enhanced Call Forward Notification

 Prior to 9.2(3) release, there was no indication for the user to know

whether a call is forwarded by some other user during the ringing phase

 With 9.2(3), when a forwarded call is answered, 8941 and 8945 IP

Phones should not only display the caller number, but also the redirected number (the number from which the call was redirected) and the dialed number (the original dialed number)

 Administrator can enable/disable this feature from the DN configuration on the CUCM Administration interface

(66)

Calling Party Normalization

 This feature provides the normalization of a calling number into an E.164 number format then the called party can determine the calling party‟s

origin without ambiguity, so phone can dial out from call history directly.

 In Call History Details page, new field „Alternate number‟ is added to show E.164 number.

66 66

(67)

Maximum CTL File Size

 8945 and 8941 phones support CTL file size up to 64 KBytes.

 64 KBytes CTL file sizes can occur in large CUCM clusters. IP Phone

shows the CTL file size under Applications  Admin Settings  Security Setup  Trust List

(68)

SRST Notification

 8945 and 8941 IP Phones support SRST notification that alerts users when the phone falls back into SRST mode

 Phone shows a toast that always appears when it is in idle state. This

toast could disappear when there is any user input or the phone is in non-idle state. Upon registering back to the CUCM, the toast message goes away

 Toast message:“Service interruption”

68 68

(69)

Incoming Call Toast Timer

 The incoming call toast timer is now configurable from 3 seconds to 60 seconds. The default value is 5 seconds.

 This feature would be available via a system wide admin setting - Incoming Call Toast Timer.

 This parameter can be configured at three levels on CUCM: 1. System > Enterprise Phone Configuration

2. Device > Device Settings > Common Phone Profile 3. Device > Phone > Phone Configuration

(70)

HTTP Download – Image and Configuration

 8945 and 8941 phone download process will be enhanced by first

attempting to download all files via HTTP protocol - the port of http server used on CUCM is 6970 .

 If an HTTP connection is rejected, the phone will fall back to downloading via TFTP.

 If a timeout or file-not-found error is returned, the phone will proceed in the same manner as it does when these errors are returned while using the TFTP protocol.

 The fall back to TFTP will only occur if the TCP connection is rejected by the specified TFTP Server.

70 70

(71)

Customized Wallpaper

 8945 and 8941 phones will support

customized wallpaper using JPG or PNG format.

 Administrator will select an image before downloading it to the phone from TFTP server. IP phone has the ability to

preview all of images on the TFTP server when a user selects wallpaper menu on phone interface

 Administrator can enable/disable end

users to choose their own wallpapers for their phone on CUCM enterprise or

common setting. They can also specify the default wallpaper by setting image

(72)

Assisted Directed Call Park (SIP)

 Assisted directed Call Park is a transfer-based feature instead of standard Call Park which is a hold-based feature. With assisted directed call park, an active call gets parked immediately at the directed park slot that

associates with a BLF Directed Call Park feature button.

72 72

(73)

BT Handsfree Profile (8945 Only)

 IP Phone 8945 supports various Handsfree Profile features that enable you to use

handsfree devices (such as Bluetooth headsets) to perform certain tasks without having to handle the phone. For example, instead of pressing Redial on the phone, users can redial a number from their Bluetooth headset according to instructions from the headset manufacturer

 The following handsfree features apply to Bluetooth headsets that are used with the

Cisco Unified IP Phone 8945:

‒ Answer a call ‒ End a call

‒ Change the headset volume for a call ‒ Redial

‒ Caller ID ‒ Reject

‒ Resume a held call

 Handsfree devices may differ in how features are activated. Device manufacturers

(74)

Classic Ringtones

 The Classic Ringtones feature supports 29 ringtones: two embedded in the phone firmware and 27 downloaded from the Cisco Unified

Communications Manager. The supported ringtones are the same as those supported by other Cisco Unified IP Phones

74 74

(75)

(76)

Features: Release 9.2(4)

 Enlarge Unique Call Identifier

 Provide Dial Tone from Release Button

 Hide Video Option

IP Phones 8961, 9951, and 9971 (March, 2012)

(77)

Enlarge Unique Call Identifier

 This feature increases the font size of the Unique Call Identifier to the same size as the calling number.

(78)

Provide Dial Tone from Release Key

 Old behavior: The Release key will only

cause the phone to end the current call session

 New behavior: If the new feature is enabled,

the Release key will not only cause the phone to end the current session but also invoke the new call window

 This feature applies to IP phones 9971,

9951, and 8961

78 78

(79)

Feature Configuration

 This feature can be configured by the parameter “Provide Dial Tone from Release Key” at three levels in Cisco Unified Communications Manager

Administration pages: enterprise profile, common phone profile and phone configuration.

(80)

User Experience – New Call Window

80 80

(81)

Default Option to Hide Video

 Old behavior: The phone always displayed video view once a video call is established. The user has to press “Hide Video” soft key to switch to the “Hide Video” view

 New behavior: There is an option

that the phone can display the “Show Video” or “Hide Video” view by

default. The video is still being

transmitted to the remote party when the “Hide Video” view is displayed

 This feature does not affect other

video options such as Video On/Off, Video Mute and Auto Transmit Video

(82)

Feature Configuration

 This feature can be configured by the parameter “Hide Video By Default” at three levels in Cisco Unified Communications Manager Administration pages: enterprise profile, common phone profile and phone configuration.

 The default value is Disabled.

82 82

(83)

(84)

Features: Release 9.3(1)

IP Phones 6900 series (June, 2012) – These features may require CUCM 9.0

84  Device Invoked Recording

 Extension Mobility Cross Cluster Enhancement

 BLF for Call Lists

 Headset Sidetone control

 PLK support for Queue Statistics

 RTCP Behavior on Hold

 View Call Logs from Shared Line

(85)

Device invoked recording

 Previously recording feature was initiated by CUCM or CTI:

 Auto recording: invoked by CUCM automatically. It can‟t be stopped unless the call ends  Silent recording: invoked by existing CTI-silent interface. It can only be stopped from CTI

interface

 In UC 9.0, recording feature has been enhanced and it can be initiated by users in

two ways:

 Invoked by pressing ‟Record‟ Softkey  CTI-user interface

Different from auto and silent recording, these two ways of recording can be stopped by each other and there is an indication on phone to show that call is being recorded now

 Configure Device toggle recording on the phone

 Set phone‟s „Built In Bridge‟ to „On‟

 Select „Selective Call Recording Enabled‟ as „Recording Option‟

 Administrator configures‘Record‟ softkey to connected call status and assign this softkey

(86)

 The phones will support‘Record’softkey in CONNECTED state

 In connected state, upon pressing „Record‟ softkey, phone displays message „Conversation is being recorded‟ and softkey will change to „Stop Recording‟

 In recording status, press „Stop Recording‟, softkey will stop the recording, phone will change to connected status. If the user ends the call directly, the recording will also stop

 If the recording is already started silently, phone interface never changes - as if the recording never started. Upon pressing ‘Record‟ softkey, the phone never changes to recording state but prompts a message „Recording already in progress‟

 Recording could also be started by a CTI user. Upon invoking „Start‟ function of CTI user to start recording, phone interface changes to recording state just like when a user presses the „Record‟

softkey. If the user presses „Stop Recording‟ or invokes the „Stop‟ function of CTI user, recording will stop

 When recording is established, user presses ‘Hold’hard key, the recording will be stopped

automatically. Upon pressing ‘Resume’ soft key, the recording will be restarted automatically.

 While recording is already in progress, if a user presses the „Conference‟ hard key, recording stops automatically

 If recording fails to establish, phone prompts the message „Recording Failed‟

Device invoked recording - Scenarios

(87)

Extension Mobility Cross Cluster Enhancement

 This is an enhancement to the existing EMCC feature. During EMCC login, phone will

not change product specific configuration from VC (Visit Cluster) to HC(Home Cluster).

CUCM Side:

 Product specific configurations are set in phone configuration file in three XML tags: vendorConfig, commonConfig and enterpriseConfig tags. VC TFTP will add these three tags when it builds the mini config file

 VC TFTP while building mini configuration file will include product specific configuration details of VC. There is no change in HC TFTP while building the full configuration file for IP phone

Phone Side:

 IP phone that supports EMCC shall preserve its product specific configuration parameters derived from the three tags in VC mini configuration file. These parameters are cached before phone

downloads the full configuration file from HC TFTP

 Phone ignores product specific configuration parameters which are present in the full configuration file that got from HC TFTP. Moreover, phone uses cached parameters obtained from VC mini

configuration file.

(88)

BLF on Call Logs

 The BLF state icon will be added for each Call History item in the Call History list. The list can display the presence statuses of monitored line numbers

 Phones follow the Enterprise Parameter „BLF For Call Lists‟ in enterprise parameter:

 If it‟s disabled, the line numbers in the Call History list will not subscribe to the BLF notification and the BLF states will not be shown.

 If it‟s enabled, all the line numbers in the Call History list will be monitored and the BLF states will be shown

 The BLF states will notify the user that the lines are in these states: Unknown, Idle,

Busy and DND. If the monitored line is out of service, the BLF state is Unknown

IP Phones 6900 series – 6921, 6941, 6945, 6961

(89)

Headset Sidetone controls

 This feature allows end user to adjust the headset side tone level. Note that side tone configuration is for wired analog headsets only

 Headset sidetone configuration is added to

Preferences menu and it can be accessed from Applications > Preferences > Headset sidetone  The Preferences menu includes the Headset

sidetone menu options

 The sidetone options include 4 levels: High, Normal, Low, and Off.

(90)

PLK support Queue Statistics

 The above 6900 series phones support queue statistics for hunt lists invoked by

Phone Line Key „QueueStatus‟ and displays the information on the phone

 Phone will query queue statistics information from CUCM, upon receiving

CUCM’s response, phone will display it on phone screen. The queue statistics

includes hunt pilot DN, # of callers in queue, and the longest call waiting in queue

 Users can update queue statistics information by pressing „Refresh‟ softkey.

Phone can exit the statistics window by pressing the exit softkey

IP Phones 6900 series – 6921, 6941, 6945, 6961

(91)

RTCP behavior while on hold (SIP only)

 Prior to 9.3(1), the above phone models closed the RTCP port if media attribute was sendonly, receiveonly, or inactive. If a call is placed on hold, media attribute in SDP will be changed to

inactive, phone closes the RTCP port, in this case, gateway will detect the RTCP port is closed and drop the call

 Since 9.3(1), the above SIP phones will keep RTCP port open when media attribute is changed to be sendonly, receiveonly, or inactive. That is, the directionality of the media stream has no

impact on the RTCP usage

 To be more elaborate, some typical scenarios are listed below assuming that the phone is making a call with destination through the media gateway:

 If phone holds the call, RTP port will close, while RTCP port remains open

 If phone resumes a held call, use the same port to open RTP, RTCP port keeps open, no re-open needed

 If phone is put on hold, and MOH is not enabled, RTP port is closed and RTCP remain open; and when this call is resumed, RTP will reopen using the same port while RTCP is not impacted

 If phone is put on hold, MOH enabled, RTP port closed and then reopened to hear music using the same port. RTCP port remains open

(92)

View Call Logs from Shared Line

 This feature enables users to view remotely received and placed calls on

shared lines logged in the call history menu

 To view all the call history logs, users can open the Call History application. In the “Call History: Details” screen, the call disposition text indicates if the call is received/placed locally or remotely

 Prior to 9.3(1), users could only see the missed call logs for shared line

 The general principle here is that local should log the same thing as the

remote shared line appearance, and no need to identify which device performed the remote activity on the shared line appearance

Locally/Remotely Placed Locally/Remotely Received

IP Phones 6900 series – 6921, 6941, 6945, 6961

(93)

 The above phones supported distinctive ring feature for On-net/Off-net or line based, but the ring cadence was fixed, and based on US standard only

 Ring cadence in US standard is opposite to Japan standard

 US: 1 ring for On-net, 2 ring for Off-net  Japan: 1 ring for Off-net, 2 ring for On-net

 To support Japan standard, the ring cadence should be configurable according to locale. Release 9.3(1) introduces a new parameter, Ring Locale, in common profile and phone specific profile. It has two options:

 Default: phone uses the existing ring cadence and ringtone.

 Japan: phone uses Japanese ring cadence, and users cannot customize Ringtones  (Ringtone menu will not appear on the phone preferences menu)

 The Japan ring cadence is described as below (ring volume and frequency are the same as ring default setting)

Ring cadence localization (Japan)

(94)

Telepresence Endpoints Registered to

(95)

(96)

…and Where We’re Going

96 96

(97)

Endpoints Can Now Be Deployed

(98)

UC Manager Line-Side Features Supported

on E20, EX, MX, SX and C-Series

(99)

Features Supported / Not Supported

 Networking & QoS

 Cisco Discovery Protocol  Auxiliary VLANs

 Medianet: AutoQoS / Smartports

 DSCP and 802.1p as per UCM service parameters  Discard 802.1Q/p tagged frames received on PC port  RTP port range as per UCM service parameters

 802.1X Aux-VLAN override and MAC-Auth Bypass

x 802.1X Proxy-EAPoL Logoff – Extensible Auth. Protocol

 802.1X Supplicant

 Provisioning

 DHCP Option 150

 Automatic configuration and firmware downloads

 HTTP port 6970, not TFTP

 device defaults and device specific loads

 Registration and Signaling

 Auto-Registration  SIP - Non Secure

 SIP - Digest Authentication  SIP – TLS (as of TE/TC6.0)  Primary UCM node

x Secondary/Tertiary UCM nodes failover/fallback

x SRST

 Register using E.164 (Directory Number)

 Alpha-numeric URI (as of UCM 9.0 and TE6.0/TC6.0)

x H.323

 Service Control Events

 Reset / Restart / Check Config

(100)

Features Supported / Not Supported

 Directories

 Corporate Directory

 Personal Favorites / Speed dials

x Personal Directory

x TMS-style hierarchical phone books

 Localization

 User Interface Local (chosen locally on the phone, not provisioned in UCM)

x Network locals (tones / cadences)

 Shared Line Appearances (E20 only)

 Remote State Notifications  Hold / Resume

 cBarge

 Unified Mobility

 Hand-off from mobile to desk x Hand-off from desk to mobile

 Calling Features

 Enbloc dialing

x Off-Hook dialing - KPML

x Forced Auth Codes / Client Matter Codes  Alpha-numeric URI dialing

 +, * and # character dialing  Hold / Resume  Transfer  Blind  Attended x Early Attended  Line Appearance

 Multiple calls on single line appearance (1 active, 4 held) x Multiple Line Appearances

 Call Forwarding

 Busy, No Answer, No Coverage, Unregistered

 All – supported only on E20 (planned for TE6.0 on EX) x Park / Pickup

 Music on Hold

 Unicast x Multicast

E20, EX, MX, SX and C-Series Endpoints Registered to UC Manager

100 100

(101)

Summary

This session helped understand:

 Recent IP Phone feature additions and updates

 Configuration steps associated with the new features

 User Experience associated with the new features

 Features on E20, EX, MX, SX, and C-Series Endpoints Registered natively to UC Manager

(102)

Related Sessions

A few related sessions:

 BRKEVT-2802 Cisco Telepresence: deploying and provisioning video

endpoints

 BRKEVT-2805 Understanding and troubleshooting EX-Series Personal

Telepresence systems and C-Series codecs

 BRKEVT-2100 Designing and Deploying IP Video Telephony Networks

 BRKEVT-2480 Cisco UC Soft clients: Deploying Cisco Jabber desktop

clients

 BRKEVT-2785 Understanding Cisco Unified Presence

(103)

Complete Your Online

Session Evaluation

 Give us your feedback and you could win fabulous prizes.

Winners announced daily.

 Receive 20 Passport points for each session evaluation you complete.

 Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.

Don‟t forget to activate your

Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the

(104)

Final Thoughts

 Get hands-on experience with the Walk-in Labs located in World of Solutions, booth 1042

 Come see demos of many key solutions and products in the main Cisco booth 2924

 Visit www.ciscoLive365.com after the event for updated PDFs, on-demand session videos, networking, and more!

 Follow Cisco Live! using social media:

‒ Facebook: https://www.facebook.com/ciscoliveus

‒ Twitter: https://twitter.com/#!/CiscoLive

‒ LinkedIn Group: http://linkd.in/CiscoLI

(105)