You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Sipwise Jenkins Builder 944a0f8565
Release new version 1:1.6.0+0~mr13.3.2.0
1 month ago
apps MT#62181 remove event queue during shut down 2 months ago
cmake Imported Upstream version 1.6.0~20140516~eaa616 11 years ago
core MT#62181 transport: slight reformat 2 months ago
debian Release new version 1:1.6.0+0~mr13.3.2.0 1 month ago
doc MT#55831 db_reg_agent: add username_with_domain option to use auth user with domain part 2 years ago
docs MT#57728 docs: add preamble for the main page 3 months ago
pkg MT#57398 deprecate pkg/deb/{jessie,precise,trusty,wheezy} 2 years ago
tools MT#56184 build: Fix parallel building 2 years ago
.gitignore TT#22072 Update packaging 8 years ago
.gitreview MT#7505 Add .gitreview file for sems 11 years ago
.readthedocs.yaml MT#57728 Docs: add .readthedocs.yml file 4 months ago
CMakeLists.txt Imported Upstream version 1.6.0~20140516~eaa616 11 years ago
Makefile MT#56184 build: Fix parallel building 2 years ago
Makefile.defs MT#59962 Makefile.defs: add TEST_ENVIRONMENT variable 6 months ago
README.md MT#57728 Docs: add GPL notice and link to sems-server 4 months ago

README.md

What is SEMS?

Sipwise SEMS stands for SIP Express Media Server, but that's not all it is.

Sipwise SEMS is originally a fork of a well known SEMS open source project but over the course of time we went far away from it realizing our own ideas and making SEMS project alive and active. Our project is fully GPL license compatible implementation.

Sipwise SEMS primarily is a B2B service, which is mainly considered to be used in VoIP setups based on SIP protocol signaling. And still it is quite agnostic in terms of which other software is to be used in combination with it.

It is also capable of media processing, e.g.: RTP relay and media generation (based on SEMS provided applications).

It's mostly meant to be used with Kamailio- or OpenSIPS- SIP proxy servers, but also any other SIP Proxy services supporting RFC3261 and RFC8866 standards.

Sipwise SEMS is designed to work based on the event processing model, which makes it efficient in combination with threading. It is opposite in this regard to other open-source projects known to the SIP world, which are traditionally dependent on process fork based implementation (coming traditionally from the years past) and also are mostly process oriented.

Mailing List

For general questions, discussion, requests for support, and community chat, join our mailing list. Please do not use the Github issue tracker for this purpose.

Features

  • full-fledged B2B user agent (its main purpose)
  • media processing (RTP relay and media generation)
  • transcoding
  • custom PBX applications (DSM)
  • support of other languages (e.g. Python)
  • Redis and MySQL support
  • VSC codes handling
  • SIP Registration client (based on RPC or configuration file)
  • Conferences support (module)
  • And many other things! (see doc/ and apps/ for more information)

Documentation

Check our general documentation here:

Contribution

Every bit matters. Join us. Make Sipwise SEMS community stronger.