Core Issue
Unexplained server or meeting failures, or attendees being disconnected from meetings, will require logs to be collected in order to determine the cause of the problem.
Resolution
In order to collect the appropriate logs, follow these steps:
MeetingPlace audio server log collection process:
- Contact Technical Assistance Center(TAC) by opening a service request, and request for the 'PWOD' (password of the day) for the 'su' user.
- Telnet to the audio server, and login as 'tech' user.
- At the su user prompt, type 'infocap -bMMDDHHMM -eMMDDHHMM (MM=month, DD=day, HH=hour24, MM=minute).
- This will generate a file named caselog.tar.gz
- FTP upload this file, and send to TAC, and specify the approximate time of the failure, Meeting ID, any calling and called numbers.
Profile IDs MeetingPlace Web Server log collection process:
- Login to the MPWeb server, and open a CMD prompt
- At the CMD prompt, change directory (cd) to the Latitude\MeetingPlace Gateway SIM subdirectory (eg: cd\Program Files\Latitude\MeetingPlace GatewaySIM)
- At the prompt, type "eventlog >> events.txt" which will parse and generate a log file named events.txt. This file could be large
- Save the Windows Event Viewer Application and System logs as a .csv file
- Upload this information to TAC, and specify approximate time of the failures
For related information on troubleshooting MeetingPlace issues, refer to:Troubleshooting TechNotes
