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)
And they also add:
Linux 2.0.x or ShareTheNet (Thanks to David
Ruggiero)
In /etc/rc.d/rc.local (ShareTheNet users,
use "Advanced Setup>Advanced
Options>Manual Startup Commands"), add the
following lines:
#for dialpad.com
#external static IP address
IP_REAL="xxx.xxx.xxx.xxx"
#internal non-routable IP address of target
PC (e.g. 10.10.xx.xx or 192.168.zz.zz)
TOIP_PC="zzz.zzz.zzz.zzz"
ipportfw -C
ipportfw -A -t$IP_REAL/51210 -R
$TOIP_PC/51210
ipportfw -A -u$IP_REAL/51201 -R
$TOIP_PC/51201
ipportfw -A -u$IP_REAL/51200 -R
$TOIP_PC/51200
ipportfw -L
#end of dialpad.com setup
So, when I add this to the manual startup and click OK, I get
configuration updated. When I reboot and look at the bottom of the boot
log, I see:
ShareTheNet VERSION=2.1.3
ipportfw: illegal local address/port specified
ipportfw: illegal local address/port specified
ipportfw: illegal local address/port specified
Prot Local Addr/Port > Remote Addr/Port
Obviously an error somewhere. I noted that the dialpad/Sharethenet
piece offered is for 2.0.x. Is there a different syntax for 2.1.3? And
if so, looking at the piece above, what should it be?
Can I skip the manual add and activate the ports through
Network/Configure/User Specified Inbound Services?
And, if so, then should it look like:
Service En Prot
Port IP Address
USER1 X udp 51200
USER1 X udp 51201
USER1 X tcp 51210
For the IP Address, does it mean the workstation IP or the Server IP
(external or internal)?
If workstation, should I leave it blank for all workstations, or is
there a wildcard like noted in the above as TOIP_PC="zzz.zzz.zzz.zzz" or
can I just type: zzz.zzz.zzz.zzz? The actual workstation IP is
192.168.0.103.
If server, should I be adding the external, outbound IP, (which is
provided by AT&T Cable) as bound by my external nic? And again if it is
for the real IP, ie on the external nic (as it can be dynamic) should it
be noted as IP_REAL="xxx.xxx.xxx.xxx" or can I just type
xxx.xxx.xxx.xxx?
I'm a novice at these things, but always willing to learn?
Thanks in advance for your help.
Arnie Rothenbaum
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
______________________________________________
Faster, stronger and able to send millions
of emails in one click: the new Topica site!
http://www.topica.com/t/14
