Call IDs: 019caf16-e5ad-7770-9d69-dff29014f8ec 019caf98-0f44-7000-852e-532459b73dfd I’ve integrated an SIP and initiated outbound campaign dialling. There are two issues. 

Firstly, The calls are not being logged at the end of the SIP Provider (https://voip.ms/). They’ve reviewed our SIP Logs (attached within this message) and they believe this is because currently INVITEs contain no SIP authentication hence they are not entering carrier billing context therefore they are not being logged. Do we have the capability to adjust this? Secondly, The calls are not being transferred. The transfer is initiated in call, the call keeps ringing but is never received on the destination number. The SIP logs also show nothing related to the transfer. 

Kindly help resolve these issues at the earliest. Thankyou https://cdn.discordapp.com/attachments/1478715395421507746/1478715395551662142/SIP_Logs.zip?ex=69a96887&is=69a81707&hm=8e43d87612b2c4067a1609a9edb037562d679510a4d9a925f9550f5f2feb56c0&

On the SIP auth issue, if the INVITEs are going out without proper authentication headers, VoIP.ms won’t place them into billing context, which explains why they’re not logged; we’ll need to confirm whether your trunk is set to IP auth or username/password auth in VoIP.ms and how it’s configured in Vapi. For the failed transfers, if nothing shows in the SIP logs, it usually means the REFER or re-INVITE isn’t being triggered correctly from the platform side. Can you confirm: are you using credential-based auth or IP whitelisting on the trunk, and are transfers set up as SIP REFER or as a new outbound leg? @anstariq

If I understood correctly, I used credential-based auth when setting up the SIP Trunk Credentials as can be seen in the screenshot attached. For the second part, can you please guide where I can check if transfers are set up as SIP REFER or new outbound leg. I am attaching the tool id for reference that is used to transfer the call incase it helps you to check this information: bf4ab468-c5b2-40bc-bd24-6ece954c50b8 https://cdn.discordapp.com/attachments/1478715395421507746/1478798752700436480/image.png?ex=69a9b629&is=69a864a9&hm=66f2e4d6dd0f5f5e9785313812ab962459cd2e6bf289c3cd604032283992b578&

Thanks for the screenshot, that confirms you’re using credential-based auth with VoIP.ms. If INVITEs aren’t carrying the auth headers from Vapi, that’s likely why calls aren’t entering billing or being logged. For transfers, if nothing shows in the SIP logs, the REFER (or second outbound leg) probably isn’t being triggered at all. I can help you trace the INVITE and transfer flow properly and pinpoint the break. Let’s take this privately and review the config together so we can sort it quickly. @anstariq

Thankyou for the swift response! Sure lets do that

Hi Anstariq, Just checking in- please let us know if you are still facing this issue or if everything is working on your side now.