[asterisk-r2] Urgente seize timeout

OrvUx orvux at orvux.net
Fri Dec 4 06:35:32 CST 2009


    Well, after a couple of hours (yes, sure) i have running wanpipe
3.5.8

    Today i will be monitoring the calls to check if the error comes
back.

    Thanks. 

L.I. Orvil Juarez
IT Manager
J&A Consulting
http://www.jacons.net
Linux and Asterisk Consulting in Tijuana, B.C.
   

On Thu, 2009-12-03 at 23:16 -0800, OrvUx wrote:

> Here tge result,,, :(
> 
>     Wanpipe 3.4.7 do not compile:
> 
> Compiling WANPIPE API Development Utilities ...Failed!
> 
> ERROR: Failed to compile WANPIPE API Tools !!!
> Please contact support at Sangoma Technologies
> email: techdesk at sangoma.com
> Please include the file setup_drv_compile.log
> 
> This is the link for the setup_drv_compile.log in pastebin.
> 
> http://pastebin.com/m3d57b0d0
> 
> Hope you can help me. Thanks.
> 
> 
> L.I. Orvil Juarez
> IT Manager
> J&A Consulting
> http://www.jacons.net
> Linux and Asterisk Consulting in Tijuana, B.C.
> 
> 
> On Thu, 2009-12-03 at 22:27 -0800, OrvUx wrote:
> 
> >     I tried with wanpipe 3.5.8 but there are errors on load:
> > 
> > Starting WAN Router...
> > Loading WAN drivers: wanpipe FATAL: Error inserting wanpipe
> > (/lib/modules/2.6.26-2-686-bigmem/kernel/drivers/net/wan/wanpipe.ko): Unknown symbol in module, or unknown parameter (see dmesg)
> > 
> > Failed to load wanpipe modules !
> > 
> > This is the error in the kern.log file ( i use Debian ;) )
> > 
> > Dec  3 22:15:29 jacpbx kernel: [44256.356231] WANPIPE(tm) Hardware
> > Support Module  3.5.8.0 (c) 1994-2009 Sangoma Technologies Inc
> > Dec  3 22:15:29 jacpbx kernel: [44256.356231] usbcore: registered
> > new interface driver sdlausb
> > Dec  3 22:15:29 jacpbx kernel: [44256.360231] Zapata Telephony
> > Interface Registered on major 196
> > Dec  3 22:15:29 jacpbx kernel: [44256.360231] Zaptel Version:
> > 1.4.12.1
> > Dec  3 22:15:29 jacpbx kernel: [44256.360231] Zaptel Echo Canceller:
> > MG2
> > Dec  3 22:15:29 jacpbx kernel: [44256.360231] WANPIPE(tm) Interface
> > Support Module 3.5.8.0 (c) 1994-2009 Sangoma Technologies Inc
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_ec_span
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_ec_span
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_hdlc_getbuf
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_hdlc_getbuf
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_receive
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_receive
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_qevent_lock
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_qevent_lock
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_ec_chunk
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_ec_chunk
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_transmit
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_transmit
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_rbsbits
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_rbsbits
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_unregister
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_unregister
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_hooksig
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_hooksig
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_register
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_register
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: no symbol
> > version for zt_alarm_notify
> > Dec  3 22:15:29 jacpbx kernel: [44256.364232] wanpipe: Unknown
> > symbol zt_alarm_notify
> > Dec  3 22:15:29 jacpbx kernel: [44256.380392] usbcore: deregistering
> > interface driver sdlausb
> > 
> > 
> >     I will try with 3.4.7
> > 
> > 
> > L.I. Orvil Juarez
> > IT Manager
> > J&A Consulting
> > http://www.jacons.net
> > Linux and Asterisk Consulting in Tijuana, B.C.
> > 
> > 
> > 
> > On Thu, 2009-12-03 at 22:42 -0500, Moises Silva wrote:
> > 
> > > no tiene nada que ver con mf
> > > 
> > > On Thu, Dec 3, 2009 at 10:41 PM, francisco flores
> > > <turuwhiska at hotmail.com> wrote:
> > > 
> > >         mmm me suena a lo mismo tampoco esta transmitiendo los mf
> > >         no?
> > >         
> > >         
> > >         __________________________________________________________
> > >         
> > >         
> > >         Date: Thu, 3 Dec 2009 22:38:21 -0500
> > >         From: moises.silva at gmail.com 
> > >         
> > >         To: orvux at orvux.net; asterisk-r2 at lists.digium.com
> > >         
> > >         Subject: Re: [asterisk-r2] Urgente seize timeout
> > >         
> > >         
> > >         
> > >         try latests wanpipe.
> > >         
> > >         On Thu, Dec 3, 2009 at 10:36 PM, OrvUx <orvux at orvux.net>
> > >         wrote: 
> > >         
> > >                 These are my versions:
> > >                 
> > >                 Asterisk 1.4.24.1
> > >                 OpenR2 version: 1.1.0, revision: exported
> > >                 Zaptel 1.4.12.1
> > >                 Wanpipe 3.4.1
> > >                 Sangoma A102
> > >                 
> > >                 This is the Call log:
> > >                 
> > >                 [10:24:02:912] [Thread: 3050707856] [Chan 7] -
> > >                 Call started at Thu Dec  3 10:24:02 2009 on chan 7
> > >                 [10:24:02:912] [Thread: 3050707856] [Chan 7] - CAS
> > >                 Tx >> [SEIZE] 0x00
> > >                 [10:24:02:912] [Thread: 3050707856] [Chan 7] - CAS
> > >                 Raw Tx >> 0x01
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 Attempting to cancel timer timer 2
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 timer id 2 found, cancelling it now
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 calling timer callback
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 Seize Timeout Expired!
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 Protocol error. Reason = Seize Timeout, R2 State =
> > >                 Seize Transmitted, MF state = MF Engine Off, MF
> > >                 Group = Forward MF init, CAS = 0x08
> > >                 DNIS = 6641238176, ANI = 018000266845, MF = 0x20
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 Attempting to cancel timer timer 0
> > >                 [10:24:10:931] [Thread: 3050707856] [Chan 7] -
> > >                 Cannot cancel timer 0
> > >                 
> > >                 
> > >                 after rebooting wanpipe and asterisk all works
> > >                 fine again...
> > >                 
> > >                 Thanks.
> > >                 
> > >                 
> > >                 L.I. Orvil Juarez 
> > >                 IT Manager
> > >                 J&A Consulting
> > >                 http://www.jacons.net
> > >                 
> > >                 Linux and Asterisk Consulting in Tijuana, B.C.
> > >                 
> > >                 
> > >                 
> > >                 
> > >                 
> > >                 On Thu, 2009-12-03 at 19:21 -0500, Moises Silva
> > >                 wrote:
> > >                 
> > >                         On Thu, Dec 3, 2009 at 2:27 PM, OrvUx
> > >                         <orvux at orvux.net> wrote:
> > >                         
> > >                                 Hi guys, sorry for my question
> > >                                 but, what happened with this
> > >                                 problem? Mr. Anton Krall did you
> > >                                 resolved it? I have a server with
> > >                                 the same problem, i will
> > >                                 appreciate if you can post your
> > >                                 solution.
> > >                                 
> > >                                 
> > >                         
> > >                         
> > >                         
> > >                         There is no easy answer, sometimes this is
> > >                         a problem with the other end not replying,
> > >                         sometimes it seems the drivers or the card
> > >                         misses bit changes. Which Asterisk,
> > >                         openr2, card and drivers do you use?
> > >                         
> > >                         
> > >                         -- 
> > >                         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 
> > >         
> > >         
> > >         
> > >         
> > >         -- 
> > >         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
> > >         
> > >         
> > >         
> > >         __________________________________________________________
> > >         
> > >         
> > >         Guardá y compartí fotos, archivos, documentos y más. ¡Con
> > >         Windows Live tienes 25 GB gratis! Probalo ahora. 
> > >         
> > >         _______________________________________________
> > >         --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 
> > > 
> > > 
> > > 
> > > 
> > > -- 
> > > 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
> 
> _______________________________________________
> --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/20091204/7ee0a7f0/attachment.htm 


More information about the asterisk-r2 mailing list