Transcoding - Revision history

Dana: /* How to do transcoding in Yate */

2013-04-03T11:06:37Z

‎How to do transcoding in Yate

2013-03-20T12:56:09Z

‎Where to change the codecs

2013-02-13T08:27:02Z

2013-02-13T08:26:36Z

Added formats flow diagram

2012-11-19T10:43:51Z

‎= How to do transcoding in Yate

2012-11-19T10:43:34Z

2012-11-19T10:10:48Z

2012-11-19T10:09:49Z

‎Transcoding

2012-10-03T12:01:51Z

‎Transcoding

2012-10-03T11:57:50Z

@@ Line 5: / Line 5: @@
 === How to do transcoding in Yate ===
-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.
+Currently there is one easy way to compute the list of possible transcoded formats.
 You can put this line in regexroute.conf section [contexts] that handles call.preroute:
@@ Line 13: / Line 15: @@
   .*=;oformats=$(transcode,,${formats})
-The empty parameter above (between the two commas) controls which formats are  returned. Please see the comments in [[Regular_expressions#The regexroute configuration file|regexroute.conf]] for more info.
+The empty parameter above (between the two commas) controls which formats are  returned.
-If inbound 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|register]] (database routing) to set the formats parameter:
+You can then use '''${oformats}''' in routing either in regexroute or in [[Register|register]] (database routing) to set the formats parameter:
   [default]

@@ Line 28: / Line 28: @@
 [[File:Format flow.png]]
-The red numbers indicate the places where the list can be altered:
+The numbers indicate the places where the list can be altered:
 # Inbound channel supported codecs (automatically filters inbound offer)
@@ Line 36: / Line 36: @@
 # Outbound channel supported codecs (automatically filters response)
 # Inbound channel supported codecs (automatically filters response)
 '''See also'''
 * [[Register]]
 * [[Regular expressions]]

@@ Line 33: / Line 33: @@
 # Routing (alters inbound and outbound codecs)
 # Executing outbound call (alters outbound codecs)
-#. Outbound channel supported codecs (automatically filters outbound offer)
+# Outbound channel supported codecs (automatically filters outbound offer)
 # Outbound channel supported codecs (automatically filters response)
 # Inbound channel supported codecs (automatically filters response)

@@ Line 21: / Line 21: @@
   ; Offer transcoded formats on outbound unless rtp_forward is in use
   ${rtp_forward}^yes$^=;formats=${oformats}
 '''See also'''
 * [[Register]]
 * [[Regular expressions]]

@@ Line 3: / Line 3: @@
 Transcoding can work only if RTP passes through Yate. When ''rtp_forward'' is enabled transcoding won't work and you must '''not''' add formats to the list - at most you can remove.
-=== How to do transcoding in Yate ==
+=== How to do transcoding in Yate ===
 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.

@@ Line 16: / Line 16: @@
 |}
-The empty parameter above (between the two commas) controls which formats are  returned. Please see the comments in [[Regular_expressions#The_regexroute_configuration_file|regexroute.conf.sample]] for more info.
+The empty parameter above (between the two commas) controls which formats are  returned. Please see the comments in [[Regular_expressions#TConfiguration|regexroute.conf]] for more info.
 If inbound 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|register]] (database routing) to set the formats parameter: