Solved 3CX Faxing not working with Grandstream HT801

Status
Not open for further replies.

ITguy2021

Free User
Joined
Oct 8, 2021
Messages
24
Reaction score
2
I posted a few days ago about not being able to get faxing to work with the Polycom OBi202 Google Voice device, and was suggested to try the Grandstream HT801 ATA device instead, however this is nothing new. We were using the HT801 before trying that device, and it wasn't working before and I cannot get it working now. I will try to explain the problem as simply as possible without losing the details.

Basically, there is no rhyme or reason to the way this thing behaves once it's configured. It even seems to behave differently depending on which ethernet drop I'm using and the VLAN I'm on.. But I could be wrong. When testing it, sometimes it seems to send/recieve faxes, and other times it does not. In the past, I've configured it as instructed, and was able to both send and receive faxes on all of my tests, but then after some time passes, it seems to stop working.. I've tested it by sending faxes to other fax machines in the office, and on some of my tests they go through right away, other times they do not and I get a "poor line quality" error on the report. My most recent test, the faxes send, but I cannot receive faxes.. On the receiving end, when sending a fax to the fax machine that the ATA is plugged into, it will just ring like it's receiving a phone call. If I move it to a different ethernet drop and a different fax machine in the office, suddenly it will receive faxes, but not send any.. There's no consistency to any of it. As I said, a few months back, I had it configured and working in my test environment with two different fax machines, but then you put the device in place where it's needed, some time passes, and then people report to me that it's not sending or receiving (or one or the other).

Here is what I'm doing to configure it...

In our 3CX web dashboard, under Advanced > Fax, I create a fax extension by clicking add, the fax authentication ID and Fax extension authentication password are automatically filled in, and then I give it a caller ID of one of our free DID numbers.

Under Advanced > FXS/DECT on the left pane, I click add FXS/DECT. I give it a name, set the provisioning method to Local LAN (in the office), there's a provisioining link to an .XML document (which I upload to the devices web page later), I put in the MAC address of the ATA, for select interface I set it to our 3CX server's IP address, device web page password is already filled in, and the fax transmision mode is set to "Fax in audio G711 (pass through)". The codecs that show up at the bottom are PCMU, PCMA, and G729A/B (these are already there). Under the extensions tab at the top, I select the fax extension I created in the previous step.

I then add an inbound rule.. I give it a name.. I give it the DID I assigned to the fax extension earlier. Route calls section.. Send fax to fax extension I created for both calls during and otuside office hours.

Outbound rules.. Give it a rule name. Apply this rule to these calls. Calls from extension (that I created). Make outbound calls on.. Set route to the ISP name. Strip Digits 0. Prepend box blank, Outbound caller ID is the DID number I assigned to the fax I created.

Then, in a web browser, I go to the IP address for the devices configruation page. I log in as admin. I change nothing under the Basic Settings tab. I go to the Advanced Settings tab.. I set 3CX auto provision to No (to avoid my settings being overwritten). Automatic upgrade to No. Always check for new firmware to "Always skip Firmware Check". I hit update. Then apply and wait for it to reboot.

I then log back into it and go to the FXS Port tab at the top of the page. I set the Primary SIP Server and Outbound Proxy IP address fields to our 3CX server's IP address. I set SIP user ID to the fax extension number I created. Authentication ID I set to the Auth ID listed under the Fax extension I created. Same deal with the Authenticate Password field. I then click update, apply, and save my changes.

Then, I go to the 3CX dashboard and to Advanced > FXS/DECT and click on the grandstream device I added earlier. I highlight the provisioning link, right click, and hit save "save link as" and save it as an .XML file. I go back to the devices configruation page, sign in as admin, go to the advanced settings tab, scroll ALL the way to the bottom, where it says "upload configuration" and click that, then I select the .XML file that I just downloaded from th 3CX dashboard and upload it. It takes some time, applies the changes, and reboots.

