ECSBU (that would be the Unity folks) hasn't finished qualifying 3.0(8) with Unity 2.4.6 yet. The CM folks may have finished their qualification and that's where you're getting this information. I'll have more news later this afternoon but I know we were able to reproduce a supervised transfer issue and a couple other minor items in our testing over the last week.
An updated TSP may be necessary to work properly with 3.0(8), it's unknown at this time. We're trying to nail this down today if at all possible.
When you get the TSP issue nailed down will you please provide another thread here with the results? Also, I understand that with this version of Unity (2.4.6) the integration type for CallManager implementations is going to change from None to TAPI. If the key is not upgraded to the proper integration type, will the two systems integrate?
I'll definitley post a new thread out here when I get a firm answer (hopefully in a couple of hourse).
Your key will need to have an integration type of "TAPI" if you want to talk to call manager. If it's not there the TSP connection wont fly.
if you're just looking to test, 2.4.6 allows you to install without a key for 2 ports and this will allow connection to any kind of ports (call manager included). If you want to go beyond two ports, however, you need a key with "TAPI" on it.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.