The behavior you describe matches what happens when the meeting duration is modified using the CTX Admin GUI. However, when the CTX AMM API is used to modify the duration when the meeting is in extension time, the extension count does not appear to be reset to zero and unless the new duration is greater than the original duration plus the extension time, the meeting will end after the extension completes.
The following is the time line using the CTX AMM API:
6:45 – A meeting with a duration of 15 minutes with 1 extension of 15 minutes starts
6:58 – The meeting extension message appears on the endpoints. Looking at the meeting in the CTX Admin GUI the duration now shows 30 minutes.
7:02 – The meeting duration is modified using the CTX AMM API to 30 minutes.
7:15 – The meeting ends.
The following is the time line using just the CTX Admin GUI:
7:45 – A meeting with a duration of 15 minutes with 1 extension of 15 minutes starts
7:58 – The meeting extension message appears on the endpoints. Looking at the meeting in the CTX Admin GUI the duration now shows 30 minutes.
8:02 – The meeting duration is modified using the CTX Admin GUI Modify Meeting to 35 minutes. Initially the page has the duration valued at 30 minutes.
7:18 – The meeting extension message appears on the endpoints. Looking at the meeting in the CTX Admin GUI the duration now shows 50 minutes.
7:35 – The meeting ends.
Is this working as designed?
Mike Nelson
AT&T Labs | 317.842.3341 | mn1968@att.com<mailto:mn1968@att.com> | Q Me
This email and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited.
