I don't know about how much it's been covered, but DialPad works well for 
me, Arnie...

You DO need to make several accommodations to IP routing..

1. Ensure your DialPad workstation has a static IP address, DHCP won't work 
here..
2. Enable TCP port 51210 to your workstations IP address
3. Enable UDP port 51200 and 51201 to your workstations IP address.

You can turn these off while you're not using DialPad if you wish, but 
unless you're running some type of daemon other than DialPad on *THAT* 
workstation there's really no need...

HopeItHelps!

                                --==jb==--

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
john burton
Midwest City, Oklahoma
1:147/34 @ fidonet

-----Original Message-----
From:   Arnie Rothenbaum [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, January 27, 2000 0:39
To:     [EMAIL PROTECTED]
Subject:        [ShareTheNet]  map incoming ports to make free telephone calls

Dear Thanks for Helping:

I'm sure this has been covered, as nauseum.  But you know how it is.
You just skim it and ignore it until you need it and then can't find it!

I've been playing around with dialpad (dialpad.com) which let's you make
free calls anywhere in the US.  And free is something worth playing
around with, I think.

Anyway, when I make a call, I can be heard by the other party but I
can't hear them.  Ad of course a "firewall" prevents this and is
discussed in the faq from dialpad:

     If you have a private network, even though you can call
     someone, you wouldn't be able to hear the remote end. This is
     because the incoming voice packets cannot find its way to the
     PC without a valid (public) IP address.

     In order to use Dialpad on a private network, you have to map
     the incoming ports on the server. You have to map the
     following incoming ports

     UDP: 51200, 51201
     TCP: 51210
     If you need a trigger for them, use TCP: 7175 (outgoing)

application/ms-tnef

Reply via email to