Podrška #18392
Zatvoren
dahdi, zaptel, qozap, mISDN ?!
Dodano od Ernad Husremović prije više od 15 godina. Izmjenjeno prije skoro 15 godina.
0%
Fajlovi
| voip-mg_1.0.0.tar.gz (5,28 MB) voip-mg_1.0.0.tar.gz | Ernad Husremović, 18.09.2009 23:26 | ||
| hfc_dahdi.tar.gz (14,6 KB) hfc_dahdi.tar.gz | Ernad Husremović, 28.09.2009 12:16 | ||
| zaptel (3,89 KB) zaptel | /etc/init.d zaptel | Ernad Husremović, 05.10.2009 16:06 | |
| asterisk (5,42 KB) asterisk | /etc/init.d asterisk | Ernad Husremović, 05.10.2009 16:06 | |
| 120-hrtimer.diff (1,01 KB) 120-hrtimer.diff | staviti u viop-mg/patches-zaptel-1.4/zaptel i dodati u series | Ernad Husremović, 05.10.2009 18:09 | |
| 120-hrtimer.diff (1,01 KB) 120-hrtimer.diff | Ernad Husremović, 05.10.2009 18:17 | ||
| 121-exclude-subdir-modules.diff (668 Bajta) 121-exclude-subdir-modules.diff | Ernad Husremović, 05.10.2009 18:28 | ||
| series (170 Bajta) series | patches-zaptel-1.4/zaptel/series | Ernad Husremović, 05.10.2009 18:28 | |
| voipmg_manual.pdf (1,92 MB) voipmg_manual.pdf | Ernad Husremović, 05.10.2009 18:30 |
Povezani tiketi 4 (0 otvoreno — 4 zatvorenih)
Izmjenjeno od Ernad Husremović prije više od 15 godina
https://issues.asterisk.org/view.php?id=12757
I have installed Asterisk 1.6beta9 with libpri 1.4.4 and zaptel 1.4.10.1.
I know that BRI support is in alpha stage but i wanted to test because we european users of asterisk we were "disregarded" until now :)
Misdn works, but not very well. The biggest problem is the echo, also with hardware echo cancellation card like Digium B410P there are some calls with echo, perhaps because chan_misdn has internal additional delay (see http://peter.schlaile.de/mISDN/). [^] The other problem is that the driver of the cards based on the HFC-multi chipset hang on some circumstances, when there are poor quality lines, and a reboot is needed (if you unload the driver the kernel crash...).
I have installed and configured the unofficial qozap driver for Digium B410P available from http://svn.digium.com/view/zaptel/team/mattf/bri-related/ [^]
I have to say, in preliminar testings, that zaptel and bri works well. No echo or stability problems occured, comparing the same hardware using misdn.
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Naslov promijenjeno iz qozap ?! u zaptel, qozap ?!
Izmjenjeno od Ernad Husremović prije više od 15 godina
Izmjenjeno od Ernad Husremović prije više od 15 godina
Izmjenjeno od Ernad Husremović prije više od 15 godina
BRI hardware supported by 1.6 libpri ?
On Wed, Apr 02, 2008 at 11:17:05PM +0200, Olivier wrote:
Hi,
Has anyone information about BRI hardware supported by 1.6 libpri ?
In another thread, I was told a basic BRI card with HFC chipset (Bewan Gazel
128) was supported but I would delighted to lear about other harwarde (and
specifically about Digium B410P).
The question should be: "which BRI devices are supported with Zaptel?"
chan_zap of Asterisk 1.6 (with the help of improvements in libpri 1.6)
supports a much larger subset of the ISDN features that are unique to
BRI (and has generally better ISDN support.
Even with the version in 1.2 / 1.4 it only took a trivial patch to
chan_zap (the count of the channels) to get a very basic and limited
support of ISDN/BRI - ISDN is, after all, ISDN.
Anyway, HFC-S cards (many single-port PCI ISDN cards) are supported with
either the module zaphfc in bristuff or vzaphfc which is not even in
bristuff.
The Junghanns Duo/Quad/Octo BRI cards and a number of compatible cards
are supported in the qozap driver from bristuff.
The the driver for BRI module from our (Xorcom) Astribank is included in
the Zaptel tarball, but requires an extra small patch from bristuff
applied to Zaptel to build.
AFAIK there is no Zaptel driver for the Digium B410P BRI card.
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Naslov promijenjeno iz zaptel, qozap ?! u dahdi, zaptel, qozap ?!
http://www.das-asterisk-buch.de/2.1/zaptel-dahdi-b410p-misdn.html
4.1.1.
Why did you create DAHDI at all?
DAHDI was created because the name "Zaptel" in the context of telephony is a registered trademark of another company, and we respected their wishes that we stop infringing on their trademark. There is a lengthy mailing list post (from me) in the asterisk-users archives describing the situation.
4.1.2.
Does DAHDI still need mISDN for the B410p card or does it come with support for Euro-ISDN BRI by itself now?
You are confusing two different things; DAHDI is the same layer as Zaptel was. It provides hardware drivers and a limited amount of signaling abstraction (along with some other features), but is not at all involved in protocol-level work. chan_dahdi is the channel driver (which used to be called chan_zap), which contains protocol level support, including analog signaling, CAS, PRI and SS7 (in Asterisk 1.6).
Zaptel and mISDN were not at all related, and the same is true of DAHDI and mISDN. The only reference to mISDN in Zaptel was a Makefile target called 'b410p' which allowed people to download, build and install the mISDN and mISDNuser packages in an automated fashion, but this was just a convenience for users, it was not related to Zaptel. In DAHDI, this is no longer present, and mISDN users must follow normal processes to obtain and install mISDN.
Now, when it gets to the channel driver layer, things get a little more complicated. Asterisk 1.4 had chan_zap, which talks to Zaptel, and chan_misdn, which talks to mISDN. They don't support any hardware in common, so for Asterisk 1.4 users, support of EuroISDN BRI is still handled by chan_misdn. This is still true even in recent Asterisk 1.4 releases where chan_zap has been renamed to chan_dahdi, and now talks to DAHDI instead of Zaptel. Even though DAHDI now contains a driver for Digium's B410P BRI card, the Asterisk 1.4 chan_dahdi channel driver does not support EuroISDN BRI.
In Asterisk 1.6 the picture is a little different: the chan_misdn channel driver is still present, and users who prefer mISDN or have hardware only supported by mISDN are still welcome to use it. The Asterisk 1.6 chan_dahdi channel driver works only with DAHDI, and it contains protocol level support for EuroISDN BRI. This means that Asterisk 1.6 users can use chan_dahdi for their EuroISDN BRI connections, over any BRI card with a DAHDI driver (see below for more details).
4.1.3.
Would you call it stable and ready for production?
There are two answers to that question: the EuroISDN BRI protocol support in chan_dahdi (which actually comes from libpri) is both stable and ready for production. It has been through extensive telecom certification testing and will be supported for BRI interoperability just as it has always been for PRI interoperability.
The DAHDI driver for the Digium B410P is very new, and is working quite well for a large number of users. However, there are some open issues being worked on (these are visible in our open source issue tracker on bugs.digium.com), primarily related to ISDN L1 layer behavior with various telco operators in Europe. It is certainly stable and fully supported by Digium's development team, but there are probably environments where it is not yet ready for production until these issues are resolved.
4.1.4.
Will Euro-ISDN BRI support be available in 1.4 and Zaptel too or only in 1.6 and DAHDI?
The B410P driver will never be part of Zaptel (as there will be no more Zaptel releases anyway), and the EuroISDN BRI support in chan_dahdi will not be added to Asterisk 1.4, as we don't add new features to that release branch. However, the chan_dahdi changes required to provide EuroISDN BRI support are relatively minor, so I expect that one or more community members will publish 'backport' patches so that users can use the DAHDI B410P driver and the libpri EuroISDN BRI support in Asterisk 1.4.
4.1.5.
Will DAHDI and Zaptel support generic Cologne HFC-S BRI cards or is it B410p-specific?
The DAHDI driver for the B410P card was written specifically for that card, but since the card is based on an HFC-4S, of course the driver could be modified to support cards from other manufacturers. We would be happy to accept patches through our normal patch submission process (on bugs.digium.com) that add support for generic or manufacturer-specific versions of the HFC-S cards, if community members wish to provide them.
4.1.6.
Why do I need the libpri PRI stack for a BRI card (as it has been announced on asterisk-users)?
Because ISDN PRI (both ANSI and Euro) and EuroISDN BRI are very nearly the same protocol; in essence, libpri has the wrong name, and it should instead be something like 'libisdn', signifying that it is really an ISDN protocol stack (Q.921 and Q.931, among others), not specific to a particular interface type.
4.1.7.
Does the BRI support in DAHDI include both PtP (Point to point233) / PtmP (Point to Multi-Point234) and TE/NT mode? If the limitation is not in DAHDI, does libpri support all of these modes?
The B410P driver in DAHDI supports TE and NT mode on the HFC4-S chip, but at that level there is no difference (the hardware layer) between PtP and PtMP. libpri currently supports being a TE over either PtP or PtMP links, or being an NT over PtP links. It does not currently support acting as an NT over PtMP links, but of course patches are welcome :-)
4.1.8.
Will Asterisk continue to support chan_misdn?
Yes, we will continue to support it (as will the community members who help support it now), but our primary ISDN-related development efforts will continue to be on libpri/chan_dahdi.
Izmjenjeno od Ernad Husremović prije više od 15 godina
bringout@nmraka-2:/usr/src/dahdi-2.2.0.2/drivers/dahdi$ sudo m-a a-i dahdi
bringout@nmraka-2:/usr/src/dahdi-2.2.0.2/drivers/dahdi$ dpkg -L dahdi-modules-2.6.31-10-generic
/. /usr /usr/share /usr/share/doc /usr/share/doc/dahdi-modules-2.6.31-10-generic /usr/share/doc/dahdi-modules-2.6.31-10-generic/changelog.Debian.gz /lib /lib/modules /lib/modules/2.6.31-10-generic /lib/modules/2.6.31-10-generic/staging /lib/modules/2.6.31-10-generic/staging/echo /lib/modules/2.6.31-10-generic/staging/echo/echo.ko /lib/modules/2.6.31-10-generic/dahdi /lib/modules/2.6.31-10-generic/dahdi/dahdi_echocan_sec.ko ... /lib/modules/2.6.31-10-generic/dahdi/xpp/xpp_usb.ko /lib/modules/2.6.31-10-generic/dahdi/xpp/xpd_bri.ko /lib/modules/2.6.31-10-generic/dahdi/xpp/xpd_pri.ko /lib/modules/2.6.31-10-generic/dahdi/xpp/xpp.ko /lib/modules/2.6.31-10-generic/dahdi/xpp/xpd_fxo.ko /lib/modules/2.6.31-10-generic/dahdi/xpp/xpd_fxs.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_echocan_kb1.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_dummy.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_dynamic_eth.ko /lib/modules/2.6.31-10-generic/dahdi/wct4xxp /lib/modules/2.6.31-10-generic/dahdi/wct4xxp/wct4xxp.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_dynamic_loc.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_transcode.ko /lib/modules/2.6.31-10-generic/dahdi/wcfxo.ko /lib/modules/2.6.31-10-generic/dahdi/wcte11xp.ko /lib/modules/2.6.31-10-generic/dahdi/wct1xxp.ko /lib/modules/2.6.31-10-generic/dahdi/wcb4xxp /lib/modules/2.6.31-10-generic/dahdi/wcb4xxp/wcb4xxp.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_echocan_sec2.ko /lib/modules/2.6.31-10-generic/dahdi/wctdm24xxp /lib/modules/2.6.31-10-generic/dahdi/wctdm24xxp/wctdm24xxp.ko /lib/modules/2.6.31-10-generic/dahdi/tor2.ko /lib/modules/2.6.31-10-generic/dahdi/zaphfc /lib/modules/2.6.31-10-generic/dahdi/zaphfc/zaphfc.ko /lib/modules/2.6.31-10-generic/dahdi/wcopenpci.ko /lib/modules/2.6.31-10-generic/dahdi/voicebus /lib/modules/2.6.31-10-generic/dahdi/voicebus/dahdi_voicebus.ko /lib/modules/2.6.31-10-generic/dahdi/dahdi_echocan_jpah.ko
Izmjenjeno od Ernad Husremović prije više od 15 godina
https://launchpad.net/ubuntu/+source/asterisk/1:1.6.2.0~dfsg~beta4-0ubuntu1
Asterisk is an Open Source PBX and telephony toolkit. It is, in a sense, middleware between Internet and telephony channels on the bottom, and Internet and telephony applications at the top. . Asterisk can be used with Voice over IP (SIP, H.323, IAX and more) standards, or the Public Switched Telephone Network (PSTN) through supported hardware. . Supported hardware: . * All Wildcard (tm) ISDN PRI cards from Digium (http://www.digium.com) * HFC-S/HFC-4S-based ISDN BRI cards (Junghanns.NET, beroNet, Digium etc.) * All TDM (FXO/FXS) cards from Digium * Various clones of Digium cards such as those by OpenVox * Xorcom Astribank USB telephony adapter (http://www.xorcom.com) * Voicetronix OpenPCI, OpenLine and OpenSwitch cards * CAPI-compatible ISDN cards (using the add-on package chan-capi) * Full Duplex Sound Card (ALSA or OSS) supported by Linux * Tormenta T1/E1 card (http://www.zapatatelephony.org) * QuickNet Internet PhoneJack and LineJack (http://www.quicknet.net) . This is the main package that includes the Asterisk daemon and most channel drivers and applications.
Izmjenjeno od Ernad Husremović prije više od 15 godina
Re: [asterisk-dev] BRI support in chan_zap of asterisk 1.6?
Re: [asterisk-dev] BRI support in chan_zap of asterisk 1.6?
Matt Riddell
Mon, 10 Mar 2008 03:49:32 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark Elkins wrote:
On Sun, 2008-03-09 at 17:42 -1000, Jean-Denis Girard wrote:
Matt Riddell a écrit :
Meaning you don't get echo using asterisk-1.6.0, zaptel-1.4,
libpri-trunk, and Junghanns's zaphfc driver (patched with bri_dchan)Yes, exactly, sorry if that was not clear from my previous post. I've
used this setup since, and it works fine, but its just a soho system,
very low volume of calls. I had echo problems with chan_misdn on the
same system. I hope Digium will continue this BRI effort.Just like to add a "Me too"...
I've used a Junghanns card and software patch for years - its always
worked well.When setting up systems for others - its been with a mix of mISDN - etc
- and never been a complete success..I am so looking forward to a consolidated Digium based ISDN BRI
solution. This will be the main reason for me to move to Asterisk 1.6
Indeed. It would prove to be a pretty compelling reason for me to start
testing and rolling some customers over to 1.6
Izmjenjeno od Ernad Husremović prije više od 15 godina
Re: [asterisk-dev] BRI support in chan_zap of asterisk 1.6?
Tzafrir Cohen
Fri, 07 Mar 2008 05:10:02 -0800
On Fri, Mar 07, 2008 at 09:58:33AM +0100, Klaus Darilion wrote:
Tzafrir Cohen schrieb:
On Wed, Mar 05, 2008 at 10:11:44AM -1000, Jean-Denis Girard wrote:
I have an HFC based PCI card connected to telco (TE PTMP), currently
working with chan_misdn. I'd like to test this new implementation, but how?I have downloaded and installed libpri-trunk, zatel-1.4-head. Now which
driver should I use? zaphfc from bristuff doesn't compile, which was
expected as it requires zaptel patches.As I mentioned, you need the bri_dchan patch:
http://updates.xorcom.com/astribank/bristuff/1.4/bristuff-current/patches/zaptel/bri_dchan
Will this patch be integrated in zaptel?
If / when it's author (Klaus-Peter Junghanns) allows it. I don't see
this happening any time soon (nor a change in the need to relicense a
patch before getting it into the main Zaptel tree).
Izmjenjeno od Ernad Husremović prije više od 15 godina
http://osdir.com/ml/telephony.pbx.asterisk.bristuff.user/2008-09/msg00021.html
I have installed Bristuff in dozens of asterisk pbx here in Italy. It
was time ago (2005-2006) and with asterisk 1.0 and 1.2 worked well, no
echo or stability problem. But there was a BIG problem: the d-channel
in PTMP, very often, went down and bristuff was unable to recover. The
problem was caused by the energy saving from the provider, but also
other external things, like a line failure or a cable disconnection.
Only an asterisk restart was able to put the span up.
The first times i had this problem i tried to contact Junghanns to
have support (i buyed from him many cards) but was like to speak to a wall... never a reply.
So i tried misdn and works, but not very well: big echo problem
(solved buying octasic licenses...) and sometimes stability problem
with hfc drivers (kernel panic).
Now that Asterisk 1.6 support BRI i tried again with official beta6
and libpri 1.4.4 and also with bristuff 0.4.0-RC4-xr2 but i see that
the problem it's still here.
I know that i'm not the only person to suffer this problem, in google
you can read hundreds of posts related to this, and also in this list
some time ago a person reported the same
(http://lists.three-dimensional.net/pipermail/bristuff-users/2007-December/000005.html).
I read that other persons suggest to put the line in PTP but in some
configuration this not works, specially when you have a NT from
provider with multi-number.
Misdn have a nice workaround option for this inconvenient:
pmp_l1_check=no
misdn.conf says:
;This option defines, if chan_misdn should check the L1 on a PMP
; before making a group call on it. The L1 may go down for PMP Ports
; so we might need this.
; But be aware! a broken or plugged off cable might be used for a group call
; as well, since chan_misdn has no chance to distinguish if the L1 is down
; because of a lost Link or because the Provider shut it down...
;
; default: no
So, it's possible to modify the bristuff and add a similar option to
force asterisk (chan_dadhi?) to dial also if a span configured in ptmp
is down, like misdn already do?
Thank you
Francesco
Izmjenjeno od Ernad Husremović prije više od 15 godina
VoIP Media Gateway voip-mg¶
The Junghanns .NET Voice over IP Media Gateway (voip-mg) turns all Junghanns.NET ISDN and GSM cards into VoIP enabled devices. The application is based on the existing OpenSource Zaptel and DAHDI drivers and offers for the first time an Asterisk independant solution. The wellknown cards can now be used with virtually any PBX using the SIP or IAX2 protocol (i.e. FreeSwitch, pbxnsip, Yate, Asterisk™ Business Edition® or Microsoft Office Communication Server®, among others) in an easy and convenient fashion. The configuration is done using a functional and clear webinterface which communicates with the HTT P/XML interface of voip-mg.
Manufacturers of VoIP PBXes can use the GPL licenced webinterface as a comfortable and easy first step into integrating the HTT P/XML interface into their own user interface. Voip-mg was designed as a simple media gateway and offers a better performance (less CPU load for the same amount of concurrent calls) compared to Asterisk based systems, because it does not use a complex multithreading PBX core, which makes it also ideally suited for embedded solutions.
- Target Applications SIP Media Gateway
- ISDN Least Cost Routers
- Voice over IP GSM/BRI Gateways
- VoIP Integration of ISDN/GSM devices
- Linux 32bit (glibc, uclibc), x86, mips,
arm, ... - Linux 64bit (glibc, uclibc), amd64,
ia64, ... - Windows 32bit (XP, Vista, Server 2003,
Server 2008) version 1.4, Q4 2009 - Windows 64bit (XP, Vista, Server 2003,
Server 2008) version 1.4, Q4 2009
- GSM, Telephony as well as sending and recieving
SMS via HTT P/XML interface - EuroISDN BRI (S0), TE/NT mode, Point to Point and Point to M ultipoint support (version 1.2)
- EuroISDN PRI (S2M), TE/NT mode (version 1.2)
- SIP (TCP/UDP)
- RTP (g711)
- IAX2
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl voip-mg_1.0.0.tar.gz voip-mg_1.0.0.tar.gz dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Naslov promijenjeno iz dahdi, zaptel, qozap ?! u dahdi, zaptel, qozap, mISDN ?!
mISDN na ast16p3¶
Izmjenjeno od Ernad Husremović prije više od 15 godina
dmesg
[ 7.169196] mISDN: HFC-multi driver 2.03 [ 7.169324] Unknown HFC multiport controller (vendor:1397 device:8b4 subvendor:ffffffff subdevice:ffffffff) <pre>
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl hfc_dahdi.tar.gz hfc_dahdi.tar.gz dodano
duoBRI¶
https://issues.asterisk.org/view.php?id=13897
? file icon hfc4s.diff [^] (2,843 bytes) 2008-11-13 16:17 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=20732&type=bug' -O - | patch -p0 ? file icon wcb4xxp.diff [^] (3,549 bytes) 2008-11-22 14:24 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=20792&type=bug' -O - | patch -p0 ? file icon base.c.patch [^] (8,374 bytes) 2009-02-22 20:52 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21713&type=bug' -O - | patch -p0 ? file icon wcb4xxp.h.patch [^] (424 bytes) 2009-02-22 20:52 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21714&type=bug' -O - | patch -p0 ? file icon base.c.V2.patch [^] (8,421 bytes) 2009-02-22 21:13 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21715&type=bug' -O - | patch -p0 ? file icon patch_b400P [^] (7,727 bytes) 2009-02-24 01:03 ? file icon patch_b400P_2.diff [^] (9,396 bytes) 2009-02-24 13:26 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21735&type=bug' -O - | patch -p0 ? file icon wcb4xxp_b4_variety.diff [^] (10,518 bytes) 2009-02-25 10:01 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21757&type=bug' -O - | patch -p0 ? file icon dahdi_tools.diff [^] (1,264 bytes) 2009-02-25 10:02 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21759&type=bug' -O - | patch -p0 ? file icon wcb4xxp_v5.diff [^] (13,559 bytes) 2009-03-03 16:04 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21842&type=bug' -O - | patch -p0 ? file icon HFC-8S.diff [^] (17,221 bytes) 2009-03-06 20:56 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21874&type=bug' -O - | patch -p0 ? file icon dahdi-linux-2.1.0.4.diff [^] (19,479 bytes) 2009-03-09 20:14 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21900&type=bug' -O - | patch -p0 ? file icon dahdi-tools-2.1.0.2.diff [^] (1,788 bytes) 2009-03-09 20:15 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21901&type=bug' -O - | patch -p0 ? file icon wcb4xxp_extracards.diff [^] (17,304 bytes) 2009-03-15 14:21 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21955&type=bug' -O - | patch -p0 ? file icon wcb4xxp_extracards_leds_fixes.diff [^] (17,008 bytes) 2009-03-16 10:51 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21961&type=bug' -O - | patch -p0 ? file icon wcb4xxp_extracards_2.diff [^] (17,447 bytes) 2009-03-17 11:17 [wget patch] [License OK (v3.0)] wget 'https://issues.asterisk.org/file_download.php?file_id=21977&type=bug' -O - | patch -p0 ? file icon wcb4xxp_extra_cards_dahdi-tools.diff [^] (2,494 bytes) 2009-03-19 06:35 [wget patch] [License OK (v3.0)]
Izmjenjeno od Ernad Husremović prije više od 15 godina
http://www.trixbox.org/forums/trixbox-forums/trunks/tb2-0-duobri (05/2007)
priča o detekciji ove kartice od strane zaptel/bristuff
Izmjenjeno od Ernad Husremović prije više od 15 godina
dahdi karmic source u git¶
bringout@nmraka-2:~/devel/junghanns.net$ apt-get source dahdi-source Čitam spiskove paketa... Done Gradim stablo zavisnosti Reading state information... Done NOTICE: 'dahdi-linux' packaging is maintained in the 'Bzr' version control system at: http://launchpad.net/~ubuntu-voip/ubuntu-voip/dahdi-linux/ Please use: bzr get http://launchpad.net/~ubuntu-voip/ubuntu-voip/dahdi-linux/ to retrieve the latest (possible unreleased) updates to the package. Need to get 1518kB of source archives. Get:1 http://archive.sigma-com.net karmic/universe dahdi-linux 1:2.2.0.2~dfsg-1ubuntu2 (dsc) [1319B] Get:2 http://archive.sigma-com.net karmic/universe dahdi-linux 1:2.2.0.2~dfsg-1ubuntu2 (tar) [1372kB] Get:3 http://archive.sigma-com.net karmic/universe dahdi-linux 1:2.2.0.2~dfsg-1ubuntu2 (diff) [145kB] Fetched 1518kB in 3s (413kB/s) gpgv: Signature made Pon 14 Sep 2009 23:07:01 CEST using DSA key ID 403BDD8B gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./dahdi-linux_2.2.0.2~dfsg-1ubuntu2.dsc dpkg-source: info: extracting dahdi-linux in dahdi-linux-2.2.0.2~dfsg dpkg-source: info: unpacking dahdi-linux_2.2.0.2~dfsg.orig.tar.gz dpkg-source: info: applying dahdi-linux_2.2.0.2~dfsg-1ubuntu2.diff.gz bringout@nmraka-2:~/devel/junghanns.net$ cd dahdi-linux-2.2.0.2~dfsg/ bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ ls build_tools debian drivers LICENSE Makefile UPGRADE.txt ChangeLog doc include LICENSE.LGPL README bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ git init Initialized empty Git repository in /home/bringout/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg/.git/ bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ git add \* bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ git commit -a -m "dahdi-linux-2.2.0.2~dfsg" [master (root-commit) 84108bf] dahdi-linux-2.2.0.2~dfsg 317 files changed, 206627 insertions(+), 0 deletions(-) create mode 100644 .version ...
Izmjenjeno od Ernad Husremović prije više od 15 godina
merge dahdi-linux dahdi-tools¶
bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg/drivers/dahdi/wcb4xxp$ patch -p0 < ~/Desktop/hfc_dahdi/base.c.V2.patch
patching file base.c Hunk #1 succeeded at 114 with fuzz 2 (offset 4 lines). Hunk #2 succeeded at 625 (offset 18 lines). Hunk #3 succeeded at 653 (offset 18 lines). Hunk #4 succeeded at 891 (offset 18 lines). Hunk #5 succeeded at 1221 (offset 18 lines). Hunk #6 succeeded at 1424 (offset 19 lines). Hunk #7 succeeded at 1794 (offset 19 lines). Hunk #8 succeeded at 1819 (offset 19 lines). Hunk #9 succeeded at 1870 (offset 19 lines). Hunk #10 succeeded at 1885 (offset 19 lines). Hunk #11 FAILED at 2004. Hunk #12 FAILED at 2261. Hunk #13 succeeded at 2528 (offset 36 lines). Hunk #14 succeeded at 2628 (offset 41 lines). Hunk #15 succeeded at 2658 (offset 41 lines). Hunk #16 succeeded at 2812 (offset 46 lines). Hunk #17 succeeded at 2877 (offset 47 lines). 2 out of 17 hunks FAILED -- saving rejects to file base.c.rej
Izmjenjeno od Ernad Husremović prije više od 15 godina
bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ patch -p4 < ~/Desktop/hfc_dahdi/dahdi-linux-2.1.0.4.diff
patching file drivers/dahdi/wcb4xxp/base.c Hunk #2 FAILED at 110. Hunk #3 succeeded at 421 (offset 25 lines). Hunk #4 FAILED at 643. Hunk #5 succeeded at 1040 (offset 29 lines). Hunk #6 FAILED at 1250. Hunk #7 FAILED at 1452. Hunk #8 FAILED at 1822. Hunk #9 succeeded at 1869 (offset 37 lines). Hunk #10 succeeded at 1884 (offset 37 lines). Hunk #11 succeeded at 1938 with fuzz 1 (offset 38 lines). Hunk #12 succeeded at 2177 with fuzz 2 (offset 121 lines). Hunk #13 FAILED at 2475. Hunk #14 succeeded at 2599 (offset 138 lines). Hunk #15 succeeded at 2625 (offset 138 lines). Hunk #16 succeeded at 2634 (offset 138 lines). Hunk #17 succeeded at 2643 (offset 138 lines). Hunk #18 succeeded at 2651 (offset 138 lines). Hunk #19 succeeded at 2733 (offset 138 lines). Hunk #20 succeeded at 2744 (offset 138 lines). Hunk #21 FAILED at 2753. Hunk #22 FAILED at 2848. Hunk #23 succeeded at 2869 (offset 144 lines). Hunk #24 FAILED at 2884. Hunk #25 FAILED at 3032. Hunk #26 FAILED at 3101. 11 out of 26 hunks FAILED -- saving rejects to file drivers/dahdi/wcb4xxp/base.c.rej patching file drivers/dahdi/wcb4xxp/wcb4xxp.h Hunk #2 succeeded at 415 (offset 1 line). Hunk #3 succeeded at 462 (offset 1 line).
Izmjenjeno od Ernad Husremović prije više od 15 godina
dahdi tools patch
bringout@nmraka-2:~/devel/junghanns.net/dahdi-tools-2.2.0$ patch -p4 < ~/Desktop/hfc_dahdi/dahdi-tools-2.1.0.2.diff
patching file xpp/perl_modules/Dahdi/Hardware/PCI.pm Hunk #1 succeeded at 95 with fuzz 1.
Izmjenjeno od Ernad Husremović prije više od 15 godina
gitorious dahdi-linux¶
bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ git remote add origin git@gitorious.bring.out.ba:asterisk/dahdi-linux.git bringout@nmraka-2:~/devel/junghanns.net/dahdi-linux-2.2.0.2~dfsg$ git push origin master Counting objects: 355, done. Delta compression using up to 2 threads. Compressing objects: 100% (341/341), done. Writing objects: 100% (355/355), 1.58 MiB | 2170 KiB/s, done. Total 355 (delta 58), reused 0 (delta 0) => Syncing Gitorious... [OK] To git@gitorious.bring.out.ba:asterisk/dahdi-linux.git * [new branch] master -> master
Izmjenjeno od Ernad Husremović prije više od 15 godina
gitorious dahdi-tools¶
bringout@nmraka-2:~/devel/junghanns.net/dahdi-tools-2.2.0$ git push origin master
Counting objects: 229, done. Delta compression using up to 2 threads. Compressing objects: 100% (220/220), done. Writing objects: 100% (229/229), 479.93 KiB, done. Total 229 (delta 25), reused 0 (delta 0) => Syncing Gitorious... [OK] To git@gitorious.bring.out.ba:asterisk/dahdi-tools.git * [new branch] master -> master
Izmjenjeno od Ernad Husremović prije više od 15 godina
gitorious asterisk¶
bringout@nmraka-2:~/devel/junghanns.net/asterisk-1.6.2.0~rc2$ git commit -a -m "ubuntu asterisk-1.6.2.0~rc2"
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/asterisk# git clone git://gitorious.bring.out.ba/asterisk/dahdi-linux.git
root@ast16p3:~/asterisk/dahdi-linux# dpkg-buildpackage
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/asterisk# sudo dpkg -i *deb
(Reading database ... 98392 files and directories currently installed.) Preparing to replace dahdi-dkms 1:2.2.0.2~dfsg-1ubuntu3 (using dahdi-dkms_2.2.0.2~dfsg-1ubuntu3_all.deb) ... Removing all DKMS Modules Done. Unpacking replacement dahdi-dkms ... Preparing to replace dahdi-linux 1:2.2.0.2~dfsg-1ubuntu3 (using dahdi-linux_2.2.0.2~dfsg-1ubuntu3_all.deb) ... Unpacking replacement dahdi-linux ... Preparing to replace dahdi-source 1:2.2.0.2~dfsg-1ubuntu3 (using dahdi-source_2.2.0.2~dfsg-1ubuntu3_all.deb) ... Unpacking replacement dahdi-source ... Setting up dahdi-dkms (1:2.2.0.2~dfsg-1ubuntu3) ... Loading new dahdi-2.2.0.2 DKMS files... Building for architecture i686 Building initial module for 2.6.31-11-generic Done. dahdi.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_dummy.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_dynamic.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_dynamic_eth.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_dynamic_loc.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_echocan_jpah.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_echocan_kb1.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_echocan_mg2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_echocan_sec.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_echocan_sec2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_transcode.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ pciradio.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ tor2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wcb4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wcfxo.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wct1xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wct4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wctc4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wctdm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wctdm24xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wcte11xp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ wcte12xp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpd_fxo.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpd_fxs.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpd_pri.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpp_usb.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ xpd_bri.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_voicebus.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ echo.ko: Running module version sanity check. Error! Module version 0.3.0 for echo.ko is not newer than what is already found in kernel 2.6.31-11-generic (0.3.0). You may override by specifying --force. dahdi_echocan_oslec.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ dahdi_vpmadt032_loader.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.31-11-generic/updates/dkms/ depmod.......... DKMS: install Completed. Setting up dahdi-linux (1:2.2.0.2~dfsg-1ubuntu3) ... Setting up dahdi-source (1:2.2.0.2~dfsg-1ubuntu3) ... Processing triggers for doc-base ... Processing 1 changed doc-base file(s)...
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/asterisk# modprobe wcb4xxp
[43089.521337] wcb4xxp 0000:01:0b.0: probe called for b4xx... [43089.521401] wcb4xxp 0000:01:0b.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 [43089.521627] wcb4xxp 0000:01:0b.0: Identified HFC-2S Junghanns.NET duoBRI PCI (controller rev 1) at 00011090, IRQ 11 [43089.523066] IRQ 11/b4xxp: IRQF_DISABLED is not guaranteed on shared IRQs [43089.523101] wcb4xxp 0000:01:0b.0: NOTE: hardware echo cancellation has been disabled [43089.523192] wcb4xxp 0000:01:0b.0: Port 1: NT mode [43089.523316] wcb4xxp 0000:01:0b.0: Port 2: NT mode [43089.544773] wcb4xxp 0000:01:0b.0: Did not do the highestorder stuff [43089.644760] wcb4xxp 0000:01:0b.0: new card sync source: port 3
root@ast16p3:~/asterisk# cat /proc/dahdi/1
Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
1 B4/0/1/1
2 B4/0/1/2
3 B4/0/1/3
root@ast16p3:~/asterisk# cat /proc/dahdi/2
Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" RED
4 B4/0/2/1 YELLOW
5 B4/0/2/2 YELLOW
6 B4/0/2/3 YELLOW
Izmjenjeno od Ernad Husremović prije više od 15 godina
kada se prikopča kabl na tom spanu se prijavljuje HDLC bad:
[Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 .. [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:39] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:40] WARNING[1253] chan_dahdi.c: Detected alarm on channel 1: Yellow Alarm [Sep 29 08:29:40] WARNING[1253] chan_dahdi.c: Detected alarm on channel 2: Yellow Alarm [Sep 29 08:29:40] NOTICE[1251] chan_dahdi.c: PRI got event: Alarm (4) on Primary D-channel of span 1 [Sep 29 08:29:41] NOTICE[1253] chan_dahdi.c: Alarm cleared on channel 1 [Sep 29 08:29:41] NOTICE[1253] chan_dahdi.c: Alarm cleared on channel 2 [Sep 29 08:29:41] NOTICE[1251] chan_dahdi.c: PRI got event: No more alarm (5) on Primary D-channel of span 1 [Sep 29 08:29:41] NOTICE[1251] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Sep 29 08:29:42] WARNING[1253] chan_dahdi.c: Detected alarm on channel 1: Yellow Alarm [Sep 29 08:29:42] WARNING[1253] chan_dahdi.c: Detected alarm on channel 2: Yellow Alarm [Sep 29 08:29:42] NOTICE[1251] chan_dahdi.c: PRI got event: Alarm (4) on Primary D-channel of span 1
YELLOW stanje je kada kabl nije prikopčan na span
bitno je da isdn uopšte ne radi (ni na ifold-u) kada se prikopča kabl na duoBRI karticu
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~# lspci -vv | egrep "(^0|Latency)"
00:00.0 Host bridge: Intel Corporation 82810E DC-133 (GMCH) Graphics Memory Controller Hub (rev 03)
Latency: 0
00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133 (CGC) Chipset Graphics Controller (rev 03)
Latency: 0
00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02)
Latency: 0
00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02)
Latency: 0
00:1f.1 IDE interface: Intel Corporation 82801AA IDE Controller (rev 02) (prog-if 80 [Master])
Latency: 0
00:1f.2 USB Controller: Intel Corporation 82801AA USB Controller (rev 02)
Latency: 0
00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 02)
Latency: 0
01:08.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
Latency: 16 (4000ns max)
01:09.0 Network controller: ASUSTeK Computer Inc. ISDNLink P-IN100-ST-D (rev 02)
Latency: 16 (4000ns max)
01:0a.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
Latency: 64 (2500ns min, 2500ns max), Cache Line Size: 32 bytes
01:0b.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
Izmjenjeno od Ernad Husremović prije više od 15 godina
http://www.cadvision.com/blanchas/Asterisk/ZaptelPerformanceTesting.html
Solution
The solution is not that easy anymore, here's some suggestions:- Disable onboard peripherals and interfaces that are not used by the server: USB ports, serial ports, sound card, floppy drive, parallel port, etc.. This will free up some IRQs and may fix your IRQ sharing problem.
- Some motherboards have a bios that allows you to set the IRQs for each PCI slot. Take the bios setting for the PCI bus off of automatic and manually set the IRQs. This was common with older motherboards. Newer motherboards it is not so common.
- Turn off the PC and move the zaptel cards to different PCI slots. Reboot and test. You may have to fiddle around with the order of cards in the PCI slots to find the "right" order where there are no IRQ sharing.
- You can give the zaptel cards a higher priority by changing the PCI latency for it. I haven't tried it yet, here is how you would change it: the Linux hardware stability guide, Part 2: Drivers, IRQs, and PCI latency
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/asterisk# cat /proc/interrupts
CPU0
0: 3538467 XT-PIC-XT timer
1: 12 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
6: 3 XT-PIC-XT floppy
8: 0 XT-PIC-XT rtc0
9: 0 XT-PIC-XT acpi
11: 57822988 XT-PIC-XT uhci_hcd:usb1, eth0, b4xxp
12: 4 XT-PIC-XT i8042
14: 47333 XT-PIC-XT ata_piix
15: 0 XT-PIC-XT ata_piix
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
SPU: 0 Spurious interrupts
CNT: 0 Performance counter interrupts
PND: 0 Performance pending work
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
ERR: 0
MIS: 0
Izmjenjeno od Ernad Husremović prije više od 15 godina
bristuff novi 0.4.0 rc3h na ast16p3¶
root@ast16p3:~/bristuff# wget http://www.junghanns.net/downloads/bristuff-0.4.0-RC3h.tar.gz
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:/etc# tar cvfz asterisk16.tar.gz asterisk
root@ast16p3:/etc# sudo apt-get remove asterisk dahdi
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h# ./install.sh
--2009-10-02 11:39:28-- http://downloads.digium.com/pub/zaptel/releases/zaptel-1.4.12.1.tar.gz Resolving downloads.digium.com... 76.164.171.232 Connecting to downloads.digium.com|76.164.171.232|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://downloads.asterisk.org/pub/telephony/zaptel/releases/zaptel-1.4.12.1.tar.gz [following] --2009-10-02 11:39:29-- http://downloads.asterisk.org/pub/telephony/zaptel/releases/zaptel-1.4.12.1.tar.gz Resolving downloads.asterisk.org... 76.164.171.233 Connecting to downloads.asterisk.org|76.164.171.233|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1706625 (1,6M) [application/x-gzip] Saving to: `zaptel-1.4.12.1.tar.gz' 100%[======================================>] 1.706.625 162K/s in 15s 2009-10-02 11:39:44 (112 KB/s) - `zaptel-1.4.12.1.tar.gz' saved [1706625/1706625] --2009-10-02 11:39:44-- http://downloads.digium.com/pub/libpri/releases/libpri-1.4.3.tar.gz Resolving downloads.digium.com... 76.164.171.232 Connecting to downloads.digium.com|76.164.171.232|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://downloads.asterisk.org/pub/telephony/libpri/releases/libpri-1.4.3.tar.gz [following] --2009-10-02 11:39:45-- http://downloads.asterisk.org/pub/telephony/libpri/releases/libpri-1.4.3.tar.gz Resolving downloads.asterisk.org... 76.164.171.233 Connecting to downloads.asterisk.org|76.164.171.233|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 81741 (80K) [application/x-gzip] Saving to: `libpri-1.4.3.tar.gz' 100%[======================================>] 81.741 84,1K/s in 0,9s 2009-10-02 11:39:46 (84,1 KB/s) - `libpri-1.4.3.tar.gz' saved [81741/81741] --2009-10-02 11:39:46-- http://downloads.digium.com/pub/asterisk/releases/asterisk-1.4.26.2.tar.gz Resolving downloads.digium.com... 76.164.171.232 Connecting to downloads.digium.com|76.164.171.232|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-1.4.26.2.tar.gz [following] --2009-10-02 11:39:46-- http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-1.4.26.2.tar.gz Resolving downloads.asterisk.org... 76.164.171.233 Connecting to downloads.asterisk.org|76.164.171.233|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21436723 (20M) [application/x-gzip] Saving to: `asterisk-1.4.26.2.tar.gz'
Izmjenjeno od Ernad Husremović prije više od 15 godina
poznati error
/root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1/kernel/ztdummy.c: In function ‘ztdummy_hr_int’: /root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1/kernel/ztdummy.c:202: error: ‘struct hrtimer’ has no member named ‘expires’ make[3]: *** [/root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1/kernel/ztdummy.o] Error 1 make[2]: *** [_module_/root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1/kernel] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-11-generic' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1' make: *** [all] Error 2
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h# cd zaptel root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h/zaptel# vi hrtimer.patch root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h/zaptel# patch -p1 < hrtimer.patch patching file kernel/ztdummy.c Hunk #1 succeeded at 90 with fuzz 2 (offset -1 lines). Hunk #2 FAILED at 211. Hunk #3 FAILED at 234. 2 out of 3 hunks FAILED -- saving rejects to file kernel/ztdummy.c.rej
Izmjenjeno od Ernad Husremović prije više od 15 godina
sljedeća greška kod pokušaja compile-a
/root/bristuff/bristuff-0.4.0-RC3h/zaptel-1.4.12.1/kernel/wctc4xxp/base.c:611: error: ‘struct net_device’ has no member named ‘priv pa se ovo 5-10 puta ponavlja...
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h/zaptel/Makefile izmjenio:
SUBDIR_MODULES:=
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h# cat patches/zaptel/120-exclude-modules.diff
diff --git a/zaptel/Makefile.orig b/zaptel/Makefile index f905dc9..6d98a23 100644 --- zaptel.orig/Makefile +++ zaptel/Makefile @@ -126,8 +126,8 @@ ifeq ($(BUILD_XPP),yes) endif #SUBDIRS_UTILS += ppp -TOPDIR_MODULES:=pciradio tor2 torisa wcfxo wct1xxp wctdm wcte11xp wcusb zaptel ztd-eth ztd-loc ztdummy ztdynamic zttranscode -SUBDIR_MODULES:=wct4xxp wctc4xxp xpp wctdm24xxp wcte12xp +TOPDIR_MODULES:=pciradio tor2 torisa wcfxo wct1xxp wctdm wcte11xp wcusb zaptel ztd-eth ztd-loc ztdynamic zttranscode +SUBDIR_MODULES:= TOPDIR_MODULES+=$(MODULES_EXTRA) SUBDIR_MODULES+=$(SUBDIRS_EXTRA) BUILD_TOPDIR_MODULES:=$(filter-out $(MENUSELECT_MODULES),$(TOPDIR_MODULES))
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h# tail patches/zaptel/series
... 100-bri_dchan.diff 101-proc_read.diff 102-zt_alarm_notify_no_master_change.diff 103-ztcfg-start_stop.diff 104-ztpty.diff 120-exclude-modules.diff
Izmjenjeno od Ernad Husremović prije više od 15 godina
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/bristuff/bristuff-0.4.0-RC3h# sudo apt-get remove dahdi-source dahdi-dkms
Čitam spiskove paketa... Done Gradim stablo zavisnosti Reading state information... Done Slijedeći paketi će biti UKLONJENI: dahdi-dkms dahdi-linux dahdi-source 0 upgraded, 0 newly installed, 3 to remove and 18 not upgraded. After this operation, 9290kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 97955 files and directories currently installed.) Removing dahdi-linux ... Removing dahdi-dkms ... Removing all DKMS Modules
Izmjenjeno od Ernad Husremović prije više od 15 godina
[ 5188.001284] Zapata Telephony Interface Registered on major 196 [ 5188.001301] Zaptel Version: 1.4.12.1 [ 5188.001308] Zaptel Echo Canceller: MG2 [ 5200.088512] pci 0000:01:09.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 [ 5200.088931] qozap: Starting hardware watchdog. [ 5200.088947] qozap: Junghanns.NET duoBRI card configured at io port 0x1088 IRQ 11 HZ 250 CardID 0 [ 5200.088959] qozap: S/T ports: 2 [ TE TE ] [ 5200.110088] qozap: 1 multiBRI card(s) in this box, 2 BRI ports total, bloop 0, pcmslave 0, dacs 1.
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:/lib/modules/2.6.31-11-generic/misc# genzaptelconf -vvvvv
Generating '/etc/zaptel.conf and /etc/asterisk/zapata-channels.conf' Note: generated /etc/asterisk/zapata-channels.conf not included in zapata.conf To fix: echo '#include zapata-channels.conf' >>/etc/asterisk/zapata.conf Reconfiguring identified channels Zaptel Version: 1.4.12.1 Echo Canceller: MG2 Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 3: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Slaves: 01) Channel 02: Clear channel (Default) (Slaves: 02) Channel 03: D-channel (Default) (Slaves: 03) Channel 04: Clear channel (Default) (Slaves: 04) Channel 05: Clear channel (Default) (Slaves: 05) Channel 06: D-channel (Default) (Slaves: 06) Channel 07: Clear channel (Default) (Slaves: 07) Channel 08: Clear channel (Default) (Slaves: 08) Channel 09: D-channel (Default) (Slaves: 09) 9 channels to configure.
isključiću zaphfc
root@ast16p3:/lib/modules/2.6.31-11-generic/misc# modprobe -r zaphfc
root@ast16p3:/lib/modules/2.6.31-11-generic/misc# lsmod
Module Size Used by qozap 26176 0 zaptel 196068 3 qozap crc_ccitt 1852 1 zaptel psmouse 56180 0 serio_raw 5280 0 intel_rng 4444 0 intel_agp 26684 1 lp 8964 0 shpchp 32272 0 agpgart 34988 1 intel_agp parport 35340 1 lp 3c59x 37604 0 mii 5212 1 3c59x
root@ast16p3:/lib/modules/2.6.31-11-generic/misc# genzaptelconf -vvvvv
Generating '/etc/zaptel.conf and /etc/asterisk/zapata-channels.conf' Note: generated /etc/asterisk/zapata-channels.conf not included in zapata.conf To fix: echo '#include zapata-channels.conf' >>/etc/asterisk/zapata.conf Reconfiguring identified channels Zaptel Version: 1.4.12.1 Echo Canceller: MG2 Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Slaves: 01) Channel 02: Clear channel (Default) (Slaves: 02) Channel 03: D-channel (Default) (Slaves: 03) Channel 04: Clear channel (Default) (Slaves: 04) Channel 05: Clear channel (Default) (Slaves: 05) Channel 06: D-channel (Default) (Slaves: 06) 6 channels to configure.
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:/lib/modules/2.6.31-11-generic/misc# ztcfg -vv
Zaptel Version: 1.4.12.1 Echo Canceller: MG2 Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Slaves: 01) Channel 02: Clear channel (Default) (Slaves: 02) Channel 03: D-channel (Default) (Slaves: 03) Channel 04: Clear channel (Default) (Slaves: 04) Channel 05: Clear channel (Default) (Slaves: 05) Channel 06: D-channel (Default) (Slaves: 06) 6 channels to configure.
Izmjenjeno od Ernad Husremović prije više od 15 godina
== Parsing '/etc/asterisk/zapata.conf': Found [Oct 3 14:43:13] WARNING[15574]: config.c:769 process_text_line: parse error: No category context for line 3 of /etc/asterisk/zapata.conf [Oct 3 14:43:13] ERROR[15574]: chan_dahdi.c:13676 setup_dahdi: Unable to load zapata.conf
;#include /etc/asterisk/zapata-channels.conf context=in switchtype = euroisdn signalling = bri_cpe_ptmp channel => 1-2 group=1 context=default
Izmjenjeno od Ernad Husremović prije više od 15 godina
ovo je falilo
[channels] <<<<<<<<<<<< ;#include /etc/asterisk/zapata-channels.conf group=1 context=bringoutba switchtype = euroisdn signalling = bri_cpe_ptmp channel => 1-2 group=1 context=default
Izmjenjeno od Ernad Husremović prije više od 15 godina
zaptel init.d skripta problem
zaptel start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5) ...
bringout@nmraka-2:~$ sudo apt-get install insserv graphviz
Izmjenjeno od Ernad Husremović prije više od 15 godina
error: Unable to read /etc/rc2.d/S15dahdi at /usr/share/insserv/check-initd-order line 380.
error: LSB header missing in /etc/rc2.d/S15dahdi error: LSB header missing in /etc/rc2.d/S21asterisk
root@ast16p3:/etc/init.d# rm /etc/rc*/*dahdi
Izmjenjeno od Ernad Husremović prije više od 15 godina
checko boot order¶
root@ast16p3:~# /usr/share/insserv/check-initd-order -g > boot.dot
.. "zaptel" -> "asterisk"[color=blue] ; ...
Izmjenjeno od Ernad Husremović prije više od 15 godina
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/voip-mg_1.0.0# ls patches-zaptel-1.4/zaptel
100-bri_dchan.diff 102-zt_alarm_notify_no_master_change.diff 104-ztpty.diff 101-proc_read.diff 103-ztcfg-start_stop.diff series
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/voip-mg_1.0.0/zaptel/kernel# diff -u ztdummy.c ztdummy.c.orig > ztdummy.diff
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl 120-hrtimer.diff dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl 120-hrtimer.diff 120-hrtimer.diff dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl obrisano (
120-hrtimer.diff)
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl 120-hrtimer.diff dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl 120-hrtimer.diff 120-hrtimer.diff dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl obrisano (
120-hrtimer.diff)
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl obrisano (
hrtimer.patch)
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl 121-exclude-subdir-modules.diff 121-exclude-subdir-modules.diff dodano
- Fajl series series dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Fajl voipmg_manual.pdf voipmg_manual.pdf dodano
Izmjenjeno od Ernad Husremović prije više od 15 godina
sa ova dva patch-a sam uspio instalirati voip-mg
root@ast16p3:~/voip-mg_1.0.0# ./install-zaptel-1.4.sh
...
make[2]: Leaving directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/xpp/utils'
make[1]: Leaving directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1'
install -d /etc/udev/rules.d
build_tools/genudevrules > /etc/udev/rules.d/zaptel.rules
build_tools/genudevrules: 3: udevinfo: not found
build_tools/uninstall-modules dahdi 2.6.31-11-generic
make -C /lib/modules/2.6.31-11-generic/build ARCH=i386 SUBDIRS=/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o tor2.o torisa.o wcfxo.o wct1xxp.o wctdm.o wcte11xp.o wcusb.o zaptel.o ztd-eth.o ztd-loc.o ztdynamic.o zttranscode.o cwain.o qozap.o zaphfc.o ztgsm.o " INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-11-generic'
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/cwain.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/pciradio.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/qozap.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/tor2.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/torisa.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/wcfxo.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/wct1xxp.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/wctdm.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/wcte11xp.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/wcusb.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/zaphfc.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/zaptel.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/ztd-eth.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/ztd-loc.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/ztdynamic.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/ztgsm.ko
INSTALL /root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/zttranscode.ko
DEPMOD 2.6.31-11-generic
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-11-generic'
[ `id -u` = 0 ] && /sbin/depmod -a 2.6.31-11-generic || :
make[1]: Entering directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/xpp/utils'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/xpp/utils'
make[1]: Entering directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/xpp/utils'
install -d /usr/sbin
install genzaptelconf fpga_load zt_registration xpp_sync lszaptel xpp_blink zapconf zaptel_hardware /usr/sbin/
install -d /usr/share/zaptel
install -m 644 ../firmwares/FPGA_1141.hex ../firmwares/FPGA_1151.hex ../firmwares/FPGA_FXS.hex ../firmwares/USB_FW.hex init_fxo_modes /usr/share/zaptel/
install ../init_card_1_30 ../init_card_2_30 ../init_card_3_30 ../init_card_4_30 xpp_fxloader /usr/share/zaptel/
install -d /usr/share/man/man8
install -m 644 genzaptelconf.8 fpga_load.8 zt_registration.8 xpp_sync.8 lszaptel.8 xpp_blink.8 zapconf.8 zaptel_hardware.8 /usr/share/man/man8/
install -d /etc/hotplug/usb
install -m 644 xpp_fxloader.usermap /etc/hotplug/usb/
# for backward compatibility and for hotplug users:
ln -sf /usr/share/zaptel/xpp_fxloader /etc/hotplug/usb/
install -d /etc/udev/rules.d
install -m 644 xpp.rules /etc/udev/rules.d/
install -d /usr/local/share/perl/5.10.0
for i in Zaptel Zaptel/Config Zaptel/Hardware Zaptel/Xpp; \
do \
install -d "/usr/local/share/perl/5.10.0/$i"; \
done
for i in Zaptel.pm Zaptel/Chans.pm Zaptel/Hardware.pm Zaptel/Span.pm Zaptel/Utils.pm Zaptel/Xpp.pm Zaptel/Config/Defaults.pm Zaptel/Hardware/PCI.pm Zaptel/Hardware/USB.pm Zaptel/Xpp/Line.pm Zaptel/Xpp/Xbus.pm Zaptel/Xpp/Xpd.pm; \
do \
install -m 644 "zconf/$i" "/usr/local/share/perl/5.10.0/$i"; \
done
make[1]: Leaving directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/kernel/xpp/utils'
install -d /sbin
install fxotune ztcfg ztmonitor ztspeed zttest ztscan zttool /sbin/
install -d /usr/share/man/man8
install -m 644 doc/fxotune.8 doc/ztcfg.8 doc/ztmonitor.8 doc/ztspeed.8 doc/zttest.8 doc/ztscan.8 doc/zttool.8 /usr/share/man/man8/
/usr/bin/install -c -D -m 755 libtonezone.a /usr/lib/libtonezone.a
/usr/bin/install -c -D -m 755 libtonezone.so /usr/lib/libtonezone.so.1.0
if [ `id -u` = 0 ]; then \
/sbin/ldconfig || : ;\
fi
rm -f /usr/liblibtonezone.so
/bin/ln -sf libtonezone.so.1.0 \
/usr/lib/libtonezone.so.1
/bin/ln -sf libtonezone.so.1.0 \
/usr/lib/libtonezone.so
/usr/bin/install -c -D -m 644 kernel/zaptel.h /usr/include/zaptel/zaptel.h
/usr/bin/install -c -D -m 644 tonezone.h /usr/include/zaptel/tonezone.h
make -C firmware hotplug-install DESTDIR= HOTPLUG_FIRMWARE=yes
make[1]: Entering directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/firmware'
Attempting to download zaptel-fw-oct6114-064-1.05.01.tar.gz
--2009-10-05 18:31:15-- http://downloads.digium.com/pub/telephony/firmware/releases/zaptel-fw-oct6114-064-1.05.01.tar.gz
Resolving downloads.digium.com... 76.164.171.232
Connecting to downloads.digium.com|76.164.171.232|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165865 (162K) [application/x-gzip]
Saving to: `zaptel-fw-oct6114-064-1.05.01.tar.gz'
100%[======================================>] 165.865 104K/s in 1,6s
2009-10-05 18:31:17 (104 KB/s) - `zaptel-fw-oct6114-064-1.05.01.tar.gz' saved [165865/165865]
Attempting to download zaptel-fw-oct6114-128-1.05.01.tar.gz
--2009-10-05 18:31:17-- http://downloads.digium.com/pub/telephony/firmware/releases/zaptel-fw-oct6114-128-1.05.01.tar.gz
Resolving downloads.digium.com... 76.164.171.232
Connecting to downloads.digium.com|76.164.171.232|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165847 (162K) [application/x-gzip]
Saving to: `zaptel-fw-oct6114-128-1.05.01.tar.gz'
100%[======================================>] 165.847 109K/s in 1,5s
2009-10-05 18:31:19 (109 KB/s) - `zaptel-fw-oct6114-128-1.05.01.tar.gz' saved [165847/165847]
Attempting to download zaptel-fw-tc400m-MR6.12.tar.gz
--2009-10-05 18:31:19-- http://downloads.digium.com/pub/telephony/firmware/releases/zaptel-fw-tc400m-MR6.12.tar.gz
Resolving downloads.digium.com... 76.164.171.232
Connecting to downloads.digium.com|76.164.171.232|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1750026 (1,7M) [application/x-gzip]
Saving to: `zaptel-fw-tc400m-MR6.12.tar.gz'
100%[======================================>] 1.750.026 107K/s in 18s
2009-10-05 18:31:37 (97,3 KB/s) - `zaptel-fw-tc400m-MR6.12.tar.gz' saved [1750026/1750026]
Attempting to download zaptel-fw-vpmadt032-1.07.tar.gz
--2009-10-05 18:31:37-- http://downloads.digium.com/pub/telephony/firmware/releases/zaptel-fw-vpmadt032-1.07.tar.gz
Resolving downloads.digium.com... 76.164.171.232
Connecting to downloads.digium.com|76.164.171.232|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41375 (40K) [application/x-gzip]
Saving to: `zaptel-fw-vpmadt032-1.07.tar.gz'
100%[======================================>] 41.375 65,7K/s in 0,6s
2009-10-05 18:31:38 (65,7 KB/s) - `zaptel-fw-vpmadt032-1.07.tar.gz' saved [41375/41375]
Firmware zaptel-fw-oct6114-064.bin is already installed with required version 1.05.01
Firmware zaptel-fw-oct6114-128.bin is already installed with required version 1.05.01
Firmware zaptel-fw-tc400m.bin is already installed with required version MR6.12
Firmware zaptel-fw-vpmadt032.bin is already installed with required version 1.07
make[1]: Leaving directory `/root/voip-mg_1.0.0/zaptel-1.4.12.1/firmware'
###################################################
###
### Zaptel installed successfully.
### If you have not done so before, install init scripts with:
###
### make config
###
###################################################
ZAPTEL installed
Installing voip-mg 32bit version
Installing default configuration (webinterface on port 18080)
Installing webinterface
Installation finished
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/voip-mg_1.0.0# modprobe qozap root@ast16p3:~/voip-mg_1.0.0# ztcfg -vvvv Zaptel Version: 1.4.12.1 Echo Canceller: MG2 Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Slaves: 01) Channel 02: Clear channel (Default) (Slaves: 02) Channel 03: D-channel (Default) (Slaves: 03) Channel 04: Clear channel (Default) (Slaves: 04) Channel 05: Clear channel (Default) (Slaves: 05) Channel 06: D-channel (Default) (Slaves: 06) 6 channels to configure. Changing signalling on channel 1 from Unused to Clear channel Changing signalling on channel 2 from Unused to Clear channel Changing signalling on channel 3 from Unused to HDLC with FCS check Changing signalling on channel 4 from Unused to Clear channel Changing signalling on channel 5 from Unused to Clear channel Changing signalling on channel 6 from Unused to HDLC with FCS check
Izmjenjeno od Ernad Husremović prije više od 15 godina
init.d voip-mg¶
root@ast16p3:~/voip-mg_1.0.0# cp rc.voip-mg /etc/init.d/voip-mg
root@ast16p3:~/voip-mg_1.0.0# update-rc.d voip-mg defaults
update-rc.d: warning: /etc/init.d/voip-mg missing LSB information update-rc.d: see <http://wiki.debian.org/LSBInitScripts> Adding system startup for /etc/init.d/voip-mg ... /etc/rc0.d/K20voip-mg -> ../init.d/voip-mg /etc/rc1.d/K20voip-mg -> ../init.d/voip-mg /etc/rc6.d/K20voip-mg -> ../init.d/voip-mg /etc/rc2.d/S20voip-mg -> ../init.d/voip-mg /etc/rc3.d/S20voip-mg -> ../init.d/voip-mg /etc/rc4.d/S20voip-mg -> ../init.d/voip-mg /etc/rc5.d/S20voip-mg -> ../init.d/voip-mg nd.
root@ast16p3:~/voip-mg_1.0.0# invoke-rc.d voip-mg start
Starting Junghanns.NET voip-mg:[ voip-mg ]
Izmjenjeno od Ernad Husremović prije više od 15 godina
admin/default
Izmjenjeno od Ernad Husremović prije više od 15 godina
pokrenuo ali kod licese key activation dobijem šupica tach :( ne da mi licencu
Izmjenjeno od Ernad Husremović prije više od 15 godina
freeswitch build¶
root@ast16p3:~/freeswitch/hernads-freeswitch/libs# git clone git://gitorious.bring.out.ba/freeswitch/openzap.git
root@ast16p3:~/freeswitch/hernads-freeswitch# apt-get install fakeroot automake1.9 unixodbc-dev libasound2-dev libcurl4-openssl-dev libogg-dev libvorbis-dev libperl-dev libgdbm-dev libdb-dev libgnutls-dev libtiff4-dev libx11-dev autogen
Izmjenjeno od Ernad Husremović prije više od 15 godina
root@ast16p3:~/freeswitch/hernads-freeswitch/src/mod/endpoints/mod_skypiax# make 2>err.log
In file included from skypiax_protocol.c:1:
skypiax.h:42:22: error: X11/Xlib.h: No such file or directory skypiax.h:43:25: error: X11/Xlibint.h: No such file or directory skypiax.h:44:23: error: X11/Xatom.h: No such file or directory
Izmjenjeno od Ernad Husremović prije više od 15 godina
traž se i autogen komanda
Izmjenjeno od Ernad Husremović prije više od 15 godina
voip-mg license key¶
to info junghanns.net
Hello, i have installed voip-mg i386 on my linux box with duoBRI card. zaptel is configured (dmesg): [133776.785900] qozap: Junghanns.NET duoBRI card configured at io port 0x1088 IRQ 11 HZ 250 CardID 0 [133776.785912] qozap: S/T ports: 2 [ TE TE ] [133776.810779] qozap: 1 multiBRI card(s) in this box, 2 BRI ports total, bloop 0, pcmslave 0, dacs 1. [133776.847850] Registered tone zone 29 (Germany) I'm getting web interface (have internet connection on voip-mg box), but cannot get license key. (empty field) I have also registered this segfault: root@ast16p3:/opt/freeswitch/bin# dmesg | grep voip [37848.262218] voip-mg[30389]: segfault at 48 ip 0812c97d sp bfdfd0e0 error 4 in voip-mg[8048000+225000] How can I obtain license key ?
Izmjenjeno od Ernad Husremović prije skoro 15 godina
- Status promijenjeno iz Dodijeljeno u Odbačeno