Re: [GnomeMeeting-list] PC-to-Phone with Quicknet

[b2g <ggb2g yahoo fr>]

Le Vendredi 28 Février 2003 09:31, derek indranet co nz a écrit :
> Hi,
>   It could be anywhere.
>
>  Can you do (as root)
>    rmmod ixj
>    insmod ixj ixjdebug=256
>
>   Now, everytime the driver generates a signal, a message will be sent to
> the kernel log file.
>
>  run Gnomemeeting
>  talk
>
>  when it exits, quit Gnomemeeting
>
>   rmmod ixj              (which stops the flood of messages)
>
>  cp /var/log/messages temp_file
>
>   insmod ixj
>
>  Peruse temp_file for clues as to what signals the driver generated which
>   stopped the call.
>
I guess this is what you are looking for:
Mar  5 20:45:00 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4580629 jiffies
Mar  5 20:45:18 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4582440 jiffies
Mar  5 20:45:21 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582714 jiffies
Mar  5 20:45:21 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582732 jiffies
Mar  5 20:45:21 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582750 jiffies
Mar  5 20:45:21 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582768 jiffies
Mar  5 20:45:21 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582789 jiffies
Mar  5 20:45:22 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582807 jiffies
Mar  5 20:45:22 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582825 jiffies
Mar  5 20:45:22 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582846 jiffies
Mar  5 20:45:22 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582864 jiffies
Mar  5 20:45:22 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582882 jiffies
Mar  5 20:45:23 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4582903 jiffies
Mar  5 20:45:36 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4584199 jiffies
Mar  5 20:46:11 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4587722 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4587994 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588012 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588033 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588051 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588069 jiffies
Mar  5 20:46:14 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588090 jiffies
Mar  5 20:46:15 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588108 jiffies
Mar  5 20:46:15 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588126 jiffies
Mar  5 20:46:15 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588144 jiffies
Mar  5 20:46:15 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588165 jiffies
Mar  5 20:46:15 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4588183 jiffies
Mar  5 20:48:38 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4602390 jiffies
Mar  5 20:48:44 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4603025 jiffies
Mar  5 20:48:47 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603297 jiffies
Mar  5 20:48:47 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603315 jiffies
Mar  5 20:48:47 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603336 jiffies
Mar  5 20:48:47 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603354 jiffies
Mar  5 20:48:47 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603372 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603393 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603411 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603429 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603447 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603468 jiffies
Mar  5 20:48:48 localhost kernel: Sending signal for event SIG_DTMF_READY (0) 
at 4603486 jiffies
Mar  5 20:51:15 localhost kernel: Sending signal for event SIG_HOOKSTATE (1) 
at 4618146 jiffies

I must say that I do not understand and as mention by Damien I will try the 
new RPM from Mandrake later during the week

