Bug #3511
closed
osmo-mgw does not forward RTP packets anymore
Added by dexter over 5 years ago.
Updated about 4 years ago.
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.
Files
- 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.
- % Done changed from 90 to 100
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?
what is the status here? Can this be closed?
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
