RTPengine - memory issue?

[Troy Changfoot]

Hi there,

We are experiencing a RTPengine failure when trying to handle siprec sessions using a subcribed RTP / forked relay setup with Opensips/SIPREC module.

The call recording initiates, but then rtpengine seems to run out of memory so the recording is unable to start??

Oct 27 08:43:22 [2614935] DBG:core:get_dummy_sip_msg: reusing the static sip msg 0x7f5f859f5760
Oct 27 08:43:22 [2614935] ERROR:rtpengine:parse_flags: error processing flag `rtpengine': no more memory
Oct 27 08:43:22 [2614935] ERROR:rtpengine:rtpe_function_call: could not parse flags
Oct 27 08:43:22 [2614935] DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0x7f5f859f5760
Oct 27 08:43:22 [2614935] ERROR:siprec:srs_handle_media: could not start recording!
Oct 27 08:43:22 [2614935] ERROR:siprec:srec_b2b_notify: cannot handle SRS media!

Any ideas to debug or get around this?  

Memory on the rtpengine is plenty:



Ordinary calls work, it just seems that when we try using rtp_relay / siprec we get this error.

Regards,

Troy

[Richard Fuchs]

On 27/10/2023 05.51, [EXT] Troy Changfoot wrote:

Hi there,

We are experiencing a RTPengine failure when trying to handle siprec sessions using a subcribed RTP / forked relay setup with Opensips/SIPREC module.

The call recording initiates, but then rtpengine seems to run out of memory so the recording is unable to start??

Oct 27 08:43:22 [2614935] DBG:core:get_dummy_sip_msg: reusing the static sip msg 0x7f5f859f5760
Oct 27 08:43:22 [2614935] ERROR:rtpengine:parse_flags: error processing flag `rtpengine': no more memory
Oct 27 08:43:22 [2614935] ERROR:rtpengine:rtpe_function_call: could not parse flags
Oct 27 08:43:22 [2614935] DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0x7f5f859f5760
Oct 27 08:43:22 [2614935] ERROR:siprec:srs_handle_media: could not start recording!
Oct 27 08:43:22 [2614935] ERROR:siprec:srec_b2b_notify: cannot handle SRS media!

Any ideas to debug or get around this? 

This error isn't coming from rtpengine itself, but rather from OpenSIPS's control module. Perhaps it has a memory leak, or perhaps you need to increase the size of the memory pool. Either way, you should direct this question to the OpenSIPS devs.

Cheers