system toolbox » voip

root@vz-test-5501:~/mISDN/mISDN-1_1_9.1# apt-get install linux-headers-2.6.24-23-openvz

root@vz-test-5501:~/mISDN/mISDN-1_1_9.1# ./std2kern

make install

modules¶

root@vz-test-5501:~/mISDN/mISDN-1_1_9.1# ls /lib/modules/2.6.24-23-openvz/extra/

avmfritz.ko  hfcpci.ko    hfcsusb.ko  mISDN_capi.ko  mISDN_debugtool.ko  mISDN_dtmf.ko  mISDN_l1.ko  mISDN_x25dte.ko  sedlfax.ko   xhfc.ko
hfcmulti.ko  hfcsmini.ko  l3udss1.ko  mISDN_core.ko  mISDN_dsp.ko        mISDN_isac.ko  mISDN_l2.ko  netjetpci.ko     w6692pci.ko

mISDN-init¶

root@vz-test-5501:~/mISDN/mISDN-1_1_9.1# ls /usr/sbin/mISDN

/usr/sbin/mISDN

root@vz-test-5501:~/mISDN/mISDN-1_1_9.1# ls /etc/init.d/mISDN -l

lrwxrwxrwx 1 root root 16 2009-04-12 14:20 /etc/init.d/mISDN -> //usr/sbin/mISDN

#apt-get install flex

root@vz-test-5501:~/mISDN/mISDNuser-1_1_9.1# sudo make install

root@vz-test-5501:~/mISDN/mISDNuser-1_1_9.1# ls /usr/lib/libisdn*

/usr/lib/libisdnnet.a  /usr/lib/libisdnnet_pic.a  /usr/lib/libisdnnet.so

root@vz-test-5501:~/mISDN/mISDNuser-1_1_9.1# ls /usr/lib/libsupp*

/usr/lib/libsuppserv.a  /usr/lib/libsuppserv_pic.a  /usr/lib/libsuppserv.so

root@vz-test-5501:~/mISDN/mISDNuser-1_1_9.1# ls /usr/lib/libmIS*

/usr/lib/libmISDN.a  /usr/lib/libmISDN_pic.a  /usr/lib/libmISDN.so

root@vz-test-5501:~/mISDN/mISDNuser-1_1_9.1# ls /usr/bin/mISDN*

/usr/bin/mISDNdebugtool

root@ifold:~/mISDN/mISDNuser-1_1_9.1# mISDN start

-- Loading mISDN modules --                      
>> /sbin/modprobe --ignore-install capi          
>> /sbin/modprobe --ignore-install mISDN_core debug=0
>> /sbin/modprobe --ignore-install mISDN_l1 debug=0  
>> /sbin/modprobe --ignore-install mISDN_l2 debug=0  
>> /sbin/modprobe --ignore-install l3udss1 debug=0   
>> /sbin/modprobe --ignore-install mISDN_capi        
>> /sbin/modprobe --ignore-install hfcpci protocol=0x2 layermask=0xf
>> /sbin/modprobe --ignore-install mISDN_dsp debug=0 options=0  

mISDN_dsp             200136  0
mISDN_capi            107916  0
mISDN_l2               41540  0
mISDN_l1               13356  0
mISDN_core             84544  6 mISDN_dsp,hfcpci,mISDN_capi,l3udss1,mISDN_l2,mISDN_l1
kernelcapi             41044  2 mISDN_capi,capi

što se tiče misdn-a njega sam uzeo iz razloga što vidim da se redovno održava te da je posljednji release iz januara 2009

takođe, pisali su ga njemci tako da je on skroz prilagođen euroisdn-u dok su svi zaptel interfejsi hack-ovi na zaptel interfejs koji su pisali amerikanci

hajde da probam transfer ... *0 hah ja sam kod upgrade-a prekrio one feature.conf ... idem ga vratiti

root@ifold:/etc/asterisk# cp features.conf.dpkg-old features.conf

transfer nakon restarta asteriska radi

jaunty¶

pokušao instalirati mISDN isto i u jaunty-ju ali imam problema ...

a evo zašto:

From Linux Kernel 2.6.27 on, mISDN v2 will be already included by kernel.org

mISDN v2.x¶

• kernelspace core covers layer1 and layer2
• complete redesigned userspace API using sockets
• embedded in kernel >= 2.6.27
• no kernel capi
• supported hardware: hfcmulti, hfcpci

• layer3 (TE/NT) in userspace libmisdn
• asterisk connectivity via lcr + chan_lcr
• tools already ported to the new socket api
  • misdn_info
  • misdn_log
  • misdn_cleanl2
• new mISDNuser tools
  • misdn_rename

root@ubuntu:/home/hernad/devel/ubuntu/linux-2.6.28/drivers/isdn/hardware/mISDN# ls -l
total 256

-rw-r--r-- 1 root root 145793 2008-12-25 00:26 hfcmulti.c
-rw-r--r-- 1 root root  31387 2008-12-25 00:26 hfc_multi.h
-rw-r--r-- 1 root root  61782 2008-12-25 00:26 hfcpci.c
-rw-r--r-- 1 root root   6112 2008-12-25 00:26 hfc_pci.h
-rw-r--r-- 1 root root    650 2008-12-25 00:26 Kconfig
-rw-r--r-- 1 root root    138 2008-12-25 00:26 Makefile

hah ... hfcusb nije pokrivena sa v2 :(

Re: [asterisk-users] Junghanns quadBRI and mISDN

Alberto Pastore
Tue, 24 Oct 2006 01:54:32 -0700

Maybe I found the cause...
My Junghanns quadBRI PCI subsystem ID is 0xB552 (that is,
quadBRI version 2.0), while mISDN expects 0xB550 (quadBRI
version 1.0)....

I'm wondering what differences lie in the two boards from a
driver's perspective... I'll try to recompile mISDN by
adding also subsys=0xB552 to the list of supported pci devices.
I'm not very familiar with kernel drivers, so... good luck to me.

Alberto.

Alberto Pastore ha scritto:

    Hi.
    I'm trying to run a Junghanns quadBRI card with mISDN drivers.

    I'm able to compile kernel mode & user mode mISDN components as well as chan_misdn.

    The "misdn-init config" properly detects the card and starts
    the hfcmulti driver; "lsmod" shows all required drivers are loaded.

    However, the misdnportinfo seems not able to find any card.

    Has any one successfully managed to run Junghanns cards with
    mISDN? (there are a couple of serious issues using bristuff
    and we've been looking for alternate drivers).

    Thanks,
    Alberto.

[Misdn-asterisk] chan_misdn and junghanns quadbri 2.0

Massimo De Nadal
Fri, 15 Dec 2006 09:15:03 -0800

Hi,

I'm triyng to use a junghanns quadbri 2.0 (the new one with hw watchdog) with chan_misdn. "misdn-init scan" seems to find the card and "misdn-init start" loads the hfcmulti module but asterisk fails to load chan_misdn.so. Does anybody know if hfcmulti modules works correctly with quadbri 2.0 boards ?

misdn v2 podržava Junghanns.NET duoBRI® PCI/miniPCI ISDN (HFC-4S based PCI card)¶

http://www.misdn.org/index.php/MISDN_v2_Hardware#HFC-4S_based_PCI_cards

HFC-4S based PCI cards

    * supported by hfcmulti.ko:
          o beronet BN2S0
          o beronet BN4S0
          o beronet BN4S0e
          o beronet BNxS0mini
          o digium B410P
          o gerdes Primux 4S
          o Junghanns.NET unoBRI® miniPCI ISDN
          o Junghanns.NET duoBRI® PCI/miniPCI ISDN <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
          o Junghanns.NET quadBRI® PCI/miniPCI ISDN
          o OpenVox B200x
          o OpenVox B400x

podrška za CologneChip HFC ISDN¶

Every ISDN TA (PCI/PCIe/USB) based on CologneChip's HFC ISDN controller series should be supported by mISDN v2.

1. The following list tries to give a complete overview of specific Products.
2. The list describes the current development snapshot of mISDN v2 (aka git 'socket' branch) and may differ from the mISDN you find within the current Linux Kernel from kernel.org.

root@ubuntu:/home/hernad/devel/ubuntu/linux-2.6.28/drivers/isdn/hardware/mISDN# lsusb | grep ISDN

Bus 002 Device 002: ID 07b0:0007 Trust Technologies ISDN TA

HFC-S USB based devices

    * supported by hfcsusb.ko:
          o ISDN USB TA (Cologne Chip HFC-S USB based) - (VID:0x0959, PID:0x2bd0)
          o DrayTek miniVigor 128 USB ISDN TA - (VID:0x0675, PID:0x1688)
          o Billion tiny USB ISDN TA 128 - (VID:0x07b0, PID:0x0007) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
          o Stollmann USB TA - (VID:0x0742, PID:0x2008)
          o OEM USB ISDN TA - (VID:0x0742, PID:0x200A)
          o Olitec USB RNIS - (VID:0x08e3, PID:0x0301)
          o Bewan Modem RNIS USB - (VID:0x07fa, PID:0x0846)
          o Djinn Numeris USB - (VID:0x07fa, PID:0x0847)
          o Twister ISDN TA - (VID:0x07b0, PID:0x0006)
          o Eicon DIVA USB 4.0 - (VID:0x071d, PID:0x1005)
          o ZyXEL OMNI.NET USB II - (VID:0x0586, PID:0x0102)

ahaa u git repos-u imam hfcsusb

hernad@nmraka-5:~/devel/git/mISDN$ git checkout -b socket origin/socket
hernad@nmraka-5:~/devel/git$ git clone git://git.misdn.org/git/mISDNuser.git
hernad@nmraka-5:~/devel/git$ git clone git://git.misdn.org/git/mISDN.git

hernad@nmraka-5:~/devel/git/mISDN$ ls drivers/isdn/hardware/mISDN/

compat_ids.h  hfc_multi.h  hfc_pci.h  hfcsusb.h  hwskel.h      l1loop.c  Makefile.v2.6  xhfc_pci2pi.c  xhfc_su.c
hfcmulti.c    hfcpci.c     hfcsusb.c  hwskel.c   Kconfig.v2.6  l1loop.h  xhfc24sucd.h   xhfc_pci2pi.h  xhfc_su.h

http://www.misdn.org/index.php/MISDN_v2_Installation

load mISDN v2 modules

• modprobe mISDN_core
• modprobe mISDN_dsp

• modprobe hfcmulti
• modprobe hfcpci
• modprobe hfcsusb
• modprobe xhfc

follow the module specific links above to get information about additional module parameters of general module descriptions.

http://www.misdn.org/index.php/MISDN_v2_hfcsusb.ko

hfcsusb module parameters

    * debug=<n>, default=0, with n=0xHHHHGGGG
          o G - common mISDN l1 debug flags
                + 0x00000001 : DEBUG_HW
                + 0x00000002 : DEBUG_HW_OPEN
                + 0x00000100 : DEBUG_HW_DCHANNEL
                + 0x00000200 : DEBUG_HW_DFIFO
                + 0x00001000 : DEBUG_HW_BCHANNEL
                + 0x00002000 : DEBUG_HW_BFIFO 
          o H - additional l1 debug flags
                + 0x00010000 : DBG_HFC_CALL_TRACE
                + 0x00020000 : DBG_HFC_FIFO_VERBOSE
                + 0x00100000 : DBG_HFC_USB_VERBOSE
                + 0x00200000 : DBG_HFC_URB_INFO
                + 0x00400000 : DBG_HFC_URB_ERROR 
    * poll=<n>, default 128
          o n : burst size of PH_DATA_IND at transparent rx data

http://www.misdn.org/index.php/Howto_for_Debian_Lenny

This it what it takes to have a HFC-S USB based ISDN TA running on Debian Lenny

I used an amd64 buisiness card install using no preselected software package categories at all.

aaa imamo hisax

root@ubuntu:/home/hernad/devel/asterisk/mISDN/mISDN# lsmod | grep hfc

hfc_usb                24600  0
hisax                 513156  1 hfc_usb

root@ubuntu:/home/hernad/devel/asterisk/mISDN/mISDN# sudo modprobe -r hfc_usb

..

nakon restarta

root@ubuntu:~# lsmod | grep hfc

hfcsusb                38808  0
mISDN_core             89380  1 hfcsusb

root@ubuntu:/home/hernad/devel/asterisk/mISDN/mISDNuser# misdn_info

Found 1 port
  Port  0 'HFC-S_USB.1':     TE/NT-mode BRI S/T (for phone lines & phones)
                             2 B-channels: 1-2

bez ikakvih problema se driver učitava i uklanja

root@ubuntu:/home/hernad/devel/asterisk/mISDN/mISDNuser# modprobe -rv hfcsusb

rmmod /lib/modules/2.6.28-11-generic/extra/hfcsusb.ko
rmmod /lib/modules/2.6.28-11-generic/extra/mISDN_core.ko

root@ubuntu:/home/hernad/devel/asterisk/mISDN/mISDNuser# modprobe -v hfcsusb

insmod /lib/modules/2.6.28-11-generic/extra/mISDN_core.ko
insmod /lib/modules/2.6.28-11-generic/extra/hfcsusb.ko

Asterisk with LCR

LCR is not only a stand allone ISDN PBX. You can use it as channel driver for Asterisk PBX. The channel driver is called chan_lcr and is a replacement of chan_mISDN. Enable "WITH-ASTERISK" in then Makefile of LCR. Compile and install. The chan_lcr will be installed and loaded next start of Asterisk.

To route calls directly to Asterisk, rather inside LCR, here are three examples. Edit "routing.conf" which is found in the installation directory ("/usr/local/lcr").

To route calls by MSN number (external calls), insert the following rule into your "[extern]" ruleset or whatever ruleset you use to route external calls.

[extern]
dialing=5678 : remote application=asterisk context=extern_context exten=5

All external calls to MSN number 5678 will be routed to chan_lcr (Asterisk). The context will be "extern_context" and the dialed extension will be "5". (On a PTP interface you may omit the "exten" keyword, so the dialed suffix will be used.)

Now you may add your extension to "/etc/asterisk/extensions.conf".

[extern_context]

exten=>5,1,Dial(SIP/phone)

In this case, all calls to extension "5" will be forwarded to chan_sip and call whatever you specified for "phone". Please refer to Asteerisk documentation.

Alternatively you can route all calls from one interface. If you have an internal interface for you phone and like to route all calls from it to Asterisk, edit the main rule in "interface.conf" of LCR.

[main]
interface=Int    : remote application=asterisk
... other rules

If "context" is omitted, the interface's name is used. In this case "Int". Because "exten" is omitted, the dialed number will be the extenion's number. Edit "/etc/asterisk/extensions.conf" and add your extensions for the interface "Int":

[Int]
exten=>_0.,1,Dial(LCR/Ext/${EXTEN:1})
exten=>5,1,Dial(SIP/phone)
exten=>6,1,Dial(SIP/phone2)
exten=>8,1,Dial(LCR/Int/1234)

By dialing "0", you will get routed to external line. Dialing "5" or "6" will do a SIP call. Dialing "8" will do an call on the internal interface "Int" and dial your MSN "1234".

If you like to use only chan_lcr for Asterisk and don't care about LCR *at all, you can *route all calls of all interfaces (internal and external) to chan_lcr:

[main]
        : remote application=asterisk

The interface name will be the extension's name for Asterisk.

To dial from Asterisk to an ISDN interface of LCR, use the following syntax:

extern=><digits>,1,Dial(LCR/<number>)
extern=><digits>,1,Dial(LCR/<interface>/<number>)
extern=><digits>,1,Dial(LCR/<interface>/<number>/<options>)

Where "number" is the number to be dialed on ISDN interface. If no "interface" is given, the first free interface is used. For "options" refer to the full documentation.

This was too fast and you still have problems? Read the documenation and drop me a mail with improved guide.

http://www.voip-info.org/wiki/view/chan_misdn

Note: chan_misdn does not yet work with the new mISDN code that's included in the Linux kernel (2.6.27). You need chan_lcr if you need to use that.

[Astlinux-users] mISDN for trunk

Hello,

I am currently preparing an update for mISDN & trunk. Unfortunately we
cannot just 'upgrade' what we have currently in trunk / 0.6 branch for
various reasons.

Therefore, please tell me what you prefer and we'll see what we can do.
I am listing a few options we have:

a.) mISDN 1.1.8 (latest official stable release), but no oslec

b.) a git-checkout from the master branch (which is similar to 1.1.8,
but it includes oslec) (not tested yet)

