
VoIP White Paper
300 Main Street • East Rochester, NY 14445 • Toll Free 1-866-ALLWORX • 585-421-3850 • www.allworx.com
© 2006 InSciTek Microsystems, Inc. All rights reserved. Allworx is a registered trademark of InSciTek Microsystems. All other names may be
trademarks or registered trademarks of their respective owners.
Revised: February 8, 2007
Page 25
attendant mechanism should always work. It can be applied individually to each station to isolate the devices
that have configuration or connectivity concerns.
14.7 Mapping ports through remote phone firewalls
When an Allworx server has remote phones at multiple sites and each site has a NAT/Firewall device between
the phone and the Internet, the remote phone’s RTP ports must be statically mapped through the firewall if you
want to call each other. It is not necessary to do this if remote phones only need to call the main office (and not
each other). The steps to perform this operation vary by the type of firewall that the remote phone uses, but the
basic goal is to map a range of UDP ports on the firewall’s IP address to the LAN address ports of the IP
phone. The Allworx server’s admin page for each handset allows you to control the range of ports the phone
will use for RTP sessions under UDP. On the firewall product’s configuration page, you need to map those
same ports (one-to-one) through the firewall – thereby allowing access from the WAN to LAN through those
ports. Some products call this “DMZing” those ports or “port mapping.” The phone’s LAN IP address must also
be entered into this firewall configuration page, so is it wise to make sure this address will be fixed.
Kommentare zu diesen Handbüchern