Dinstar SIP Trunk can't register to local SIP server

[tylertucker1]

I'm trying to use a Dinstar UC2000 gateway as a trunk for my 3CX SIP server which I'm running as a virtual machine. The gateway is directly connected to my computer via ethernet. I'm able to ping the gateway from the VM but I cannot ping the VM from the gateway. Also, my firewall checker for the SIP server fails and prints: testing port 5060... Mapping does not match 5060. Mapping is 58651.

Network information:

Dinstar Gateway
IP: 192.168.11.1
Subnet Mask: 255.255.0.0

Host Computer
Ethernet IP: 192.168.11.15
Ethernet Subnet: 255.255.255.0
vmnet8 IP: 192.168.142.1
vmnet8 Subnet: 255.255.255.0

3CX VM
IP: 192.168.142.131
Subnet: 255.255.255.0

I'm thinking this is a NAT issue as it appears the gateway cannot find a path to the IP of the SIP server (I see unanswered ARP requests for the 3CX server's IP from the gateway on Wireshark). I've followed the Dinstar guide on how to use the UC2000 as a trunk for 3CX, but I'm still running into this issue. Does anyone have any suggestions?

 

[ChrisC_3CX]

Since this is not a 3CX Supported Gateway we cannot really provide specific information on how to set it up, however, from the sounds of it you might have some network configuration issues that you'll need to sort out first as local communication from and to the 3CX PBX must be possible so you'd definitely need to make sure that this is possible.

In regards to the Gateway configuration in 3CX do bear in mind that, creating a SIP Trunk means that the 3CX PBX will attempt to register by contacting the registrar specified, as opposed to creating a Gateway entry in which case the 3CX PBX will wait for the Gateway to register. I'm mentioning this just so that you know what to expect in case you investigate further by reviewing traffic on either end.

 

[leejor]

Given the IP's you are using, I'm not certain, but, should not all of your subnets be 255.255.0.0?

Are you using a router that re-maps ports?