Since you are coming from a dissimilar system, my advice is to create a phone template in CUCM (located in the phone subsection of the BAT menu of the publisher), per model, and put as much standardized data as you can in the phone template (device pool, CSS, sip profile, number of lines, CFNA/CFB treatments ...etc).
Then I would manually build a single phone configuration per model and do a phone export/all details (again, under the phone subsection of the BAT menu) and downloaded it and rename it to a .CSV. Break out the export file into multiple files (one per model) and redact the columns not needed from the files; keep the columns that represent unique data elements like external mask, line text labels ... etc and remove the columns that represent standard data already set in the phone template for that model. Once you have it set, uploaded those files into BAT as a phone / insert - specific details. Then go back to the phone subsection of the BAT menu to "insert phone". Pick the CSV file you uploaded from the drop down, along with the appropriate phone template that you created and select "run now" and execute the job. You may find that you have to run the job a few different times as you'll inevitably find things that need tweaked. To do that, same process, just remember to select "override existing configuration". If this is an existing system in production with data already in it, I would also put a unique piece of text in the beginning of the description field for each phone; this makes the imported data easier to find/isolate from the rest of the data should you need to delete everything you just imported ... etc. Once you're happy with the way the data imported, you can just override with another import and remove the unique text. Once the phones are in, you can follow a similar process for end user accounts (if the accounts are LDAP synced, BAT can still be useful for the CTI Controlled Device column, default device ... etc). Going forth into operate, after implementing; changes can be a matter of downloading the BAT CSV files, changing the data in the CSV file, re-upload and re-import. This can be a big help on a troubledesk with green support folks that do MACD ... etc. BAT is a unique tool; most BAT tasks require a time-sink upfront to set up, but you get the time savings back in scale. Having said that, I've always found BAT to be quite useless for less than 50 phones/users; I've always seemed to be able to manually build out 50 or less, quicker than what it would take me to setup the BAT templates ... etc. Not quite what you asked for, but I think you'll be better served doing it yourself in this manner. Thanks, Ryan On May 12, 2017, at 8:26 PM, Hamu Ebiso <hebiso2...@hotmail.com<mailto:hebiso2...@hotmail.com>> wrote: Does anyone has a good phone BATTING Tamplate? I am converting Avaya phone system to cisco phone system and having issue getting good tamplate. CUCM VERSION: 10.5.2. PHONES MODEL, 7942's, 881's, 8851's and some wireless phones. Anything with good instructions will be appreciate. Thanks Hamu Sent from my Sprint Samsung Galaxy S® 6. _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
