I guess by looking at how SQL Server DB replication works, you'd be able to figure out what to put in there.
However, you should consider CCM to be just like any other 3 tier system.. with the database being the third tier and a business layer in the middle. If you write directly to the database, you bypass the business layer, which means that you'll bypass certain logic that ensures a consistent database.
Starting with CCM 5.0, there's an axl command to write into the CCM database, and the schema has been extended quite a bit with a lot of consistency information.. you'll note that depending on which table, there's quite a bit of processing to be done to ensure consistency, which makes AXL a lot more attractive as all those checks are done automatically for you that way.
Just to make you scared, once I needed to create a lot of pickup groups for a CCM cluster with 2000 users. I figured out what the pickup groups look like in the CCM database and sort of added the new ones in a couple of minutes then walked away to have a beer.
Next day I found out pickup groups do not work at all and I spent a week correcting what I broke in a couple of minutes.
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...