You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Sipdroid connects ok through the vpn client, but when the vpn drops because
the phone moves out of WIFI for even a short time when the VPN comes back up
Sipdroid will not register again.
What steps will reproduce the problem?
1.Connect Sipdroid through VPN (NCP VPN Client Premium)
2.Disconnect VPN by ether turning it off or loosing wifi signal.
3.when wifi signal is good again the vpn will reconnect but sipdroid will not.
What is the expected output? What do you see instead?
When the net work is down sipdroid says "no network available,
but when the network is returned sipdroid notifications registering but can not
register.
(Note there is no change of ip-address from the vpn or wifi involved in this)
What version of the product are you using? On what device/operating system?
Sipdroid 3.5 and 2.7 have not tried any other.
Samsung tab-s sm-t800 android 4.4.2
NCP vpn Client Premium V2.33
Which SIP server are you using? What happens with PBXes?
LAN and VPN connected AXON IPBX
The PBX does not receive any registration request.
Which type of network are you using?
LAN and VPN
Please provide any additional information below.
If i force stop and reopen sipdroid or make a change to the setting it
re-registers ok.
I think there need to be a user adjustable timer to check for network
changes or a "use this gateway setting"
I think sipdroid moves to the wifi network before the vpn comes up and does not
change to the vpn tunnel once it is up, and i gess it has no reason to because
it does not know the IPBX is at the end of the tunnel.
Kind Regards
David
Original issue reported on code.google.com by da...@theranch.co.nz on 3 Nov 2014 at 7:43
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
da...@theranch.co.nz
on 3 Nov 2014 at 7:43The text was updated successfully, but these errors were encountered: