ivozprovider icon indicating copy to clipboard operation
ivozprovider copied to clipboard

Published 20 hours ago • verified publisher icon irontec

Evaluate removing Asterisk direct_media mechanism

Open cruzccl opened this issue 6 years ago • 1 comments

After RTPengine (#375) and SEMS (#391) are integrated into IvozProvider, Asterisk media liberation mechanism must be evaluated:

  • Currently, it is only enabled for internal calls, as some carriers have problems receiving a reINVITE as soon as the call establishment has been acknowledged.

  • RTPengine internals are quite different from RTPproxy ones, so somes tests are needed.

  • Media liberation delay mechanism is ugly and should be removed from KamTrunks.

  • SEMS and RTPengine transcoding (#387) may be enough for non-PBX calls (and Asterisk can manage media related to PBX calls).

This is an evaluation issue to think about this stuff.

cruzccl avatar Apr 05 '18 16:04 cruzccl

Asterisk media liberation mechanism causes trouble with some carriers. Besides, rtpengine changes ports in liberation reINVITE (that causes even more problems). That's why rtpproxy has not been removed yet (as mentioned in #375).

The idea for 2.X is to take Asterisk out of the way for all non-vPBX sessions (wholesale, retail...). But Asterisk will still be used for vPBX and some of them want to liberate media to handle more calls or to achieve geo-scalation.

This issue needs more evaluation, so no changes will be introduced in 2.2.

cruzccl avatar Apr 16 '18 17:04 cruzccl