There has been a glitch here. I have notified the doc team and they are going to update the document asap. It should still be the final version (just that the watermark is still there). Thanks for letting me know.
TMS 14.5 is compatible with TMSPE 1.3 but its not a pre-req. If they where then they would have been released together. However TMSPE 1.3 is not far away, I don´t have the exact date but I would say it´s only days away.
Upgraded to 14.5 and 1.3 this morning - and now have lost all phone books from scheduling interface - see https://supportforums.cisco.com/discussion/12316351/phonebooks-disappeared-scheduling-interface-after-upgrading-tms-145
Cisco TelePresence Management Suite Provisioning Extension (TMSPE) v1.3 will be released imminently. Engineering is completing some last remaining regulatory and internal documentation processes before releasing.
Rest assured though, TMSPE 1.2 has been smoke-tested with TMS v14.5 before release and works together.
Having read about the unmanaged bridges feature prior to the release of this, I was quite excited as it would allow external parties to schedule multiple endpoints to dial our TP servers and visa versa, but then I read this in the release notes:
"A Network Integration license key must be purchased for each unmanaged bridge"
Looking at the pricing, it is literally cheaper to buy a licensed TP server 7010 than one of these license keys, so I don't see this feature getting alot of use unfortunately.
Why does this feature require an option key to enable, it's just providing TMS managed endpoints to dial into conference bridges that essentially you're creating, what kind of integration does it give you?
I'd hope that you'd only need to buy one Network Integration Licence per TMS Server, and not one for each unmanaged bridge. At ~$50k US list price for the TMS Network Integration License - I'm hoping that's been documented wrong in the release notes!
I can understand that an unmanaged bridge may use a "System License" for each one (~$5400 US list for 25 licenses), and there may be a requirement to have a single L-TMS-NETINT present on the TMS server for it to work... but one for each just sounds completely wrong (unless there's new licencing coming out that's not yet mentioned anywhere).
Hopefully Magnus or Michael can confirm.
Please remember to rate responses and to mark your question as answered if appropriate.