NSLU2-Linux
view · edit · print · history

OpenSlug.Asterisk History

Hide minor edits - Show changes to markup

October 27, 2008, at 02:51 PM by krim -- update
Changed lines 1-26 from:

At the moment there is Asterisk 1.2 in the feeds: http://ipkg.nslu2-linux.org/feeds/openslug/cross/3.10-beta/

The new Asterisk 1.4 is not available in the feeds, but it can be installed from the experimental optware feed for openslug: http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/unstable/

Here are the steps (see also Optware.Slugosbe):

 cd /tmp
 wget http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/unstable/ipkg-opt_0.99.163-9_armeb.ipk
 tar -zxvf /tmp/ipkg-opt_0.99.163-9_armeb.ipk
 rm /tmp/debian-binary
 rm /tmp/control.tar.gz
 tar -ztvf /tmp/data.tar.gz
 cd /
 tar -zxvf /tmp/data.tar.gz
 rm /tmp/data.tar.gz
 cd /opt/etc
 sed -i "s/\/stable/\/unstable/" ipkg.conf
 /opt/bin/ipkg update
 /opt/bin/ipkg install asterisk14

This will install asterisk 1.4 on openslug in an optware fashion.

You can find some information about a slim Asterisk configuration here: http://www.voip-info.org/tiki-index.php?page=Asterisk+Slimming

to:

The new Asterisk 1.4 is available in the feeds

ipkg install asterisk

January 27, 2007, at 01:09 AM by osas --
Added lines 12-13:
 rm /tmp/debian-binary
 rm /tmp/control.tar.gz
Added line 17:
 rm /tmp/data.tar.gz
January 27, 2007, at 01:07 AM by osas --
Changed lines 11-12 from:
 tar -zxvf ipkg-opt_0.99.163-9_armeb.ipk
 tar -ztvf data.tar.gz
to:
 tar -zxvf /tmp/ipkg-opt_0.99.163-9_armeb.ipk
 tar -ztvf /tmp/data.tar.gz
Changed line 14 from:
 tar -zxvf data.tar.gz
to:
 tar -zxvf /tmp/data.tar.gz
January 13, 2007, at 06:22 AM by BrianZhou --
Changed lines 7-8 from:

Here are the steps (see also Optware/Slugosbe):

to:

Here are the steps (see also Optware.Slugosbe):

January 13, 2007, at 06:22 AM by BrianZhou --
Changed lines 7-8 from:

Here are the steps:

to:

Here are the steps (see also Optware/Slugosbe):

January 12, 2007, at 07:51 PM by osas -- add asterisk 1.4 info
Changed lines 1-9 from:

At the moment there is Asterisk 1.0.9 in OpenEmbedded, but not in OpenSlug. So you have to edit openembedded/conf/distro/openslug-packages.conf and openembedded/packages/meta/openslug-packages.bb in order to include asterisk in your package feed.

You could also run: $ bb -b openembedded/packages/asterisk/asterisk_1.0.9.bb

If it is in your feed, run ipkg update and ipkg install asterisk on your slug, if you have build it with bitbake directly, copy it to your slug and install it with ipkg install asterisk_1.0.9...ipkg

This installation comes without the sample config files (provided by make samples) which isn't that bad, because you don't want to use them anyway.

to:

At the moment there is Asterisk 1.2 in the feeds: http://ipkg.nslu2-linux.org/feeds/openslug/cross/3.10-beta/

The new Asterisk 1.4 is not available in the feeds, but it can be installed from the experimental optware feed for openslug: http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/unstable/

Here are the steps:

 cd /tmp
 wget http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/unstable/ipkg-opt_0.99.163-9_armeb.ipk
 tar -zxvf ipkg-opt_0.99.163-9_armeb.ipk
 tar -ztvf data.tar.gz
 cd /
 tar -zxvf data.tar.gz
 cd /opt/etc
 sed -i "s/\/stable/\/unstable/" ipkg.conf
 /opt/bin/ipkg update
 /opt/bin/ipkg install asterisk14

