[OpenSIPS-Devel] [OpenSIPS/opensips] bf4e33: rtpproxy: drain timeout notification sockets

Bogdan Andrei IANCU noreply at github.com
Tue Jun 9 06:17:42 UTC 2026


  Branch: refs/heads/master
  Home:   https://github.com/OpenSIPS/opensips
  Commit: bf4e33fc74611a5dd0e7372325f4cfcb77da6fed
      https://github.com/OpenSIPS/opensips/commit/bf4e33fc74611a5dd0e7372325f4cfcb77da6fed
  Author: Maksym Sobolyev <sobomax at sippysoft.com>
  Date:   2026-06-06 (Sat, 06 Jun 2026)

  Changed paths:
    M modules/rtpproxy/notification_process.c

  Log Message:
  -----------
  rtpproxy: drain timeout notification sockets

RTPProxy may keep the notification connection open while writing a burst of
timeout events.  The rtpproxy notification callback only performed a single
read per reactor wakeup, so already-buffered notifications could be left
pending with no further event to wake the process.

Set notification sockets nonblocking and drain them until EAGAIN, preserving
partial commands between callbacks.  Also centralize notification connection
cleanup so error, EOF and handler failure paths consistently unregister the fd,
free pending data and close the socket.


  Commit: bfdfa97c5a0f72f604008e99374726fde972f3ab
      https://github.com/OpenSIPS/opensips/commit/bfdfa97c5a0f72f604008e99374726fde972f3ab
  Author: Bogdan Andrei IANCU <bogdan at opensips.org>
  Date:   2026-06-09 (Tue, 09 Jun 2026)

  Changed paths:
    M modules/rtpproxy/notification_process.c

  Log Message:
  -----------
  Merge pull request #3911 from sippy/pr_rtpproxy_nsock_drain

rtpproxy: drain timeout notification sockets


Compare: https://github.com/OpenSIPS/opensips/compare/bd831dad1742...bfdfa97c5a0f

To unsubscribe from these emails, change your notification settings at https://github.com/OpenSIPS/opensips/settings/notifications



More information about the Devel mailing list