Unsupported Outgoing calls on grandstream HT813 not working..

[scabst]

Good day.. hope some of you have some ideas how to make this work.

On my HT813 box, i do see the FXO register:



But on the 3cx console (under SIP trunks), is not register:



Any ideas?

 

[leejor]

Which port is not working...the FXO or FXS, or both?
Have you checked the Activity Log for any clues?
Is the device local?

 

[scabst]

I do see something weird... the ip 192.168.1.20 (not my lan)

23-12-2019 12:27:01:893 | 4 | [CM303003]: There are no available outbound lines on gateway gw1.xxxxxxxx.com at this time. First line: Lc:10001(@gw1.xxxxxxxx.com[<sip:[email protected]:5062/UDP>])

 

[leejor]

In the 3CX trunk settings (for this device), you specify the IP and the port of the FXO device. It might register with a correct IP but you must tell 3CX where to send outgoing trunk calls.

 

[scabst]

My 3CX is on the cloud and i have a SBC.. my FXO is on the same lan as the SBC. FXS works just fine.. FOX incoming calls, also good.

 

[leejor]

The FXO portion is not supported behind an SBC, or not local to the server.. It might work if it had a public IP, or you used VPN. that said, there are some posts on the forum of members getting some makes of FXO gateways to work. As I said earlier, the issue is going to be outgoing calls. 3CX wants an IP and port to send the calls to. If you can manage that, and the voice packets also get to the correct destination, then, in theory, it will work.
You may be able to get around this limitation by moving the 813 from behind the SBC, and using port forwarding on the remote router. Getting SIP signalling through, should be fairly straight forward, getting audio both directions may require some trial and error.

 

[scabst]

I setup the 3CX locally, my HT813 is on the same lan.. and still have the same issues. On the 3cx sip gateway option, you need to specify the 813 local IP and port (5062).. but on the 813 it self, you need to specify the SIP port. so if we follow logic, the port forwarding on my router should point to the 813..

 

[leejor]

If the 813 is on the same LAN, then in the 3CX trunk settings, you would set the local IP of the 813 plus the port assigned to the FXO part of the device...5062? In the 813, you specify the (outgoing) sip port of 3CX (probably defaults to 5060), and the local port of the FXO portion (I assume 5062, or 5061?).
If that is done, and i is still failing, then post the Activity Log of an outbound call towards the 813, X out part of the PSTN phone number, the IP's should be private LAN IP's so not a security risk.

You should not require any port forwarding on the local router if both 3CX and the 813 are on the same network.

 

[scabst]

I found the issue..!!! Need to setup the authentication on the 3cx sip trunk to inbound

 

[scabst]

Now my only issue is all incoming calls from Pstn thru FXO shows my voice gateway name as caller id.. so I can’t know who is calling

 

[leejor]

Now my only issue is all incoming calls from Pstn thru FXO shows my voice gateway name as caller id.. so I can’t know who is calling

This usually happens when there is no caller ID available. Check that the 813 is set for the correct type of caller ID for your area/region. If you use Bellcore type, be sure that the Gateway is waiting enough time for the caller Id to be collected (between first and second ring...3 seconds), before sending the call to 3CX. Also confirm that the line has the CID feature.