System information
System Administration Guide
300 Main Street • East Rochester, NY 14445 • Toll Free 1-866-ALLWORX • 585-421-3850 • www.allworx.com
© 2007 InSciTek Microsystems, Inc. All rights reserved. Allworx is a registered trademark of InSciTek Microsystems.
Revised: March 28, 2007
Page 23
7.2.2 Details about SIP Gateways
Many parameters associated with SIP Gateways are the same as their counterpart under SIP proxies. In
particular, all the Advanced Settings are identical. See the SIP Proxy section above for more information
about the common fields. Parameter information specific to SIP Gateways is detailed here.
Gateway uses SIP Registration
– This parameter selection requires the definition of the Login ID and
Password the gateway will use to register with Allworx, assuming the gateway supports SIP registration. This
is the desired configuration to use especially if the gateway uses DHCP to obtain its IP address so that the
Allworx always knows how to contact the gateway for outbound calls.
Gateway uses Static IP Address
– This parameter selection is used when the gateway does not support
registration or when you do not wish to authenticate the gateway. Contacting the gateway through this
mechanism requires the gateway to have a static IP address. DNS names are not allowed for security
reasons.
Prefix String
– This parameter defines DTMF digits to be prepended to the dialed number string when placing
outbound calls through the gateway (e.g. ‘9’ for dialing through another SIP PBX).
7.3 Enterprise Dialing Feature
Allworx
supports multi-site configurations using remote phones and remote servers. Remote phones are
adequate for individual remote users that need access to the phone services of the office. Remote servers
provide independent phone services per site, but with point-to-point dialing between users at the sites via the
Internet. The Remote Servers functionality is referred to as Site-to-Site Calling. See the Remote Server Multi-
site Calling section for more information.
While the Remote Servers functionality is fully integrated and easy to configure, since the remote servers
need to be configured in a full mesh fashion; each site must know about all other sites. While this works well
for small installations, more than ten sites can become more difficult to administer.
The Enterprise Dialing feature in Allworx is designed to address this by allowing a third party SIP server to be
the central hub for all calls between sites. This provides a centralized phone book and administrative service
for the entire VoIP network.
Note: The required centralized server functionality referred to in this section is not an application currently
available from Allworx. The Allworx servers themselves are designed to be able to integrate with such
an enterprise level infrastructure, but not to host the Enterprise Server functionality itself. Such SIP
Proxy Enterprise Servers are available from other providers.
7.3.1 Allworx
Enterprise Client
Each Allworx
server can be configured as an enterprise client and direct inter-office calls to the central hub. A
SIP Proxy is created for the central hub, with the call routing set to Proxy is an enterprise server. The
Enterprise Dialing rule (Phone System / Dial Plan web page) is set to a service group that contains just the
SIP Proxy entry for the central hub server. The number of digits to collect/send is set to cover the entire
enterprise.
The Allworx
dial plan uses an ‘8’ prefix to indicate that the dialed number is to be forwarded to the Enterprise
Server. For example, dialing 81234 will send a SIP INVITE with a URI of <sip:1234@centralHubServer> to
the Enterprise Server.
7.3.2 Central Hub / Enterprise Server
The central hub is a SIP proxy server that accepts incoming INVITEs from the Allworx
servers, determines
the final destination for the request, and forwards the request to the destination Allworx. It maintains an active