In my house, due to bad Wifi signal through the rooms, I have wired routers physically connected to a main router through a switch. Only the main router is a DHCP server and all the routers are in the same network, 192.168.1.0/24.
My phone running Voxwav is on the same LAN as the PC running VC, which means both are using IPs on the same LAN 192.168.1.0/24, although they are in different routers. Actual Voxwav IP is 192.168.1.111 and the VC IP is 192.168.1.105 (it is a reserved IP that has been set on the DHCP).
When both Voxwav and VC devices are connected via wifi to the same router on my LAN, I see no issues, everything works perfectly.
When the PC running VC is connected via wifi to one router and Android phone is connected to another router, Voxwav reports the TCP error below:
Could not establish connection to 192.168.1.105:33339
failed to connect to
/192.168.1.105 (port 33339) after 3000ms: isConnected failed: EHOSTUNREACH (No route to host)
The PC does not show any sign of a connection on this test.
Then, I tested using a telnet app on the phone opening a TCP connection to 192.168.1.105 on port 33339. The history tab on VC running on the PC displayed "TcpMic.NewClient" which confirms the phone is able to make a tcp connection on port 33339 to the PC. So maybe this error message above is complaining about the TCP connection where it is not the real issue?
But I don't know what happens with the UDP connection and how it is necessary for Voxwav to perform its job. I suppose this is the part of the communication that is not working.
On a side note, the antena icon on Voxwav pro does not find the IP of the PC on this scenario and I suppose it is because of the broadcast that can't pass through from one router, through the switch and then to another router. ANyway, I have set the host IP for the UDP config on Voxwav manually to 192.168.1.105.
From the
wiki:
"Your Android device must be connected to the same LAN (local area network) as the PC running VoxCommando"
Technically, both the android and PC are in the same LAN in my case, but maybe you meant they should be on the same router?
Could you please give me some light on what can be done to fix it?