I am moving users over with the COBRAS tool from a Unity 4.0(5) system to a new Unity 5.0(1) system. Both systems have two integrations, one with CallManager and one with a PBX. When I move a few test users over who are asoociated with the PBX integration, they are being imported in and some how getting mapped to the CallManager integration.
I have tried matching up the Integration IDs from server to server but that still isn't working correctly. So I was wondering if there is a way to bulk edit Subscribers' Integration ID. I don't think there is a parameter for it with the Bulk Import tool.
Durring the import you should get the option of saying all users mapped to integration "X" on the backed up system should be mapped to integration "Y" on the target system - is that not being offered? Are those selections not being respected?
I'd like to look at your restore logs - COBRAS should absolutely not being just throwing users into random switch assignments...
Page 14 on the COBRAS Help web page and page 12 in the wizard.
I tested it with one user yesterday who was associated with the PBX integration and it showed that the 'Backed Up Switch Name' was CallManager when it should of been the PBX. Is this because of this statement from the Help page:
"Page 14 shows all the switch (phone system) references made by any of the call handlers or subscribers you've selected to restore. Since switch data is not included in the COBRAS backup, all switch references will be shown here regardless."
Now I did have the option to select the PBX integration for the 'Existing Switch Name on Voice Mail Server'.
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 ...