[asterisk-users] MOH Codec Issue - Fixed
Nick Brown
Nick at ipera.com.au
Tue Nov 13 23:17:09 CST 2007
I recompiled a version of Zaptel to no avail in an attempt to find a quick
fix. This did not help, however have since upgraded the box to Asterisk
1.4.13 and the issue has disappeared. As such I put it down to either being;
1. Zaptel was broken, I should have however recompiled Asterisk after
recompiling Zap (Opposed to being impatient and frustrated), or
2. There is a bug in 1.4.7. I haven't had time to try and reproduce it,
plus it would be a purely academic project as if there was a bug it has
since been fixed.
Thanks for the suggestions Paul.
Nick.
On 13/11/07 4:48 PM, "Paul Hales" wrote:
> Is it possibly a funny zaptel issue? Paul Hales AsteriskIT > > On Tue,
2007-11-13 at
> 15:04 +1100, Nick Brown wrote: > >> Afternoon All, > >> > >> Today rolled a
> pre-production box from Trunk back to 1.4.7 (In an > >> attempt to get a
> working SCCP channel). During the process Music On > >> Hold appears to have
> died (Not, just when calling from a SCCP device, > >> but coming in on SIP
> also). > >> > >> CLI is showing > >> > >> -- Executing
> [XXXXXXXX at unauthed-inbound:2] > >> MusicOnHold("SIP/10.97.1.33-09f0cfc8",
> "sounds") in new stack > >> [Nov 13 15:00:14] WARNING[5461]: channel.c:2964
> set_format: Unable to > >> find a codec translation path from alaw to
> unknown > >> [Nov 13 15:00:14] WARNING[5461]: res_musiconhold.c:702
> moh_alloc: > >> Unable to set channel 'SIP/10.97.1.33-09f0cfc8' to format
> 'unknown' > >> -- Started music on hold, class '?S?', on channel > >>
> 'SIP/10.97.1.33-09f0cfc8' > >> [Nov 13 15:00:14] WARNING[5461]:
> res_musiconhold.c:575 moh0_exec: > >> Unable to start music on hold (class
> 'sounds') on channel > >> SIP/10.97.1.33-09f0cfc8 > >> > >> Have attempted to
> use an alternate Music On Hold context and forced a > >> format= within
> musiconhold.conf. > >> > >> Otherwise all other audio (Playback, voice etc)
> seems fine. > >> > >> Anyone seen this before? Can not see anything in the
> tracker regarding > >> this issue in 1.4.7 specifically. > >> > >> Cheers >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071114/86baecf3/attachment.htm
More information about the asterisk-users
mailing list