Asterisk FAQ

1. How do I install wanpipe-driver on trixbox ?
2. How do I enable hardware DTMF support for Asterisk with my "d" model card ?
3. Why does Zaptel  not compile on some Redhat, CentOS and trixbox systems?
4. How do I auto-start Zaptel after wanrouter start ( Wanpipe start up script ) ?
5. Does the card have PMC or Dallas/Maxim framer?
6. Which PRI dial plan configuration works with Batelco Jordan with Siemens ESW switch type?
7. I have an E1/PRI line, incoming calls are working but outgoing calls are not working what is wrong ?
8. I am using Ubuntu and am getting the following error when I try to use ./Setup install " ./Setup: 1041: Syntax error: Bad substitution"
9. How do I debug  DTMF recognition issue ?
10. How do I debug incoming and/or outgoing call issue on T1/E1 - PRI line ?
11. How do I check if the card has on board hardware echo cancellation and it's running?
12. How do I perform physical layer (connection) debugging on AFT series cards ?
    
13. How do I debug echo issue with software echo cancellation ?
14. How do I configure my T1/E1 card for fractional voice and data (in mix mode) ?
15. What is proper timing configuration on Sangoma card when I am configuring my A102/A104/A108 with Telco, Channel Bank or/and traditional PBX ?
16. How do I configure my "d" model card to enable hardware DTMF ?
17. Why do my FXS modules show up as FXO in Zaptel or FXO modules show up as FXS in Zaptel?
18. How do I configure single port on  AFT series T1/E1 card in mixed Voice and data mode ( configuring single port for fractional voice and data ) ?
19. What does "HARDHDLC" in zaptel.conf mean or why can't I make calls after upgrading to Zaptel-1.4.X and Wanpipe-3.2.X and re-using my old configs?
20. How do I configure my Sangoma Hardware for a J1 line?
21. How to determine what port and channel number a call is using on an A500?
    
22. How to have Asterisk stop when the Wanrouter stop script is run?

Telecommunication FAQ

1. What is the difference between T1 and E1?
2. What are the red, blue, and yellow alarms in a T1 system?
3. What are the alarm indication signal (AIS), remote alarm indication (RAI), and distant multiframe alarm (DMA) in an E1 system?
4. What are the differences between robbed-bit signaling (RBS), channel-associated signaling (CAS), and common-channel signaling (CCS)? 
5. What is the difference between AMI, B8ZS, and HDB3?

Q. Why does Zaptel not compile on some RedHat, CentOs and Trixbox Systems? 

A. If you are getting these errors when compiling zaptel:

/usr/src/zaptel/zaptel.c:384: error: syntax error before "zone_lock"
/usr/src/zaptel/zaptel.c:384: warning: type defaults to `int' in declaration of `zone_lock'
/usr/src/zaptel/zaptel.c:384: error: incompatible types in initialization
/usr/src/zaptel/zaptel.c:384: error: initializer element is not constant

:
:

There is a typo in your kernel headers.
View a file called spinlock.h in your kernel source directory:

#>vi /lib/modules/$(uname -r)/build/include/linux/spinlock.h
look for this line:

#define DEFINE_RWLOCK(x) rw_lock_t x = RW__LOCK_UNLOCK

(it is around line 407)
and change it to:

#define DEFINE_RWLOCK(x) rwlock_t x = RW__LOCK_UNLOCK

then try to recompile Zaptel again.

From julian - 2/22/07 5:27 PM [Delete]

Ubuntu server 2.6.17-10

 I'm having problems running Setup.  It gives a syntax error :

./Setup: 1014: Syntax error: Bad substitution

 any ideas?

 FIX!!

 I needed to change the first line of the setup script to  #!/bin/bash and it worked. 

A.     You can configure a port for either T1 or E1.

Do wanrouterstart and check your system log (/var/log/messages) right after wanrouterstart.
If the card has PMC framer you will see following on the system log:

wanpipe1: Global EC Clock Port = 1

wanpipe1: AFT Data Mux Bit Map: 0x01234567

wanpipe1: Configuring PMC COMET-QUAD T1 FE

If the card has Maxim/Dallas Framer, you will see followingin the system log:

wanpipe1: Global EC Clock Port = 1

wanpipe1: Global E1 Front End configuration

wanpipe1: AFT Data Mux Bit Map: 0x01234567

wanpipe1: Configuring DSDS26521 E1 FE

You can also visit our hardware-matrix

Q. Which PRI dialplan configuration work with Batelco Jordan with Siemens ESW switch type?

    Following configuration works with Batelco Jordan
    pridialplan=unknown
    switchtype=euroisdn
   

 Q. I have an E1/PRI line, incoming calls are working but outgoing calls are not working, what is wrong?

Most E1 lines require LibPRI/Asterisk to specify the type of number dialed.  In Zapata.conf try playing around with the following value (remember to add this option before the channels are defined):
pridialplan= local                    (this value can also be unknown, private, national, and international)

Q. I am using Ubuntu and am getting the following error when I try to use ./Setup install; "./Setup: 1014: Syntax error: Bad substitution"?

Ubuntu uses the Dash shell environment rather then a Bash style environment and the scripts need to be aware of this.  Open up the "Setup" script and change the first line from "#!/bin/sh" to "#!/bin/bash".  This will tell ubuntu to use the Bash shell rather then the default shell.

Q. Why do my FXS modules show up as FXO in Zaptel or FXO modules show up as FXS in Zaptel?

