[SR-Users] RTPEngine UDP receive queue issue

Alex Balashov abalashov at evaristesys.com
Wed Aug 8 19:05:15 CEST 2018

On Wed, Aug 08, 2018 at 09:38:02AM -0400, Richard Fuchs wrote:

> On 2018-08-08 09:25, Alex Balashov wrote:
> > Richard,
> > 
> > rtpproxy classic edition had an SDP attribute that could be inserted to
> > prevent rtpproxy from operating on the SDP if another rtpproxy had
> > already been engaged upstream. Does RTPEngine have a similar feature?
> > 
> Yes, if you include the `loop-protect` option.

Thanks! Are there any SDP interoperability concerns with using it?

The other aspect of this that I am puzzling over is where the packets in
this loop are coming from. The call is long dead, the ports involved are
not in use (per the RTPEngine call list), but I'm still getting:

Aug 08 12:50:00 gw1 rtpengine[18934]: ERR: [992251125_16092378 at x.x.x.x port 60368]: Too many packets in UDP receive queue (more than 50), aborting loop. Dropped packets possible

Are these RTP frames that were previously sent at some point during the
call looping?

-- Alex

Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

More information about the sr-users mailing list