osmo_ortp: Don't print ERROR message for every missing RTP frame
* it's inconsistent to print ERROR in a LOGL_INFO message * loosing RTP packets is not that unusual, especially when the channel is just starting up Change-Id: Ide0017987b4cea7fd24795941494f1da913ea673 Closes: OS#4464
This commit is contained in:
parent
b3952c60f1
commit
8c724c0551
|
@ -202,8 +202,10 @@ int osmo_rtp_socket_poll(struct osmo_rtp_socket *rs)
|
||||||
if (recv_with_cb(rs))
|
if (recv_with_cb(rs))
|
||||||
return 1;
|
return 1;
|
||||||
|
|
||||||
LOGP(DLMIB, LOGL_INFO, "osmo_rtp_socket_poll(%u): ERROR!\n",
|
/* this happens every time we miss an incoming RTP frame, which is quite common
|
||||||
rs->rx_user_ts);
|
* when a voice channel is first activated, or also in case of packet loss.
|
||||||
|
* See also https://osmocom.org/issues/4464 */
|
||||||
|
LOGP(DLMIB, LOGL_DEBUG, "osmo_rtp_socket_poll(%u): No message received\n", rs->rx_user_ts);
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue