Direct Sip responding to internal 3CX ip

[Sebastião Figueiredo]

Hello, I have a doorphone connected to 3CX via Direct Sip, I can make calls using it but can't receive.
I did a packet tracer on the doorphone and saw that it's responding the invite to the internal 3CX ip instead of the external.
Is there a parameter to change on 3CX?

 

[leejor]

Why do you not manually program the device to register with 3CX, as an extension? The registration process is what "tells" 3CX how to reach the device, if it is available.

 

[Sebastião Figueiredo]

Why do you not manually program the device to register with 3CX, as an extension? The registration process is what "tells" 3CX how to reach the device, if it is available.

That's how it is, the doorphone is registered directly to 3cx using it's external ip as server address, I may have expressed myself wrong sorry

 

[leejor]

So, the doorphone is use STUN, I assume, and is behind a router. The registration , in 3CX, shows the public IP of the router that the doorphone is behind. and it's port. Is that correct? If so, then that is how it should be. the remote router may have to be setup to forward ports to the local IP of the doorphone.

If the doorphone is registering using it's local IP, then STUN is not setup correctly on the device.

 

[Sebastião Figueiredo]

It's not using STUN as it's not a supported doorphone, after some research I think that's the problem, and apparently the only solution is using a SBC.

 

[leejor]

If it does not have STUN available as a feature, and is therefore unable to discover it's public IP, then it will continue to register with it's local IP, which is not going to work. Unfortunately some devices are designed to be used only on the same LAN as the server. Is the need to call the doorphone related to programming?. Normally, calling, on those sorts of devices is only outbound.

I suspect using an SBC, or VPN, if possible, are going to be your options.