Hi
I tried also turn debugging off. The result was the same.
What can we do next?
Marek
On Mon, 31 Mar 2008, Andrea Lanza wrote:
>
> As I already said, I had to move from ISDN with misdn to analogue with
> tdm400.
>
> Then I had to turn off debugging, as probably you could remember: enabling
> debugging
> brought to line missing pages (timing issues); disabling debugging turned
> off the problem.
>
> Andrea
>
> > -----Messaggio originale-----
> > Da: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Per conto di
> > Steve Underwood
> > Inviato: sabato 29 marzo 2008 5.01
> > A: Users Mailing List - Non-Commercial Discussion
> > Oggetto: Re: [Callweaver-users] Cannot manage T38Gateway to work (fwd)
> >
> > Marek Zelem wrote:
> > > Hi
> > >
> > > I have changed NSE to REINVITE on ATA. Now there is word
> > 're-invite'
> > > in logs, so something changed. But fax is still not working.
> > >
> > > I did both directions.
> > >
> > > Receiving fax from ISDN CAPI --> ATA --> fax:
> > > http://marek.terminus.sk/cw/full_2_in.gz
> > >
> > > http://marek.terminus.sk/cw/callweaver_incoming_fax_2_in.tcpdump.gz
> > >
> > > Sending fax from Fax machine --> ATA --> ISDN CAPI
> > > http://marek.terminus.sk/cw/full_2_out.gz
> > >
> > > http://marek.terminus.sk/cw/callweaver_incoming_fax_2_out.tcpdump.gz
> > >
> > > When I was sending fax I observer interesting fact. I have
> > asterisk on
> > > receiving side with NVBackgroundDetect but call was not detected as
> > > fax. I did the same fax sending before but instead of
> > callweaver I had asterisk.
> > > In that case receiving asterisk detected fax with
> > NVBackgroundDetect.
> > > I have filling I cannot get rid of that there is signal somehow
> > > degraded when using callweaver. Also when I tried
> > BackgroundDetect on
> > > callweaver - dtmf and fax detection was very very unreliable. With
> > > NVBackgroundDetect and asterisk it works 100% reliable.
> > Same machine,
> > > same environment, same configuration, only one difference: with
> > > asterisk I use mISDN, with Callweaver CAPI.
> > >
> > A lot of people seem to have trouble with mISDN and CAPI on
> > various machines, both with Asterisk and Callweaver. ISDN on
> > Linux is a mess. It could be the signal is stuttering at
> > times, causing your DTMF detection issues. However, the small
> > amount of audio from the ISDN channel logged as RTP packets
> > in your files looks OK.
> >
> > The receiving FAX looks fine until the point where things switch into
> > T.38 mode. From then on nothing is received from the
> > Callweaver box, except a final SIP disconnect when the PSTN
> > call drops. Looking at the Callweaver log, it seems the T.38
> > data is correctly received and by T38Gateway(), and forwarded
> > as audio to the FAX machine. However, it looks like nothing
> > is received from the FAX machine. The fragment of audio sent
> > as RTP before the T.38 changeover looks OK, though. I wonder
> > if there is some issue between T38Gateway() and the CAPI
> > channel driver?
> >
> > The sending case looks stranger. No RTP or UDPTL is sent by
> > the Callweaver box at all. The initial negotiation goes OK,
> > but the CAPI channel seems to immediately foul up with
> > endless repeating of:
> >
> > ERROR[3059407792] chan_capi.c: Could not write to pipe for ISDN1#02
> >
> > Maybe we have chan_capi problems here, rather than T.38 gateway ones.
> > Are there any other chan_capi user who can comment?
> >
> > Steve
> >
> >
> > _______________________________________________
> > Callweaver-users mailing list
> > [email protected]
> > http://lists.callweaver.org/mailman/listinfo/callweaver-users
> >
>
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
