For what it's worth, the Redhat mpg321->mpg123 trickery has been well
documented on this list. See the archives for multiple references to
this.
Dave
=====================================================================
David C. Troy [EMAIL PROTECTED] 410-384-2500 Sales
ToadNet - Want to go fast? 410-544-1329 FAX
570 Ritchie Highway, Severna Park, MD 21146-2925 www.toad.net
On Sun, 14 Sep 2003, Rich Adamson wrote:
> Music on hold problem solved... needs to be in an FAQ somewhere!!!
>
> After spending many hours trying to diagnose the MOH problem, it turned
> out to be the mpg123 code from the RedHat site. My * machine is RH9 with
> no mpg123 (or mpg321) installed by default. Searching the RedHat site
> found the rpm needed, however RedHat has substituted an incompatible
> version without any notations of having done that. (The code that gets
> installed is mgp321 with links that make it look like mpg123.)
>
> The corrective action involved removing all occurances of mpg123 and
> mpg321 from the linux box (including sym links), and installing the
> correct software from:
> www.mpg123.de/mpg123/precompiled/mpg123-0.59q-1.i386.rpm
> then, "cp /usr/local/bin/mpg123 /usr/bin/mpg123"
> and MOH worked fine.
>
> As a side note for those that might have the same problem and searched
> the archives, other people have had this same problem, however finding
> the steps necesary to correct this was not easy.
>
> The symptom of this problem is... when placing a call on hold and expecting
> music on hold, rather then hearing music one hears a low-level rumbling
> sound. The CLI interface would show:
> Started music on hold, class 'default', on Zap/1-1
> but one would only hear this rumbling sound.
>
> Music on hold also relies on routines that are installed when certain Digium
> hardware cards are installed (such as the X100P). If one of their cards are
> not installed, then the user must uncomment the "# ztdummy" line (around
> line 90) in the Makefile located in the zaptel source directory, do a
> "make clean" followed by a "make install" to obtain the needed routines.
> If that is successful, then "/sbin/lsmod" will display a list of modules
> that are running when * is active which must include the ztdummy entry. If
> that entry is not shown, then execute "/sbin/insmod ztdummy".
>
> There was also assumptions made by several people that suggested an entry
> in the extensions.conf file was needed, like:
> exten => 3000,2,MusicOnHold(default)
> or
> exten => 3000,2,SetMusicOnHold,default
> or
> exten => 3000,2,mp3player(/var/lib/asterisk/mohmp3/sample-hold.mp3)
>
> These statments are NOT required at all. Apparently, they do provide
> a way to specify a certain music directory and/or file on a "per extension"
> basis, but they are optional and not required.
>
> The only configuration statement that was needed to make MOH work for
> extensions was one in the musiconhold.conf file like:
> default => mp3:/var/lib/asterisk/mohmp3
>
> With the above statement active, ALL extensions are provided music on hold
> without further configuration statements.
>
> Hope this helps others with the same problem.
>
> Rich
> ------------------------
> > On Sat, 13 Sep 2003, Rich Adamson wrote:
> >
> > > Thanks John, but the question is not regarding the server. MOH is 'not'
> > > working with the C7960's. If you wouldn't mind, read through the remainder
> > > of the stuff below. Everything seems to suggest it should be working, but
> > > the question was oriented around the error message "sound device: Resource
> > > temporarily unavailable" (which obviously pertains to the server, and I
> > > don't care about the server). Would the server's sound device issue be
> > > impacting the inability of the C7960's to hear MOH?
> > >
> > > Rich
> > > -------------------------------
> > >
> > > > Nope, you only need a sound board if you want to hear
> > > > things on the * server
> > > -------------------------------
> > > > On Sat, Sep 13, 2003 at 05:05:32PM -0600, Rich Adamson wrote:
> > > > >
> > > > > Does anyone know whether the linux machine running * have to have a
> > > > > sound card on it in order for musiconhold to work for sip phones?
> > > > >
> > > > > I've tried about everything (including tons of google searching) to get
> > > > > it to work, and nothing.
> > > > >
> > > > > When a call is placed on hold between two C7960's, the CLI indicates:
> > > > > -- Executing Dial("SIP/3002-c418", "SIP/3000|20") in new stack
> > > > > -- Called 3000
> > > > > -- SIP/3000-56a0 is ringing
> > > > > -- SIP/3000-56a0 answered SIP/3002-c418
> > > > > -- Attempting native bridge of SIP/3002-c418 and SIP/3000-56a0
> > > > > -- Started music on hold, class 'default', on SIP/3002-c418
> > > > > -- Stopped music on hold on SIP/3002-c418
> > > > > == Spawn extension (from-sip, 3000, 1) exited non-zero on 'SIP/3002-c418'
> > > > >
> > > > > If I do a "ps ax" to see what's running, I see:
> > > > > 16243 pts/1 S 0:00 /usr/bin/mpg123 -q -s --mono -r 8000 -b 2048
> > > > > For-You.
> > > > >
> > > > > If I go to the * console and listen to "For-You", it plays through the
> > > > > speakers
> > > > > just fine.
> > > > >
> > > > > However, after starting * with -vvvvvc, I see:
> > > > >
> > > > > [chan_oss.so] => (OSS Console Channel Driver)
> > > > > WARNING[1074504864]: File chan_oss.c, Line 974 (load_module): XXX I don't
> > > > > work r
> > > > > ight with non-full duplex sound cards XXX
> > > > > == Registered channel type 'Console' (OSS Console Channel Driver)
> > > > > == Parsing '/etc/asterisk/oss.conf': Found
> > > > > WARNING[1142127920]: File chan_oss.c, Line 232 (sound_thread): Read error on
> > > > > sou
> > > > > nd device: Resource temporarily unavailable
> > > > > <snip>
> > > > > [app_mp3.so] => (Silly MP3 Application)
> > > > > == Registered application 'MP3Player'
> > > > > <snip>
> > > > >
> > > > >
> > > > > I can't seem to find any other reason for MOH to not work. If someone has
> > > > > MOH working, would it be possible for you to send me a "sip debug" listing
> > > > > of what's going on so I can compare it to mine? (offlist to [EMAIL
> > > > > PROTECTED])
> > > > >
> > > > > If anyone can think of anything more I can try it would be greatly
> > > > > appreciated.
> > > > >
> > > > > This system does have two X100P cards, everything else is working fine, its
> > > > > just the MOH that won't work.
> > > > >
> > > > > Thanks
> > > > > Rich
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Asterisk-Users mailing list
> > > > > [EMAIL PROTECTED]
> > > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > > _______________________________________________
> > > > Asterisk-Users mailing list
> > > > [EMAIL PROTECTED]
> > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> > > ---------------End of Original Message-----------------
> > >
> > >
> > > _______________________________________________
> > > Asterisk-Users mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> >
> > _______________________________________________
> > Asterisk-Users mailing list
> > [EMAIL PROTECTED]
> > http://lists.digium.com/mailman/listinfo/asterisk-users
>
> ---------------End of Original Message-----------------
>
>
> _______________________________________________
> Asterisk-Users mailing list
> [EMAIL PROTECTED]
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
