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(a)freyther.de> wrote:
On 23 Sep 2016, at 11:22, Anonim Stefan
<fanx07(a)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).