We're a small development team working on various mobile phones, including the majority of Nokia devices.
We're currently having problems with the Nokia 6600/Series 60 phones. Our midlets request information from remote servers using the normal HttpConnection methodology, i.e.
HttpConnection c = (HttpConnection) Connector.open("http://hostname/docname");
This works fine on Series 30/40 phones (i.e. MIDP1). In fact it works fine on Series 60 phones that connect using Orange GPRS settings and O2 [contract only] edited GPRS settings. However various providers and gateways do not work correctly.
For instance this connection method on O2 pay-as-you-go does not work with any GPRS settings on the Nokia 6600 (O2 have said that direct internet traffic is not allowed on pay-as-you-go), but obviously standard WAP browsing via the built-in browser works fine using these GPRS settings.
What we have concluded thus far, is that MID1 phones somehow wrap any http requests in some kind of WAP-Gateway friendly request, but MID2 phones do not - thus some WAP gateways are ignoring the requests.
Is there some way we can revert MIDP2 phones to use the original method?! Or is there a way of forcing the phone to using a WAP connection as opposed to the Internet connection?
The answer to this problem, I believe, will solve a hell of a lot of the http connection problems I've been seeing on all of the support forums. Any help from anyone will be much appreciated.
Have you tried whether the Opera browser works under the GPRS settings? I think part of the reason might be that your older phones are WAP-based while the newer ones are based on the TCP/IP wireless profile?
In general the latest devices use TCP/IP connections instead of Wap with or without a proxy. In order to make it work from within a MIDlet, almost all telco companies require to configure a web profile instead of a wap profile. In fact, for instance, using a wap profile with Nokia 6600 you can see all the requests coming from the IP address of the device assigned directly by the Access Point (GPRS) and not from the wap gateway, also if configured in wap profile. When connecting from MIDlets this device creates connection "jumping" any proxy you have configured. In these cases carriers stop the request that don't come from their proxy gateway. The only way to make it work is to use the web profile from where the carriers accept the requests. In other words for Nokia 6600 you need to configure to profiles: - a wap profile to download the midlets; - a web profile to connect from within the MIDlet itself.
For your infromation, following find some of the configurations available in telco operators here in Italy. - Vodafone: APN Wap = wap.vodafone.it and Gateway = 10.128.201.76 APN Web = web.omnitel.it
- Tim: APN Wap = wap.tim.it (requires authentication) and Gateway = 220.127.116.11 APN Web = uni.tim.it (requires authentication)
Also some Samsung and Motorola devices have the same behaviour. Siemens have two different settings (one for wap browsing and one for MIDlet connections) and for them is easier to configure.
Yes we realise this. Unfortunately this is the problem. On every phone the WAP settings will work in the browser, but the problem is a lot of various WEB settings won't, whatever the configuration (for example O2 block PAYG access to the WEB but not WAP). Is there anyway to fool (or actually use) the phone or gateway into thinking we're using?
Obviously this is whats happening with other phones (eg Nokia Series 30/40) as they work perfectly. [ September 17, 2004: Message edited by: Dean Pullen ]
posted 14 years ago
As far as I know there is no possibility... it is a matter of device profiles configurations. From MIDlet code you cannot manage this kind of settings :-( The only way is to force the device to ask to the user the profile for connections within MIDlets. Nokia 6600 already has this capability for default, SE P800 needs to select it in network configurations. However it supposes that the user, when asked, understand which profile to use... Ed