Wanpipe Asterisk Configuratrion Legacy

Documentation below is still valid, however in should not be used.
The default wanec_zaptel script should work for 100% of Asterisk installs!
If you are having trouble with it please contact Sangoma Support

1. Miscelaneous Wanpipe Config Documentation
2. A104D Mixed HW Echo Cancelled Voice & Wan Data Configuration
3. Configuring Zaptel and Asterisk Zap Channels
4. Why is wanpipe1.conf needed along with zaptel.conf
   
   Old Wanpipe Config Documentation 
5. AFT A104 Wanpipe Config for Asterisk 
6. AFT A101/2/3/4/8D HWEC Wanpipe Config for Asterisk 
7. AFT A200 Analog HWEC Wanpipe Config for Asterisk
8. Wanpipe Config for Mixed Data and Voice over the same span/port

         AFT a102/4/8 Setup with Telco, Channel Bank and PBX
     9. Setuping up AFT a102/4/8 with Telco, Channel Bank and PBX + Clock Synchronization

AFT A104 Wanpipe Configuration

Use his configuration method only if you are an advaced/power user.
Otherwise, use the above automatic method for configuring wanpipe for Asterisk.

Run wanpipe configuration utility:

/usr/sbin/wancfg (Linux)

/usr/local/sbin/wancfg (FreeBSD) 

Hardware Setup (AFT):

Select Hardware: Specify which AFT card installed from hardware probe.

    After probing the hardware, wancfg screen should show  you:
    (in this example, an A104 card)
    ----------------------------
    Card Type-------> A104    
    Physical Medium-> T1    
    ----------------------------

Sepecify Line Type:  T1 or E1
                                 Default is T1 

Default configuration is complete: Select <BACK>

Protocol Setup:

Select Protocol: TDM VOICE

Configuration is complete: Select <BACK>

Interface Setup:

Skip First two options and leave them default.

Select: SPAN Number: 1 - Unlimited
            The SPAN usually starts with 1
            This option binds HW Port to a particular SPAN.

Select: Override Asterisk Echo Enable  (AFT101/2/3/4/4d)
            Default: NO

  Setting this option to YES will DISABLE echo cancellation
  for this particular span.
  ie: ignore what is configured in zapata.conf,
       then set this option to YES.

  This is mainly used in switching applications where one SPAN needs echo
  cancellation and others do not.  

Select: DCHAN PRI Timeslot:     (AFT101/2/3/4/4d)

Hardware HDLC support for DCHAN PRI

Options: 
0     : Disable Hardware HDLC on PRI timeslot.
24   : T1 Line DCHAN is usually on timeslot 24
         Enable Hardware HDLC on PRI timeslot. Default 24
16   : E1 Line DHCAN is usually on timeslot 16
         Enable Hardware HDLC on PRI timeslot. Default