c.) mISDN V2 (git or snapshot 'release'), which includes all goodies,
but does not support i.e. AVM Fritz card. Another caveat, V2 cannot be
used with chan_misdn. You need chan_lcr, a new channel driver for
Asterisk and also lcr itself. (not tested yet)

ovo je znači bitno:

c.) mISDN V2 (git or snapshot 'release'), which includes all goodies,
but does not support i.e. AVM Fritz card. Another caveat, V2 cannot be
used with chan_misdn. You need chan_lcr, a new channel driver for
Asterisk and also lcr itself. (not tested yet)

na ovom threadu nastavlja se diskusija:

Philip Prindeville wrote:

What are oslec and LCR in short?

Open Source Line Echo Canceller
http://www.rowetel.com/ucasterisk/oslec.html

It is used currently in mISDN and as an option for Zaptel.

LCR is Linux Call Router, another open source project for dealing with
ISDN. It provides an Asterisk channel driver to use mISDN v2 with Asterisk.

http://www.linux-call-router.de/

zaključak astlinux community-ja je:

Hello Matt,

> Anywayz, while we're at it, chan_lcr is licensed under GPL, which means 
> it's unlikely to get included in main stream Asterisk, which means that 
> support for it may fail at some time.

That's a problem of Asterisk, not of GPL software.

