Hi Marc,   The  CP-8800-V-KEM is not supported on the 8851/61's as they now use the CP-8800-A-KEM and the 8865's use only the V-KEM;   "This means that you cannot mix audio expansion modules with video expansion modules. You also cannot use a video expansion module on an audio phone or an audio expansion module on a video phone."   From;   https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7800-8800/english/accessories/p881_b_accessorie-guide-for-cisco-ip/p881_b_accessorie-guide-for-cisco-ip_chapter_01.pdf   You also see the distinction between the two module/models in this doc;   For 8865 deployments please consider the CP-8800-V-KEM=   For 8851/61 deployments please consider the CP-8800-A-KEM=   From;   https://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-8800-series/eos-eol-notice-c51-741310.html   Cheers! Rob     ... View more

Hi Joshua,   I think it may actually be this bug;   Cluster reboot needed for device pack in CUCM version 11.5(1) CSCvk22694   Description Symptom: phone showing "none" in registration status in CUCM web page. Conditions: as per documentations: https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/213290-configure-device-pack-on-cisco-call-mana.html https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/Devpacks_admin/CMDP_BK_CD82F19C_00_cisco-unified-communications-manager-device/Cisco_Unified_Communications_Manager_Device_Package_Installation_and_Administration.html "When you apply a device package to enable new device support, a cluster-wide reboot is not required for CUCM version 11.5(1) or later. Instead, after you add the device pack, follow this in CUCM Restart the Cisco Tomcat service on all nodes Restart Cisco TFTP on all servers, where this service is running Restart Cisco CallManager on the Publisher. If you're not running the Cisco CallManager service on the Publisher, you can skip this step." however when adding device pack 11.5(1)(15078-1) (cmterm-devicepack11.5.1.15078-1.cop.sgn) into CUCM 11.5(1) SU1, in order to add 8832 Cisco IP Conference Phone, the phone gets registered fine, but it doesn't show up registered in CUCM web page. it looks like following documentation steps doesn't allow for the phone to show up registered. Workaround: Reboot the cluster   Cheers! Rob ... View more

Hi Claudio,   Yes the 210-060 would work for re certification as it is considered an Associate level exam;   CCNA Collaboration certifications are valid for three years. To recertify, pass ONE of the following before the certification expiration date: Pass any current Associate-level exam except for the ICND1 exam https://www.cisco.com/c/en_ca/training-events/career-certifications/associate/ccna-collaboration.html#~Recert   Cheers! Rob ... View more

Hi Brent,   The only model that you listed that is nearing end of support is the 7920. It is one of the "Deprecated" models beginning in CUCM 11.5(x);   The following phone models are deprecated and are not supported by Cisco Unified Communications Manager Release 11.5(x). If you are using any of these phone models and you upgrade to release 11.5(x), you will be unable to use the phone after the upgrade. After you switch over to the new release, registration on the phone will be blocked. Cisco IP Phone 12 S   Cisco IP Phone 12 SP   Cisco IP Phone 12 SP+   Cisco IP Phone 30 SP+   Cisco IP Phone 30 VIP   Cisco Unified IP Phone 7902G   Cisco Unified IP Phone 7905G   Cisco Unified IP Phone 7910   Cisco Unified IP Phone 7910G   Cisco Unified IP Phone 7910+SW   Cisco Unified IP Phone 7910G+SW   Cisco Unified IP Phone 7912G   Cisco Unified Wireless IP Phone 7920   Cisco Unified IP Conference Station 7935 From this Field Notice;   https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/fieldNotice/cucm_b_fn-deprecated-phone-models-1151.html   You're good to go with the 8821;   Cisco Unified Communications Manager 9.1(2) 9.1(2),10.5(2), 11.0(1), 11.5(1),and later     https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8821/firmware/11-0-2/w882_b_cisco-8821-rns-110002.html     Cheers! Rob   ... View more

Hi there,   Just wanted to add a note to the good tips from my friend Jonathan.   If you look closely at the RJ11 ends on the working vs non-working quick disconnect cords you will likely see a wiring difference. You will need the part number listed below.   I believe the required cord is actually the U10 (the U10 is used with almost all Cisco phone models) rather than the A10 which is likely the non-working cord. You can check via the Plantronics compatibility guide;   Coil Cord to QD Modular Plug Model:   U10 Part Number:   26716-01   http://www.plantronics.com/ca/compatibility-guide/#/detail/?key=sku6790027sku4230017   Cheers! Rob ... View more

Hi Rob,   Welcome aboard!   The 7937 is not going to be able to be modified in the way that you desire and it is actually an "End of Life" product.   From;   https://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-7940g/end_of_life_notice_c51-729487.html   You would need to look at installing the new 8831 Conference phone which has the ability to have 2 units "daisy chained" together with multiple mics to better support large conference rooms. Here's a clip;   Expanded room coverage ●   160-degrees conical pattern provides even coverage of listening area. ●   Four Hemi-Cardioid microphones are perfectly spaced so that they combine to provide a 180-degree pick-up pattern around the device. Speech is captured at the same level at all points around the Cisco Unified IP Conference Phone 8831. ●   Ability to grow to fit a variety of room needs. ◦    Small Office (base unit) ◦    Standard Conference Room (base unit and 2 wired or wireless extension microphones) ◦    Boardroom (daisy chaining two base units) ◦    Large Boardroom (daisy chaining two base units and 2 wired or wireless extension microphones)   From;   https://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-8800-series/data_sheet_c78-726887.html   Cheers! Rob ... View more

Hi there,   You may be hitting this bug;   AXL connection to Unity Connection/Call Manager fails (v. 11.5.1.11900-26) CSCvc84307   Cheers! Rob ... View more