The problem: you are missing a module Let's say you add the db_mysql module to your opensips.cfg file: loadmodule "db_mysql.so" And you go to run check your opensips config via docker (like you learned here): docker run -v ${PWD}/:/etc/opensips --en...
The docker compose file below will let you have a running opensips, rtpengine and mysql server. Take note of the OPENSIPS_EXTRA_MODULES variable. Change that to include any extra modules you need in your opensips. Check out below the file for the oth...
Here is a small snippet, showing how to answer a call and play audio from your opensips config using the opensips b2b_entities module. if (is_method("INVITE") && !has_totag()) { xlog("[$fU $tU $ci $rm] initiating ua_session_server_init\n"); ...
If you develop with opensips on Mac or Windows, frustration will quickly set in when you think you have your opensips.cfg file ready for testing calls, so you push to your remote server or VM, try to start opensips, and get an error like this: Jun 7...