diff options
author | Harald Welte <laforge@osmocom.org> | 2021-02-06 15:25:39 +0100 |
---|---|---|
committer | Harald Welte <laforge@osmocom.org> | 2021-02-06 15:26:41 +0100 |
commit | 8c724c05517e5cb125599550ee5f6d43a04bbe69 (patch) | |
tree | 36d75e11ce18487c0b8cfe103c46fa4282a4b623 | |
parent | b3952c60f12fd2d2b2496a47ecb34dd5b966e0d8 (diff) |
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
-rw-r--r-- | src/trau/osmo_ortp.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/src/trau/osmo_ortp.c b/src/trau/osmo_ortp.c index 0cd4e9d..6e91f8d 100644 --- a/src/trau/osmo_ortp.c +++ b/src/trau/osmo_ortp.c @@ -202,8 +202,10 @@ int osmo_rtp_socket_poll(struct osmo_rtp_socket *rs) if (recv_with_cb(rs)) return 1; - LOGP(DLMIB, LOGL_INFO, "osmo_rtp_socket_poll(%u): ERROR!\n", - rs->rx_user_ts); + /* this happens every time we miss an incoming RTP frame, which is quite common + * 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; } |