Equisys Technical Notes

Technical guidance, explanations and fixes for our products

HOWTO: Configuring for local exchanges using Zetafax dialing properties

Print

ZTN1732

ID: ZTN1732

This Zetafax technical note applies to:

  • Zetafax 2009
  • North American systems using a mix of 10-digit dialing and 7-digit dialing (local exchanges) within the same area code

Summary

This document describes how to configure Zetafax dialing properties in locations where the area code must be omitted for a specific list of exchanges within that area code.  This is a typical requirement in some areas of North America which are transitioning to full 10-digit dialing.

An alternative approach may also be used to achieve the same ends, using the dialing rules within Windows dialing properties (“TAPI settings”).  However using Zetafax dialing properties as described below is generally simpler to configure and support, and is recommended for locations with 20 or fewer local exchanges.

More information

North American phone numbers typically comprise a 3 digit area code followed by a 3 digit prefix (exchange). 

Phone numbers in a different area code are typically dialled in full, prefixed by the national carrier code (typically “1”).  Phone numbers in the same area code may either need to be dialled in full (10-digit dialing) or dialled with the area code removed – depending on the phone company and whether the number is in the same exchange or another local exchange.  In some cases there is a specific list of local exchanges; in other cases there is a specific list of “non-local” exchanges instead.

Microsoft Windows includes dialing rules which can be configured to add or remove the area code from dialled numbers automatically when required – these are referred to as “Windows TAPI” (Telephony API) settings.  Zetafax can be configured to use these TAPI rules from Windows to edit fax numbers being dialled.

Zetafax also includes a simplified alternative to these TAPI rules, referred to as “Zetafax dialing properties”.  These are usually recommended in cases where they offer the required flexibility, as they are simpler to configure and maintain if the server is moved to a different computer, and are common across different versions of Windows.

Zetafax dialing properties are configured using the Zetafax Configuration program.  Although this supports lists of “non-local” exchanges within an area code, the user interface does not permit a specific list of local exchanges to be configured.  However it is still possible to use this mechanism with a list of local exchanges by configuring this in a different manner.

This technical note describes a way of configuring Zetafax with a list of local exchanges bypassing this user interface.  This approach is recommended in cases where the number of such local exchanges is small (20 or fewer), or can be defined with 20 or fewer “matching” rules.

Companies requiring more complex rules, or with more than 20 local exchanges, can use the Windows TAPI settings.  This is described in a separate technical note, included in the “References” section below.

Configuration

Using the Zetafax Configuration Program, display the "Telephone dialing properties" panel and select the "use dialing properties" .

Click "Configure" to display the "Dialing properties"screen, then select "Use Zetafax dialing properties" .  Enter the area code, and national and international access codes.

Select "Always dial area code" and "Include the National access code" .  This will ensure that all numbers are converted to a standard format by the Zetafax server before it applies the rules for local exchanges.

If you have previously configured any area rules within Zetafax, remove these by clicking the "Area rules" button and deleting the rules.  These are used for specifying an explicit list of non-local exchanges (exchanges where the area code should be added), rather than a list of local exchanges as in this case.

Now, edit the file SETUP.INI (in folder program files\Zetafax Server\SYSTEM\Z-DB) using Notepad.  Locate the [QUEUEMAN] section, then add lines similar to the following to the end of that section (without the two "< < ... > > " lines).

< < start of text > >

; Telephone number editing rules for local exchanges, to remove the access code ; and area code when dialing these numbers.  Note that the system should be

; configured to use Zetafax dialing properties, and for 10 digit dialing, so

; that the numbers are in standard format before processing these rules

; A maximum of 20 rules can be specified, though the comparison numbers may be

; different lengths (eg all prefixes starting with a given 2 digits could be

; handled with a single rule)

TelnumEdit: "1541222" "222"

TelnumEdit: "1541333" "333"

TelnumEdit: "1541444" "444"

< < end of text > >

The text given above configures 3 local exchanges for the 541 area code: "541 222 ..." , "541 333 ..." and "541  444 ..." .  Replace these with the correct lines for your area code and list of local exchanges.

You can also include partial matches and exceptions in the list if required - for example the following lines would treat all "541 55x ..." as local exchanges except "541 555 ..." :

TelnumEdit: "1541555" "1541555"

TelnumEdit: "154155" "55"

A maximum of 20 lines may be included.  Note that lines are processed in order from top to bottom, and all matching rules will be applied until one is found where no modification is made (as with the first line in the example above).

After making the changes, the SETUP.INI file should look similar to the following.  Save the updated file, then restart the Zetafax Server if already running to apply the changes.

Testing

You should now test the TAPI settings using the Zetafax Client.  (Note that it is not possible to use the Zetafax dialing properties screen to test this as it does not process TelnumEdit settings).

Send a test fax to a range of number types, check the server log which shows the number which is being dialed.  The server log is displayed in the Zetafax Server Monitor program, and also stored in Program Files\Zetafax Server\SERVER\Z-DB\SERVER.LOG.

Message sent from Zetafax Client:

Results from server log:

11:51:41            QUEUEMAN     Phone number changed to '15418881234'

...

11:52:11            QUEUEMAN     Phone number changed to '2221234'

...

11:52:41            QUEUEMAN     Phone number changed to '17708881234'

...

11:53:11            QUEUEMAN     Phone number changed to '011442072034000'

References

ZTN1733-HOWTO Configuring for local exchanges using Windows TAPI settings

Last updated: 17 April 2009 (GW/AA)

EquisysLogo

Recent news

This article describes the new features and other improvements in the August 2019 release of the Zetadocs Expenses service. Zetadocs Expenses ...

This article describes the new features and other improvements in the latest release of Zetafax. This improves support for using Fax over IP (FoIP) with SIP trunks and public SIP fax services, ...