The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document provides a basic configuration example for Jabber for Windows 10.5 call pickup and Hunt Group call answer.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
In this case Jabber CSF has an extension of 1004 and the need is to add the pickup group in its DN page. See this screenshot for details.
Once Jabber accepts these settings, this is what you will see activated in Jabber for Windows.
Click the "Log into Hunt Groups" radio button in order to ensure Jabber for Windows is enabled to answer calls as a member of the Hunt Group. As soon as this is configured, the Hunt Group & Pickup icon in Jabber displays a green button that confirms Jabber is enabled for Hunt Group and call pickup answer mode.
In this test example, this is what is set up:
In summary, a call was placed to the Hunt pilot (7000) and it was verified that the "Log into Hunt groups" option was enabled, otherwise the call would not make it to the Jabber for Windows .csf extension.
Use this section in order to confirm that your configuration works properly.
Since 1002 (a desk phone at extension 7975 in the lab) and 1004 (test Jabber for Windows CSF extension) are made to point to the same call pickup group, if 1002 is called then Jabber is prompted for a call pickup as both extensions point to the same call pickup group. Here is how Jabber receives the notification:
Calling Party number : 1000
Called Party number : 1002
Call pickup group number and name: 4000 (test); both 1000 and 1002 are part of this call pickup group, hence Jabber receives the call pickup group call as seen in this screen capture.
Here is a notification received when Jabber for Windows receives the call as per the "distribution algorithm" in Line group. Details of the call that was placed to lead to the mentioned notification are shown here:
Calling Party : 1000
Called Party : 7000 ( hunt pilot pattern)
Jabber CSF ( ext :1004) is member of the line group point via Hunt list to this Hunt Group
There is currently no specific troubleshooting information available for this configuration.