RE: Meeting Extension Behavior After Adding Endpoint with AMM API http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id= 2013-05-24T04:35:39Z 2013-05-24T04:35:39Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15458256 2013-05-21T17:04:23Z 2013-05-21T17:04:23Z

Hi Jannik, Yes, it appears that the CDR API and the Scheduling API present different numbers in the totalNumberFound value.  I will try to have this changed in a future release to be more consistent.  For your other question, the meetingKey returned in the APIMeeting object from the GetMeetings method is not usable in the CTX Admin (i.e. web interface).  However, the conferenceId in the APIMeeting object can be used on the Meetings list page (Collaboration Services > Meetings) to find the meeting.  You can also filter by subject, start time, scheduler, etc., on that page using the column filters.  I hope that answers your question. - John

John Yontz 2013-05-21T17:04:23Z Jannik Hochfeld http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15447448 2013-05-21T12:50:57Z 2013-05-21T12:50:57Z

Hello John, Thanks for your help. It guided me to correct conclusion. My mistake was to expect the Scheduling API to work the same way as the CDR API. But there is a difference, as the CDR API tells you all elements with the totalNumberFound Value and the scheduling API tells you only the elements of the currect request I've got another Question: Is it possible to get directly to a meeting in the CTX webinterface with the "meetingKey" or with another value requestable via the API?

Jannik Hochfeld 2013-05-21T12:50:57Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15381718 2013-05-17T22:48:04Z 2013-05-17T22:48:04Z

Hi Jannik, The getMeetings request has additional parameters for pagination that will solve your problem.  The API Guide documentation has a paragraph (with an example) that describes how to do pagination for datasets that are larger than 100. You can find the documentation here:  http://developer.cisco.com/documents/3094533/11264455/CTX+1.1+API+Guide.  Hope that helps. - John

John Yontz 2013-05-17T22:48:04Z Jannik Hochfeld http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15362183 2013-05-17T11:52:35Z 2013-05-17T11:50:31Z

Hi guys, i wonder how i raise the number of maximum Meetings, that are in the getMeetings result. When i do a soapCall with getMeetings and check the totalNumberFound Value it is always 100. When i look in the CTX Web Interface there are more than 100 Meetings. I want to build a overview of todays meetings and don't get all the meetings because of this limitation. CTX Version 1.1.0.5.1.1

Jannik Hochfeld 2013-05-17T11:50:31Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14863625 2013-05-01T22:54:44Z 2013-05-01T22:54:44Z

Hi Mike, The AMM requests to drop, redial, mute/unmute, and send endpoint text return with success when the operation is initiated to the bridge resource.  The request does not wait for the operation to complete (either from bridge resource response or telephony signaling).  It looks like our documentation needs to be clearer about that. For the scenario that you describe, you have two options:  You can provide a safe delay between the previous drop and the redial attempt.  It looks like 5 seconds works for you, but perhaps you could increase to 10 seconds to be absolutely certain.  The other option is to always retrieve the list of active participants prior to doing the redial. If the participant to be redialed still shows as active, you can delay and re-retrieve the status until it is not active. By the way, in 1.3 the GetCurrentMeetingStatus result will also include the previous participants (in addition to the active participants). - John

John Yontz 2013-05-01T22:54:44Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13953158 2013-04-06T01:20:45Z 2013-04-06T01:20:45Z

Hi Mike, Sorry for the late reply on this.  I had discussed this with my team, and we are not aware of this type of failure.  We searched the open defect and could not find anything on this either.  The error is coming directly from the CTMS, and CTX is relaying it via the API.  My guess is that if you tried the same operation using the CTX Admin Meeting Diagnostics Page, you would see the same result.  That is, when it fails, it should fail in both.  Perhaps this is related to a specific version of the CTMS software?  I would recommend that you open a defect and include in the defect the CTMS version, the type of endpoint(s) that fail, endpoint versions, and how reproduceable it is. Thanks - John

John Yontz 2013-04-06T01:20:45Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13946209 2013-04-05T22:00:24Z 2013-04-05T22:00:24Z

Anything on this question?

Michael Nelson 2013-04-05T22:00:24Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13676338 2013-03-29T21:56:48Z 2013-03-29T21:56:48Z

