Skip to content

Twilio call timing out #174

Closed Answered by hnimminh
Wurstcake asked this question in Q&A
Sep 20, 2024 · 4 comments · 5 replies
Discussion options

You must be logged in to vote

I believe I found what wrong here, your server has only 1 interface (eth0) and IP is 10.0.3.4.

external sip profile was configured wrongly. In general a service cannot listen on IP address that does not engaged.

correct way for your case is:
internal listen on port 5080 & use NetAlias private
external listen on port 5060 & use new NetAlias, example natnet

{
    "desc": "Network alias for Twilio external signaling and RTP",
    "name": "netnat",
    "addresses": [
        {
            "member": "vm-sbc-dev-sec",
            "listen": "<LibreSBC VM Private IP>",
            "advertise": "<LibreSBC VM Public IP>"
        }
    ]
}

Replies: 4 comments 5 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@hnimminh
Comment options

@Wurstcake
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
3 replies
@hnimminh
Comment options

Answer selected by Wurstcake
@Wurstcake
Comment options

@hnimminh
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants