MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony
Go to file
Oliver Smith b544ea396a mncc.c: fix gsm_mncc_rtp size checks
Verify is the parsed data is at least the size of the struct, not
exactly the size. Make it accept messages with additional data, like
the SDP information the TTCN-3 testsuite is sending since

This change makes the size checks consistent with the two other size
checks in the file:
	if (rc < sizeof(*rtp)) {
	if (rc < sizeof(**mncc)) {

Related: OS#4282
Change-Id: I522ce7f206932a816a64f03d916799c3215bb8c7
2019-11-28 15:11:33 +01:00
contrib .service: require to ran after 2019-09-16 19:51:07 +02:00
debian Bump version: → 1.3.0 2019-08-08 17:54:49 +02:00
doc debian: create -doc subpackage with pdf manuals 2019-05-29 12:14:22 +02:00
src mncc.c: fix gsm_mncc_rtp size checks 2019-11-28 15:11:33 +01:00
tests distcheck/tests: Add the referenced for testing 2016-04-24 22:28:35 +02:00
.gitignore build manuals moved here from osmo-gsm-manuals.git 2018-11-27 18:34:56 +01:00
.gitreview Add git review config 2017-08-25 18:38:05 +02:00
COPYING Initial commit for a MNCC to SIP gateway (and maybe auth GW too) 2016-03-21 09:54:37 +01:00 Fix DISTCHECK_CONFIGURE_FLAGS override 2018-12-04 15:32:11 +01:00
README.asciidoc Write down some of the limitations of the current setup 2016-03-26 16:31:00 +01:00 Require newer libosmocore 1.0.0 2019-08-08 17:54:11 +02:00
git-version-gen Fix git-version-gen 2017-10-28 18:20:00 +02:00 osmoappdesc: Fix VTY prompt to use OsmoSIPcon, not old OsmoMNCC 2018-03-27 15:51:02 +02:00


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.