Grandstream ATA and 3CX

[macery]

I'm having issues with no audio. Both inbound and outbound calls.

3CX log:
No RTP packets were received:remoteAddr=192.168.1.203:5036,extAddr=<none>,localAddr=xxx.xxx.xxx.xxx:9648

3CX v16.0.611 in cloud (OVH OpenStack)
4x Granstream ATA HT802 with two extensions (7 extensions, one unused)

ATA devices are behind NAT router (no CGN NAT).
SIP and RTP ports forwareded, SIP ALG disabled.
Every ATA has unique SIP port, eg. 506x and RTP ports, eg. 5036 - 5043
ATAs configured as direct STUN (NAT Traversal), I've tried with keep-alive and with NAT traversal disabled.

3CX firewall green.

SIP extensions correctly registered.

What else can I do/try?

 

[AWS2P]

Why not starting here to let us a chance to know near same as you
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[macery]

I thought that I wrote all the relevant informations. Nevertheless, as requested:

• 3CX Version: Standard Annual 16.0.611
• Server OS: Debian 9
• Is the 3CX Server Hosted and where?: OVH
• IP Phone Make/Model/Firmware: Grandstream HT802, firmware v1.0.17.5
• Provisioning Method: Local / VPN / STUN / SBC: STUN
• Trunk Provider or Gateway Make/Model: Generic SIP Trunk
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Maybe it is worth to mention that every extension has enabled: PBX deliveres audio.
And although there is Generic SIP provider, I have to say that I have few OVH hosted PBXs configured same way with the same SIP provider and it works well. The only difference is that I use other phones on the other instances.

 

[JohnS_3CX]

Hi macery,

The device must be local to 3CX, in the same subnet and/or locally routed subnet (including site to site VPN)

Currently it is used in a non-supported scenario. What it probably happening is that it states its local IP in the SIP messages and the audio never reaches it.

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

 

[leejor]

Check the STUN settings in the ATA, Device will have to show (in the 3CX Activity Log) as registering with the Public IP (of the remote router),and device local port, or 3CX will not be able to send to the device.

 

[macery]

I think I've resolved this issue.

ATAs NAT Traversal set to UPnP and router enabled with UPnP. SIP and RTP ports mapped as configured in ATA settings.

Now I can see ATAs registering with the Public IP and no "No RTP packets were received..." entries in log.

All STUN settings removed.