Re: [asterisk-users] Queue announcement issues
On 07/27/06 03:28 Phil Jordan said the following: Jul 26 20:05:22 DEBUG[16371] channel.c: Scheduling timer at 160 sample intervals Jul 26 20:05:22 DEBUG[16371] channel.c: Avoiding initial deadlock for 'IAX2/phil-5' Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Called IAX2/phil Jul 26 20:05:22 DEBUG[16371] channel.c: Generator got voice, switching to phase locked mode Jul 26 20:05:22 DEBUG[16371] channel.c: Scheduling timer at 0 sample intervals Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Call accepted by 82.11.45.110 (format gsm) Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Format for call is (gsm) Jul 26 20:05:22 VERBOSE[16371] logger.c: -- IAX2/phil-5 is ringing Jul 26 20:05:56 DEBUG[16371] chan_sip.c: Stopping retransmission on it does seem that IAX2/phil is still logged in as an agent of the queue, thus the caller is delivered to that agent and no hold times, position or periodic announcements are made. what does 'show queue hasbean' and 'show agents' say ? this may be the case because you have persistentagents=yes in queues.conf. -- Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](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 | +=+ ___ --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
[asterisk-users] Queue announcement issues
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 - ___ --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
Re: [asterisk-users] Queue announcement issues
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 the no, 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 what the 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. [EMAIL PROTECTED](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 | +=+ ___ --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
Re: [asterisk-users] Queue announcement issues
Thank you for replying, Dinesh.
Right, if all the cryptic comment I found just refers to the Zaptel
stuff, that isn't a problem. Thank you for the clarification. To
business:
My queue timeout is 240 seconds. My periodic announcement interval is
30 seconds. Queue position announcements are disabled (and anyway they
don't work either - which may be a clue).
After 90 plus seconds in the verbose log example to follow, the caller
hangs up, having heard MoH for the duration and the agent's phone
having been ringing just fine. Any insight about where to proceed next
would be most welcome. Thanks.
This is my queue statement in extensions.conf:
exten = s,n,Queue(hasbean-sales,Hthn|||240)
This is my queues.conf:
[general]
persistentmembers = yes
[hasbean-sales]
strategy = ringall
maxlen=0
announce-holdtime = no
announce-frequency = 0
announce = hasbean/salescall
periodic-announce = hasbean/que
periodic-announce-frequency = 30
joinempty = strict
leavewhenempty = strict
. and another queue which is identical in all but name.
This is the verbose log from the call:
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Accepting
AUTHENTICATED call from 193.111.200.135:
requested format = ulaw,
requested prefs = (),
actual format = alaw,
host prefs = (alaw|ilbc|gsm|ulaw),
priority = mine
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Executing
Goto(IAX2/193.111.200.135:4569-4, hasbean-incoming|s|1) in new stack
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Goto (hasbean-incoming,s,1)
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Executing
Answer(IAX2/193.111.200.135:4569-4, ) in new stack
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Executing
Set(IAX2/193.111.200.135:4569-4, TIMEOUT(digit)=5) in new stack
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Digit timeout set to 5
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Executing
Set(IAX2/193.111.200.135:4569-4, TIMEOUT(response)=30) in new stack
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Response timeout set to 30
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Executing
BackGround(IAX2/193.111.200.135:4569-4, hasbean/initialmessage) in
new stack
Jul 26 20:05:13 DEBUG[16371] channel.c: Scheduling timer at 160 sample
intervals
Jul 26 20:05:13 VERBOSE[16371] logger.c: -- Playing
'hasbean/initialmessage' (language 'en')
Jul 26 20:05:13 DEBUG[16371] chan_iax2.c: Ooh, voice format changed to 8
Jul 26 20:05:17 DEBUG[16371] channel.c: Scheduling timer at 0 sample intervals
Jul 26 20:05:17 DEBUG[16371] pbx.c: Oooh, got something to jump out
with ('1')!
Jul 26 20:05:22 VERBOSE[16371] logger.c: == CDR updated on
IAX2/193.111.200.135:4569-4
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Executing
Goto(IAX2/193.111.200.135:4569-4, hasbean-sales|s|1) in new stack
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Goto (hasbean-sales,s,1)
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Executing
Set(IAX2/193.111.200.135:4569-4, CALLERID(name)=Sales Queue) in
new stack
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Executing
Queue(IAX2/193.111.200.135:4569-4, hasbean-sales|Hthn|||240) in
new stack
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Started music on hold,
class 'default', on IAX2/193.111.200.135:4569-4
Jul 26 20:05:22 DEBUG[16371] channel.c: Scheduling timer at 160 sample
intervals
Jul 26 20:05:22 DEBUG[16371] channel.c: Avoiding initial deadlock for
'IAX2/phil-5'
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Called IAX2/phil
Jul 26 20:05:22 DEBUG[16371] channel.c: Generator got voice, switching
to phase locked mode
Jul 26 20:05:22 DEBUG[16371] channel.c: Scheduling timer at 0 sample intervals
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Call accepted by
82.11.45.110 (format gsm)
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- Format for call is (gsm)
Jul 26 20:05:22 VERBOSE[16371] logger.c: -- IAX2/phil-5 is ringing
Jul 26 20:05:56 DEBUG[16371] chan_sip.c: Stopping retransmission on
'[EMAIL PROTECTED]' of Request 102:
Match Found
Jul 26 20:06:03 DEBUG[16371] chan_sip.c: Auto destroying call
'[EMAIL PROTECTED]'
Jul 26 20:06:56 DEBUG[16371] chan_sip.c: Stopping retransmission on
'[EMAIL PROTECTED]' of Request 102:
Match Found
Jul 26 20:06:57 DEBUG[16371] chan_iax2.c: Immediately destroying 4,
having received hangup
Jul 26 20:06:57 VERBOSE[16371] logger.c: -- Stopped music on hold
on IAX2/193.111.200.135:4569-4
Jul 26 20:06:57 DEBUG[16371] channel.c: Scheduling timer at 0 sample intervals
Jul 26 20:06:57 DEBUG[16371] chan_iax2.c: We're hanging up IAX2/phil-5 now...
Jul 26 20:06:57 VERBOSE[16371] logger.c: -- Hungup 'IAX2/phil-5'
Jul 26 20:06:57 VERBOSE[16371] logger.c: == Spawn extension
(hasbean-sales, s, 2) exited non-zero on 'IAX2/193.111.200.135:4569-4'
Jul 26 20:06:57 DEBUG[16371] pbx.c: Function result is 'Sales Queue
07798614850'
Jul 26 20:06:57 DEBUG[16371] pbx.c: Function result is
Re: [asterisk-users] Queue announcement issues
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 ___ --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
