G.729 codec issue

Asterisk Asterisk Support
1

Hi all,
I have upgraded my asterisk to ver 1.2. Before the upgrade my asterisk machine was able to talk to g729 enabled clients but not any more. I am not sure what is causing this. I never got the chance to do “show translations” before upgrade and after the upgrade, below is the output:

[code]show translation
Translation times between formats (in milliseconds)
Source Format (Rows) Destination Format(Columns)

     g723   gsm  ulaw  alaw  g726 adpcm  slin lpc10  g729 speex  ilbc

g723 - - - - - - - - - - -
gsm - - 2 2 2 2 1 4 - 33 15
ulaw - 3 - 1 2 2 1 4 - 33 15
alaw - 3 1 - 2 2 1 4 - 33 15
g726 - 3 2 2 - 2 1 4 - 33 15
adpcm - 3 2 2 2 - 1 4 - 33 15
slin - 2 1 1 1 1 - 3 - 32 14
lpc10 - 4 3 3 3 3 2 - - 34 16
g729 - - - - - - - - - - -
speex - 4 3 3 3 3 2 5 - - 16
ilbc - 4 3 3 3 3 2 5 - 34 -[/code]

Please tell me what might be causing this issue?

2

Do you have ‘allow=g729’ set in sip.conf?

3

You obviously haven’t got a g729 codec installed. Had you previously bought a licence from Digium?

4

Actually, I got the problem solved. It was a problem within zultys. But since, I have already posted, what does the table mean which I have posted in my first post (above). Thanks again guys for all your help.

5

The table shows the time needed to transcode the audio stream from one codec to another, the source codecs are the rows, the destination codecs are the columns, this time is called translation cost; Asterisk do a codec transcoding (translation) when you have a call with legs using different codecs, reading the table you can see that to transcode from gsm to ulaw takes 2 milliseconds of time.

Regards.

Marco Bruni

6

can anyone publish “show translation” table with both g729 and speex codecs?

7

Thanks Marco. Now, I am experimenting with G.729 codec and this is what my “show translation” table shows:

[code]show translation
Translation times between formats (in milliseconds)
Source Format (Rows) Destination Format(Columns)

     g723   gsm  ulaw  alaw  g726 adpcm  slin lpc10  g729 speex  ilbc

g723 - 3 2 2 2 2 1 4 9 33 16
gsm 9 - 2 2 2 2 1 4 9 33 16
ulaw 9 3 - 1 2 2 1 4 9 33 16
alaw 9 3 1 - 2 2 1 4 9 33 16
g726 9 3 2 2 - 2 1 4 9 33 16
adpcm 9 3 2 2 2 - 1 4 9 33 16
slin 8 2 1 1 1 1 - 3 8 32 15
lpc10 10 4 3 3 3 3 2 - 10 34 17
g729 10 4 3 3 3 3 2 5 - 34 17
speex 10 4 3 3 3 3 2 5 10 - 17
ilbc 10 4 3 3 3 3 2 5 10 34 -[/code]

It clearly shows that my Asterisk has the capabilities to transcode but it is still not be able to connect calls from G.729 users. When a person from a G.729 enabled phone (or proxy) calls, I still get:

or when I call a G.729 proxy, I get:

I would appreciate some help here! Thanks! :smile:

8

Interesting, the results must be processor specific, 'cause I get

9

Yeah, they are. The show translation command shows the time it takes to do the translation. That will obviously depend on the speed of your processor, along with some other factors.

10

Some Desi,
to use the g.729 codec with Asterisk you need a license from Digium, have you it ?

Regards.

Marco Bruni

11

I got the same problem. My sip.conf have disallow=all allow=g729.
A Have already purchased the licenses from digium and installed:

linux1*CLI> show g729
0/0 encoders/decoders of 5 licensed channels are currently in use

But when a i try to call another extension, i received the message " No compatible codecs!".

I tryied whithout the disallow=all, only whit allow=g729 and works, but I guess asterisk is using another codec, because the " 0/0 encoders/decoders of 5 licensed channels are currently in use " remains the same.

Samebody have any idea ?

Regards,

Ivan

12

I have the exact smae prob as trewq above…i see the codec installed, and cli shows i have the codecs, etc, etc, etc…but any incoming alls give me the error no compatible codecs…

this is a major show stopper for me as the SIP provider I have requires G729.

I did have the g729 codecs from sometime in November, but I noticed that the codecs folders on the download site now have 30/1/08 on them, so i am taking it that that codecs have been rebuilt or something, but I do believe they are not the same as the ones I had from November (which did work properly).