[chan-capi-users] Hints for respond to incoming calls

[Andreas Ruf]

Am Dienstag, den 07.04.2009, 17:59 +0200 schrieb Armin Schindler:
> On Tue, 7 Apr 2009, Andreas Ruf wrote:
> ...
> >> So my conclusion is that your libcapi20 (which is in charge of using and
> >> showing these values) is buggy!!! It is not acting according to CAPI 2.0
> >> standard.

> Also, in the reply the vendor claims about GlobalConfiguration not beeing 
> existent in older libcapi20. Basically that's true. But because of the 
> nature of the CAPI message, it is possible to omit this.
> GlobalConfiguration is part of a sub-structure, but when length of that 
> structure tells no more data, it is just not used.
> So for this issue, there is no difference between libcapi20.so.2 and .3 !
> Just the extended functions of libcapi20 (which are not used with chan_capi)
> are different, what was the reason for having .2 -> .3.
> The raw capi message handling/parsing/use was never changed in linux and
> is according to CAPI 2.0 spec.
> I don't know where the capi message parsing is done for your ISDN card. In 
> either case (driver of libcapi20-vendor), there is a bug when parsing the
> capi message. The vendor should read the CAPI spec.

I asked the manufacturer of the card if the parsing done by the libcapi
could be incorrect. Below is a part of the vendor's reply; perhaps of
interest for you:
"...chan_capi verwendet die Linux Spezial Tools ausschliesslich für das
Logging. Insofern liegt das Problem also eher darin, dass chan_capi zwar
eine korrekt formatierte Nachricht generiert, diese dann aber falsch
dumped....Dies alles hat jedoch nichts mit Ihrem eigentlichen Problem zu
tun. Es wäre in jedem Falle sinnvoll, wenn Sie sich nicht auf
chan_capi/Asterisk bzgl. des CAPI-Trace verlassen, sondern den ctracer
von uns verwenden. Dann sieht man nämlich, was wirklich beim CAPI
ankommt und nicht, was die Software daraus macht...."

Sincerely,
Andreas Ruf

> 
> Armin
> _______________________________________________