Hi! We have an issue with call statuses getting stuck in VoiceAiWrapper. We have 38 calls in the “Registered” status and 1 in “Ongoing”. We can’t find the calls with the “Registered” status in Retell. Only the 1 “Ongoing” call is visible there. We also checked it in Twilio — the call was ended by Retell and lasted 4 seconds. Could you please help us resolve this issue? "Registered" call_f9465ce810528d660eeb42e4cae call_0b9d40682e5593fb5909580c12f call_14fcba031a6172cbaef89deaf8b call_16fd3e492e72615f55499ffbf65 call_1f30b3256f1bb8569c656cdce31 call_259753b3dab261c707bcf9f42ea call_2d885d62e1d3afadfcb8c5212e1 call_38b4f47def19e6fe9ca9277a8db call_3e3ac264f5c8a57bc38e6c69fb9 call_3f2a88dd128db210248754a2993 call_3f774c624a0e956e43328c4c76a call_40385f427cd70cc5a6bdafb763a call_48fefc39db6c46cdbfa4f72b753 call_64fae51bb18501eb034a5ecf86d call_6d90c7e8300a666d999d695ced0 call_811fde945da374adfb0b72eada1 call_817d1556a8939d9dbf5ffb0d078 call_8d12bffba4d606cfe0bee6e87ec call_8d6bbc859c24378ce2ca430b565 call_8e4f8344c4cd5826b45e3793369 call_06001d4bb21bf5b34d8e2cfc53a call_90c7072e328930a8818084aa056 call_a796d0e5f2a4ec6ee8bfb6985ea call_aa3c8d43081a1dc7f7bff297e29 call_b014a5bafc078d1ad135bcce46b call_b12dbcf2edabb810bd6a77f5766 call_b42fa8c3a7f2b4d5eb0725c04e9 call_b447efcf13f8fdbd2c876236e59 call_b65f4808d99e2b87bc19a93f4c7 call_bbcc2600f822a4b60bfe2608569 call_be2a62d1c81f1a6227b6877bf86 call_c4410685750803bebf534183940 call_cc89e7eb1154387c3c720916081 call_e1bef0d49621590f96244695c16 call_e87d9fb8c11fd702fd4f7ee9a52 call_ec6d18eaece28cd41456707f98d call_f1b6e818c6c6f39112dc9dd4602 call_f6e72828dd2e41d826afc2118ef "Ongoing" call_8fff29a3eed188b4a0e65221b2d https://cdn.discordapp.com/attachments/1455586990043955313/1455586990455259208/image.png?ex=697985c6&is=69783446&hm=e4ec4b63fb3990f8c14a828868033fdabbcf146d6a2ba9cc61066a003967dc94&

can you elaborate a little bit about voice AI wrapper? i haven’t heard of this one

Please check this video It's about how calls stocks @User https://yash-sf-workspace.neetorecord.com/watch/ec767984ca0fab501f2b The calls we make are stuck in “Registered” or “Ongoing” status in VAW. This status is assigned by your system. Of the calls listed, we only found calls with “Registered” status in the Retell logs. Please help us resolve this issue.

so voice ai wrapper isn’t apart of our native software

Can you check this issue on your end?

@User guys please assist us, it's urgent as we can't use our RetellAI properly, check stuck calls we provided you in a list and fix this issue

Hello @Phill , the calls with Registered status, is calls that is Registered so it can be used using dial to sip method , but if the calls is not used in a call it will stay as Registered, and Registered calls do not show up in the dashboard.

@Omar Ashraf | Community Lead Can you fix their status so that they are not listed as “Registered”?

This is the correct status for these calls , they were Registered but not used, there is nothing wrong with them.

@Omar Ashraf | Community Lead roger, can you please internally change "call_status" value from "registered" to "ended" for this calls? I think this action will resolve our issue call_06001d4bb21bf5b34d8e2cfc53a call_060d1dd403af5f4e76a440ab19d call_0b9d40682e5593fb5909580c12f call_14fcba031a6172cbaef89deaf8b call_16fd3e492e72615f55499ffbf65 call_1f30b3256f1bb8569c656cdce31 call_259753b3dab261c707bcf9f42ea call_2d885d62e1d3afadfcb8c5212e1 call_38b4f47def19e6fe9ca9277a8db call_3e3ac264f5c8a57bc38e6c69fb9 call_3f2a88dd128db210248754a2993 call_3f774c624a0e956e43328c4c76a call_40385f427cd70cc5a6bdafb763a call_4383253ce7bd446a7f15ec26a5b call_48fefc39db6c46cdbfa4f72b753 call_64fae51bb18501eb034a5ecf86d call_6d90c7e8300a666d999d695ced0 call_811fde945da374adfb0b72eada1 call_817d1556a8939d9dbf5ffb0d078 call_840553f8c5c0c332f60f2c7e3de call_8d12bffba4d606cfe0bee6e87ec call_8d6bbc859c24378ce2ca430b565 call_8e4f8344c4cd5826b45e3793369 call_90c7072e328930a8818084aa056 call_97ae0c4fcb3f2dc141e4ec95b12 call_9c12edde5e42f0e7437cff1bb2a call_a796d0e5f2a4ec6ee8bfb6985ea call_aa3c8d43081a1dc7f7bff297e29 call_b014a5bafc078d1ad135bcce46b call_b12dbcf2edabb810bd6a77f5766 call_b42fa8c3a7f2b4d5eb0725c04e9 call_b447efcf13f8fdbd2c876236e59 call_b65f4808d99e2b87bc19a93f4c7 call_bbcc2600f822a4b60bfe2608569 call_be2a62d1c81f1a6227b6877bf86 call_c4410685750803bebf534183940 call_cabea6abbcbd01827bef92e81d0 call_cc89e7eb1154387c3c720916081 call_e1bef0d49621590f96244695c16 call_e87d9fb8c11fd702fd4f7ee9a52 call_ec6d18eaece28cd41456707f98d call_f1b6e818c6c6f39112dc9dd4602 call_f6e72828dd2e41d826afc2118ef call_f9465ce810528d660eeb42e4cae

I will ask the team if this is possible, can you tell me why making the status ended will solve your issue ?

Thank you! This calls are stuck in registered status since previous year and it's using our available RetellAI concurrency, so we can't use all our available lines, only which left

this is not taking any concurrency , the current concurrency for this workspace is 2 , for calls that is actually is ongoing.

Hello! The system we use does not receive information about the end of a call, so it keeps the concurrency closed This means we lose one concurrency for each call that is stuck in the registered status Therefore, please change the status of these calls and then let us know if we can change the status of calls, for example, via API, considering that we make a lot of calls per month and this is important to us