Document ID: 50025
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Configuration and Click-to-Attend Link Setting Options
Related Information
Introduction
This document explains Cisco MeetingPlace Simple Mail Transfer Protocol (SMTP) post-install configuration and Click-to-Attend link registry settings and their primary functions.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on Cisco MeetingPlace SMTP Version 4.2.1.x.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Configuration and Click-to-Attend Link Setting Options
This screenshot shows locations in the Cisco MeetingPlace notification gateway registry key:

Restart SMTP and notification services for these changes to take effect.
-
GenerateAttendConfAttachments—If the registry value is set to 1, then the Click-to-Attend link is an icon. (This is the default.) If the registry value is set to 0, then the Click-to-Attend link is an embedded URL. If you want the embedded URL, you must add <!-- #LATD AttendConference --> to the NotifySchedule.tpl and NotifyReSchedule.tpl templates, located at drive:\latitude\MeetingPlace Notification Gateway. (No need to edit the others.)
-
Verbose Logging—If the registry value is set to 0, then regular logging is used. (This is the default.) If the registry value is set to 1, then verbose logging is used. (This setting should be used only for troubleshooting.)
-
WebPublisher Hostname—If a value is entered in this field, then a Click-toAttend link icon or embedded URL is present in notifications. If the value is blank, then there will not be a Click-to-Attend link or embedded URL in notifications.
Related Information
- Voice Technology Support
- Voice and Unified Communications Product Support
- Recommended Reading: Troubleshooting Cisco IP Telephony

- Technical Support - Cisco Systems
| Updated: Jan 31, 2006 | Document ID: 50025 |
