Twilio ACK not received from the SIP endpoint

ive just realised @Stewart1 that the 3rd site i look after which has the exact same setup and has NEVER EVER had any problems with twilio or this ACT issues,
they dont have any external VOIP phones, all there phones are internal to there freepbx server!

so i do think you could be correct that its one of the phones hogging the port in the router!

and after checking the firewall connections and changing columns to see properly,
it is indeed from the looks of it, one of the voip phones hogging the 5060 port!

some phones register back to 5061 because they have 2 extensions, first one internal, second one external (cloud provider)

im managed to capture it right as it was doing an OPTIONS to twilio (54.14.xxx.xxx IP),
i have no idea WHY its now using port 1694 on the returning?

I stage any on-prem PBX in our lab which is behind an RB4011 that has 5 IP phones connecting back to the cloud platform for our office phones. We stage all our of FXS gateways and IP phones at the same location. All of them have a primary account that listens on 5060.

There can be times where I have the standard office phones for us, a PBX being staged and gateways/IP Phones for other installs being staged. Been doing this for the better part of a decade with Mikrotik’s in front of everything. I cannot replicate these kinds of issues.

That doesn’t matter, it really really doesn’t matter that the external port is 5060. The external NAT port could be 3035 and that is where the location would use for sending incoming calls.

Do you have any port forwarding for the RTP ports setup?

At this point let’s see the firewall settings for this RB1100…log into the terminal and do ip/firewall/export, if any of your external IPs are in there clean them up but I want to see how this firewall looks.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.