Subject: RE: mcu api: participant.add
Replied by: David Vrtin on 27-08-2012 10:33:26 AM
Another version of same problem is: if we add pre-configured participants with API with by_address (and such participants are not visible on MCU web interface), then option preconfiguredParticipantsDefer does not work for such participants. It is working only for pre-configured participants on web UI. Is this bug?
Subject: RE: mcu api: participant.add
Replied by: David Vrtin on 27-08-2012 07:30:39 AM
We would like to use MCU API to add pre-configured participant to conference configuration, like it is possible over MCU web portal (see attachment).
With this feature we can use auto-dialing to IP-VCR (for VC recording): when first endpoint joins conference MCU will call IP-VCR (start recording) and when last endpoint leaves conference MCU will disconnect IP-VCR recorder (stop recording).
Is this possible?
In conference.create or conference.modify API 2.9 is nothing about adding pre-configured participants, only preconfiguredParticipantsDefer setting.
This document was generated from CDN thread
Created by: Uroš Smerdelj on 16-12-2011 11:50:47 AM
Hello,
This question is regarding MCU 4220 and MCU 4520.
Cisco Telepresence MCU API 2.8 guide states that participant.add command accepts participantType parameter with values 'ad_hoc' and 'by_address'.
I wonder how can you add 'by_name' participants to a conference which are pre-configured on the MCU and can be listed with addressBookEntry.enumerate api?
Right now I have to read endpoint configuration with addressBookEntry.enumerate and then make a participant.add call with that configuration which is 'sufficient' but there is one problem, I need MCU to call this endpoint after some other ad_hoc participant enters the conference but if I add participant with 'deferConnection ' to 'true', I need to manualy call participant with participant.connect api.
Am I missing something or this cannot be done?
