/mcpC H A P T E R 2 Cisco Unity Connection Telephony Interface (CUTI) API -- Using CUTI for Basic Call Operations Links to Other API pages: Cisco_Unity_Connection_APIs • About Basic Call Operations , on page 5 • Playing and Recording by Using a Call , on page 6 • Examples, on page 6 • Play Greetings, on page 14 • Save Video Greetings , on page 18 • Example of Data Fields , on page 19 About Basic Call Operations The basic call operations are making a call, checking call-connected status, and hanging up. The call object is used to convey information about a call (see API XSD's). Cisco Unity Connection 10.5(2) and later facilitates you to make a video call. A user will be able to establish a video call, if all the required pre-checks are satisfied, which are as follows: • Mapping video service accounts: subscriber needs a video service configured with the video service account. • Enabling Class of Service (COS) Settings for the subscriber When making a call, the following fields are used: • number: the only field that does not have a default value. Users with the system administrator role can call any number, but end users can call only those numbers that do not violate their associated restriction table, based on their class of service. • maximumRings: defaults to 4. • mediaSwitchObjectId: for end users, defaults to the phone system that is associated with the user. For users who do not have an associated phone system (for example, administrators), the phone system that is marked as the default TRAP phone system is used. • calltype: indicates whether the call type is audio or video. If you do not specify the call type, then by default the call will be placed as an audio call only. Cisco Unity Connection Telephony Interface (CUTI) API 5
