vB Easy Archive - 8910 wap acting strangely

Pages: 1

8910 wap acting strangely
(Click here to view the original thread with full colors/images)

Posted by: arosboro

I've been working on setting up free wap. I've configured my own wap proxy using kannel on a linux server. I also forwarded port 9201 on my router. When I try to connect to openwave it times out. I changed the host config port from 9201 to 80 while trying things around after this failure and google loaded up.

I can't enter other addresses in openwave (doesn't appear to be an option in the menu) I've removed google completely from the host name in host config and I'm trying to connect to tagtag.com, but google.com continuously loads. (Openwave says it's the homepage or something) I don't know what port 80 would do that automatically starts google. I've never seen anything in the logs to make it appear that the phone has even attempted a connection.

Wap browsing does work using a nokia emulator on the local network with my kannel gateway.

I've tried regular proxies as well. Has anyone else have this problem?

If you have a working phone, pm me I'll send you my ip and port so that you can try (I'd appreciate the help)

Thanks,
Andrew

Posted by: 8910user15650

Verizon had disabled all free WAP solutions with it's new web features... since you've deleted your User/Pass from the phone, your only bet to get any type of WAP is to have it reflashed.

As of now, there is no way to get free WAP on Verizon's new phones (MW2.0 enabled phones)...

Sorry to break it to you...

Posted by: arosboro

I never had a verizon user and pass programmed into the phone, got it from ebay. The default settings for wap were for alltel.

I guess I just missed the boat on free wap :-/. Not that big of a deal tho, some how I can still get wap.google.com to come up if I change the host name to that and the port to 80, regardless of what my IP and authorization settings are.

tagtag.com does not work
wap.google.com, wap.yahoo.com do work

I just can't leave those sites with the phone's browser. And when I try to download content it gives me a 404 error.

I think Verizon must have been concerned most about people downloading "premium" content to their phones. They prefer getting those nickle and dime charges (but in this case $2.99 rather than $.05).