I'm not sure why they are enforcing this on imports... I think there's a set of characters they allow for various fields on new creates and imports across the boards and they're just blindly enforcing them regardless. Just tried this exact scenario out on the new 4.0(1) import and it does the same thing. I've sent up a flag to the DB boys (responsible for the builk import these days) to see what they have to say...
Yeah, you can work around this easily in 4.0(1) I just tried it on my test box and it works like a champ.
All the field definitions and allowable characters for the new import tool are defined in an XML file called ImportSpec.xml thats found in the \commserver\utilities\ciscoUnityBulkImport\ directory (where CUBI is installed). If you pop open this file with a text editor, find the section that starts with:
In there you will find the definition for alias which looks like so:
The [[:alnum:]] nodation there means alpha numeric only. To add underscore (or any other character for that matter) you only need to add it here such that it looks like this:
Save it and re run the import tool, it should not bark about underscores any longer.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...