My configuration was working, but it appears that some time ago it had stopped answering inbound calls. For my HW config I have an ATA FXO (HT813) and before that I splitter to a POTS phone for troubleshooting. Inbound calls continue to ring the POTS phone, but FreePBX believes that it has picked up the call when it hasn’t.
Again, I haven’t made any configuration changes, but I did have auto-update configured for modules and it has been several months since I’ve looked at the system.
Any assistance on where I should be looking would be greatly appropriated.
At this level of logging, it appears ok. We can try a SIP trace next; if that also looks normal we can use the HT syslog features to troubleshoot further.
However, first confirm that outbound calls through the HT trunk are working properly. If not, that is likely easier to debug.
For the SIP trace, at the Asterisk command prompt type sip set debug on
make another failing inbound call and paste the new log.
It appears that Asterisk responded to the incoming INVITE with a proper 200 OK and the HT replied with a proper ACK (which Asterisk must have treated as valid, because it did not retransmit the 200 OK).
So, why didn’t the HT trip the ring? Possibly, it’s something simple like a bad connector or cord. Please confirm that outbound calls via the HT trunk are working properly, and you have tried rebooting the HT. Also, post a screenshot of the HT Status page, refreshed just after the IVR announcement starts playing.
This is starting to look like a hardware failure in the HT. With luck, it’s just the power adapter and you have a compatible one from another device you can use to check.
The log shows an apparently OK call lasting 26 seconds. Do you you know whether the called phone rang? What happens when you pick up the bridged POTS phone while the call is apparently in progress?
No, the called number does not ring. Interestingly the FXO LED on the HT813 does flash when the outbound call is attempted. Picking up the bridged POTS line produces dial-tone.
Unfortunately, this looks like a hardware failure to me – the HT shows the line taken off hook but sufficient loop current did not flow.
Try with a different cord (and different wall jack, if applicable). Though unlikely, it’s conceivably a firmware corruption issue; try reloading it. Possibly, a power module issue (try a spare or check voltage and ripple when trying to call).
If your POTS service has call forwarding, you could redirect calls to a SIP trunk. For outbound, you can probably find a trunking provider that allows you to send the POTS number as outbound caller ID.
Replacing the HT813 worked. While I don’t see obvious damage to the old HT813’s board, I’m pretty sure that it had taken an ESD strike. So Stewart1, where do I send the beer?
