Enterprise Vault.cloud™ Lync Connector Administration Guide
- About Lync Connector
- Introduction to Enterprise Vault.cloud Lync Connector
- Changes in Lync Connector version 1.2.2
- Lync Connector release history
- Lync Connector architecture
- The components of Lync Connector
- About Lync Connector synchronizations
- Conference transcript availability options
- About SIP address substitution
- About the format of the archived transcripts
- About the archiving of historical data
- Lync Connector evaluation mode
- About the Lync Connector Console
- Requirements for Lync Connector
- Steps for setting up archiving with Lync Connector
- Installing Lync Connector
- Configuring Lync Connector
- Configuring Lync Connector
- Configuration wizard page 1: Enterprise Vault.cloud credentials
- Configuration wizard page 2: Lync archiving database
- Configuration wizard page 3: Working folder
- Configuration wizard page 4: File management
- Configuration wizard page 5: Active Directory
- Configuration wizard page 6: SMTP
- Configuration wizard page 7: Sender email address
- Configuration wizard page 8: Conference transcript availability
- Configuration wizard: Configuration complete page
- Viewing or changing the credentials of the Lync Connector service account
- Managing archiving with Lync Connector
- Managing SIP address substitution
- Lync Connector workflow
- Lync Connector reports and logged events
- Lync Connector advanced settings
- Troubleshooting Lync Connector issues
- About troubleshooting Lync Connector issues
- Use of Lync 2013 clients with a Lync 2010 server
- Lync archiving database export failure errors
- Synchronization failures
- Transcript processing failures
- SMTP server issues
- Failure reason: "Message size exceeds fixed maximum message size"
- About the Lync Connector trace logs
- Accessing the trace logs
About the format of the archived transcripts
Figure: Example Lync transcript email message in Personal.cloud shows how a Lync transcript appears in Personal.cloud for each participant.
The transcript email messages have the following properties:
For a two-person conversation, the initiator is assigned as the sender of the email, and the other person is the recipient.
For a conference, the initiator is assigned as the sender of the email, and the other participants are the recipients. All of the participants of a conference are included as recipients, including those participants who joined late or left early.
The subject of the email message indicates the communication type, which is conversation for a two-person conversation, otherwise conference. The subject then shows the SIP addresses of the conversation participants or the conference organizer. For example:
Conversation between user1@domain and user2@domain
The start time of the conversation or conference is used as the date of the email message.
The Lync conversation forms the body of the email message.
Conference session information is included as attachments. This information includes a record of the users who joined and left the conference.
Conference handouts are included as attachments.
The time of each interaction in the conversation or conference is shown in Coordinated Universal Time (UTC).
If Lync Connector performed SIP address substitution, the From and To fields of the transcript email message use the substituted email addresses.
The example in the figure shows the effect when Lync Connector replaces a participant's SIP address with an email address that differs from the SIP address. In this example the initiator's SIP address is lync5@domain.local but the email address is lyncuser5@domain.local. Lync Connector has replaced the SIP address with the email address in the From fields of the message. The SIP address is retained in the title and the body of the email message.