[asterisk-r2] Full Debug Libopenr2

Tue May 5 14:06:02 CDT 2009

That's all you got. The other end isn't replying to your SEIZE, hence the
timeout after 8 seconds. The call didn't pass the SEIZE/ACK initial phase.
There's no more information about R2 than that. You would end up with pretty
much the same on unicall in the same set up.

If you want to see OpenR2 library debug, you can re-compile it with the
proper option. Check ./configure --help
HOWEVER, that wouldn't be of any less help cause you'll only see in deep how
the library works and I don't think that is what you're looking for.

-
MM

On Tue, May 5, 2009 at 2:01 PM, "ROQUÉ, Francisco Emiliano" <
froque at 3tech.com.ar> wrote:

> Thanks for your reply Moises.
>
> this is the debug I see:
>
> [Apr 30 13:17:01] DEBUG[5308] chan_dahdi.c: Chan 30 - Attempting to make
> call (ANI=303, DNIS=91236, category=National Subscrib
> er)
> [Apr 30 13:17:01] DEBUG[5308] chan_dahdi.c: Chan 30 - Call started at
> Thu Apr 30 13:17:01 2009 on chan 30
> [Apr 30 13:17:01] DEBUG[5308] chan_dahdi.c: Chan 30 - CAS Tx >> [SEIZE]
> 0x00
> [Apr 30 13:17:01] DEBUG[5308] chan_dahdi.c: Chan 30 - CAS Raw Tx >> 0x01
> [Apr 30 13:17:01] VERBOSE[5308] logger.c:     -- Called 30/91236
> [Apr 30 13:17:09] DEBUG[5308] chan_dahdi.c: Chan 30 - calling timer
> callback
> [Apr 30 13:17:09] WARNING[5308] chan_dahdi.c: Chan 30 - Seize Timeout
> Expired!
>
> [Apr 30 13:17:09] ERROR[5308] chan_dahdi.c: Chan 30 - Protocol error.
> Reason = Seize Timeout, R2 State = Seize Transmitted, MF
>  state = MF Engine Off, MF Group = Forward MF init, CAS = 0x08
> DNIS = 91236, ANI = 303, MF = 0x20
> [Apr 30 13:17:09] DEBUG[5308] chan_dahdi.c: Chan 30 - CAS Tx >> [IDLE] 0x08
> [Apr 30 13:17:09] DEBUG[5308] chan_dahdi.c: Chan 30 - CAS Raw Tx >> 0x09
> [Apr 30 13:17:09] ERROR[5308] chan_dahdi.c: MFC/R2 protocol error on
> chan 30: Seize Timeout
> [Apr 30 13:17:09] DEBUG[5308] chan_dahdi.c: disconnecting MFC/R2 call on
> chan 30
> [Apr 30 13:17:09] VERBOSE[5308] logger.c:     -- Hungup 'DAHDI/30-1'
>
> I needed to have a greater level of detail....
>
> In my logger.conf i set:
> full => notice,warning,error,debug,verbose
>
> in my chan_dahdi.conf i set:
> mfcr2_logdir=log
> mfcr2_logging=all
> mfcr2_call_files=yes
>
>
> In this way the files *.call were created, but its content is very poor,
> for example, the file:
>
>  /var/log/asterisk/mfcr2/log/chan-1-forward-0-20090430140630.call contain:
>
>
> 14:06:30:129] [Thread: 43326352] [Chan 1] - Call started at Thu Apr 30
> 14:06:30 2009 on chan 1
> [14:06:30:129] [Thread: 43326352] [Chan 1] - CAS Tx >> [SEIZE] 0x00
> [14:06:30:129] [Thread: 43326352] [Chan 1] - CAS Raw Tx >> 0x01
> [14:06:38:148] [Thread: 43326352] [Chan 1] - Attempting to cancel timer
> timer 2
> [14:06:38:148] [Thread: 43326352] [Chan 1] - timer id 2 found,
> cancelling it now
> [14:06:38:148] [Thread: 43326352] [Chan 1] - calling timer callback
> [14:06:38:148] [Thread: 43326352] [Chan 1] - Seize Timeout Expired!
> [14:06:38:148] [Thread: 43326352] [Chan 1] - Protocol error. Reason =
> Seize Timeout, R2 State = Seize Transmitted, MF state = MF Engine Off,
> MF Group = Forward MF init, CAS = 0x08
> DNIS = 90956, ANI = 60001, MF = 0x20
> [14:06:38:148] [Thread: 43326352] [Chan 1] - Attempting to cancel timer
> timer 0
> [14:06:38:148] [Thread: 43326352] [Chan 1] - Cannot cancel timer 0
>
> This is practically equal to that observed in /var/log/asterisk/full....
>
>
> How can I get more detail? like.... unicall debug....
>
> Regards
>
> Francisco
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Ing Francisco Roqué
> 3Tech SRL
> Plaza Paso Nº92, EP B
> Buenos Aires, Argentina.
> Tel. +54 11 5252 8727
>     +54 221 4255116
> www.3tech.com.ar
>
>
>
> Moises Silva wrote:
> >> In /etc/asterisk/chan_dahdi.conf i have enabled mfcr2_logging set to
> all.
> >>
> > This just enables debugging on the library itself, you still need to
> > enable Asterisk debugging output in /etc/asterisk/logger.conf, read
> > the comments there.
> >
> >
> >> In /etc/openr2/r2test.conf i have loglevel set to all....
> >>
> > This has nothing to do with Asterisk debugging, this file is only used
> > by the r2test program.
> >
> >
> >> Can i enable a debug very full?
> >>
> > Yes, mfcr2_logging=all has all you may want
> >
> >
> >> Also check the console: mfcr2 set debug all and configuration of call
> >> files, but the debugs are identically
> >>
> > I don't understand what you mean. call files  ALWAYS have FULL
> > debugging information regardless of the mfcr2_logging parameter. Read
> > the comments in configs/chan_dahdi.conf.sample in Asterisk 1.6.2 or
> > download the sample .conf files in google code.
> >
> >
> >> Do you recommend the use of the package libopenr2-debuginfo?
> >>
> > No, that package probably just includes debugging symbols for the
> > openr2 library.
> >
> >  --
> > Moises Silva
> > Software Developer
> > Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
> > L3R 9T3 Canada
> > t. 1 905 474 1990 x 128 | e. moy at sangoma.com
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-r2 mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-r2
> >
> >
> >
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090505/5856cd47/attachment.htm 