Hey, I can definitely help with this. The core issue is that Vapi's SIP trunk registration uses its own sip.vapi.ai domain in the From/To headers by default, rather than your trunk domain. Karel is expecting those headers to reflect your domain (tolunaydin.connect.com) so it can correctly associate the registration with your trunk which is why the call tracking breaks down. Some of this can be addressed through Vapi's SIP trunk configuration, but the extent of header-level customisation depends on how your trunk is set up on the Vapi side. Can you share a screenshot or export of your current SIP trunk configuration in Vapi? That'll let me tell you exactly what can be changed and what might need a workaround.