[asterisk-dev] musiconhold

[Aaron Paxson]

Probably, the most common, is that you'll need to compile Zaptel, even if you do not use Digium hardware, for the timing.  Otherwise:

Taken from asteriskguru.com:

------------------
2) NOTICE[1100258240]: res_musiconhold.c:260 monmp3thread: Request to schedule in the past?!?!


As you could see this one is related to music on hold.

The sound become very choppy, slow, even metallic


1. The reason could be in the mpg123 package. It has a bug that prevents it from freeing up memory that it no longer needs. This is the so called memory leak. What actually happen is that the program steals more and more memory and finally the system will crashes, because the lack of memory.

Possible solution is to use the Native Asterisk format_mp3 for the Music on Hold instead of mpg123

The format_mp3 comes with the asterisk-addons package. Also if you decide to use it, first be sure that you have been removed mpg123 from your system.

Other options is to use rawplayer instead of mpg123.

Rawplayer is a simple replacement, which could be used to stream raw music files, in place of the mpg123
It is the most efficient way to implement Music On Hold, because it does not have the problem with the memory leaking

Rawplayer comes with the asterisk package

Installing rawplayer

* go to asterisk source dir and then to 'contrib/utils/' and compile the player
o gcc -O2 rawplayer.c -o /usr/bin/rawplayer
+ This will compile and install rawplayer at /usr/bin 
* edit /etc/asterisk/musiconhold.conf and change
o default => custom:/var/lib/asterisk/mohraw,/usr/bin/rawplayer
+ in /var/lib/asterisk/mohraw we will store raw MOH files 

For the converting of the files we will use sox

* convert MP3 to RAW
o sox -c 1 filename.mp3 -t raw -r 8000 -c 1 -s -w filename.raw 
* copy RAW file to mohraw dir
o cp filenam.raw /var/lib/asterisk/mohraw 



2. Other possible reason for the message Request to schedule in the past?!?! could be a timing issue, as a Zaptel timing issue.

Especially if you want to use MeetMe with Music On Hold you will need a timing source, regardless of the kernel.

If you do not use Digium hardware and you are using kernel earlier then 2.6, you need to have either ztdummy or zaprtc module running.

If you are using kernels 2.6.x and up, the ztdummy module will use the processor as a timing source

If you use Digium hardware, then you do not need ztdummy or zaprtc module.
  ----- Original Message ----- 
  From: Juergen John 
  To: asterisk-dev at lists.digium.com 
  Sent: Monday, July 31, 2006 6:11 AM
  Subject: [asterisk-dev] musiconhold


  Hi,
  I´ve a problem with musiconhold.
  I use Asterisk on UBUNTU version 1.2.7.1

  When I dial an extension with musiconhold, the following log appears:

  -- Executing WaitMusicOnHold("SIP/222-4236", "30") in new stack
      -- Started music on hold, class 'default', on channel 'SIP/222-4236'
      -- Stopped music on hold on SIP/222-4236
    == Spawn extension (chef, 223, 2) exited non-zero on 'SIP/222-4236'
  Jul 30 05:11:46 NOTICE[4568]: res_musiconhold.c:507 monmp3thread:
  Request to schedule in the past?!?!


  Any ideas?

  Regards

  Jürgen


------------------------------------------------------------------------------


  _______________________________________________
  --Bandwidth and Colocation provided by Easynews.com --

  asterisk-dev mailing list
  To UNSUBSCRIBE or update options visit:
     http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20060731/7a65ab6f/attachment.htm