How Cisco CUCM devices and profiles are allocated

When performing a Cisco CUCM audit, the configuration of the platform can be made in a number of seemingly diverse ways. To this end, the UCentric decoder supports several methodolgies and rulesets to normalise this data in the best way possible.

There are two command line switches that can be used to affect the order and way in which it is processed, --allowduplicates and --usersfirst These switches are switched “off” by default

Main Capture logic

The main capture of users and devices is processed in the following order

phone.csv                           <-- Will create new "Devices" for all entries
deviceprofile.csv                   <-- Will Update or add new "Profile" (or add duplicate 'Profile' if --allowduplicates)
enduser.csv                         <-- Will Update or add new "Profile"
callingpartytranspattern.csv

When processing the phone.csv and deviceprofile.csv, the following actions are taken:-

Device/Profile Type

The primary type “Phone” (Physical) if it comes from phone.csv and “Device Profile” if it comes from deviceprofile.csv or enduser.csv
If the [Device Type] column contains FXS, VGC, ATA or Analog, then the device is determined to be an analog phone
If the [Device Type] column contains Jabber, Android, iPhone or Unified Client then the “Softphone” tag is set

When processing phone.csv or deviceprofile.csv If a device or profile already exists, then it is updated with any additional information that exists in the previous file unless the --allowduplicates flag is set, in which case there will be 2 entries with the same DN (Directory number), one as a ‘Phone’ the other as a ‘Profile’ - e.g. if “TELEPHONE NUMBER” 1234 exists in phone.csv and deviceprofile.csv

DDIs

When looking at the callingpartytranspattern.csv file, in an entry contains “DDI” in the [DESCRIPTION] column and the [PATTERN] matches an Extension number, then all users and devices matching the Extension number are updated to have a DDI that is taken from the [CALLING PARTY TRANSFORMATION MASK]

Override the processing order

When peforming the audit and option can be added to the command line of the Universal Decoder

--usersfirst

This will cause the enduser.csv file to be processed before the phone.csv and deviceprofile.csv in the following order

enduser.csv                     <-- Will create new 'Device Profile' for all entries
phone.csv                       <-- Will Update or add if missing (or add duplicate "Device" if --allowduplicates)
deviceprofile.csv               <-- Will Update or add if missing (or add duplicate "Profile" if --allowduplicates)
callingpartytranspattern.csv    <-- Will insert DDIs