Can I use voice from behind a firewall?

From Second Life Wiki
Revision as of 23:13, 5 October 2009 by Fritz Linden (talk | contribs) (Revised Parature import)
Jump to navigation Jump to search
Kb-seal.png

This article is part of the Extended Second Life Knowledge Base that includes advanced and specialized information. This information was originally provided by Linden Lab, but is not actively maintained nor guaranteed to be accurate. Linden Lab does not certify nor assume any responsibility for this information.

See the official Second Life Knowledge Base for the most current information.

Voice, like Second Life® itself, is designed to work with "zero configuration" and should work with most firewalls. Your firewall software may request permission to let "SLVoice.exe" and "SLVoiceAgent.exe" access the internet on their first execution; you should allow this access.

The following ports need to be reachable through any firewall infrastructure:

  • Ports 12000-17000 - UDP - for voice media
  • Port 80/443 - TCP - for Web server
  • Ports 5060 or 5062 - UDP - for voice control signals
  • Ports 3478/3479 - UDP - to aid in setting up voice with NAT

The current production IP ranges:

  • 64.34.14.0/24
  • 70.42.62.0/24
  • 74.201.98.0/23
  • 64.127.104.64/30
  • 64.127.112.104/29
  • 64.127.121.88/29
  • 64.127.123.192/26
  • 64.147.162.0/26
  • 64.147.180.128/27
  • 69.80.215.224/30

If the SIP connection on port 5060 fails (as it might if the router is designed to provide VoIP services of its own), the Second Life Viewer will automatically retry on port 5062. This means that port 5062 may need to be opened on some restrictive firewalls in rare instances.