UPDATE 2012/09/07 Ich möchte von der Verwendung von Asterisk abraten. Nutzt stattdessen lieber FreeSWITCH.

Die Sangoma B700 ist eine Hybrid Sprach- und Datenkarte die sowohl ISDN als auch analog vereint. Technische Details sind dem Datenblatt zu entnehmen. Im Vollausbau mit zwei BRI Modulen und einen FXS (oder FXO) Modul sind vier S0 ISDN Leitungen (sprich 8 Kanäle) und zwei analoge Leitungen möglich. Durch drehen des BRI Moduls kann man zwischen NT (stellt ein Amt bereit) und TE (wird ans Telefonnetz angeschlossen) Modus wechseln. Den analogen Teil kann man nicht drehen, der ist in der gewünschten Ausführung zu erwerben. Für das Auge ist die farbliche Beleuchtung der Anschlüsse. Rot symbolisiert TE und grün NT. Das sieht man sehr gut in der A500 Demo. Die B700 ist sozusagen eine Kreuzung der Produkte A500 und A200. Ferner überzeugt auch die Hardware Echounterdrückung von Octasic. Dies bringt der PC-basierten Telefonanlagen den letzten Feinschliff.

Für die Installation unter Ubuntu Hardy sind die build-essantials sowie die Kernel Header Dateien notwendig. Dies erledigt apt-get zuverlässig.

apt-get update

apt-get install build-essential linux-headers-`uname -r` udev libnewt-dev libssl-dev libncurses5-dev libcurl3-dev udev lksctp-tools libsctp-dev bison flex automake1.9 libtool

Im Sangoma wiki ist der aktuelle Treiber für die B700 zu finden. Zur Zeit ist dies der beta Treiber 3.5.2. Diese entpacken wir in /usr/src/wanpipe-X.X.X und wechseln in das Verzeichnis. Sangoma bietet ein sehr umfangreiches Setupscript, das alle denkbaren Einsatzzwecke abdeckt. Wir benötigen zaptel und bri support – das ist Option 7. Analoge Karten werden in Deutschland mit TBR21 betrieben. Eine der letzten Neuerungen in der Treibersammlung wanpipe. Los gehts mit der Ausführung von Setup:

root@ubuntu:/usr/src/wanpipe-3.5.2# bash -p Setup install
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE INSTALLATION

You are about to install WANPIPE Multi-Protocol
TDM Voice & WAN Router into your system.

This script will examine your system, then install, create
and/or modify necessary files and directories.

You must have Linux Kernel Headers along with
full development tools (i.e. GNU C compiler and utilities)
installed in order to be able to install this product.

This script will automatically compile all WANPIPE kernel
drivers and install them in their appropriate directory.

If you are installing Wanpipe for ASTERISK/ZAPTEL this
script will will prompt you for zaptel source location.

If you have previoulsy installed WANPIPE, this release
will overrite/upgrade full release without the need to
uninstall first!

IMPORTANT:
It is always recommended to say YES to all options
prompted during the install!

Please visit: http://wiki.sangoma.com for more info.

Would you like to install WANPIPE now? [y] (y/n) y
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Fixing file permissions…

Verifying files and fixing permissions …Done
Checking for C developement tools …(gcc) OK
Checking for C++ developement tools …OK
Checking for Make utility …OK
Checking for ncurses library … OK
Checking for Perl developement tools …OK
Checking for AWK …OK
Checking for FLEX …OK
Checking for Patch …OK
Checking for libtermcap-devel…OK
Checking for bison…OK

Press [Enter] to continue…
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Installing WANPIPE Device Drivers: Linux KERNEL

To integrate WANPIPE Multi-Protocol Voice & WAN Router
modules into the Linux kernel, the kernel has to be
updated with latest wanpipe sources.  Install will only
modify existing wanpipe source that is already in the
Kernel.

IMPORTANT:
It is always recommended to say YES to all options
prompted during the install!

———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Please specify absolute path name of your linux headers/source directory

Press Enter for Default: /lib/modules/2.6.24-21-generic/build

#>
Setting linux directory to /lib/modules/2.6.24-21-generic/build

Current WANPIPE kernel patch is 3.5.2

Upgrading WANPIPE kernel documentation …Done.

Upgrading WANPIPE kernel headers …Done.

