asterisk users - Dec 2011 - Asterisk 1.8.7.1 forcing uLaw bug NOT fixed yet

Hi everyone,

I see that there was a bug in version 1.8.5.x and people were advised to
move to 1.8.7.1 but now I have 1.8.7.1 and experiencing the same problem.
Here is the output:

*"chan_sip.c: Asked to transmit frame type ulaw, while native formats is
0x100 (g729) read/write = 0x100 (g729)/0x100 (g729)"*
*
*
Now, I see an update to 1.8.8.1 is available. I am wondering if this issue
is fixed in this version or not? Furthermore, has anyone tested 1.8.8.1
yet? Are there any other problems to that? It's frustrating as I see we
should once again move back to 1.6x and forget about 1.8x all together.

Any input is appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20111228/4bce1e43/attachment.htm>

The issue is not fixed in 1.8.8.0 either.

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces
at lists.digium.com] On Behalf Of Bruce B
Sent: Wednesday, December 28, 2011 3:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Asterisk 1.8.7.1 forcing uLaw bug NOT fixed yet

Hi everyone,

I see that there was a bug in version 1.8.5.x and people were advised to move to
1.8.7.1 but now I have 1.8.7.1 and experiencing the same problem. Here is the
output:

"chan_sip.c: Asked to transmit frame type ulaw, while native formats is
0x100 (g729) read/write = 0x100 (g729)/0x100 (g729)"


Now, I see an update to 1.8.8.1 is available. I am wondering if this issue is
fixed in this version or not? Furthermore, has anyone tested 1.8.8.1 yet? Are
there any other problems to that? It's frustrating as I see we should once
again move back to 1.6x and forget about 1.8x all together.

Any input is appreciated.