We are getting a error.amm.callControlException.muteFailed exception when issuing a muteParticipant. The message in the exception is "Error muting participants:   Error muting/unmuting participant(s): Not able to mute/unmute participant". Can you provide some additional guidence on this return code and where we might find more information to help determine the issue. This has been reported for a meeting on a CTMS bridge with CTS endpoints.

Michael Nelson 2013-03-29T21:56:48Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12763933 2013-03-07T21:21:21Z 2013-03-07T21:21:21Z

Mike, We verified that your observations are correct, both through the Admin and the API.  CTX will limit to 45 characters as you mentioned.  This limit was imposed because of limits in the TPS 8710 bridge resource. If you feel that 45 is too restrictive, please open a defect with CTX and we will try to address this. Thanks - John

John Yontz 2013-03-07T21:21:21Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12741667 2013-03-07T11:48:28Z 2013-03-07T11:48:28Z

We are getting this error in the API response. You also get the error if you schedule a meeting directly in CTX.

Michael Nelson 2013-03-07T11:48:28Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12728071 2013-03-07T02:06:17Z 2013-03-07T02:06:17Z

Hi Mike, I cannot find any limitation of 45 characters within the CTX code.  In fact, I see that the schema allows up to 128 characters.  Is it possible that your scheduling portal is enforcing that limit? - John

John Yontz 2013-03-07T02:06:17Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12703287 2013-03-06T16:04:22Z 2013-03-06T16:04:22Z

It seems that the CTX limits the number of characters that can be specified in the Number field for a dial-out endpoint to 45 characters. Is this configurable?

Michael Nelson 2013-03-06T16:04:22Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12170192 2013-02-20T18:10:40Z 2013-02-20T17:47:26Z

Hi Mike, This issue has also been reported by another partner and a defect has been raised for it: CSCue57886.  Unfortunately, there is no workaround.  We are planning for a patch to fix this, but I am not clear on the delivery date. - John

John Yontz 2013-02-20T17:47:26Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12161050 2013-02-20T14:31:36Z 2013-02-20T14:31:36Z

It appears that the isMuted is always returning false in the participantsInCurrentMeeting item in the getCurrentMeetingStatus response. We are seeing false for both CTMS and TPS (8710) bridges. Is there an issue with this or is there something we need to do differently to receive the mute status?

Michael Nelson 2013-02-20T14:31:36Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11904095 2013-02-13T19:30:01Z 2013-02-13T19:30:01Z

It looks like you want to use scheduled with best effort instead of guaranteed perhaps because you want to take advantage of overbooking on the resource pool?  In any case, you are correctly inferring what the proper behavior should be.  Rather than needing to calculate the number of screens for your given scheduled meeting + endpoints, you can simply provide a sufficiently large value (e.g. 100) for your minScreens value and CTX will do a minimum of that value and the calculated value for the meeting.  Doing so will guarantee that when/if the meeting happens, it will have the required capacity for all participants allocated at the beginning of the meeting. - John

John Yontz 2013-02-13T19:30:01Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11901590 2013-02-13T19:10:40Z 2013-02-13T19:10:40Z

Hi Mike, I've verified that the following is a defect: > Case 3: Endpoint added at the 14-minute mark >> 2 15-minute extensions (1 extra extension) And I trust that the others that you reported are variations on this.  Please open a defect for this (using your normal channels), attach all of your findings to that defect, and mention that the CTX development team has specifically confirmed the failure in case 3.  You can mention my name in the defect if you wish. Thanks for your research on this. - John

John Yontz 2013-02-13T19:10:40Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11898534 2013-02-13T17:15:22Z 2013-02-13T17:15:22Z

