search

livekit / sip

SIP to WebRTC bridge for LiveKit
111 stars 26 forks source link

Twilio Test Error #170

Closed tricksterANDthug closed 1 month ago

tricksterANDthug commented 1 month ago

My twilio phone number is +14707983338 and public ip of aws is 107.20.81.14 .I am using Twilio's SIP Trunking service and have deployed the corresponding SIP service on an AWS server with port 5060. The result is show below:

截屏2024-09-10 17 17 30

I have configured the Origination SIP URI in Twilio's SIP Trunking settings as sip:107.20.81.147:5060, where 107.20.81.147 is the server's public IP. Since I am only using the inbound functionality, no configuration was made in the Termination URI. The ports 5060 and the corresponding RTP ports 10000-20000 are open on the server, and the IPs listed on this page https://www.twilio.com/docs/sip-trunking/ip-addresses can access the server. I made a call through Skype, and the error code displayed in the backend is 32011. In this situation, where is the most likely place where the issue could be occurring?

tricksterANDthug commented 1 month ago

I have also started the LiveKit server and the corresponding AI agent, the result is show below:

截屏2024-09-10 17 25 29
dennwc commented 1 month ago

First, you may have noticed that LiveKit logs show a conflict error for SIP Trunks. Without proper configuration LiveKit SIP may reject the calls.

Second, I would suggest checking Twilio Error Logs to see what kind of error is reported there for this call. Downloading PCAP to diagnose these issues may be helpful as well.

Also, the screenshots do not show any logs for SIP service during the call. This may mean that the service is not getting any SIP messages at all. Could be a firewall or MTU issue.