Hi,
When I make an external call to someone the hangup is not detected when the external party initiated the hangup. My phone keeps on running like I still have a connection.
When I get an incoming external call and the external party initiates the hangup it does work.
Does this ring a bell?
Regards,
Emiel.
Typical of an analogue FXO line without answer supervision, or with the wrong sort of answer supervision configured. On the other hand, those who fail to identify the technology are usually using SIP, in which case this is a problem with the provider.
Hi david, yes it’s SIP. Haven’t used analogue for over a decade 
SIP trunk with the same settings on an older FreePBX has no issues. 
But I have send a support request to the provider to be sure.
That suggest that you are sending the wrong Contact address, but that would also cause calls to fail at 32 seconds, because it would also prevent the ACK arriving.
I suppose it could be a dynamic rule timing out in the router.
Solved, it was a NAT issue
In the old FreePBX the External Address (in Asterisk SIP Settings) was left empty but I think that wasn’t enough with FreePBX17. Disabling NAT in the advanced settings solved the issue.
The advanced NAT settings are dealing with a very different NAT context the public addresses and local networks.
Are the remote phones Cisco? I believe they can’t work with the workarounds that Asterisk uses for when the remote party is inside NAT and fails to compensate. Normal SIP environments can cope with these being turned on even when not needed. Public addresses are for when Asterisk is behind NAT and is aware of it.
Hi, remote phones in this case are Mitel 6800 and 6900 series.
This FreePBX17 is on a digital ocean vm.
Digital ocean assigns a wan and a lan ip address to the vm.
The old FreePBX was hosted somewhere else and only had a wan ip.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.