MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony
https://osmocom.org/projects/osmo-sip-conector
550264987f
In case of solely managing the application through the VTY we want/need to have the application running besides a wrong config has been entered. SIP will be broken but a user will be able to see the log message and can fix it. |
||
|---|---|---|
| contrib | ||
| debian | ||
| doc/examples | ||
| src | ||
| tests | ||
| .gitignore | ||
| COPYING | ||
| Makefile.am | ||
| README.asciidoc | ||
| configure.ac | ||
| git-version-gen | ||
| osmoappdesc.py | ||
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.