Many calls are transcoded

From Kolmisoft Wiki
Revision as of 13:08, 7 October 2018 by Admin (talk | contribs) (→‎Problem gone)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Codec transcoding takes a lot of CPU cycles.

Quick Solution

Make sure ALL devices (OP and TP) have these settings set to Yes:

Fs transcoded settings.jpg

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:

Freeswitch transcoded calls bad.jpg

In the Call List page you can observe which calls are transcoded. They are marked by RED icon:

Freeswitch transcoded calls bad2.jpg

Solution

Go through all your devices (OP and TP) and set these options:

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:

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!

Fs transcoded calls good.jpg

And in the Call List we see many green icons, which means that calls are not transcoded:

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.