Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@rfuchs Thank you for this. I can confirm that this fixes the issue.
Feb 14 20:33:51 debian-kamailio kamailio[5066]: INFO: {1 63658613 INVITE 98dbb579-2773-123c-48af-80fa5d718101} <script>: failure_route: calling RTPMANAGE
Feb 14 20:33:56 debian-kamailio kamailio[5066]: ERROR: {1 63658613 INVITE 98dbb579-2773-123c-48af-80fa5d718101} rtpengine [rtpengine.c:3129]: send_rtpp_command(): timeout waiting reply for command "delete" from RTPEngine <udp:192.168.X.X:2223>
Feb 14 20:33:56 debian-kamailio kamailio[5066]: ERROR: {1 63658613 INVITE 98dbb579-2773-123c-48af-80fa5d718101} rtpengine [rtpengine.c:3382]: select_rtpp_node(): rtpengine node for callid=98dbb579-2773-123c-48af-80fa5d718101 is known (udp:192.168.X.X:2223) but it has already been queried, therefore not returning it
Feb 14 20:33:56 debian-kamailio kamailio[5066]: ERROR: {1 63658613 INVITE 98dbb579-2773-123c-48af-80fa5d718101} rtpengine [rtpengine.c:2735]: rtpp_function_call(): no available proxies
Feb 14 20:33:56 debian-kamailio kamailio[5066]: INFO: {1 63658613 INVITE 98dbb579-2773-123c-48af-80fa5d718101} <script>: failure_route: completed calling RTPMANAGE
I can also confirm everything still works normally when rtpengine is up; and when there are multiple rtpengine instances and one is unavailable (ie initial node selection works as normal).
The only very minor observation I have is that the call remains in the hash table until hash_table_tout as observed with kamcmd rtpengine.get_hash_total. I assume this happened before, and it's very minor, but thought I'd mention it.
Apologies if info on release cycles is somewhere already & my eagerness, but can I ask when I should look out for a release with this patch?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.