I've been asked whether or not its possible to export ALL users personal speed dials from 3 existing UCM 5.1 clusters and importing them back into a new 8.6 cluster. Anybody have any funky ideas aside from hiring a team to manually extract them and readd on the new cluster?
In theory it's possible with AXL but I have yet to be forced to figure out how. You could probably suck the database entries out from one cluster into a CSV and reimport them on the new cluster. Note that speed dials and abbreviated dial entries are stored against a specific device name, not the end user object.
Here's the AXL developer's link. Hopefully others will add to this response with more specific AXL guidence.
Well - getting the speed dials out is easy enough:
admin:run sql select d.name, s.* from device d join speeddial s on d.pkid = s.fkdevice
name pkid fkdevice speeddialindex speeddialnumber label labelascii
============= ==================================== ==================================== ============== =============== ===== ==========
SEPWORKLAPTOP bfc1b619-bc4b-48af-9679-02993332275c a164b74d-f1dc-f1b6-c552-5c5be6953132 1 123456789 hello hello
Putting them in you would have two options.
1) Use AXL - bit more of a learning curve
2) Use SQL and Excel. Basically conjugate some commands in Excel based on the output of the command above. The pkid in the speed dial table is generated by the system, so you need to supply all the other fields to make up a command like so:
insert into speeddial (fkdevice, speeddialindex, speeddialnumber, label, labelascii) values ((select pkid from device where device.name like 'SEPWORKLAPTOP'),1,'123456789','hello','hello')
The AXLSQLToolkit can then be used to insert a long series of those commands into the database. Or prefix them with 'run sql' and put them in the server CLI if you have time on your hands.
Be aware that direct DB manipulation is a very bad idea if you don't know what you are doing. The DB should enforce basic constraints (unique indexes where necessary and so on) but may not do the same validation of character strings etc that the web interface does - so you might put something in that makes CCMAdmin explode when it reads it. Since you are extracting from a 'working' system, hopefully your info won't stop this system 'working'.
Back up the server first, test a small batch first, etc. etc.
AXL is more 'supported' in as much as it shouldn't let you 'break' the DB, but you won't get much assistance from TAC with using the API.
It's all in the DB, and it's all accessible via AXL - so yes, it's just a matter of looking up the information in the docs Jonathan posted..
Please rate helpful posts..