An FXS module is used to connect a telephone/fax/modem/CPE device to a computer so it needs to emulate the signaling used by a telco; this signaling is called FXO (kewl start or loop start).  While an FXO module is the exact opposite, it is used to connect a computer to a telco line so it needs to emulate the signaling of a normal phone; this signaling is called FXS (kewl stat or loop start).  So it is perfectly normal and actually correct that the signaling used by Zaptel is always the opposite of what the module is called.  If you are still worried that you have purchased or received the wrong module you can check exactly what type of module you have by running the "wanrouter hwprobe verbose" command from the Wanpipe drivers which displays all the Sangoma cards installed and the location of any FXO or FXS modules.  If there are any problems contact techdesk@sangoma.com with a brief description of the problem.

 Q. What does "HARDHDLC" in zaptel.conf mean or why can't I make callsafter upgrading to Zaptel-1.4.X and Wanpipe-3.2.X and re-using my oldconfigs?

As of Zaptel-1.4.X Digium has integrated the option for hardware HDLC framing into Zaptel so that it no longer needs to be patched.  As of Wanpipe-3.2.2 the driver install program will no longer patch Zaptel with our hardware HDLC patch, instead the configuration scripts "wancfg_zaptel" and "setup-sangoma" will now create zaptel.conf with the D-channel specified using "hardhdlc".  When zaptel.conf is parsed by Zaptel and it sees "hardhdlc=" Zaptel will NOT do HDLC framing on the D-channel stream, on the other hand if it sees "dhcan=" Zaptel will perform HDLC framing on the D-channel specified.

If you have recently upgraded your version of Wanpipe to Wanpipe-3.2.2 or newer then you need to run "wancfg_zaptel" or "setup-sangoma" after the driver install to create updated configuration files.   If you are feeling brave then feel free to simply change your zaptel.conf file manually:

1. Open the file /etc/zaptel.conf with your favourite  text editor.
2. Look for the line "dchan=24" or "dchan=16" and change it to "hardhdlc=24" or "hardhdlc=16".
3. Save the file, exit the text editor, and run "ztcfg -vvv" to apply the new configuration.

NOTE: If you are having problems making a call on a PRI line and you have both incoming and outgoing frames when you run the command "pri intense debug span X" in Asterisk then check the D-channel using Wanpipe: "wanpipemon -i wXg1 -c trd" (where X is the port number of the Sangoma card). If you only see incoming frames then both the hardware and Zaptel are doing HDLC framing on the D-channel, disable software HDLC framing by following the instructions above.

For Wanpipe-3.3.6 or newer:

Asterisk will display the following output for the show channels command:

 asterisk*CLI> show channels
Channel                             Location                      State   Application(Data)
WOOMERA/g2/5-88c1       200@from-internal:2   Up      Playback(demo-congrats)
WOOMERA/g1/1                100@misc:2                Up      Echo()
2 active channels
2 active calls

As you can see the woomera channel being used is specified by the following string "woomera/g1/1-XXXXXX".  The number after the "/" and before the "-" is the combined channel number the call is going through.  This number maps to the span number and channel using the following map:

span 1 channel 1 = 1
span 1 channel 2 = 2
span 2 channel 1 = 3
span 2 channel 2 = 4
span 3 channel 1 = 5

Now the span number in most cases is also the wanpipe number but if you want to be 100% sure or you are running any other Sangoma cards you will need to confirm which span belongs to which wanpipe.  In the /etc/wanpipe/wanpipeX.conf file you will find a value "TDMV_SPAN=Y" which is the span number attached to this wanpipe. 

....
IGNORE_FRONT_END = NO
TDMV_SPAN       = 1

[w1g1]
ACTIVE_CH       = ALL
....

EXAMPLE: If wanpipe2.conf has a TDMV_SPAN=3 then the Asterisk channels the calls would go across are "woomera/g1/5" and "woomera/g1/6".

For Wanpipe-3.3.5 or older:

Coming Soon 

 How to have Asterisk stop when the Wanrouter stop script is run?

A relative unknown feature of the Wanpipe drivers is the pre-"wanrouter stop" stop script.  This is a file that can modified to run as a shell script (intelligent loops with variables) or to simply run Linux command prompt commands.  By default the file does not exist, there's nothing we need to stop with it but all you need to do to activate it is to create the file.

1. Change directory to /etc/wanpipe/scripts using "cd /etc/wanpipe/scripts/".
2. Create the file using the "touch" command, i.e.  "touch stop".
3. Open the file using you favourite text editor and add anything you want the driver to do before it shuts itself down.

Now a common problem with some installs (PBX in a FLASH) does not by default have an Asterisk stop script to be run on reboot/shutdown.  This is a problem because it can cause Zaptel to panic when the Wanpipe drivers don't shutdown because they are in use (a safety feature).  Use the "stop" script to easily force an Asterisk shutdown before the Wanpipe drivers stop.

1. Run "vim /etc/wanpipe/scripts/stop" to open up the "stop" script for editing.
2. Hit the "INSERT" key on your keyboard to put Vim into "insert" mode.
3. Add the following command to safely stop Asterisk "asterisk -rx 'stop now' ".
4. Hit the "ESC" key on keyboard to exit "insert" mode.
5. Save and exit Vim by hitting ":wq".

Do a test shutdown when you can control the system in case you still have a problem, if you continue to have problems please contact Sangoma support at "techdesk@sangoma.com"