asterisk from the ports

[eng. Anatoli Marinov]

Hi folks,
I have a problem with asterisk from ports.
So my system is:
FreeBSD triton.******.com 7.1-STABLE FreeBSD 7.1-STABLE #9: Thu Feb  5
19:43:38 EET 2009
root at triton.*****.com:/usr/obj/usr/src/sys/TRITON_7  i386

and my asterisk is :
Asterisk 1.4.22.2 built by root @ triton.******.com on a i386 running
FreeBSD on 2009-02-06 09:28:53 UTC

The issue appears when I tried to make a conference call with
app_meetme.so. I got:
And when I run the application I get:
   -- <SIP/1003-2870d000> Playing 'auth-thankyou' (language 'en')
   -- <SIP/1003-2870d000> Playing 'vm-review' (language 'en')
   -- <SIP/1003-2870d000> Playing 'vm-msgsaved' (language 'en')
   -- <SIP/1003-2870d000> Playing 'conf-onlyperson' (language 'en')
[Feb  9 10:20:13] WARNING[48968]: app_meetme.c:1620 conf_run: Unable
to set flags: Inappropriate ioctl for device

At these lines there is wrriten:

                if (fcntl(fd, F_SETFL, flags | O_NONBLOCK)) {
                        ast_log(LOG_WARNING, "Unable to set flags:
%s\n", strerror(errno));
                        close(fd);
                        goto outrun;
                }

As I understand  O_NONBLOCK is not supported for this kind of
descriptor and I just removed this code but after that I see regular
crashes everyday :)

And this is from the core file:

#0  0x08092ca7 in ast_closestream ()
#1  0x08092dae in ast_playstream ()
#2  0x080d69a7 in ast_sched_runq ()
#3  0x08092f07 in ast_stopstream ()
#4  0x0809345a in ast_waitstream ()
#5  0x28a831dd in conf_run (chan=0x28709400, conf=0x28b01800,
confflags=74052, optargs=0xbf75baa4) at app_meetme.c:2273
#6  0x28a88498 in conf_exec (chan=0x28709400, data=0xbf75db48) at
app_meetme.c:2767
#7  0x080b0a71 in pbx_exec ()
#8  0x080b3a94 in ast_extension_state ()
#9  0x080b52ed in pbx_builtin_setvar ()
#10 0x080b60ce in ast_pbx_run ()
#11 0x080e22d4 in ast_wait_for_input ()
#12 0x28401afb in pthread_getprio () from /lib/libthr.so.3
#13 0xbf79cfec in ?? ()


Any ideas?

I want to clear this and will prepare the patch.
Mr. Sobolev (he is a port maintainer) know this but I still do not
have any feedback from him.

All the best


-- 
Best Regards
eng. Anatoli Marinov