Hi,
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?
On 23 Sep 2016, at 11:22, Anonim Stefan fanx07@gmail.com wrote:
Hi,
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:
did it work before? It seems the phone is paged, a channel is opened, the RTP socket is opened but then the call 1073741832 is unknown. Could you check the dpkg.log to see from when to when you upgraded?
So one call is not known and the other ends with an unknown codec type (where the call is accepted and then terminated as a result).
Hi,
Yes, the same scenario worked before.
Previous version I had was a pretty old one: osmocom-nitb:amd64 0.15.1.20160622
Thanks, Stefan
On Fri, Sep 23, 2016 at 5:36 PM, Holger Freyther holger@freyther.de wrote:
On 23 Sep 2016, at 11:22, Anonim Stefan fanx07@gmail.com wrote:
Hi,
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:
did it work before? It seems the phone is paged, a channel is opened, the RTP socket is opened but then the call 1073741832 is unknown. Could you check the dpkg.log to see from when to when you upgraded?
So one call is not known and the other ends with an unknown codec type (where the call is accepted and then terminated as a result).
On 23 Sep 2016, at 17:03, Anonim Stefan fanx07@gmail.com wrote:
Hi,
Hi!
Yes, the same scenario worked before.
Previous version I had was a pretty old one: osmocom-nitb:amd64 0.15.1.20160622
I tried to reproduce (with a manual built) and couldn't. Could you send us your openbsc-nitb and osmo-sip-connector configuration file?
thank you!
holger
I'm attaching the config for both.
Thanks, Stefan
On Tue, Sep 27, 2016 at 8:42 PM, Holger Freyther holger@freyther.de wrote:
On 23 Sep 2016, at 17:03, Anonim Stefan fanx07@gmail.com wrote:
Hi,
Hi!
Yes, the same scenario worked before.
Previous version I had was a pretty old one: osmocom-nitb:amd64
0.15.1.20160622
I tried to reproduce (with a manual built) and couldn't. Could you send us your openbsc-nitb and osmo-sip-connector configuration file?
thank you!
holger
On 28 Sep 2016, at 11:47, Anonim Stefan fanx07@gmail.com wrote:
I'm attaching the config for both.
config looks fine and besides the band (changed to 1800) I have used your config on:
ii libosmoabis5:amd64 0.3.3.20160929 amd64 GSM A-bis handling ii libosmocore7:amd64 0.9.3.20160929 amd64 Osmo Core library ii libosmoctrl0:amd64 0.9.3.20160929 amd64 Osmo control library ii libosmogsm5:amd64 0.9.3.20160929 amd64 Osmo GSM utility library ii libosmovty3:amd64 0.9.3.20160929 amd64 Osmo VTY library ii osmo-sip-connector 1.20160929 amd64 MNCC to SIP bridge for osmo-nitb ii osmocom-nitb 0.15.1.20160929 amd64 GSM Network-in-a-Box, implements BSC, MSC, SMSC, HLR, VLR
it works here(tm). Can you retry and if it fails keep the first error and include RSL+SIP in the same trace and include osmo-nitb log output (-e 1) and enable timestamps.
thank you
holger
-
Anonim Stefan -
Holger Freyther