>Number: 138128
>Category: misc
>Synopsis: asterisk stais longer in "wait" when app_meetme is used
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Aug 24 09:30:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Anatoli Marinov
>Release: 7.2-RELEASE-p2
>Organization:
TS
>Environment:
FreeBSD b***pbx-jr.b***bg.com 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
>Description:
The schema is:
Asterisk 1.4.25
zaptel 1.4.11_1
The problem appears when somebody uses conference service and aka he is ini conference room.
After that if a new call goes in extensions.conf in extension for example:
exten => _3592.,1,Ringing
exten => _3592.,n,Wait,2
exten => _3592.,n,Answer
The call stops in "Wait" command and never get next one even 2 seconds expired.
This is appeared only when app_meatme is used.
The same problem appears with asterisk-1.4.24.1_3
>How-To-Repeat:
Load app_meatme.so and chan_zap.so. Make a call and enter in conference room.
Make another call to extension like this:
exten => _3592.,1,Wait,2
exten => _3592.,n,Playback(some mp3 or other sound file)
Look at the asterisk console to see that Playback will be executed.
The problem appears sometime but if reproduced all next tries will observe the same problem.
>Fix:
I think the problem is in zaptel because app_meatme uses its timers.
Maybe there is porting issue ....
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"