MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony
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.
Pau Espin 55faf38675 Bump version: → 1.1.1 4 years ago
contrib contrib: Disable doxygen in libosmocore build 5 years ago
debian Bump version: → 1.1.1 4 years ago
doc/examples vty: Work on configuration of the MNCC to SIP gateway 7 years ago
src use osmo_init_logging2() to avoid allocating from NULL context 5 years ago
tests distcheck/tests: Add the referenced for testing 7 years ago
.gitignore Use release helper from libosmocore 5 years ago
.gitreview Add git review config 5 years ago
COPYING Initial commit for a MNCC to SIP gateway (and maybe auth GW too) 7 years ago Use release helper from libosmocore 5 years ago
README.asciidoc Write down some of the limitations of the current setup 7 years ago Bump version: → 1.1.1 4 years ago
git-version-gen Fix git-version-gen 5 years ago osmoappdesc: Fix VTY prompt to use OsmoSIPcon, not old OsmoMNCC 5 years ago


Osmo SIP Connector

Simple utility to map MNCC to SIP and SIP to MNCC. The VTY interface
can be used to make configurations. The code doesn't have any RTP or
transcoding support.

Call identities can be either the MSISDN or the IMSI of the subscriber.

Requirements of Equipment

* DTMF need to be sent using SIP INFO messages. DTMF in RTP is not

* BTS+PBX and SIP connector+PBX must be in the same network (UDP must be
able to flow directly between these elements)

* No handover support.

* IP based BTS (e.g. Sysmocom sysmoBTS but no Siemens BS11)

* No emergency calls


* PT of RTP needs to match the one used by the BTS. E.g. AMR needs to use
the same PT as the BTS. This is because rtp_payload2 is not yet supported
by the osmo-bts software.

* AMR SDP file doesn't include the mode-set params and allowed codec modes.
This needs to be configured in some way.