If in the illustration it shows channel 1 is your Zap extension

then add a zap extension for channel 1 in AMP and if it shows your Zap trunk is channel 2 you should create a zap trunk for channel 2 in AMP.

Once this is done, reboot your PC and when Asterisk starts, use AMP to add a route for incoming calls or asterisk will not answer your trunk. Similarly, to make outbound calls you will need an outbound route. Set them up as per setting up routes in the earlier chapters of this document.

If you have this card installed, you will need to edit the

following files; zapata.conf and zaptel.conf as per the X100P card in the previous section.

9.2.2 modules.conf (modprobe.conf for AAH 2.x)

You will need to edit the modules.conf, or modprobe.conf to add the necessary option for usage in Australia.

The example below is for AAH 1.x. where you need to add the following line;

options wctdm opermode=AUSTRALIA fxshonormode=1 bootstringer=1

Your modules.conf (AAH 1.x) should look like the example below:

alias eth0 e100

alias sound-slot-0 es1370

post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :

pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

alias usb-controller usb-uhci

alias char-major-196 torisa

options wctdm opermode=AUSTRALIA fxshonormode=1 boostringer=1

options torisa base=0xd0000

post-install tor2 /sbin/ztcfg

post-install torisa /sbin/ztcfg

post-install wcusb /sbin/ztcfg

post-install wcfxo /sbin/ztcfg

post-install wctdm /sbin/ztcfg

post-install ztdynamic /sbin/ztcfg

You will only need to add the line in red. Do not change anything else.

Or, in AAH Ver.2.1, you may also do the following:

Locate the line 'install wctdm /sbin/ztcfg-- --ignore-install wctdm && /sbin/ztcfg' and edit it to reflect the following:

install wctdm opermode=AUSTRALIA fxshonormode=1 boostringer=1 /sbin/ztcfg-- --ignore-install wctdm && /sbin/ztcfg

Note: as of Zaptel

Drivers 1.2.4, by selecting opermode=AUSTRALIA the zaptel drivers automatically add the 'boostringer=1 , fxshonormode=1'

Also see Appendix E.3 (Users Suggestions)

9.3 REBUILDING ZAPTEL DRIVER

Every time there is a kernel update with yum (which is the case

with Asterisk and CentOS), ZAP device support needs to be rebuilt using the new kernel. Unfortunately, this will cause a slight problem as RedHat bug caused the rebuilding process to fail.

The following is the fix - source Nerd Vittles http://nerdvittles.com/index.php?p=123

Log into your new server as root and issue the following commands:

cd /usr/src/kernels/2.6.9-34.EL-i686/ include/linux

mv spinlock.h spinlock.h.old

wget http://nerdvittles.com/aah27/spinlock.h

Once the file has been retrieved, reboot using the following command:

shutdown -r now

When the reboot completes, you can start rebuilding the support for your ZAP devices or for that matter, ztdummy if you don’t have any ZAP devices.

Log in as root and type the following command:

rebuild_zaptel

Then reboot your system:

shutdown -r now

Now log in as root again and enter the following command:

amportal stop

genzaptelconf

Reboot once again:

shutdown -r now

..and you're done.

(See also user Users’ Suggestions)

9.4 SIPURA SPA3000 AS A PSTN INTERFACE

To those new to the SPA3000, there is a simplified installation and configuration instruction by JMG Technology. While it is directed mainly at standalone ATA users, it gives a good insight of the Sipura SPA3000’s capabilities.

I have come across a few people in the various forums wanting to use their Sipura SPA-3000s as FXO front-end to their Asterisk@Home boxes. To help them in their endeavours, I've put the following together, as no one single source of information that I've found so far has a config that would actually work for me.

9.4.1 Log in to SPA3000

Login to your SPA-3000 as admin/advanced.