In article <[EMAIL PROTECTED]>, Erik Hensema <[EMAIL PROTECTED]> wrote: > Hello, > > Situation: I've got two asterisk 1.2.4 servers, connected to each > other over the internet with IAX2 with about 20msec delay. > > One of the servers is hosting MeetMe. It's working fine as long as > only SIP phones connected to the meetme server participate in the > conference. As soon as a participant using IAX2 is connecting, lots > and lots of buffer overruns and underruns are generated: > > Apr 20 17:37:27 NOTICE[20970]: app_meetme.c:1276 conf_run: Audio > bytes: 640 Buffer size: 320 > Apr 20 17:37:27 NOTICE[20970]: app_meetme.c:1276 conf_run: Audio > bytes: 320 Buffer size: 640 > Apr 20 17:37:27 NOTICE[20970]: app_meetme.c:1276 conf_run: Audio > bytes: 640 Buffer size: 320 > Apr 20 17:37:28 NOTICE[20970]: app_meetme.c:1276 conf_run: Audio > bytes: 320 Buffer size: 640 > Apr 20 17:37:28 NOTICE[20970]: app_meetme.c:1276 conf_run: Audio > bytes: 640 Buffer size: 320 > > This always happens, even if there's only one participant in the > conference.
Those messages are not a part of the standard MeetMe. It looks like you are running a version that includes Dan Austin's dynamic buffer patch from Mantis bug #5697. That dynamic buffer patch is not really required. It was an attempt to get the pseudo-device to accept a whole frame in one write(), but this has been obviated by the non-blocking flag to careful_write(). Try updating to an unpatched 1.2.7 instead. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