>  Or just send temp_file to me offline.
>
> Derek.
> ====================================================================
>   there is a log feature in GnomeMeeting.
>
> On Fri, 28 Feb 2003, b2g wrote:
> > Le Vendredi 28 Février 2003 01:04, Damien Sandras a écrit :
> > > Did you try PC-To-Phone calls already?
> >
> > yes and the quality is excellent (Macau SAR to France).
> > the only remaining problem is that every 2 minutes and 10 secondes it
> > just cut the call abnormaly. Any ideas or suggestions?
> > I guess is more a problem with MicroTelco?
> >
> >
> > Gerald
> >
> > > Le jeu 27/02/2003 à 17:45, b2g a écrit :
> > > > OK!
> > > > I was afraid to go for compiling but finally it went smoothly and it
> > > > works! Thanks to you guys.
> > > > Gerald
> > > >
> > > > Le Jeudi 27 Février 2003 18:58, Damien Sandras a écrit :
> > > > > Le jeu 27/02/2003 à 10:01, derek indranet co nz a écrit :
> > > > > > Now, you should be able to run Gnomemeeting as an ordinary user.
> > > > > >
> > > > > > Running Gnomemeeting as root - surely, this a security problem?
> > > > >
> > > > > I didn't suggest to run GnomeMeeting as root, I suggested to try to
> > > > > run it as root to determine if it is a permissions problem. If it
> > > > > is simply a permission problem, no need to install a new driver
> > > > > version.
> > > > >
> > > > > > Derek.
> > > > > > ========
> > > > > >
> > > > > > On 27 Feb 2003, Damien Sandras wrote:
> > > > > > > Le jeu 27/02/2003 à 07:31, b2g a écrit :
> > > > > > > > 1. yes I've subscribe to microtelco service through
> > > > > > > > linuxjack.com and get a special gnomemeeting account.
> > > > > > > > Gnomemeeting is connected to the hote gatekeeper
> > > > > > > > gk.microtelco.com and display something like :
> > > > > > > > bmac ip-similar-number  And I can check online my account
> > > > > > > > status through GM.
> > > > > > >
> > > > > > > That's correct :)
> > > > > > >
> > > > > > > > 2. I've check the rights:  /proc/ixj is r--r--r--. Is it that
> > > > > > > > I have to check?
> > > > > > >
> > > > > > > No, but simply running GnomeMeeting as "root" could help to
> > > > > > > determine if it is a permission problem. If it detects the
> > > > > > > /dev/phone0 as root, then it is ok.
> > > > > > >
> > > > > > > Also, do you have any /dev/phone0 or /dev/phone device ?
> > > > > > >
> > > > > > > > 3. the output of cat /proc/ixj is:
> > > > > > > > ====================================
> > > > > > > > $Id: ixj.c,v 4.7 2001/08/13 06:19:33 craigs Exp $
> > > > > > > > $Id: ixj.h,v 4.1 2001/08/04 14:49:27 craigs Exp $
> > > > > > > > $Id: ixjuser.h,v 4.1 2001/08/05 00:17:37 craigs Exp $
> > > > > > > > Driver version 1.0.1
> > > > > > > > sizeof IXJ struct 21144 bytes
> > > > > > > > sizeof DAA struct 642 bytes
> > > > > > > > Using old telephony API
> > > > > > > > Debug Level 0
> > > > > > > >
> > > > > > > > Card Num 0
> > > > > > > > DSP Base Address 0xb000
> > > > > > > > XILINX Base Address 0xb010
> > > > > > > > DSP Type 8022
> > > > > > > > DSP Version 01.17
> > > > > > > > Serial Number 5119034c
> > > > > > > > Card Type = Internet PhoneJACK PCI
> > > > > > > > Readers 0
> > > > > > > > Writers 0
> > > > > > > > Capabilities 13
> > > > > > > > DSP Processor load 0
> > > > > > > > Caller ID data not sent
> > > > > > > > Play CODEC NO CODEC CHOSEN
> > > > > > > > Record CODEC NO CODEC CHOSEN
> > > > > > > > AEC Off
> > > > > > > > Rec volume 0x100
> > > > > > > > Play volume 0x100
> > > > > > > > DTMF prescale 0x40
> > > > > > > > Hook state 0
> > > > > > > > Port POTS
> > > > > > > > SLIC state RINGING
> > > > > > > > Base Frame 00.00
> > > > > > > > CID Base Frame  0
> > > > > > > > Timer Checks 3537
> > > > > > > > RX Ready Checks 3537
> > > > > > > > TX Ready Checks 3537
> > > > > > > > Frames Read 0
> > > > > > > > Frames Written 0
> > > > > > > > Dry Buffer 0
> > > > > > > > Read Waits 0
> > > > > > > > Write Waits 0
> > > > > > > > Status Waits 82
> > > > > > > > Status Wait Fails 0
> > > > > > > > PControl Waits 0
> > > > > > > > PControl Wait Fails 0
> > > > > > > > Is Control Ready Checks 0
> > > > > > > > Is Control Ready Check failures 0
> > > > > > > > =======================================
> > > > > > > >
> > > > > > > >
> > > > > > > > I am going to try to compile the latest driver to see if any
> > > > > > > > difference. I will probably recontact you guys for more help.
> > > > > > > > Thanks a lot for your help and this wonderful soft.
> > > > > > > >
> > > > > > > > Gerald
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > GnomeMeeting-list mailing list
> > > > > > > > GnomeMeeting-list gnome org
> > > > > > > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
> > > >
> > > > _______________________________________________
> > > > GnomeMeeting-list mailing list
> > > > GnomeMeeting-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
> >
> > _______________________________________________
> > GnomeMeeting-list mailing list
> > GnomeMeeting-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list