Configure Grandstream HT812 using SBC manual configuration

[byfaith]

Hello

I have 3CX hosted on the cloud, i will like to setup my analog line to work with 3CX on the cloud, I can't get the manual configuration right,

I will appreciate if someone can assist me with the right step so I can get it right, we currently working from home, and our clients can't reach us as the line is not working.

Thank you for your support

 

[AWS2P]

ATA's can't work from cloud PBX, need to be on same Lan or you need a VPN

 

[byfaith]

Currently do not have access to VPN, reason why we setup SBC, phones are provisioning fine using SBC, left to get analog ATA Gateway line to work over SBC, if there is any guide to achieve this manually, i will appreciate the steps so I can get it work over SBC.

Thank You

 

[leejor]

Unless you are trying to use it for a fax machine, there is no reason you should not be able to manually configure it, to use with a hosted 3CX installation. If you just have the one SIP device, at the remote location then using STUN should suffice, and local port forwarding should not be necessary. If you want to use behind an SBC, then use the local IP of the SBC, as the server, and no STUN.

https://www.3cx.com/community/threads/how-to-provision-unsupported-grandstream-devices-to-3cx.56991/

 

[byfaith]

We are not willing to use it as Fax machine. We will like to receive and make call from the gateway using SBC or any way to connect it to the 3cx on the cloud and have it working.

 

[leejor]

Yes, As I said, you will have to manually configure it. There are a number of posts about doing just that with various Grandstream devices, on the forum, (use Google),and the menus of each, are very similar. If it is behind an SBC, then the Server address will be the local SBC IP.

 

[byfaith]

I have tested all method, edited the xml file and put SBC address there, uploaded firmware to the HT812, but can't get it right, so a link to a detailed guide and steps will be much appreciated. Thank You

 

[leejor]

I'm not aware of a guide on this site, for manually provisioning the HT812. However someone else may have programmed one recently, for use behind an SBC, and can provider more information. The SBC address may have to go in , in multiple locations.

You can post the SIP configuration page of the ATA, there may be something that is obviously incorrect. Does the 3CX Activity Log, show any signs of it attempting to register?

Similar...
https://www.3cx.com/community/threads/grandstream-ht801-setup.67103/

 

[byfaith]

I registered the HT812 in Sip trunk as Generic Gateway, then register and extensiom with it, created outbound rule and inbound rule, but when trying to make call with it, it retuns internal error

SIP Server/Call Manager ID: 12294
Call or Registration to 9XXXXXXXX@(Ln.10001@Grandstream Gateway HT812) has failed. 127.0.0.1 replied: 503 No DNS results; warning: No other DNS entries to try (0,0); from IP:127.0.0.1:5080

When i check phone menu, i see that the H812 device is listed there but with IP 127.0.0.1, I will appreciate help to solve this issue I don't mind over remote session, I seriously need to solve this issue as is impacting productivity this time of lock-down

Thank you for your support

Attached the screenshot of the phone menu

 

[leejor]

The HT812 is not a trunk, and as such, will not use inbound or outbound rules directly. The extension number, when making calls will use the rules, but they will be associated with the trunk group being used at the time. It is an FXS device (connects to an analogue telephone set), and would be provisioned as an extension.

 

[byfaith]

Can you give me the full setup guide to achieve this and make it work. I have been on this for days without being able to get it work

 

[leejor]

I have not seen a "full set up guide" for that ATA, for use with 3CX, on this site. There are other posts dealing with similar ATAs, Grandsteams included, if you do some searching. There may also be information on other sites.
The device is an ATA, and to provision in an unsupported mode, you should have, at least a general idea how SIP works, as will will probably be doing some "trial and error' in getting it to work.

The basics will be...
Create an extension in 3CX. Will need the extension number, password, Authentication ID, and Server (proxy) information, to start with. If it is behind an SBC, that that will be the server, and perhaps the proxy.