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
Resolving issues caused by SIP substitution failures
If a SIP address substitution failure causes a problem you can add an entry to Lync Connector's manual address mapping file, SipAddressMapping.csv. Lync Connector uses any mappings in this file in precedence to the results of its Active Directory lookup. You can therefore use entries in this file to override the results of an Active Directory lookup, as well as to circumvent any email address lookup failures.
To resolve issues caused by SIP substitution failures
- In Windows Explorer go to the Lync Connector configuration folder, at the following location:
If you use the Veritas-branded version of Lync Connector:
%ProgramData%\Veritas\EV.Cloud\Lync connector\configuration
If you use the Symantec-branded version of Lync Connector:
%ProgramData%\Symantec\EV.Cloud\Lync connector\configuration
where %ProgramData% is the value of the ProgramData environment variable, typically C:\ProgramData.
- Open the SipAddressMapping.csv file with a text editor, such as Notepad.
- Edit the file to add an entry for each required mapping, in the format:
SIPaddress,EMAILaddress
Separate the SIP address and its corresponding email address with a comma. See the comments at the beginning of the file for more information.
Note:
Entries that begin with a semicolon are treated as comments, and are ignored.
- Save the changes to the file.
Note:
Remember to keep the file in .csv format.