Summary:ASTERISK-07490: With no one logged into the queue, there is no music on hold for the first caller to the queue.
Reporter:Bob Belcher (bbelcher)Labels:
Date Opened:2006-08-08 16:16:03Date Closed:2006-10-31 11:39:41.000-0600
Versions:Frequency of
Environment:Attachments:( 0) messages.zip
( 1) queues.conf
Description:I have a queue setup to allow callers into the queue when no one is logged in. When a caller calls in and there are no agents or devices in the queue, the first caller hears anouncements at the correct times that I have setup but hears no music on hold. The second person that calls in hears music on hold fine. If the first person hangs up, which they usually do because it sounds like they got disconnected, the second person becomes the first person and their music on hold goes away. If the first person waiting in the queue stays holding, they hear music on hold the moment an agent logs into the queue.


I have three phone stations setup for a small call center. The phone itself is not part of the queue. It is a cisco 7960 running SIP 7.4. When the tech gets here to answer phones, he has to log into the queue. The queue is using AgentCallbackLogin(|l) in the extensions.conf to log people on and off the queue. All agents are part of 1 queue. I will attach my queues.conf so that you can see how the queue is setup.
I have this same problem on my production 1.2.5 box as I do with my development 1.2.10 box. Each server is running Fedora Core 4. Besides server hardware differences the software is almost the same on each box as far as whats installed. The production server runs a pri card and the development box runs ztdummy interface. Music on hold "default" selection is running rawplayer. However, I have tried different formats and programs to run music on hold. Same thing happens on each program that is used to run music on hold. If you need any additional info, let me know I will provide you with what you need.
Comments:By: Joshua C. Colp (jcolp) 2006-08-08 16:56:04

Console output would also be nice to see.

By: Bob Belcher (bbelcher) 2006-08-08 22:45:13

Console output shows that music on hold is being played. Sorry I forgot to mention that. It actually shows that it is doing the MOH correctly and that there is no problems. Even with debug and verbosity set to 4. However, if you want to see it, I will get it for you.

By: Bob Belcher (bbelcher) 2006-08-09 08:02:23

Connected to Asterisk 1.2.10 currently running on asterisk (pid = 21222)
Verbosity is at least 3
   -- Registered SIP '73333' at port 7942 expires 3600
   -- Executing Answer("SIP/73333-09fafc88", "") in new stack
   -- Executing Ringing("SIP/73333-09fafc88", "") in new stack
   -- Executing Wait("SIP/73333-09fafc88", "2") in new stack
   -- Executing Queue("SIP/73333-09fafc88", "tech") in new stack
   -- Started music on hold, class 'default', on channel 'SIP/73333-09fafc88'
   -- Stopped music on hold on SIP/73333-09fafc88
   -- Playing 'queue-youarenext' (language 'en')
   -- Told SIP/73333-09fafc88 in tech their queue position (which was 1)
   -- Playing 'queue-thankyou' (language 'en')
   -- Started music on hold, class 'default', on channel 'SIP/73333-09fafc88'
   -- Stopped music on hold on SIP/73333-09fafc88
   -- Playing periodic announcement
   -- Playing 'queue-periodic-announce' (language 'en')
   -- Started music on hold, class 'default', on channel 'SIP/73333-09fafc88'
   -- User disconnected from queue tech when they almost made it
 == Spawn extension (intern, 850, 4) exited non-zero on 'SIP/73333-09fafc88'
   -- Stopped music on hold on SIP/73333-09fafc88

Here is the console output. It shows my phone turning on and registering then me calling the queue. Shows music on hold starting up however all I heard was you are first in the queue then dead air. Waited for the first periodic announcement to play. I heard it start up and then back to dead air. That is when I hung up.

By: Serge Vecher (serge-v) 2006-08-09 10:11:51

let's see if anything turns up if we turn debug log on. Also, since you are using sip image on a Cisco, we'll turn sip debug on too. Try this:
1) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
2) restart Asterik.
3) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
sip debug
4) Save complete console log to file and _attach_ said file to the bug.

By: Bob Belcher (bbelcher) 2006-08-10 09:27:06

Here is a log file that has all the debug info you requested. It only shows a call to the queue playing the first queue anouncement then I waited until the second queue anouncement to play. Then I also checked music on hold to make sure it was working and it is.

By: Scott Chirpich (schirpich) 2006-10-07 13:05:00

Gentoo 2006 Stage 1 install
libpri 1.2.2-r2
zaptel 1.2.5-r1
asterisk 1.2.7_p1-r1

Module                  Size  Used by
wct4xxp                99648  96
zaptel                186500  225 wct4xxp

I have precisley the exact same issue as this poster.  Error log's show literally nothing at all. According to asterisk, everything is fine and dandy.  But in my case its a little more severe.  We do approx 900 calls in a day through this system.

I've even tried disabling the queue announcements all together and it still goes to silence for the person in the queue.   The really strange thing is, that every so often the music will chime in for about 1-2 seconds and goes away again if you wait on hold long enough. The announcements however will chime in always when specified.

I'll admit, I am fairly new to asterisk.  But I'm pretty sure this isn't something I've caused by syntax or misconfiguration.  At least I hope not.

It looks like it's been a while since anyone has brought this issue up,  any updates?

By: Serge Vecher (serge-v) 2006-10-09 11:10:15

well, there have been updates to musiconhold since release, I can tell you that much. Please install Asterisk release from the tarballs available on asterisk.org and see if the issue still exists there.

By: jmls (jmls) 2006-10-31 11:25:18.000-0600

any news on this ? Did work for you ?

By: Scott Chirpich (schirpich) 2006-10-31 11:35:29.000-0600

Yes, I can confirm.  Upgrading to 1.2.13 did resolve my issues.  Used all my same config's and everything is working as it should as of now.  Been running 1.2.13 for the past two weeks without any hiccups.

Good luck to you all with your issues.

By: jmls (jmls) 2006-10-31 11:39:40.000-0600

confirmed fixed in 1.2.13