This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Anonim Stefan fanx07 at gmail.comHi,
I am using osmo-nitb + osmo-sip-connector and I am sending INVITE to it, as
in the attached trace. The connector replies with 0.0.0.0 RTP IP and
0/unknown codec and then ends the call. I am seeing the following log:
"
Sep 23 09:08:00 openbsc1 osmo-sip-connector[1723]: #033[0;m<0001>
mncc.c:334 call(1073741832) can not be found
Sep 23 09:08:02 openbsc1 osmo-sip-connector[1723]: #033[0;m<0002> app.c:104
Unknown ptmsg(0). call broken
Sep 23 09:08:02 openbsc1 osmo-sip-connector[1723]: #033[0;m<0001>
mncc.c:312 leg(5001) rtp connect failed
Sep 23 09:08:02 openbsc1 osmo-sip-connector[1723]: #033[0;m<0000> sip.c:245
Ending leg(0x91ec30) in con
Sep 23 09:08:02 openbsc1 osmo-sip-connector[1723]: #033[0;m<0001>
mncc.c:304 leg(1073741832) can not be found
Sep 23 09:08:02 openbsc1 osmo-sip-connector[1723]: #033[0;m<0000> sip.c:186
leg(0x91ec30) got bye, releasing.
"
This issue happens *after* *recently* *updated* *packages* to:
"
ii osmocom-nitb 0.15.1.20160922 amd64
GSM Network-in-a-Box, implements BSC, MSC, SMSC, HLR, VLR
ii osmo-sip-connector 1.20160922 amd64
MNCC to SIP bridge for osmo-nitb
"
On the osmo-nitb side I am seeing logs [1].
I suspect a bug in the osmo-sip-connector code. Can someone confirm this?
[1] http://pastebin.com/giG0HHha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160923/0eb222fa/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-sip-connector.pcap
Type: application/vnd.tcpdump.pcap
Size: 6880 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160923/0eb222fa/attachment.bin>