Phone showing up as external IP

[RuntyCardinal]

Good afternoon,

Recently my clients have ran into an issue where the phones show up as the router IP instead of the 192.168.xxx.xx. The only thing I have found to resolve the issue is re-provisioning the phones from Direct SIP to local lan. I'm wondering what could be causing these issues, and how can I resolve them without switching all clients to local lan. Some of our systems are cloud based and not hosted in the same building as the 3cx users.

 

[cobaltit]

So you've given next to zero information on this. Let's focus on this one particular setup and please provide details as far as where 3CX is located, version, phone models, and how they are provisioned.

 

[leejor]

By "router IP", do you mean the public IP of the router? If so, then that is normal if the sets are using STUN. The port numbers of the sets will then each be different (unique on the LAN). That is how 3CX identifies them as it cannot access the private IPs directly, it relies on the router to forward, based on the port number.

 

[JohnS_3CX]

Hi Runty,

From what I understand the server is remote to the phones, and they reach it via STUN provisioning.

The phones will appear in your management console with their Public IP, the same one the router uses.

 

[RuntyCardinal]

I'm running V15.5 with 4 yealink t42s' firmware 66.83.0.55. They are provisioned with Direct Sip (STUN Remote). Local SIP port 5060, local RTP Audio ports 14000-14019. The server is a virtual machine hosted in a data center outside of the clients location.

By "router IP" I mean the public IP of the clients site. So all phones are showing up with their public IP instead of their internal IP. For instance on the photo attached, the phones should all be in the 192.168.187.x range, however they are showing up as 68.101.x.x instead. The phones are retaining their IP address, but are falsely reporting it back to the 3cx admin console.

This issue just showed up this past week or so.

 

[RuntyCardinal]

Hi Runty,

From what I understand the server is remote to the phones, and they reach it via STUN provisioning.

The phones will appear in your management console with their Public IP, the same one the router uses.

Correct

 

[Saqqara]

As you are using stun, each phone needs different SIP and RTP ports and you need to configure portforwarding on the router protecting the phones

More info here - https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296

 

[RuntyCardinal]

As you are using stun, each phone needs different SIP and RTP ports and you need to configure portforwarding on the router protecting the phones

More info here - https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296

Thank you, that helps out a lot. We'll try this out.

Any idea's on why this would have just started to happen? We have clients that have used the same setup for a year with no issues until a few weeks ago.

 

[JohnS_3CX]

Hi Runty

What issues do you actually have with the phones though?

The fact that they show the public IP is not considered an issue, it's actually expected behavior under STUN.

Is there also a VPN between the PBX datacenter VM and the phones site?