[ previous ] [ next ] [ threads ]
 To : 
 From :  ZZ Wave <zzwave@g...>
 Subject :  Re: [yate] trancoding in Yate
 Date :  Thu, 1 Mar 2012 14:36:37 +0400
Everything is OK only when I have one same codec both on trunk and client.
If I set alaw only on trunk and mulaw only on client, there is no voice at
all.

I don't use rtp_forward=enable option in regexroute.

2012/3/1 Paul Chitescu 

> Hi!
>
> Yate supports internally G.711 (both mulaw and alaw) and through an
> embedded
> library iLBC. A-Law to mu-Law transcoding should always work.
>
> Modules that depend on external libraries add support for GSM, SPEEX and
> AMR-
> NB.
>
> There are no G.729 or G.726 codecs in Yate although for G.729 and G.723
> some
> third party modules exist. Using them is subject to specific patent
> license.
>
> Are you perchance using rtp_forward? In that case the RTP is sent directly
> between endpoints so Yate cannot do any transcoding.
>
> Paul
>
>
> On Thursday 01 March 2012 12:05:46 pm ZZ Wave wrote:
> > Which formats can be transcoded by Yate? g729 to alaw, g726 to alaw, even
> > mulaw to alaw seems to fail :(
>
>



Everything is OK only when I have one same codec both on trunk and client. If I set alaw only on trunk and mulaw only on client, there is no voice at all.

I don't use rtp_forward=enable option in regexroute.

2012/3/1 Paul Chitescu <paulc@v...>
Hi!

Yate supports internally G.711 (both mulaw and alaw) and through an embedded
library iLBC. A-Law to mu-Law transcoding should always work.

Modules that depend on external libraries add support for GSM, SPEEX and AMR-
NB.

There are no G.729 or G.726 codecs in Yate although for G.729 and G.723 some
third party modules exist. Using them is subject to specific patent license.

Are you perchance using rtp_forward? In that case the RTP is sent directly
between endpoints so Yate cannot do any transcoding.

Paul


On Thursday 01 March 2012 12:05:46 pm ZZ Wave wrote:
> Which formats can be transcoded by Yate? g729 to alaw, g726 to alaw, even
> mulaw to alaw seems to fail :(