This will install asterisk 1.4 on openslug in an optware fashion.

December 10, 2005, at 02:16 PM by xaver --
Changed lines 112-113 from:

- Where can we ge a kernel with ISDN and the HFC-S module?

to:

- Where can we get a kernel with ISDN and the HFC-S module?

December 10, 2005, at 02:16 PM by xaver -- Questions
Added lines 105-113:

Questions:

- Is this working fully functional with a HFC-S adapter?

- Where can we ge a kernel with ISDN and the HFC-S module?

August 18, 2005, at 07:26 PM by tman --
Changed lines 43-44 from:

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the OE bugtracker you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.

to:

The current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the OE bugtracker you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel CAPI support.

Changed lines 49-52 from:

I will try to talk the openslug guys into enabling this, so that the produced misdn modules do work on your slug. Until then you have to build your own capi modules.

The next step is to get mISDNuser working. There are several issues with headerfiles, for example the bitops.h from kernel headers does include serveral bit operation macros on x86 but not on ARM, I don't really know why.

to:

I will try to talk the openslug guys into enabling this, so that the produced mISDN modules do work on your slug. Until then you have to build your own CAPI modules.

The next step is to get mISDNuser working. There are several issues with headerfiles, for example the bitops.h from kernel headers does include several bit operation macros on x86 but not on ARM, I don't really know why.

August 18, 2005, at 07:24 PM by tman --
Changed line 104 from:

As you can see, ilbc and lpc10 are floating point based and not useable on a slug as long as you don't recode these codecs in a fixed point way. :-)

to:

As you can see, ilbc and lpc10 are floating point based and not usable on a slug as long as you don't recode these codecs in a fixed point way due to the lack of a floating point unit :-)

August 18, 2005, at 07:23 PM by tman --
Changed lines 53-81 from:

It loads fine on my slug (dmesg after modprobe hfcsusb debug=0) :
Modular ISDN Stack core $Revision: 1.25 $
mISDNd: kernel daemon started
mISDNd: test event done
CAPI Subsystem Rev 1.1.2.8
mISDN Capi 2.0 driver file version 1.14
hfcsusb driver Rev. 1.5 (debug=0)
HFC-S USB: probing interface(0) actalt(0) minor(0)
mISDN_hfcsusb: probe of 3-1:1.0 failed with error -5
HFC-S USB: probing interface(1) actalt(0) minor(0)
HFC-S USB: detected "Billion tiny USB ISDN TA 128"
HFC-S USB: Endpoint-Config: 3 Interrupt IN + 3 Isochron OUT (if=1 alt=2)
hfcsusb_1 wants TE Mode
HFC-S USB: starting intr IN fifo:5
HFC-S USB: starting intr IN fifo:1
HFC-S USB: starting intr IN fifo:3
HFC-S USB: starting ISO-chain for Fifo 4
HFC-S USB: starting ISO-chain for Fifo 0
HFC-S USB: starting ISO-chain for Fifo 2
HFC-S USB: probing interface(0) actalt(0) minor(0)
HFC-S USB: no valid vendor found in USB descriptor
mISDN_hfcsusb: probe of 2-1:1.0 failed with error -5
usbcore: registered new driver mISDN_hfcsusb
ISDN L1 driver version 1.11
ISDN L2 driver version 1.20
mISDN: DSS1 Rev. 1.30
kcapi: Controller 1: mISDN1 attached
kcapi: card 1 "mISDN1" ready.

to:

