08-01-2013 04:50 PM - edited 03-18-2019 01:34 AM
Hello!
When scheduling a conference in TMS involving a MCU, after the conference starts the remaining time as expressed in the MCU is around 15 minutes longer than what you scheduled.
Is this some sort of padding that TMS sends to the MCU, kind of like TMS considering an endpoint in an ad hoc call as being busy for the next 5 minutes?
This is seen in the following combinations: TMS14.3 (beta)/MCU 4.4(3.54) & TMS13.0/MCU 4.3(2.32)
Thanks!
Solved! Go to Solution.