Session expired when routing changes from internal to external IP-address

[PhilK]

Hello,

when my colleagues switch their devices (notebooks, etc.) on from home, the 3cx webclient autostarts and connects with the public IP to our 3cx.
When they start their VPN, the ip-address and the routing to our 3cx automatically changes to the internal/private IP of the system.
If they forget to refresh the webclient, they always have a problem with the first incoming call, because the webclient "session expired".
Is there any way to implement a automatically refresh to the 3cx server if the routing ip-address changes?
Other applications don't have any problems with a changing ip-address with/without VPN-connection.

Please check this.

 

[JohnS_3CX]

Hi Phil,

For users that have a VPN, they must close their tab and reopen it after connecting (or reconnecting).

If the connection is broken due to a route change ti will not reconnect automatically.

 

[PhilK]

Hi Phil,

For users that have a VPN, they must close their tab and reopen it after connecting (or reconnecting).

If the connection is broken due to a route change ti will not reconnect automatically.

Is this really the only possible answer? a little disappointing.

 

[JohnS_3CX]

Sorry Phil, this is the only possible solution at the moment. A route change means the old route is now stale and the connection was broken.

Reloading will force authentication to happen again. Please note that the browser will also need to do some work in the background to re-discover the route to the internet, and sometimes this means closing and reopening the browser. From VPN to VPN you may notice differences (Depending on how they implement their interface on the PC side)

 

[PhilK]

Alright, thank you.