It loads fine on my slug (dmesg after modprobe hfcsusb debug=0):

 Modular ISDN Stack core $Revision: 1.25 $
 mISDNd: kernel daemon started
 mISDNd: test event done
 CAPI Subsystem Rev 1.1.2.8
 mISDN Capi 2.0 driver file version 1.14
 hfcsusb driver Rev. 1.5 (debug=0)
 HFC-S USB: probing interface(0) actalt(0) minor(0)
 mISDN_hfcsusb: probe of 3-1:1.0 failed with error -5
 HFC-S USB: probing interface(1) actalt(0) minor(0)
 HFC-S USB: detected "Billion tiny USB ISDN TA 128"
 HFC-S USB: Endpoint-Config: 3 Interrupt IN + 3 Isochron OUT (if=1 alt=2)
 hfcsusb_1 wants TE Mode
 HFC-S USB: starting intr IN fifo:5
 HFC-S USB: starting intr IN fifo:1
 HFC-S USB: starting intr IN fifo:3
 HFC-S USB: starting ISO-chain for Fifo 4
 HFC-S USB: starting ISO-chain for Fifo 0
 HFC-S USB: starting ISO-chain for Fifo 2
 HFC-S USB: probing interface(0) actalt(0) minor(0)
 HFC-S USB: no valid vendor found in USB descriptor
 mISDN_hfcsusb: probe of 2-1:1.0 failed with error -5
 usbcore: registered new driver mISDN_hfcsusb
 ISDN L1 driver version 1.11
 ISDN L2 driver version 1.20
 mISDN: DSS1 Rev. 1.30
 kcapi: Controller 1: mISDN1 attached
 kcapi: card 1 "mISDN1" ready.
Changed lines 85-87 from:

This is on a TurboSlug? (266MHz):

slung*CLI> show translation

to:

This is on a TurboSlug (266MHz):

 slung*CLI> show translation
August 18, 2005, at 07:21 PM by tman --
Changed lines 18-19 from:
  • The newest revisions of the DrayTek? miniVigor contains the chip. I bought one on eBay and it had a WinBond chipset. All versions look the same from the outside, the only way you can tell which chipset it uses is to open the plastic case. Furthermore these miniVigors are supported with Mac OS X so you may have to pay a higher price on eBay because those rich apple guys are also bidding.
to:
  • The newest revisions of the DrayTek miniVigor contains the chip. I bought one on eBay and it had a WinBond chipset. All versions look the same from the outside, the only way you can tell which chipset it uses is to open the plastic case. Furthermore these miniVigors are supported with Mac OS X so you may have to pay a higher price on eBay because those rich apple guys are also bidding.
