You are right. Thank you for the suggestion. On 25/06/2021 12:04, Răzvan Crainea wrote: > I am 90% sure this has been fixed in the latest sources. The 10% > hesitation comes from the fact that you haven't specified the version > you are running. > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > On 6/25/21 12:52 PM, johan wrote: >> hmmnm, >> >> Core was generated by `/data/opensips/sbin/opensips -P >> /var/run/opensips/opensips.pid -m 64 -M 4 -u ro'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 0x00007f1677a72fda in notification_listener_process (rank=0) at >> notification_process.c:345 >> 345 *rtpp_notify_process_no = process_no; >> (gdb) bt full >> #0 0x00007f1677a72fda in notification_listener_process (rank=0) at >> notification_process.c:345 >> saddr_un = {sun_family = 54088, >> sun_path = >> "(x\026\177\000\000\000\000\000\000\000\000\000\000PF\000\000\000\000\000\000\060\v\036\001\223U\000\000\020\370{$\376\177\000\000l{(\001\223U\000\000`\370{$g\245\370@LO%\001\223U\000\000PF\000\000\000\000\000\000\220\341P|\026\177\000\000\036\000\000\000\000\000\000\000\021\353#\001\223U\000\000p\370{$\376\177\000\000\000\000\000\000\000"} >> >> saddr_in = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = >> 4294967294}, sin_zero = "\310\004\356{\026\177\000"} >> p = 0x5500011e0b30 <error: Cannot access memory at address >> 0x5500011e0b30> >> id = {s = 0x0, len = 20658503} >> port = 0 >> saddr = 0x101287cce >> len = 32766 >> n = 0 >> optval = 1 >> socket_fd = 612104256 >> __FUNCTION__ = "notification_listener_process" >> #1 0x0000559301288b4d in start_module_procs () at sr_module.c:847 >> m = 0x7f167bedfc78 >> n = 0 >> l = 0 >> flags = 12 >> x = 0 >> __FUNCTION__ = "start_module_procs" >> #2 0x0000559301280df9 in main_loop () at main.c:206 >> chd_rank = 0 >> startup_done = 0x0 >> last_check = 0 >> rc = 0 >> __FUNCTION__ = "main_loop" >> #3 0x00005593012845f6 in main (argc=15, argv=0x7ffe247bfa48) at >> main.c:916 >> cfg_log_stderr = 1 >> c = -1 >> r = 0 >> tmp = 0x7ffe247c0f16 "" >> tmp_len = 0 >> --Type <RET> for more, q to quit, c to continue without paging-- >> port = 1 >> proto = 32766 >> protos_no = 1 >> options = 0x5593013afb28 >> "f:cCm:M:b:l:n:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:" >> ret = -1 >> seed = 2724266361 >> rfd = 3 >> __FUNCTION__ = "main" >> >> >> config file in attach. >> >> >> >> On 25/06/2021 11:25, Răzvan Crainea wrote: >>> No, SIPREC can not currently work with rtpengine due to the fact that >>> RTPEngine cannot fork the media stream to a new destination, at least >>> not as RTP. AFAIK, only RTPProxy can do this now. >>> >>> Best regards, >>> >>> Răzvan Crainea >>> OpenSIPS Core Developer >>> http://www.opensips-solutions.com >>> >>> On 6/25/21 11:44 AM, johan wrote: >>>> Hi, >>>> >>>> >>>> can the opensips configuration for siprec work with rtpengine ? >>>> >>>> To me it seems that it is dependant on rtpproxy. So how can I >>>> combine >>>> siprec with rtpengine for a script in which rtpengine is always in the >>>> middle. >>>> >>>> >>>> wkr, >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
OpenPGP_0xD7D896F7DDA70EC3.asc
Description: OpenPGP public key
Description: OpenPGP digital signature_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
