This document contains the Frequently Asked Questions on the DMCC .NET SDK. Only the questions are initially shown. Click on a question to reveal its answer.
Note that there is also an AES DMCC FAQ that can be found by clicking on the FAQ: DMCC.
DMCC/AES Version 3.1 (or later) is needed. CM version 3.0 or later.
Not for using .NET. Obviously, there is a need to have CM and DMCC servers and appropriate licenses, but these are not unique to the .NET API.
The limitation on the number of extensions a single server can handle will depend on numerous variables. Some variables of note are the application server's speed, memory, and number of transaction per second. Whether or not RTP media is being terminated at the application server is also an important consideration, as is if the server is running other applications. The AES server is specified to handle 1000 device registrations and the resulting traffic from them. As an example of the capacity of a desktop PC application Avaya has developed a sample application which had 100 registered extensions (no CLIENT media) and it was well behaved on the PC.
When you establish a connection to DMCC you need to specify what port to use. By default, DMCC uses port 4721 for unsecure socket communications and port 4722 for secure sockets. If the application creates softphones in CLIENT media mode then the RTP/RTCP data will come in over additional ports which are specified in the MediaConnected event. If the application is supposed to work over the Internet then appropriate measures would have to be taken to allow the application to talk to the DMCC. Either by using a VPN or allowing the DMCC port to be exposed (this is a security risk that most IT groups would not allow).
Not at this time.
Login to the DevConnect web portal replace the URL with https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=125 look for and download this file "Application Enablement Services IP Communications SDK (Device and Media Control/CMAPI) (.NET)". The dashboard application is in the .NET SDK.
Yes, the .NET API/SDK has a sample call recording application (simpleRecord) which gives an example of how to receive and record media and also how to inject media. In the call recording case, the media that is being injected is a tone so the other party knows the call is being recorded. In addition, the .NET SDK has a code snippet which provides an example of how to write a thread which receives the RTP data.
Yes, edit the DMCC.config file that resides in the directory with your application (if you don't already have one copy the one that is in the dashboard directory of the SDK). Search the file for "<logger name="XML">" (towards the bottom).
Set the "level value" to INFO
<logger name="XML"> <!-- <appender-ref ref="B" /> --> <level value="INFO" /> <appender-ref ref="RollingLogFileAppender" /> <appender-ref ref="ConsoleAppender" /> </logger>
The output will be placed in the same directory as the application and DMCC.config files, and be named "log-file.txt". There are other files (rolling-log .*) created by the log4net utilities.