Upgrading WANPIPE kernel drivers …Done.

WANPIPE device drivers upgraded successfully!

Press [Enter] to continue…
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE KERNEL DRIVER COMPILATION

The next step in WANPIPE installation involves compiling
WANPIPE kernel modules.

This script will compile and install WANPIPE modules
into the currently running linux kernel.

For greater customization you will be prompted to
select which Protocol/Drivers you would like to
build into the WANPIPE kernel modules.

Wanpipe for Asterisk/Zaptel
Default for Asterisk/Zaptel
Wanpipe for Wan Routing/API
Default for Wan/IP Routing and Data API
Wanpipe for Asterisk SMG/SS7
Default for Asterisk SS7
Wanpipe for TDM API
Default for FreeSwitch and Voice API

Custom Compilation:
——————
Customise WANPIPE driver compilation to add only the
protocols that you need.  This way one can reduce
the size of the WANPIPE kernel drivers.

Refer to http://wiki.sangoma.com for more info

———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Please Select Compilation Mode

1. WAN Protocols Support
Protocols: Frame Relay, CHDLC, PPP, ATM, X25, ADSL, TDM API
Default for: Wan Routing, Data & Voice API devel.

2. TDM Voice (Zaptel) Support
Protocols: TDMV (Zaptel), TDM API on AFT adatpers.
Default for: Asterisk & CallWeaver

3. TDM Voice (Zaptel) + WAN Protocol Support

4. SMG (SS7) (Default for Asterisk SMG/SS7 install)

5. SMG (SS7) + TDM Voice (Zaptel)
Default for: Asterisk SS7 + PRI

6. SMG (BRI) (Default for Asterisk SMG/BRI install)

7. SMG (BRI) + TDM Voice (Zaptel)
Default for: Asterisk BRI + PRI + Analog

8. TDM API
Protocols: TDM API on AFT adapters:
Default for: FreeSwitch, Yate, Sunrise
Custom voice development

9. Custom Compilation Mode
Specify protocols to be added into the WANPIPE
kernel drivers.

Please select (1,2,3,4,5,6,7,8 or 9) [Default: 1]: 7
Enabling the AFT TE1 Support

Hier ist die Weiche gestellt, wir möchten die Karte mit Asterisk verwenden und haben sowohl ISDN (BRI) und Analog (TDM Voice) in Verwendung.

Looking for zaptel/dahdi directory in /usr/src …
——————————————-
1 : /usr/src/zaptel-1.4.12.1
——————————————
——————————————
m : Enter zaptel path manually

(ctrl-c to Exit)
Please select working zaptel directory [1-1][m]: 1

Enabling the TDM Voice Asterisk Support

Zaptel HW HDLC Support Detected: Enabling DCHAN Feature
Native Zaptel HW HDLC Support Detected – No patch required
Zaptel source unmodified

Checking for UDEV Zaptel compatibility…   UDEV rules not found/or not used

Checking for SCTP Utilities….OK.

Looking for Asteris/CallWeaver directory in /usr/src …
——————————————-
1 : /usr/src/asterisk
2 : /usr/src/asterisk-1.4.21
——————————————
——————————————
m : Enter Asterisk/CallWeaver path manually

(ctrl-c to Exit)
Please select working Asterisk/CallWeaver directory [1-2][m]: 1

Checking for SMP support …Enabled.

Checking current processor type …i386

Wan Update Flags:  -DAF_WANPIPE_2612_FORCE_UPDATE -DWANPIPE_MOD_266_FORCE_UPDATE

————————————————–
CFLAGS: gcc -Wp,-MD,.wanpipe.o.d -nostdinc -iwithprefix include -D__LINUX__ -Dlinux -D__KERNEL__ -I/lib/modules/2.6.24-21-generic/build/include  -DMODULE   -DAF_WANPIPE_2612_FORCE_UPDATE -DWANPIPE_MOD_266_FORCE_UPDATE   -m32
————————————————–

Checking for REGPARM kernel option …Enabled.

Compiling General WANPIPE Driver for 2.6.X Kernel …..Done.

WAN HWEC module enabled and compiled!
Linking Wanpipe Driver and protocols …Done.

Updating Kernel Modules …Done.

Visually Confirm that driver compilation was successful! (y/n) y
Compilation Successful.
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE META CONFIGURATION

