Project

General

Profile

Bug #3511

osmo-mgw does not forward RTP packets anymore

Added by dexter about 2 years ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/29/2018
Due date:
% Done:

100%

Spec Reference:

Description

The MGW that is located next to the BTS seems not to forward any RTP packets. There are RTP packets comming from the BTS, but none of them get forwarded. The MGCP negotiation looks correct on the first look. All the ports match up and the circuit seems to be closed.

Attached one finds the configuration files, a trace and a map of the RTP traffic I worked out.

1535542883.tar 1535542883.tar 1.21 MB dexter, 08/29/2018 12:28 PM

History

#1 Updated by dexter about 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

Apparently the reason for the fault is in the following change: Ie51cc86e90ffeca5b66bcb8f6db0d389241abe57. The client can now only create connections in MGCP_CONN_RECV_ONLY, which explains the behavior.

#2 Updated by dexter about 2 years ago

  • % Done changed from 90 to 100

The problem should now be fixed, see also:

https://gerrit.osmocom.org/#/c/osmo-mgw/+/10690 mgcp_client_fsm: switch to MGCP_CONN_RECV_SEND in add_audio()

#3 Updated by neels about 2 years ago

Hmm, I tested the patch and was routing voice calls with it all the time.
I see now that the patch did indeed cause this conn_mode change, my bad, but I'm still wondering:
shouldn't the MGCP messages indicate explicitly the receive/send mode?

#4 Updated by laforge 7 months ago

  • Assignee set to dexter

what is the status here? Can this be closed?

#5 Updated by dexter 7 months ago

  • Status changed from In Progress to Resolved

Yes, we can close this.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)