Third-party devices are obviously not certified or supported by Cisco. What matters is the RFC compliance of those devices. SIP is governed by several RFCs including RFC3261, RFC2833, RFC2543. There are several others as well. The only thing Cisco would support is if UCM is not complying with the SIP RFCs properly when signaling to devices. If the device complies with the RFC, it should work. Basically you'll need to test and see what the behavior is.
Cisco participates in an independent third party testing and interoperability verification process being offered by tekVizion which has been established to allow 3rd party vendors to test and verify the interoperability of their end points with CallManager and CallManager Express.
Third-party SIP phones are supported by CUCM. The SIP Verified program tests 3rd-party SIP phones for compatibility with CUCM. See:
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...