Hi,
I'm the developer of this application:
http://forum.xda-developers.com/showthread.php?t=586654
Two people are claiming that my app doesn't work over WIFI on their device.
In fact they can't even ping their device's Wifi interface IP address, although internet works.
So, outbound connections works, inbound connections doesn't.
And they have no firewall installed. How it that possible? Is there a rom/driver issue on some HTC devices? (one user has a touch pro, the other a touch cruise)
The weird thing is that the incoming connection works over USB (with the virtual network connection created by activesync/WMDC), pings succeed and my app works.
Has someone ever had the same issue?
I know it's not very common to use applications that need to handle incoming connections on a WM device...
It would be great if someone had an idea about the root of the problem!
Julien
Related
Does anyone know of a ROM in which the PPTP VPN actually works? I've tried 6 or 7 different roms today and have yet to find one that works. Is this a Google issue, or something else? Surely some developer must have tested this function and can speak to whether or not the VPN works. I recall that in WINMO only a few roms had reliable VPN functionally, Mighty Mike and Silence come to mind. Just to be clear...here is what is generally happening; the VPN connects without a problem. The RAS server displays the connection and shows packets in and out. Some roms will not route one packet properly to the device. Others will appear to work great, pinging remote resources, but as soon as you try to do anything else, i.e. RDP, the connection crashes.
Thanks
Is there a way to change the default wifi client ID that is transmitted to the wifi router when the phone is connected?
The default seems to be 'android_<somereallylongnumber>'
Is there a way to change this? It just helps sort out which devices are connected to which routers.....I've got something like 30+ wifi clients connected to numerous routers at home....it gets complicated sometimes.
I've noticed more and more devices are coming with an option to let you define the wifi Client ID that gets reported.
My WiFi calling at home is flawless so far. At work is a different story. I worked with our IT group to track down the lack of connection. Turns out our firewall was blocking SIP traffic. Easy fix. Now I get the blue icon, but calls have no audio on either end. No dial tone, no ringing, nothing. Back to the IT guys, this time they see my IP opening ports in the 58,000 to 59,000 range. They are unwilling to open those ports without good reason. My question is, why is the Kineto app connecting calls in the normal SIP port range, then dumping audio through ports in the dynamic & private port ranges? Does anyone know anything about how the Kineto VoIP client works?
Sent from my SGH-T889 using xda app-developers app
I'd be very curious on this too if anyone's got things mapped out better.
That is the way SIP phones work. SIP signaling is done usually at port 5060 and the rtp (audio) is in another random range. Most asterisk (Open source PBX) systems use 10,000 - 20,000 port range for signalling. But there must be another problem as those ports generally are opened by the outgoing connection and need not be left open by the router.
phinphan said:
That is the way SIP phones work. SIP signaling is done usually at port 5060 and the rtp (audio) is in another random range. Most asterisk (Open source PBX) systems use 10,000 - 20,000 port range for signalling. But there must be another problem as those ports generally are opened by the outgoing connection and need not be left open by the router.
Click to expand...
Click to collapse
The IT guys were perplexed also, since we use VoIP for many other applications without having this issue. In terms of running a secure network environment, I wonder if opening such a large range of ports for two-way RTP traffic is a good idea. The RTP data seems to want to hop around in the port range randomly, also. Our firewall is not letting the SIP client open those ports, since we have the ranges I mentioned earlier blocked. I'm still unclear whether the issue lies with the way Kineto set up the T-Mo client or with our firewall settings.
Here's ports I use for WiFi Calling (HTC Sensation, HTC Amaze, and Samsung S3) in my house.
UDP
Dst Port: 40000-59999
TCP
Dst Port: 500,4500,5060,5061
Make sure they're on the high priority list if you have QoS.
SiliconBug said:
Here's ports I use for WiFi Calling.
UDP
Dst Port: 40000-59999
TCP
Dst Port: 500,4500,5060,5061
Make sure they're on the high priority list if you have QoS.
Click to expand...
Click to collapse
It seems that the Kineto app is really not a very well designed tool. For example, Lync uses SIP for outgoing calls. It initiates the call using port 5060, then tunnels the RTP using SIP_TLS at that same port location. The more I learn, the more I see that real SIP applications are much more advanced than the one that got cobbled into our TMo ROMs. Even the open-source SIP applications use a fairly standard range of ports in the 10K - 20K range. The reason so many people have issues with the Kineto app is that is was designed in a way that makes it prone to failure. There are much better and more reliable ways to conduct RTP transfers. Let's hope the next ROM update sees a more advanced version of the WiFi calling application.
OwenW71 said:
It seems that the Kineto app is really not a very well designed tool. For example, Lync uses SIP for outgoing calls. It initiates the call using port 5060, then tunnels the RTP using SIP_TLS at that same port location. The more I learn, the more I see that real SIP applications are much more advanced than the one that got cobbled into our TMo ROMs. Even the open-source SIP applications use a fairly standard range of ports in the 10K - 20K range. The reason so many people have issues with the Kineto app is that is was designed in a way that makes it prone to failure. There are much better and more reliable ways to conduct RTP transfers. Let's hope the next ROM update sees a more advanced version of the WiFi calling application.
Click to expand...
Click to collapse
And it works so well for voice because it is flagged by Tmobile's servers and given some QoS. -Which is what I'm assuming based on my unscientific testing and years of using different Voip services.
Have you thought of using a software VPN AFTER connecting to wifi?
Is there any way for the fire TV to connect to it? My university uses it, and I was wondering if I could connect, but the access point is not showing up
Can´t look now because I´m not at home but wasn´t there a setting for a manual AP setup where you could enter the SSID by yourself?
Some organizations may keep a second network available for legacy devices like printers, XBoxes, and older machines. You can check with your university's tech support to see how you can add your device to the list of allowed access for that network.
This isn't a guarantee that this network exists for you, but most enterprise and even some residential-grade equipment have this capability.
Otherwise, you might be able to find a router or range extender that can understand and connect to WPA2-Enterprise to work around this. In a pinch, an old laptop with two wifi cards or a wifi Ethernet port should suffice.
Or you may want to scrap wifi and run an Ethernet cable to your dorm's jack or personal switch.
Related topics found through Googling, but no further help:
https://www.reddit.com/r/cordcutters/comments/2sv1ov/best_option_for_college_wifi/
https://www.reddit.com/r/fireTV/comments/2mydhh/fire_tv_stick_can_you_use_a_wireless_network_that/
Thanks the responses, but neither of them works well for me. there is a secondary unsecured wifi network, but it is just too slow to use, especially for streaming videos. I sideloaded a wifi APK onto it, and the networks DO show up, but there is no way to enter the login information (you need both a username and password.) Anyone know of an app that can do that?
I want to start out by stating this may be a general Verizon issue, but was hoping to get some input here first on the issue I'm facing.
My situation is that I want to replace my home cable internet with my LG G4 via tethering. I installed a wireless card on a desktop computer, connected it to VZW network via wifi tethering from the G4, enabled connection sharing on the desktop computer, then plugged an Ethernet cord from the desktop into the WAN port of my home firewall/router. This worked perfectly, giving the rest of my home devices internet via my 4G connection!
However I have some externally facing services, such as VPN and RD Gateway that don't seem to work over the 4G connection. I've done some troubleshooting and have a suspicion inbound communication on these ports is possible blocked by Verizon.
Sidenote - these services are configured with a Dynamic DNS provider - the external IP address does change correctly when I cutover to 4G service.
I reverted my home network back to the way it was and started focusing on the G4. I played with iptables (I'm rooted) with no luck. I attempted to open ftp connection to the G4 on port 2221 with no luck (using FTPServer & FTP Server Plus apps), still nothing. I changed the port a few times to something random > 1032, still nothing.
Does anyone know if Verizon is blocking external inbound communication, or possibly if there is something on the G4 I'm overlooking?
Any information is appreciated! If I can get through this issue, I can cut my ties to Comcast!!
Everything I've read in the past says that Verizon does not allow inbound TCP connections to your device via LTE. I'm guessing that the same applies to other wireless providers.