This documents describes reimplementation and migration of Conference IVR application on PortaSIP Media Server Cluster.
Additional info
Current implementation of call conferencing functionality uses Asterisk as main essential part for call and media streams handling. It leads to several important limitations and drawbacks such as:
Presence of Asterisk as essential processing part makes customers to think that they are forced to pay for freely available Asterisk which causing complaints.
We are tightly linked to functionality provided by Asterisk and its code-base. As result we have to maintain own set of patches in case we want to changes something in processing engine.
Asterisk SIP stack has design limitations and issues which sometimes are not really easy to solve and deal with.
Presence of one additional SIP and media stacks for particular IVR may cause an unexpected behaviour inconsistency which is hard to diagnose and troubleshot.
So it was made a decision to re-implement Conference IVR on top of PortaSIP Media Server Cluster using its SIP (B2BUA) and media (RTPProxy) stacks as main processing engines.