Unsupported Grandstream HT813 FXO issues

[morro]

Im lost. Got a HT813 fxo cant get it to work. after 2 rings 3cx hangs up, cant call out. Its green on the sip trunk, got the outbound rules correct, apparently GS ht813 has a port issue and gotta use port 5062 instead of 5060 so i did that, inbound rules are correct.. you guys see anything?

 

[eddv123]

Hi morro,

These devices do not exist on the supported list unfortunately: https://www.3cx.com/voip-gateways/

First as always check the firmware version you are running on the device (1.0.1.2 is the latest available on the Grandstream site).

Its green on the sip trunk

Just to confirm have you have set this up as a generic FXO device correct ? and you simply mean in the SIP Trunks screen where the Gateway section lives ?

Can you also confirm that the line(s) themselves do not have any services on them (such as BT featureline - PBX like features sent from the exchange or Recare) as these would defiantly cause problems for you. - if you don't know, check.

It would also be useful if all the above checks out to do some logging to diagnose where the issue lies (either with the device or on 3CX), so get the Verbose logging from 3CX (binary log viewer is best):

https://www.3cx.com/docs/3cx-log-viewer/
https://www.3cx.com/docs/collecting-logs-for-3cx-support/

Also on the Granstream you could also run the syslog viewer on it, and perhaps send the results to Wireshark filtering just "syslog" packets.

My advise as always however is opt for Patton Gateways, they are both supported and have fantastic in-built logging functionality. Just a note

 

[morro]

Hi morro,

These devices do not exist on the supported list unfortunately: https://www.3cx.com/voip-gateways/

++++++ yes i know but the grandstream ht813 was $89, Patton $300, I have a Grandstream gvw4104 on another system it works great.

First as always check the firmware version you are running on the device (1.0.1.2 is the latest available on the Grandstream site).

++++++ yes of course its the latest.

Just to confirm have you have set this up as a generic FXO device correct ? and you simply mean in the SIP Trunks screen where the Gateway section lives ?

++++ Had them it Grandstream FXO, changed to Generic FXO same results.

Can you also confirm that the line(s) themselves do not have any services on them (such as BT featureline - PBX like features sent from the exchange or Recare) as these would defiantly cause problems for you. - if you don't know, check.

++++ Goes direct to cable modem, nothing else


It would also be useful if all the above checks out to do some logging to diagnose where the issue lies (either with the device or on 3CX), so get the Verbose logging from 3CX (binary log viewer is best):

++++++ok

https://www.3cx.com/docs/3cx-log-viewer/
https://www.3cx.com/docs/collecting-logs-for-3cx-support/

Also on the Granstream you could also run the syslog viewer on it, and perhaps send the results to Wireshark filtering just "syslog" packets.

+++++ok

My advise as always however is opt for Patton Gateways, they are both supported and have fantastic in-built logging functionality. Just a note

++++yes but i was looking for a 1 pstn line, didnt want to spend $300 its just not worth the money to use a pstn line. hence the cheap grandstream that doesnt work

Changed ports to 5062 and 5004. Now i get inbound calls just cant dial out yet. still working on it.

 

[morro]

got this error,

SIP Server/Call Manager ID: 12294
Call or Registration to 5050000@(Ln.10001@Generic Gateway Device) has failed. 192.168.0.51 replied: 403 Forbidden; from IP:192.168.0.51:5062

 

[morro]

absolute insane.

Stage Method (1/2): 1
(Default 2 - 2 stage dialing)

default is 2 and when changed to 1. It all works fine...... who ever wrote the code on this is an idiot hours wasted to find this problem.

 

[eddv123]

Glad to hear you have got this sorted, I cannot see how the fix has any relation to the registration error you had but OK good to know.

Also get your point on the Grandstream to Patton pricing - this is a major benefit to Grandstream and probably a major reason that they were taken back on by 3CX.