Does anybody have the configuration settings that they are using for FreePBX with Grandstream HT813 ATA on the UK PSTN network?
I could also do with the settings for an HT814 Grandstream ATA.
I had this working apart from caller ID and all of a sudden I cannot get things to work properly again.
I am unable to get the FXO port to dial out correctly, I either get a dead line or I get told the number I have dialled is incorrect.
Every time I put the ATA PSTN access code into the prefix box of an outgoing call route I get that error but without it I get no error and no outgoing call.
Incoming calls have also stopped working and I am finding it hard to find ways of troubleshooting the ATA Ports.
The UK doesn’t have a monopoly local loop operator, and I think different operators differ in their settings, particularly for caller ID. I don’t think everyone uses the BT, before first ring, system.
Also, within the next year, you can expect to be moved to an on premises ATA, as the analogue network is very close to shutdown, and, I think, has already been shut down, in some areas.
I assume this is not a PABX line (i.e. it is loop start, rather than earth start) and you are not in the wilds of Scotland. Note that SIN 351 still allows BT some implementation choices, even for this, particularly for how ringing current is injected, and how disconnect supervision is signalled.
My educated guess is that the correct CID mode is “ETSI-FSK prior to ringing with LR+DTAS”.
Enable Current Disconnect would probably be preferred, however any combination of the options is allowed on the network side.
I’d do AC termination by country.
It looks like the default first digit delay is long enough not to need to detect dialtone, but enabling dialtone detection would be better, if it works.
Digit length and dial pause each need to be at least 40ms.
Dialing a prefix such as 9 or 0 to get an “outside line” is not recommended for modern systems. Unless you need compatibility with a legacy system, you shouldn’t use one. Set up your numbering so you dial outside numbers the same as you would on a landline or mobile phone.
Log into the HT admin page and look at the Status tab. The FXO status should show On Hook (if not, check physical connection to PSTN line) and Registered (unless you configured the trunk with the static IP of the HT).
At the Asterisk command prompt type pjsip set logger on
or sip set debug on
according to the channel driver you are using.
Make a failing outgoing call to 020 3026 4621, paste the Asterisk log for the call at pastebin.com and post the link here. Call from an IP phone or softphone, so we aren’t concerned with possible issues with an ATA on the extension side. Repeat for a failing incoming call.
Also, post screenshots of the FXO Port tab on the HT.
Hi, it sounds like you’re having some issues with your Grandstream HT813 and HT814 on FreePBX. For UK PSTN, ensure your SIP settings point to your FreePBX IP and use your extension details for authentication. Set the PSTN accesshttps://19216801.pro/ code (like ‘9’ if required) and choose “UK” for Caller ID type. In your outbound route, make sure dial patterns align with UK formats, such as 0[1-9]xxxxxxxxx;. For troubleshooting,IP address check the FreePBX logs for SIP messages to identify issues, update your ATA firmware, and consider a factory reset if problems persist. If you have specific error messages or settings you’d like help with, feel free to share! Good luck!
Sure, but I would first confirm the electrical connection to the PSTN line by unplugging the cord from the HT and connecting an analogue phone in its place. Assuming that the phone can make and receive calls, the plug it back into the HT and do a factory reset.
Before re-entering the config, you should be able to connect a phone to the FXS port and make calls by dialing *00 to get dialtone from the PSTN. Incoming calls should also ring through to the FXS port. If those tests fail, the problem may be with the power supply. If you have one with the same voltage and polarity, sufficient maximum current and a compatible plug, try replacing that first. If you still have trouble, I think it’s likely that the hardware has failed. Was there recently a nearby lightning strike?
It’s puzzling that Asterisk is rejecting the Authorization header but repeatedly re-requests authentication.
Please confirm that the HT is registering to a pjsip trunk named 900, Authentication is set to Both, and Match Inbound Authentication is set to Auth Username. If no help, post a log (including pjsip logger) from the Asterisk side. and screenshots of trunk settings.
At the Asterisk command prompt (not a shell prompt) type pjsip set logger on
make the failing call, paste the Asterisk log for the call (at the end of /var/log/asterisk/full) and post the link.
Here is a pastebin of an outgoing call to my mobile.
My mobile does not ring and on this end the call just goes quiet.
I have replaced my numver with xxxxxx and my landline caller ID with yyyyyy and my public IP address with ddd.ddd.ddd.ddd FreePBX - Outgoing call - Pastebin.com
I get a 403 error trying to read the paste. Possibly it’s flagged as private or somehow triggered moderation. If retry doesn’t help, try pasting at pastebin.freepbx.org .
Your public IP should not be involved at all. What is the relationship between 172.16.40.64 and 172.16.50.118? Are they on the same LAN with a wide netmask? Or there’s a non-NAT router between them that doesn’t modify packets? Or they are part of a site-to-site VPN? Or something else?
Just guessing what might help, in Asterisk SIP settings, set Local Networks to 172.16.0.0/12, after Submit and Apply Config, restart Asterisk and retest.
