HOWTO: Configuring for local exchanges using Windows TAPI settings

ID: ZTN1733 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 Windows dialing properties (TAPI settings) on a Zetafax Server, for use 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 Zetafax dialing properties built in to the product. This is generally simpler to configure and support, and is recommended for locations with 20 or fewer local exchanges rather than the mechanism described below. This alternative approach is described in a separate technical note see the References section below.

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. The instructions below describe how to configure and test these rules with a specific list of local exchanges they are based on the user interface in Windows Server 2003, although other versions of Windows should be similar to this. 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 sufficient 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. This alternative approach is described in a separate technical note see the References section below. The remainder of this section describes how to configure and test the Windows dialing rules with Zetafax. Configuration Using the Zetafax Configuration Program, display the "Telephone dialing properties" panel and select the "use dialing properties" ,

http://www.equisys.com/technotes/ztn1733.htm

Click "Configure" to display the "Dialing properties"screen, then select "Use standard TAPI dialing properties"

Click "Edit TAPI settings" to display the Windows TAPI configuration screens. These vary with different versions

http://www.equisys.com/technotes/ztn1733.htm

of Windows - the screens and instructions below are for Windows Server 2003 and will need adapting for other versions of Windows. Configure the area code, and national and international access (carrier) codes. Note that in this example the "carrier code for long distance calls" had to be left blank to prevent the code being added twice for calls to other exchanges - you can check this with the test options described further below.

Select the "Area Code Rules" tab, then add two area code rules. The first rule gives the prefixes in your area code which do not require the area code to be dialled - ie the local exchanges. In this example, 3 local exchanges have been configured ("541 222 ..." , "541 333 ..." and "541 444 ..."

http://www.equisys.com/technotes/ztn1733.htm

Now add a second area code rule which instructs Windows to dial the access code and area code for your own area. This will be used for prefixes (exchanges) which were not explicitly included in the first rule.

http://www.equisys.com/technotes/ztn1733.htm

You should now have two rules configured for this area code, as shown below:

http://www.equisys.com/technotes/ztn1733.htm

Click OK to return to the Zetafax dialing properties screen, then click OK to return to the Zetafax Configuration Program main screen. Now restart the Zetafax Server if already running to apply the changes. Testing You should now test the TAPI settings using the Zetafax dialing properties screen. Test 1: Non local exchange (prefix) - check that the access code and area code are included in the "dialable" number

http://www.equisys.com/technotes/ztn1733.htm

Test 2: Local exchange (prefix) - check that the access code and area code are omitted from the "dialable" number

http://www.equisys.com/technotes/ztn1733.htm

Test 3: Other area code - check that the correct access code and area code are included in the "dialable" number

http://www.equisys.com/technotes/ztn1733.htm

Test 4: International number - check that the correct international access code is included in the "dialable&2:40 PM 5/19/2009; number

http://www.equisys.com/technotes/ztn1733.htm

Test 5: Send a test fax to a range of number types, check the server log which shows the number which is being dialled. The server log is displayed in the Zetafax Server Monitor program, and also stored in file SERVER.LOG (in the folder Program Files\Zetafax Server\SERVER\Z-DB) Message sent from Zetafax Client:

http://www.equisys.com/technotes/ztn1733.htm

10

Results from Server log 11:59:46 ... 12:00:16 ... 12:00:46 ... 12:01:16 QUEUEMAN Phone number changed to '011442072034000' QUEUEMAN Phone number changed to '17708881234' QUEUEMAN Phone number changed to '2221234' QUEUEMAN Phone number changed to '15418881234'

References
ZTN1732-HOWTO Configuring for local exchanges using Zetafax dialing properties Last updated: 17 April 2009 (GW/AA)

http://www.equisys.com/technotes/ztn1733.htm

11