This topic is a chance to clarify your questions about Cisco Unified Communications Manager (Unified CM) Bulk Administration Tool (BAT) and the best practices to solve its common issues.
This session will help CUCM administrators with using BAT to solve day-to-day administrative tasks. If you've ever thought "I wish I could…” bulk edit the description field for all of your phones; find a way to make the Home Cluster checkbox consistent in multiple clusters; migrate a single phone to a new model; modify the Voice Mail Profile field on lines in bulk; deploy Access Lists for Single Number Reach users in bulk; deploy a set of Abbreviated Dials across multiple phones, or work with CSV and TAR files for editing the database.
To participate in this event, please use the button below to ask your questions
Ask questions from Tuesday 14th to Friday 17th of January, 2020
Maren might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Unified Communications Infrastructure community.
**Helpful votes Encourage Participation! **
Please be sure to rate the Answers to Questions
Here is a set of instructions I sent to a student of mine that needed to do this (which is how I figured it out). BE SURE TO DO TEST RUNS before you do this on a widespread basis.
NOTE: The following works for a single phone model. If you have multiple phone models you will need a different Phone Template for each model and a separate job.
Step 1: Set up a BAT Phone Template:
Step 2: Create Phone File Format
Step 3: Export the Phones to be Modified
Step 4: Modify the resulting CSV file and re-upload to CUCM
Step 5: Use Insert Phones to Apply the Changes
I have successfully used this procedure several times. That said, I sent these instructions to one of my students and he could not get it to work even after we worked together (via message) to verify steps. This tells me I may have mis-worded a step but I don't know which one. Essentially, I'm saying to use your best judgement and that you may have to poke around a bit to get it to work in your environment.
I would like to ask regarding Phone Templates.
For example I am going insert phones using BAT --> Phones --> Insert phones.
What is purpose of Phone template ? Does it mean that data in CSV file have priority and all other options (which are not in CSV file) will be configured according to phone template ?
Thank you in advance
You can think of the phone template (and the line templates that you build into the phone template) as the 'common settings for all phones/lines built on that template'. The rules of the interaction between the CSV file and the template are:
So, essentially, you are correct in saying that the CSV file has priority over the template during imports.
Let me know if you have further questions.
I recently came across an issue when trying to import calling party transformation patterns using an export file. I'm getting the following unmapped exception, 'Unmapped Exception bad header in block 0 record 3, header magic is not 'ustar' or unix-style zeros, it is '76737871328065', or (dec) 76, 73, 78, 71, 32, 80, 65'
Are there additional files required as part of the upload? The export contains a header.txt text file. Is that required to be uploaded as part of the .tar file containing the CSV?
Let me answer your second question first. Yes, the header file is required as part of the import TAR file. The header file tells the Import function which files are available for import. (Via: BAT > Import/Export > Import) If you use the same header file from the export TAR in the import TAR file, you should be fine.
As for that specific exception, let me say that I have imported called and calling transformation patterns without a problem in the past. So the problem is either the TAR file itself or the CSV inside the TAR file.
If you are editing the CSV file, it is possible the text is not formatted correctly. After finishing your edits and saving, open the CSV file in Notepad++. First, make sure that carriage returns, numbering (like E164) and such look okay. Second, do a "save as" and ensure that the file is saved as UTF-8 (rather than ANSI) text. UTF-8 is common in CUCM for text formatting. As but one example, the jabber-config.xml file must be UTF-8 formatted to be correctly read by CUCM.
And for the TAR file, use 7-Zip rather than WinZip or Microsoft's native compression function.
Let me know how this goes. If you do all of the above and it still doesn't work, I'll ask you to upload your TAR file (or send it to me privately) and I'll take a look.
Hi @Maren Mahoney thank you for the amazing session, we have learned lots.
Please help to answer some remaining questions from the live session
Let me take these three questions in reverse:
In one of the last scenarios Maren presented, what will happen to the delated phone? Would the phone profile will be completely removed, or would it be still available when you search it in the DN or MAC address?
I think you are referring to the "Migrating a Single Phone to a New Phone Model" scenario, so I'll answer that question.
The answer is: If you use the method shown to migrate a single phone to a new phone model the old phone is removed from the database. It is a true migration. (Thank you, Cisco!)
If you are working with the Export/Import feature, you will want to leave files in CSV format.
For other BAT tools (like Insert Phones or Update Users) CUCM is expecting a TXT file (UTF-8 format, if that ever comes up) which contains commas as field separators.