AW: AW: asterisk 1.11 and chan_misdn

Sorry i forgot to add that i'am speaking for misdn_v1 only.

Last time i tried to compile the mISDN sources, as the ones from the kernel tree where outdated or incomplete, i needed to hack the sources and makefile to remove deprecated kernel lock calls as well as checks to outdated header files. (Please don't nail me for the versions.) I also needed to hack the asterisk 1.8.x configure script as it didn't identified the mISDN sources correctly and won't build chan_misdn.

I didn't tried to build chan_lcr and mISDNv2 as they missed some features in the past. (Don't know if that changed.)

Please don't understand me as a supporter of DAHDI, that driver isn't the best either ^^ not to say i really hate this thing meanwhile.

On the other hand following ran out of the box.

Installed debian Squeez.
Got kernel 3.7.8
Build it installed it.
Got asterisk 1.8.15
Got dahdid 2.6.2 (openvox version)
Got libpri 1.4.11 or so
Build them without any issues

Ran dahdi_genconf, adopted the config to NT mode (you need to set a module parameter to set NT mode)

Voila all is running. One E1-Card and two 8 Port S0-Cards.

NT Mode ran for Digium and Openvox, guess your right that the hfc port for foreign cards isn't available as default. I didn't check that as i used the driver from openvox as we use their cards or Digium :) Would be worth to test our older Beronet cards. Compatibility for ISDN devices isn't the best as it seems. Out ISDN test phones Siemens and Telecom work but restart of Asterisk quite often requires a power cycle of the phone also. 

The system runs stable especially transfer/hold retrieve (Broker's call) that was known to crash randomly under mISDN v1 works with a charm. Only missing feature is 3py conference but i guess that isn't working for any other channel than SIP in the moment.

BUT

As said DHADI is a performance pig .. the IRQ quote is so high that many mainboards have problems to handle that and you often get the helpful answer from the support crew .. try another PCI slot. Running multiple cards at once can be really difficult. The cards hate IRQ-Share and we hunt a random crash of the system in the moment and i'am afraid that is simply a bug of the cards driver if the system IRQ-Load is reaching the boards capacity.

I hope this report is helpful

...

Sven


-----Ursprüngliche Nachricht-----
Von: isdn4linux [mailto:isdn4linux-bounces-JX7+OpRa80SjiSfgN6Y1Ib39b6g2fGNp@public.gmane.org] Im Auftrag von Birger Harzenetter
Gesendet: Freitag, 31. Mai 2013 17:42
An: [email protected]
Betreff: Re: AW: asterisk 1.11 and chan_misdn

On Mon, 27 May 2013 08:46:54 +0200, Hirschmüller,_Sven <[email protected]> wrote:

>
> It's still a hassle to get mISDN running in a new environment. (Kernel >  
> 3.x.x)

Why?
Sure, having to get the user space part from git is not user friendly at  
all and really bad if there's an issue in the current version.
But apart from that?

> Meanwhile the guys from Digium add BRI-ISDN support to their dahdi  
> driver and it runs quite well in the latest versions. They also

I don't see the dahdi_hfcs in the official archive.
And as far as I see (2.6.2) you still need a patch to enable NT mode on  
cards without the famous 5th jumper.

> added support for foreign HFC-S cards so you can get foreign cards like  
> ones from openvox running quite easily.
>
> So if you don't need the low level mISDN interfaces as you only use  
> asterisk you can use dahdi and counter a possible heart attack by trying  
> to get mISDN running :)

DAHDI has given me a lot more headaches (and surprise features) so far.

> On the other hand the dahdi drivers are performance pigs as they heavily  
> use IRQs and you can get problems with your hardware because of that.

Oh yes, they have some extremely nasty internals.

On the other hand I think DAHDI has taken the lead on the feature list.  
(ECT being the killer)
But it depends on the specific use case which feature list will be the  
winner.

But as far as installation and configuration goes, mISDN is the winner for  
me.

   Greetings,
     WIMPy
_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux