Issue with customer phone formatting with Inbound ...
# support
c
Hello Vapi Team, I have a system I designed some time ago that in some cases is supposed to transfer to a destination I specified, but recently an issue appeared which causes s problems. First of all, I see in my call logs that some calls do not have the user phone number showing, but the call goes through. I used the API to get the call details, and saw that the reason the call logs dashboard is not showing the customer number is because the number is formatted incorrectly. An example of how the number looks is +17869612345;oli=62;rn=+15619270000 Second, is that since VAPI is receiving the number incorrectly, when my assistant tries to transfer the call it doesnt work. VAPI just ends the call. The weird thing here is that this issues only happen with some numbers, not all. We have not seen any pattern, so its been hard to work with this issue. This issue appeared out of the blue, and has been causing havoc in our client's campaigns. I will leave a callId here so you can see the issues. Thanks in advanced. Call ID: cf438677-6929-4642-965d-6a5684d5dec6
@User sorry for the ping.
c
Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!
c
all the info you need is above
havent been able to solve the issue I dont understand how something so native to vapi like a call transfer isnt working out of the blue.
I tried to force format the customer number when it hits my server, but still nothing solves the formatiing issue
@Vapi Support Bot
c
Thank you for providing the call info. We are reviewing the details of your request and will reach out to you when we have an update or if we need additional information.
c
For sure thank you.
Still trying to find a fix but haven't been able to resolve the issue.
c
Hi, could you please provide another call id that is more recent? We would like to review the logs for a consistency check of the issue
c
I just saw your response my bad. Here is the id: b078e635-e740-4254-99ae-4aa8a3d7a43f
its been very inconsitent. Some days 80% of calls fail to transfer, and other days all calls work as normal.
No clue what the issue is and havent been able to fix it. Seems to be a sip parsing issue
c
We see that you are using gpt-4.1 as the model, which is not as strong as gpt-4o in terms of complex logic handling especially with tool calls. We recommend switching to gpt-4o for test purposes and see if it improves your results with transfers
3 Views