Source record · tier 2 current vendor documentation
Add your customer managed device
- Publisher
- Cisco
- URL
- https://help.webex.com/en-us/article/nemh93t/Add-your-customer-managed-device
- Published
- 2026-02-09
- Updated
- unknown
- Accessed
- 2026-09-30
- HTTP status
- 200
- License
- Cisco proprietary; no-redistribution; short excerpts and locators only
Source notes citing this source
- Third-party ATAs can be added to Webex Calling as customer managed devices, for which Webex supplies SIP credentials and outbound proxy details but no configuration file, and Cisco Technical Support does not investigate issues with devices connected through that option. in context
- To add a customer-managed device to a user, the administrator goes to Management, Devices, Add device in Control Hub, selects Personal usage, names the owner, chooses Customer Managed Devices as the device type, selects the device vendor, enters the MAC address, and confirms the disclaimer before saving. in context
- To add a customer-managed device to a new workspace, the administrator goes to Management, Devices, Add device, selects Shared usage then New workspace, names the workspace, chooses the customer-managed device type, vendor and MAC address, and assigns the calling service, location and phone number. in context
- For a customer-managed device the customer provisions the device manually, owns the SIP authentication credential, and is responsible for any fraud arising from a failure to secure it. in context
- Removing a customer-managed device means deleting its lines under Configure Lines and then the device in Control Hub, and the administrator must also remove the SIP line data from the physical device for every line removed. in context
- A customer-managed device must be provisioned to use DNS SRV, which resolves the domain given as the Outbound Proxy. in context
- Cisco's field-mapping example puts the Line ID user part in the phone's address or user name, the SIP Username in the authentication user ID or register name, the SIP Password in the authentication password, the Outbound Proxy in the outbound proxy address, and the Line ID domain part in the SIP server address. in context
- After a customer-managed device is added, Control Hub displays the Line ID (a user part and a domain part), the SIP Username, the SIP Password and the Outbound Proxy address. in context
- Customer-managed devices offer two generic SIP profiles, Generic SIP Phone and Generic SIP Gateway, intended for SIP-TLS 1.2 compliant devices. in context
- Cisco says minimum firmware requirements apply to customer-managed devices and refers the reader to the third-party vendor's documentation for them. in context
- Customer-managed devices are not supported when adding devices in bulk. in context
- Cisco Technical Support does not investigate issues with devices that connect through the customer-managed provisioning option. in context
- The confirmation shown when a customer-managed device is added is the last time the SIP password can be seen in full. in context
- The SIP password of a customer-managed device is regenerated from Management, Devices, the device's Details, Reset Password, and the new password must be copied when it is shown. in context
- In Cisco's Poly and Yealink example, both the Outbound Proxy and Server 1 entries on a customer-managed device are set to Port 0 and Transport TLS. in context
- The customer-managed device option lets an enterprise administrator provision third-party SIP devices such as door phones, overhead pagers, analog adapters and digital fax solutions on Webex Calling. in context
- Every third-party device added as a customer-managed device must support the Webex Calling security requirements. in context
- A shared line is added to a customer-managed device from the device's Configure Lines page by adding a shared port configuration, and the SIP username, password and Outbound Proxy saved from the first line are used for the added line when provisioning the physical device. in context
- Setting the port to 0 alongside the DNS SRV instruction implies the device is meant to learn the signalling port from the SRV record rather than from a statically entered port. inferred in context
- A workspace with a professional workspace license can have up to five customer-managed devices, and a workspace with a common area workspace license can have only one device. in context
Cite this source record
APA
WarmTransfer. (2026, February 9). Add your customer managed device. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-nemh93t-add-customer-managed-device
BibTeX
@misc{warmtransfer-cisco-help-nemh93t-add-customer-managed-device,
title = {Add your customer managed device},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-help-nemh93t-add-customer-managed-device},
note = {Cisco, accessed 2026-09-30}
}