Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration
Which transfer method is my client using?
Debug sametime client logs are needed to determine this:
1.
Open sametime.properties
2.
Set “.level” to “FINE” (.level=FINE). NOTE: do not confuse ‘.level’ with ‘logger.level’.
3.
Use your client for file transfer
4.
Go to the Sametime user folder (this is not the install folder; the Sametime user folder can found
within the user’s C:\Documents and Settings folder)
5.
Locate file name sametime.log.0
Server (RTC) file transfer logging will look like this:
[com.ibm.collaboration.realtime.filetransfer.FileTransferServiceFactory.
getService] ::FINE:: File Transfer enabled in Policy
[com.ibm.collaboration.realtime.filetransfer.FileTransferServiceFactory.
getService] ::FINE:: Virus scanning is available for this file transfer
[com.ibm.collaboration.realtime.filetransfer.FileTransferServiceFactory.
getService] ::FINE:: Virus Scanning is enabled. Using RTC file
Transfer.
[com.ibm.collaboration.realtime.filetransfer.rtc.FileTransferServiceRtc
.fileTransferStarted] ::FINE:: RTC File Transfer Started...
[com.ibm.collaboration.realtime.filetransfer.rtc.FileTransferServiceRtc
.fileTransferCompleted] ::INFO:: RTC File Transfer Completed
P2P file transfer logging will look like this:
[com.ibm.collaboration.realtime.filetransfer.FileTransferServiceFactory.
getService] ::FINE:: File Transfer disabled in Policy. Using P2P.
[com.ibm.collaboration.realtime.filetransfer.FileTransferServiceFactory.
getService] ::FINE:: Virus scanning is not available
[com.ibm.collaboration.realtime.filetransfer.
.startTransfer] ::FINE:: Transfer started...
p2p.FileSender
[com.ibm.collaboration.realtime.filetransfer.p2p.FileSender
.closeFileInputStream] ::FINE:: Closing file input stream...
[com.ibm.collaboration.realtime.filetransfer.p2p.FileTransferServer.addF
ileSender] ::FINE:: added id1155131608343
[com.ibm.collaboration.realtime.filetransfer.p2p.FileTransferServer.star
tServer] ::FINE:: Starting filetransfer server on port 5656
[com.ibm.collaboration.realtime.rtcadapter.meeting.ChatAdapter.messageRe
ceived] ::FINE:: messageReceived [meeting CONV$4DEA2B75C606C469] msg
type: text
[com.ibm.collaboration.realtime.filetransfer.p2p.FileSender.onTransferAc
cepted] ::FINE:: [Transfer accepted] notice received
[com.ibm.collaboration.realtime.filetransfer.p2p.FileSender.onTransferAc
cepted] ::FINE:: Transfer accepted by receiver. Testing connectivity...
Voice chat and Network Address Translation (NAT)
The Sametime 7.5 voice chat component provides Voice over IP (VoIP) services. To work correctly, voice
chat needs to have the network configured properly. Voice chat works with UDP packets; it needs UDP
ports to be opened on the firewall of every 7.5 client. The clients are using a single port (UDP port 20830)
for all audio chats; this port needs to be opened for both incoming and outgoing UDP traffic.
Voice chat operates in two different modes:
z
Direct P2P connection: UDP packets flow directly between users
z
Reflector connection: UDP packets go through an audio proxy, called a "reflector", which is a
piece of code installed with the Sametime 7.5 server
27