My advice to you is to start BATting earlier in your implementation process as it's likely to take you a longer amount of time (and leave you with bald patches with all the head scratching).
Oddities include:
- All sorts of odd fields crop up when you export Device Profiles (most of which are blank) such as Device Pool! When I exported a Device Profile i'd configured and then deleted it from the system I found that (without editing) I couldn't use that exact file to import the same record because I got a "Audible Message Waiting" field was not a valid field. Stupid thing...
- The User export now contains a "PKID" field which looks to be the CallManager's Primary Key field for users in the system. Attempts to import users while leaving this field blank failed due to a "Duplicate value in index field" error. To fix it I had to generate 250 hex strings and stick them into the spreadsheet.
- Both the Phones import and the Device Profiles import failed to recognise that I had configured a Service and Service URL buttons. Every attempt to get this to work failed and I ended up manually adding Extension Mobility Service to 250 phones and 250 Device Profiles. I hope I never have to do a 1000 phone system using CM6 - it would just be a nightmare...
Fun!
1 comment:
Same here. We are now testing Belkin devices to see if it has better implementation for Call manager.
Post a Comment