Sorry Steve, I did not want to blame anybody or any product  I am new
to this whole thing, and I was trying to isolate the problem.  Maybe I
just do not know where to search.

I have been trying to create Debian packages both from the releases as
well as from the snapshots, but it did not work on my Debian 64bit
system, because of a lib / lib64 mismatch in Spandsp and the Debian
patch.  I tried to correct the problems (but in my first approach at
the wrong place) with the result that spandsp build, but the final
combination did not work.  Compiling both packages locally still
needed some corrections.  Because I could not find much documentation
on Callweaver to isolate the error, I tried to isolate the problem by
installing Asterisk.  The same mISDN seemed to work there, so I
thought it could be related to spandsp, especially as I had some
trouble compiling it.

However, now it seems to work and is properly installed.  I still have
to figure out how to configure the T.38 gateway (ISDN FAX <-> T.38
SIP). Is there any documentation of the t38gateway besides the short
FAQ?

Bye,
Karel

On 6/27/07, Steve Underwood <[EMAIL PROTECTED]> wrote:
> Karel K. wrote:
> > On 6/26/07, Karel K. <[EMAIL PROTECTED]> wrote:
> >
> >> Hello,
> >>
> >> I have tried installing the latest Callweaver, mISDN and SpanDSP(tried
> >> both spandsp-0.0.4pre3 and latest snapshot) version on a Debian 64bit
> >> system.
> >>
> > ...
> >
> >> Problem: Any functions producing a sound output eg. Playback() lead to
> >> a crash of callweaver.
> >> ...
> >>
> >
> > Just a short update, I tried again with the 25 Jun snapshot and the
> > latest svn version of callweaver and things seem to work now.
> >
> Why would you think this has anything to do with spandsp? Do you blame
> it for anything which doesn't work?
>
> Steve
>
>
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to