Koozali.org: home of the SME Server

How do I make Dialpad work?

Randy

How do I make Dialpad work?
« on: April 27, 2000, 11:41:45 AM »
hi every body,

  I hope that sombody out there can help me out. I really like my esmith server and have ben using it for quite some time, however I just started using Dialpad (www.dialpad.com  --- free longdistance over the internet)
and I can send messages and the person i called receives the messages, but I don't get any of there messages.
 there is probebly just some port that i need to open up in the masq but I don't know whst port or how to open it up. Can sombody please help?

thanks
Randy

Charlie Brady

RE: How do I make Dialpad work?
« Reply #1 on: April 27, 2000, 03:51:04 PM »
Randy wrote:

> I hope that sombody out there can help me out. I really like my
> esmith server and have ben using it for quite some time,
> however I just started using Dialpad (www.dialpad.com  --- free
> longdistance over the internet) and I can send messages and the
> person i called receives the messages, but I don't get any of
> there messages. there is probebly just some port that i need to
> open up in the masq but I don't know whst port or how to open
> it up. Can sombody please help?

You should be able to find out from Dialpad what protocols and ports you need open to make a connection. If you search this bulletin board you will find some hints on how to enable incoming connections to a machine on your LAN. Ask here if you need further help. You should be aware that this is a potential security risk, if the Dialpad software is not secure.

Regards

Charlie

Carl Milloshewski

RE: How do I make Dialpad work?
« Reply #2 on: April 27, 2000, 07:25:49 PM »
Charlie is correct, the dialpad FAQ or knowledge base has a list of UDP ports that need to be forwarded.

Here is a cut from their support page:
************
If you have a private network, you can call someone but you can't hear them. The incoming voice packets cannot find their way to your PC without an IP address. This can be fixed.

Map the following incoming ports on the server:

      UDP: 51200, 51201
      TCP: 51210

If you need a trigger, use TCP: 7175 (outgoing)

There are many software/hardware solutions for routing traffic on a private network. Although they have different ways of configuring the ports, they basically work in the same way. Here are several known solutions. If you have a software/hardware solution that is not listed in here, please let us know so that we can add it.


Linux IP Masquerading (2.2.x kernel)
(Thanks to Allen Rotton and Eric Jorgensen)
If you're using a firewall, then enable the UDP: 51200, 51201, and TCP: 51210.
In your /etc/rc.d/rc.local, add the following lines and reboot:
/usr/sbin/ipmasqadm autofw -A -v -u -r udp 51200 51201 -c tcp 7175
/usr/sbin/ipmasqadm autofw -A -v -u -r tcp 51210 51210 -c tcp 7175

Also, please take a look at http://my.ispchannel.com/~rottona/linux_dialpad.html
*************

I don't think the port forwarding utilities are installed by default.

Carl