> I've noticed a few changes going in to libpri (or maybe it was Dahdi) to 
> support BRI over the past couple of days (albeit in trunk), which makes 
> me think that long term the best bet is going to be native support.

DAHDI support for ISDN/BRI would be great. No more worries about mISDN
and such. But: do you think, that people start writing kernel drivers
for various BRI cards or do you think, they will use mISDN V2 code from
kernel >= 2.6.27 and just write an interface to that? Writing all
drivers again from scratch for all available cards sounds like a nice
task.....

> Which makes me think that maybe we should stick with chan_misdn for the 
> moment and then later move to native libpri/dahdi support once the 
> project moves to 1.6/trunk.

Yes, we stick with chan_misdn for now. That's the easiest for the community.

regards,

Ingmar

ima još, ovaj Ingmar je kako sam shvatio glavna faca za astlinux i pravo ufuran u tematiku

On the other hand, chan_misdn was developed by the same guys who develop
mISDN. Now they stopped working on chan_misdn and who is maintaining
that code in the future? Hmm, nobody knows ;-) That's always the same
story with open source... People want everything for free with great
support and code maintenance.

> If chan_lcr is something which could receive more support than 
> chan_misdn then maybe we should consider it.

Let it say this way: chan_misdn does not work with the latest mISDN
version which is V2. Probably chan_misdn will never work with V2 because
no one is porting it. So it has to stick with V1 code of mISDN. The
latest release here is 1.1.8. Do you believe that this code will be
maintained in the future as there is already V2? I don't know... The
ISDN protocol in general won't change probably, but kernel versions
change and you have at least to adopt your structures to newer kernel
versions. So in the future someone would have to touch the V1 code again
to make it compatible with the latest kernel.

