Dear Alan,
Yes, the Multi-Channel Interface Product License goes on the MCIS line.
The proper key for the TAPI voice driver is: TAPIConnector=<insert license key> . I believe you are using the wrong Server Profile template, because the TAPI license should show up on the line. Note, if you are using Cisco UCM, you MUST use the TAPI template. Cisco templates are only for UCCE, PCCE, and UCCX. You should use the SOAP TAPI template.
Warning: If you do not use the correct template, you will not have the proper CTI Module settings to configure the TAPI connection.
The .NET Adapter license is for the SOAP adapter gateway, used with Salesforce, Microsoft Dynamics CRM, Desk.com and CCA Toolkit.
Note: You can always find the license key information in the appropriate Implementation Guide. (In this case the VoiceDriver For Microsoft TAPI Implementation Guide)...
Step 3: Generate and apply the TAPI Driver license
+ The voice drive requires one license for each concurrent user.
+ See the AMC Contact Canvas Implementation Guide and the AMC On-Line Licensing Guide for instructions on how to generate licenses keys.
+ Add the license key to the License Manager section of the configuration. Use the generated license key as the “value” in the license key-value entry.
Table 7‑6: TAPI Driver License Manager Key
License Module Entries
|
Notes / Description
|
TAPIConnector=<generated license key>
|
Apply the generated license key for TAPI.
|
Sincerely,
Ken Rush