This way, In case I have a failed call, I'll have to retry once, then I'll have the right config next time. Then I check the list items, and if an IP belongs to Amazon, I add it to the Viber IP group, and Viber IP group is rerouted towards the secondary gateway. It will still be failed, but I'll have a (not too big list). Now, every time when I'm making a call and it fails, I start the IP collection, and retry the call. My list is growing, luckily not too much traffic goes towards Amazon servers during a (failing) VoIP call. So I started collecting IP addresses during failed calls. Okay, but we don't want to redirect the whole Amazon, right? Now, how to detect those IP addresses? As Viber uses Amazon, so theoretically, we can forward all Amazon IPs and then we are good. If also TCP443 was added to the list, Viber Android started working perfectly, but I don't want to limit myself, 443 is an important port, we shouldn't generally reroute it!īased on my research, Android application needs its traffic towards some IP addresses to be forwarded to the same direction as the ports above to be able to correctly build up the call. Traffic redirection purely based on these ports are
0 kommentar(er)
