It looks like a problem with the Device portion of the Phone Template. Have a close look at what you have configured;
Creating a Phone Template
The phone template and Comma Separate Values (CSV) files work together in bulk transactions. Based on the type of phone you want to add in batch, you can create a template that has the common features for all the phones in a batch, such as the Model, Device Pool, and so on. These templates are stored and are reusable for other phone batches. For example, you can configure a template for the Cisco 7960 Model with only two lines configured and another with four lines configured.
The CSV file has the details of all the phones that are individualistic in nature to a phone, such as its Name, Description, and so on. See "Creating the CSV File for Phones" section for more details on the CSV file.
To create a phone template, you must first enter the required phone settings and then add the appropriate number of lines to the phone.
Yes, I'm sure that this is a type of compatability issue. BAT is very fussy about upgrading/migrating vs uninstall/install. Only the proper migration path methodology will also migrate the BAT Templates. I am guessing that that version on the Production server was done using the uninstall/install method. The only thing that I can think of is to try to re-install 4.5.69 on the Production server and then upgrade if you need to. You may want to open a Tac case on this one, as you say 90 Templates would be a real pain to lose. Here is some pertinant info;
If you uninstall BAT and then install the newer version of BAT, none of your previous templates can migrate to the newer version. You must upgrade BAT to migrate templates to the new BAT release.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...