| Getting started. |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| philippe bruno New member Username: Tlk Post Number: 1 Registered: 04-2005 |
Hi. I'm getting started with wap gatways and wap technoglogies in general. I have a wap site setup and it displays correctly using my mobile's browser. I can download midi's without any problems. Thing is my buddy can't. He has a samsung a600 with bell mobility (canada) and when he clicks a link it play's back a midi instead of downloading it. Now I tried using gcd files to no avail. I would get a prompt asking if I wanted to "Launch this file now" and when I click yes. it ask's me if I wan't to download the heandler for this content in the web. If I click yes I get a "client sent malformed host header". So I figured there must be a comunication error. Basically my server doesn't understand what my mobile is telling it. On another cell phone (still with bell mobility here) I get an error 907 I beleive. Now I figure I'll install a wap gateway and it should fix the problem. My settings seem correct. Basically, what I wan't to know.. Is my reaserch headed in the right direction or am I completly off target. If I am, a nudge in the right direction would be greatly apreciated. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4459 Registered: 10-2002 |
Philippe, I don't think installing your own WAP gateway is going to make any difference. I think what you are experiencing is just that the user interface for how things are handled varies greatly between different browsers on different phones. I'm not familiar with the user interface of the Samsung A600 when it comes to downloading MIDI files, but I would expect that your buddy should have an option somewhere on screen to save a copy of the file. This all sounds like user interface issues on the browser, not anything at the transport layer. I'd need more details on the "907" error ... but it is possible that phone might not support the MIDI content type. I'd check the specs on the phone first. This issue is different from the first ... it could point to a case where a different WAP gateway could make a difference ... however, I still consider that unlikely because if one user on Bell Mobility can access the content, but another can't ... that doesn't suggest a compatibility problem with Bell Mobility's WAP gateway ... instead it suggests a compatibility issue with the phone. -bn | |||
| philippe bruno New member Username: Tlk Post Number: 2 Registered: 04-2005 |
Thanks for the reply bryce. I tried with two diffrent mobiles on the bell mobility network. Both failed. I can download without a problem (i'm with fido). Now here is what I'm doing.. very simple.. 1. create wml page 2. add link using a href tag to midi The real question is, what are the factors that can influence the download. What I have up to now is.. - Operator restrictions - Mobile incompatibility with midi files - Mobile settings what else am I missing. and keep in mind, other wap sites can send to my two bell phones without a problem. Only mine can't. I heard kannel supports alot of current and future mobiles. I was considering it but it linux based and I'm not very fammiliar with linux security, thought I should, I'm more of a microsoft guy..  I'm most probably going to purchase the nowsms wap gateway (won't have a choice in about 25 days) but I'd like to get it up and running before investing money on it. tlk | |||
| Kent Williams Moderator Username: Kent Post Number: 120 Registered: 10-2003 |
Philippe, Do you have the MIME type configured correctly on your web server? Whatever file extension you are using for your MIDI files should be associated with the MIME content type "application/midi". (You might have a situation where the phone that works just isn't particular about content types and tries to figure out the type based upon the actual content. But most phones are very particular about the content type being correct.) If you want me to try accessing a test file, post a URL, and one of us will check it out, and see if anything looks amiss. It's hard to say what all of the potential factors could be. I agree with Bryce that installing a WAP gateway is not always the best solution, because then you have to deal with changing phone settings. So it is usually for more specialised requirements. If you want to go ahead and try to set it up, there's really not much to it. Install it and start the service. The default values are fine, unless you need to enable the WAP2/HTTP proxy (used primarily by Nokia phones, but also a few others), in which case you need to define which port to use. Then you change the settings on the phone to connect to your WAP proxy. You might also need to change other connection settings to allow the phone to have an internet connection that can connect to a WAP proxy external to the mobile operator. If a phone is using the WSP stack, then it will connect on UDP port 9200 or 9201, which needs to be open. Basically, you'd look at the stats to see if the proxy is seeing any requests. If you edit the WAPGW.INI file (should be created automatically, but if you don't change any settings, it might not be ... this file is in the NowWAP installation directory), and add Debug=Yes under the [WAPGW] header, then NowWAP will log debug information as it runs. If there was any attempt coming through from a device to one of those ports, you would see it in that log. So if you're not seeing anything, your device is not actually connecting as far as the proxy, and you might need to change your other connection settings on the phone for general internet connectivity ... and/or change your firewall setup to allow the connection through. - Kent | |||
