Bug#491310: asterisk: Problem not solved by downgrade

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sun Aug 3 13:27:50 UTC 2008


On Sun, Aug 03, 2008 at 02:48:06PM +0200, Christoph Kling wrote:
> Followup-For: Bug #491310
> Package: asterisk
> Version: 1:1.4.21.2~dfsg-1+b1
> 
> 
> Hello,
> 
> I cannot solve the problem by downgrading to 1.4.20, 1.4.19 or 1.4.18. I also 
> tried to downgrade zaptel from 1.4.11 to 1.4.10 - problem remains.
> 
> The error behaviour is different than Louis-David reported it:
> - there is no error when starting asterisk
> - but a Dial(...) on a zap device results in:
>       
>   -- Channel 0/1, span 1 got hangup, cause 18

(AST_CAUSE_NO_USER_RESPONSE)

Could you please provide a pri trace 'pri debug span 1') of the call?

> 
> - if I try "zap show status", it shows:
>   
> debian*CLI> zap show status
> Description                              Alarms     IRQ        bpviol     CRC4      
> HFC-S PCI A ISDN card 0 [NT] layer 1 AC  OK         0          0          0         
> 
> - "zap show channels" shows:
> 
> debian*CLI> zap show channels
>    Chan Extension  Context         Language   MOH Interpret       
>  pseudo            from-internal              default             
>       1            from-internal              default             
>       2            from-internal              default             

This is clearly a different issue than #491810 . #491810 is about
Asterisk not starting at all.

> 
> - "zap restart" results in:
> 
> debian*CLI> zap restart
>  Destroying channels and reloading zaptel configuration.
>   == Parsing '/etc/asterisk/zapata.conf': Found
> [Aug  3 14:39:45] WARNING[4177]: chan_zap.c:957 zt_open: Unable to specify channel 1: Device or resource busy
> [Aug  3 14:39:45] ERROR[4177]: chan_zap.c:7413 mkintf: Unable to open channel 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Aug  3 14:39:45] ERROR[4177]: chan_zap.c:11896 build_channels: Unable to register channel '1-2'
> [Aug  3 14:39:45] WARNING[4177]: chan_zap.c:11184 zap_restart: Reload channels from zap config failed!

'zap restart' is known not to work on digital channels. This is a known
issue. There's currently some work on it, but it won't even get into
Asterisk 1.6.0 and I'm not sure how simple it would be to backport.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir





More information about the Pkg-voip-maintainers mailing list