Help needed setting up HT803v2

fin1000

Running 2.9.0
Attempting to set up ht802v2 on one of my vlans
In and out to service ips and udp port set with alias
No reports in log of blocking to or from VoIP servers
But it won’t provision
Am suspecting a NAT problem
Nothing set for it in NAT and not sure what, if anything is needed.
Some help with this would appreciated as I built this a long time ago and have forgotten most of it
Thanks in advance

darkhobby5

@fin1000 said:

Running 2.9.0
Attempting to set up ht802v2 on one of my vlans
In and out to service ips and udp port set with alias
No reports in log of blocking to or from VoIP servers
But it won’t provision
Am suspecting a NAT problem
Nothing set for it in NAT and not sure what, if anything is needed.
Some help with this would appreciated as I built this a long time ago and have forgotten most of it
Thanks in advance

Had the same headache with an ATA on a vlan a while back, spent ages staring at NAT rules and it turned out to be something totally unrelated lol. Those Grandstream boxes are picky about provisioning imo.

chpalmer

I use a Grandstream HT802v2 on a Zoom number and have no issues without VLAN tagging. (it is on its own subnet and interface)

Any changes I make on the device after I factory reset it get wiped out from the actual TFTP config from Zoom.. other than my DHCP address. (Just something to keep in mind as you troubleshoot..)

I do have my VOIP interface on pfSense set for "Static Port" for all ports.. Its been a while since I set it up but those two facts remain constant.

darkhobby5

@fin1000 said in Help needed setting up HT803v2:

Running 2.9.0
Attempting to set up ht802v2 on one of my vlans
In and out to service ips and udp port set with alias
No reports in log of blocking to or from VoIP servers
But it won’t provision
Am suspecting a NAT problem
Nothing set for it in NAT and not sure what, if anything is needed.
Some help with this would appreciated as I built this a long time ago and have forgotten most of it
Thanks in advance

SIP stuff can be weirdly silent when the basics look open, especially if the ATA is sitting on a separate VLAN. The provisioning URL and DNS path can be the bit that trips it up, not just the UDP rules.

fin1000

@darkhobby5

It’s certainly acting very strangely - ended up having to get another ata as thought the first was bad as every time it was connected to the vlan with internet on it the thing changed its password but not to to one given by the VoIP supplier to use after provision. Which means you can’t look and see what’s going on on the ata cos you can’t get in and reset just clears it.
Insurrections from the VoIP supplier is just to open a bunch of ip addresses and port 5080 and udp
The second one I got set it’self to the VoIP provider s password but nothing had been added to any of the fields on it just changed the password (both of them had the MAC address and serial number sent to the provider for provision ) firewall logs show no issues but am guessing it won’t show a NAT issue - I built this system long time ago an have forgotten most of them suff!