"Failed to respond" cause has been found for me

Question

I, like many of you, have been having problems with "xx failed to respond". I just found out from my ISP that the telephone company here (Pakistan) is blocking ports 5190 and 5060 which basically shuts down iChat and gives you that message. You can still text but audio and video are blocked. I guess they think I'll actually use the telephone and make them more money if they do this. The million dollar question...is there a way around this?

Answer 1

The plot thickens.
My ISP is routing my traffic through a tunnel now. I downloaded IPNetMonitorX and the tests seem to confirm that the tunnel is functioning if I'm interpreting the program correctly. I used some of the IPNetMonitors features to trace the route and discovered that I'm getting at least a .25 second delay consistently between two servers. Would that kind of delay cause a timeout issue that would result in me "not responding?" See below:
Hop     Sent     Rcvd     Seconds     IP Address     Name
1     YYY     YYY     0.001     10.0.0.138     speedtouch.lan
2     YYY     YYY     0.062     203.82.63.253     lo-0-bras.dsl.net.pk
3     YYY     YYY     0.063     203.82.48.125     fa-0-1-gw.dsl.net.pk
4     YYY     YYY     0.254     202.125.155.61     s4-0-1.rwp44d1.pie.net.pk
5     YYY     YYY     0.230     202.125.148.152     f5-0-0.rwp44c1.pie.net.pk
6     YYY     YYY     0.229     202.125.159.13     a1-0-201.khi77gw1.pie.net.pk
7     YYY     YYY     0.252     202.125.128.181     g5-0-0.khi77gw2.pie.net.pk
8     YYY     YYY     0.291     144.232.229.21     sl-gw28-nyc-0-1.sprintlink.n et
9     YYY     YYY     0.291     144.232.7.29     sl-bb21-nyc-10-2.sprintlink.ne t
10     YYY     YYY     0.290     144.232.13.64     sl-gw37-nyc-0-0.sprintlink.n et
11     YYY     YYY     0.291     144.232.228.74     sl-ameronl-16-0.sprintlink. net
12     YYY     YYY     0.298     66.185.151.50     bb2-nye-p0-0.atdn.net
13     YYY     YYY     0.304     66.185.152.201     bb2-vie-p12-0.atdn.net
14     YYY     YYY     0.296     66.185.139.83     pop1-vie-p1-0.atdn.net
15     YYY     YYY     0.297     66.185.141.118     dar2-dtc-s1-0-0.atdn.net
16     YYY     NNN          
17     YYY     NNN          
18     YYY     YYY     0.298     205.188.179.233     ibucp-vip-d.blue.aol.com
The second thing I discovered is that when I traceroute to login.oscar.aol.com I get up to one of their internal servers and then it never makes it to the final destination. I'm not sure if that is a protection feature and should be considered normal. See hops 16-18 above.
I rechecked my connection speeds and I'm at 460 down/319 up. I've also bypassed all routers and I'm connected directly via ethernet to the dsl modem. I'm not sure what else to try. Hopefully Apple reads these pages and realize they have a real problem based on the number of posts.