I use the term "phone lines" here simply because when a phone use toggles HLog to false, they are logged out of all line groups and this includes all lines on the phone. False means that the lines are logged out of line groups. True means that the phone lines are logged into all line groups. DeviceHlogDynamic This table simply keeps trag of whether a device has the "HLOG" status toggled.Note, that Hunt Lists are also stored in the Device table. Since users log into/out of line groups from a device level (instead of the line level), you will need to know which phone you are dealing with. Device This table will contain devices like the IP phone.It will match up phone line directory numbers in NumPlan to the IP phones in the Device table. DeviceNumPlanMap This is another mapping table.For your purposes you need this value to get to identify a device and you may want to use it for display purposes. This includes phone lines, Hunt Pilots, translations, route patterns, etc. NumPlan This is the master table for all digit patterns configured in your CUCM cluster.LineGroupNumPlanMap This will map a line group to a specific numplan entry, such as a phone line directory number.LineGroup This table defines the line group name, hunt algorithms, etc.The table will be named (x).įor some basic examples on using the various table types, you can check out one of the posts I wrote on the Chesapeake NetCraftsmen blog site.įrom a db perspective the following Informix database tables store information related to line groups and hunt lists: ik(x): This is used when a field is de-referencing another unique record in the same table as the source record.The table will be named type(x) and the foreign key will always be enum. tk(x): This is a type key (enumerator) in another table.The table will be named (x) and the "_(y)" is a descriptor which usually indicates that in a given record there is more than one field pointing to the same foreign table. fk(x)_(y): This is a foreign key (unique value) in another table.That table will be named (x) and the foreign key field will always be pkid. fk(x): This is a foreign key (unique value) in another table.Whenever a field in a table is linked to another table or another record in the same table, the following field name conventions are used: Enumeration or "type" tables also have a unique key that is always named: enum. Standard tables and mapping tables use a unique key that is always named: pkid. Mapping Tables: Basically connects unique records from one table to unique records in another table. That is understating their purpose somewhat, but from a SQL query point of view you will use type tables mainly to resolve enumerator values to a human readable format. Standard Tables: Tables which contain the core data values of a particular object like devices, number patterns, end users, etc.Įnumeration or "type" Tables: Used by other tables to resolve enumerator IDs to some name or moniker.
I classify tables in the CUCM databases into three (3) categories: Anyone looking to build a custom query to run against their CUCM system may want to take a look at the following resources: