ahhhh… There is no “but” about… More like one simple question.
I have a Grandstream HT813 firmware v. 1.0.17 that I took too 1.0.19(beta) after much trouble with the original version not registering with freePBX (I can go back down to 17 as the beta gives clutter I’m not interested in).
I also have freePBX version 17.0.28 running on a proxmox server as a vm on debian 12.
I used sngrep to watch the traffic and my best guess is that the HT813 cannot respond to an authentication request by freePBX. I tried a number of ways to get the hash types to match.
That really doesn’t matter. Will these versions work together? Will the HT813 register with freepbx or do I need older versions?
Has anyone here gotten an HT813 to work with freepbx with the versions mentioned? Or tell me what versions are currently working for you. If I know it can be done then I can get it done.
Are you having trouble with the FXS side, the FXO side, or both?
For the FXS, the HT username should match the extension number and the HT SIP password should match the extension Secret.
For FXO, the HT username should match the trunk name and the HT SIP password should match the trunk secret. Try these trunk settings:
Authentication: Both
Registration: Receive
Match Inbound Authentication: Auth Username
Rewrite Contact: Yes
Force rport: Yes
If you still have trouble, paste the Asterisk log for a failing registration or call, with pjsip logger turned on, at pastebin.com .
I’ve been busy but to say thank you I must. After endless hours I figured how stopping the firewall off the bat didn’t stop the IDS on freepbx. That killed me that hill in the road.
I can say for anybody interested in the question I posed. Yes, it can be done with that hardware and software versions. Basic phone functionality at least. :0)
I’m looking forward to reaching the Himalayan roof top when my zoiper laden cell phone can forward calls to freepbx and process those calls for me. I want control of my phone back.
I got around to fixing it. That hardware and software version work to give you back basic phone functionality. I can say that. I hope to make it do more than that. Learned a lot through a bunch of mistakes/errors. I could have learned less would probably made me happier.
I have it on none and none. I’m hoping to VLAN it and have the firewall and IDS back up an running. It was a real catch-22. I like my authentication but it stripped away my caller ID on 1 ring and canceled the call on 2 rings when authenticating. So my FXS registers while FXO doesn’t. Seems I’m going to have to live with that for as long as the land line lives. That “asterisk -rvvvvv” is the bee’s knees as was a multitude of AI. Couldn’t have done it without them and took to long to do it with them.
Thanks for your time. I might use this thread to build this out for someone else to follow.
After going around in circles with the authentication going from none to both and receive/send… blah blah…
I made a second trunk. And they both fxs/fxo ended up authenticating and registered. All thanks to sngrep and asterisk -rvvvvv and some AI. I’m just worried about entering a third trunk for my cell phones. Trying to reason it out before trying. (when you none it you get no registration and no asterisk traffic).
I’m just working on getting the IVR working next. Just got to crank up my audacity to make some spec recordings. I proxmox’ed the freepbx and decided to add three servers more to that proxmox and a container. Has taken my time up to responding. Of course went much faster than that blasted freepbx and that IDS… I’ll remember that.