Last but not least, kernel >= linux 2.6.27 includes mISDN V2 !! I think,
that's the future and I don't think that chan_misdn is the future unless
someone put either money on the table for the existing developers to
port it or someone else feels smart enough to do the port as another
open source project.

cheers, Ingmar

on objašnjava da je chan misdnv2/chan_lcr nešto što je izvjesno s obzirom da je to uletilo u main kernel tree

new misdn v2 api

>>     
>
> I hope that chan_mISDN will be supported. I don't much like the idea
> that when routing ISDN calls, all voice data will be transported through
> unix sockets from one process to another. Twice. That doesn't really
> seem like it will help to keep latency down.
>
> Or do I misunderstand the design of chan_lcr?
>
>   
only the signalling is transported through unix Sockets between lcr and 
chan_lcr , the Audio data will be handled by chan_lcr directly, so you 
won't have more latency issues than before i guess.

regarding chan_misdn:

I *don't think that we'll port chan_misdn to the socket branch*, it has a 
*very different interface* compared to the old mISDN and since it is a lot 
of work for us we don't have the time to do that :-( 

there are so many BRI Board clones on the market now, so that the prices 
are lowered like every month, this means unfortunately that we can't 
afford to spend too much money into open source developement anymore,  
though it's sad, we'll have to go this way.