Then I test it by making phonecalls to and from an analog phone plugged into port 1 on the ATA device. I'm able to make phone calls within the office. I'm able to call my cell phone from the analog phone, and I'm able to make calls to the analog phone from my cell phone...


I then take the ATA device, plug it into a fax machine instead of an analog phone, and I then get the faxing behavior I described above..

What am I missing? what am I doing wrong here?
 
Then, in a web browser, I go to the IP address for the devices configruation page. I log in as admin. I change nothing under the Basic Settings tab. I go to the Advanced Settings tab.. I set 3CX auto provision to No (to avoid my settings being overwritten). Automatic upgrade to No. Always check for new firmware to "Always skip Firmware Check". I hit update. Then apply and wait for it to reboot.

I then log back into it and go to the FXS Port tab at the top of the page. I set the Primary SIP Server and Outbound Proxy IP address fields to our 3CX server's IP address. I set SIP user ID to the fax extension number I created. Authentication ID I set to the Auth ID listed under the Fax extension I created. Same deal with the Authenticate Password field. I then click update, apply, and save my changes.
Why are you doing this part???

In the next paragraph you say you download the XML and load it into the device. That's all you need to do.
Factory Reset the device and skip this what I quoted, only do what you say in the following paragraph, i.e. load the XML file.

Also, consider upgrading it to the latest available firmware from the Grandstream website.
 
Because I was doing it before months ago with just uploading the .XML document like you suggest, and it was working during testing, but then after some time sitting in someone's office, they would go to use it and it wouldn't work.. So, I started adding in that infromation manually recently because I figured that something to do with auto provisioning was messing up the configuration..
 
Because I was doing it before months ago with just uploading the .XML document like you suggest, and it was working during testing, but then after some time sitting in someone's office, they would go to use it and it wouldn't work.. So, I started adding in that infromation manually recently because I figured that something to do with auto provisioning was messing up the configuration..
While I can't tell you why it stopped working after some time, I can certainly tell you that it's not required.
 
It even seems to behave differently depending on which ethernet drop I'm using and the VLAN I'm on.
This would lead me to believe that it may have something to do with the configuration of your network. Have you made use of something like Wireshark, to compare a working and non-working fax? See if there is a patten of failure?
 
Which SIP Trunk are you using?

What you are describing leads me to think you are experiencing the standard pain in doing Fax over VOIP. Fax via G711 will not work as well as Fax via T.38, but your SIP provider needs to support it.

If you plug a regular telephone into the ATA and make and receive calls with it (still programmed for the fax extension number) do you have any issues?
 
I have two HT801 ATA's setup both exactly the same, just as the above poster instructed me to do, by not manually altering the config page at all, and only uploading the .XML configuration that I got from 3CX, and both fax machines connected to both ATA's will not send faxes, they only receive faxes. They receive faxes from what seems to be any fax machine, however they can only send to one fax machine in the building, which is connected to an RJ11 phone line. They will not send to any fax machine that is using ethernet.. I get an error report saying the line is busy or poor line condition every time.
 
Which SIP Trunk are you using?

What you are describing leads me to think you are experiencing the standard pain in doing Fax over VOIP. Fax via G711 will not work as well as Fax via T.38, but your SIP provider needs to support it.

If you plug a regular telephone into the ATA and make and receive calls with it (still programmed for the fax extension number) do you have any issues?
I'm actually not sure off the top of my head as I'm no expert with this sort of thing. If you instruct me on where in 3CX I can find this, then I can tell you.. But, yes, If I connect an analog phone to the ATA's, I can make calls to my cell phone and I can call the analog phone from my cell phone with no issue.. The issue happens when I plug the phone line into a fax machine and try to send faxes from it. They do not go through. I get busy signals or poor line condition error reports. They do, however, receive faxes..
 
So it doesn't sound like an ATA issue.

What's listed in the SIP Trunks page?
 
