kenw@kmsi.net
December 5th 03, 01:45 PM
Today I tried to help a client make intercontinental voice calls using
Messenger. The challenge here is the we're behind a non-uPnP NAT firewall
which does not, and will not, allow inbound IP connections, as a matter of
security policy.
I knew I'd need a way to deal with the firewall issue, so I looked around
and found a couple of possible solutions -- JDSoft's eNat and Ridgeway's
IPfreedom. I tried the latter.
It was not a pleasant experience. What I discovered, after wasting
considerable time, is that it requires you to use a specific SIP server
service (we used Ridgeway's).
The kicker is that, apparently, any two people who want to communicate must
use the _same_ service and, with IPfreedom, that service apparently cannot
be Microsoft's .NET Messenger Service. ("Apparently" because their support
tech, incredibly, didn't seem quite sure).
So far as I have since been able to determine, no product that provides a
NAT-traversing voice communication product for Messenger will work
Microsoft's .NET Messenger Service. Can this really be true?
If anyone knows of a software product that allows safe NAT traversal for
voice calls with Messenger, I'd dearly love to hear about it.
BTW, what's up with Microsoft Portrait? Would it work?
/kenw
Ken Wallewein
Calgary, Alberta
www.kmsi.net
Messenger. The challenge here is the we're behind a non-uPnP NAT firewall
which does not, and will not, allow inbound IP connections, as a matter of
security policy.
I knew I'd need a way to deal with the firewall issue, so I looked around
and found a couple of possible solutions -- JDSoft's eNat and Ridgeway's
IPfreedom. I tried the latter.
It was not a pleasant experience. What I discovered, after wasting
considerable time, is that it requires you to use a specific SIP server
service (we used Ridgeway's).
The kicker is that, apparently, any two people who want to communicate must
use the _same_ service and, with IPfreedom, that service apparently cannot
be Microsoft's .NET Messenger Service. ("Apparently" because their support
tech, incredibly, didn't seem quite sure).
So far as I have since been able to determine, no product that provides a
NAT-traversing voice communication product for Messenger will work
Microsoft's .NET Messenger Service. Can this really be true?
If anyone knows of a software product that allows safe NAT traversal for
voice calls with Messenger, I'd dearly love to hear about it.
BTW, what's up with Microsoft Portrait? Would it work?
/kenw
Ken Wallewein
Calgary, Alberta
www.kmsi.net