Summary:ASTERISK-07980: Fail of ioctl
Reporter:Anton Fedorov (datacompboy)Labels:
Date Opened:2006-10-23 08:04:17Date Closed:2011-06-07 14:07:27
Versions:Frequency of
Description:If /dev/zap/timer are not device but plain file (as for me -- dead after partial system upgrade) asterisk fails to start timer, and no RTP generated/received:

[b7f8099e] tgkill(6670, 6670, SIGURG) = 0
[b7e50c24] ioctl(18, 0x40044a2f, 0xb72dcde4) = -1 ENOTTY (Inappropriate ioctl for device)
 ** Do you see that? That are failed timer start.

[b7e0bc31] gettimeofday({1161600561, 294471}, NULL) = 0
[b7e4ee19] poll([{fd=10, events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|POLLPRI, revents=POLLIN}, {fd=19, events=POLLIN|POLLPRI}], 4, 1000) = 1
 ** As result -- poll() report event on 18th

[b7e0bc31] gettimeofday({1161600561, 294917}, NULL) = 0
[b7f823d1] read(19, 0xb72dce28, 4) = -1 EAGAIN (Resource temporarily unavailable)
 ** But since that was timer, we just hope that data arrived -- but that wrong, and read(19) fails.

[b7e0bc1d] time([1161600561]) = 1161600561
[b7e0bc31] gettimeofday({1161600561, 295294}, NULL) = 0
  ... and everything cycled -- since on 18th still pending data (was written to driver)

****** STEPS TO REPRODUCE ******

rm /dev/zap/timer
touch /dev/zap/timer
and try to use asterisk's thru SIP
Comments:By: Russell Bryant (russell) 2006-10-23 20:13:09

There isn't anything we can do if your system was broken.  If you build Asterisk will zaptel support, it will assume that you have a working installation ...