Actions
Bug #2825
closedosmo-mgw for osmo-bsc receives RTCP from wrong port and tosses all of them (from sysmoBTS)
Start date:
01/10/2018
Due date:
% Done:
100%
Spec Reference:
Description
My sysmoBTS is sending RTP from port 44286, which go through. However, it appears to send RTCP from port 39839, where the osmo-mgw wants to enforce it to come from port 44287. As a result, it tosses all RTCP packets.
20180110192222187 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:900 endpoint:0x21 receiving RTP/RTCP packet... 20180110192222187 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:802 receiving 140 bytes length packet from 192.168.0.9:39839 ... 20180110192222187 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:907 endpoint:0x21 receiveing from 3 192.168.0.9 39839 20180110192222187 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:912 endpoint:0x21 conn:(3/rtp, id:0x056EDA798F9250F3ECAFDCAE998FB14E, ip:192.168.0.9, rtp:44286 rtcp:44287) 20180110192222187 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:849 endpoint:0x21 data from wrong source port: 39839, expected: 44286 for RTP or 44287 for RTCP 20180110192222188 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:854 endpoint:0x21 packet tossed 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:1070 endpoint:0x21 source conn:(3/rtp, id:0x056EDA798F9250F3ECAFDCAE998FB14E, ip:192.168.0.9, rtp:44286 rtcp:44287) 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:900 endpoint:0x21 receiving RTP/RTCP packet... 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:802 receiving 29 bytes length packet from 192.168.0.9:44286 ... 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:907 endpoint:0x21 receiveing from 3 192.168.0.9 44286 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:912 endpoint:0x21 conn:(3/rtp, id:0x056EDA798F9250F3ECAFDCAE998FB14E, ip:192.168.0.9, rtp:44286 rtcp:44287) 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:951 endpoint:0x21 destin conn:(3/rtp, id:0xD7655E43E6894076C8AAF7A33263BABE, ip:192.168.0.10, rtp:4002 rtcp:4003) 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:966 endpoint:0x21 endpoint type is MGCP_RTP_DEFAULT, using mgcp_send() to forward data directly 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:673 endpoint:0x21 delivering RTP packet... 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:682 endpoint:0x21 loop:0, mode:3 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:396 endpoint:0x21 transcoding disabled 20180110192222191 DRTP <0000> ../../../../src/osmo-mgw/src/libosmo-mgcp/mgcp_network.c:725 endpoint:0x21 process/send to 3 192.168.0.10 rtp_port:4002 rtcp_port:4003
What is going on here? Should we not enforce the source port in the first place? Has the RTCP source port become unconfigured for some odd reason?
Actions
