| | Doesn't work for me ...
This sounds great, but it did not work for my Tmobile 6230 with 220.127.116.11.
We have our own 3rd party app that goes to our web service for data. Traditionally we've had to do the config string at the end of the uri to get through. Big hassle figuring out what all those are, not all carriers seem to provide them, etc. This would be a big boon.
I did what you suggested for Tmobile and removed my config string, so I was sending the URI, no trailing config string. No luck. Put back my config string and all worked OK. Having the wap.voicestream.com in the Status-TCP settings didn't HURT, but it didn't help either!
Any idea why this wouldn't work? or what this might mean? Makes me wonder about switching to this method for other networks, etc.