There's three entries.. I wouldn't really feel comvortable taking a screenshot of it and putting it on the internet. One is our fiber line provider with the main office number.. The other entries say FlowRoute with sip.flowroute.com (light is red next to it other two are green lights). The third one says web meeting bridge. That's it.
 
Do your fax machines have an option to optimize for VoIP? Some do, and amongst other things, can set the modem to use a lower (more reliable) speed.
 
There's three entries.. I wouldn't really feel comvortable taking a screenshot of it and putting it on the internet. One is our fiber line provider with the main office number.. The other entries say FlowRoute with sip.flowroute.com (light is red next to it other two are green lights). The third one says web meeting bridge. That's it.
Open each one and look at the DID tab. Find the one with your fax number.

If that number is on the flowroute account (doubtful if flowroute one is red - it's likely unused) then in the fax settings check the box for t.38 and reprovision the ATA.
If it's on your fiber line... ask your fiber provider if they support t.38. If so, same as above. If not, ask your fiber provider if they support fax over IP in any way and how.
 
  • Like
Reactions: Evolute IT
Open each one and look at the DID tab. Find the one with your fax number.

If that number is on the flowroute account (doubtful if flowroute one is red - it's likely unused) then in the fax settings check the box for t.38 and reprovision the ATA.
If it's on your fiber line... ask your fiber provider if they support t.38. If so, same as above. If not, ask your fiber provider if they support fax over IP in any way and how.
I did exactly what you told me to do. Flowroute is an inactive service. Our fiber provider is Salsgiver (small local provider). Our faxes are going out over this provider. I've provisioned both of these ATA's to work with both T.38 and G711 Passthrough exactly as it is described here...

https://www.3cx.com/voip-gateways/grandstream-ht-fxs/#h.oxzb48jgf61h

And I get the same results every time.. Provisioned both ways.

If I plug an analog phone into the devices, I can call it from an outside line. If I call from it to an outside line (like my cell phone), I get a busy signal.

Neither device will send a fax to the other..

Both devices will receive faxes from other fax machines in the office, but will not send to any fax machines in the offixce except one, which is a standalone fax machine plugged into just a phone line.
 
Last edited:
If I call from it to an outside line (like my cell phone), I get a busy signal.
You might troubleshoot this by looking a the 3CX Activity, log after a call attempt,t to see why you are getting a busy signal. Is the call even getting that far?. It may be something to do with your outbound rules, or a dialplan on the ATA,
 
You might troubleshoot this by looking a the 3CX Activity, log after a call attempt,t to see why you are getting a busy signal. Is the call even getting that far?. It may be something to do with your outbound rules, or a dialplan on the ATA,
The ATA's work perfectly with faxing and calling within the office as long as you're using the extensions.. It's when you use the full number (for sending) that it fails.. All except for one fax machine.
 
You will want to figure out what is causing a busy signal...the ATA, 3CX, your provider, the far end.
 
I with leejor here. It's unlikely a fax issue if the problem occurs with a regular telephone as well connected to the ATA

1) set logs to verbose
2) make call that fails
3) post logs (you can redact private info) (or via PM would be OK)
4) Change logging back
 
My provider is saying there may be something wrong with my outbound rules.. What exactlly should the outbound rules look like for this? Just in case I'm missing some detail somewhere.
 
If outbound calls are working from other phones, and you are dialing the same number, from the fax line, then there may be some extension restrictions, or rules set just for the fax extension, which cause the calls to fail.

Place a call from a "normal" extension, check the 3CX Activity log, for that call, make note of the outbound route name that the call uses. Call the same number from the fax extension, check the log, is the route name the same? If not, then I suspect an outbound rule has been created and placed above the default rule, that applies only to the fax extension. Rules are read from top to bottom, with the first match being used.
 
I contacted my ISP and found out that my faxes are failing because they are being sent out using the OPUS codec instead of G711. Why is this? I'm provisioning these ATA's using the .xml link provided in the 3CX dashboard. Inbound faxes are coming in via PCMU (G711) so why are outbound faxes trying to go out using OPUS?
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet