[asterisk-users] Possible bug - queue doesn't play hold music

[Richard Mudgett]

> On Fri, 2012-12-14 at 15:16 +0000, Ishfaq Malik wrote:
> > Hi
> > 
> > Can someone else please check the following:
> > We have installed asterisk 1.8.18.0 onto our development and test
> > servers. They were previously on 1.8.7.0
> > 
> > When an inbound call executes a queue, I can see in the logs that
> > the
> > hold music is supposed to start playing but there is no sound. If
> > the
> > call is answered and the callee puts the caller on hold, I can see
> > the
> > same log message of hold music starting but this time the hold
> > music can
> > be heard.
> > 
> > This is happening on both installations of 1.8.18.0.
> > 
> > If other people are experiencing the same thing we can raise a bug
> > on
> > it.
> > 
> > Log excerpts below with my comments after a # symbol
> > 
> >     -- Executing [s at ethn-xxxxxxxxxx-work:4]
> >     Queue("SIP/x.x.x.x-00000061", "test-ish,Tn,,,600")
> >     -- Started music on hold, class 'default', on
> >     SIP/x.x.x.x-00000061                          #comment: no
> >     music heard
> >   == Using SIP RTP CoS mark 5
> >     -- SIP/101-00000062 is ringing
> >     -- SIP/101-00000062 is ringing
> >     -- SIP/101-00000062 is ringing
> >     -- SIP/101-00000062 is ringing
> >     -- SIP/101-00000062 is ringing
> >     -- SIP/101-00000062 answered SIP/x.x.x.x-00000061
> >     -- Stopped music on hold on SIP/x.x.x.x-00000061
> > [2012-12-14 14:44:04] ERROR[26568]: chan_sip.c:29941 setup_srtp: No
> > SRTP module loaded, can't setup SRTP session.
> >     -- Started music on hold, class 'default', on
> >     SIP/x.x.x.x-00000061
> >                                                  #comment: music
> >     can be heard
> > [2012-12-14 14:44:12] ERROR[26568]: chan_sip.c:29941 setup_srtp: No
> > SRTP module loaded, can't setup SRTP session.
> >     -- Stopped music on hold on SIP/x.x.x.x-00000061
> >   == Spawn extension (ethn-xxxxxxxxxx-work, s, 4) exited non-zero
> >   on 'SIP/x.x.x.x-00000061'
> > 
> 
> Really could do with a second opinion on this issue as it would quite
> a
> serious bug if it is one...

The incoming call leg does not appear to be answered yet so I would not
expect the caller to be able to hear MOH.

Richard