This seems to be more tm issue rather then rtpengengine module. I think it may happen if for any reason RTPEngine dissapears between offer in invite and ack
Nov 28 10:08:11 ip-10-23-247-205 /usr/sbin/kamailio[14702]: [INVITE eldnybgg6e_87665 src_ip:3010@udp]--> ERROR: rtpengine [rtpengine.c:2538]: send_rtpp_command(): timeout waiting reply from RTP proxy <udp:rtpengine_ip:22222>
Nov 28 10:08:11 ip-10-23-247-205 /usr/sbin/kamailio[14702]: [INVITE eldnybgg6e_87665 src_ip:3010@udp]--> ERROR: rtpengine [rtpengine.c:2412]: rtpp_test(): proxy did not respond to ping
Nov 28 10:08:11 ip-10-23-247-205 /usr/sbin/kamailio[14702]: [INVITE eldnybgg6e_87665 src_ip:3010@udp]--> ERROR: rtpengine [rtpengine.c:2749]: select_rtpp_node(): rtpengine failed to select new for calllen=30 callid=eldnybgg6e_87665
Nov 28 10:08:11 ip-10-23-247-205 /usr/sbin/kamailio[14702]: [INVITE eldnybgg6e_87665 src_ip:3010@udp]--> ERROR: rtpengine [rtpengine.c:2239]: rtpp_function_call(): no available proxies
Nov 28 10:08:11 ip-10-23-247-205 kernel: [586868.258562] show_signal_msg: 30 callbacks suppressed
Nov 28 10:08:11 ip-10-23-247-205 kernel: [586868.258566] kamailio[14702]: segfault at 24 ip 00007efca782242e sp 00007fffbef66410 error 4 in tm.so[7efca775c000+138000]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.