With release 4.0 the expected happened.
They managed to mess up a lot of things with TAPI so now my 3rd party CTI app don't work properly until the private build.
This I had expected, so I thought I try the 3.2 55 maint release. Installed it, a few quick tests and found out that they seem to have changed how CLI is presented for CTI apps in this release so back to "good old" 3.2 54 again.
I hope this was just me mezzing things up cause I wouldn't expect that to happen in a maint release, but as we have learned, test everything before you put it on a customer site.
Guess Q1 releases will stay on the lab system until they work fine enough for our office (which usually gets final testing before customer installation).
Can't wait for what they come up with in the May release
They managed to mess up a lot of things with TAPI so now my 3rd party CTI app don't work properly until the private build.
This I had expected, so I thought I try the 3.2 55 maint release. Installed it, a few quick tests and found out that they seem to have changed how CLI is presented for CTI apps in this release so back to "good old" 3.2 54 again.
I hope this was just me mezzing things up cause I wouldn't expect that to happen in a maint release, but as we have learned, test everything before you put it on a customer site.
Guess Q1 releases will stay on the lab system until they work fine enough for our office (which usually gets final testing before customer installation).
Can't wait for what they come up with in the May release