Jabber Pickup Groups

Cisco recently released Jabber for Windows 10.5 which introduces support for notification of calls to hunt groups & group pickup capability. However these features aren't enabled by default & the Call Pickup/Hunt Group sections in the Jabber Jabber deployment guide don't actually tell you this, nor does the release notes or the advanced functionality guide. To enable these features you need to add some parameters to jabber-config.xml, the deployment guide does list these parameters in the Client Configuration > Configure Users > Policies Parameters > On-Premises Policies section.
Below is an example jabber-config.xml that enable hunt group notification, pickup & other group pickup:

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Policies>
   <EnableCallPickup>true</EnableCallPickup>
   <EnableOtherGroupPickup>true</EnableOtherGroupPickup>
   <EnableHuntGroup>true</EnableHuntGroup>
 </Policies>
</config>

As per usual, this needs to be uploaded to all your TFTP servers & the TFTP service restarted.

HLog and 6900 Series Phones

Unfortunately the 6900 series phones don't have any visible notification of whether or not the phone is logged into hunt groups. This means that once the message displayed after pressing the HLog softkey disappears, there's no way of telling if your phone will take calls from hunt groups, other than to press HLog again. This is a rather bizarre omission given that queuing on hunt pilots is one of the big new features in CUCM 9.x & that in 9.0 it actually automatically HLogs you out if you don't answer a call from a hunt pilot with queuing enable. Thus it's easy to get into a situation where no one is receiving calls from hunt groups & they have no idea why.
Thankfully in CUCM 9.1 you can disable the auto HLog out of phones via "Automatically Logout Hunt Member on No Answer" within the line group settings. But this still leaves 6900 series phones with no indication of HLog status. The solution is to use a custom phone button template with one of the buttons being the HLog PLK, for example:

The LED on that button then indicates whether or not the phone is logged in to hunt groups. This is actually pretty handy for 7900 series phones too, as their "Logged out of Hunt Group" status message gets overwritten by the number of missed calls status message.

CME Hunt Group Final Not Being Reached

Given the following configuration, what do you think will happen when 7343 is called and no one in the hunt group answers?

ephone-dn 1 dual-line
 number 7241
 label Kathleen
 name Kathleen
 call-forward busy 5000
 call-forward noan 5000 timeout 20
 huntstop channel
ephone-dn 2 dual-line
 number 7254
 label Eleanor
 name Eleanor
 call-forward busy 5000
 call-forward noan 5000 timeout 20
 huntstop channel
ephone-dn 3 dual-line
 number 7258
 label Natasha
 name Natasha
 call-forward busy 5000
 call-forward noan 5000 timeout 20
 huntstop channel

voice hunt-group 5 parallel
 final 5000
 list 7254,7258,7241
 timeout 30
 pilot 7343

Contrary to expectations, the call doesn't get forwarded to the hunt group final number of 5000. This is becaue CME won't ever use the final number in a hunt group if the time out on the hunt group is greater than the time out defined in the ephone-dns!