media through proxy for live meeting service
- As I know, media is not supported through proxy with Authentication for live meeting service
Administrators are ready to disable Authentication on proxy for spesial IP addresses
Where can I find IP addresses for media in Microsoft live meeting service?
P.S I know about possibility to use firewall client, but this question about how to deal with Microsoft live meeting service without firewall client
Answers
Hi Alexander,
You must disable proxy authentication for the following range of IP addresses so that user authentication is not required for the Live Meeting 2007 service:
64.41.193.0/24
209.1.15.0/24
216.34.51.0/24
204.79.188.0/24
216.32.182.0/24
204.176.46.0/24
65.221.5.0/24
204.79.179.0/24
216.32.242.0/24
193.221.113.0/24
194.110.197.0/24
When you use audio and video in a Live Meeting 2007 session, Live Meeting 2007 uses one of the following methods:
l Live Meeting 2007 uses a direct connection to a media relay.
l Live Meeting 2007 uses the proxy settings that are configured in Windows Internet Explorer to connect through an HTTP proxy connection.
The following two protocols are used for audio and for video in Live Meeting 2007:
l User Datagram Protocol (UDP) port 3478
l Transmission Control Protocol (TCP) port 443
Typically, UDP is preferred for performance. However, UDP connections can cause network congestion. Audio and video use TCP if UDP ports are blocked. TCP lowers network congestion. However, TCP also lowers the quality of audio and of video. Audio is affected the most when TCP is used because the ear is more sensitive
When you connect to Live Meeting Manager, SSL port 443 is used. This is a Web site where meetings can be scheduled and updated over the Internet.
To enable users to watch streaming recordings of a video or to hear streaming recordings of audio, the following range of streaming ports is used:
TCP ports 80, 443, 554, 1755, 7070
UDP ports 1755 and 5055
For your information:
Application
Protocol
Ports
Features
Meeting Console
(LM2003 - LM2007)
HTTP
TCP 80
Slide transfers, custom pane, web slides, Getting started pane, connection to Media Server for negotiating IAB stream (LM2005)
HTTPS (SSL)
TCP 443
PWRPC, AppSharing
HTTPS (TLS)
8000-8100 (2005)
8057 and 3478 (2007)
PWRPC, AppSharing
Optional - will fall back to 443 if probe fails
(LM2005)
RTSP
TC
LM2007)
SIP
5060
Connection to Office Communication Server
SIP-TLS
5061
Connection to Office Communication Server
Live Meeting Manager
(aka Rapid)
HTTP
TCP 80
Redirects to HTTPS for Login and all subsequent page service
HTTPS (SSL)
TCP 443
All web UI
Windows Media Player
HTTP
TCP 80
Connection to Media Server for negotiating recording playback
RTSP
TCP 554
Streaming media
MMS
TCP 1755 or
UDP 1755
Streaming media for recording playback (no longer supported in WMP11)
Hope this helps.
Lu Zou- Marked As Answer byLu Zou-MSFTMSFT, ModeratorThursday, September 17, 2009 7:56 AM
All Replies
Hi Alexander,
You must disable proxy authentication for the following range of IP addresses so that user authentication is not required for the Live Meeting 2007 service:
64.41.193.0/24
209.1.15.0/24
216.34.51.0/24
204.79.188.0/24
216.32.182.0/24
204.176.46.0/24
65.221.5.0/24
204.79.179.0/24
216.32.242.0/24
193.221.113.0/24
194.110.197.0/24
When you use audio and video in a Live Meeting 2007 session, Live Meeting 2007 uses one of the following methods:
l Live Meeting 2007 uses a direct connection to a media relay.
l Live Meeting 2007 uses the proxy settings that are configured in Windows Internet Explorer to connect through an HTTP proxy connection.
The following two protocols are used for audio and for video in Live Meeting 2007:
l User Datagram Protocol (UDP) port 3478
l Transmission Control Protocol (TCP) port 443
Typically, UDP is preferred for performance. However, UDP connections can cause network congestion. Audio and video use TCP if UDP ports are blocked. TCP lowers network congestion. However, TCP also lowers the quality of audio and of video. Audio is affected the most when TCP is used because the ear is more sensitive
When you connect to Live Meeting Manager, SSL port 443 is used. This is a Web site where meetings can be scheduled and updated over the Internet.
To enable users to watch streaming recordings of a video or to hear streaming recordings of audio, the following range of streaming ports is used:
TCP ports 80, 443, 554, 1755, 7070
UDP ports 1755 and 5055
For your information:
Application
Protocol
Ports
Features
Meeting Console
(LM2003 - LM2007)
HTTP
TCP 80
Slide transfers, custom pane, web slides, Getting started pane, connection to Media Server for negotiating IAB stream (LM2005)
HTTPS (SSL)
TCP 443
PWRPC, AppSharing
HTTPS (TLS)
8000-8100 (2005)
8057 and 3478 (2007)
PWRPC, AppSharing
Optional - will fall back to 443 if probe fails
(LM2005)
RTSP
TC
LM2007)
SIP
5060
Connection to Office Communication Server
SIP-TLS
5061
Connection to Office Communication Server
Live Meeting Manager
(aka Rapid)
HTTP
TCP 80
Redirects to HTTPS for Login and all subsequent page service
HTTPS (SSL)
TCP 443
All web UI
Windows Media Player
HTTP
TCP 80
Connection to Media Server for negotiating recording playback
RTSP
TCP 554
Streaming media
MMS
TCP 1755 or
UDP 1755
Streaming media for recording playback (no longer supported in WMP11)
Hope this helps.
Lu Zou- Marked As Answer byLu Zou-MSFTMSFT, ModeratorThursday, September 17, 2009 7:56 AM
- thank you for very comprehensive answer
We are having problems with our proxy server when we intercept livemeeting traffic. The meeting loads correctly however any tunneled SIP traffic or direct SIP traffic from the client to the source is either not supported by our proxy or blocked explicitly on the inside - in interface of our firewall. We are willing to add an exception for SIP traffic to the livemeeting public IP ranges. Are the Subnets listed above the same subnets that SIP traffic will be sourced from?
Thank you.
