Sign up with GoogleI don't see it that way. The problem was reported more than 10 weeks ago (even 2 weeks to resolve the 197.x IP range is too long). They should have resolved it by now. I want a service that works, that is what I pay for.
-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
TCP connections stalling / Gmail, Gtalk, WhatsApp issues [fix in place - testing]
- Thread starter benitok
- Start date
I don't see it that way. The problem was reported more than 10 weeks ago (even 2 weeks to resolve the 197.x IP range is too long). They should have resolved it by now. I want a service that works, that is what I pay for.
Also not getting any 41.x IP addresses this morning yet, although my "unrestricted" APN is getting the normal 41.55.x range.
It does seem rather strange that Cell C simply haven't applied the "fix" in the 197.x range as they did with the 41.x range. Maybe there are some sort of technical hardware/system limitations?
The lack of feedback from Cell C can be frustrating, as we have no idea as to the progress.
They have indicated that a more "permanent" solution should be in place by month end.
We will see if they stick to this....
The_Unnamed
WUD FTW
- Joined
- Oct 14, 2010
- Messages
- 13,437
Am i missing something? I am always getting a 41.x IP and i still have the problem :-/.
The_Unnamed
WUD FTW
- Joined
- Oct 14, 2010
- Messages
- 13,437
I am on 41.48.25.44. Its never been working for me and i am always on the 41 network :-/.
shaunbrookes
Well-Known Member
- Joined
- Sep 16, 2009
- Messages
- 162
If virgin mobile works completely off the Cell C network, then why is it working perfectly on virgin mobile now? Can't cell c contact virgin mobile to find out what they are doing differently with their ip addresses / settings etc?
Sent from my GT-I9100 using MyBroadband Android App
Sent from my GT-I9100 using MyBroadband Android App
Something very different is happening here on the 41.x range at the moment.
Restarted my Cell C HTC Desire HD twice now to be sure.
Using GTalk for testing:
First, I disconnect and reconnect the mobile data connection for a "clean" session.
On reconnect, a port 5228 C2DM connection (critical for Gtalk and "push notifications") is established after a few seconds. (normal behaviour)
I then send a Gtalk test message from my Vodacom phone and it is received on the HTC within 2-3 seconds.
Now I wait for the magic 240 second period to elapse.
After around 5 mins, I send another Gtalk test to the Cell C HTC. (21h30)
After a few seconds, I see a quick burst of data and then the port 5228 connection promptly closes (observing with OS Monitor) without the test message actually arriving on the phone. (never seen this happen before)
After a period of time (haven't timed this yet), a new port 5228 connection is established and voila up pops the Gtalk test message! (21h43)
So, somehow this port 5228 connection is closing for some reason when it should not and while it is closed, there can obviously be no C2DM notification activity. It looks like a "watchdog" process (probably on the phone) then sees that this port 5228 connection is no longer active and establishes a new one.
This connection then works normally again with Gtalk, WhatsApp and Gmail tests, but 4 minutes after the last test activity, it is closed again by an incoming burst of data (another Gtalk test message)
Not able to get a 197.x range IP address at the moment, so can't check if this is happening there as well.
Edit:22h12
Managed to get a 197.x IP address.
What is happening now, is pretty much the same as before. (definitely delayed - push broken)
After 4 mins the Gtalk test message simply does not arrive. (no data activity is noted at all)
The port 5228 connection remains established and unaffected.
Why the difference then between the 41.x and 197.x ranges?
Well, we can only hope that some configuration work is being done to solve this problem issue and we are observing the effects of that.
Edit:22h26
Back to a 41.x IP address.
A Gtalk test message after the 4 minute period, definitely "kills" the port 5228 connection.
This time it re-established after 15 seconds or so and the test message popped up.
Not sure what is determining the period to re-establish this absent port 5228 connection.
Restarted my Cell C HTC Desire HD twice now to be sure.
Using GTalk for testing:
First, I disconnect and reconnect the mobile data connection for a "clean" session.
On reconnect, a port 5228 C2DM connection (critical for Gtalk and "push notifications") is established after a few seconds. (normal behaviour)
I then send a Gtalk test message from my Vodacom phone and it is received on the HTC within 2-3 seconds.
Now I wait for the magic 240 second period to elapse.
After around 5 mins, I send another Gtalk test to the Cell C HTC. (21h30)
After a few seconds, I see a quick burst of data and then the port 5228 connection promptly closes (observing with OS Monitor) without the test message actually arriving on the phone. (never seen this happen before)
After a period of time (haven't timed this yet), a new port 5228 connection is established and voila up pops the Gtalk test message! (21h43)
So, somehow this port 5228 connection is closing for some reason when it should not and while it is closed, there can obviously be no C2DM notification activity. It looks like a "watchdog" process (probably on the phone) then sees that this port 5228 connection is no longer active and establishes a new one.
This connection then works normally again with Gtalk, WhatsApp and Gmail tests, but 4 minutes after the last test activity, it is closed again by an incoming burst of data (another Gtalk test message)
Not able to get a 197.x range IP address at the moment, so can't check if this is happening there as well.
Edit:22h12
Managed to get a 197.x IP address.
What is happening now, is pretty much the same as before. (definitely delayed - push broken)
After 4 mins the Gtalk test message simply does not arrive. (no data activity is noted at all)
The port 5228 connection remains established and unaffected.
Why the difference then between the 41.x and 197.x ranges?
Well, we can only hope that some configuration work is being done to solve this problem issue and we are observing the effects of that.
Edit:22h26
Back to a 41.x IP address.
A Gtalk test message after the 4 minute period, definitely "kills" the port 5228 connection.
This time it re-established after 15 seconds or so and the test message popped up.
Not sure what is determining the period to re-establish this absent port 5228 connection.
Last edited:
Same story this morning.
IP Range 197.x
Gtalk test message does not arrive after 4 min inactivity period. (arrived 20 mins later)
IP Range 41.x
Gtalk test message "kills" port 5228 connection after 4 min inactivity period.
Connection is re-established randomly, anything from a few seconds to 10-15 mins later.
Test messages are then received.
IP Range 197.x
Gtalk test message does not arrive after 4 min inactivity period. (arrived 20 mins later)
IP Range 41.x
Gtalk test message "kills" port 5228 connection after 4 min inactivity period.
Connection is re-established randomly, anything from a few seconds to 10-15 mins later.
Test messages are then received.
Update:
Virgin Mobile on 10.192.219.225 seems to be having the same problem as the 197.x range, where Gtalk test messages simply do not arrive on the phone after the 4 min inactivity period. Port 5228 connection shows "Established" but no inbound message, until some random delay period later.
Even more interesting, an attempt to send a Gtalk message from the Cell C HTC on 41.x after the 4 min inactivity period, results in the OS monitor displayed "Established" port 5228 connection immediately disappearing, with a "server offline" warning in the Gtalk client App.
This warning is due to the port 5228 connection suddenly not being active anymore for some reason.
This connection is then re-established after a random period. Some test messages are received, but some messages are going "missing" as well.
Trying to test Gtalk between my Cell C (41.x) and Virgin Mobile (10.x) Android phones, is an absolute mess of delayed and missing messages after the 4 min inactivity period. Once the two phones have had their port 5228 connections "activated" properly again, test messages between the phones works perfectly. But, let the phones idle for just over 4 mins and....you get the picture!
Have no idea what Cell C have done, but this situation is definitely worse than before.
Something in their system, is seriously messing with this port 5228 connection, which is key to Gtalk messaging and C2DM "tickles" for proper WhatsApp and Gmail "push" (alert to poll) functionality.
Virgin Mobile on 10.192.219.225 seems to be having the same problem as the 197.x range, where Gtalk test messages simply do not arrive on the phone after the 4 min inactivity period. Port 5228 connection shows "Established" but no inbound message, until some random delay period later.
Even more interesting, an attempt to send a Gtalk message from the Cell C HTC on 41.x after the 4 min inactivity period, results in the OS monitor displayed "Established" port 5228 connection immediately disappearing, with a "server offline" warning in the Gtalk client App.
This warning is due to the port 5228 connection suddenly not being active anymore for some reason.
This connection is then re-established after a random period. Some test messages are received, but some messages are going "missing" as well.
Trying to test Gtalk between my Cell C (41.x) and Virgin Mobile (10.x) Android phones, is an absolute mess of delayed and missing messages after the 4 min inactivity period. Once the two phones have had their port 5228 connections "activated" properly again, test messages between the phones works perfectly. But, let the phones idle for just over 4 mins and....you get the picture!
Have no idea what Cell C have done, but this situation is definitely worse than before.
Something in their system, is seriously messing with this port 5228 connection, which is key to Gtalk messaging and C2DM "tickles" for proper WhatsApp and Gmail "push" (alert to poll) functionality.
Last edited:
shaunbrookes
Well-Known Member
- Joined
- Sep 16, 2009
- Messages
- 162
Started having problems on virgin mobile again today after it was working perfectly for 2 weeks.
Sent from my GT-I9100 using MyBroadband Android App
Sent from my GT-I9100 using MyBroadband Android App
Update:
The problem of port 5228 being "killed" has now showed up on the 197.x IP range as well.
Now on both 41.x and 197.x, an incoming Gtalk test message after the 4 min inactivity period, promptly kills the port 5228 connection. Connection re-establishes after some random period. Incoming message does seem to show up then.
Also, an attempt to send a Gtalk message on both 41.x and 197.x after the 4 min inactivity period, also kills the port 5228 connection, resulting in the message going "missing". Maybe it will show up later, who knows?
Edit: 21h03
"missing" messages never showed up over the course of the day.
What I have started doing now is putting a sequence number and time tag in each message, to help with tracking.
Would suggest if anyone else is testing, to at least use a time tag inside the message E.g. 2103
This will give a better idea of the delay periods.
Last edited:
Looks like the 41.x range is working properly again, with no delays so far this morning on Gtalk and WhatsApp.
197.x is still experiencing delays with Gtalk and WhatApp.
Gtalk message send attempts from my Cell C HTC, still result in the port 5228 connection being "killed" after the 4 min inactivity period, with the message going missing.
Seems like we are back to where we were before last Friday.
197.x is still experiencing delays with Gtalk and WhatApp.
Gtalk message send attempts from my Cell C HTC, still result in the port 5228 connection being "killed" after the 4 min inactivity period, with the message going missing.
Seems like we are back to where we were before last Friday.
falcon786
Honorary Master
- Joined
- Jan 29, 2011
- Messages
- 10,279
Dude they said they working on the problem...what more did you want from him i'm sure cell c doesnt wish to share their entire technical set-up with everyone,now he gives feedback you still criticize,geez some people are just impossible to please.
Be thankful that they not like mtn on this forum,non-existant.
All I'm saying is, give us some feedback. Don't disappear for days and leave us wondering what is happening.
Edit: The last post by Cell_C was on 08-09-2011 11:46 AM Post #252, which was 19 days ago.
Last edited: