| LG phones and concurrent users. |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Joseph Smith New member Username: Falangjoe Post Number: 9 Registered: 08-2006 |
I have tested Nokia, Motorola, LG, Sony and Samsung phones with the Now WAP gateway. When I send MMS messages with the phones, all the phones except the Nokia and Samsung show up as current users for ten minutes after the message is sent. If I set Max Keep-Alive for Client Connections = 0. The only phones that show up as current users are the LG phones. The LG phones tested are the LG1400i and LG2000. How can I deal with this problem? Is my only option to set SesionTimeout to a smaller value? Thanks, Joseph | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6493 Registered: 10-2002 |
Hi Joseph, Unfortunately, it does depend on the behaviour of the phones. The "Max Keep-Alive" setting that you mention applies only to WAP2/HTTP clients. In general, WAP2/HTTP clients are much better at releasing their connection when they are done. I would not suggest setting this value to 0, as this disables keep-alive sockets, and some phones expect keep-alive sockets to be enabled ... you run into a problem where the phone will report an error after receiving a message, because it expects to use a keep-alive socket to post the receive acknowledgment. A value of 30 is quite reasonable if you are only supporting MMS traffic. The WAP/WSP clients are trickier. Some of these clients will disconnect their session when they are done ... some will not, even if they do release their GPRS session. We did make some changes in v2.58, where if you have a RADIUS accounting feed, we will drop the connection if RADIUS accounting tells us that the data connection has dropped. Aside from that, if the client does not disconnect, there is only a timeout setting in the WAPGW.INI file. Under the WAPGW.INI header, you can set SessionTimeout=xx, where xx is a value in minutes (the default being 10). For browsing, some phones will display strange error messages if the session times out. That is why we set this value to such a relatively high timeout. But if the gateway is only supporting MMS clients, then a timeout value of 1 or 2 is reasonable. -bn | |||