There are two configuration files associated with WANPIPE.

1) /usr/src/wanpipe-3.5.2/wanrouter.rc:
– defines locations of important files such as lock
and configuration files as well as start/stop
order of multiple WANPIPE devices.
2) /usr/src/wanpipe-3.5.2/wanpipe1.conf:
– main configuration file for each WANPIPE device.
– defines interfaces, hardware and protocol information.
– this file can be created using the ‚wancfg‘ GUI
utility or manually based on sample files located
in /etc/wanpipe/samples.

Please read the WanpipeInstallation.(pdf/txt) manual for further
information.

Press [Enter] to continue…

Wanpipe META config file found in /etc/wanpipe directory

Wanpipe startup sequence: wanpipe1 wanpipe2 wanpipe3 wanpipe4 wanpipe5

Would you like to keep the original wanpipe startup sequence? (y/n) y

Please specify a desired location for WANPIPE configuration files.

(Press Enter for Default: /etc/wanpipe)

<specify path:>

Please specify a desired location for WANPIPE interface files.

(Press Enter for Default: /etc/wanpipe/interfaces)

<specify path:>

Please specify a location for WANPIPE binary, firmware files.

(Press Enter for Default: /etc/wanpipe/firmware)

<specify path:>
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE UTILITIES SETUP

WANPIPE utilities are used to:
1) create configuration files: for Zaptel and Asterisk
/usr/sbin/wancfg_zaptel      #Zaptel and Asterisk
/usr/sbin/wancfg_dahdi      #Dahdi and Asterisk
/usr/sbin/wancfg_smg        #BRI/SS7, Zaptel and Asterisk
/usr/sbin/wancfg_tdmapi    #TDM API
2) create WANPIPE WAN/IP configuration files.
(/usr/sbin/wancfg)
3) start,stop,restart individual/all devices and interfaces.
(/usr/sbin/wanrouter)
4) debug line, protocol and driver problems.
(/usr/sbin/wanpipemon)
5) aid in WANPIPE API development
(/etc/wanpipe/api)

Refer to the WanpipeInstallation.(pdf/txt) for more information.

Press [Enter] to continue…

Compiling WANPIPE Utilities …Done.

Compiling WANPIPE WanCfg Utility …
Done.

Compiling WANPIPE Misc Utilities …Done.

Compiling WANPIPE LibSangoma API library …/usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of AM_PATH_LIBMCRYPT
run info ‚(automake)Extending aclocal‘
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
Done.

Compiling WANPIPE LibStelephony API library …/usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of AM_PATH_LIBMCRYPT
run info ‚(automake)Extending aclocal‘
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
Done.

Compiling WANPIPE API Development Utilities …Done.

Compiling WANPIPE HWEC Utilities …Done.

WANPIPE Environment Setup Complete !!!

Press [Enter] to continue…
Installing WANPIPE Files … !
Installing  WANPIPE Utilities in /usr/sbin
Installing wanrouter.rc in /etc/wanpipe
Installing wanpipe libraries in /etc/wanpipe
Installing firmware in /etc/wanpipe/firmware
Installing documentation in /usr/share/doc/wanpipe
Installing sample api code in /etc/wanpipe/api
Installing AFT Firmware update utility in /etc/wanpipe/util
Installing driver headers in /etc/wanpipe/api/include/linux
Installing Hardware Echo Cancel Utilites
Press [Enter] to continue…
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE BOOTSTRAP CONFIGURATION

Your system uses System V -style initialization scripts.  You have an option
to add router start-up script to those scripts so that the router will start
automatically when system enters multi-user mode and shut down when it enters
single-user mode or when it is halted.

i.e. By selecting this option WANPIPE will startup on system bootup and
stop on system shutdown.

Would you like to install WANPIPE start-up scripts? (y/n) y

#####################################
#                       Sangoma Wanpipe
#        Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script
#                             v2.32
#                     Sangoma Technologies Inc.
#                        Copyright(c) 2009.
#####################################

cat: /etc/inittab: No such file or directory
Warning: Failed to determine init boot level, assuming 3

Wanrouter boot scripts configuration…

Removing existing wanrouter boot scripts…OK
Verifying  boot scripts…
Enabling wanrouter init scripts …(start:8, stop:91)
Would you like to auto-execute ztcfg after wanrouter start? (y/n) y
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Checking for SCTP Utilities….OK.
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

Installing Sangoma Media Gateway Daemon…

Installing SMG Daemon…

Checking Syslog ….
found /etc/syslog.conf
Ok

Checking logrotate …
Error: Logrotate dir: /etc/logrotate.d not found !
OK.

Checking for SCTP Utilities….
OK.

Checking for SCTP modules…
OK.

Compiling LibTeletone MGD …

…
make[1]: Betrete Verzeichnis ‚/usr/src/wanpipe-3.5.2/ssmg/sangoma_mgd.trunk/lib/libteletone‘
make[2]: Betrete Verzeichnis ‚/usr/src/wanpipe-3.5.2/ssmg/sangoma_mgd.trunk/lib/libteletone‘
test -z „/usr/local/lib“ || mkdir -p — „/usr/local/lib“
/bin/sh ./libtool –mode=install /usr/bin/install -c  ‚libteletone.la‘ ‚/usr/local/lib/libteletone.la‘
/usr/bin/install -c .libs/libteletone.so.0.0.0 /usr/local/lib/libteletone.so.0.0.0
(cd /usr/local/lib && rm -f libteletone.so.0 && ln -s libteletone.so.0.0.0 libteletone.so.0)
(cd /usr/local/lib && rm -f libteletone.so && ln -s libteletone.so.0.0.0 libteletone.so)
/usr/bin/install -c .libs/libteletone.lai /usr/local/lib/libteletone.la
/usr/bin/install -c .libs/libteletone.a /usr/local/lib/libteletone.a
ranlib /usr/local/lib/libteletone.a
chmod 644 /usr/local/lib/libteletone.a
PATH=“$PATH:/sbin“ ldconfig -n /usr/local/lib
———————————————————————-
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR‘
flag during linking and do at least one of the following:
– add LIBDIR to the `LD_LIBRARY_PATH‘ environment variable
during execution
– add LIBDIR to the `LD_RUN_PATH‘ environment variable
during linking
– use the `-Wl,–rpath -Wl,LIBDIR‘ linker flag
– have your system administrator add LIBDIR to `/etc/ld.so.conf‘

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
———————————————————————-
test -z „/usr/local/include“ || mkdir -p — „/usr/local/include“
/usr/bin/install -c -m 644 ’src/libteletone.h‘ ‚/usr/local/include/libteletone.h‘
/usr/bin/install -c -m 644 ’src/libteletone_detect.h‘ ‚/usr/local/include/libteletone_detect.h‘
/usr/bin/install -c -m 644 ’src/libteletone_generate.h‘ ‚/usr/local/include/libteletone_generate.h‘
make[2]: Verlasse Verzeichnis ‚/usr/src/wanpipe-3.5.2/ssmg/sangoma_mgd.trunk/lib/libteletone‘
make[1]: Verlasse Verzeichnis ‚/usr/src/wanpipe-3.5.2/ssmg/sangoma_mgd.trunk/lib/libteletone‘
Ok.

Compiling Sangoma MGD …

[…]
BRI control scripts installed
install -D -m 755 smg_ctrl_bri /usr/sbin/smg_ctrl
sangoma_mgd Installed
Ok.
Compiling Woomera Channel …
gcc  -I/usr/include -I./ -I/usr/src/asterisk -I/usr/src/asterisk/include -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -Iinclude -I../include -D_REENTRANT  -DWOOMERA_CHAN_NAME=\“WOOMERA\“ -D_GNU_SOURCE  -DWOO_CONTROL_SRC_FEATURE  -O6 -fomit-frame-pointer  -fPIC  -DAST14 -DAST_MODULE=\“chan_woomera\“ -c chan_woomera.c -o chan_woomera.o
gcc -shared -Xlinker -x -o chan_woomera.so chan_woomera.o
install -D -m 755 chan_woomera.so /usr/lib/asterisk/modules/chan_woomera.so
chan_woomera Installed
Ok.
———————————

SMG Install Done

–> Config: /etc/sangoma_mgd.conf
–> Start:  sangoma_mgd -bg

Chan Woomera Install Done

–> Config: /etc/asterisk/woomera.conf
–> Start: start asterisk (part of asterisk)

———————————

Installing SMG BRI Daemon…

—————————————-
Sangoma BRI Installation Complete

-> To configure for BRI run:
-> /usr/bin/wancfg_smg

—————————————-

Append sample config in Asterisk Extensions and Iax Conf (y/n) y
Asterisk extensions.conf file updated with woomera config
Asterisk iax.conf file updated with bri guest config
Press [Enter] to continue…
———————————————————-
WANPIPE v3.5.2 Installation Script
Copyright (c) 1995-2009, Sangoma Technologies Inc.
———————————————————-

WANPIPE INSTALLATON: COMPLETE

WANPIPE installation is now complete. WANPIPE kernel drivers
and configuration/debug utilities have been compiled and installed.

1) Proceed to configure the WANPIPE drivers:
Asterisk/Zaptel:    /usr/sbin/wancfg_zaptel
Asterisk/Dahdi :   /usr/sbin/wancfg_dahdi
TDM API        :    /usr/sbin/wancfg_tdmapi
SMG SS7/BRI    : /usr/sbin/wancfg_smg
WAN Routing/API: /usr/sbin/wancfg
2) Use the /usr/sbin/wanrouter startup script to start and stop
the router. (eg: wanrouter start)
3) To uninstall WANPIPE package run ./Setup remove

Please read http://wiki.sangoma.com for further instructions.

Wanpipe / Zaptel/Dahdi & SMG BRI Configuration
========================================

wancfg_smg configurator can create all wanpipe config files
for ZAPTEL as well as for SMG BRI.
—————————————————–
Would you like to configure wanpipe devices for ZAPTEL/DAHDI & BRI? (y/n) y
error: permission denied on key ‚kernel.sched_nr_migrate‘
error: permission denied on key ’net.ipv4.route.flush‘
error: permission denied on key ’net.ipv6.route.flush‘
error: permission denied on key ‚dev.parport.parport0.autoprobe‘
error: permission denied on key ‚dev.parport.parport0.autoprobe0‘
error: permission denied on key ‚dev.parport.parport0.autoprobe1‘
error: permission denied on key ‚dev.parport.parport0.autoprobe2‘
error: permission denied on key ‚dev.parport.parport0.autoprobe3‘

#################################
#                       Sangoma Wanpipe
#        Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script
#                             v2.32
#                     Sangoma Technologies Inc.
#                        Copyright(c) 2009.
#################################

Generating configuration files for Sangoma Media Gateway
Checking for native zaptel hardhdlc support…Yes

———————————————
Configuring T1/E1 cards [A101/A102/A104/A108]
———————————————
————————————
Configuring ISDN BRI cards [A500/B700]
————————————

———————————————————–
A700 detected on slot:0 bus:4
———————————————————–

Would you like to configure AFT-B700 port 1 on slot:0 bus:4
1. YES
2. NO
3. Exit
[1-3]:1

Would you like to enable hardware DTMF detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Would you like to enable hardware fax detection?
1. YES
2. NO
[1-2, ENTER=’NO‘]:1

Configuring port 1 on AFT-B700 [slot:0 bus:4 span:1]

Select connection type for port 1
1. Point to multipoint
2. Point to point
[1-2, ENTER=’Point to multipoint‘]:1

Wir konfigurieren einen normalen Mehrgeräteanschluss (point to multipoint). Ein Anlagenanschluss erfordert die Punkt zu Punkt Signalisierung (point to point).

Input the group for this port
: 1

Select dialplan context for group:1
1. from-pstn
2. Custom
[1-2]:1

Configuring span:1 as TEI:127
1. YES – Keep this setting
2. NO  – Specify a different TEI
[1-2, ENTER=’YES‘]:1

———————————————————–
A700 detected on slot:0 bus:4
———————————————————–

Would you like to configure AFT-B700 port 2 on slot:0 bus:4
1. YES
2. NO
3. Exit
[1-3, ENTER=’YES‘]:1

Would you like to enable hardware DTMF detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Would you like to enable hardware fax detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Configuring port 2 on AFT-B700 [slot:0 bus:4 span:2]

Select connection type for port 2
1. Point to multipoint
2. Point to point
[1-2, ENTER=’Point to multipoint‘]:1

Input the group for this port
def=“1″:

Configuring span:2 as TEI:127
1. YES – Keep this setting
2. NO  – Specify a different TEI
[1-2, ENTER=’YES‘]:1

———————————————————–
A700 detected on slot:0 bus:4
———————————————————–

Would you like to configure AFT-B700 port 3 on slot:0 bus:4
1. YES
2. NO
3. Exit
[1-3, ENTER=’YES‘]:1

Would you like to enable hardware DTMF detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Would you like to enable hardware fax detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Configuring port 3 on AFT-B700 [slot:0 bus:4 span:3]

Select connection type for port 3
1. Point to multipoint
2. Point to point
[1-2, ENTER=’Point to multipoint‘]:1

Input the group for this port
def=“1″: 2

Select dialplan context for group:2
1. from-internal
2. Custom
[1-2, ENTER=’from-pstn‘]:1

———————————————————–
A700 detected on slot:0 bus:4
———————————————————–

Would you like to configure AFT-B700 port 4 on slot:0 bus:4
1. YES
2. NO
3. Exit
[1-3, ENTER=’YES‘]:1

Would you like to enable hardware DTMF detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Would you like to enable hardware fax detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Configuring port 4 on AFT-B700 [slot:0 bus:4 span:4]

Select connection type for port 4
1. Point to multipoint
2. Point to point
[1-2, ENTER=’Point to multipoint‘]:1

Input the group for this port
def=“2″:

ISBN BRI card configuration complete

Press any key to continue:
————————————
Configuring analog cards [A200/A400/B600/B700]
————————————

———————————————————–
A700 detected on slot:0 bus:4
———————————————————–

Would you like to configure AFT-B700 on slot:0 bus:4
1. YES
2. NO
[1-2]:1

Would you like to enable hardware DTMF detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Would you like to enable hardware fax detection?
1. YES
2. NO
[1-2, ENTER=’YES‘]:1

Which Operation Mode will be used?
1. FCC
2. TBR21
3. AUSTRALIA
[1-3, ENTER=’FCC‘]:2

Press any key to continue:
AFT-B700 configured on slot:0 bus:4 span:1

Analog card configuration complete

Press any key to continue:
————————————
Configuring USB devices [U100]
————————————

###############################
#                             SUMMARY
###############################

0 T1/E1 port(s) detected, 0 configured
4 ISDN BRI port(s) detected, 4 configured
1 analog card(s) detected, 1 configured
0 usb device(s) detected, 0 configured

Configurator will create the following files:
1. Wanpipe config files in /etc/wanpipe
2. sangoma_brid config file /etc/wanpipe/smg_bri
3. Zaptel config file /etc/zaptel.conf
4. Zapata config file /etc/asterisk/zapata.conf

Your original configuration files will be saved to:
1. /etc/zaptel.conf.bak
2. /etc/asterisk/zapata.conf.bak

Your configuration has been saved in /etc/wanpipe/debug-2009-05-24.tgz.
When requesting support, email this file to techdesk@sangoma.com

###############################

Configuration Complete! Please select following:
1. YES – Continue
2. NO – Exit
[1-2]:1

Zaptel and Wanpipe configuration complete: choose action
1. Save cfg: Restart Asterisk & Wanpipe now
2. Save cfg: Restart Asterisk & Wanpipe when convenient
3. Save cfg: Stop Asterisk & Wanpipe now
4. Save cfg: Stop Asterisk & Wanpipe when convenient
5. Save cfg: Save cfg only
6. Do not save cfg: Exit
[1-6]:5

Removing old configuration files…

Copying new Wanpipe configuration files…

Copying new sangoma_brid configuration files (/etc/wanpipe/smg_bri.conf)…

Copying new Zaptel configuration file (/etc/zaptel.conf)…

Copying new Zapata configuration files (/etc/asterisk/zapata.conf)…
Saving files only
cat: /etc/inittab: No such file or directory
Warning: Failed to determine init boot level, assuming 3

Wanrouter boot scripts configuration…

Removing existing wanrouter boot scripts…OK
Would you like wanrouter to start on system boot?
1. YES
2. NO
[1-2]:1

Verifying Zaptel boot scripts…
Verifying Zaptel boot scripts…Enabled (level:15)
Verifying Zaptel shutdown scripts…Enabled (level:30)
Enabling wanrouter init scripts …(start:14, stop:29)
Remvoing old smg_ctrl boot…..OK
Remvoing old smg_ctrl_safe boot…..OK
Would you like smg_ctrl to start on system boot?
1. YES
2. NO
[1-2]:1

Verifying Network boot scripts…Enabled (level:40)
Enabling smg_ctrl start scripts…(level:41)
Enabling smg_ctrl boot scripts …(level:41)
root@ubuntu:/usr/src/wanpipe-3.5.2#
root@ubuntu:/etc/wanpipe# /etc/init.d/wanrouter start

Wir starten jetzt wanrouter – dieser läd alle notwendigen Kernelmodule und Firmware für die Hardwareechounterdrückung. Der ISDN Teil besteht aus dem sangoma_mgd und dem sangoma_bgd.

Starting up device: wanpipe1
–> Loading ec image OCT6116-64S.ima…
Starting up device: wanpipe2
Starting up device: wanpipe3
Starting up device: wanpipe4
Starting up device: wanpipe5
Configuring interfaces: w1g1
done.
Configuring interfaces: w2g1
done.
Configuring interfaces: w3g1
done.
Configuring interfaces: w4g1
done.
Configuring interfaces: w5g1
done.

Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
======================

Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)

2 channels to configure.

Changing signalling on channel 1 from Unused to FXS Kewlstart
Changing signalling on channel 2 from Unused to FXS Kewlstart

Um zeitkritische Dinge sofort und CPU schonend zu erledigen, besitzt die Karte einen FPGA Chip. wanrouter hwprobe verbose zeigt die Version der Firmware.root@ubuntu:/etc/wanpipe# wanrouter hwprobe verbose

—————————————–
| Wanpipe Hardware Probe Info (verbose) |
—————————————–
1 . AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=9 : PORT=1 : HWEC=16 : V=34
+01:TE: PCI: NONE: C01
2 . AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=9 : PORT=2 : HWEC=16 : V=34
+02:TE: PCI: NONE: C01
3 . AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=9 : PORT=3 : HWEC=16 : V=34
+03:NT: PCI: NONE: C01
4 . AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=9 : PORT=4 : HWEC=16 : V=34
+04:NT: PCI: NONE: C01
5 . AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=9 : PORT=5 : HWEC=16 : V=34
+01:FXO: PCI: NONE
+02:FXO: PCI: NONE

Card Cnt: B700=1

root@ubuntu:/etc/wanpipe# /etc/init.d/wanrouter stop

Stopping running processes…
safe_sangoma not running…
sangoma_brid is stopped
sangoma_mgd not running…
Removing PID files…done
Shutting down wanpipe5 interface: w5g1
Shutting down wanpipe4 interface: w4g1
Shutting down wanpipe3 interface: w3g1
Shutting down wanpipe2 interface: w2g1
Shutting down wanpipe1 interface: w1g1
Shutting down device: wanpipe5
Shutting down device: wanpipe4
Shutting down device: wanpipe3
Shutting down device: wanpipe2
Shutting down device: wanpipe1
No devices running, Unloading Modules

Das Updaten der FPGA Firmwae ist nicht zwingend notwendig. Asterisk und wanrouter müssen gestoppt werden, die Kernelmodule entladen sein.

root@ubuntu:/etc/wanpipe# wanrouter modules

root@ubuntu:/etc/wanpipe# cd util/wan_aftup/
root@ubuntu:/etc/wanpipe/util/wan_aftup# ./update_aft_firm.sh
modprobe wan_aften  > /dev/null
AFT card enabled

Sangoma AFT Series card update flash software (version 1.9)

Sangoma AFT card list:
w1g1: AFT-B700-SH : SLOT=0 : BUS=4 : IRQ=21 : PORT=1 : HWEC=16 : V=34 (Ver.34)

Please select card interface [def=w1g1; q=exit] > w1g1

List of available versions:
Version no. 35 (filename=B700_0040_V35.BIN)
Version no. 34 (filename=B700_0040_V34.BIN)
Please specify version number [def=35; q=exit] > 35

w1g1: Current Sangoma Flash: Revision=34 ID=0x205B
Erasing sectors                57%
94%     Verification                98%

Verification                Passed
w1g1: Sangoma Flash update            DONE

w1g1: Reloading Sangoma flash        DONE
w1g1: Sangoma Flash updated successfully

modprobe -r wan_aften
AFT card disabled