Difference between revisions of "Many calls are transcoded"
(9 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Codec transcoding takes a lot of CPU cycles. | Codec transcoding takes a lot of CPU cycles. | ||
= Solution = | = Quick Solution = | ||
Make sure ALL devices (OP and TP) have these settings set to Yes: | Make sure ALL devices (OP and TP) have these settings set to Yes: | ||
Line 7: | Line 7: | ||
[[File:fs_transcoded_settings.jpg]] | [[File:fs_transcoded_settings.jpg]] | ||
Note that | Note that OP devices will have only first option available and TP devices only second option available. Mark them YES anyway. | ||
<br><br> | <br><br> | ||
= Detailed problem description = | = Detailed problem description = | ||
== We have a problem == | |||
Example in which you can see that 284 calls takes 287.9% of CPU for Freeswitch: | Example in which you can see that 284 calls takes 287.9% of CPU for Freeswitch: | ||
Line 19: | Line 22: | ||
[[File:freeswitch_transcoded_calls_bad2.jpg]] | [[File:freeswitch_transcoded_calls_bad2.jpg]] | ||
== Solution == | |||
Go through all your devices (OP and TP) and set these options: | |||
[[File:fs_transcoded_settings.jpg]] | |||
These options will force Freeswitch to use same codecs for both legs 99% of the time. Detailed description here: [[M2 Codec Negotiation]] | |||
Note that only OP devices will have only first option available and only TP devices only second option available. Mark them YES anyway. | |||
Also make sure your devices have same codecs available. | |||
This is just an example how it could look like. On your system you can have different codecs enabled: | |||
[[File:fs_transcoded_codecs.jpg]] | |||
== Problem gone == | |||
As you can see after codecs are negotiated properly and call is not transcoded anymore, we have big imrpovement on the Freeswitch CPU usage. In this example CPU load decreased 3 times! | |||
[[File:fs_transcoded_calls_good.jpg]] | |||
And in the Call List we see many green icons, which means that calls are not transcoded: | |||
[[File:freeswitch_transcoded_calls_good2.jpg]] | |||
Note that sometimes some calls will be transcoded, because Freeswitch sometimes is unable to negotiate same codec between Originator and Terminator. This is ok, because it will be a very low number of not transcoded calls. |
Latest revision as of 13:08, 7 October 2018
Codec transcoding takes a lot of CPU cycles.
Quick Solution
Make sure ALL devices (OP and TP) have these settings set to Yes:
Note that OP devices will have only first option available and TP devices only second option available. Mark them YES anyway.
Detailed problem description
We have a problem
Example in which you can see that 284 calls takes 287.9% of CPU for Freeswitch:
In the Call List page you can observe which calls are transcoded. They are marked by RED icon:
Solution
Go through all your devices (OP and TP) and set these options:
These options will force Freeswitch to use same codecs for both legs 99% of the time. Detailed description here: M2 Codec Negotiation
Note that only OP devices will have only first option available and only TP devices only second option available. Mark them YES anyway.
Also make sure your devices have same codecs available.
This is just an example how it could look like. On your system you can have different codecs enabled:
Problem gone
As you can see after codecs are negotiated properly and call is not transcoded anymore, we have big imrpovement on the Freeswitch CPU usage. In this example CPU load decreased 3 times!
And in the Call List we see many green icons, which means that calls are not transcoded:
Note that sometimes some calls will be transcoded, because Freeswitch sometimes is unable to negotiate same codec between Originator and Terminator. This is ok, because it will be a very low number of not transcoded calls.