Resolve "Device Already in Use" Error When Adding 8841 Phone to Webex Calling

Available Languages

Download Options

  • PDF     (17.4 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (86.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (71.5 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:November 10, 2026
Document ID:226575

Bias-Free Language

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.

Contents

Issue

When attempting to add a Cisco 8841 phone to Webex Calling, the operation fails with an ATLAS error indicating the device is already in use. The specific error message received is:

Add device failed. TrackingID: ATLAS_12345678-ec69-4de1-8e8d-43b4b773801e_30. Timestamp: 2026-07-14 10:47:08 PDT (2026-07-14 17:47:08 UTC)

This error occurs even when the device does not appear to be provisioned in any Multitenant or Carrier organization, preventing the successful addition of the phone to the Webex Calling service.

Environment

  • Cisco 8841 IP Phone

  • Webex Calling service

  • Partner organization type

  • Admin persona attempting device configuration

Resolution

The resolution requires a Webex Calling TAC case to be opened and involves manually disassociating the MAC address from the backend system through Cisco support intervention. These next steps outline the resolution process.

Step 1: Verify Device Status in Provisioning Tools

The support engineer reviews internal provisioning tools and lookup outputs to confirm the MAC address status. In this case, the tools showed that the device was not provisioned in any Multitenant or Carrier organization, but the MAC address was identified as "stuck" in the backend and unable to disassociate automatically.

Step 2: Manual Backend Disassociation

The support engineer performs a manual disassociation of the MAC address from the backend system. This action frees up the device and removes the association that was preventing the device from being added to the new organization.

Step 3: Retry Device Addition

After the manual disassociation is completed, attempt to add the Cisco 8841 phone to Webex Calling again using the same MAC address and user configuration that previously failed.

Step 4: Verify Successful Addition

Confirm that the device can now be successfully added to the Webex Calling service without receiving the "device already in use" error. The device must appear properly provisioned for the intended user.

Cause

The MAC address becomes stuck in the backend system and is unable to disassociate automatically from previous associations. This condition prevents the device from being added to a new organization or user configuration, even when the device does not appear to be actively provisioned in any current Multitenant or Carrier organization. The automatic disassociation process fails to clear the backend association, requiring manual intervention to free the device.

Related Content

Revision History

Revision Publish Date Comments
1.0
09-Nov-2026
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Adrian Esquillo
    Technical Consulting Engineer

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products