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
167 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
Keith Whyte 1f1f3f6fb9 IPs stored in the call struct are NETWORK byte order 
As far as I can make out, the intention is to always store ip address in the call struct
in network byte order, whereas the ip address sent on MNCC are in host byte order.

Change-Id: I89ef26aa32a672f394699251cf560b53ae01a814
 		2019-08-06 14:38:32 +02:00
contrib contrib/jenkins.sh: run "make maintainer-clean" 2019-07-10 13:25:00 +02:00
debian debian: create -doc subpackage with pdf manuals 2019-05-29 12:14:22 +02:00
doc debian: create -doc subpackage with pdf manuals 2019-05-29 12:14:22 +02:00
src IPs stored in the call struct are NETWORK byte order 2019-08-06 14:38:32 +02:00
tests distcheck/tests: Add the referenced osmoappdesc.py 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
Makefile.am 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
configure.ac build manuals moved here from osmo-gsm-manuals.git 2018-11-27 18:34:56 +01:00
git-version-gen Fix git-version-gen 2017-10-28 18:20:00 +02:00
osmoappdesc.py osmoappdesc: Fix VTY prompt to use OsmoSIPcon, not old OsmoMNCC 2018-03-27 15:51:02 +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.