In/Out Office Identification

[Brett Garfitt]

I just wanted to clarify how the Windows Client identifies if it is In the office, or Out of the office.

Is this purely identified via the subnet?

Our PBX is on a 10.0.10.x/24 IP while we have two remote offices 10.0.30.x/24 and 10.0.40.x/22 which connect back to the PBX over a VPN.

I am assuming that they would be deemed as being on separate subnets, therefore Out of office? I would expect the system to use the Out of office FQDN instead of the IP address, in that case, am I correct?

Would the remote clients use a tunnel to connect over the VPN?

 

[Saqqara]

Maybe wrong

If the client can connect to 'in office settings', it will use this setting else out of office settings

As you have site to site vpn, it should be using in office settings - note : if the in office is using FQDN and this can not be resolved at the remote site it will use 'out of office

 

[VoIPTools]

3CX evaluates whether a phone is "local" or "remote" based on the IP address (subnet). If your phone is configured with (or coming from) a public IP address, then it will be considered a remote phone. If it is a private address then it will be treated as a local phone. Therefore, just because your phone may be on a different subnet than your 3CX server, it is not necessarily treated as a remote phone.

If for some reason your are using a "public" subnet as an internal address (highly discouraged), you can overwrite this behavior by setting your "local" subnets at: 3CX Management Console --> Settings --> Parameters --> Local Subnets

Just an FYI: Private subnets are: 10.0.0.0 to 10.255.255.255. 172.16.0.0 to 172.31.255.255. 192.168.0.0 to192.168.255.255. Everything else is a publicly routable address and should not be used in your internal network.

 

[YiannisH_3CX]

If the client is using a local IP as the In office routing then the client will first try the local IP for registering. If there is no reply in a timely manner then it will try to register using the out of office routing. Local IPs are consider the ones specified in RFC1918.