|
Home Resources Products
Developers |
Main • Transcoding
TranscodingAutomatic transcoding is performed (if possible) when call legs are connected together. By default negotiation does not take into account possible transcodings since this is route dependent. Currently there is one easy way to compute the list of possible transcoded formats. The regexroute module offers a transcode function to build an extended list. You should not use this list always, only when you are sure RTP is proxied through Yate. You can put this line in regexroute.conf section [contexts] that handles call.preroute:
.*=;oformats=$(transcode,,${formats})
The empty parameter above (between the two commas) controls which formats are returned. Please see the comments in regexroute.conf.sample for more info. If formats=alaw,mulaw you will get something like oformats=alaw,mulaw,slin,gsm,ilbc,speex (assuming the modules are compiled and loaded). You can then use ${oformats} in routing either in regexroute or in register (database routing) to set the formats parameter:
${rtp_forward}possible=;rtp_forward=yes
${rtp_forward}^yes$^=;formats=${oformats}
|
3 May 2010: 8 March 2010: 6-7 February 2010: 2 Nov 2009: 6 Aug 2008: 4 Aug 2008: 10 Jul 2008: Feb 2008: 21 Jan 2008: 3 September: 14 August: 16 April: 25 September: 25 September: 11 July 2006: 10 July 2006: June 1st 2006: |