![]() |
The Device, Media, and Call Control (DMCC) service provides third-party call control and first-party call control (device control and media control). The DMCC SDK provides a Java, XML and .NET API. For more information about the DMCC SDKs, see SDKs.
DMCC first-party call control (1PCC)
DMCC with Device Control can set up a DMCC softphone that gains exclusive or shared control of a softphone-enabled Communication Manager telephone or extension. A DMCC softphone is an instance of a phone or extension that is created by AE Services and then registered on Communication Manager.
DMCC with Media Control provides the ability to record media from a call into a WAV file or play a voice announcement or tone that is prerecorded in a WAV file. Media session control also provides a way for a client application to send and receive TTY characters over Real-time Transport Protocol (RTP) streams in the form of RFC2833 packets. Applications can use this capability to implement Voice Carry Over (VCO). The TTY capability is available in client-media mode only.
DMCC third-party call control (3PCC)
DMCC with Call Control Services uses the TSAPI service to provide an expanded set of third party call control capabilities, such as the ability to place calls, create conference calls, deflect calls, reconnect call, and monitor call control events, just to name a few.
Routing Services
Routing Services allows applications to request and receive routing instructions for a call. These instructions, issued by a client routing server application, are based on the incoming call information provided by Communication Manager.
System Services
System Services allows applications to request and receive health status of a TSAPI TLink.
System Services also allows applications to request and receive events on the status of TSAPI CTI (Tlink) connections between the AE Services server and the Communications Manager(s). Once an application is registered, notification events are sent when the Tlink status changes for example linkUp/linkDown for the switches for which it has registered.
For DMCC call recording solutions, Avaya recommends that you use the Avaya IP Migration Readiness and Optimization services to help you safely implement IP-based solutions in a stable, optimized infrastructure.
These services include a two-phased, detailed analysis of the entire network to help assess whether you can deploy a converged IP solution such as AE Services without adversely affecting your existing network applications and services.
The first phase of this analysis is the Customer Infrastructure Readiness Survey (CIRS). Certified Avaya engineers conduct a high-level evaluation of the local and wide area network infrastructure to identify any significant network issues that must be resolved prior to deploying the proposed IP solution.
The second phase of this analysis — Network Analysis/Network Optimization (NANO), is required when the CIRS indicates that the network cannot support the proposed IP solution at the desired performance levels. Starting with the information and data gathered for the CIRS, Avaya engineers perform problem diagnosis to get at the root causes of network issues. They also provide functional requirements and recommendations for a network design that optimizes all of the resources needed to support the IP solution.