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 SIP address substitution failures
By default, Lync Connector attempts to substitute SIP addresses with email addresses in the extracted Lync transcripts. Lync Connector performs an Active Directory lookup of the SIP address to find the associated email address.
See About SIP address substitution.
In some cases the Active Directory lookup may find that no user is associated with the SIP address, or that no primary email address is listed for the SIP address. For example in a federated environment the lookup for all external users fails. For internal users the lookup can fail if the SIP address has changed, or if the user has left the company and their Active Directory user object has been deleted.
If Lync Connector fails to find the email address for a SIP address it retains the SIP address in the transcript. In cases where company policy is to use identical SIP addresses and email addresses, this fall-back option should result in the transcript being routed to the user's archive. However, if the SIP address is different from the email address, the transcript is unlikely to be routed correctly.