03-18-2013 05:25 PM - edited 03-18-2019 12:47 AM
Hi All,
I wonder if anyone is able to confirm A) if you are seeing this behaviour. B) if you know this is expected behaviour.
TMS: 13.2.1
TMSXE: 3.0.2
Users are placing ad-hoc calls with no scheduling, which is fine. TMS however is then syncing the ad-hoc call details back into the corresponding exchange room calendars. Is anyone else seeing this behaviour/know it is expected behaviour.
Solved! Go to Solution.
03-19-2013 03:26 AM
Hi,
This is expected behavior. When TMS picks up an ongoing ad-hoc call, the endpoint is reserved for the next five minutes in the TMS database. This is information that has to be replicated over to the Exchange resource calendars for the free/busy information to be correct.
Regards,
Kjetil
03-19-2013 03:26 AM
Hi,
This is expected behavior. When TMS picks up an ongoing ad-hoc call, the endpoint is reserved for the next five minutes in the TMS database. This is information that has to be replicated over to the Exchange resource calendars for the free/busy information to be correct.
Regards,
Kjetil
03-19-2013 03:45 AM
Kool. I thought it was expected behaviour but I couldn't see it documented anywhere (are you able to point in in the direction if it is documented?). Thanks Kjetil
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide