diff --git a/ChangeLog.beta b/ChangeLog.beta index 0fce0db..a780572 100644 --- a/ChangeLog.beta +++ b/ChangeLog.beta @@ -1,24 +1,45 @@ ------------------------------------------------------------------------------ WANPIPE TDM VOICE - IP/WAN Package - -Linux Voice TDM/WAN Router Package -For more info visit: http://wiki.sangoma.com ------------------------------------------------------------------------------ Author: Nenad Corbic Copyright (c) 1995-2008 Sangoma Technologies Inc. ------------------------------------------------------------------------------ -* Wed Jul 14 2008 Nenad Corbic - Beta - 3.3.11 +For more info visit: http://wiki.sangoma.com + + +* Fri Aug 1 2008 Nenad Corbic - Beta - 3.3.12 +===================================================================== + +- Compilation fix for 2.6.25 kernel + Introduced in 3.3.11 release + +- Setup update + Added bri and zaptel installation modes. + -> ./Setup install #General installation + -> ./Setup zaptel #Zaptel based installation + -> ./Setup bri #SMG BRI installation + + Streamlined Setup installation script + Added check for Asterisk directory when installing BRI + Added check for x86 in architecture + +- Fixed Makefile build + +- Updated README File + + +* Wed Jul 30 2008 Nenad Corbic - Beta - 3.3.11 ===================================================================== - BRI to Analog Faxing Update Improved faxing over SMG Gateway and Zaptel Analog. - This feature drasticly improves faxing peformance between + This feature drastically improves faxing performance between BRI and Analog cards over Asterisk. - BRI Update - Added overlap dailing support - Added support for BRI with 16 channel Echo Canceller. + Added overlap dialing support + Added support for BRI with 16 channel Echo Canceler. Support for test start option, that only verifies configuration files without applying changes. Support for non-syslog logging. @@ -47,7 +68,7 @@ Copyright (c) 1995-2008 Sangoma Technologies Inc. Added a check for buffer overflow in write function. - New Octasic EC Image - Impoves faxing over Hardware Echo Canceller. + Improves faxing over Hardware Echo Canceler. - BRI Bug fix on startup The clock measuring function has limited and could fail on some machines. diff --git a/Makefile b/Makefile index fc51195..60354fe 100644 --- a/Makefile +++ b/Makefile @@ -73,6 +73,7 @@ ifneq (,$(wildcard $(ZAPDIR)/zaptel.h)) EXTRA_CFLGS+= -DSTANDALONE_ZAPATA -DBUILDING_TONEZONE ZAP_OPTS= --zaptel-path=$(ZAPDIR) ZAP_PROT=TDM + PROTS=DEF else ifneq (,$(wildcard $(ZAPDIR)/kernel/zaptel.h)) ZAPDIR=/usr/src/zaptel/kernel @@ -81,11 +82,13 @@ else EXTRA_CFLGS+= -DSTANDALONE_ZAPATA -DBUILDING_TONEZONE ZAP_OPTS= --zaptel-path=$(ZAPDIR) ZAP_PROT=TDM + PROTS=DEF-TDM else ZAP_OPTS= ZAP_PROT= ZAPDIR_PRIV= ENABLE_WANPIPEMON_ZAP=NO + PROTS=DEF endif endif @@ -117,7 +120,7 @@ all_bin_kmod: _checkzap _checksrc _cleanoldwanpipe _check_kver rm -rf $(PWD)/ast_build_dir; \ fi @mkdir -p $(PWD)/ast_build_dir - ./Setup drivers --builddir=$(PWD)/ast_build_dir --with-linux=$(KDIR) $(ZAP_OPTS) --usr-cc=$(CC) --protocol=DEF-$(ZAP_PROT) --no-zaptel-compile --noautostart --arch=$(ARCH) --silent + ./Setup drivers --builddir=$(PWD)/ast_build_dir --with-linux=$(KDIR) $(ZAP_OPTS) --usr-cc=$(CC) --protocol=$(PROTS) --no-zaptel-compile --noautostart --arch=$(ARCH) --silent @eval "./patches/copy_modules.sh $(PWD)/ast_build_dir $(WAN_DIR)" diff --git a/README b/README index e03bb3a..9e1b7ba 100644 --- a/README +++ b/README @@ -1,12 +1,57 @@ ------------------------------------------------------------------------------ -Linux WAN Router Utilities Package ------------------------------------------------------------------------------- - -Author: Nenad Corbic -Copyright (c) 1995-2006 Sangoma Technologies Inc. ------------------------------------------------------------------------------- - For latest docs please visit Sangoma Wiki Sangoma Wiki: http://wiki.sangoma.com ------------------------------------------------------------------------------ +Copyright (c) 1995-2008 Sangoma Technologies Inc. + + +Installation +------------ + + ./Setup install #General Installation (Most Flexible) +or + ./Setup zaptel #Install for Asterisk/CallWeaver/Zaptel +or + ./Setup bri #Install SMG BRI card for Asterisk/CallWeaver + + +Configuration +------------- + + 1) create configuration files for Zaptel and Asterisk/CallWeaver + -> /usr/sbin/wancfg_zaptel + + 2) create configuration files for SMG BRI/SS7, Zaptel and Asterisk/CallWeaver + -> /usr/sbin/wancfg_smg + + 3) create configuration files for TDM API (Default for FreeSwitch) + -> /usr/sbin/wancfg_tdmapi + + 2) create WANPIPE WAN/IP configuration files. + -> /usr/sbin/wancfg + + +Operation +--------- + + 1) start,stop,restart individual/all devices and interfaces. + -> /usr/sbin/wanrouter + -> /usr/sbin/wanrouter [start|stop|restart|status|hwprobe|help] + + 2) debug line, protocol and driver problems. + -> /usr/sbin/wanpipemon + -> /usr/sbin/wanpipemon -p aft #Help + -> /usr/sbin/wanpipemon -g #GUI Debug Mode + -> /usr/sbin/wanpipemon -i w1g1 -c Ta #View T1/E1 Alarms + + +API Samples +------------ + + 1) aid in WANPIPE API development + -> /etc/wanpipe/api + + + + diff --git a/README-1.install b/README-1.install deleted file mode 100644 index 8d6d0fb..0000000 --- a/README-1.install +++ /dev/null @@ -1,390 +0,0 @@ -WANPIPE PACKAGE INSTALLATION/UN-INSTALLATION -============================================ - -Author: Nenad Corbic - - -For Lates Docs Please visit -http://wiki.sangoma.com - - - -WANPIPE PACKAGES -================ - -Wanpipe SOURCE packages are located in: - ftp.sangoma.com/linux/current_wanpipe - - Download the latest SOURCE wanpipe release - in ANY directory: - ex: cd /tmp - tar xvfz wanpipe-.tgz - - The tar will create the temporary - wanpipe/ directory. - - -WANPIPE SOURCE PACKAGE Installation -==================================== - -The 'Setup' script located in temporary wanpipe/ -directory should be used to install/un-install -and re-configure all WANPIPE driver and utilities. - -The Setup installation script contains numerous -options that can be used to customise wanpipe -installation. Run ./Setup without any arguments -for usage. - -Run the Setup script from temporary wanpipe/ directory -(wanpipe directory was created by untaring the source package) - - cd wanpipe/ - - ./Setup install - -The install option will do the following: - ------- - 1. Check that all WANPIPE files are accounted for. - - 2. Check/modify permissions on all WANPIPE files. - - 3. Prompt the user to Install/Upgrade WANPIPE - drivers into the Linux kernel source. - - NOTE: The kernel source must be located - in /usr/src/linux. - - Or the linux source directory - must be supplied with '--with-linux' argument. - - It is always RECOMMENDED to upgrade/update - the kernel source tree with the latest - wanpipe source. - - 4. Prompt the user to re-compile all WANPIPE - kernel drivers and install them as modules - in the the current /lib/modules/ - directory. - - Compilaton Options: Default or Custom - - Default compilation: - option will compile the standard WANPIPE protocols - into the kernel device driver: Frame Relay, PPP, CHDLC - Multi-Port Frame Relay, Multi-Port PPP, and X25(API). " - - Custom compilation: - option will offer a menu of all available WAN and - API protocols. The user will be able to enable - protocols individually or all at once, - as desired. - - With this option, NO kernel recomilation is - necessary :) - - 5. Prompt the user to install bootstrap - scripts that will be used to start wanpipe - during boot up. - - 6. Setup the ENVIRONMENT configuration file that will - contain directory locations of WANPIPE configuration - interface and lock files. - - 7. Compile all WANPIPE utilities - - 8. Setup the WANPIPE working environment. - i.e. Install all binary files into - linux file tree. - - /etc/wanpipe : config, library, sample - and firmware files. - - /usr/sbin : user space, binary - utilites - - /lib/modules/ : wanpipe kernel - modules - - /usr/share/doc/wanpipe : doc files - - - The last message in the 'Setup install' sequence will - inform you of the next step that you should take - in getting WANPIPE working. - - -o Read 'README-2.config' on how to configure wanpipe - device - - -o End of Installation - - - - -CUSTOMIZING WANPIPE SOURCE INSTALLATION -========================================= - -Installation using the '--silent' option --------------------------------------- - -The '--silent' option is available to install wanpipe -without any user interaction: - - ./Setup install --silent - - All defaults will be used! - -------------------------- - 1. Configuration directory /etc/wanpipe - 2. Start wanpipe on boot up - 3. Recompile modules for the kenrel source - in /usr/src/linux - - - -Installation using the --builddir option --------------------------------------- - -When customising the wanpipe package, it is -useful to install the package into a -virtual directory so not to pollute the -current environment. - -This way a user can tar up the temporary -directory and create a custom binary -WANPIPE package. - -eg ./Setup install --builddir=/tmp/wanpipe_build - -Note: the /tmp/wanpipe_build directory must - exist. - - - -Installation using the --protocol option --------------------------------------- - -Standard Wanpipe installatin will only -include MAINSTREAM WAN protocols when building -the kernel modules to cut down on kernel -module size. - -Mainstream Protocols: - Frame Relay, PPP, CHDLC, X25, API stack - - -To enable NON Mainstream protocols specify -extra protocols with the --protocol option. - -Non Mainstream Protocols: - BSC : API for Multipoint Bisync - BSCSTRM : API for Bisync Streaming - SS7 : API for Level2 SS7 protocol - EDU : API for Educational software - SDLC : API for SDLC protocol - POS : API for POS (S515/S509) card. - BITSTRM : API for Bitstreaming protocol - -eg: ./Setup install --protocol= - - = -- - -eg: - Compile in Bitstreaming protocol - ./Setup install --protocol=BITSTRM - - Compile in BitStreaming and POS and SDLC - ./Setup install --protocol=BITSTRM-POS-SDLC - - - -Building a custom RPM ---------------------- - - ./Setup buildrpm - - All defaults will be used! - -------------------------- - 1. Configuration directory /etc/wanpipe - 2. Start wanpipe on boot up - 3. Recompile modules for the kernel source - locatd in /usr/src/linux direcotory, - or directory supplied with --with-linux= - argument. - - - -Note: start with -- and are defined above. - - i.e. - user the --protocol filed to add in extra protocols - into the wanpipe kernel modules. - -Refer to README.rpmbuild - - - - -WANPIPE Kernel Driver Compile/Update -==================================== - -This option should be used to update the kernel -source tree with the latest wanpipe drivers -and to compile the wanpipe kernel modules -against the updated kernel source tree. - -Run the Setup script in temporary wanpipe/ directory: - -ex: cd wanpipe/ - - ./Setup drivers - -The drivers option will do the following: - ------- - 1. Prompt the user to Install/Upgrade Wanpipe - drivers into the Linux kernel source. - - NOTE: The kernel source must be located - in /usr/src/linux - - It is always RECOMMENDED to upgrade/update - the kernel source tree with the latest - wanpipe source. - - 2. Prompt the user to re-compile all WANPIPE - kernel drivers and install the as modules - in the the current /lib/modules/ - directory. - - Compilaton Options: Default or Custom - - Default compilation: - option will compile the standard WANPIPE protocols - into the kernel device driver: Frame Relay, PPP, CHDLC - Multi-Port Frame Relay, Multi-Port PPP, and X25(API). " - - Custom compilation: - option will offer a menu of all available WAN and - API protocols. The user will be able to enable - protocols individually or all at once, - as desired. - - - - -WANPIPE Utilities Re-Compilation -================================= - -This option will re-compile all WANPIPE utilities -in temporary wanpipe/ directory. - -NOTE: If this is a first time install you MUST run - the install option: Setup install. - -Run the Setup script in temporary wanpipe/ directory: - -ex: cd wanpipe/ - ./Setup utility - -The utility option will do the following: - ------- - 1. Compile all WANPIPE utilities - in temporary wanpipe/ directory - -To install utilities into /usr/sbin -directory one must run: - - ./Setup inst - - -For more info about Setup command run -./Setup without any arguments for full usage -info. - - - - -WANPIPE Un-Install -================== - -Run the Setup script in temporary wanpipe/ directory: - -ex: cd wanpipe/ - ./Setup remove - - -The remove option will do the following: - ------ - 1. Remove all boot strap WANPIPE scripts. - 2. Remove all utilities from /usr/sbin, - /etc/wanpipe, /usr/share/doc/wanpipe - directories. - -After the 'Setup remove' command, it is safe -to remove the whole temporary wanpipe/ directory. - - ex: - rm -rf wanpipe/ - - - - - - - - -WANPIPE RPM PACKAGE Installation -================================ - -Choosing an RPM: --------------- - - o Determine the Linux Distribution: - cat /etc/issue - (eg: RedHat 7.1) - - o Determine the Kernel image you are running: - uname -r - (eg: 2.4.2-2 : it is not an smp kernel) - (eg: 2.4.2-2smp : smp kernel) - - o Determine the processor type - uname -m - (eg: i686) - - o Based on the above information choose an RPM package. - - wanpipe-....rpm - - eg: ftp.sangoma.com/linux/RPM/redhat/7.1/i686/ - wanpipe-2.2.4-3.rh71up.k242-2.i686.rpm - - - -Installing RPM ----------- - - o List the contents of the rpm - - rpm -qipl - - Make sure that the /lib/modules/ directory - matches your current kernel modules directory. - - i.e. the output of command 'uname -r' must match the above - directory. - - - o The rpm must be installed using the --force option, to - override the old modules. - - rpm -i --force - - - o Read 'README-2.config' on how to configure wanpipe - device - - - -For further info, refer to WanpipeInstallation.pdf diff --git a/README-2.config b/README-2.config deleted file mode 100644 index 792a91f..0000000 --- a/README-2.config +++ /dev/null @@ -1,381 +0,0 @@ -Wanpipe Configuration -====================== - -For Latest Info please visit -http://wiki.sangoma.com - - - -Before starting WANPIPE, a configuration file (wanpipeN.conf, where -N=1,2,3..etc.)must be created in /etc/wanpipe directory. -This file contains the line, hardware and interface definitions -for the WAN connection. - -RELEASE 2.3.2 and on: - The new WANCFG utility has been release. It should - be used to configure standard WAN protocols like: - FR, PPP, CHDLC, - MULTILINK PPP (TTY), TDM_VOICE - HDLC API - ADSL - - - For both AFT and S514 series cards. - - The old WANCFG utility has been renamed to wancfg_legacy. - This utility should be used for all API protocols like: - X25, SDLC, BITSTREAMING ... - - -The program /usr/sbin/wancfg should be used to create the -configuration file(s). It is a GUI, ncurses based, -configurator that contains all wanpipe options -as well as extended help information on each -option. - -In case wancfg is not used, i.e. embedded systems, use -the sample configuration files located in -/etc/wanpipe/samples directory. - - -Things you should know before starting /usr/sbin/wancfg: - - 1. Protocol: - Frame Relay, MulitPort Frame Relay, - CHDLC, PPP, MultiPort PPP, ADSL, X25 ... - - 2. Protocol/IP Info: - Frame Relay: Type of Status Signaling (LMI, - ANSI, or Q.933 - Number of DLCI to configure - DLCI numbers - IP info for each DLCI - - CHDLC: IP info - - PPP: IP info - - X25: Maximum packet size - Number of SVCs/PVCs - IP info - - ADSL: ATM encapsulation: - Bridged Ethernet LLC over ATM: (PPPoE) - Bridged Ethernet VC over ATM - Classical IP LLC over ATM - Router IP VC over ATM - PPP LLC over ATM - PPP VC over ATM: (PPPoA) - - ATM configuration: - VPI and VCI - - If not available use the auto - config option to autodetect - these values. - - IP Info: (Not needed for PPPoE) - - NOTE: - For PPPoE and PPPoA setup please refer to - APPENDIX A below. - - ATM: ATM encapsulation: - Bridged Ethernet LLC over ATM: (PPPoE) - Bridged Ethernet VC over ATM - Classical IP LLC over ATM - Router IP VC over ATM - - ATM configuration: - VPI and VCI - - IP Info: (Not needed for PPPoE) - - 3. CSU/DSU Info: - - T1/E1: Encoding - Framing - Active Channels/Baud Rate - - 56K: Internal or External Clocking - Internal clocking should only be used - in back to back situations. - Default: External - - -For the rest of this document, we will assume we are working with the -following ISP/Telco supplied data: - - - Protocol: Frame Relay - Prot Info: - Num of DLCI's = 2 - DLCI=16 and 17 - - IP Info: DLCI 16 - Local =201.1.1.1 - PtoP =201.1.1.2 - Netmask =255.255.255.0 - Gateway =201.1.1.2 (i.e. this is the system - default gateway) - - DLCI 17 - Local =202.1.1.1 - PtoP =202.1.1.2 - Netmask =255.255.255.0 - Gateway =N/A - - - -WANCFG -====== - -IMPORTANT: - Use the "ADVANCED" sections only for non - standard configurations, otherwise leave - them default. - - -1. Start /usr/sbin/wancfg - -2. Select Create opton - -3. Select Card from Hardware Probe - -4. Specify Hardware information: - T1/E1/V35 - -5. Specify Protocol - FR,PPP,CHDLC,TTY(Multilink PPP) ... - - Frame Relay is by default configured - for Auto DLCI. Use the advanced sections - to change this. - -6. Network Interface Setup - - Specify Operation mode: - - WANPIPE: IP mode proceed to specify IP addresss - API: Custom API mode, no IP addresses - - Specify IP addresses: - -7. Save and exit - - -For old WANCFG_LEGACY example refer to APPENDIX B below! - - - - - -Troubleshooting the driver load process -======================================= - - After a startup failure run wanrouter debug - option for more information and possible solutions: - - wanrouter debug - - - Syntax Errors: - -------------- - - All wanpipe configuration file syntax errors are - reported in /var/log/wanrouter - - wanrouter conflogs - - - Driver Messages: - ---------------- - - All wanpipe driver events will be recorded in - /var/log/messages. - - Thus if errors occur, first check /var/log/messages - to find out what exactly went wrong - with the drivers startup. - - wanrouter messages - - or - - tail -f /var/log/messages - - Once the device is started you should see a - "link connecting" message. This message - indicates that the card was been configured - successfully and that the link is trying to - connect. - - - Wanpipe Debugger: - ----------------- - - /usr/sbin/wanpipemon should be used to further debug - hardware, line and protocol problems. - - /usr/sbin/wanpipemon -g - - - - Sangoma Tech Support: - --------------------- - - When reporting problems to Sangoma Tech Support please - dump the current system debug information into - a temporary file and send it via email. - - 1. wanrouter debug if_name > sangoma_debug_file.txt - (where if_name is wanpipe interface name: eg wp1fr16) - - 2. Wait for 2-5 minutes - - 3. Stop the debug by pressing ENTER - - 4. Email sangoma_debug_file.txt to Sangoma Tech Support - - - Refer to README-4.debugging - - - - - - - - -APPENDIX A: ADSL PPPoE and PPPoA Configuration -========== - -Refer to README.adsl - - - - - - - - - -APPENDIX B: WANCFG_LEGACY (Old Configurator) -========== - -1. Start /usr/sbin/wancfg - -2. Select 'Create' option - -3. Select a wanpipe device. - If this is a first device select wanpipe1 - and hit