We provide a reasonable coverage of device types, but we can’t know them all. Did you know that you can edit existing names or add new ones?
Let’s jump right into an example of creating a new device type.
Suppose you have a situation where there are some Alpine Horns that you have connected to CallManager. (I’ll bet you can hear me now!)
Also suppose they are all showing up with a device name that starts with AN.
Unfortunately, they do not show up with a dest_device_type of “alpenhorn.” Whatever are we to do?
(Note, please see the disclaimers at the end of this blog entry!)
Our first task is to create the field transformation.
^(CSF\w+), which matches items like CSFblahblah123blah
^(AN\w+)so that it will match items like ANblahblah123blah
destJabberDeviceis set to the entire original name (
dest_device_typeis set to the string
When finished, you’ll have something like this:After that you should have a new field transform called cisco-cdr-custom-dest-alphorn. Find it and, in order to let everyone partake of alphorn naming goodness, change it’s permissions so everyone who is using the CDR app can read it:
You will very, very likely want to repeat the above steps, starting with cisco-cdr-origjabberphone, to make the originating side transform, too!
Now that we have the transform, we can assign it to where we need it to be seen by creating an extraction that references that transform.
The result:After that you should have a new field extraction called cucm_cdr : REPORT-cisco-cdr-custom-dest-alphorn. When you find it we need to fix permissions again, much like the last time
You will very, very likely want to repeat the above steps and create a cisco-cdr-custom-orig-alphorn to make the originating side transform, too!
I am pretty sure that Alpine Horns are NOT registered under Cisco CallManager as devices that start with “AN”, so you should only take this as an example, not as truth.
Also note that I cannot find a canonical way to spell Alphorn/Alpenhorn/Alpine Horn so I mixed it up a little to be inclusive!