DMCC with Call Control Services - checklist

Last Updated : Dec 08, 2021 |
Prolog information
Use this checklist if you are administering DMCC with Call Control Services.
#
Description
Notes
1
Networking > Network Configure
2
Networking > AE Services (Local IP)
Required. Based on your AE Services configuration, see either of the following topics:
3
Networking > Ports
Optional. You can use the default settings.
Note:
If you have a firewall, you might need to change these settings. See TCP ports and firewall settings.
Important:
4
Communication Manager Interface > Switch Connection
Required. The Transport Layer is used. See Adding a switch connection.
5
CTI Link Admin
Required (you must add a TSAPI Link).
Applications that use DMCC with Call Control rely on the TSAPI Service. See Administering TSAPI Links.
6
AE Services > DMCC Configuration
Optional. You can use the default media properties. See Setting DMCC Media Properties.
7
Security > Security Database
Optional. If you are using the AE Service Security Database for controlling device access you must administer the TSAPI Configuration settings. See Chapter 6: The Security Database.
8
Security > Enterprise Directory
Optional. If you are using an external LDAP directory you will need to use the Enterprise Directory Configuration page. For more information, see Enterprise Directory settings in the AE Services Management Console.
9
Security > Certificate Management
Optional. if you are using link encryption, you must set up certificates. For more information, see Certificate management.
10
Security > Host AA
Not applicable if you are not using encryption. It is optional if you are using link encryption. The DMCC service can be set up to provide far-end client authentication and authorization. For more information, see the Avaya Aura®Application Enablement Services Device, Media, and Call Control Java Programmer 's Guide, 02-300359.