Dinstar Trunk registering against 3CX server doesn't work

[gbaya]

Hello,
I have an AWS hosted 3CX. Now I'm trying to install a Dinstar UC100 behind a Nat to add a GSM and a FXO lines to the PBX.

Previously I had installed a SP3102 and worked fine FXS and FXO (until It died).

Now with Dinstar UC100 I cannot register the gateway in the 3CX. IP address of UC100 and forwarding ports in the router are the same than SP3102,

Any ideas or a guide to solve the problem?

Best Regards
Gabriel.

 

[cobaltit]

So neither the 3102 or the Dinstar are supported and neither are gateways connecting to a cloud instance unless using a VPN. That being said, are you using the exact same information from the SPA3102 in the Dinstar to register? Are you seeing anything in the activity long showing registration attempts?

 

[gbaya]

So neither the 3102 or the Dinstar are supported and neither are gateways connecting to a cloud instance unless using a VPN. That being said, are you using the exact same information from the SPA3102 in the Dinstar to register? Are you seeing anything in the activity long showing registration attempts?

At the best of my knowledge, parameters are the same, but I don't see any activity trying registration.
I used a Stun Server to see the public IP address and an Output proxy server (the same domain name).


Regards.
Gabriel.