the conclusion is, that *we won't port chan_misdn unless somebody is 
willing to pay for that*, personally i would be glad to port it, but i 
guess it'll be far too expensive to do it.

Howto get Asterisk with mISDN V2 and Linux Call Router running on debian lenny

This is a short howto how I built the debian patches and how you can — as a user — install everything needed for mISDN version 2 and Linux Call Router (LCR) with asterisk chan_lcr running on debian lenny.

I’m providing debian packages for Kernel (v 2.6.28.5), an updated zaptel (debian lenny zaptel doesn’t compile with newer kernels and zaptel wctdm uses some settings for analogue phones that don’t work with german and austrian phone like the “R”-key or optional pulse dialling), finally I’m providing a slightly patched asterisk for larger buffer sizes when playing long tones, LCR and misdnv2user packages originally built by Joerg Dorchain. My misdnv2user is the same as Joergs. The lcr package contains my bug-fix for DTMF digits A-F (also in Joergs packages now) which don’t work in upstream LCR version 1.3 and an updated /etc/init.d/lcr for querying the status of lcr.

I’m also providing source packages, except for the kernel — the kernel is stock kernel.org 2.6.28.5 configured for use of mISDN. The kernel was built using debians make-kpkg from the kernel-package debian package. And the config used for building the kernel is in the binary package.

http://www.dorchain.net/~joerg/code/debian/

hernad@ubuntu:/lib/modules/2.6.28-11-generic/extra$ sudo insmod ./mISDN_core.ko
hernad@ubuntu:/lib/modules/2.6.28-11-generic/extra$ sudo insmod ./mISDN_dsp.ko
hernad@ubuntu:/lib/modules/2.6.28-11-generic/extra$ sudo insmod ./mISDN_dsp_oslec.ko
hernad@ubuntu:/lib/modules/2.6.28-11-generic/extra$ sudo insmod ./hfcsusb.ko

hernad@ubuntu:/lib/modules/2.6.28-11-generic/extra$ lsmod | grep mISDN

mISDN_dsp_oslec        14336  0
mISDN_dsp             209892  1 mISDN_dsp_oslec
mISDN_core             89380  2 hfcsusb,mISDN_dsp

dmesg

[14068.774966] mISDN_dsp: DSP clocks every 64 samples. This equals 2 jiffies.
[14094.228347] HFC-S_USB driver Rev. Revision: 0.3.3 (socket), 2008-11-05 debug(0x0) poll(128)
[14094.228371] hfcsusb_probe: interface(0) actalt(0) minor(0) vend_idx(2)
[14094.228380] HFC-S_USB: probe of 2-1:1.0 failed with error -5
[14094.228387] hfcsusb_probe: interface(1) actalt(0) minor(0) vend_idx(2)
[14094.228403] HFC-S_USB: hfcsusb_probe: detected "Billion tiny USB ISDN TA 128" (4 Isochron IN + 3 Isochron OUT, if=1 alt=1)
[14094.233536] HFC-S_USB: registered as 'HFC-S_USB.1'
[14094.233633] usbcore: registered new interface driver HFC-S_USB

hernad@ubuntu:/usr/local/lcr$ lcr query

** LCR  Version 1.4

-> Using 'misdn_info'

Found 1 port
  Port  0 'HFC-S_USB.1':     TE/NT-mode BRI S/T (for phone lines & phones)
                             2 B-channels: 1-2