[Home]

Summary:ASTERISK-15681: [regression] Context option in queue.conf no longer works
Reporter:Mike Tesliuk (pruonckk)Labels:
Date Opened:2010-02-23 14:25:14.000-0600Date Closed:2011-06-07 14:00:47
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Applications/app_queue
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hi guys,

Im implementing a queue on asterisk 1.6.2.4 , and when i define a context= option on my queues.conf and create the context on extensions.conf nothing happens when i press the exten.




****** ADDITIONAL INFORMATION ******

below my confs.

(queues.conf)
[atendimento]
musicclass = default
context = queuereturn
strategy = fewestcalls
wrapuptime=0
announce-frequency = 165
queue-youarenext =
queue-thereare  =
queue-callswaiting =
queue-holdtime =
queue-minutes =
queue-seconds =
queue-thankyou = /var/lib/asterisk/sounds/pt_BR/i-conecta/obrigado_por_ligar
queue-reporthold =
monitor-format = gsm


on my (extensions.conf)

exten => _atendimento,1,NoOp(Chamada destinada a fila ${EXTEN} - origem: ${CALLERID(all)})
exten => _atendimento,n,Answer()
exten => _atendimento,n,Set(MONITOR_FILENAME=/var/spool/asterisk/monitor/${STRFTIME(${EPOCH},,%Y%m%d)}/atendimento-${CALLERID(num)}-${STRFTIME(${EPOCH},,%Y%m%d%H%M%S)})
exten => _atendimento,n,Macro(VerificaDir)
exten => _atendimento,n,NoOp(GRAVACAO EM ${MONITOR_FILENAME})
exten => _atendimento,n,Queue(atendimento,tk,,,900)
exten => _atendimento,n,GotoIf($["${QUEUESTATUS}" == "TIMEOUT"]?filas,ocupado,1)
exten => _atendimento,n,GotoIf($["${QUEUESTATUS}" == "FULL"]?filas,ocupado,1)
exten => _atendimento,n,Hangup()


[teste]
exten => _X,1,NoOp(Usuario ${CALLERID(num)} optou por sair da fila)
exten => _X,n,Goto(filas,suporte,1)


when i call to the queue and i press any digit, nothing happens, on debug mode i can get the dtmf .

[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: Sending dtmf: 57 (9), at 189.127.48.6
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: Sending dtmf: 57 (9), at 189.127.48.6
[Feb 23 19:20:48] DEBUG[5250] pbx.c: return at end of func
[Feb 23 19:20:48] DEBUG[5250] app_queue.c: There are 0 available members.
[Feb 23 19:20:48] DEBUG[5250] app_queue.c: It's not our turn (SIP/1113-0000001a).
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)
[Feb 23 19:20:48] DEBUG[5250] rtp.c: - RTP 2833 Event: 00000009 (len = 4)

[Feb 23 19:20:48] DEBUG[5250] rtp.c: Difference is 800, ms is 120

and i have a lot of this messages:
[Feb 23 19:20:48] DEBUG[5250] channel.c: Internal timing is disabled (option_internal_timing=0 chan->timingfd=30)
Comments:By: Mike Tesliuk (pruonckk) 2010-02-23 15:03:47.000-0600

Just to explain, i post a queue.conf that say context=queuereturn and i put a extension named [teste], i have another queue with the same configuration that point to this context, im sorry for my mistake, the problem continue whatever...
By: Mike Tesliuk (pruonckk) 2010-02-23 16:08:19.000-0600

I make a test now with asterisk 1.4.29.1 and this option work without problem to me ? was this feature removed from asterisk 1.6 ?
By: Leif Madsen (lmadsen) 2010-02-25 12:17:24.000-0600

This feature would not have been removed. I only see this listed in the [general] section, but since you say this works in 1.4.29 (with the same configuration I presume), then this is a regression.
By: Mike Tesliuk (pruonckk) 2010-02-26 05:57:23.000-0600

Shure, with 1.4.29.1 a use the same configuration without any problem, you say that you just see this option listed in the general section.

In the queues.conf (from make sampmles), i have a sample use of this option behind the markq context, so i presume that i can (and i need this) set a diferent context from each one queue that i have.
By: Tilghman Lesher (tilghman) 2010-03-10 17:58:47.000-0600

A note:  The extension '_atendimento' is probably not what you want.  It is equivalent to:

exten => _ate[2-9]dime[2-9]to

I made a single change to your configuration above, and it works fine:  I changed your context named "teste" to "queuereturn", since that's what context points to in your queues.conf, and it works perfectly.  What am I missing?

   -- Executing [8168@digium:1] Answer("SIP/103-00000000", "") in new stack
   -- Executing [8168@digium:2] Queue("SIP/103-00000000", "atendimento,tk,,,900") in new stack
   -- Started music on hold, class 'default', on channel 'SIP/103-00000000'
   -- Stopped music on hold on SIP/103-00000000
   -- Told SIP/103-00000000 in atendimento their queue position (which was 1)
   -- <SIP/103-00000000> Playing '/var/lib/asterisk/sounds/pt_BR/i-conecta/obrigado_por_ligar.gsm' (language 'en')
   -- Executing [2@queuereturn:1] NoOp("SIP/103-00000000", "Usuario 103 optou por sair da fila") in new stack
   -- Executing [2@queuereturn:2] Goto("SIP/103-00000000", "filas,suporte,1") in new stack
   -- Goto (filas,suporte,1)
[Mar 10 17:55:20] WARNING[5985]: pbx.c:4358 __ast_pbx_run: Channel 'SIP/103-00000000' sent into invalid extension 'suporte' in context 'filas', but no invalid handler
By: Mike Tesliuk (pruonckk) 2010-03-11 13:40:00.000-0600

I try again on a virtual machine with asterisk 1.6.1.16

Asterisk 1.6.1.16 built by root @ teste-asterisk-1 on a i686 running Linux on 2010-02-23 18:20:13 UTC


-> queues.conf

[general]

[teste]
musicclass = default
joinempty=yes
context = teste
strategy = fewestcalls
wrapuptime=0
announce-frequency = 165



--> extensions.conf

[filas]
exten => teste,1,NoOp(Chamada destinada a fila ${EXTEN} - origem: ${CALLERID(all)})
exten => teste,n,Answer()
exten => teste,n,Queue(teste,tk,,,900)
exten => teste,n,GotoIf($["${QUEUESTATUS}" == "TIMEOUT"]?filas,ocupado,1)
exten => teste,n,GotoIf($["${QUEUESTATUS}" == "FULL"]?filas,ocupado,1)
exten => teste,n,Hangup()


[teste]
exten => 2,1,NoOp(Usuario ${CALLERID(num)} optou por sair da fila)
exten => 2,n,Goto(filas,suporte,1)


In this situation my user cant get out of the queue.


Just to remember i get this working prefectly on 1.4.28 with the same configuration (im using 1.4.28 because i need the openr2 patch)


have you tried with 1.6.2.4 ????
By: Tilghman Lesher (tilghman) 2010-03-22 15:19:45

There is no difference between the version I tried and 1.6.2.4 in the Queue application.  I cannot reproduce the issue at all.

If somebody else can reproduce this issue, I'm happy to hear about it, but it appears you've left out a critical piece of information that is required to reproduce the issue.
By: Tilghman Lesher (tilghman) 2010-03-22 15:23:43

One thing pops to mind.  On the link on which you're having this problem, can you receive DTMF at all?  This might just be a DTMF issue and not a Queue issue.
By: Tilghman Lesher (tilghman) 2010-03-31 16:19:03

No response from reporter.