MOH Translator

Unanswered Question
Jul 3rd, 2003
User Badges:

I have CCM 3.3(2) for whatever reason the MOH translator is not converting the files into G.711. Its always converting it into G.729. So I am getting very poor quality for MOH.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
scottiptel Sun, 07/13/2003 - 09:02
User Badges:

I have not configured any location. Device pool is same for both of them. Even sample audio source file has g.729 codec it doesnt have g.711.

dugrant Sun, 07/13/2003 - 09:39
User Badges:
  • Bronze, 100 points or more

Goto the Service Paramaters for the IP Voice Media Streaming App. At the bottom of the page, there is a paramater "supported MoH codecs" with a list of codecs. I suspect that you only have g.729 highlighted, highlight only the codecs that you are actually going to use.

If you highlight all the codecs, then a file will be created for every codec. Add several MoH sources and the space used adds up pretty quickly, and makes your backups huge.

scottiptel Mon, 07/14/2003 - 13:57
User Badges:

I have highlighted g.729 and g.711. But still itc converting into g.729 only.

dgoodwin Mon, 07/14/2003 - 18:45
User Badges:
  • Cisco Employee,

There should be 4 output files: g729, wb (wideband), ulaw (G.711 ulaw), and alaw (G.711 alaw).

Double-tap the "i" button or "?" button on the held IP phone while it's been put on hold, and you'll see what codec is being used. The codec to use for the held call is determined by the region setting between the MOH server device and the held device.

scottiptel Thu, 07/17/2003 - 14:20
User Badges:

When I will put a caller on hold the codec in the info is g.729 and I have only one region which is default. The codec within this region is g.711. The important thing is that I cant see g.711 fine in audio source properties.


This Discussion