MSN Messenger - help with Voice

[Accessdabbler]

I'm using an SMC Barricade 7004ABR router. I'm going to "go postal" if I can't get this f***ing thing to work with MSN Messenger.

I can use all of Messenger's features EXCEPT for Voice Chatting.

I have a packet sniffer and it showed that the source TCP port was 1863 and the destination was 1093.

I've tried "opening" this port (and ALL ports from 1-65535) and still no connection.

I've tried adding my computer to the Demilitarized Zone - nothing.

I tried turning off the router firewall function - nada.

Does anyone else out there have this router and use MSN voice chat?

(now, where did I put that shotgun...)

 

[hexn]

Perhaps it is something beyond your router?

Your ISP?

The MSN Voice service is down?

 

[robca]

I have the same problem i can't do voice conversations with msn-messenger since my Belkin router is here

 

[audiopimp]

I work for a VOIP company and there are a few things you might want to consider. I know for a fact that often NAT on cheap routers, although I do not know where yours stands by those terms but often its a NAT issue. You can determine this from a choppiness in audio either way. Something else to consider, sometimes firealls (ie PIX) when behind NAT they block RTP and RTCP ports for voice to pass. This would be your ISP problem and there for probably won't want to modify anything for you...
If you try with a direct IP m pretty sure you wouldnt get this problem, but I know that is not a solution.

 

[Sealzzz]

Have you tried upgrading to its latest firmware? See the link below:

http://www.smc.com/index.cfm?action=products_downloads&productCode=SMC7004ABR&prod_id=67

 

[smah]

Accessdabbler, I think we had this conversation before. Sometime after that, I found a list on MS's site of uPnP routers that would support voice communication with messenger, but I can't find it again . Here's a good article about using NAT with messenger:

http://www.microsoft.com/windowsxp/pro/techinfo/deployment/natfw/default.asp

It might be worth noting, that:

1) both ends of the transmission need to be set correctly for voice to work - aka you may be set correctly, but the other person may not be.
2) it definately won't work through nested NAT/firewall devices, so if your ISP uses some nat/firewall device and you use some nat/firewall device it won't work.
3) I didn't look to see if your router supports UPnP, but if it does, you might want to make sure you have UPnP enabled on your pc - use your own judgement about the possible security ramifications.

If all else fails, have a look at this:

http://www.topshareware.com/DirectTalk-for-MSN-Messenger-download-1655.htm

I haven't used it, so I don't know if it works as well as it says. I also suspect that it still won't work if any of the 'problem conditions' exist - nested NAT devices etc.

 

[Accessdabbler]

Thanks smah. My original question was posted 2 months ago but I still don't have a definitive answer.

My router does not support UPnP. I haven't taken the time to figure out what UPnP is. I do know that it is bad (according to

http://www.grc.com).

I'm sure that my ISP does not use NAT (they charge extra for firewall and virus-scanning services).

As for the other person's setup, I don't know what they would need to configure. Two people I try to converse with use Win98 and 1 uses WinXP.

Either way, I'm sure the NAT is the problem since I can get the chat to work if I disconnect my broadband router and connect directly to the ISP (not a secure option).

I have tried using ZoneAlarm instead of the router (I currently only have 1 PC anyway) but I was unable to configure ZA to work with the voice. I haven't tried the full version of ZA but I think I should give it a-tinkerin'.

Strangely, file downloading is also not supposed to work, but it works fine.