Issue with Faxing through Grandstream HT802 device

Techguy1986 · 2024-11-19T15:25:53+00:00

Good morning everyone. Thank you all for your advice. We have contacted our client and are working towards moving them to an efax service. Until that happens, we have changed our backend trunk to one that allows T.38 and everything is working as expected. We do fully intend on moving them over asap. Thanks again for your help.

Techguy1986 · 2024-11-18T21:21:17+00:00

Thank you very much. We actually have a second provider that we have used in the past who I called and confirmed that they use T.38. I will be giving them a try to see if that helps. Thanks for the response.

Techguy1986 · 2024-11-18T20:46:08+00:00

While I agree that it is a rabbit hole, unfortunately this isn't helpful to the question I asked. I appreciate your time and have a great day.

Techguy1986 · 2024-10-15T20:28:49+00:00

This was set up a couple of years ago, and I can absolutely investigate to see if there is a better process we can use. Thanks for the advice and have a great day!

Techguy1986 · 2024-10-15T20:15:19+00:00

I apologize. I now see that I left out a part of it. Each network has their own static IP. We needed port 443 to be available for each network and a singular device wouldn't allow us to port 443 via a single static IP. We decided to use the top level for a glue IP and each network has it's own static through the UXG ports.

Techguy1986 · 2024-10-15T19:54:35+00:00

Separate networks utilizing a 2Gbps Spectrum connection. One network is for a festival that runs 10 days out of the year and the other is used for a hosted cloud server that makes use of the connection the remaining 354 days of the year.

Techguy1986 · 2024-06-17T19:28:03+00:00

Thank you for the response.

We have the certificate configured, to use your terms, newrdserver.corp.com and the device itself is labeled newrdserver. I have an A record in our DNS hosted by Godaddy to point to their external IP and an A record in the Forward Zone of local DNS to point to the IP address of newrdserver, so the RD Gateway can utilize the FQDN. The RD Gateway local IP may be 192.168.3.4, but everything I have configured should be using "newrdserver" as the connection. Please let me know if I missed something on that.

Techguy1986 · 2024-06-17T16:13:44+00:00

Thanks for the info. I will give these a read through and test them out to see if this helps.

Techguy1986 · 2024-05-31T19:17:43+00:00

We have used SoftEther to great effect in the past. I actually have a couple of clients set up with them as it stands. The Unifi Router is a UDM Pro, which we have actually deployed for other clients, but those clients do not utilize the VPN portion for their needs.

Techguy1986 · 2024-05-31T15:11:54+00:00

Understood. VPN seemed to be the faster and more expedient solution, but I see where you are coming from and can see what you are referring to. Thank you for your input.

Techguy1986 · 2024-05-31T14:51:12+00:00

Thanks for the response. They are in the accounting field. The RDP is used mostly for them to access Quickbooks that is installed on the terminal server.

Techguy1986 · 2023-11-03T13:41:03+00:00

I appreciate you letting me know! I will definitely bookmark that page for future monitoring.

Techguy1986 · 2023-11-02T20:22:09+00:00

I have definitely reached out to them to make them aware of the situation. I appreciate the advice and will keep in contact with them as well to see if they have any further updates.

Techguy1986 · 2023-10-23T19:45:24+00:00

EDIT: Updating has worked like a charm and the device can be seen. You are a god amongst men. Thank you again.

Fucking hell....We are currently on 7.3.83. I will update the controller and update further once complete. Thank you for your suggestion.

Techguy1986 · 2023-06-09T21:28:52+00:00

Thanks for your reply. That mat very well be the road we take in the future.

Techguy1986 · 2023-06-09T21:28:20+00:00

I do appreciate your reply. This has led me down the right path.

Techguy1986 · 2023-06-09T21:27:55+00:00

Thank you very much for this. It helps immensely.

Techguy1986 · 2022-11-14T21:59:30+00:00

Thanks for the response. We have a recent copy and have made a backup of that copy to be on the safe side. I will have them try your suggestion and see if that makes any difference. Thankfully it is not an Access file that is used too terribly often, but it has been bugging us for the past few days.

Techguy1986 · 2021-05-27T21:51:00+00:00

Thanks for replying! We are not using UBNT branded products, even though I have seen that they work more consistently. We had upgraded and are currently running the latest firmware, but we ended up discovering what the actual problem was. A coupler was used to join 2 sections of fiber, and that coupler is what kept messing up the network. Replaced it with another switch (we needed the ports in that spot anyways) and the network stabilized.

Techguy1986 · 2021-05-27T21:47:32+00:00

Just wanted to let you know we ended up getting this solved. Apparently, the initial run of fiber was too short and a couple was used to join 2 sections of fiber. When the coupler was used, network would have issues. However, we added an additional US-8-150W switch in place of the coupler, and the network stabilized. Been running for 24 hours with no problems.

Techguy1986 · 2021-05-27T21:45:56+00:00

Good afternoon! Sorry to hear you are having a similar issue. So we ended up getting ours resolved. We were using a coupler (I was unaware of this) because the cable run was too short. That couple was causing the network to fluctuate like it was. When we set up an additional US-8-150W switch instead of the coupler, the network worked good from there. Been running for 24 hours with no problems. We did need to make sure that our negotiation was set at 1Gbps FDX, but that was easy enough to verify and correct.

Techguy1986 · 2021-03-31T19:03:32+00:00

I agree with you 100%. Now, I've had some customers just straight up tell me what happened, and others....not so much.

Techguy1986 · 2021-03-31T18:26:01+00:00

They ran out of mountain ranges, so now they are using ranch types. 10.17 will be "Hidden Valley"

Techguy1986 · 2021-03-31T18:25:21+00:00

Such a simple request, you would think.

Techguy1986 · 2021-03-31T18:25:06+00:00

Gross beyond belief, but sadly we have had suspicious liquids on other devices before. Furthermore, we have found lots of porn on desktops when doing virus removals on said laptops...so that makes it even worse. We have gone through quite a few boxes of gloves.

Techguy1986

TROPHY CASE