[asterisk-dev] Fwd: [asterisk-users] Asterisk 1.8.7.1 forcing uLaw bug NOT fixed yet

[Matthew Jordan]

There is already an issue in JIRA tracking this:

https://issues.asterisk.org/jira/browse/ASTERISK-18993

Per David, this appears to be related to dialing with the MOH parameter.  If you are experiencing this in the same scenario, use that issue for your tracking and/or to contribute towards the solution.  If you are experiencing this in a different scenario, please file an issue and include the relevant portions of extensions.conf, sip.conf, and preferably relevant portions of a DEBUG log showing when it begins and ends.

Thanks

Matt

----- Original Message -----
> From: "CDR" <venefax at gmail.com>
> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> Sent: Thursday, December 29, 2011 8:34:32 AM
> Subject: Re: [asterisk-dev] Fwd: [asterisk-users] Asterisk 1.8.7.1 forcing uLaw bug NOT fixed yet
> 
> We need to fix this. This is clearly a bug (not the message, the real
> reason).
> I am being affected as well.
> 
> On Thu, Dec 29, 2011 at 12:02 AM, Bruce B <bruceb444 at gmail.com>
> wrote:
> > On Wed, Dec 28, 2011 at 4:29 PM, Kevin P. Fleming
> > <kpfleming at digium.com>
> > wrote:
> >>
> >> On 12/28/2011 03:20 PM, Bruce B wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> Can this bug be fixed? Apparently the offending code is what is
> >>> mentioned below by Danny Nicholas.
> >>
> >>
> >> This is incorrect. The code posted below is what generates the
> >> warning
> >> message, but it (correctly) generates the message when a frame is
> >> written to
> >> a channel in a format that the channel is not expecting.
> >>
> >> Something is causing these frames to be sent; that is the real
> >> cause of
> >> this bug. Other than the warning messages, though, I haven't seen
> >> anyone
> >> report an actual *problem* (one-way audio, no audio, bad audio,
> >> etc.). If
> >> the only problem is some annoying warning messages, and calls are
> >> otherwise
> >> successful, this is not going to be a high priority to get fixed.
> >>
> > It's filling up the logs for sure leading to much confusion while
> > looking
> > through. Each call generates like 100 lines of this error. I have
> > seen some
> > BUSY calls and assuming it's the same problem but I can't confirm
> > yet.
> >
> > Regards,
> >
> > --
> > _____________________________________________________________________
> > -- Bandwidth and Colocation Provided by http://www.api-digital.com
> > --
> >
> > asterisk-dev mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>