Grandstream HT801 setup

Status
Not open for further replies.

Toddalex2000

Premier Customer
Joined
Aug 26, 2017
Messages
44
Reaction score
2
finally got it working. I mirrored another one we had which requires additional info on the advanced settings tab for provisioning URL;s and the FXS Port tab for SIP server info and auth ID. Not sure why the instructions don't go into detail more with this. I mean how in the heck would one figure this out!
 
Note: for a care free FAX deployment setup either locally to the PBX or via a VPN to the hosted cloud.

FAX can be very sensitive to conversions and delay and thus the SBC and STUN methods are not supported. If your provider does not support T.38 FAX (which they should) then you need to use G711 pass-through to carry the FAX signals.
 
Note: for a care free FAX deployment setup either locally to the PBX or via a VPN to the hosted cloud.

FAX can be very sensitive to conversions and delay and thus the SBC and STUN methods are not supported. If your provider does not support T.38 FAX (which they should) then you need to use G711 pass-through to carry the FAX signals.

If we are not using ATAs for fax but as FXS gateways for analog phones, do you think the SBC would work correctly?
 
  • Like
Reactions: Evolute IT
Ive setup FXS gateways and ATA's for analogy phones via the SBC before - you point the registrar of the device to the SBC address (if it does not support proxy mode) and it works fine.

In the case of analogue handsetsI have never experienced that many issues.

FAX I have got working via STUN even (using a Grandstream HT701 but it was really fiddly and took a lot of changes (G711 Pass-through and speed transmission changes). It was for a test, but if deploying in the real world I would not waste your time.

You want to stay supported if you can also.
 
  • Like
Reactions: Evolute IT
Ive setup FXS gateways and ATA's for analogy phones via the SBC before - you point the registrar of the device to the SBC address (if it does not support proxy mode) and it works fine.

In the case of analogue handsetsI have never experienced that many issues.

FAX I have got working via STUN even (using a Grandstream HT701 but it was really fiddly and took a lot of changes (G711 Pass-through and speed transmission changes). It was for a test, but if deploying in the real world I would not waste your time.

You want to stay supported if you can also.

It's more because we have a VPN only for the ATA. All of our phones support SBC. I could drop my VPN if it's not needed.

@JohnS_3CX While the HT80x isn't "officially" supported in SBC mode, would it work for regular calls? There are no fax going through it.
 
@JohnS_3CX, yes i did. its the provisioning method we use to configure that differed.
I had to use the SIP ID and auth along with the provisioning link to our on prem 3cx.
We provision our phones using the manual provisioning method.
 
I could drop my VPN if it's not needed.

I am still a big advocate of VPN over other remote connection types, although you are right despite the "supported/unsupported" nature of remote ATA's it does seem a bit over-kill to have a VPN just for this.

This is the only time you will hear me say this (and that is only because I have tested it myself with the HT701) but for a single extension ATA you could just direct STUN/SIP it. For a single extension port forwarding issues should not be an issue, you just have to consider the lack of security.
 
It's more because we have a VPN only for the ATA. All of our phones support SBC. I could drop my VPN if it's not needed.

@JohnS_3CX While the HT80x isn't "officially" supported in SBC mode, would it work for regular calls? There are no fax going through it.
What can potentially work, and what is officially supported are two separate things. I will just leave it at that ;)
 
Status
Not open for further replies.

Forum statistics

Threads
111,933
Messages
589,809
Members
164,807
Latest member
Smax