Remote office - 3CX making route to remote LAN, not WAN.

[eihli]

At a remote office, we have 3 linksys phones, a Cyberdata ceiling speaker, and a Cyberdata intercom.

Each device has a static IP and a static SIP port.

The phones and the intercom work fine.

The ceiling speaker does not work.

When we try to call the ceiling speaker, 3CX tries to route the call to the LAN ip of the device rather than the WAN ip. For all other devices, 3CX routes to the WAN ip of the remote subnet.

Ex - call to intercom:

09:49:46.315  [CM503004]: Call(3774): Route 1: Ext:Ext.199@[Dev:sip:199@<remoteWANIP>:5063;line=b0e481044ef2646,Dev:sip:[email protected]:5063;line=b0e481044ef2646,Dev:sip:[email protected]:5060;line=ab2bb6e57760f3d]

call to ceiling speaker:

09:35:04.541  [CM503004]: Call(3759): Route 1: Ext:Ext.210@[Dev:sip:[email protected]:5066]

I have spoken with Cyberdata tech support and they have assured me that this method would work for the ceiling speaker. I have triple-checked all settings.

Any idea what would cause this?

Thanks,
Eric Ihli

 

[mfm]

Hi,

From what I can understand it appears that it might be registering with a internal ip, this could be because of stun issues, or for some reason it not being able to detect its IP.

Can you unplug the device, replugh it and paste the log of the registration.

 

[eihli]

11:24:34.683 [CM504001]: Ext.210: new contact is registered. Contact(s): [sip:[email protected]:5066/210]