Added line 38:
Changed lines 43-44 from:

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the [[OE bugtracker|http://bugs.openembedded.org/show_bug.cgi?id=240[[ you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.\\

to:

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the OE bugtracker you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.

August 18, 2005, at 07:20 PM by tman --
Changed lines 10-11 from:

You can find some information about a slim asterisk configuration here: http://www.voip-info.org/tiki-index.php?page=Asterisk+Slimming

to:

You can find some information about a slim Asterisk configuration here: http://www.voip-info.org/tiki-index.php?page=Asterisk+Slimming

Changed lines 16-21 from:

Which hardware doesn include such a chip:

  • DrayTek? miniVigor is told to has such chips, but only the newest revisions. I bought one on ebay and it had a winbond chipset. You cannot distinguish which version you get, they look all the same, until you open this plastic case. Furthermore these miniVigors are supported with OSX so you may have to pay a higher price on ebay because those rich apple guys are also bidding.
  • Billion tiny usb or Acer are the same and I haven't heard about a non hfc-s version so far. I bought a Billion adapter on ebay for about 10 bucks.

The following table is aggregated from the hfcs-usb misdn driver (http://www.isdn4linux.de/cgi-bin/viewcvs.cgi/mISDN/drivers/isdn/hardware/mISDN/hfcs_usb.c?rev=HEAD&content-type=text/vnd.viewcvs-markup)

to:

HFC-S USB hardware:

  • The newest revisions of the DrayTek? miniVigor contains the chip. I bought one on eBay and it had a WinBond chipset. All versions look the same from the outside, the only way you can tell which chipset it uses is to open the plastic case. Furthermore these miniVigors are supported with Mac OS X so you may have to pay a higher price on eBay because those rich apple guys are also bidding.
  • Billion tiny USB or Acer are the same and I haven't heard about a non HFC-S version so far. I bought a Billion adapter on eBay for about 10 bucks.

The following table is aggregated from the hfcs-usb misdn driver

Changed line 42 from:

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the OE bugtracker (http://bugs.openembedded.org/show_bug.cgi?id=240) you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.\\

to:

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the [[OE bugtracker|http://bugs.openembedded.org/show_bug.cgi?id=240[[ you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.\\

Changed line 76 from:

mISDN: DSS1? Rev. 1.30\\

to:

mISDN: DSS1 Rev. 1.30\\

Deleted lines 79-80:
Changed lines 82-83 from:

This is on a powerslug (266mhz):

to:

This is on a TurboSlug? (266MHz):

Deleted line 101:
August 18, 2005, at 04:59 PM by Malfi --
Changed lines 37-38 from:
=USB ISDN TA06756694
to:
NameVendor IDProduct ID
USB ISDN TA0x06750x6694
August 18, 2005, at 04:59 PM by Malfi --
Added lines 35-38:

The Winbond Draytek miniVigor128 (unusable for misdn) looks like this (according to /proc/bus/usb/devices)

=USB ISDN TA06756694
August 18, 2005, at 02:45 AM by Malfi -- informations about hfcs-usb
Changed lines 12-76 from:
to:

HFC-S USB

As I want to connect a HFC-S USB ISDN adapter to my slug, I stumbled across several things:

Which hardware doesn include such a chip:

  • DrayTek? miniVigor is told to has such chips, but only the newest revisions. I bought one on ebay and it had a winbond chipset. You cannot distinguish which version you get, they look all the same, until you open this plastic case. Furthermore these miniVigors are supported with OSX so you may have to pay a higher price on ebay because those rich apple guys are also bidding.
  • Billion tiny usb or Acer are the same and I haven't heard about a non hfc-s version so far. I bought a Billion adapter on ebay for about 10 bucks.

The following table is aggregated from the hfcs-usb misdn driver (http://www.isdn4linux.de/cgi-bin/viewcvs.cgi/mISDN/drivers/isdn/hardware/mISDN/hfcs_usb.c?rev=HEAD&content-type=text/vnd.viewcvs-markup)

NameVendor IDProduct ID
ISDN USB TA (Cologne Chip HFC-S USB based)0x09590x2bd0
Draytek miniVigor 128 USB ISDN TA0x06750x1688
Billion tiny USB ISDN TA 1280x07b00x0007
Stollmann USB TA0x07420x2008
Aceex USB ISDN TA0x07420x2009
OEM USB ISDN TA0x07420x200A
Olitec USB RNIS0x08e30x0301
Bewan Modem RNIS USB0x07fa0x0846
Djinn Numeris USB0x07fa0x0847
Twister ISDN TA0x07b00x0006

the current mISDN driver isn't tested on big endian machines and it won't even recognize your adapter once you plug it. I've build a bitbake file for OpenEmbedded, and posted it to the OE bugtracker (http://bugs.openembedded.org/show_bug.cgi?id=240) you get the bitbake and endian-patches from there. It will build the needed kernel modules. The problem until today is, that you need the common kernel capi support.
$ grep ISDN openembedded/packages/linux/openslug-kernel-2.6.12.2/defconfig

  1. ISDN subsystem
  2. CONFIG_ISDN is not set

I will try to talk the openslug guys into enabling this, so that the produced misdn modules do work on your slug. Until then you have to build your own capi modules.

The next step is to get mISDNuser working. There are several issues with headerfiles, for example the bitops.h from kernel headers does include serveral bit operation macros on x86 but not on ARM, I don't really know why.

It loads fine on my slug (dmesg after modprobe hfcsusb debug=0) :
Modular ISDN Stack core $Revision: 1.25 $
mISDNd: kernel daemon started
mISDNd: test event done
CAPI Subsystem Rev 1.1.2.8
mISDN Capi 2.0 driver file version 1.14
hfcsusb driver Rev. 1.5 (debug=0)
HFC-S USB: probing interface(0) actalt(0) minor(0)
mISDN_hfcsusb: probe of 3-1:1.0 failed with error -5
HFC-S USB: probing interface(1) actalt(0) minor(0)
HFC-S USB: detected "Billion tiny USB ISDN TA 128"
HFC-S USB: Endpoint-Config: 3 Interrupt IN + 3 Isochron OUT (if=1 alt=2)
hfcsusb_1 wants TE Mode
HFC-S USB: starting intr IN fifo:5
HFC-S USB: starting intr IN fifo:1
HFC-S USB: starting intr IN fifo:3
HFC-S USB: starting ISO-chain for Fifo 4
HFC-S USB: starting ISO-chain for Fifo 0
HFC-S USB: starting ISO-chain for Fifo 2
HFC-S USB: probing interface(0) actalt(0) minor(0)
HFC-S USB: no valid vendor found in USB descriptor
mISDN_hfcsusb: probe of 2-1:1.0 failed with error -5
usbcore: registered new driver mISDN_hfcsusb
ISDN L1 driver version 1.11
ISDN L2 driver version 1.20
mISDN: DSS1? Rev. 1.30
kcapi: Controller 1: mISDN1 attached
kcapi: card 1 "mISDN1" ready.


August 17, 2005, at 04:36 AM by malfi --
Changed lines 32-33 from:

As you can see, ilbc and lpc10 are floating point based and not useable on a slug aslong as you don't recode these codes in a fixed point way. :-)

to:

As you can see, ilbc and lpc10 are floating point based and not useable on a slug as long as you don't recode these codecs in a fixed point way. :-)

August 17, 2005, at 04:35 AM by malfi --
Added line 14:
August 17, 2005, at 04:35 AM by malfi -- asterisk on openslug
Added lines 1-32:

At the moment there is Asterisk 1.0.9 in OpenEmbedded, but not in OpenSlug. So you have to edit openembedded/conf/distro/openslug-packages.conf and openembedded/packages/meta/openslug-packages.bb in order to include asterisk in your package feed.

You could also run: $ bb -b openembedded/packages/asterisk/asterisk_1.0.9.bb

If it is in your feed, run ipkg update and ipkg install asterisk on your slug, if you have build it with bitbake directly, copy it to your slug and install it with ipkg install asterisk_1.0.9...ipkg

This installation comes without the sample config files (provided by make samples) which isn't that bad, because you don't want to use them anyway.

You can find some information about a slim asterisk configuration here: http://www.voip-info.org/tiki-index.php?page=Asterisk+Slimming

This is on a powerslug (266mhz): slung*CLI> show translation

         Translation times between formats (in milliseconds)
          Source Format (Rows) Destination Format(Columns)

         g723   gsm  ulaw  alaw  g726 adpcm  slin lpc10  g729 speex  ilbc
   g723     -     -     -     -     -     -     -     -     -     -     -
    gsm     -     -    14    14    55    17    13   170     -     -  2297
   ulaw     -    42     -     1    43     5     1   158     -     -  2285
   alaw     -    42     1     -    43     5     1   158     -     -  2285
   g726     -    82    42    42     -    45    41   198     -     -  2325
  adpcm     -    44     4     4    45     -     3   160     -     -  2287
   slin     -    41     1     1    42     4     -   157     -     -  2284
  lpc10     -   268   228   228   269   231   227     -     -     -  2511
   g729     -     -     -     -     -     -     -     -     -     -     -
  speex     -     -     -     -     -     -     -     -     -     -     -
   ilbc     -   495   455   455   496   458   454   611     -     -     -

As you can see, ilbc and lpc10 are floating point based and not useable on a slug aslong as you don't recode these codes in a fixed point way. :-)

view · edit · print · history · Last edited by krim.
Based on work by osas, BrianZhou, xaver, tman, Malfi, and malfi.
Originally by malfi.
Page last modified on October 27, 2008, at 02:51 PM