osmo-sip-connector

MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony https://osmocom.org/projects/osmo-sip-conector

Go to file

Holger Hans Peter Freyther 4f8cafa5b0 call: Continue up to the point of call routing We accept the call on MNCC and ask the core to select/create the second leg of the call.		2016-03-23 17:41:23 +01:00
doc/examples	vty: Work on configuration of the MNCC to SIP gateway	2016-03-21 15:39:41 +01:00
src	call: Continue up to the point of call routing	2016-03-23 17:41:23 +01:00
.gitignore	Initial commit for a MNCC to SIP gateway (and maybe auth GW too)	2016-03-21 09:54:37 +01: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	Initial commit for a MNCC to SIP gateway (and maybe auth GW too)	2016-03-21 09:54:37 +01:00
README.asciidoc	doc: Update with some requirements and limitations	2016-03-23 17:02:32 +01:00
configure.ac	Initial commit for a MNCC to SIP gateway (and maybe auth GW too)	2016-03-21 09:54:37 +01:00
git-version-gen	Initial commit for a MNCC to SIP gateway (and maybe auth GW too)	2016-03-21 09:54:37 +01: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