Forum Home
Press F1
 
Thread ID: 55857 2005-03-21 05:56:00 Trouble with using web cam bruceinwdc (4457) Press F1
Post ID Timestamp Content User
336416 2005-03-21 05:56:00 Running XP SP2 laptop Toshiba A75.
Trying to set up web cam sessions, but have been having difficulties.
Using MS Messenger I can communicate with distant parties by instant message, but as soon as I try to contact for a video or voice session I strick problems.
MS Messenger reports I am not "signed into SIP" but when I click on to sign into SIP I get the messages:
"Signing in to SIP Communication Service faile because the service is temporarily unavailable." or
With upgraded versionn to 5.0
"An HTTPS or TCP connection could not be made."
In addiition I am unable to transfer a picture or a voice call on MS Messenger..
I have a wireless router that I have allowed any connection to no avail.
I have upgraded from MS Messager v.4.? to 5.1.
It seems clear this is something to do with some for of blockage to access, some port or something else that is not allowing the correct connection.
First thought was with the MS Firewall. However, turning the firewall off didn't solve the problem.
Any ideas.
BTB, I live in the US, but choose to seek advice from NZ because you guys are by far able to pull all the facts together.
Bruce
bruceinwdc (4457)
336417 2005-03-21 06:19:00 Get the latest patched version of MSN Messenger or the beta versiion of v 7 of it.

I think the other person may have to have the same version as u... as well.
Speedy Gonzales (78)
336418 2005-03-21 06:40:00 Also your router must allow UnPnP (Universal Plug and Play) in order to get audio/video working in XP, and UPnP Framework has to be enabled in the MS Firewall too. It enables Messenger to get through Network Address Translation.
(That's why MSN Messenger audio and video doesn't work in Windows 98, no UPnP in 98, but Yahoo Messenger does :) )

Have a look at this site which has helpful comments:
ask-leo.com
Terry Porritt (14)
336419 2005-03-21 07:08:00 Latest MSN shouldnt make a difference - Its the ports that need opening.

The router doesn _have_ to allow UPnP, but it can make life a little easier
Shut off any personal firewall programs such as BlackIce, ZoneAlarm, etc.

Ports 6891-6900 enable File send,
Port 6901 is for voice communications

Allows Voice, PC to Phone, Messages, and Full File transfer capabilities.

IN TCP 6891 - 6900
IN TCP 1863
IN UDP 1863
IN UDP 5190
IN UDP 6901
IN TCP 6901

Taken from a quick google which lead me to E-E.

This may help also:
www.outpostfirewall.com

BTW Bruce, Welcome to PressF1 :)
Chilling_Silence (9)
336420 2005-03-21 10:27:00 Well, from my experience of using MSN in both Win 98 and Win XP, both with an ADSL router with NAT, which didn't have a capability to open a vast range of ports, to be precise the Dynalink RTA220, I will still have to say UPnP is essential.

[There was no problem with Win98 using dialup and a software firewall.]

Since for audio/video (and here I must disagree Chill) ports in the range 5004 to 65535 are dynamically allocated as researched a long time ago and all the references I have seen confirm this. Therefore, if your router allows such a range to be set, then you are leaving yourself wide open.

Here is what Microsoft say:

<<Audio

* To ensure we deliver the best audio technology for computer-to-computer or computer-to-phone communications from MSN Messenger, we have made technical enhancements. This means you will only be able to use Messenger version 4.5 or higher for these features if:
o You are not behind a firewall or
o You are behind a Universal Plug and Play (UPnP) firewall or
o You are using a UPnP-enabled Network Address Translation (NAT) device>>

messenger.msn.com
Terry Porritt (14)
336421 2005-03-21 14:20:00 Thanks for the replies.
Now some research on opening ports!!
bruceinwdc (4457)
336422 2005-03-21 20:30:00 Also for a heavy read (refers to Windows Messenger, but it's the same with MSN):

www.microsoft.com
Terry Porritt (14)
1