Finding custom Jabber configuration files can be a pain. These are set via a “Remote Support Field”, which internally to CUCM is stored inside a vendorConfig when pulling the information via AXL.

Sometimes there is a need to see which devices are using custom Jabber configuration files, and SQL is a handy tool to extract this. The DB tables are a little confusing, and without getting into too much detail, the data is stored as XML, usually (almost always) in 1 table, but in theory in more. The following query can be used to find all devices on the system which are configured to use custom configuration files:

SELECT d.name
FROM devicexml4k x
INNER JOIN device d ON d.pkid=x.fkdevice
WHERE x.xml MATCHES '*<ciscoSupportField>*.xml</ciscoSupportField>*'
UNION
SELECT d.name
FROM devicexml8k x
INNER JOIN device d ON d.pkid=x.fkdevice
WHERE x.xml MATCHES '*<ciscoSupportField>*.xml</ciscoSupportField>*'
UNION
SELECT d.name
FROM devicexml16k x
INNER JOIN device d ON d.pkid=x.fkdevice
WHERE x.xml MATCHES '*<ciscoSupportField>*.xml</ciscoSupportField>*'
ORDER BY d.name