The MWS GW keepalives..

[teflondepa]

I am testing a nokia MWS GW in a WLAN and the data channels are not working.. What is the prefered keepalive state
- discovering or fixed

[jhnwkmn]

I am testing a nokia MWS GW in a WLAN and the data channels are not working.. What is the prefered keepalive state
- discovering or fixed

It shouldn't matter. In discovery mode, the initial keepalive period is as short as 3 seconds and is then incrementally made longer until the predefined maximum is reached, or it is detected that it has become too long at which point the period is shortened to the last known good.

In a WLAN context, discovery mode should just work and fixed as well, with any reasonable period length.

Johan

[teflondepa]

I have successfully installed the gateway and have smoketested it.. The control channels are working perfectly. I can see the connected musers but when I point the browser at http://<GW IP address>:8080/~<muserID>, I get a '404 not found' from the gateway tomcat server..

This is all on a LAN...

I know it is not necessary but are data channels supposed to work in a WLAN or LAN? Because even when I used the mws.connector.client, mws.httpclient to smoketest I could not browse to a particular muser's page despite the fact that they are online..

[jhnwkmn]

The control channels are working perfectly.

If the control channels are working (I assume you see the keepalive ticking), then connectivity-wise everything should be in order. The system works fine in both a WLAN and LAN context.

I can see the connected musers but when I point the browser at http://<GW IP address>:8080/~<muserID>, I get a '404 not found' from the gateway tomcat server..

Something must be astray in the muser setup. Are you sure you are trying to browse to the right URL? A muser's ID and his URL are not identical, unless you have created it that way.

Johan

[teflondepa]

I have set up the muser ID as the url, an have also tried it with the demo(http//:loclhost/~john.hacker) .. I can also see the keepalive tickings.

In the tamcat logs I found this:
com.nokia.mws.connector.server - Unknown element (newer protocol?)connector

- Doese this suggest protocol differences?

-Is Cadaver or any other Webdav client necessary for the functioning of the data channels?

[teflondepa]

I've managed to fix my problem..
Thanks for your help..