A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Open-source telephony core / Four projects, four roles

Four projects, four roles

Read the role each project states. Do not treat them as four names for one PBX.

Learn in 5 minutes

  1. Place Asterisk, FreeSWITCH, Kamailio, and rtpengine
  2. Say which one is a media proxy meant to sit with Kamailio
  3. Refuse a single configuration that the pages do not share

Visual

SIP hits Kamailio. Media can be anchored in rtpengine. · study drawing · cyphermonkeylabs.com PhoneKamailioPBX INVITE INVITE 200 200

SVG HTML PNG

Kamailio can sit in front of a PBX. rtpengine proxies the RTP. This drawing is that relationship, not a production size.

Worked example

Place the box Four lines. Pick the one that proxies RTP.

  1. Read each name.
  2. Match it to the page you would open.
  3. Pick the media proxy.

Fault

Calls reach Kamailio. Someone pastes an Asterisk dialplan into rtpengine and expects extensions to run.

The README defines rtpengine as a media proxy. Asterisk and FreeSWITCH document the dialplan.

Quiz

Kamailio's home page describes it as


rtpengine is meant to be used with


The Asterisk history page calls the project an


FreeSWITCH's manual, as opened here, teaches


Kamailio says it can scale in front of


rtpengine's supported platform, per the README, is


Ecosystem

Glossary, sister systems, and the integration seam for this room.

Workforce management WFM forecasts volume and builds schedules. It consumes contact-center events. It does not parse Via headers. When a forecast is wrong, the SIP symptom is usually queue delay and 480 or carrier congestion, not a broken dialog ID.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper