SyncML Server not working

SyncML Server not working SearchSearch
Author Message
Kinjan Shah
New member
Username: Kinjan

Post Number: 5
Registered: 04-2005
Posted on Tuesday, June 14, 2005 - 05:16 pm:   

Hello All,

Here is what is happening with now.wap gateway while a SyncML client Application (from phone) connects to my SyncML server via now.wap gateway.

1. The server receives first request from phone which is wbxml understood by gateway and passed on to our server.
2. The server then processes the request and generates syncml (wbxml) response according to the request received.
3. The server adds following http headers to the response…
application/vnd.syncml+wbxml
content lenght
accept-charset=UTF-8
Cache-Control= no-store
Cache-Control= private
Transfer-Encoding: chunked
user-agent: the class name

Now here is the problem the response generated is either not reaching to the gateway because on phone it gives the error message “sync failed”.

The problem could be two things… either I am missing something in the code of the response or the gateway is not configured for receiving the response.

On gateway I am using HTTP (wap2) proxy port.

I need help from now.wap support to know what could be wrong on my part or if anything which is missing in configuration.

Please help me find out the solutions on this issue.

I am using my own dial up number to connect to the WAP Gateway

The same code works well with Vodafone UK gateway.

Thanks,
Kinjan
Kent Williams
Moderator
Username: Kent

Post Number: 126
Registered: 10-2003
Posted on Wednesday, June 15, 2005 - 06:57 pm:   

Hi Kinjan,

When you use the HTTP/WAP2 proxy interface, there is minimal translation that occurs.

I'd like to suggest the following:

1.) Configure the browser on the device to go through the WAP proxy, and make sure that it is able to browse ok (this will tell us if perhaps there is a problem with the proxy delivering the response to the device ... if it can deliver a page to the browser ok, it should be able to do the same for the SyncML server).

2.) Enable the debug log in the WAP Proxy. This is done by manually editing WAPGW.INI, and under the [WAPGW] header, adding Debug=Yes. Repeat your connection attempt, and reply back, posting the WAPDEBUG.LOG file so that I can see exactly what is going on.

--
Kent Williams
Now Wireless Support
Kinjan Shah
New member
Username: Kinjan

Post Number: 6
Registered: 04-2005
Posted on Thursday, June 16, 2005 - 02:48 pm:   

Hello Kent,
Thanks for quick reply...
please find attached here with WAPDEBUG.LOG as you asked for...

Thanks,
Kinjan
application/octet-streamWAPDEBUG.LOG
WAPDEBUG.LOG (85.5 k)