
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 19
11.3 Troubleshooting ABLF
Generally speaking, the ABLF protocol and Allworx devices take care of themselves, even when NAT/Firewalls
exist at the remote sites sitting in front of the remote phones. This is because the Allworx server and phones
work together to safely traverse NAT devices within the same restrictions explored previously when talking
about SIP. It is not even normally necessary to open a specific NAT firewall device port at the remote site to
support ABLF – the phone will keep an automatic port open with the server. In the event that one or more
devices or subnets are not correctly receiving ABLF packet updates, something is probably administratively
blocking traffic on the configured ABLF UDP port (2088 by default). Make sure that nothing is specifically
blocking port 2088 to the Allworx WAN port and that no intermediary NAT/Firewalls limit port 2088 traffic from
local LAN to WAN. If port 2088 is limited or blocked, you can change the Allworx server’s receiving UDP port
as specified previously.
Comentarios a estos manuales