12 Apr
2022
12 Apr
'22
12:24 p.m.
Hi,
I'm using OsmoMGW version 1.9.0.20.069dd.202204110026 and OsmoHNBGW version
1.2.1.13.be9e.202204110026.
Call is established, but is silent.
The connection is up,but only data flowing one way:
OsmoMGW# show mgcp endpoint rtpbridge/1@mgw
Virtual trunk 0 endpoint rtpbridge/1@mgw:
Availability: available
CONN: (1701/rtp, id:0x49AD9023, ip:10.40.16.36, rtp:19856 rtcp:19857)
Packets Sent: 0 (0 bytes total)
Packets Received: 0 (0 bytes total)
Timestamp Errs: 0->0
Dropped Packets: 0
Payload Type: 96 Rate: 16000 Channels: 1
Frame Duration: 20 Frame Denominator: 1000
FPP: 0 Packet Duration: 20
FMTP-Extra: (null) Audio-Name: VND.3GPP.IUFP/16000 Sub-Type: VND.3GPP.IUFP
Output-Enabled: 1 Force-PTIME: 0
CONN: (1701/rtp, id:0x5AFEDEF8, ip:10.103.36.93, rtp:55078 rtcp:55079)
Packets Sent: 918 (15606 bytes total)
Packets Received: 1118 (34350 bytes total)
Timestamp Errs: 0->0
Dropped Packets: 0
Payload Type: 96 Rate: 16000 Channels: 1
Frame Duration: 20 Frame Denominator: 1000
FPP: 0 Packet Duration: 20
FMTP-Extra: (null) Audio-Name: VND.3GPP.IUFP/16000 Sub-Type: VND.3GPP.IUFP
Output-Enabled: 1 Force-PTIME: 0
OsmoMGW#
And I can ping 10.40.16.36 with source 10.40.50.67.
But there seems to be aproblem with RTP initialization on link towards core ( Ericsson MGW
)
<0012> mgcp_protocol.c:855 endpoint:rtpbridge/1@mgw CRCX: creating new connection
...
<0012> mgcp_protocol.c:165 endpoint:rtpbridge/1@mgw RTP-setup: Endpoint is in
loopback mode, stopping here!
<0012> mgcp_protocol.c:1091 endpoint:rtpbridge/1@mgw CI:C6A09234 CRCX: connection
successfully created
<0012> mgcp_protocol.c:1124 endpoint:rtpbridge/1@mgw MDCX: modifying existing
connection ...
<0012> mgcp_sdp.c:436 endpoint:rtpbridge/1@mgw CI:C6A09234 Got media info via SDP:
port:55076, addr:10.103.36.93, duration:20, payload-types:96=VND.3GPP.IUFP
<0000> mgcp_iuup.c:705 (rtpbridge/1@mgw I:C6A09234) No RFCI NO_DATA found, unable to
send dummy packet
<0012> mgcp_protocol.c:1312 endpoint:rtpbridge/1@mgw CI:C6A09234 MDCX: connection
successfully modified
<0012> mgcp_protocol.c:855 endpoint:rtpbridge/1@mgw CRCX: creating new connection
...
<0012> mgcp_sdp.c:436 endpoint:rtpbridge/1@mgw CI:E7B356C6 Got media info via SDP:
port:19008, addr:10.40.16.36, duration:20, payload-types:96=VND.3GPP.IUFP
<0000> mgcp_iuup.c:705 (rtpbridge/1@mgw I:E7B356C6) No RFCI NO_DATA found, unable to
send dummy packet
<0012> mgcp_protocol.c:1091 endpoint:rtpbridge/1@mgw CI:E7B356C6 CRCX: connection
successfully created
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<
.
.
.
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<0019> iuup.c:895 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Event
IuUP-DATA-ind not permitted
<0000> mgcp_iuup.c:189 (rtpbridge/1@mgw I:C6A09234) Failed passing IuUP-Init to IuUP
layer
<0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization:
Unexpected RFCI 1 at position 0 received
<0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization
NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00
<00
Configs:
! MGW
mgcp
domain mgw
local ip 10.40.50.67
bind ip 10.40.50.67
bind port 2427
rtp port-range 4002 16001
no rtp ip-probing
rtp ip-dscp 0
rtp keep-alive once
no rtcp-omit
no rtp-patch
sdp audio-payload send-ptime
sdp audio-payload send-name
number endpoints 15
allow-transcoding
osmux off
end
!HnbGW
cs7 instance 0
network-indicator national
point-code 0.69.4
sccp-address msc
routing-indicator PC
point-code 0.27.4
sccp-address sgsn
routing-indicator PC
point-code 0.113.6
hnbgw
log-prefix hnb-id
iuh
local-ip 10.40.50.69
iucs
remote-addr msc
iups
remote-addr sgsn
mgcp
mgw remote-ip 10.40.50.67
mgw remote-port 2427
mgw reset-endpoint rtpbridge/*
end
Best Regards
Sjur Thomas Lien
Systems engineer Roaming & Network access
Telenor Maritime
+47 91602376
Kystveien 2D
N-4841 Arendal, Norway
www.telenormaritime.com<http://www.telenormaritime.com/>
LinkedIn<https://www.linkedin.com/company/telenor-maritime/>
[/Users/rinomartinsen/Dropbox (ANTI)/Telenor/2_Projects/TNO036_digitizing and renewal of
the telenor identity/FINAL/Toolkit/Logo/Symbol/RGB/pdf/telenor_symbol_blue.pdf]
Internal
12 Apr
12 Apr
12:45 p.m.
Hi,
I guess you mean Ericsson HNB, not Ericcson MGW as you wrote in the
email topic.
this is the problem:
On 4/12/22 12:24, Sjur Thomas Lien wrote:
<0019> iuup.c:537
IuUP(C6A09234)[0x562a59d9c600]{Initialisation}:
Initialization: Unexpected RFCI 1 at position 0 received
Our IuUP implementation expects RFCI num X to be at position X of the
array (starting from 0). This is a limitation of the current
implementation, which worked well with nano3g HNB so far.
see libosmocore/src/gsm/iuup.c
Patches to improve IuUP support are welcome. Otherwise, if you need
someone to invest some hours into improving this part of the code or any
integration work in general, I kindly remind you that you can contact
sysmocom for commercial support on this kind of topics.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
2:32 p.m.
Hi,
Thanks for feedback.
No, I mean Ericsson MGW.
On the Iuh side we have Spidercloud wires Services Node.
The RTP link to Iuh is OK, problem is Osmo MGW - Ericsson Mgw.
But Ok, I'll get in contact with Sysmocom.
Regards,
/Sjur
-----Original Message-----
From: Pau Espin Pedrol <pespin(a)sysmocom.de>
Sent: Tuesday, April 12, 2022 12:45 PM
To: Sjur Thomas Lien <sjur.lien(a)telenormaritime.com>om>; openbsc(a)lists.osmocom.org
Subject: Re: Osmo MGW problem with real Ericsson MGW
Hi,
I guess you mean Ericsson HNB, not Ericcson MGW as you wrote in the email topic.
this is the problem:
On 4/12/22 12:24, Sjur Thomas Lien wrote:
<0019> iuup.c:537
IuUP(C6A09234)[0x562a59d9c600]{Initialisation}:
Initialization: Unexpected RFCI 1 at position 0 received
Our IuUP implementation expects RFCI num X to be at position X of the array (starting from
0). This is a limitation of the current implementation, which worked well with nano3g HNB
so far.
see libosmocore/src/gsm/iuup.c
Patches to improve IuUP support are welcome. Otherwise, if you need someone to invest some
hours into improving this part of the code or any integration work in general, I kindly
remind you that you can contact sysmocom for commercial support on this kind of topics.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de>
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sysmoc…
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Internal
5:59 p.m.
A small typo there..
" On the Iuh side we have Spidercloud wireless Services Node"
Right should be right😊
/Sjur
-----Original Message-----
From: Sjur Thomas Lien <sjur.lien(a)telenormaritime.com>
Sent: Tuesday, April 12, 2022 2:32 PM
To: Pau Espin Pedrol <pespin(a)sysmocom.de>de>; openbsc(a)lists.osmocom.org
Subject: RE: Osmo MGW problem with real Ericsson MGW
Hi,
Thanks for feedback.
No, I mean Ericsson MGW.
On the Iuh side we have Spidercloud wires Services Node.
The RTP link to Iuh is OK, problem is Osmo MGW - Ericsson Mgw.
But Ok, I'll get in contact with Sysmocom.
Regards,
/Sjur
-----Original Message-----
From: Pau Espin Pedrol <pespin(a)sysmocom.de>
Sent: Tuesday, April 12, 2022 12:45 PM
To: Sjur Thomas Lien <sjur.lien(a)telenormaritime.com>om>; openbsc(a)lists.osmocom.org
Subject: Re: Osmo MGW problem with real Ericsson MGW
Hi,
I guess you mean Ericsson HNB, not Ericcson MGW as you wrote in the email topic.
this is the problem:
On 4/12/22 12:24, Sjur Thomas Lien wrote:
<0019> iuup.c:537
IuUP(C6A09234)[0x562a59d9c600]{Initialisation}:
Initialization: Unexpected RFCI 1 at position 0 received
Our IuUP implementation expects RFCI num X to be at position X of the array (starting from
0). This is a limitation of the current implementation, which worked well with nano3g HNB
so far.
see libosmocore/src/gsm/iuup.c
Patches to improve IuUP support are welcome. Otherwise, if you need someone to invest some
hours into improving this part of the code or any integration work in general, I kindly
remind you that you can contact sysmocom for commercial support on this kind of topics.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de>
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sysmoc…
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Internal
Internal
Internal
769
days inactive
769
days old
3 comments
2 participants
participants (2)
-
Pau Espin Pedrol -
Sjur Thomas Lien