| How to verify compiled WML |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | ||||
| Facundo Batista New member Username: Fbatista Post Number: 1 Registered: 04-2004 |
I'm working in a mobile operator. We have a previous version of wap3gx, and now I'm trying Now.WAP Proxy 2.5, because we need to forward the MSISDN when using even newer phones that talk HTTP directly. So, downloaded it, installed, and started configuring. Set up the RADIUS so it forward accounting messages to Now.WAP. Set up Now.WAP to forward MSISDN only to our server (Apache on Solaris). Set up also proxy and other smalls configurations. So I tried with our new Nokia 5100a. Configured it to use a proxy and directed to Now.WAP. And works OK! Download the page and, tracing it with Ethereal, sends the X-MSISDN field. Then, I took an older phone: Nokia 3100. Everything worked allrigh with this phone before, but now, pointing it to Now.WAP, it gives me "File format unknown". So I started tracing. The information that the Apache sends to Now.WAP is exactly the same for both phones. This gives me the idea that the issue is in the compiled WML: for one phone it's ok (the newer one) but for the other don't (the older one). How could I verify that the compiled WML is OK? I attach in this message a zip file with: - phone-wap.txt: All traffic between the phone and Now.WAP . - apache-wap.txt: All traffic between Now.WAP and the Apache Web Server. - Wapdebug.log: The log of Now.WAP - Wapgw.ini: The configuration file of Now.WAP. The firs three files are about one session with the non working phone. Thank you for your help! . Facundo
| ||||
| Kent Williams Moderator Username: Kent Post Number: 59 Registered: 10-2003 |
Hi Facundo, Do you still have the old version? If not, can you advise what version of WAP3GX you were running previously? If possible, I would be very interested in seeing WAPDEBUG.LOG transactions of the old vs. new versions. I have difficulty reading text versions of Ethereal traces (too much information, and it makes it difficult for me to follow the packet flow, especially as all the text trace shows is Ethereal's interpretation of the data, not the raw data itself). A file that I could load directly into Ethereal would be helpful. Also, I'd be curious to see more WAPDEBUG.LOG. The WAPDEBUG.LOG in your attachment was of a different transaction from that of the Ethereal trace. In the WAPDEBUG.LOG the phone asks if the requested file has been modified, and the response is returned that it has not been. So I did not see the complete transaction information (try clearing the cache on the phone before you attempt again). It can be difficult to verify that the compiled WML is ok. Certainly, in your logs, Ethereal has no problem decoding it. But I would be curious to see the raw data directly. As your server is not directly on the internet, I would like to see a WAPDEBUG.LOG ... that way I can cut & paste the data from your WAP page, and run it through my test gateway here with different phones. -- Kent Williams Now Wireless Support | ||||
| Facundo Batista New member Username: Fbatista Post Number: 2 Registered: 04-2004 |
Kent: We don't have access to the previus GW,  I collected the info you need: pure ethereal traces, the debug log for the same transaction, and again the configuration file. Thank you very much for your help, we're in a hurry for buy the product but first need to solve this issue. . Facundo
| ||||
| Kent Williams Moderator Username: Kent Post Number: 60 Registered: 10-2003 |
Facundo, No worries. The problem is the character before "Desarrollo de Servicios", and there is some confusion about what character set this character belongs to, because there is no encoding parameter in the XML header. The following XML header would be appropriate: <?xml version="1.0" encoding="iso-8859-1"?> So that you don't have to change your content, I have replied to your e-mail and sent details on how to tell Now.WAP to specify "iso-8859-1" by default. -- Kent Williams Now Wireless Support | ||||
Zip with four files inside, described in the message body
