I followed the instructions of setting up telnyx with vapi and inbound and outbound calls work.. The issue is that the hangup event is reporting incorrectly.. No matter who hangs up (us or the person we are calling) the event will report "hangup_source: 'callee'" which is incorrect! This is why it is happening.. The number we are calling is being registered as a telnyx sip when it is not.. "{ call_control_id: 'v3:xdH5qvDdgeMjouxcmCYYk1fKE_3EDuPPxwkB8N0Cw4lkz0XKvaK4mQ', call_leg_id: 'ed791788-b8f9-11ef-a5bb-02420aef2220', call_session_id: 'ed791e9a-b8f9-11ef-babe-02420aef2220', calling_party_type: 'sip', client_state: null, connection_id: '2582325413673960809', custom_headers: [ { name: 'X-Account-Sid', value: 'b464c6be-906f-4e97-a6ff-44cd837bf4a4' }, { name: 'X-Call-Sid', value: 'b5ef8d72-6367-493f-add4-7f59208e3a9d' } ], direction: 'outgoing', from: '+18183810450', from_sip_uri: '18183810450@44.229.228.186:5060', state: 'bridging', to: '+18182826756', to_sip_uri: '327618182826756@sip.telnyx.com' }" Is there a work around to this?? @Vapi @Shubham Bajaj

@John I'm sorry to hear you're experiencing issues with the hangup event reporting. It seems like there might be a misconfiguration or a bug that's causing the system to incorrectly identify the hangup source. To address this issue, I would recommend checking the following: 1. **Configuration Check**: Ensure that your Telnyx and VAPI integration is configured correctly. Double-check the webhook URLs and the event settings to make sure they are pointing to the right endpoints and are set up to handle events correctly. 2. **Event Handling**: Verify that your event handling logic is correctly interpreting the events sent by Telnyx. It's possible that the logic might be assuming the hangup source or not handling the event data properly. 3. **Contact Support**: Since this seems to be an issue with how the system is interpreting the SIP information, it would be best to reach out to VAPI support with the details you've provided here. They will be able to look into the system logs and configuration to determine why the hangup source is being incorrectly reported. 4. **Workaround**: As a temporary workaround, you might consider implementing additional logic in your event handling to determine the hangup source based on other call details or states, if possible. If you would like me to assist you further by contacting support or if you need help with any specific configuration, please let me know.

@John let me check with team.