Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Using different participant types
When using the API as a web reference, the participant types, such as "IP Video", "ISDN Video", and so on
are created as enumerations called, for example, IPTel, IPTel1. Values ending in 1 are dial-out, values not
ending in 1 are dial-ins.
are created as enumerations called, for example, IPTel, IPTel1. Values ending in 1 are dial-out, values not
ending in 1 are dial-ins.
The code snippet below shows how to create a conference with three different participant types. An MCU is
required for this call to be saved.
required for this call to be saved.
public
void
SaveConferenceWithVariousParticipantTypes()
{
InitBookingService();
// Get a default conference object from TMS, where most common values are set
// (using default values specified in TMS)
Conference conference = bookingService.GetDefaultConference();
// Create and initialize an array of conference participants, and add it to the conference
conference.Participants =
new
[]
{
new
Participant
{
// Adds a SIP Dial-in participant
NameOrNumber =
"SIP Dial-in 1"
, ParticipantCallType = ParticipantType.SIP
},
new
Participant
{
// Adds a SIP Dial-out participant
NameOrNumber =
"manager1@example.com"
, ParticipantCallType = ParticipantType.SIP1
},
new
Participant
{
// Adds a TMS participant (endpoint)
ParticipantCallType = ParticipantType.TMS, ParticipantId = 4
}
};
// Save the conference, saving the returned conference (where all values are now specified)
conference = bookingService.SaveConference(conference);
PrintConferenceInformation(conference);
}
Cisco TMSBA Programming Reference Guide (14.3)
Page 60 of 67
Code examples