Hoi
Misschien heb je hier wat aan (weet ik niet zeker)
Firewalls and Windows Messenger
Like NAT devices, firewalls can present problems when you’re trying to communicate using Windows Messenger. Problems introduced by firewall devices include:
• The messages used for SIP signaling may come from an external client and seem to be unsolicited from either a dynamic port or port 5060. For these messages to make it to the Windows Messenger client, the ports must be opened on the firewall. For example, when using ICF on Windows XP, port 5060 is blocked by default.
• Ports for media streams and other data, such as the dynamic ports for AV and port 1503 for AS or WB, must be allowed to traverse the firewall.
Working With Different Firewall Configurations
The following section discuss issues related to different firewall configurations:
UPnP-enabled Firewalls
UPnP-enabled gateway devices were discussed earlier in this article. The Windows XP firewall, known as the Internet Connection Firewall, is UPnP- enabled. Windows Messenger in Windows XP uses this capability by opening the ports required for signaling, connections or media streams.
Non-UPnP Firewalls
Very few options exist for using the advanced features of Windows Messenger with a non-UPnP firewall. Points to consider on this topic include:
• Peers on the same side of the firewall can use all of the features of Windows Messenger.
• IM and Presence will work through most firewall configurations.
• To support AV in both directions through the firewall, all UDP ports between 5004 and 65535 must be opened to allow signaling (SIP) and media streams (RTP) to traverse the firewall. This is required because dynamic ports are used. AS and WB also use dynamic ports for signaling.
• FT can be enabled by opening ports 6891 to 6900 on the firewall. Remote Assistance can be enabled by opening port 3389.
Cascading Firewalls
Cascading firewalls can cause problems similar to cascading NAT devices.
Limitations of UPnP in Windows XP
In Windows XP, outgoing calls from Windows Messenger will not work when ICF is enabled on the local interface and the user does not have administrative privileges. This feature will work correctly for users that have administrative privileges.
p.s bij mij werkt het wel als de gene die niet achter firewall zitten op praten drukken en de ander accepteert
