Keith 5f79d5a319 Fix bug with MO calls not connecting.
Fixes a bug I introduced in 5f73c2033b
where we would not call mncc_call_leg_connect() on receiving 200 from
SIP side, and therefore never send MNCC_SETUP_RSP to the MS

Fixes: 5f73c2033b

Change-Id: Ic7cc56c0d68a27eb1229c0c4aa1fa54d00b660b6
2019-08-06 17:40:17 +00:00
2019-08-06 17:40:17 +00:00
2017-08-25 18:38:05 +02:00
2017-10-28 18:20:00 +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
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.
Description
MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony
Readme 1.7 MiB
Languages
C 86.7%
Shell 5.7%
M4 4.5%
Makefile 1.4%
Dockerfile 0.9%
Other 0.8%