My ISP said they do not block ANY ports between 2000 and 6000. Period.
And I just want to be clear on this -- I have had this problem for literally 3 years. In that time, according to skuzzy's post, the ports used by the TA have changed repeatedly -- but even with those changes, the problem ALWAYS affected the TA and nothing else. (At least until orange came about.)
Next, I have had this problem on four different computers over this time frame. They do not have much in common at all, except that they connect to the internet through the same ISP.
Now, the same computer that cannot HEAR vox (sends just fine, remember) in the TA can hear absolutely fine with a different ISP. Makes software port conflicts very hard to accept as the problem== SAME computer, after all. And, from what I understand, both incoming and outgoing Vox uses the same port.
If the same port is used for both, how could a problem with only one be caused by a blocked port????
I have poiinted this out repeatedly, and it seems to me that this combination of facts makes the port VERY unlikely (almost logically impossible) to be the source of the problem. I don't understand why folks can't either tell me why this logic is flawed, or talk about something other than ports!!!!
_________
It seems to me -- as I've suggested several times -- that the problem seems logically most likely to come from removal of a tag, or blockage of a things carrying the tag, that tell AH "this is TA received vox." I can't see how anything else could do this in this particular way...but again, I'm not a tech guy. I'm stuck using general logic, and unfortunately I can't see how these other suggestions could result in what we see.