MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony https://osmocom.org/projects/osmo-sip-conector
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Adds cause field to the call_leg and sip_call_leg structs. Translates the SIP status to MNCC cause and vice versa and uses this information in the SIP/MNCC messages at call leg release time. Change-Id: Ic1b80dff7e583cd6fff2b662bc6cc4bad3f81cd4
|5 years ago|
|contrib||5 years ago|
|debian||5 years ago|
|doc/examples||7 years ago|
|src||5 years ago|
|tests||7 years ago|
|.gitignore||6 years ago|
|.gitreview||6 years ago|
|COPYING||7 years ago|
|Makefile.am||6 years ago|
|README.asciidoc||7 years ago|
|configure.ac||5 years ago|
|git-version-gen||5 years ago|
|osmoappdesc.py||5 years ago|
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
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.