I tried sending this to asterisk-bsd a couple of days ago I've been using Asterisk in various versions on FreeBSD for some time now, but I've only just got to messing around with ACD. I find I can't get any in-queue announcements to work, be they either periodic or queue position announcements. I've read all of the recent posts on this, and the closest thing to my problem I can find is a chap on asterisk-users who reported something similar a month ago, but worked around it by not selecting the "r" queue option. That doesn't work for me (I wasn't using it anyway) - and I've dropped all queue options as a test, still to no avail. Before I get round to posting my configs for critique, is this a BSD port issue? I see stuff around on the net re the BSD port, to the effect that there are some issues with Asterisk applications which are related to timers. What exactly is meant by that please? Is that what I'm suffering from here or is it something entirely different? My environment is FreeBSD 5.3.18 (in production use), Asterisk 1.2.9.1 from Ports, no hardware telephony cards (using a wholesale IAX provider). Calls are being routed in via IAX2 and the agents are on IAX2 hardphones, not that that latter makes any difference methinks. Many thanks in advance for any help that can be offered. Phil ----- End forwarded message -----
On 07/26/06 14:58 Phil Jordan said the following:> Before I get round to posting my configs for critique, is this a BSD > port issue? I see stuff around on the net re the BSD port, to theno, it isn't a BSD port issue. many people run asterisk from ports with ACDs without any problems. in your situation, you'd probably need to provide more information (CLI verbose output, for starters) before someone can give you a more accurate solution.> effect that there are some issues with Asterisk applications which are > related to timers. What exactly is meant by that please? Is that whatthe zaptel-bsd drivers have the ztdummy timer and they're in ports and subversion. look for zaptel-bsd in the wiki. -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.openmalaysiablog.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
On Jul 26, 2006, at 8:58 AM, Phil Jordan wrote:> I tried sending this to asterisk-bsd a couple of days ago > > I've been using Asterisk in various versions on FreeBSD for some time > now, but I've only just got to messing around with ACD. > > I find I can't get any in-queue announcements to work, be they either > periodic or queue position announcements. I've read all of the recent > posts on this, and the closest thing to my problem I can find is a > chap on asterisk-users who reported something similar a month ago, > but worked around it by not selecting the "r" queue option. That > doesn't work for me (I wasn't using it anyway) - and I've dropped > all queue options as a test, still > to no avail.That chap is me ;) I tried this setup on linux, openbsd and osx and everywhere I get the same result. Removing the 'r' option from the Queue dialplan fixed the announcements. I did those tests on the debian packages and the svn 1.2 and trunk. Right now we are looking into recording the 'ringing sound' as moh mp3 :(> > Before I get round to posting my configs for critique, is this a > BSD port issue? I see stuff around on the net re the BSD port, to > the effect that there are some issues with Asterisk applications > which are related to timers. What exactly is meant by that please? > Is that what I'm suffering from here or is it something entirely > different? > > My environment is FreeBSD 5.3.18 (in production use), Asterisk 1.2.9.1 > from Ports, no hardware telephony cards (using a wholesale IAX > provider). Calls are being routed in via IAX2 and the agents are on > IAX2 hardphones, not that that latter makes any difference methinks.again no help, but the issue appears on platforms with sangoma E1 interfaces, junghanns quadbri cards and IAX2 only. ztdummy or not makes no difference.> > Many thanks in advance for any help that can be offered.If you find a way to get it working with the 'r' option, please share Michiel