MNCC<->SIP bridge; attaches to OsmoMSC to interface with external SIP VoIP telephony
https://osmocom.org/projects/osmo-sip-conector
97c7916892
Copy the m_mode before freeing the parser. Address sanitizer aborted with: 20210601033017695 DSIP INFO re-INVITE for call 854A5CDA8037073 (sip.c:192) ================================================================= ==8583==ERROR: AddressSanitizer: heap-use-after-free on address 0x612000003250 at pc 0x55c3b4624dc5 bp 0x7ffe8a4464d0 sp 0x7ffe8a4464c8 READ of size 8 at 0x612000003250 thread T0 #0 0x55c3b4624dc4 in sdp_get_sdp_mode ../../../src/osmo-sip-connector/src/sdp.c:72 #1 0x55c3b462be9e in sip_handle_reinvite ../../../src/osmo-sip-connector/src/sip.c:202 #2 0x55c3b462d676 in nua_callback ../../../src/osmo-sip-connector/src/sip.c:397 [...] Change-Id: I4c48832f01e61e98536de8f164ab5a3caa64f34a |
||
---|---|---|
contrib | ||
debian | ||
doc | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
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.