Note: TDMV_DCHAN values are ALWAYS  [0 | 24 | 16]
(Don't confuse this with the Asterisk configuration that uses values greater than 24/31 for the DCHAN specification).

Configuration is complete: Select <BACK> to Save and Exit

echocancel=yes
echocancelwhenbridged=yes

Run wanpipe configuration utility: /usr/sbin/wancfg

Hardware Setup (AFT):

Select Hardware: Specify which AFT card is installed from hardware probe.

    After hardware probe,  wancfg screen should show  you:
    (in this example, an A104D card)
    ----------------------------
    Card Type-------> A104    
    Physical Medium-> T1    
    ----------------------------

Sepecify Line Type:  T1 or E1
                                 Default is T1 

Default configuration is complete: Select <BACK>

Protocol Setup:

Select Protocol: TDM VOICE

Configuration is complete: Select <BACK>

Interface Setup:

Skip the first two options and leave them on the default selection.

Select: SPAN Number: 1 - Unlimited
            The SPAN usually starts with 1
            This option binds HW Port to a particular SPAN.

Select: Override Asterisk Echo Enable  (AFT101/2/3/4/4d)
            Default: NO

  Setting this option to YES will DISABLE SOFTWARE echo cancellation
  for this particular span.
  ie: ignore what is configured in zapata.conf,
       then set this option to YES.

  This is often used in switching applications where one SPAN needs echo
  cancellation and others do not.  

Select: DCHAN PRI Timeslot:     (AFT101/2/3/4/4d)

Hardware HDLC support for DCHAN PRI

Options: 
0     : Disable Hardware HDLC on PRI timeslot.
24   : T1 Line DCHAN is usually on timeslot 24
         Enable Hardware HDLC on PRI timeslot. Default 24
16   : E1 Line DHCAN is usually on timeslot 16
         Enable Hardware HDLC on PRI timeslot. Default

Note: TDMV_DCHAN values are ALWAYS  [0 | 24 | 16]
(Don't confuse this with the Asterisk configuration that uses values greater than 24/31 for the DCHAN specification).

Select: Hardware Echo Cancellation (For A104D and A200 cards only)

Options: 
YES: Enables Hardware Echo Cancellation
NO : Disables Hardware Echo Cancellation

Hardware Echo Device: UDEV Configuration

From the wanpipe-beta3 release and forward, the HW Echo Cancelation interface is a device located in the /dev/ directory.  There is one device per analog port on each card.  "/dev/wanec"

AFT A200-Analog with HW Echo Canceler Configuration

Run wanpipe configuration utility:

#>usr/sbin/wancfg

Note: If we do not specifically mention an option, please leave it on the default selection.
Why is wanpipe1.conf needed along with zaptel.conf?

Hardware Setup (A200 Analog)

Select Hardware: Specify AFT 200 Analog card from hardware probe.

After hardware probe,  wancfg screen should show  you:
    (in the example of an A200 card)
    ----------------------------
    Card Type-------> A200-Analog    
    TDMV LAW -------> MuLaw    
    ----------------------------
Specify Line Encoding:  MuLaw or ALaw
                                      Default is MuLaw
MuLaw is normally used in North America and Japan, ALaw is normally used outside North America and Japan. If you are in doubt, check with your Telco.

Default configuration is complete: Select <BACK>

Protocol Setup:

Select Protocol: TDM VOICE

Configuration is complete: Select <BACK>

Interface Setup:

Select: SPAN Number: 1 - Unlimited
            The SPAN usually starts with 1
            This option binds HW Port to a particular SPAN.

Select: Hardware Echo Cancellation (if supported by A200 card)

Options: 
YES: Enables Hardware Echo Cancellation
NO : Disables Hardware Echo Cancellation

Note: Make sure that echocancel=yes, echocancelwhenbridged=yes option is set in zapata.conf

Configuration is complete: Select <BACK> to Save and Exit

Hardware Echo Device: UDEV Configuration

From the wanpipe-beta3 release and forward, the Hardware Echo Cancellation interface is a device located in the /dev/ directory.  There is one device per analog card.

/dev/wp1ec   ->  Card 1
/dev/wp2ec   ->  Card 2
    ...
System with Linux 2.6 kernels and UDEV
If you are running on the Linux 2.6 kernel and a system with UDEV, these devices will be created automatically by UDEV during wanrouter start.

Systems with Linux 2.4 kernels or 2.6 kernels without UDEV
If you are running on a Linux 2.4 kernel or 2.6 kernel and a system without UDEV, the ./Setup installation script should have created 32 /dev/wpXec devices for you. 

If you don't see any /dev/wpXec devices after the wanrouter start command, they must be created manually by using the following command:

#>mknod /dev/wp1ec c 242 1
#>mknod /dev/wp2ec c 242 2
etc. (for each analog card configured)

The Wanpipe TDM driver enables HW Echo Cancellation only on channels that have active calls: It waits for zaptel to enable echo cancellation after the call has been established. Therefore, Echo Cancellation option MUST be enabled in /etc/asterisk/zapata.conf.

echocancel=yes   
echocancelwhenbridged=yes

Top

Select Hardware: Specify AFT card from hardware probe.

    After hardware probe, wancfg screen should show  you:
    (in this example, an A104 card)
    ----------------------------
    Card Type-------> A104    
    Physical Medium-> T1    
    ----------------------------

Specify Line Type:  T1 or E1
                                Default is T1

Select Advanced Timeslot Groups Configuration

Set the number of Timeslot Groups to 2 or more.
Specify the number of channels for each timeslot groups.
Your screen should look like this:
--------------------------------------------------
Number of Timeslot Groups ----->2
Timeslot Group 1 configuration -> 1-12
Timeslot Group 2 configuration -> 13-24
---------------------------------------------------

Timeslot Groups configuration is complete: Select <BACK>
Default configuration is complete: Select <BACK>

Protocol and Interface Setup:
          Configuration for each individual timeslot is the same as standard wanpipe configuration.

A group of channels (1 to 10) can run in TDM Voice mode (ZAPTEL) mode and another group of channels (11 to 24) can run WAN (Frame Relay) protocol all over a SINGLE T1/E1 line.

Therefore, TDM Voice mode is just one of the WANPIPE supported modes of operation.
For this reason, wanpipe1.conf is need to configure a WANPIPE TDM Voice driver to load the correct card and attach the hardware T1/E1 port to correct ZAPTEL SPAN.

There is an added benefit to this configuration.  User can specify exactly which T1/E1 PORT is bound to which ZAPTEL SPAN.  On a single PORT/SPAN system this might not be a big deal, however on systems with 16+ PORTs/SPANs, it can prove difficult to figure out which SPAN belongs to which port if PORTs/SPANs are autoconfigured.  With Wanpipe drivers

Port 1 <------> Telco (TE_CLOCK = NORMAL in /etc/wanpipe/wanpipe1.conf)
Port 2 <------> Channel Bank / PBX (TE_CLOCK = MASTER, TE_REF_CLOCK = 1in /etc/wanpipe/wanpipe2.conf)

Note: Please make sure that Telco is alwasy connected with Port 1 (if you have more than one Telco line than use Port 2 and so on to connect with Telco ). Make sure that channel bank / PBX are configured as slave.