Some additional scenarios: [color=#1f497d]****[/color] [color=#1f497d]Scheduled Meeting Duration: 15 mins[/color] [color=#1f497d]Scheduled Meeting extension enabled type: ENABLE[/color] [color=#1f497d]Scheduled Extension period: 15 mins[/color] [color=#1f497d]Scheduled Number of extensions: 2[/color] [color=#1f497d]Active meeting new Duration: null[/color] [color=#1f497d]Active meeting extension enabled type: null if within first 13 mins else DISABLE[/color] [color=#1f497d]Active meeting Extension period: null[/color] [color=#1f497d]Active meeting Number of extensions: null[/color] [color=#1f497d]>> [/color]Tried adding endpoint in the first meeting extension at 20mins mark, request fails with message “Cannot change the meeting extension enabled setting for active meeting.” [color=#1f497d]>>   [/color][color=#1f497d]Tried adding endpoint in the second meeting extension at 40 mins mark, request fails with message “Cannot change the meeting extension enabled setting for active meeting.”[/color] [color=#1f497d]****[/color] [color=#1f497d]Scheduled Meeting Duration: 15 mins[/color] [color=#1f497d]Scheduled Meeting extension enabled type: ENABLE[/color] [color=#1f497d]Scheduled Extension period: 15 mins[/color] [color=#1f497d]Scheduled Number of extensions: 1[/color] [color=#1f497d]Active meeting new Duration: null[/color] [color=#1f497d]Active meeting extension enabled type: null if within first 13 mins else DISABLE[/color] [color=#1f497d]Active meeting Extension period: null[/color] [color=#1f497d]Active meeting Number of extensions: null[/color] >>[color=#1f497d]       [/color][color=#1f497d]Tried adding endpoint in the meeting extension at 20mins mark, request fails with message “Cannot change the meeting extension enabled setting for active meeting.”[/color] [color=#1f497d][/color] [color=#1f497d]****[/color]

Michael Nelson 2013-02-13T17:15:22Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11895348 2013-02-13T16:10:42Z 2013-02-13T16:10:42Z

Can you provide guidance on what to set the minScreensDefinitionType and minScreens fields to in a scheduleMeeting request when the meeting is best-effort but we want all the screens to be allocated when the meeting starts. Do we have to calculate the number of screens in the meeting or can we send a number that is greater than the number of screens that will be in the meeting and expect CTX to do a minimum on the that number and the number of actual screens scheduled for the meeting.

Michael Nelson 2013-02-13T16:10:42Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11868035 2013-02-12T23:22:22Z 2013-02-12T23:22:22Z

Hi Mike, Thank you for the detailed analysis.  With this information, we will attempt to reproduce and diagnose here.  I will aim to respond within the next day or so. - John

John Yontz 2013-02-12T23:22:22Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11867094 2013-02-12T23:17:43Z 2013-02-12T23:17:43Z

Some additional testing has provided the following: Scenario: Meet-me meeting, scheduled duration = 15 minutes, Meeting Extension Enabled Type = ENABLED, Meeting Extension Period = 15 minutes, Number of Extensions = 1 Active Meeting Management API Modify Meeting parameters: Duration = null, Meeting Extension Enabled Type = null, Meeting Extension Period = null, Number of Extensions = null   Case 1: No endpoints added during the meeting >> 1 15-minute extension (as expected) Case 2: Endpoint added at the 10-minute mark >> 1 15-minute extension (as expected) Case 3: Endpoint added at the 14-minute mark >> 2 15-minute extensions (1 extra extension) Case 4: Endpoint added at the 20-minute mark (5 minutes into 1st extension) >> 2 15-minute extensions (1 extra extension) Case 5:  Endpoint added at the 10-minute mark and at the 20-minute mark (5 minutes into 1st extension) >> 2 15-minute extensions (1 extra extension) Case 6: Endpoint added at the 10-minute mark and at the 12-minute mark >> 1 15-minute extensions (as expected) Case 7: Endpoint added at the 20-minute mark (5 minutes into 1st extension) and the 22-minute mark (7 minutes into 1st extension) >> 2 15-minute extensions (1 extra extension)   Another group reported: Meeting extension is added if another endpoint is dialed out to after the notice of meeting extension is seen. For example with 2 minutes left in the scheduled meeting the text saying "your meeting has been extended 15 minutes" is displayed. If an endpoint is dialed out after that, the meeting is extended 15 minutes as expected but then again for a second 15 minutes. If you dial out another endpoint after you are in the first meeting extension you get a third extension. Dropping the endpoint that was dialed out does not cause the meeting extension to be taken away.   Can you advise us if when we add an endpoint within the "meeting extension period" (see definition that follows) and specify DISABLE for the Meeting Extension Enabled Type will that stop any further meeting extensions? We observed that once the meeting is at the 2 minute warning the CTX shows the extension being added so for the purposes of this question consider the "meeting extension period" to be any time within 2-minutes of the meeting ending or in meeting extension time.

Michael Nelson 2013-02-12T23:17:43Z