[Asterisk-Users] Netjet/Linux/Asterisk issue

Bob Purdon bobp at tekmax.com.au
Sun Apr 24 04:26:06 MST 2005


Hi All,

Debian Sarge (most recent update yesterday).  Running a custom-built 
2.6.8 kernel (Debian kernel doesn't have the Traverse transparent mode 
patch - the 2.4 patch seemed to apply to the 2.6 sources OK).

0000:01:09.0 Network controller: Tiger Jet Network Inc. Tiger3XX 
Modem/ISDN interface
         Subsystem: Unknown device 0001:000e
         Flags: bus master, medium devsel, latency 220, IRQ 11
         I/O ports at d400 [size=256]
         Memory at ff8fd000 (32-bit, non-prefetchable) [size=4K]

*CLI> show version
Asterisk 1.0.7-BRIstuffed-0.2.0-RC7k built by kk at nyx on a x86_64 running 
Linux


(Typing this, I wonder if the 'BRIstuffed' in the version number is 
relevant to my problem)

I can dial out from a SIP phone fine - all works as expected.

If I dial in via the BRI to a SIP phone, regardless of which end hangs 
up first, I get:

Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success
Apr 24 16:22:52 WARNING[2191]: chan_modem_i4l.c:391 i4l_read: Read 
failed: Success

...and so on.  Once this happens the BRI channel is wedged until I 
restart Asterisk.


Has anyone seen this behaviour?  I Google'd for a good while but didn't 
turn anything up :-(

I realise it could be the 2.4 Traverse patch not working with the 2.6 
netjet.c code, or the 'BRIstuffed' Debian package of Asterisk.  I'm 
hoping someone has seen this and can save me a few hours work :-)

In the absence of any advice I'll be trying a 2.4 kernel tomorrow, time 
permitting.  I suppose, beyond that, I'll try a build-from-sources 
version of Asterisk (although for this application I prefer the Debian 
package).

Cheers.



More information about the asterisk-users mailing list