Configure Avaya Communication Manager for QM and Analytics
In an Avaya Communication Manager (CM) environment, you can configure the connection information for the Avaya Application Enablement (AE) Services and DMCC associated with the telephony group.
Setting the Avaya DMCC device password
Use the fields in this section to configure the passwords for Avaya DMCC devices. Avaya passwords can be from three to seven digits in length. If you use more than seven digits in your extensions, you will need to configure passwords to be compatible with Avaya standards.
- Click Use Device Extension to set passwords if your extension is between three and seven digits.
- Click Use Static Password if you want to use a single password for all of your devices. When you click this button, QM displays a text box to allow you to add the three to seven digit password.
- Click Use Custom Pattern to select a custom device password pattern for setting the passwords of your Avaya devices based on your extensions. The password must be between three and seven digits. If your extensions have more than seven digits, this functionality allows you to convert your device numbers to acceptable Avaya passwords. Key the pattern in the Custom Pattern field.
The custom Avaya DMCC password pattern functionality uses two wildcard characters to represent your extensions:
- F—first (or leading) digits
- L—last (or trailing) digits
You can also insert static digits 0 to 9 in the password pattern.
Click the question mark for examples of using custom password patterns.
Field |
Description |
---|---|
Device Password |
The default password for all devices. NOTE If you change a password, you must restart all associated signaling services. |
Associated Avaya ACD |
The ACD with which this telephony group is associated. |
Enable Free Seating |
Select this check box to record agents by user name or agent-ID instead of by a physical channel number. |
Recording Skill Hunt Group |
The extension associated with the Hunt Group. A Hunt Group is a collection of users handling similar types of calls. NOTE If you are using free seating, the Hunt Group must contain all the extensions that you want to record. |
Device Synchronization Data Server |
The data server used to synchronize Avaya CM devices. |
Switch Connection Name |
The switch name or IP address of the switch connection. NOTE This field is case-sensitive. |
HOSTNAME / IP ADDRESS |
The host name or IP address of the AE Services Device, Media, and Call Control (DMCC). The DMCC controls the media (that is, it handles the RTP). The Monitoring and Recording CTI Service connects to it. BEST PRACTICE Use a host name in all instances where you are required to specify a host name or IP address, if possible. |
Port |
The port for the Application Enablement Services server. The default port number is 4721. |
User Name |
The name of a user created in the AES Management Console that has the CT User attribute set to Yes. NOTE If you change a user name or password, you must restart all associated signaling services. |
Password |
The password for the account used to access the server. NOTE If you change a user name or password, you must restart all associated signaling services. |
Use Device Extension |
Select this check box to use a device’s extension as the password for DMCC configurations. If you do not select the check box, the DMCC uses the default password for all devices entered in the Device Password field. The device password is also known as Security Code in the Avaya CM Station configuration. |
Generate CDRs from Signaling Events |
Select this check box to start generating contact detail records (CDRs) for an existing ACD integration with the CTI server. Calabrio ONE does not use these CDRs for reconciliation unless you also select Use CDRs for Reconciliation check box. |
Use CDRs for Reconciliation |
Select this check box to use the CDRs generated by the CTI server for reconciliation instead of the CDRs imported from the ACD. This check box displays after you check the Generate CDRs from Signaling Events check box. |