We have alot of calls that are between 22s and 23s, with status Silence Timed Out and we don't understand what is happening with the call, we are using SIP trunking with squaretalk, can you please check it and see what info can you get for us ? CID: 36f33444-19c4-4aac-ac19-80f78c92d1d2 c2d77ca5-a214-4779-a454-8b8b72e89fc1 0d2dbc15-7f0d-4029-a29a-2a1af1aa45bd e9bbca11-4d4f-4e6e-8cb4-5c7977d191f9 0b5e9546-bce7-4be2-bb35-2e0d308c9cb2 . there are litteraly hundreds if not thousands of calls like this.

I see you're experiencing a lot of calls with "Silence Timed Out" status that end around 22-23 seconds when using SIP trunking with Squaretalk. This typically happens when the system detects silence for longer than the configured timeout period. To help troubleshoot this issue more effectively, could you share any of these details: 1. Have you checked or modified the

silenceTimeoutSeconds

parameter in your configuration? The default is usually 30 seconds, but it sounds like yours might be set to around 20-25 seconds. 2. Are you using any voicemail detection settings like

machineDetectionSilenceTimeout

or

machineDetectionTimeout

? 3. Have you noticed any patterns in these calls - are they all to specific numbers, at certain times of day, or following a particular action in the call flow? 4. Have you recently made any changes to your SIP trunk configuration with Squaretalk before these issues started occurring? This information would help me provide more targeted troubleshooting advice for your specific setup. Sources: - [Definition of "silence-timed-out"](https://docs.vapi.ai/calls/call-ended-reason) - [Silence Timeout Settings](https://docs.vapi.ai/api-reference/calls/delete) - [Voicemail Detection Settings](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336548894896816222)

1. I had voicemail detection at 15 seconds. 2. not using 3. no pattern, happens all the time 4. no changes from my side.

Allow me some time to get back to you on this with proper investigation.