This feature is built into Cisco Jabber and provides a way to migrate contacts in the buddy list and other common user preferences from Jabber to Webex. The data is encrypted. You just need to configure some settings before users see this option pop up automatically in Jabber.
For more information about how to configure Jabber users to move to Webex, see this article.
During a call, you can access call statistics such as video frame rate, audio codec, packet loss, jitter, and bandwidth usage. An indicator also appears that shows the call environment that you're on (your administrator or support team may need this information for troubleshooting purposes).
Follow the steps or have your users follow the steps in Access Call Statistics to access statistics for a call in Webex for desktop or mobile.
| Step 1 |
From the customer view in https://admin.webex.com, go to and click the search drop-down to choose a device type. After you choose Type, the results appear with all the devices in your organization, including headsets.
|
||
| Step 2 |
(Optional) Check the check box next to any headset entries that you want to export a local record of, click Export as CSV, check attributes that you want to include, and then click Export. |
||
| Step 3 |
Click a headset entry to open an overview pane that shows the device status, who it last was connected to, search tags, actions you can take on the device (delete) and further details (connection type, serial number, and software channel). |
If you see registration issues when trying to use Calling in Webex (Unified CM), go through these checklist items before you submit a ticket.
A warning icon appear in the app if Webex failed to register to Unified CM because of a sign in failure or other reason. A summary of the reason appears next to the icon.
 Tip |
You can hover over the icon to show an error message that may give you clues about what to troubleshoot. You can also click the icon to see if there are any next steps that you have to take to resolve the issue (such as sign into phone services or start a new session).
See the Error Messages documentation for more information on the errors that may appear in Webex. |
 Note |
If https://status.webex.com shows a Webex cloud full or partial outage, Calling in Webex (Unified CM) still works, as long as the call type is a Unified CM call and goes through Unified CM infrastructure. If Unified CM is not reachable from Webex, users can use the Self Care Portal (a link is available in Webex) to set up Single Number Reach (SNR) so that calls get routed to mobile through the PSTN. For administrative steps, see the Cisco Unified Mobility Features chapter in the Feature Configuration Guide for Cisco Unified Communications Manager. For user self-care configuration, see the Self Care Portal User Guide. |
| Step 1 |
Disable Hybrid Calling for users in Control Hub. (See the Prepare Your Environment chapter for further details.) |
| Step 2 |
Verify that any CTI-RD or Cisco Spark-RD was removed from Unified CM for the user; if not, delete any stray remote devices. (See the Prepare Your Environment chapter for further details.) |
| Step 3 |
If your organization is enabled for a different call behavior (such as a calling app cross launch) in Control Hub, disable this feature and reselect Calling in Webex (Unified CM) because Unified CM registration and cross-launch cannot be enabled together. |
| Step 4 |
Exit Jabber if it's installed on the same machine, because Jabber and Webex cannot both be registered to Unified CM in softphone mode at the same time. |
| Step 5 |
Check other configuration on Unified CM. Some common culprits include the following:
|
If you addressed all of these steps and issues still persist, restart Webex and then choose to submit logs and open a case for the support team to investigate.
Feedback