Good sound quality… That’s what’s so nice about G.729… It has both low bandwidth and good quality.
Most handsets support it (and some, such as the Zyxel wireless handsets, actually work better with it). Quite a lot of softphones, especially free ones, don’t.
No. If the other SIP system can’t handle G.729, Asterisk will negotiate another codec, as long as you have other codecs enabled.
If the other system can’t handle it, Asterisk will negotiate a switch to a codec supported on both systems.
Yes. All you have to do is enable the other codecs in your sip.conf and iax.conf files.
I have been very happy with G.729 and feel it is definitely worth the $10, especially if used on a typical home DSL connection (1024k down/256k up, for example), where 64kbps connections quickly add up and saturate the upload bandwidth. As I also mentioned, it helps a lot with some handsets and alongside the latest firmware was instrumental in making our Zyxel P2000W handsets useable (if not fantastically so!)
What’s the saying “a gentleman and a scholar”? Thanks, helps indeed. It would be nice of Digium incorporated your response into their product description (for idiots such as myself) - just makes it clear what a truly good benefit & deal their g729 offering is.
We purchased four licenses with our TDM400P under the vague impression of the things you covered. Good to have them confirmed and better understood.
This seems to be an incredibly common question, If any one wishes to add to the comment feel free but I feel this should not get lost in the forum especially as it picks up speed.
One last question/confusion regarding licensing under Asterisk:
The Digium site suggests one per FXO channel you may be using to a PSTN (e.g. four for TDM400P w/4xFXO). However there is a wiki page at voip-info.org that suggests a very different and more expensive scenario (see end of article at … voip-info.org/wiki-Asterisk+G.729+Licensing) — which might be correct?
For most apps it is a one encoder one decoder. So I have sip phone a and fxo b going from sip g729 to fxo takes one transcoder for all of call, listening to voicemail takes a transcoder while you are listening to message or recording message. however few apps take more than one, monitor takes two do to the way the apps and channels work in asterisk. but for the most part you need a license for the max number of channels you will have up at any give time.
If running, for example, an Asterisk@Home distro which is CentOS v3.x (RHEL3) which shows configured for i686 (even though it is a Pentium 4 machine) - which codec binary should be downloaded … i686 or Pentium 4?
Is it possible to change the codec during the session? Like I receive a call with g729, detect fax and switch to ulaw or receve with ulaw, not detect fax and then switch to g729…
—quote—
Should you want to place 5 licenses on one machine and 5 on
another machine, please place two orders for 5 licenses each. Do not make one order for 10 licenses. Your registration number will be keyed to unlock X amount of licenses on one machine.
—quote—
Question:
Lets say you buy 5 licenses and then later find you need 5 more. Can you just buy another licsense for 5 more or do you need to buy a new license for 10? I’m assuming that you do because in the above ording instruction you would have simply purchased 10 individual licenses. If so what happens to the 5 you already have? Do you just kiss them good bye? Trade them in? Sell them on ebay?
I haven’t purchased any licenses so I’m not quite sure how Asterisk handles them. I was just curious.
I have a asterisk server up and running and am currently using IAX2 and some softphones to do some testing. I want to purchase and add the g729 codec on the test server. I do not think this will be much of a problem.
Question is:
If I purchase and install codec on this test server. If/when I want to upgrade to a Newer more powerful production server will I need to purchase licenses again for the new production server? I am presently testing on an older pIII 600 and will most likely be reinstalling on a more current server when I put this into production.