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.
Make build and external tests work with python3, so we can drop the python2 dependency. This should be merged shortly after osmo-python-tests was migrated to python3, and the jenkins build slaves were (automatically) updated to have the new osmo-python-tests installed. Related: OS#2819 Depends: osmo-python-tests I3ffc3519bf6c22536a49dad7a966188ddad351a7 Change-Id: Ic913e336a5a962fe9515479b03eecdbef0917721
|3 years ago|
|contrib||3 years ago|
|debian||3 years ago|
|doc||3 years ago|
|src||3 years ago|
|tests||7 years ago|
|.gitignore||4 years ago|
|.gitreview||5 years ago|
|COPYING||7 years ago|
|Makefile.am||4 years ago|
|README.asciidoc||7 years ago|
|configure.ac||3 years ago|
|git-version-gen||5 years ago|
|osmoappdesc.py||3 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.