We have a recurring issue with PBX extensions deregistering after approximately 10-15 days of uptime. This is causing service interruptions. Could you please investigate if any recent vAPI changes or updates are a potential cause? We would appreciate any insight you can provide to help us troubleshoot this problem. @Vapi Extension registers SIP credentials

Hi Harry, To address the issue with your PBX extensions deregistering every 10-15 days, please ensure the following: 1. **SIP Trunk Configuration**: Double-check that your SIP trunk configuration is correctly set up, particularly if your provider requires periodic re-authentication or supports long registration duration. Refer to our [SIP Trunking guide](https://docs.vapi.ai/advanced/sip/sip-trunk) for detailed setup instructions. 2. **Network Stability**: Verify that there are no intermittent network issues that could be impacting your SIP trunks or PBX communication. Ensuring stable and continuous connectivity is crucial. 3. **VAPI and Provider Compatibility**: Make sure that your VAPI configurations align well with your SIP provider's requirements and settings. Some settings such as maximum call duration for VAPI were updated, which is now up to 43,200 seconds (12 hours) as mentioned in the [recent changelog](https://docs.vapi.ai/changelog/2024/10/19). 4. **Logs and Error Codes**: Review the error codes found in the VAPI logs related to call completion status or SIP-related errors. Specifically, codes such as

call.in-progress.error-sip-telephony-provider-failed-to-connect-call

might provide insights. 5. **PBX Settings**: Check for any PBX settings that might cause deregistration, such as SIP registration timeout or reauthentication intervals. If after checking these areas the issue persists, consider reviewing your PBX and SIP provider documentation for additional troubleshooting steps or common configurations for long-term stability. If this doesn’t resolve the issue, please let us know and we’ll be happy to step in and assist further.