If your Sametime® deployment
experiences problems with NAT traversal, begin by troubleshooting
the Sametime TURN Server.
About this task
Attention: Diagnostics should only be enabled
only when you are advised to do so by IBM® Technical
Support. IBM Technical Support
will determine whether extended diagnostics are required.
Procedure
- On the TURN Server, navigate to the directory where the
TURN Server files were installed (for example, C:\TURN).
- Open the logging.properties file for
editing.
- Change the following settings as shown:
java.util.logging.FileHandler.level=ALL
java.util.logging.ConsoleHandler.level=ALL
com.ibm.stun.level=FINER
com.ibm.turn.server.level=FINER
com.ibm.network.agent.level=FINER
Trace levels are:
- FINE: Information logs as well as severe messages
- FINER: Information logs and all messages
- FINEST: ALL logs
- Save and close the file.
- Stop the TURN Server by pressing Ctrl + C.
- Restart the TURN Server by running the batch file again.
What to do next
If you cannot isolate a problem on the TURN Server, you may
need to troubleshoot other Sametime components that
are involved in NAT traversal:
- Sametime Connect
Client
- Sametime web audio-visual
plugin
- Sametime Proxy Server
- Sametime Media Manager
- SIP Proxy/Registrar component