cellular-infrastructure
/
osmo-sip-connector
mirror of https://gerrit.osmocom.org/osmo-sip-connector
9
0
Fork 0
Code Issues Releases Wiki Activity
MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony https://osmocom.org/projects/osmo-sip-conector
109 Commits 27 Branches 14 Tags 1.7 MiB
C 86.7%
Shell 5.7%
M4 4.5%
Makefile 1.4%
Dockerfile 0.9%
Other 0.8%
Go to file
Harald Welte fd203f6a97 mncc: use 'const' to denote read-only input buffer/message 
We normally use the 'const' modifier whenever using read-only input
data, let's do so in the mncc parser/handler, too.

Change-Id: Ide24feb536c04fe7ef08c62b4498fdd95605b58c
 		2018-03-19 10:03:26 +01:00
contrib contrib: jenkins.sh: Disable doxygen in libosmocore build 2018-02-20 20:23:10 +01:00
debian debian/control: Fix URLs for homepage / git 2018-02-09 11:17:29 +01:00
doc/examples vty: Work on configuration of the MNCC to SIP gateway 2016-03-21 15:39:41 +01:00
src mncc: use 'const' to denote read-only input buffer/message 2018-03-19 10:03:26 +01:00
tests distcheck/tests: Add the referenced osmoappdesc.py for testing 2016-04-24 22:28:35 +02:00
.gitignore Use release helper from libosmocore 2017-08-26 05:56:55 +00: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
Makefile.am Use release helper from libosmocore 2017-08-26 05:56:55 +00:00
README.asciidoc Write down some of the limitations of the current setup 2016-03-26 16:31:00 +01:00
configure.ac configure.ac: Depend on latest upstream libosmo-* 2017-10-28 18:20:01 +02:00
git-version-gen Fix git-version-gen 2017-10-28 18:20:00 +02:00
osmoappdesc.py distcheck/tests: Add the referenced osmoappdesc.py for testing 2016-04-24 22:28:35 +02:00

README.asciidoc 

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
supported.

* 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

Limitations
^^^^^^^^^^^

* 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.